Building Automation Knowledge Base

Issue Is it possible to configure Workstation so that certain users see certain alarm categories? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Cause There may be a need to restrict access to certain alarms on a site, if for example a site is comprised of two or more buildings, it may be appropriate for users in Building 1 to only see alarms from Building 1, and not the others. Resolution To achieve this filtering a workspace, alarm view and user group must be configured. Start by creating an Alarm View object in Workstation. Edit the Alarm view and set an appropriate filter i.e. the alarm priority to be displayed. Next create a new Workspace. Ensure that an Alarms Pane is added and that the Initial Path property is set to the Alarm View created in step 1.  Create a new user group and add the Workspace created in step 3 to the group's Selected Workspaces. On the Software Permissions tab for the group, give the group Read permission for the Alarm View created in step 1. Add other appropriate permissions as required. Lastly, create a user a make them a member of the User Group created in step 5. Log in to workstation with the new user. You should then only be able to see the filtered alarms and the user should not be able to change the filter. Also check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.

Issue How do you determine how large a database will grow when using Vista? Which version of Microsoft SQL Server is needed? Product Line TAC Vista Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of trend logs and events should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called SQL Server Express. The size limitations are 4 and 10 gigabytes for Microsoft SQL Server 2005 Express and Microsoft SQL Server 2008 Express respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption, data loss, or inaccessible data. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Vista database, to determine which version of SQL should be used. The Vista database estimating spreadsheet takes into consideration 2 main areas: Trend Logs- total amount of logs, intervals and the number of days to retain Events- total amount of access events. The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate which version of SQL Server is needed This spreadsheet can be downloaded by clicking on the following link: Click Here Update: In Vista 5.1.7, there is a Trend Log Calculation Tool included (under Schneider Electric-Tools)

Issue Running an ActivityEvent ListView with filter longer than one week (example - One MonthToNow).  Listview returns 13621 events. When trying to page down the list,  CyberStation locks up. There are 3 popup windows that occur in this order: Error: Continuum has detected an internal error. If you continue experiencing problem, it is recommended that you shutdown and restart Continuum. Reason Code: 4 ListView: It is illegal to call out while inside message filter. CONTIN~1: The RPC Server is unavailable. At this point CyberStation must be shut down via ContinuumProcesses.exe and then restarted. Environment CyberStation v. 1.81 Windows XP   Cause RPC error occurs and CyberStation locks up when running a large listview. Resolution Increase Windows virtual memory for the workstation from the default value (set by Windows) to a custom size. The "Initial Size (MB)" should be set to a minimum of 1000MB (per the CyberStation Installation Guide). For fastest performance do not set the Maximum Size (MB) to more than the amount of RAM. This will avoid using the hard disk for the virtual memory and RAM is faster than disk drives. If necessary to run the task, increase this setting beyond the amount of RAM. To change the virtual memory settings open Control Panel. Then System>>Advanced tab>>Performance Settings>>Advanced tab>> Virtual Memory Change.

Issue When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Product Line TAC INET, TAC Vista Environment I/NET XBuilder I/NET Host Tool Cause When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Resolution This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913. Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged. Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO) Create an internal AO point to function as a translator (logic AO) Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80 Perform a Station save In XBuilder, create a project for the 527 Web Server Insert or re-insert the I/NET network Add a connection object Drag the Flags attribute of the Doors DO point to the "from" part of the connection object Drag the Value attribute of the logic AO point to the "to part of the connection object Generate the Project and Send to Target. The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO.  The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test.  The Buzzer will not activate if the point is in Manual or Test The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc).  Turn off the other possible alarms, or create an addition internal point labeled Door Forced.  The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2))  C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal

Issue After a power failure, the Automation Server has a designed procedure to restore script programs in to a particular state. This process should be taken in to consideration when designing the system.  Product Line EcoStruxure Building Operation Environment Automation Server Cause Automation Server loses power and restarts, unsure where script programs will start from once the Automation Server comes back online. Due to the onboard "super cap" saving the database to flash on power loss, are the last script program line and variable values retained for when the Automation Server starts back up? Resolution The Automation Server saves it's current active database to flash before losing power completely, the super cap has enough power for it to do this one last task before the Automation Server loses power completely. See AS Power supply interruption or failure on how this is accomplished. On startup from power fail, any script Programs in the Automation Server will start scanning at the first program line. Make sure to keep this in mind and write your programs so that the first line sets your control values to the default "safe" value before moving on to further control logic.

