Building Automation Knowledge Base

Issue Customer are running an ES with version 3.2.3 sending emails through SMTP server using TLS protocol. After site is upgraded to version 4.0.3, emails are not sent and the following error is shown in the ES: "SSL routines: tls_process server_certificate:certificate verify failed. Email service failed to connect to SMTP Server." In version 6.0.3, the following error is also displayed in the ES: "error:16000069:STORE routines::unregistered scheme" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 4.0.1 and later Building Operation Automation Server Premium (AS-P) version 4.0.1 and later   Cause The following is stated in the EBO version 4.0.1 release notes: "Certificate validation for SMTP When choosing TLS as encryption method (i.e. encryption of all traffic) for SMTP, then the certificate will be validated from EBO 4.0. If a corresponding CA-certificate isn’t present in the server, then a system alarm is generated. See more in “CA Certificate Management” ( also in section 2.17.5) how to import CA Certificate." Resolution In EBO version 4.0.1 and later a valid certificate needs to be installed if alarms should be sent when using TLS protocol in the communication to the SMTP server.

Issue Is there a way to tell if the battery is bad in a controller? Product Line Andover Continuum Environment BCX - 4000, 4040, 9640 ACX5740, 5720 Netcontroller II 9680 Infinet II controllers B3 controllers Cause Determine if a battery is good Resolution Battery health is tricky to measure.  Open circuit voltage COULD look ok with a marginal battery.  The only sure way is to pull the power on the Netcontroller and see if it holds the data for our specified time.  Most sites will not want to take their controller down for that long. Take the battery out and measure it with a voltmeter, it should read not much lower than --- BCX and ACX model controllers  3.6V Netcontroller II, Infinet II and B3 controllers 2.7V BCX Spec Battery section: Replaceable, rechargeable battery. Provides 30 days typical accumulated power failure backup of RAM memory All data stored in Flash on power loss. ACX Spec Battery section: Replaceable, rechargeable battery. Provides 7 days typical accumulated power failure backup of RAM memory All data stored in Flash on power loss. I2/B3 Coin type battery: The small coin battery in the i2 / b3 is rated 41mAH;  if you calculate based only on the SRAM and RTC current draw you get about 85 days.  Netcontroller II: The battery type here and SRAM are typical of infinet II controller battery life and will maintain backup of SRAM down to 2.7v. NOTE: Backup Flash is non-volatile memory and once written will hold unless manually cleared. SRAM is a part of memory that holds information as to where to start programs when power is re-applied to the controller in cases of main power loss. The problem is that battery life is highly dependant on number of charge / recharge cycles which is beyond our control.   You don't find the battery manufacturers giving such specs either.  Example:  The coin cells in our i2 / b3 have a shelf life "up to 10 years". Day to day use it is suggested that batteries should be replaced every 5 years.

Issue Windows authentication is not working with Security Expert once configured. Product Line EcoStruxure Security Expert Environment Security Expert Server Windows Authentication Cause Windows authentication was not installed or configured properly during initial install/setup of Security Expert. Resolution Install the Security Expert Server, and any Security Expert Clients, with the "Enable Windows Authentication" option enabled during the installation process. If this was not initially done at install then it will be required to backup the SecurityExpert and SecurityExpertEvents databases, uninstall Security Expert (installing overtop or repairing install may not work) and then re-install Security Expert with the "Enable Windows Authentication" option enabled.  Refer to Determining Security Expert authentication settings after installation to determine the authentication used. When Windows Authentication is enabled in the client go to Global (1) and select Operators (2).  Create a new operator as below: Select to add a new operator (1).  Enter a Name (2).  The name does not need to be the same as the operator's username. Enter a UserName (3).  The username must match the domain name and domain username required to have access to Security Expert.  This is in the form of "DomainName\UserName" as shown in the example image. Set a Role for this operator (4). Enable the "Use Windows Authentication" checkbox (5) and save the changes. Go to Global (1) and select Home (2) and logout of Security Expert. On the login page select the "Use Windows Authentication" checkbox (1), set the Server to the Security Expert Server machine name (2).  Leave this blank if it is the local machine) and press Log in (3). The system should now be logged into Security Expert with the Windows username being used.   If an "Access Denied" is received or another error then confirm the following before contacting Product Support for further help. Ensure Security Expert Client and Server were installed with the "Enable Windows Authentication" option enabled.  Refer to Determining Security Expert authentication settings after installation to determine the authentication used. There is an operator object created in Security Expert with the same domain and user name as the domain user required for login. The "Use Windows Authentication" option is enabled on this operator object. At the login screen "Use Windows Authentication" is enabled and the Server is set correctly.

