Building Automation Knowledge Base

Issue When you select a trend chart from a Automation Server or a Enterprise Server the Internet Explorer Hangs and finally crashes. Product Line EcoStruxure Building Operation Environment WebStation 1.1 and 1.2 Internet Explorer 8 Cause The wrong version of Java is installed. StruxureWare 1.1 and 1.2 requires Java version 1.6 update 26 to function correctly. This error is the result of Java version 7 installed on the WebStation computer.  Resolution Note:  Java is no longer required from SBO/EBO version 1.7 and above.  Uninstall Java 7 and install the correct version of Java (Java version 1.6 update 26) stated on the WebStation data sheet. Refer to the Online Help Topic WebStation Specification Sheet and select the version of WebStation in use to determine the version of Java required.   

Issue Power Monitoring Expert (PME) is able to make its data objects and alarms visible to EBO via EcoStruxure Web Services (EWS). But when viewed, the Alarms from these EWS objects only shows a number rather than its actual object name in PME. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server EWS Integration Cause There are two stages to bringing data via EWS into EBO.  The first is to create the EWS interface in EBO so that the EWS source (in this case PME) can be discovered.  However, if those discovered EWS objects are not then hosted in EBO, the Alarm Source details will be not complete. Resolution 1. First Identify an object in PME which is also in Alarm and will also be Alarming in EBO when hosted. The date and time of the actual Last Occurrence can be useful here. 2. Notice that the Source name and Source of the same Alarm in EBO is only a number. In this case 3 or EWS Client/3. 3. Now select Host EWS objects from the EBO Menu and host that point or controller onto the EWS interface 4. Note now that all Alarm references previously showing just a number now immediately update with the correct Source name and Source now that the point has been hosted in the EBO Database.  In this case PDU_2B_1_6A_ION9200 Note:At this point it would be very easy to simply decide to Host the entire PME Server onto the EBO Interface rather than a single object or controller as this would then update the sources of all alarmed objects.  However care must be taken that at this point not to overload the system.  Every hosted object will then be polled for value and alarm status periodically adding greatly to the comms between the PME and EBO systems and while the polling rate for Value and Alarm can be adjusted to sensible values there is an argument to only host those EWS objects that data is required from.

Issue Script editor shows blank canvas or shuts down immediately after launching. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Cause User settings file contains information the Script Editor application can't process correctly. Resolution First, to confirm that the issue is indeed caused by information in the user settings file, navigate to the location where the file is located (i.e. C:\Users\Your User\AppData\Roaming\Schneider Electric EcoStruxure\Script Editor\3.1.2.29) and make a backup of the User.settings file then delete it. If the Script Editor launches fine after deletion of the file, and you need to narrow down which setting was causing the problem, you can put back the original file then open the file in a text editor such as Notepad++ and comment out suspected lines until you identify the exact setting causing the issue. You comment a line or block of lines by inserting <!-- at the beginning of a line and ending the line(s) with -->  (see below)

Issue What are the measures in the AS to protect the system in cases of network broadcast storm or Denial of Service attacks? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Cause Offline alarms received after excessive network traffic observed. Resolution The firmware in the AS will temporarily shut down its Ethernet connection when exposed to a broadcast storm or DoS attack in order to protect the application in terms of control programs and IO. A side effect of this is that the communication to external IP devices is temporarily unavailable during the storm/attack. The Automation Server will log the network storm event in its log journal file. (see screenshot below)

Issue EcoStruxure Building Operation - Sigma logging does not work. Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Sigma logging has been transitioned to EcoStruxure Building Operation, but does not work. Resolution  The Procedure is as follows; Import the log data sets from Sigma to EcoStruxure Building Operation. Highlight "Log Sets" in the system tree under the Sigma Interface and select to "Send log sets" To confirm that the controller has started logging, select the appropriate controller, and choose "Diagnostics" and "Log Set Statistics" where you can see the statistics which include the log set/object details. To upload the logging, highlight the required log set and select "Retrieve Logged values". To review the uploaded data, highlight the required log value and view it as required Once that the logging in the Sigma controllers is working correctly to EcoStruxure Building Operation, logging from the Sigma server should be disabled.

Issue Missing LNS plugins for  EcoStruxure Buildings Operation Workstation Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Cause Plugins for EcoStruxure Buildings Operation are not included in these releases. Resolution Download the TAC Vista 5.1.9 tool pack and this will install the 100 series controller plugin and Z-Builder programming tool. Once this is installed EBO will be able to access these plugin when used with Open LNS. Download the TAC Vista 5.1.9 Toolpack - Software from Exchange Extranet. Direct Download also provided. 

Issue What are the basics steps when setting up the Engage Mobile application to use it for the first time? Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) Cause The Engage mobile application enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. Resolution Below are the basic steps when setting up the Engage Mobile application to use it for the first time:  First create and configure the Occupant App Menu object. Make sure Bluetooth is enabled for the RP-C. Download the Engage mobile application and connect to the RP-C Available on App Store and Google Play To see details for every step please see video:  