Issue Where can I get information and documents on the Building Analytics service? Environment Building Analytics Cause Information and documentation is required on this product. Resolution Available documentation is available on the Download Center A diagram of network architectures can be seen Here.

Issue I/NET Seven custom installation/upgrade tips Product Line TAC INET Environment I/NET Site Cause Desire to install/upgrade I/NET Seven Resolution Please see following document: Installation Precautions.doc

Issue A job site has several ENCs installed each doing a LON integration and a Schneider-Electric legacy integration (like ASD, GCM, DMS, or MS). Any ENC is currently licensed with the following filter: accept.wb.in="TAC". This only allows copies of Workbench branded as "TAC" to connect with it and perform tasks like data extraction and logic programming. Can an ENC's brand filter of "TAC" be changed to "*" to allow any company's copy of Workbench to access it? Product Line TAC IA Series Environment Niagara G3 ENC-410, ENC-520 Cause Sites may contain equipment from two Tridium integrators and the end customer wants one copy of Workbench to work with all equipment. A performance contracting company may also be Tridium integrators and want access to the ENCs with their own copy of Workbench. Resolution Typically, if the ENC does not have a Schneider-Electric legacy integration, an open branding of the license is allowable. However, for all requests to open brand a Niagara G3 license, contact Schneider-Electric's Regional Sales Manager (customer care can provide the contact name for your office) If this is a new order, an open branding of the license can be requested directly on the license order form. See Niagara G3 (NiagaraAx) Open NiCS (Niagara Compatibility Statement) for details.

Issue During the installation of the WorkPlace Tech Tool release 5.8 software, the following error is displayed: Environment Windows 7, Visio 2007sp2 WorkPlace Tech Tool release 5.8 installation Cause The message will be displayed if no Microsoft Office 2010 components have been installed on the computer. Resolution If Microsoft Office 2010 or any of its individual products including Word-2010, Excel-2010, Visio-2010, etc.,  have not been installed on the computer, the message can be ignored.  The Microsoft Office 2010 component upgrade failed because the no upgradable components were not found by the installer.  Click the [Yes] button to continue the installation.

Issue Valid card swipes sometimes successfully unlock the door and other times result in invalid attempts with the message "Bit count not supported by system" Environment CyberStation ACX7xx CX9900 CX9702 CX9680 ACX5740 ACX5720 Cause Random bit count not supported by system events typically indicate that the signal from the card swipe at the reader got corrupted on its way to the panel, this happens on very long runs (reader is too far from panel) or due to wiring issues and/or electrical noise interfering with the signal. Resolution Make sure the max distance from reader to panel has not been exceeded. (A Wiegand signal repeater may be used) Make sure the reader wire conforms to the specs in the controller's installation guide. Eliminate any source of electrical noise that may be interfering with the card swipe signal on its way to the panel.

Issue A control room requires that someone is physically in the room at all rimes. Require a sample programming solution for triggering an alarm output if the Area is empty for a specified amount of time.  Product Line EcoStruxure Security Expert Environment Security Expert Cause Sample programming solution. Resolution There are a number of ways to do this depending on the exact requirements. The easiest solution is to have an input trigger an alarm that then triggers an output. In my example I will create: Area - System Input - Motion Sensor Input Type - No Motion Detected Alarm Output - VO No Motion Alarm Bell 1. Create new Input Type, in my example mine is called "No Motion Detected Alarm". 2. On the OPTIONS (1) tab enable Generate Alarms, Generate 24HR Alarms and Report Alarms. 3. On the OPTIONS (3) tab enable Activate Input Control Output On Alarm and Deactivate Input Control Output On Restore. 4. On the Input set the Control Output field to your output you want to trigger. Set the Alarm Input Speed to 10m or 30m. (This is the caveat here, we do not have 15m selection with this option. If 15m is the required time then we will need to use another solution utilizing automation.) Set the Restore Input Speed to 0s or your preferred selection. 5. On the AREAS AND INPUT TYPES tab set the Area, in my case this will be System. Set the Input Type to the new one you created earlier, in my case this is No Motion Detected Alarm. You may need to change the Contact Type (on the OPTIONS tab) depending on what action the PIR is doing. Note1: You could also use the Bell output field in the Area (on the OUTPUT tab) as that will be triggered when the Area goes into alarm and reset when it restores to normal.  