Issue How can I determine which comm port on my Infinity Controller has been Xdriver enabled. Product Line Andover Continuum Environment Infinity Controller CX9900 (NC), CX9980 (NC2), bCX9640, bCX4040, ACX5720 ACX5740 XDriver, x-driver Cause Need to determine if the comm port(s) on a controller are XDriver enabled. Resolution View the controller options page in CyberStation or from the controllers webpage.  NC2 (NCII, NetController 2, CX9680) Option tab - example NC2 Xdriver Comm1 : 00000009 (0000)  (XDriver enable and but not loaded) Xdriver Comm2 : 00000000 (0000)  (XDriver not enabled) Xdriver Comm3 : 00000000 (0000)  (XDriver not enabled) Xdriver Comm4 : 00000000 (0000)  (XDriver not enabled)   bCX bCX9640 bCX4040 - NOT bCX4000 The bCX has two comms ports, the XDriver functions can be enabled on none, either or both at the time of ordering (add X1, X2 or X12) Option tab - example bCX Xdrvr Comm1:00000009 (DF23)  (XDriver enable and loaded) Xdrvr Comm2:00000000 (0000)  (XDriver not enabled) ACX ACX5720 ACX5740 The ACX57x0 has a single comm port, the XDriver functions can be enabled at the time of ordering (see the Option tab - example ACX57 Xdriver Comm1 : 00000009 (0000)  (XDriver enable and but not loaded) NOTES (00000000=XDriver not enabled, 00000001=CommPort only, 00000009=CommPort & Ethernet enable) The four digit number in bracket shows which Xdriver is load and corresponds to "Xdriver valid" at the bottom of the xdriver.xdr file. If Ethernet support is required on the port then this should be requested at the time of ordering. XDrivers like Modbus TCP/IP and Bacnet IP are loaded on to a comms port but communicate via the Ethernet port, therefore the XDriver Ethernet support needs to be enabled for these XDrivers to operate.

Issue Belkin Bluetooth adapter (F8T01n) on WIN 7 32-bit computer won't connect to MNB-ROAM-IA. Environment PC with Windows 7, 32-bit operating system Belkin Bluetooth adapter, model # F8T016 - F8T017 MNB-ROAM-IA WorkPlace Tech 5.x, configured for BACnet/ MSTP communications with MNB-ROAM-IA Cause The instructions for installing the Belkin Bluetooth adapter as documented in F-27578, TAC I/A Series ROAM-IA Quick Start Guide, "Windows XP-Specific Instructions for Bluetooth Installation", do not apply to installing the adapter on a computer with the Windows 7 operating system.  The procedure is substantially  different in "look and feel" on a Windows 7 computer than on a Windows XP machine - the instructions for Windows XP are not much help on a Windows 7 installation. Resolution The following series of screen captures will illustrate the procedure for installing a Belkin Bluetooth adapter on a Windows 7, 32-bit machine. 1. According to the Belkin FAQ shown, "Most Belkin Bluetooth USB adaptors install automatically without any extra software on Windows 7. Simply plug the device into a spare USB Slot. Windows 7 should automatically recognize the device and install the necessary drivers and software."  This was the case on the laptop PC tested, a Dell Latitude E5500. Screen prompts indicated that the drivers were loaded successfully, and the device was ready to use. 2. Open the Device manager, and there will be a folder for Bluetooth Radios. Expand the node, see the Generic Bluetooth Adapter. 3. Switch on the MNB-ROAM-IA. A Bluetooth icon will be added to the Windows Toolbar. 4. Click on the icon to bring up a menu. From the menu, select "Add a Device". The wizard will search for Bluetooth devices within range, should find the tac-RoamIA:nnnnnnn, where nnnnnnn is the serial number of the MNB-ROAM-IA. This should match the label on the back of the MNB-ROAM-IA 5. Pressing the "Next " button will bring up the "Select Pairing Option" screen. 6. Select the middle option, "Enter the device's pairing code", and press "Next". This brings up the following screen.  Type the pairing code "tac" in the box. The code is case-sensitive, must use lower-case as shown. 7. When the MNB-ROAM-IA has been successfully added and paired, the wizard will display the status. 8. Click on the hyperlink for Devices and Printers to verify that the device has finished installing properly, as follows. 9. In the Windows Device Manager, a Bluetooth Radios folder should be displayed. Expand the folder to see the Generic Bluetooth Adapter. 10. Right-click on the Generic Bluetooth Adapter, go to its Properties, Driver tab. The driver shown (6.1.7600.16385) was installed when the adapter was first plugged into the USB port   11. In the Device Manager, expand the ports folder, and two "Standard Serial over Bluetooth link" ports are shown, COM15 and COM5 12. Use the port with the lower number in the WorkPlace Tech communications setup for the MNB-ROAM-IA. In the example shown, COM5 is selected. Press the "Test and Configure Connection" button. 13. When communications are successfully established, the blue LED on the MNB-ROAM-IA will be ON continuously.

Issue Information for replacement for the SPA1505 and SPA1506 Product Line Field devices Environment Pressure sensors Cause "PA-00167 Sensors and Input Devices New SPP930 Relative Pressure Switch" suggests SPP930 replaces SPA 1505 and SPA 1506. The link provided for the SPP930’s manufacturer’s data sheet, no longer works Resolution SPP930 Part number 004701160 replaces the SPA 1505 SPP930 Part number 004701170 replaces the SPA 1506 The site wiring should be checked, to ensure it complies with replacement switches reduced current ratings.   SPA 1505/1506 data sheet Huba Controls type 620/625 data sheet.

Issue Java 8 is only supported together with TAC Vista 5.1.9 Product Line TAC Vista Environment Webstation Xenta Server web Cause The current version was developed and tested together with Java version 7, but not Java version 8 as Java 8 was released subsequently After the latest update of Java (Java 8u31) SSLv3 has been disabled by default in Java. If updating to that version of Java, the Xenta Server web (graphics and schedules) will not work, as the Xenta Server relies on SSLv3. Resolution Making the proper configurations has enabled a number of sites to use Java 8 with the TAC Vista product range. Java 8 is supported for TAC Vista 5.1.9 according to TPA-VSTA-15-0000.03 Refer to this video for settings required: Download video - View on YouTube   The proper settings in Java are: [1] Install the newest version of Java. If you are working on a 64 bit operating system, it's crucial that you install both the x86 and the x64 versions: https://java.com/en/download/manual.jsp [2] Make sure all older versions are removed: https://java.com/en/download/uninstallapplet.jsp [3] Make sure Java is enabled in your browser: https://java.com/en/download/help/enable_browser.xml [4] Add all addresses to the site exception list in the "Security" tab. Both http and https addresses are needed for Xenta Servers. If a special port is used (not 80 for http and 443 for https), the port needs to be entered, e.g. http://IP_ADDRESS:81 if port 81 is used for HTTP communication. [5] Click "Restore Security Prompts" in the "Security" tab. [6] In some cases you might need to add the IP address of the PC or Xenta Server to trusted sites in Internet Explorer   TAC Xenta Server web uses SSLv3 for Java if high security is set in XBuilder. The workaround for SSLv3 being disabled in Java 8u31 and above is: (read Java's own release note) [1] Edit the following two files: C:\Program Files (x86)\Java\jre1.8.0_31\lib\security\java.security C:\Program Files\Java\jre1.8.0_31\lib\security\java.security [2] Scroll down to the last line where it says: jdk.tls.disabledAlgorithms=SSLv3 In both files, comment that line so it says: #jdk.tls.disabledAlgorithms=SSLv3 [3] Edit the file: C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\deployment.properties [4] Add the following line: deployment.security.SSLv3=true

