Building Automation Knowledge Base

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

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 How to bring a BACnet controller online after restoring a backup Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Customers may want to take a backup from a site and use it on other setups. If there would be any BACnet controller under the Backup, they may need to know the process of hosting the BACnet controllers under the restored backup on the physical BACnet controllers.   Resolution This video will demonstrate how to bring a BACnet controller online after restoring a backup. NOTE After matching up the Device ID of the BACnet controller under the restored server and the Object ID of the physical BACnet controller, if the hosting status shows “Not hosted”, users need to perform a "Repair Hosting". Please refer to Repair Hosting a BACnet/IP controller 

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 When adding a new Domain an error shows “Object does not exist – The domain “your Domain Name” does not exist, and the Domain is not created.   Using control panel Or using System/Domains folder Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Building Operation Enterprise Central Cause A Content Type rule could be incorrectly configured Resolution Navigate to /Your Server Name/System/Content Types/Rules/ If there is a “*” in the “Container Name Pattern” of any of the rules, correct this or delete the rule.     Once completed, new domains can be added.

Issue If the AS is configured to get the time from an NTP server the customer need to know how often the AS will ask the NTP server for the time.    Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Central  EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server (AS/ASB/ASP) Cause In version 1.4, the AS asked the NTP server 1 time per minute. Starting in version 1.5, this was changed so the AS is using the standard solution for the NPT protocol. Resolution When using the standard solution in the NTP protocol as the AS does starting in version 1.5, it depends on how much the AS drifts from the NTP server. The faster the AS drifts, the more frequently the time is updated.   For more information regarding Network Time, please see WebHelp article 6370 and corresponding articles. 

Issue When a local user belonging to the administrator group on an AS-P is logged in to the AS-P using Workstation the user can for example via a Link in a graphic access the system folder in the ES the AS-P is connected to.  The local user in the AS-P can even change the admin password on the ES. How can this be avoided? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Cause In EBO v3.2.1 and later versions, it is possible to restrict access of the logged-in user to only the server that they are logged into, i.e. it is possible to prevent access to the ES\Servers folder when logged directly into an AS-P that is a sub server of the ES, thus preventing access to the whole system. Resolution In the ES Control Panel open Security Settings: Mark the option "Restrict root permission to logged in server"

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 client can't start properly with "Hardware virtualization is not enabled" error. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) (All Versions) Cause Hardware Virtualization is Disabled or not available for PCT Resolution  Install "Intel® Processor Identification Utility" then verify the status of "Intel® Virtualization Technology" from the Utility. Using the table below, you can see if your processor supports Intel® Virtualization(provided by Intel).  The above information can also be found on Intel® Virtualization Technology web page If Virtualization is disabled in BIOS then enable it from BIOS else identify other software utilizing the Virtualization and stop the application.  Use Win key or press the Windows Start button Type: cmd Select Run as Administrator  Verify command prompt window title bar is Administrator: Command Prompt Type: shutdown /r /fw/ /f  Press enter and the computer will shut down immediately forcing all applications to close (/f) and restart (/r) into firmware interface (/fw)   If the issue persists, the following article may provide the answer Knowledge Base article - PCT error Hardware-virtualization is not enabled-Please-enable.

Issue Unwanted hardware and other alarms received at Enterprise Server Product Line Satchwell BAS & Sigma, EcoStruxure Building Operation Environment EcoStruxure Building Operation Sigma Release 4_08 (Build 3_46_57) Cause Unwanted Sigma hardware and other alarms received at Enterprise Server. Resolution Navigate through the “Sigma interface”, to the controller (OSN) that the alarms need to be disabled from. Select the controller’s property (basic tab), Device monitoring can be enabled or disabled.     If you need to disable the alarms for multiple controllers, this can be done by multi selecting the required controllers, opening the property panel and change the setting there.  

Issue The BACnet Interface Contains a Yellow Exclamation Icon and when you hover over to read the tooltip it states, “Contains Unresolved BACnet Reference”. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Building Operation Multi-Purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller Building Operation IP-IO Cause There is a reference misconfiguration within the “Time Synchronization Recipients” under the BACnet Interface. Resolution Select and highlight the BACnet Interface then select the Time Synchronization Recipients TAB Compare the list Names with the list to the left under the IP Network Tree. In this example, we can see that MPV-9A is not a controller within my database under the IP Network_2. Highlight/Select the controller under Time Synchronization recipients and edit the details by clicking on the pencil icon. Within the Time Synchronization Recipient screen, we want to adjust this device to match the ACTUAL device located under our IP Network_2 named MP-9A_Roof. Click on the “three dots|ellipsis “to browse to the correct Recipient device identifier. In this example: Select the BACnet Interface > IP Network_2 > MPV-9A_Roof as this is the correct path for this device. At this point, we have the correct path under the Recipient device object reference. Adjust the Recipient name to match the BACnet name you configured for that device. In this example, it was set to MPV-9A_Roof. TIP: Click the BACnet button to fill in the recipient name field with the BACnet name of the device referenced in the recipient device object reference field. Click OK. If this is the only device you need to modify then you can click the SAVE icon. If you have more devices to adjust, then you will repeat the process until you're done with all the devices. You have now resolved the reference errors against the BACnet Interface.