Issue The Local Variables Pane in the Script Editor is not displaying local variables or arrays. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Local Variables Pane can only be used in debug mode, i.e. when pressing Start and then either Step or trace (Trace On) through the script. When the Script Editor is not in debug mode the Local Variables Pane is empty. Note that the debugger is not available at all when editing scripts in the RP-C or MP-X, or when using Script Event Programs.  Resolution Click Start in the Debug tool list at the top of the Script Editor (or press F5) to start debugging. The local variables will now be visible in the Local Variables pane. If you have arrays you can expand them by clicking the plus sign. Next use the Step button (or press F10) to step through the program. The values of the local variables will change as the script is executed line by line. ClickTrace On to automatically step through the program. ClickTrace Off to stop the automatic stepping. For troubleshooting purposes, values can also be updated directly by editing the entry in the Value column in the Local Variables pane. 

Issue When there are multiple displays, and the script editor is in the right window, the autocomplete popup window goes off-screen. *note* this only happens in full screen Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The issue depends on which way you assign the two monitors in the Windows settings or how you have the monitor cables hooked in the docking station/laptop. Resolution Swap the physical monitor plugs on the PC or docking station, allowing Windows to recognize your monitors synchronously from left to right Go into your Windows monitor settings and drag each screen to its proper position and hit apply.

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue BACnet devices not found but are visible in other third party BACnet applications An update may cause devices to go offline Product Line EcoStruxure Building Operation Environment BACnet IP Network Building Operation EnterpriseServer Building Operation Automation Server (AS, AS-P, AS-B) Cause According to BACnet routing rules, each BACnet Device should have a unique BACnet Instance ID and each BACnet Network should have a unique BACnet Network ID  When a BACnet interface is created on an EBO Server, a BACnet IP network is created with default Network ID of 1. This is a local Network address and in not published on the network, it is therefore not a problem if this is duplicated with other EBO Servers. On many site this will remain at 1 for multiple EBO servers with no problems. If a third party BACnet device uses a published Network ID that is identical to the EBO local Network ID, then it will be ignored. There will be a "Duplicate of local network"  System Alarm and line similar to below in the trace log "nsp.pin.BACnet Device <device name>claims to be router to Network #1234 but that is a local network (BACnetMain)" Resolution If the EBO Server is not finding a BACnet device on a different network type (via BACnet routing like MSTP or virtual IP) then it could be the Network ID is identical to the local EBO Server Network ID. If this is the case, then simply change the EBO local Network ID and retest. BACnet Devices on the same IP network, including those on different IP subnets and linked via BBMD or Foreign Devices are not BACnet routed and therefore will not have this issue (no BACnet Network ID route is involved) Some earlier versions of EBO did not ignore these duplicate Network IDs, thus when up grading some devices could go offline. The workaround would be the same. The correction to the BACnet operation occurred in v1.9.3 and v2.0.2

Issue Living Space Sensore goes offline after upgrading SmartX Controller firmware from 2.0x to 3.01 or later Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) v3.01 or later Building Operation SmartX Living Space Sensor Cause Living Space Sensor RJ-45 connector is plugged into Room Bus port on RPC. Resolution Move RJ-45 connector from Room Bus port to Sensor Bus port.

Issue The value of DateTime will different depending on how the variable is declared Differences between DateTime declared as a local variable and as input, output or public in Script program Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Script Editor Cause Local and bound variables will initialize differently Resolution Local DateTime variables are local and known only to the Script program or function, and are initialized to the current local date-time value of the sever in which they  execute. Binding variables, including Input, Output and Public variables, are not effected by the Script engine by default. The EBO system uses the 1/1/1970 date as default and the Script simply uses that. If a different initial value is required then one can be set in the script

Issue How to calculate total memory required for controller to store logging information for the required duration. Product Line EcoStruxure Building Operation, Andover Continuum Environment NetController (CX9900, CX9940, CX9680, bCX9640) InfinetController (i2xxx) BACnet Controller (bCX4040, bCX9640, b3xxx) Cause Need to know how much memory is needed per point to determine the maximum number of entries and minimum interval time that the controller can use. Resolution The general equation of calculating memory use for controller logging is as below; * Memory usage per point = { 8bytes + (4bytes * NumberOfLog) } In addition to that, each controller requires minimum 1~2KB of freemem after the controller logging memory allocated.  Regarding the log interval, if the point is being logged for controller only, you can set the interval in seconds unit.   But if you configure the point for ExtendedLog as well, the logging interval should be in minute unit. Again, if there many objects with one minute interval for Extended Logging, it will affect the performance of the Cyberstation and also increases the size of ContinuumDB dramatically in short period of time. In this case, consider increasing the log interval to 5 ~ 15 minutes for Extended Logging.

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 Pins 4 through 7 across the top of the Automation Server are labeled as "Operator Panel" although there is not an Operator Panel part available. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Cause There is no explanation of what the AS Operator Panel contacts are for? On front of AS:  Operator Panel Terminals Term 4 RET Internally connected to ground Term 5 10V 10 VDC max. 120 mA Term 6 Tx/Rx+ RS-485 communication Term 7 Tx/Rx- RS-485 communication Resolution At one time there were plans to create an Operator Panel so terminals were reserved on the Automation Server for local OP connection, however, these plans were not implemented. The next generation Automation Server Premium (AS-P) does not have the Operator Panel label, and today most operators use Webstation or Workstation.