Issue When saving or importing a MTA (Menta) file in SmartStruxure Workstation, and error is shown indicating that there are more than one occurrence of one or more file types in the MTA file. Product Line EcoStruxure Building Operation Environment Workstation Menta Function Block Cause A MTA file contains various files that together forms the complete program. In some cases (e.g. when using a . in the MTA file name) various occurrences of the same file types will be placed in the MTA file. Resolution Open the MTA file in with the Menta editor Mark everything and export as an AUT file Create a new MTA file Insert the AUT file created in step 2 Save the MTA file only using standard characters Import the the MTA file Generate the MTA file to ensure you have no errors and all the public constants have been updated.

Issue Use the block DI to monitor an IO module, and generate an alarm when it is offline. But the above-mentioned function cannot be realized. Product Line TAC Vista Environment Menta Xenta 301, 302, 401 Xenta I/O Modules Cause If there is a configuration error in block DI, the right alarm cannot be generated. It is necessary to check and correct the configuration error. Resolution Create and configure the block DI and Alarm block according to the following procedure, then the IO module status can be monitored. When it is offline, an alarm will occur in the alarm window in TAC Workstation.   1. Create a block DI. (See the Figure 1) Figure 1 2. Edit the block DI and input DI identifier such as the monitored module name, Status_411 in instance. (See the Figure 2)           Figure 2 3. Click BIND in Edit window, select the Online Device in BIND TO column, and input the IO module number in DEVICE ADDRESS. (See the Figure 3)               Figure 3 4. The module number can be found in IO Expansion and Wall Module Table of DEVICE SPECIFICATION in Menta Options toolbar. In the under instance picture, the M1 module, TAC Xenta 411, its device address is 1; the M2 module, TAC Xenta 421A, its device address is 2; and so on, the M5’s device address is 5. (See the Figure 4)       Figure 4 5. After creating and configuring the block DI, the block Alarm should be created. (See the Figure 5)                Figure 5 6. Then connect the block DI and Alarm. When the IO module is online, the DI value is generally 1. So the block NOT must be used. (See the Figure 6)         Figure 6   You can also reference Monitor the online status of a base unit's associated I/O modules.

