Building Automation Knowledge Base

Issue How to view user login/logout information in TAC Vista Workstation Environment TAC Vista Workstation Cause User login/logout information is captured in the events log. Event viewer can be filtered for displaying just the login information. Resolution Sign in TAC Vista Workstation as an administrator. Open the Event Viewer.   Use event filter to filter out unnecessary information Open Event Filter window, and select “General” tab. Under “Type”, leave “Commands” to be checked and uncheck everything else. Under “Object type”, Type “Vista Server” After the filtering, the event viewer will only display user login, user logout, server start up information. Additional Information: Viewing only the login/logout information: In the Event Filter window, select “Event Specific” tab Under “Command”, type “LOGIN” or “LOGOUT   Viewing specific user login/logout information In the Event Filter window, select “General” tab Under “User”, type the user name NOTE: if the user is in a user group, need to include the user group name also. For example, user SYSTEM is also in the SYSTEM MANAGER group, need to type “SYSTEM (User Profile SYSTEM)” in "User" textbox.

Issue When downloading a controller in the Vista System Plug-in, messages are received saying the System Plug-in is waiting for the controller to restart, but this never completes successfully. This message may be shown many times. Environment Vista System Plug-in LonMaker Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There may be several different causes including communications errors or a corrupted application. However, by taking the controller offline in LonMaker, any extraneous interaction with the controller is temporarily ignored during the download. Resolution First, please double check the Vista ToolPack version that is installed, and make sure the version matches TAC Vista Server version. If not, please uninstall the Vista ToolPack and install the correct version of ToolPack. TAC Vista ToolPack can be download from Extranet (Software and Firmware > Engineering Tools). In LonMaker force the controller's neuron chip into a configured, bypass mode: Right-click the controller and select "Manage" In the LonMaker Device Manager window click "Offline" Download the controller in the Vista System Plug-in. In LonMaker set the controller's neuron chip back to configured, online mode: Click "Online" in the LonMaker Device Manager window then close window

Issue Serial Communication with Xenta Units (511, 527, 911, 913): Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause Incorrect cables can cause improper ground references between the PC and the Xenta unit, which will disable serial communication. Resolution The Xenta units that utilize a web interface all have a certain amount of setup that is done with a direct serial connection via HyperTerminal. This communication however can be problematic at times due to grounding between the Xenta unit and the computer. If both devices do not share a common earth ground reference, then communication will not occur at all. There will be no indication that either side is receiving the transmissions from other device. This is most commonly encountered when using the incorrect cable since the proper cable provides a conductor for ground and thus a common ground reference. An OP panel cable is not the proper cable to use in such a situation. Instead you should be using the cables found in the TAC Xenta programming Serial Kit. If you are using a cable made by someone other then TAC the most likely cause is your cable having the improper or insufficient connections. When stuck in a situation where the proper cable is not available and working with a laptop computer we recommend that you plug the computer’s power supply in preferably to the same power supply as the controller to try to establish the common earth ground. Any other attempts to stabilize the differing grounds will be at your own risk.

Issue What kind of preparation must be done prior to upgrading a Continuum LAN system? Environment Continuum Cyberstation SQL Server Cause Continuum Upgrade Resolution Study the Continuum Compatibility Matrix and the Continuum Video Compatibility Matrix.   Plan the upgrade of supporting software applications and hardware using the Continuum compatibility matrix as your guide.  .Net versions and SQL versions must be compatible with the final version of Continuum before you begin the upgrade process.  Older CX controllers (with firmware <= 1.500029) use a different algorithm for defining handles so they should be up-rev’d prior to the upgrade process.   For all other controller the controller firmware can be upgraded after the front end systems upgrade has been completed.    The upgrade process presents an opportunity to make an assessment of all computer hardware that is currently being used in order to make recommendations for upgrading hardware.  This is especially important with respect to the Continuum Database server.   Selecting the right server is a process that involves determining the customer’s needs and defining the systems requirements.  This is an engineering decision that is beyond the scope of Product Support Services.  The customers IT department will likely be involved in this process also.  When are adding a new database server, it may be advantageous to build your Continuum server and prepare the Continuum database off-site. Completing a Continuum LAN system upgrade is a complex process and not something that you can accomplish simply by following a step list. It is crucial that an engineer who is experienced with the Continuum LAN upgrade process on site to direct the upgrade.  This is both to ensure that the upgrade process is handled correctly and to mentor technicians who will be involved in future upgrades on LAN systems.