Issue ODBC used with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause ODBC (Open Database Connectivity), a standard C programming language middleware API. is used to access database management systems (DBMS). Resolution ODBC is not supported with the current or previous releases of EcoStruxure Building Operation.

Issue Integrating to Zigbee devices not available in Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager SmartStruxure Lite Building Expert Cause The Zigbee device is not available in Building Expert Resolution Zigbee devices are fairly complex to integrate when compared with EnOcean devices and requires development work from the engineers in R&D. Therefore, depending on the business case in your region, it has to be discussed with offer management on whether it could be part of the roadmap or not. You are reach out to the regional product managers to discuss about the opportunity. APAC - EMEA Dusan Janjic (dusan.janjic@schneider-electric.com) Ilda Metani (ilda.metani@schneider-electric.com)  North America Michael Sabinash (michael.sabinash@schneider-electric.com) South America Marcelo Varde (marcelo.varde@schneider-electric.com)   To be able to build a driver for a 3rd party Zigbee device, the following information are required. IEEE Address Endpoint(s) Cluster(s) Attributes Instead of waiting for R&D to build a driver though, you can always write your own script using the information above. However, no active support will be provided by our support teams.

Issue Is MNL-V2RV3-APP the actual controller hardware or is it an application for the actual physical controller? Environment I/A MicroNet LonMark series controllers. MNL-5RF3-APP, MNL-5RH3-APP, MNL-5RR3-APP, MNL-5RS3-APP, MNL-5RS4-APP MNL-10RF3-APP, MNL-10RH3-APP, MNL-10RR3-APP, MNL-10RS3-APP, MNL-10RS4-APP MNL-11-RF3-APP MNL-13-RF3-APP MNL-20RF3-APP, MNL-20RH3-APP, MNL-20RR3-APP, MNL-20RS3-APP, MNL-20RS4-APP MNL-V1RV3-APP, MNL-V2RV3-APP, MNL-V3RV3-APP Cause Part Number description Resolution The MNL-V2RV3 is the actual controller; the extension -APP is an option for factory to install customer's in-house engineered application. Contact Customer Service for details.

Issue Modbus slave device only supports function code 10 hex/16 dec for writing of holding registers. Environment Xenta 913 Xenta 701/711/721/731 Xenta 511/527 Cause In system program 5.1.4 a trigger was added to the Xenta Server software that enables the device to use only the Multi-Register function code. This command is executed from the console port or from the VXI web shell command webpage. VX M 1 = Enable Multi-Register write VX M 0 = Disable Multi-Register write VX M = Display current status of the trigger Note: This setting is persistent on the unit until the firmware has been reloaded. If the unit is upgraded the setting will need to be reapplied. Resolution Log In to the webpage of the Xenta Server Access the Utilities\Target System\VXI Web Shell Commands webpage. Issue a "VX M" command to display the current status. Issue a "VX M 1" to enable the multi register write command option. Some of the Xenta Servers with recent Modbus support do not have the VXI web shell commands web page and the console will need to be used instead. The VXI web shell commands web page should be available in firmware 5.1.6.

Issue Newly added Automation Servers do not communicate correctly with other devices. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.5 StruxureWare Building Operation 1.6 Communications Tab Cause An existing and working site has been extended by adding two new Automation Servers, these servers do not respond to Lead/shadow functions and only show the Enterprise Server in their "Communications Tab" Resolution A system is installed, and the Enterprise Server port numbers are set as required. Automation Servers are then added, and in the communications tab for the Enterprise Server and Automation Servers, all devices are seen.   If the Enterprise Server port number is then changed, things appear to work as normal, but If a new Automation Server is added to the system, it appears to attach correctly, but only the Enterprise Server details are shown in its communication tab. Selecting to "Repair server communications" does not correct this.     To resolve the issue, it is necessary to select the Enterprise Server, and in it's communication tab, change the port number to the number set in the Software Administrator.     Repair server communications, can now be used to update the Automation Server.  