Issue Configuring the Workplace Tech encrypted LON Tunnel Client  Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.9.4 Click for WorkPlace Tech 5.10.4 information I/A Series N4 Jace Cause How to handle the encrypted LON tunnel for single and multiple LON networks.  Understanding possible errors during tunneling. Resolution The following video will help us, Apply the Encrypted LON Tunnel in an N4 Jace Configure the Tunnel Client for use with multiple LON Networks on a single Jace Recognize a Timeout Error and how to handle it

Issue When launching a program or when working with a program, you get an error from "Microsoft .NET Framework".   Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC INET, TAC Vista Environment Windows .NET Framework Cause Microsoft .NET Framework is used in almost all larger applications, and there can be various reasons why you see an error. One reason can be application specific, meaning that there is an actual issue with the software and the way the software is using .NET Framework, but another reason can be that the .NET Framework installation itself is corrupted. If it's an application specific issue, you need to contact product support, but in many cases simply repairing the .NET Framework installation has proven to solve the issue. Resolution 1: Close all applications 2: Make sure you have the correct version of .NET Framework installed for the software you use referencing the product's data sheet. You can use this tool to check what versions you have. Here is a direct download link. 3: Install versions that might be missing. You can download the various versions from the tool linked above. 4: Download Microsoft's .NET Framework repair tool and run it applying all fixes the tool suggests. Here is a direct download link.

Issue Untranslated infinity error when creating object in b3 or i2 device. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Infinet i2 Controller BACnet b3 Controller Cause b3/i2 devices do not support certain characters in their objects name. Resolution b3/i2 devices do not support certain characters in their objects name. For example, creating an analog input using the name AI-1 will cause the error is the BACnet field is left blank, the EBO name AI-1 can be used but a name needs to be specified in the BACnet name field that is consistent with the b3 naming convention such as AI_1.