Issue Need to edit StruxureWare Building Operation Reports Product Line EcoStruxure Building Operation Environment SmartStruxure Report Server Report Builder 3.0 Cause Users wish to directly edit or create customized versions of existing reports. Resolution Open Microsoft Report Builder In the Menu, Select Options Change the database path to "http://localhost/reportserver_SQLEXPRESS' Where localhost is changed to the PC name or IP address and SQLEXPRESS is changed to the installed instance of SQL Click OK You can now open existing files on the server and save new files directly to the Reports Server. You must Synchronize the StruxureWare Reports Interface for newly published reports to be available from the StruxureWare Interface.

Issue When launching a Access Expert on a Premise install, an error "Unable to retrieve license. Please notify your Keep service provider" when trying to log on to the instance. Product Line Access Expert Environment Access Expert Wondows 7, SQL 2012 SQl 2014 Cause Keep does not have access to the database for license information. Resolution Install SQL Studio and give NT AUTHORITY\SYSTEM sysadmin rights. The following captures shows where to go to enable this in SQL. Connect to SQL, go to the Security Folder and expand it, select the Logins Folder and expand that then select the NT Authority When the tab opens select the Server Roles, then check the box for sysadmin.

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 Sample programs for carpark access control. Environment Continuum Access Control Carpark Access Carspace Counting Cause Want sample code on how to provide Carpark Access Control. Resolution It is possible to do car park control with Continuum Controllers. There are a number of different ways to do this depending on the sites specific requirements. PSS doesn't provide programming for specific projects but we can provide generic examples. *** Note: This sample code is provided as-is to be used as a sample only.   *** To start off, a very simple solution could be:   To have three Areas defined, Outside, CommonCarPark, and EmployeeCarpark. You then create Door objects for the Entry Readers at the entrance to CommonCarPark and EmployeeCarpark. Use a PE Program to Monitor the CommonEntry Entry Reader for ValidAccess and set a pre-alarm flag (Numeric). Have an AlarmEnrollment attached to the pre-alarm flag and set for a specific amount of time (3 minutes). Have another PE Program that monitors the EmployeeEntry Entry Reader for ValidAccess and then re-sets the pre-alarm flag stopping the alarm from being sent. You could use this sample program, with some modifications, to provide you with this functionality. This is a very simple way of doing it that doesn't take into account having more than one car coming in at the same time though...you could expand on this to include using arrays to store the details of the Personnel that have badged and then have a timer associated with that specific Personnel, set both values into an Array and then have another program monitor that Array and compare the time they entered against the current time...if the difference was more than your alarm time then raise an alarm. When that Personnel badges at the EmployeeEntry Reader you remove their entry from the Array. A sample on how to do this is here. This one is a bit more complex than the previous example but it should give some ideas to start with to mold into a solution. There is a WS program as well as a controller program. The controller program does all of the carpark control which uses arrays to store the number of car spaces currently available for each department group (company/tenant) and allows of disallows new cars from that dept depending on available slots. This solution required both a roller door and a gate inside the roller door to create a "mantrap" for the desired control but the same principle could be applied in a simpler design. The WS program was used to provide a solution to the tenants locking themselves out of the carpark when they didn't badge out properly. It uses an object to search though all Personnel to find a specific card number and then resets that Personnel's current Area so they can badge at the anti-passback enabled Door. From memory, this part of it didn't work as well as the carpark access. The code is good just the method of searching through all Personnel was prone to locking up. Depending on the number of Personnel and size of Database it can take a longtime to do the search ... and the program can time out and go to disabled. So there was human intervention needed at various times.  

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 A third party BACnet system is able to host  values from a SmartStruxure Lite MPM but an MPM does not seem able to host values from another BACnet system or device. Environment BACnet MPM-VA MPM-UN MPM-GW Cause SmartStruxure Lite Managers have full BACnet server capabilities, however BACnet client functionality is not native to the MPM and is currently only available through Lua programming. Resolution Integrating SmartStruxure Lite™ Managers with third-party BACnet server devices requires a BACnet client script. A sample script (download here) can be used to perform read and write operations to other devices via BACnet IP, however, a few tips and limitations must be taken into consideration before deployment on site. NOTE1: The delay at the beginning of the script (if scl.sysclock() > 90 then) must not be removed or modified. Otherwise, the MPM will keep rebooting endlessly and would require restoring its factory defaults before gaining access to Building Expert again. NOTE2 : The more points used in the script, The higher the MPMs CPU% Usage will be and the less responsive the MPM will be. Therefore, it is recommended to only read/write the necessary points and not all the points on the third party devices. Also, if some points are more important that others, the polling time can be increased to 60 seconds for example.   NOTE3: The more objects you have on the MPM, the less room you have for BACnet points. PGs, Trends and Events consume a substantial amount of CPU Usage so it is important to keep an eye on it as you add more points in the script.   NOTE4 : Run the script every 5 seconds or more if possible   Limitations: - Reading/Writing to Multi State Values (MSV) is not supported

