Building Automation Knowledge Base

Issue The setpoint values are displayed briefly and then change to 621.X on the Proview display? Environment All LON proview installations. Cause This occurs when the setpoints are being written into network variable inputs (nvi).  The nvi's default to using the receive heartbeat and will fallback to default after the timeout occurs.  Proview does not perform a send heartbeat function as the connection is an nv update and not an actual binding. The receive heartbeat mechanism in the MNL controllers cause the nvi values to fallback to NA upon heartbeat timeout. Resolution The heartbeat can be disabled for the setpoint nvi, however nvi values are stored in RAM (not EEPROM) and will return to default upon a controller power cycle.  The best solution is to use network configuration inputs (nci) for setpoint displays on the Proview.  These do not have the heartbeat issue and the values are maintained in EEPROM so they are not lost following a controller power cycle.

Issue Is it possible to create host bindings to Vista using NL220? Environment Vista 5.1.7 NL220 Cause Yes it is possible but you must use a Loytec network interface Resolution Create binding to the LON interface in NL220 and use the Vista System Plug-in to import the project to Vista

Issue Guidance is needed for creating a PE program for announcing access by VIP to a door Product Line Andover Continuum Environment Continuum Cyberstation Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause Need a way to identify a sub-set of credential holders, (Personnel Objects), with access to the site and take some action when one of those individuals gain access to a door. Resolution The subset of credential holders is defined via the Department Code which is an attribute of the personnel object.   PERSONNEL CONFIGURATION   Any person with a Department Code of 600 will be identified as VIP by the PE Program.   DOOR CONFIGURATION  The door(s) need to be configured with a department point (InfinityNumeric)  *** In this example we are only doing the entry side of the door, the program can be easily modified to handle the exit side of a door as well. Upon valid access, Continuum will automatically place the department code from the personnel object in the value of the InfinityNumeric configured at the door for department point.   INFINITY PROGRAM CONFIGURATION (Program resides at the controller)  ***In this example an alarm is sent when VIP enters a door, program/configuration can be easily modified to take other actions such as sending email, sounding an audible alarm, etc.   Here is the code for the InfinityProgram  'This program monitors the Front Lobby door for access by VIP individuals 'an alarm is dispatched upon door access by VIPs 'Program is LOOPING/AUTOSTART Object theDOOR Numeric theCODE Object theDepPOINT Line INIT theDOOR = MainLobby 'PUT THE FULL PATH TO THE DOOR TO MONITOR HERE theDepPOINT = theDOOR LastDepEntrdPnt theCODE = 600 'PUT THE DEPT CODE THAT DENOTES VIP HERE Goto MONITOR Line MONITOR VIP_Flag = False If theDOOR ValidAccess then If theDepPOINT Value = theCODE then Goto SendALM Endif Line SendALM VIP_Flag = True Goto MONITOR Line E If TS > 0 then Goto INIT

Issue After an upgrade to EBO version 3 the  "Alarm State Sort Order" in EBO Webstation is not following the  "Alarm State Sort Order" set in Workstation for certain Alarm Views. Workstation:   Webstation: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and later Cause This issue is only seen on Alarm views upgraded from a version earlier than 1.9 to EBO 3.0 or later The problem is that in EBO version 1.9 Webstation did not follow the sort order for Workstation, back then the sort order in the alarm view in Workstation and Webstation was separated. And the default sort order in Webstation was "Triggered time" when upgrading to version 3 the upgrade does not change the sort order for Webstation. So after the upgrade the sort order in the alarm view is "Triggered time" and it will not follow the sort order from Workstation.    Resolution In EBO Webstation version 3 click on the "Filter" button in the Alarm view. Click on "Sort" and remove "Triggered time", click OK In Workstation open the Alarm view and right-click, Open Alarm view settings and click on "Reset standard layout to standard default"  

Issue Both errors indicate WorkPlace Tech cannot determine if the vsd file being opened is in the current project. Environment WorkPlace Tech Cause The names of the folders that were brought forward contained an apostrophe, i.e. Vav's, AHU's, etc. Resolution Rename the folders eliminating the apostrophe before bringing the folders\drawings into the new project and these errors will not occur.