Issue Can the current revision of I/NET Seven Software CD key be used to install older revisions of I/NET Seven Software.  Site has a revision of I/NET installed older than the current release version and additional Site or Seat License is required for the site. Upgrade or revision changes. Product Line TAC INET Environment TAC I/NET Seven Cause Additional License Seats requested by site\customer. Resolution Only current revisions of I/NET seats are available for purchase. Current revision of I/NET Seven Software CD keys are backward compatible within the same major revision release (i.e. 2.40 CD keys are compatible with any 2.XX revision.) Every computer which has I/NET installed must have a I/NET CD regardless if the site is HVAC, Security or both. At a site which has a StandAlone with I/NET, it must have a Site License. If I make that a FileMaster and add one Equalized Client, a SEAT license must be purchased for that Equalized Client. If I add another Equalized Client(s) or perhaps Remote Client(s) additional SEAT licenses must be purchased for those.  The license key is registered to the site, see I/NET CD Key and software revision for more information. When looked up, it reveals how many licenses (Site or Seat) have been purchased for that site. After the initial purchase, any I/NET PC upgrade uses Part Number INETSEVEN24U If upgrading Site computer use Part Number INETSEVEN24U If upgrading File Master use Part Number INETSEVEN24U If upgrading Equalized Client computer use Part Number INETSEVEN24U If upgrading Remote Client computer use Part Number INETSEVEN24U If there is a separate database for a site, let's say they open a new building with INET install with a different db, then an additional Site license is required which would be a new license key. For the latest version information check Software and Firmware compatibility matrix for older versions of the traditional product lines   Upgrade orders can be placed using the following part number: P/N: INETSEVEN24U TAC I/NET Seven Software CD TAC I/NET Seven Getting Started - TCON298 Software License Agreements TAC I/NET Seven Software Box New software orders can be placed using the following part numbers: SEVENMAXR - HVAC & Security site license, w/ CD SEVENHVACR - HVAC only site license, w/ CD SEVENSECR - Security only site license, w/ CD SEVENADDHVAC - Add HVAC, site license only SEVENADDSEC - Add Security, site license only SEVENSEATR - HVAC & Security license for 1 workstation, w/ CD, site license required SEVENSEAT3 - HVAC & Security license for 3 workstations, w/ 3 CDs, site license required SEVENSEAT5 - HVAC & Security license for 5 workstations, w/ 5 CDs, site license required SEVENMANUAL - Manual set, 3 volumes. No CD   Example: The site is currently at I/NET Seven Software Revision 2.14 and requires the purchase of additional seat licenses. The newly purchased seat licenses are the current I/NET Seven Software Revision 2.47. Two options available: 1) Use the newly purchased I/NET Seven Software revision 2.47 seat licenses to install the I/NET Seven Software revision 2.14. Upgrade the sites original licenses from I/NET Seven Software revision 2.14 to 2.47 Older revision I/NET Seven Software can be obtained from either the original CD Media or can be downloaded from EcoBuilding Download Center. Example 2: A site has an existing Host File Master, and Five(5) SEAT licenses(Equalized Client or Remote Client). To upgrade, they would purchase six(6) INETSEVEN24U part numbers which is for each of those workstations. To add an additional I/NET workstation, they would purchase a SEVENSEAT, which is the additional SEAT license.  

Issue The object identifier of a BACnet device (device id) must be unique internetwork-wide, different vendors use different methods for calculating the device id default value. When integrating devices from different vendors sometimes it become necessary to change a device's default object id. Product Line Andover Continuum Environment bCX4040 b3s Third party BACnet devices Cause BACnet integration Resolution If the BACnet device is a Continuum device (bCX4040 or b3), Continuum provides a mechanism for changing the default device id. For a third party BACnet device, VTS can be used to write to the Object Identifier of the device in order to change the device id. Note that this will only work if the device manufacturer has made the object identifier for the device object writable. Click here to download VTS Click here to see the procedure to follow to set a third party device id using VTS.

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 Cybersecurity vulnerability scans are flagging the Building Operation License Server because it is using HTTP rather than HTTPS Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation License Server Cause The Building Operation License Server contains a web portal for diagnostics and administration. By default, the Building Operation License Server Administration web portal is configured to use HTTP Resolution It is possible from the Administration area of the Building Operation License Server Administration web portal to configure HTTPS communications. Note: this does not change how Ecostruxure Building Operation connects to the license server.   The following process configures the Building Operation License Server Administration web portal to use HTTPS   From a web browser open the Building Operation License Server Administration web portal by typing http://localhost:8888 Once the web portal opens, select Administration at the top right. You will be prompted to log on, use "admin" as the user name. If you have logged in before, use the password you have defined. If not, enter "admin" as the password, and you will then be prompted to create a password. Once signed in Select the Server Configuration tab. Under the Secure Web Server Configuration section, select Enable HTTPS Change HTTPS Port to a unique number e.g. 8443 Select Redirect Non-Secure Web Access to Secure Web Access At the bottom of the page click the Save button and close the web browser tab. Restart the Building Operation X.X License Server from the Windows Services app (services.msc) If the license server is opened using http://localhost:8888 it will now redirect to HTTPS using the port specified in step 4 above