Issue The Enterprise Server enters a restart loop filling the hard drive with crash dump (dmp) files Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause This happens due to corrupt backup sets from AS being present. To make a quick check if this is the issue, rename the following folder replacing x.x with the version you have installed. C:\ProgramData\Schneider Electric StruxureWare\Building Operation x.x\Enterprise Server\db_backup\ASArchives If the ES starts after that, identify the faulty backup sets as described below. Resolution Browse to the AS backup folder (see above in "Cause") Detect backup sets not looking correct e.g. having a size of 0 KB Delete these backup sets   From version 1.7.0 and forward, these backup sets are automatically removed

Issue BACnet Input shows "Out of Service". When attempting to set a value or remove the out of service flag an error is seen. "An attempt has been made to write to a BACnet property with a value that is outside the range of values defined for the property." Environment bCX4040 b3 Controllers Cause An xP Module attached to the Controller was malfunctioning and the inputs on this board were not functioning. Resolution Powering everything down, re-seating the xP Module board and powering the Controller back up resolved the problem.

Issue Can't get the a Sigma laptop to communicate with a Sigma controller via the RS-232 connection (Diagnostic Port SK1). Environment Sigma RS-232 Communications Serial Communications Local Communications Service port Cause Configuration error Resolution Use the following check list to confirm correct configuration. On the main Sigma server Create a service server in the main server and ensure the Att.set files are downloaded to the controllers On the laptop Set the C:\Sigma\Data\Sigma.ini file entry RS232 = 1 Set the C:\Sigma\Data\Sigma.ini file entry Commport=1, Baudrate=9600 (Note: ensure the BAS Integrator is not enabled as it also set for Comm port 1 by default) Set the laptop server number the same as service server number in item 1 above (System Setup -General - Server Details). Restart the laptop Sigma server If you are using Sigma 4.05 build 3.42.34 then you need a Hotfix to enable the Sigma serial communications.  Click here for Hotfix 3.42.46.  Later Sigma releases do not require a hotfix. Confirm the RS232 cable wiring is correct and not broken.

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 When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.