Issue Continuum Add-On Reports will not launch Environment Continuum Continuum Add-On Report Suite Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The reports may not launch because of configuration issues or because the Workstation Instance in the database is corrupt. Resolution Ensure that Continuum Reports is installed in Add/Remove programs Check that the Programs are listed under the workstation after importing the Continuum_Reports.dmp file and that they contain the reports programming code. If they are empty, re-import or cut and paste the code from the dmp file and correct errors. Check that the programs are enabled, if not enable the report and try again. Test the report from the command line instead of launching from a button (Ex. Run Reports_Suite). The second to last line is a Shell command, check that the Reports.exe 0 ( the number represents each report) has a unique number. Reports_Suite=0, Alarms_Report=2. A duplicated number may not run correctly. As a last test, create a new program called TestCalc with the following one line of code: Shell "C:\Windows\System32\Calc.exe" Fall Thru, AutoStart=False Run TestCalc from the command line and the Windows Calculator should show. Usually if you are at this point, it will not start. If that is the case do the following to correct this. Get a database backup Go offline Edit Export everything under the Cyberstation to a text (dmp) file and verify it's contents. Delete the Cyberstation and it's folder  Exit Cyber (You will get an error that it cannot find the object in the database - click OK) Open Database Initialization and select Workstation and re-initialize the WS Create TestCalc as mentioned above and verify that Calculator opens (It should) Go offline edit and import the .dmp file that had been created for this Workstation and verify all is working. Note: If this is on a 64 bit system, the path may need to be changed. reset_password.bat  However, if you did not install Continuum Reports in the default directory, you must edit the Reset_Password.bat file and include the DOS installation path after “password” in the run string.  ie: reports reset password D:\Reports

Issue SNMP Flashing options for Netcontrollers and BCXs Product Line Andover Continuum Environment All Continuum master controllers Cause Documentation Resolution BCXs & Netcontrollers can be in 3 states: SNMP Standard is how all controllers are shipped by default. This means that the controller model and some other object info can be obtained via SNMP. SNMP Alarming Enabled means Standard SNMP as well as SNMP Alarming is enabled in order to send alarms to a network management system. This is a paid for option either initially when the controller is ordered or by contacting repair. To enable this option in the field, repair sends a file and instructions after payment. SNMP Disabled means that no SNMP information will come from the controller. Upgrading controllers with future firmware versions Depending on which SNMP option state the controller is in will determine the application flash that should be used going forward. Selecting the incorrect file can disable or re-enable SNMP options. Netcontroller v1.5300x SNMP Not Set means no SNMP options will be changed when upgrading firmware v1.5300x Standard SNMP means use with Standard SNMP (default) v1.5300x SNMP Alarming Enabled means use when SNMP Alarming is enabled (Not Set could be used also since it will not change the enabled option) v1.53 SNMP Disable means this will disable All SNMP traffic, Standard and Alarming BCX Use the default firmware upgrade after SNMP is enabled. If you use the BCX SNMP Disable flash files and then upgrade to a newer version of firmware, you will have to run the disable flash file again to disable SNMP. NOTE: The flash files used to disable SNMP are posted on The Exchange. Note2: If the flash file doesn't enable the options because it was sitting at resetting controller,  Reload the controller which will force a reset and then try the flash file again.

Issue All values in the Xenta 102-AX Plug-in are blank. Product Line TAC Vista Environment Xenta 102-AX Plug-In LonMaker Cause If the Resource File Languages have become corrupted on your PC, then the plug-in will not know how to display the required data. Go to LonMaker > Network Properties > Resource File Languages.   If the only Language listed is "ENU," then the language files are corrupted. ENU is the default language and will display all data in the LNS environment -- plug-ins, browser, get values -- in an enumerated format that is not usable. Everything will continue to work, but monitoring data in the LNS environment and configuring ASCs via plug-ins will be impossible. Resolution Restore the Resource File Languages: Shut down LonMaker Go to http://www.lonmark.org/technical_resources/resource_files/ Download LonMarkResourceFiles1300.exe Run the executable Restart LonMaker Check Network Properties again. US English should be listed and the plug-in should populate with data. Note: There may be Beta versions 13.04 and 13.10 on this website. Do not use these LonMark resource files. The newer versions cause errors in the 102-AX plug-in. For more information see Opening the Xenta 102-AX plug-in results in "request for LonMark Object status" error .