Issue Testing Modbus device with a Modbus simulator. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Enterprise Server Modbus Protocol Cause The field device and Modbus registers can be tested with the Modbus simulator to ensure the device is set up correctly and communication is working. Resolution Once a device is tested with the Modbus simulator, the live Modbus device can be implemented with confidence knowing that the setup in the Server is correct.   Here you can download the Modbus Simulator    Review the following video to assist with the following: Run the ModRSim application Setup the simulator to display the values you need to test Adjust values checking that they are updated by the polling device Display the Modbus traffic and capture traffic if fault finding is needed.  

Issue Need to ensure that there are not any unresolved or invalid bindings Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation v1.5 and above Bindings Diagnostics Cause Bindings are invalid because they point to something that cannot be bound together or they are unresolved because the binding points to an object that is not in the database. Resolution From the Workstation run the Bindings Diagnostics to check for invalid or unresolved bindings.   Open the Control Panel To Check the Status of Bindings  click the option for Bindings Diagnostics.   Observe the Status to identify any invalid or unresolved bindings. Refer to the EBO Webhelp Binding Status Icons topic for more information Right-click the invalid or unresolved binding, edit the binding or view properties, and correct as appropriate.

Issue What mode must a LoyTec L-IP be configured to work with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Loytec L-IP Building Operation Enterprise Server Cause The operating mode limits the capabilities of the LoyTec L-IP when used with an Enterprise Server Resolution Smart Switch Mode Ensure that the LoyTec L-IP is in Smart Switch mode. This is achieved by using the DIP switch settings for switches 1 and 2 in the ON position.     Reset Forwarding Tables Press the status button for at least 20 seconds. This will clear the forwarding group, the subnet/node forwarding, and the router domain table when used in smart switch mode. Important: If the L-IP is operated in smart switch mode and is moved from one location to another or if major changes to the configuration of the network are made, it is recommended to reset the L-IP forwarding tables Important: Wait at least 30 seconds after power-up of the L-IP before pressing the Status Button to ensure that the L-IP has booted properly!     For additional detail please reference the LoyTec L-IP user manual.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Difficulty getting b3 controller online in order to replace a failed one Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Continuum b3 Controller Cause A b3 controller has failed and needs to replace with the same model. Resolution Remove the failed b3 controller. In EcoStruxure Building Operation Workstation change the serial number of the failed b3 to that of the replacement b3. Install the replacement b3 and ensure the MSTP bus is connected so it autobauds to the correct rate. Then power it up. Remove the battery tab from the replacement b3 (if applicable). In Workstation right-click on the replacement b3 and select Device -> Commission. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Download all objects. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Device -> Backup to flash.

Issue Requirement to set the BACnet max master setting on a SE8000 series room controller Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server SE8000 BACnet MS/TP Cause The BACnet max master setting is not available to be set locally on the SE8000 room controller Resolution The max master setting of the SE8000 can be changed in EcoStruxure Building Operation Workstation.  Add the SE8000 to the EcoStruxure Server Open the SE8000 device properties On the Advanced tab, change the Maximum master property (which is a read/write property) to the required value. 

Issue What is the password recovery procedure for the SpaceLogic Operator Display if the password is lost? Product Line EcoStruxure Building Operation Environment SpaceLogic Operator Display Cause If losing the password for the SpaceLogic Operator Display there is no password recovery procedure available to recover it. The only option to access the device again is to do a device recovery procedure on the device. When doing a device recovery on the device everything on it, all users, configuration data, and logs will be deleted and a new firmware loaded into the device Resolution Steps to perform a device recovery procedure:   Download the device recovery file (tar.gz file) which is included in the “SpaceLogic Operator Display HMIST6400SL Firmware Package” which you can download from Schneider Electric Exchange Extract files and copy them to a USB stick (Format: FAT) a. Unpack the tar.gz  b. Two unpacks are required, then "aurora" folder should be present c. Copy whole "aurora" folder to a USB stick d. The structure on disk should be: e. aurora (folder)-FIRMWARE (folder)- AURORA.CFG-nand.img Power off OPD (Operator Display) Connect a USB-OTG cable (On-The-Go cable, USB-micro-B to USB-A) to the USB-2 port on the rear of OPD . Note: The cable is like a key, to enable device recovery. Do NOT connect USB stick to cable. Connect the USB stick to the USB-1 port on the rear of the OPD Power on OPD Device will boot to a white screen and display: Recovery Mode Loading nand.img... Writing KERNEL... Writing ROOTFS... Udisk upgrade success! (Loud beep) "Upgrade successfully, Wait to Reboot!" Power off OPD. Remove USB stick and USB-OTG cable Power on device and it will boot to the loaded firmware Firmware version is shown on startup screen.   For more details see video:  