Issue The site has Alarm Action to email certain door alarm condition but only at a specific time of day and/or day of the week Product Line Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause Alarm actions do not allow association with a regular schedule, instead, the filter query can be used to specify a time and/or the day the action should take place. Resolution The screenshot below shows the schedule that the site wanted to use to specify when the action should be carried out... Since we can not associate the schedule with the alarm action, we should instead specify the days/hours in the filter query using the following filter...   ((EventData["Status"].AsString == "Activated")&&(((OccurredOn.Date.Hour < 17 && OccurredOn.Date.Hour < 4)&&(OccurredOn.Date.DayOfWeek == "Tuesday"|| OccurredOn.Date.DayOfWeek == "Wednesday" || OccurredOn.Date.DayOfWeek == "Thursday" || OccurredOn.Date.DayOfWeek == "Friday")) || (OccurredOn.Date.DayOfWeek == "Saturday" && OccurredOn.Date.Hour > 4)|| (OccurredOn.Date.DayOfWeek == "Sunday")||(OccurredOn

Issue On two occasions all of the scheduled periods disappear from the schedule. Environment AS Schedules Exception Schedules Cause Weekly scheduled times were entered as exception schedules. Resolution Recurring periodic scheduled event which occur week after week should be programmed as weekly schedules.  Exception schedules are used to override weekly scheduled events.

Issue When setting "Notification on change" on a Xenta Server in Vista, nothing seems to happen. There is no reduction in the traffic. Environment XBuilder Confirmed in Vista version 5.1.1 Cause If you have a space in the XBuilder project name (see Project > Settings) "Notification on change" does not work. Resolution In XBuilder, navigate to Project > Settings If there is a space in the Project Name, delete the space or substitute with an underscore Upload the project again.

Issue Once working access cards now produce invalid read when presented to card reader. Environment Card reader Invalid read Cause Reader power supply was no longer supplying power to the reader. Battery backup had been depleted and was not supplying sufficient voltage to the reader.   Resolution Repair or replace card reader power supply.

  Issue PIBCV valves, stem up or stem down for valve open. Product Line Field Devices Environment PIBCV Valves VP220, VP221, VP222, VP228 Cause Further information required as to whether stem up or stem down for valve open position. Resolution When the stem is up (retracted into the actuator) the valve is open.   Example:

Issue How does the controller-resident schedule work in a Revision 11.x MicroSmart controller? Environment MicroSmart controllers revision 11.x and 10.x Cause Main DMS panel and/or NC panel were removed. Resolution With the loss of schedule control from the DMS or NC, each controller has two built-in schedules numbered 1 and 2. The Start/Stop point requiring a schedule can be assigned either one of these schedules followed by a letter A or letter B. Letter A stands for 'always' and letter B for 'backup'. With no DMS or NC present, enter the schedule as 1/A or 2/A.  Assign 'off' and 'on' times as required. Remove any reference to a DMS or NC schedule number (i.e. set it to a value of 00). 

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue What are the specifications of the internal battery of a UNC-6x0? Environment UNC600 UNC610 Cause When the battery is replaced, follow Technical Bulletin TB06-05 to restore the BIOS settings. Resolution The internal battery is a CR2032 (3 Vdc) and is available from any retail technology outlet store.

Issue Can Enterprise Servers inherit licenses from a parent Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need to know if Enterprise Central Licenses can be inherited by an Enterprise Server, and then, in turn by Automation Servers. Resolution An Enterprise Server cannot inherit its licenses from a parent Enterprise Central. Licenses can only be inherited from an Enterprise Server by the attached automation servers. Refer to WebHelp article Inherited Licenses and Knowledge Base article SmartX Server License Inheritance in EBO 3.x.

Issue Samsung’s Knox security protection on your phone or tablet data is out of date. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Advanced Display v2 Cause   One of the security features contained within the Android operating system is Samsung Knox which the Advanced Display uses. Samsung Knox needs to get security updates periodically and needs to be online to the Internet to receive these updates. As a security feature if Samsung Knox is out of date it can stop the operation of some of the apps. For further information, see the Samsung’s Knox website. If Samsung Knox security needs an update when the AD-Link is launched then one or both the following messages may appear on your display.   Resolution Firstly, if the Advanced Display v2 is not running SmartXKiosk v8.2 and SmartX AD-Link v8.0.apk, then the latest versions are not installed and a request can be made by raising a case with your local product support team for the latest releases. To resolve the Samsung Knox issue, carry out the following procedure: Connect the Advanced Display to a WiFi network that has Internet access. Re-start the device. Confirm the phone or tablet still has an internet connection. Launch AD-Link. (several license windows will appear on your display). The SmartX AD-Link app should now run.

Issue Will Signal XP software run on Windows 7 in the XP mode? Environment Signal XP, Windows 7 Cause Will Signal XP software run on Windows 7 in the XP mode? Resolution SIGNAL XP software has not been tested or validated to be compatible with the Microsoft Windows 7 operating system or running in either Windows 7 XP or Virtual XP mode. Since the product is obsolete, no further engineering work will be done with the product.

Issue The WorkPlace Tech application drawing contains a hardware tag that is outlined in red and displays this error message when viewing the right-click Display Errors option for the tag Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio Cause The issue may be caused by incorrect copying and pasting of objects inside or between drawings.  An absolute cause has not been determined  Resolution Open the application in WorkPlace Tech or Editor.  Don't open the .vsd or .vsdx file in Visio alone. Enable the Developer in the Visio ribbon. File/Options/Customize Ribbon/check "Developer"  The Developer must be enabled to have the Show ShapeSheet option available  Right-click the Input object and select Show ShapeSheet In the ShapeSheet:  Step 1. Select the corrupted string for the Connection Points Step 2. Delete the string Step 3. Click the green check mark to save Unlink and Relink the connector between the previously corrupt object, UI01 in this case, and the Analog Input object.  Note, that this could be a Binary Input object as well.  This will add the correct string to the Connection Points.  

Issue When a Xenta Server alarm object generates and email, the email is accompanied by several emails showing alarms from objects that did not go into alarm. Environment Xenta Server 5.0.2 through 5.1.7 Cause When the system program in the Xenta server polls multiple point simultaneously it may interpret one alarm signal as multiple alarm signals from all polled points. Resolution Option 1 - Edit the Xenta Servers Xbuilder project Change the scan time on all alarm objects so that they are at different scan rates. Generate the project Send the project to target. Option 2 - Connect to the affected I/NET controllers Modify the points in Resident I/O Change the scan rate of each point so that all alarms have different scan rates.

Issue What is Life Reporting? Product Line EcoStruxure Security Expert Environment Security Expert Schindler Elevator HLI Integration Cause What function does the Life Reporting feature in a Schindler Elevator HLI Integration perform Resolution Life Reporting is a feature in the Security Expert Schindler Elevator HLI Integration. The life reporting interface is how Access Events from the Schindler system are reported back to Security Expert via TCP port. When enabled, you can receive "floor unlocked" events. Multiple loggers can be configured for the life reporting interface using the same IP address. Up to 32 loggers can be configured for the life reporting interface. You can also use Schneider Electric card readers for elevator access control alongside the Schindler system. For more details including prerequisites and configuration, please read AN - 196 - Security Expert Schindler HLI Integration    NOTE: Security Expert Software v 4.1.180 or higher is required. SX Controller Firmware v 2.08.919 or higher is required. One Security Expert Schindler Elevator High Level Interface License (SX-ELV-HLI-SC) per controller is required.

Issue Specifying engineer wants to know the input impedance of the voltage inputs on the MNL-10Rxx / 15Rxx / 20Rxx controllers.  This information is not in the data sheet. Environment MNL-10Rxx controller MNL-15Rxx controller MNL-20Rxx controller Cause Job specification requirement Resolution The minimum input impedance for a MNL-10Rxx /-15Rxx / -20Rxx  UI configured as a voltage type input is 20K ohms.