Warning Issue Upgrading Reports Server from 1.4.1 to 1.5 Environment StruxureWare Building Operation 1.5.0 Windows Server 2008 R2 Reports Server WebReports Enterprise Server Cause Failure to follow upgrade guides may result in data loss. The most likely point of failure seems to be running the Reporting Agent Service on the Reports Server while upgrading the Enterprise Server. The Upgrade will error out if SQL2008 R2 is not upgraded to SP2 or .NET framework is not upgraded to 4.5 at the indicated points. Resolution This resolution process was developed from the System Upgrade Reference Guide and tested on a single PC. Windows Server 2008 R2 at StruxureWare Building Operation 1.4.1 running SQL2008 R2 SP1 and .NET 4.0 upgraded to StruxureWare Building Operation 1.5.0 SQL2008 R2 SP2 and .NET 4.5.  You can find and download all 1.5.0 released software and documentation by searching the Building Download Center for the tag "relsbov1.5" Backup Enterpriser Server, All Automation Servers and Report Server. Store backups on external media. If desired, create a Windows snapshot for a quick return point. Download all StruxureWare Building Operation 1.5 Installation files, SQL2008 R2 Upgrade files and .NET 4.5 installer. Close all StruxureWare applications In the Windows Server Manager, Expand Configuration and Select Services Browse to “StruxureWare Reporting Agent”, right click on it and select stop Open Software Administrator and stop the ES service. Close Software Administrator In the Windows Server Manager - Services section, stop the service “Building Operation 1.4 License Server” Run the .NET 4.5 installer. If prompted to restart, select Restart Later. If the PC restarts on its own, verify that all services listed above are stopped before moving forward. (repeat on all PCs) Run the License Administrator 1.5.0 installer Run the Enterprise Server 1.5.0 installer; select the Upgrade current version option. Note the ports used. Port 80 should not be used for http communication when the ES is installed on the Same PC as the Report Server. If desired install the Project Configuration Server.  Be sure that the HTTP port is not the same as what is used for the Enterprise Server and not port 80 Open Software Administrator and verify that both the Enterprise Server and PCS are running and using different ports Install Workstation. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading Install Device Administrator. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading At this time, upgrade any required Automation Servers. If upgrading from 1.4.0, all AS must be upgraded together. Install any required language packs If required, download and install the SQL2008 R2 upgrade to SP2 : http://www.microsoft.com/en-us/download/details.aspx?id=30437The default file name for the upgrade installer is SQLServer2008R2SP2-KB2630458-x64-ENU.exe In Windows Control Panel, go to Programs and Features Uninstall the “Building Operation Reports Installation” application only. This is the installer application for 1.4 Web Reports Run the Reports Server 1.5.0 installer Browse to C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation Reports Installer Right Click on SE.SBO.WebReports.Installer and select “Run as Administrator” For Setup Type, select “Upgrade both software and database” Fill in site specific information as instructed. For Reporting Agent, be sure to specify the exact Enterprise Server Address and port used. Follow the remaining prompts to install WebReports On completion, log into the StruxureWare WebReports interface and run a few test reports.

Issue Issue1: Unable to use some of the function blocks in the Graphical Editor when creating a graphical program. Issue2: Unable to find some of the function blocks in the Graphical Editor Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Description of each function block is not available in Building Expert Resolution Resolution 1: A detailed explanation of each function can be found in the StruxureWare Building Expert Graphical Block Programming User Guide. Resolution 2: Upgrade MPM firmware to 2.16

Issue Points from a SmartStruxure Lite MPM display the question mark character (?) instead of the correct engineering unit when brought into Building Operation via BACnet. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Building Operation WorkSation SmartStruxure Lite MPM with firmware version 2.5.8 or earlier Cause The question mark (?) placeholder for units is used when Building Operation reads a BACnet unit id that we do not have a translation for to Building Operation units. In MPM firmware version 2.5.8 and earlier, units are translated as vendor proprietary, in firmware version 2.7 and later the units are translated to standard BACnet units. Resolution Upgrade the MPM firmware to Version 2.7x or later. MPM firmware can be downloaded from the https://ecoxpert.se.com/building-expert/discover#tab/documents . Please note that firmware is on a secure area of the site that is only accessible to certified SmartStruxure Lite engineers.   I M P O R T A N T   Also, any thermostat where the communication module is replaced must be re-addressed and re-discovered, additionally all related Widgets will have to be re-linked to the new object(s). If you are not sure which module you have on your SE7000P units do the following... a) Remove the cover. b) look at the part number, the new extended profile modules are 051-0132