Issue Unable to drag and drop the Application folder into the include types box while performing a search of application files.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation v3.0.x  Building Operation Workstation v3.1.x  Cause Searchable interface not implemented on the Application folder (nor on other devices like b3). This is a known issue in v3.0.x and v3.1.x Resolution Rather than using the left mouse button to drag the application folder, right-click the application folder to drag and drop into the include types box. This is to be fixed in 3.2.1.x.

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 Sometimes as an administrator, you may need to kill a service which is stuck at starting or stopping in order to avoid having to reboot a server in the middle of the day. Or even after the reboot, the service will not start. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Licensing Server Security Expert Windows Services Access Expert Windows Services (on-premise only) Cause Sometimes the service times out and gets stuck in a loop due to fallback protocols within the service Resolution Find out the name of the service To do this, go into services and double click on the service which has stuck.   Make a note of the “Service Name”. Find out the PID of the service Open an elevated command prompt and type in: "sc queryex servicename" (where servicename is the name of the service you obtained from Step 1). Make note of the PID Kill the PID From the same command prompt type in: "taskkill /f /pid [PID]" (Where [PID] is the service number).   If it is successful you should receive the following message: "SUCCESS: The process with PID XXXX has been terminated."     Be careful of what you are killing though. If you kill a critical windows service you may end up forcing the machine to reboot on it own.   If the service returns back into this state you may need to increase the time allotment for the service to start.   Global (entire system): Open Windows Registry: Start -> Run -> regedit.exe File --> Export --> make a backup of the current registry Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Right click on the right page ---> New ---> DWORD call the new DWORD "AutoStartDelay" Set AutoStartDelay in milliseconds (decimal). E.G. 240000 is 240 seconds. Per-service: Open Windows Registry: Start -> Run -> regedit.exe File --> Export --> make a backup of the current registry Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<servicename> To increase the default delay of 120 seconds, right click the registry key and add new key AutoStartDelay (DWORD (32-bit)) Set AutoStartDelay in milliseconds (decimal). E.G. 240000 is 240 seconds.

Issue Unable to assign output channels on a some b3/i2 series controller under an AS. CCT(Continuum Conversion Tool) unable to assign channel with error "Could not find channel" in the conversion report. When creating an output channel, that is out of range, the workstation error is "Could not find channel" eg. if output channels 15 or 16 (on b3810) are assigned Product Line EcoStruxure Building Operation Environment AS ES b3, i2 Expansion Module xPD04, XPD02, xPA04, xPA02 Cause b3/i2 series expansion channels are software limited in line with the maximum xP module capacity The maximum b3/i2 expansion current available is 180mA, so some combinations of 2 xP modules are not supported, see below   Resolution Both input and output channels are limited in line with the allowable xP expansion units that can be added. For example a maximum of 6 xP output channels can be added to b3/i2920, b3/i2810, b3/i2814, b3/i2850, b3/i2851 & b3/i2853 controllers, (2 xPD/A04 Output modules is above the maximum power supply to xP units from the b3/i2 series controllers)                                   Output Channels               On board                               xP Modules    b3920     1 to 16                                   18 to 22 b3810     1 to 8                                      9 to 14 b3814     1 to 8                                      9 to 14 b3850     1 to 4 (5 reserved)                  6 to 11 b3851     1 to 4 (5 reserved)                  6 to 11 b3853     1 to 4 (5 reserved)                  6 to 11 NOTE Continuum did not limit the channel numbers, thus unsupported configuration could be installed and in some cases these may work. This can cause an issue during an upgrade/conversion.

Issue When a TGML graphic is opened from Webstation and the user right clicks on a value in the graphic to open properties, it can take up to 20 seconds before the properties dialog is displayed. During the 20 seconds the working area is just grey. Product Line EcoStruxure Building Operation Environment Building Operation Webstation 2.0.4 and earlier versions Cause This problem only occurs when the signals in the graphic resides in a TAC Xenta; The problem has not been observed with Modbus or BACnet signals, and is only present in Webstation, not in Workstation. Resolution This issue is fixed in EBO 3.0. There is also a hotfix for version 2.0.4. It is labelled 2.0.4.5801. Contact you local technical support organisation if you need the hotfix.