Issue Using a Lon Binding in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Cause Binding LON objects to LON objects using the SmartStruxure Variable Connector can cause increase traffic on the LON FT-10 network. Resolution To correctly Bind the LON objects: Edit this bindings of the node object, (not the SNVT object) Use the binding Browser to navigate to the appropriate node/SNVT to bind to Drag and drop the object to create the bind When you are finished you will see a Hexagon button, which will allow you to edit the Lon Binding Properties. This is the indicator that you are using a LON binding and not a Variable Connector object, which would be represented by a gear and pencil icon. Click the Hexagon to edit the Lon Binding properties Do not use the default of Acknowledged Profile.  Unless the device has a specific reason not to, the best option is to use Unacknowledged Profile.  Please see below for the explanations of the LON Message ServiceTypes. Message Service Type You can specify one of the following message service types for each connection description. The message service types vary in reliability and resources consumed. • Acknowledged - means that the sending device expects to receive confirmation from the receiving device or devices that a network variable update was delivered. The sending application is notified when an update fails, but it is up to the developer of the sending device to handle the notification in the device application. While acknowledged service is very reliable, it can create excessive message traffic, especially for large fan-out or polled fan-in connections. When acknowledged messaging is used, every receiving device has to return an acknowledgment.  Acknowledged messaging can be used with up to 63 receiving devices, but an acknowledged message to 63 devices generates at least 63 acknowledgements—more if any retries are required due to lost acknowledgements. • Repeated - means that the sending device sends out a series of network variable updates, but does not expect any confirmation from the receiving device. Repeated service with three repeats has a 99.999% success rate in delivering messages. Repeated service provides the same probability of message delivery as acknowledged messaging with the same number of retries, with significantly lower network overhead for large multicast fan-out connections. For example, a repeated message with three retries to 64 devices generates four packets on the network, whereas an acknowledged message requires at least 64 packets • Unacknowledged - means that the sending device sends out the network variable update only once and does not expect any confirmation from the receiving device. This message service type consumes the least amount of resources, but is the least reliable.

Issue Is it possible to open TGML links in a new window or tab in Workstation? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The user wants to keep the current graphic open and open a new graphic/calendar/function etc so that both can be viewed simultaneously. Resolution Hold down SHIFT key whilst clicking on the link.