Issue How does Modbus scattered read work? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation (1.5 and above) EcoStruxure Building Operation Modbus Cause Requirement to optimise communication over Modbus to improve performance. Resolution The following is an extract from Web Help. The complete section can be viewed at  Modbus Batch Read Function:   'Scattered read is an enhancement to the batch read function that enables multiple, non-contiguous slave device registers to be read in a single Modbus query. By using the scattered read function, you can enable the Enterprise Server or Automation Server to avoid reading a large block of contiguous registers when it is only necessary to read a few registers. Also, using scattered read avoids the multiple use of group function codes 03 (analog output holding registers) and 04 (analog input registers) in order to read non-contiguous registers. Group function codes 01 (discrete output logic coils) and 02 (discrete input contacts) are not supported for scattered read.   Scattered read is available only for supported devices, for example, Schneider Electric branch circuit power meters with split core CTs. Furthermore, the scattered read function applies only when the Enterprise Server or Automation Server is operating as the master, not as as a slave. You can enable the scattered read function in the properties of all Modbus devices. However, if a device does not support scattered read, the device is polled by the master device in the same way as if you had not enabled scattered read.'   The image below shows the properties dialogue window for a Modbus device and the corresponding setting.  The left is version 3.1 and above, the right is version 3.0 and below where it is referred to as 'Non-contiguous read'.  Refer to the Modbus TCP Device  section on Web Help for more information.     

Issue How are the 'Advanced Polling Configuration' settings under the BACnet interface to be used? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause These settings can be used to reduce traffic on the BACnet networks that can overload both the EBO server as well as the devices being polled. Resolution The settings are used to specify an amount of time (in milliseconds) that the server should wait after completing a polling cycle on the applicable BACnet network before starting the next cycle. A polling cycle is the set of point being polled on a particular network interface. For example, lets assume that the Minimum polling interval for MSTPA network has been set to 1000 ms, if you are polling 30 points on MSTP port A then the BACnet plug in will do synchronous ReadProperty requests to poll each of the 30 points one at a time. Once the 30 points are polled, (one polling cycle) the BACnet plug-in will delay 1000ms before polling the 30 points again. (next polling cycle) NOTE: The settings apply to polling ONLY and do not affect communications done via change of value (COV) To find a proper value to use, it is recommended that you start with 1000 ms and then adjust the value up or down based on polling performance. If the polled values update fast enough, increase the minimum polling interval to reduce CPU usage. If the polled values become too sluggish, reduce the minimum polling interval until performance returns to satisfactory levels. It may take some trial and error to find the optimum balance.

Issue Internal counter stops counting. Product Line EcoStruxure Building Operation Environment Script Function Block Counter 167777216 Cause When this script is used it stops counting at 16777216. Numeric Output CountOut   Main: CountOut = 16777100 goto Counter Counter: CountOut = CountOut + 1   Resolution This issue was identified in the early days of Continuum and is regarded as a limitation, not a defect. Explanation - Internally the Script handles all numbers as IEEE754 single precision floats, which means that 16777216 is handled as 1.6777216E7. Adding 1 to 16777216 is unrecognizable in that representation. Using an IEEE754 converter at https://www.h-schmidt.net/FloatConverter/IEEE754.html, one can see that 16777216 and 16777217 have the same binary representation. The point at which the counter will stop, will depend upon the value being added each time, so adding 0.9 will count to a different number than adding 1. The counting range can be extended by two or more variables as shown below. Numeric Output CountOut Numeric CountOut1 Numeric CountOut2   Main: CountOut1 = 16777100 goto Counter1   Counter1: CountOut1 = CountOut1 + 1 CountOut = CountOut1 if CountOut1 = 16777216 then goto Counter2   Counter2: CountOut2 = CountOut2 + 1 CountOut = CountOut1 + CountOut2  

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 User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue Unable to see EWS objects/points under an EcoStruxure Web Services interface Product Line EcoStruxure Building Operation Environment EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause An EWS License may be needed to allow your ES/AS to use EcoStruxure Web Services Resolution Purchase and install an EWS License if required.     Note: The EWS option is NOT required when using EWS to integrate between two Schneider Electric systems or services. Refer to PA-00349 for details.   This includes the new Smart Connector by Schneider Electric which does not require an EWS License but does require a Smart Connector License as usual