Issue When an Automation Server backup is restored, the programs or IO's linked to a time schedule does not show their correct states Environment Automation Server Backplane Function Block Time Schedule Cause More than one AS has been fitted onto the same backplane and this e.g. causes the Function Block program to malfunction. The result of this is that the FB program does not reflect the correct state of the time schedule binding, when a backup is restored.               Resolution The installation of multiple AS's onto the same backplane is not allowed.  Do not install more than one AS on a backplane. If you do, they will both try to drive the IO bus and will collide in doing so. This causes the Task Scheduler to lock up in the AS. Results will be unpredictable! To overcome this issue, make sure only one AS is fitted on the same backplane, and "warm-start" the AS.

Issue Lost Entitlement ID when you want to rehost/return/modify existing license. Product Line TAC Vista Environment Vista 5 Cause When a rehost/return/modify of an existing license is required, the Entitlement ID is required. Resolution Contact support and provide the current Host ID (PC MAC address) /Dongle ID used, alternatively the current license file or Fulfillment ID. The directory that the License file is located in can be found using the License Setting tool. Support will then provide the Entitlement ID for license in question.  The Entitlement can also be found providing the original Purchase Order ID to the order entry department at 1-888-444-1311 if in the continental US.

Issue Shortly after a successful backup to flash the exclamation point appears again on the controller's icon in the Continuum explorer indicating that a backup to flash is needed. Environment CyberStation bCX9640 bCX4040 CX9680 ACX5740 ACX5720 Cause PE program changing configuration attributes. A setpoint changes value. Resolution Any changes to a configuration attribute will cause the database in the controller to be marked as needing backup up to flash. Also, if an object is configured as a setpoint, changing its value causes the database to be marked as needing backup to flash. Find and modify any PE programs that change configuration attributes (i.e. description, format)  and/or setpoint values.

Issue Does Continuum support multiple object trend reports? How can I display a report that shows the trend data for multiple objects. Environment Continuum CyberStation BACnet TrendLogs Cause While trend data for a single BACnet point can be reported from the TrendLog object by selecting View Report from the Data page of the TrendLog object editor, it is usually necessary to display comparative trend data from multiple points. Resolution Since BACnet points themselves do not store trend data the way Infinity points do, BACnet requires that another object, the TrendLog object, be used to store this data in the controller.  The trend data for a single object can be viewed by selecting View Report from the Data page of the TrendLog object editor to which the point is attached.  Continuum Report objects can be used to view BACnet trend data. Unlike Infinity points, BACnet points are not added to the Report objects member list  since BACnet points contains no trend data.  Instead the TrendLog object which has been configured for, and to which the BACnet point has been attached, is added to the Continuum Report TrendLog member list. Multiple TrendLog objects can be added to the member list of a Continuum Report. The member list is the Trend Log window found on the Filter page of the Report object editor.   The configuration of the Report object editor should be as follows. Data Source: Current Value Report Type:  SnapShot of Trend Log buffer contents. Chart Type:  Text (data schedule)  or Trend (graph)

Issue When logging on to the Report Manager or Report Builder to manage, create or install custom report packs, the following error is shown: User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed Environment WebReports Cause This is a known issue with Microsoft Reporting Services when User Account Control (UAC) is enabled on the server. By default the local administrators are only given the role of "Content Manager", which does not allow for all operations. The easy solution is to disable UAC, but below is the solution for how to solve it without disabling UAC. For further reference, refer to the following discussion. Resolution 1. Launch Internet Explorer as administrator (right click the shortcut and click "Run as administrator"). 2. Open the Report Manager on the local server using "localhost" in the URL. E.g. if the URL is normally http://server_name/Reports_SQLEXPRESS you need to enter http://localhost/Reports_SQLEXPRESS 3. Click "Folder Settings" 4. Click "Edit" next to the "BUILTIN\Administrators" 5. Check all the options and click "Apply"