Issue Create EWS between SmartStruxure and SmartStruxure Lite Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation site SmartStruxure Lite site Cause Steps to create EWS (EcoStruxure Web Service) between SmartStruxure and SmartStruxure Lite Resolution Release requirements: SmartStruxure Building Operation Release 1.3.938 and higher SmartStruxure Lite Version: Schneider Electric 2.7.0 and above Verification the Enterprise Server is running Open Building Operation Software Administrator. If Status shows Stopped, you must configure Building Operation. Otherwise, proceed to step 2. Ensure all Ports are correctly configured. Click Start Service and wait until application running shows in Path field. Click OK. Building Operation is now ready to integrate with SmartStruxure Lite The following example is using Server 1 in System Tree tab. In System Tree tab, right-click on Server 1. In newly opened window, select New. In newly opened sub window, select Interface. Click on Web Service to expand. Select EcoStruxure Web Service. In Name field, enter EcoStruxure Web Service. Click Next button. In Server field, enter IP address of Multi-purpose Manager (MPM) Controller you are connecting with. In Protocol field, ensure Communication port matches that on your server. In SOAP Endpoint field, enter ews in lower case letters. Take note that from SBO version 1.5 onwards, 'SOAP Endpoint' has been renamed to 'EWS Path'. IMPORTANT: You must enter ews in lower case letters in step 11. NOTE: If you are connecting to another StruxureWare Server, you must use an account that is in the default domain for log in credentials. Click Create button. Allow database to save completely before moving on to next step. In Server Tree tab, ensure new interface shows. You are now ready to connect your MPM Controller with Building Operation. Refer below to “Procedure - Connect MPM Controller to Building Operation." Procedure - Connect MPM Controller to Building Operation Ensure your MPM is physically connected to your workstation. In Server Tree tab, expand System folder. Expand Hardware folder. Expand EcoStruxure Web Services folder. Right-click C2G_root folder and select Host EWS Objects in sub window. Expand EcoStruxure Web Services folder. Select EcoStruxure and then select Web Services Properties Tab. Set Alarm Polling to Disabled. Procedure - View and Watch Data Points Expand CAN2GO controller. The List View tab shows all Objects available in Device. NOTE: EWS Consume in Building Operation server does not support connection over a ProxyServer.

Issue What is the difference between "Enhanced MSTP" and "Standard MSTP" Token Passing in Continuum BACnet? Environment Continuum BACnet Cause It is important to note that Only Continuum BACnet controllers have this feature. Any third party BACnet MSTP controller connected to a Continuum BACnet system will only perform Standard MSTP token Passing. In a network where you have Continuum B3 controllers and third party MSTP controllers and you have enabled Enhanced MSTP, you will have a combination of the two methods. The Continuum B3's will always pass the token back to the BCX, and the 3rd party controllers will always pass the token to the next ID on the MSTP. If you wanted the benefit of Enhanced MSTP on this type of a system, you could intersperse the MSTP ID's of the B3's and the third party so that you would have a more even flow of the token back to the BCX. Resolution Continuum Bacnet Controllers default to "Enhanced MSTP". What this means is that the Ethernet level controller (BCX or B4920) that manages the MSTP network sends out a message to all Continuum B3 controllers which tells them that after they are done with the token on the network, that they should pass it back to the BCX or B4920 instead of sending it to the next B3 down the line. The purpose of this is so that any user interaction with the B3 network such as graphics, listviews, reports, etc.. will be much faster. This Token passing scheme is similar to how Infinet performs. Standard BACnet MSTP token passing is done such that each controller on the MSTP network gets the token equally and this includes the BCX or B4920. So if you had 127 nodes on the network, the BCX controller would only get a chance to talk once after every MSTP controller had a chance to talk. The Continuum BACnet controllers can operate in either mode by setting this feature in the BCX or B4920 Web Configuration page. Each token Passing scheme has some benefits. If there were a lot of user interface type access needed on a system, the Enhanced mode would be preferable for speedy response. If there was very little or no user interaction but there was a lot of data sharing or alarm delivery from the MSTP controllers, the standard token passing would give all the devices on the MSTP network more opportunity to export their data.

Issue How to create a workspace with a banner and a TGML graphic as the home page.  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A graphical overview of a building or area containing a number of buildings can be a logical way for a customer to navigate around a site in Workstation. Resolution Preparation Create a folder to contain the graphics and banners to be used. Create a Panel object Right-click the folder and select New->Panel. Set the initial path (ie. the home page) to the desired graphic.   Add a graphic pane to the panel. Edit the graphic pane and select the banner graphic to be used. Set the desired layout settings such as Default dock position to Top.   Create a workspace Click on the control panel icon. Select User Accounts - Account Management and then under the Workspaces section click on Add. Select the desired security and authority settings. Add a Panel Pane to Workspace. Edit the Panel Pane and set the initial path to the Panel object created in step 2.   Assign the workspace to a user group Under the Select User accounts - Account Management menu in the control panel select the User Group that is to use this workspace. Edit the User Group and go to the Workspaces tab. Highlight the appropriate workspace and add it to the Select Workspaces pane by clicking on the arrow.   Test the workspace Log in with the appropriate user and confirm the layout is as desired.