Building Automation Knowledge Base

Issue Alarm bell icon that appears on the pinpoint door control does not appear when the door is in an alarm state. Environment Pinpoint Door Control Icon Cause The door control is on a lower level and the alarm icon is being masked by a graphic component that is on top of it.  Resolution Select the door control. Right click on the door control. Select Bring to Front. 

Issue Attempting to upgrade an I/A Series R2 Enterprise Server station and the database conversion fails: java.lang.OutOfMemoryError Environment I/A Enterprise Server R2 (all versions) Cause The issue is related to the limitation of the Java Virtual Machine (JVM). The conversion process is attempting to perform the upgrade on the station database and is exceeding the 1GB Java heap during the process. This typically occurs on an Enterprise Server station where the station database (db) contains a large number of log objects and associated logged data records.  Even though the records are archived in the SQL, the running station (log objects) still maintains records within each object. Resolution Verify that the Java heap is configured to allocate the maximum memory. Use the Windows Explorer and locate the nre.properties file (\niagara\lib directory). Edit with a text editor and verify the setting is Java.options=-Xmx1024MB. If not, change and save then restart the Niagara service and try to upgrade again. If the upgrade or conversion still fails (out of memory error), logs will need to be cleared in the running station to decrease the number of logged records. Restart the station in the current version (prior to the upgrade). Open the station and save the current records to the associated SQL database.  Select the Log Service (double click) and perform an archiveAll command (WorkPlace Pro menu items - Command).  The archiveAll command causes the data currently held in every log object to be immediately archived (sent to the LogService archive destination). Note this applies even to logs that are not configured to archive (daily and/or near full). There are two methods of clearing the logs.  The first method involves selecting each log object (double click) and perform a clear command (WorkPlace Pro menu items - Command).  The clear command clears all log data currently held in the object’s log buffer. The second method utilizes the AdminTool object to globally modify the log buffer sizes to temporarily decrease the buffers that will subsequently remove records that currently exist in the log object.  The AdminTool object is a special “utility” apps object, available in the Local Library (tridium/apps/AdminTool). This object provides an admin-level command to “Search and Replace” property values for objects in the station database. Config properties define the property name to search, new value to write, plus other parameters for filtering and recursion. This operation automates what would otherwise be a manual process of opening and modifying multiple objects’ property sheets. Note: The adminTool will globally apply the changes to objects defined within the utility.  Multiple iterations of this process may be required if log objects are configured with different buffer sizes. Open the local library and copy the AdminTool object to the station's root directory. Open the AdminTool properties and select the Config tab. rootNode -- Configure the swid of the starting point (upper hierarchy) of the station database in which the AdminTool function operates. This can range from the station’s root (/db/stationName) to any container or primitive object in the station’s database. If the recurseChildren property is True, the AdminTool function applies to any and all objects under the rootNode swid.  In Tree View, a right-click “copy” on any object under the station captures its swid. Use CTRL-V to paste the swid into the rootNode field of the property sheet. propertyName -- The target property name, exactly as shown on the object(s) property sheet(s). The property should be a read-write type.  In this example, configure the propertyName to bufferSize. elementName -- Not required for most properties that specify a single value of type float, integer, boolean, or string.  In this example, leave unchanged "-". newValue -- The new value assigned to all matching properties in (and under) the specified rootNode.  In this example, configure the newValue to 1 (bufferSize temporarily changed to size of 1). recurseChildren -- Defines if the search-and-replace function is extended to all children (and subchildren, etc.) of the specified rootNode.  In this example, configure the recurseChildren to True. objectTypeFilter -- Defines a match filter, meaning only objects of this matching type are affected. The asterisk (*) is used as a “wildcard.”  Partial strings of object types are supported, for example, AnalogO* will apply to object types AnalogOutput and AnalogOverride.  In this example, configure the objectTypeFilter to *Log (modify all logs e.g. AnalogLog, BinaryLog, IntegerLog, MultistateLog, and StringLog).  Note: The entire log type could be specified to only apply the changes to a specific type. nodeNameFilter -- Defines a match filter, meaning only objects with matching name are affected.  The asterisk (*) is used as a “wildcard.”  In this example, leave unchanged "wildcard." propertyValueFilter -- Defines a match filter, meaning only objects with this exact value are affected.  In this example, leave unchanged "wildcard." Execute the search and replace command (WorkPlace Pro menu items - Command). Return the newValue to the required buffer size and execute the search and replace command.  The smaller database can now be saved and upgraded or converted as required.

Issue When printing a multiple page application, i.e., an application consisting of a device definition and one or more custom object pages, all pages are numbered 0 of 0. Environment WorkPlace Tech Tool release 5.8.0 or release 5.8.1 Cause The title block stencil script created in WorkPlace Tech release 5.8.0 or release 5.8.1 does not execute properly resulting in all pages showing "Page 0 or 0". Resolution Update to WorkPlace Tech Tool release 5.8.2.  Note that upgrading will not automatically correct the issue in application files created with release 5.8.0 or release 5.8.1.  Use the following procedure to correct the issue in application files created with those releases of the WorkPlace Tech Tool software. Open the application using WPT 5.8.2. Select the "Background" page of the drawing. Press Ctrl-A to select everything on the page then press the Delete key to delete everything from the page. Select the "Annotation" style sheet (stencil page). Drag a new copy of the "Schneider Electric Border" stencil onto the page. Drag a new copy of the "Controller Info Block" stencil onto the page.  This block is normally placed in the lower left corner of the drawing. Save the updated application file.

Issue Added multiple Lon devices to Lon Network and need to mirror SNVTs from more than one device to the Local Node Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Enterprise Server Cause Using SNVT bindings between devices and the Local Node of the EBO server allows LON communications bandwidth to be optimized by using the LonWorks protocol Send and Receive Heartbeats configured per device. However, it can be a time-consuming task to mirror SNVTs from multiple identical devices. This time can be reduced by selecting SNVTs in multiple devices using search. Resolution Create a new search Search for one SNVT that is available on multiple devices Use this article to create the mirrored SNVTs in the local node: Creating Network Variables Automatically Search for the next SNVT that is available on multiple devices Repeat until all desired SNVTs are mirrored. RECOMMENDATION: Save the searches for use later when adding more new devices.

Warning This article describes a feature that is not standard functionality within the Product Line.  It has been provided to allow customers the option to use this requirement.  Pay particular attention to the Prerequisites of the required programming. Issue Customer requires the functionality for Individuals  to double badge (present their credentials twice) to gain access. Product Line TAC INET Environment Access Control Cause Customer application requirement Resolution Prerequisites: LIMITATIONS: As this is not a standard access control feature within I/NET, it uses custom programming, which therefore reduces/limits the standard features within I/NET The description provided below must be set for ALL individuals with access to the door that requires double badging.  It does NOT cater to custom individual use.  It may be possible to provide additional programming to achieve this, but this is not detailed in this article. Door Automatic Time Schedules (ATS), if applied, can be overridden if the door reader is badged during the scheduled operation.  The functionality of this feature uses event-driven programming, which in its nature is single-shot programming and therefore relies on the following:  Requires reliable communication between SLI/MCI (779x) and the SCU (Door Controller).  The door reads from the SCU must be received by the SLI/MCI to activate the badge/read occurrence. Requires SLI/MCI (779x) CPU loading below 65%. LAN Load of this controller should be below 2%; anything above this can cause the operation to fail/be inconsistent.  Removes the standalone capability of the Door controller (SCU) POINTS The points required for each door that requires this functionality are Door Reader (Internal DO door point as required in I/NET)  Door Strike (External DO Point) must be programmed within the controller Door Intermediate (Internal DO Point). :: Scan Rate 1 second Door Read Count (Internal AO Point). :: Scan Rate 1 second I/NET Controller Summary Note: The address order, as shown in the screenshot above, is important for the overall operation.   That is Read Count must be at a lower address than all other points.  Next the Intermediate point.  The Strike and Reader addresses are fixed by I/NET but must be at a HIGHER address than the Read count and Intermediate points.    DOOR Intercard Interval (sec) should be set as low as possible.  This allows the card to be present within this time setting (minimum is 1 second) Door strike: Configuration of the door/reader must have this set to either. None: When a valid read is received, no action is sent to the strike Exit: Only when an Exit read to Request to exit (REX) is received by the door does it activate the strike.  Strike duration (sec): Should be set 1 second above the scan rate of the Intermediate / Read Count points above.  In this case, it is set to 2 seconds.  Note: this does not have any bearing on how long the strike remains "unlocked" Door editor Programming DOOR No additional programming is required for the door apart from the details provided in the above prerequisites.  ACCESS INITIATED CONTROL (AIC) Add an AIC that will trigger the Intermediate point on a "valid" reader entry for the nominated door. Select the Target point (DR1 Intermediate) Select either Use all individuals in the range which will trigger this action for all individuals.  Note: If selected Individuals are needed to activate this feature, then additional programming is required and not detailed in this article.    Select Reader entry to START the target point  Select which Doors are to trigger this action Access Initiated Control editor POINTS From the screenshots below, it can be seen that: Point DR1 Read Count has two extensions: Calculation (C)  Operation: The result of this calculation is displayed on the DR1 Read Count point.  The calculation adds the value of itself (P0) DR1 Read Count and point (P1) DR1 Intermediate point (where 0=OFF 1=ON), the result of which is then multiplied by the NOT (~) the value of (P2) Door Strike (where sec = 0 Unlk = 1). Result: DR1 Read Count is incremented by one on each valid read.  The counter is reset (zeroed) when the Door Strike is energized.        Event Definition (EV)   Operation: When the point DR1 Read Count crosses the value 1 (the value of 2 represents the double (2) badge), Sequence/Action #1 is triggered.  From the above Event Definition (EV), this runs Sequence/Action Num 1, which is shown below:  Operation: When triggered by the (EV) above, the Door Strike is immediately "Stop"  (Unlocked); after a 5-second delay, the Door Strike is "Start" (secured). Note: The delay of 5 seconds on line #2 determines how long the strike remains in the unlocked state.  Modifying this value will shorten or extend the unlocked state.     Point DR1 Intermediate has only one extension: Calculation (C)  SUMMARY OPERATION A valid card read is presented to the reader; this triggers AIC to turn point DR1 Intermediate to ON. This increments DR1 Read Count by 1 to the value of 1 via its Calculation (C) extension The additional card read repeats Steps 1 and 2 above;  DR1 Read Count value increments to a value of 2. Event Defintin (EV) high-value crossing (>1) triggers Event Sequence #1 Event Sequence #1 unlocks Door Strike 1 and, after a 5-second delay, relocks (secures) Door Strike 1 point. This relock (secure) of Door Strike 1 zeros the DR1 Read Count value via its Calculation (C) extension.  ATTACHMENTS - for reference showing the above details  I/NET Controller SAV file (DCU0201.zip) Backup InetDb (SQL.bak).  (InetDb_DoubleBadge.zip)  

Issue When performing a backup of all Servers and All Data on an Enterprise Server the backup fails and generates an error in Software Administrator indicating the backup is corrupt although the backup is not corrupt. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Enterprise Server Cause There is not enough free disk space on the Enterprise Server to save the backup file created.  The error generated in Software Administrator is a generic error. Resolution Check the Trace Log for Internal Server Error: Insufficient_Space_For_Backup If this is evident free up additional space on the Enterprise Server and re-try saving the backup.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue There is an alarm showing after adding a downstream controller Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Instructions needed to eliminate the power failure and  tamper alarms showing on newly added downstream devices Resolution When adding downstream devices, for example, An MR50, MR52 or MR16In/Out to an SSC, EP1501 or EP1502 controller, an alarm may show in the hardware tree. To get the controller out of this state, the following steps need to be taken: a. Locate the terminal block(TB) on the panel which contains the connections for CT (Cabinet Tamper) and BA (Power Fault) Note: You may need to consult the specific controller documentation since the TB#  with these connections are different on each board. It will look similar to the following: b. Remove the connector Cut two small pieces of wire, one for each Alarm Use the 2 wires to jumper each connection (CT and BA) to create a closed circuit. This assumes these contacts are not being used for their usual purpose. No resistors are required Place the connector back on the board The downstream devices no longer show alarms for the respective addresses.

Issue Is it needed to connect DC voltage to trigger the DI of the 301 and 421A What is the max current/voltage that a DI point can handle. Environment Xenta 301, Xenta 302, Xenta 4xx Cause The inputs on the Xenta 300 and 4xx are active inputs from the terminals X1, U1 etc. Meaning the terminal is at high voltage when open.  For a UI (act as a DI) channel, the voltage across open contact is approximately 20 V DC, and for a XI channel,  the voltage across open contact is approximately 33 V DC. To activate the digital input, engineer needs to connect the signal to M ( = 0 volt) terminal, so current flows FROM the X1 to M. So basically we expect a switch that connects M and X1 (U1). Resolution No you only need a switch that connects M0 to X1 or U1 (or other digital, universal input). Note: It is recommended to have a non-voltage dry point relay switch to protect the digital input on the controller and IO module.

Issue Setting up camera motion detected or camera image lost camera events to trigger an Output or Output Group. Product Line EcoStruxure Security Expert Environment Security Expert Video Integration Cause Through various Video Integrations, Security Expert is able to use camera events (such as camera motion detected) to popup a camera window when those events are seen. However, camera events are not associated with an Input or Door and therefore Security Expert is not able to trigger Outputs or Output Groups directly from these camera events.  Resolution Camera events are not able to be used to trigger Outputs or Output Groups in Security Expert. If this is a requirement, contact local solution category management to have this setup as a new feature. 

Issue Information needed for Integrating Access Expert BACnet objects into Continuum and EBO Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted EcoStruxure Building Operation Andover Continuum BACNet Cause BACnet objects from Access Expert may show in Andover Continuum, but will not function. An integration using EcoStruxure Building Operation is needed. Resolution BACnet objects from Access Expert may show in Continuum when a BACnet discovery is done, but they will not function.  An integration using EBO with a SmartConnector is required to use Access Expert BACnet objects. Further details on the EcoStruxure Access Expert Smartconnector are available from the Exchange Marketplace.  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When adding a new Domain an error shows “Object does not exist – The domain “your Domain Name” does not exist, and the Domain is not created.   Using control panel Or using System/Domains folder Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Building Operation Enterprise Central Cause A Content Type rule could be incorrectly configured Resolution Navigate to /Your Server Name/System/Content Types/Rules/ If there is a “*” in the “Container Name Pattern” of any of the rules, correct this or delete the rule.     Once completed, new domains can be added.

  Issue Is it possible to use the RP-C relays to control LED Light?  The specification sheet does not specify the maximum inrush current. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause RP-C is not designed for switching light loads, and especially not LED loads. LED loads will result in a very high inrush current and require relays that are designed for that. Furthermore, the light application often requires relays that keep the light on in case of power failures which is not the case for RP-C. Resolution The CRS light modules and the Hotel Relay modules have that type of relays and can handle peak currents up to 800A, which is typical for LED loads. If using the CRS modules is not an option for the customer another possibility is to use a contactor connected to the RP-C.

Issue The Zenitel integration to Access Expert provides the ability to add Zenitel ICX-500 controllers and stations for interaction with intercom devices and monitoring Zenitel events. In the Access Expert Windows Client, Zenitel Exchanges are accessible from the Intercom tab within the Hardware Provisioning section. The associated list of stations will appear when selecting and opening an Exchange. Product Line EcoStruxure Access Expert Environment Access Expert Hosted software Cause While trying to integrate a Zenitel intercom system to Access Expert there are some very specific steps that need to be followed Resolution Zenitel Exchanges Exchanges are used to group together and connect a specific set of Zenitel Stations. Through the Exchanges list, the following functionalities and properties are accessible: Add an Exchange: To add an Exchange, navigate to the Exchanges list and click “Create Exchange” in the upper left-hand corner. A dialogue will appear, prompting for a Display Name and MAC Address. Additional properties and information are available for viewing on the Exchange document once it’s been added. Note: It is important that the MAC address is valid. This is how the stations connect and populate in the instance. Note: The MAC address is not editable in the Exchange document after creation. Stations List: Each Exchange document has a read-only list of Stations connected to it. The system automatically populates the list based on Stations with a connecting MAC Address. This list is automatically updated with the most current available stations.   Zenitel Stations Stations are used to make calls. Stations can be accessed via the Exchange to which it’s connected, the global search bar, or the hardware tree. The Station contains the following properties: Display Name (Editable): This is the editable display name associated with the station. Connected To (Read-Only): Display name of the connected Exchange Configured Name (Read-Only): This is the non-editable original display name of the station configured by the ICX-500. Exchange Number (Read-Only): Number of the associated Exchange. Directory Number (Read-Only): Number to dial to reach this station. Connected Reader (Editable): Reader associated with the Station. Users may specify a reader in case they need to perform actions on surrounding hardware. Cameras/Views (Editable): Multiple cameras and views may be added via the Cameras tab. Reader functionality: Within the Stations form, users may specify a connected reader. Associated functionality to the reader is accessible directly through the “Actions” dropdown list or in the context menu when right-clicking a station that has a connected reader attached.   Functionalities for the associated readers include: Pulse Connected Reader Turn Connected Reader to Online Mode Unlock Connected Reader Lock Down Connected Reader Reset Connected Reader Floor Plans Edit Floor Plan: Stations may be added to floor plans. In the left-hand list of Available Hardware, all stations within the current instance will appear and may be added using the plus button to the right. At the top of the available hardware, a station icon exists for filtering.   View Floor Plan: When viewing a floor plan with connected stations, the station's alarm status will appear in real-time. The appropriate statuses and line states of the stations are also displayed and changes occurring with the stations are updated on the floor plan accordingly.   Hardware Tree Stations can be accessed via the hardware tree and can be filtered from the top of the list via its icon. The color of the Station object is used to determine its state (Green for Online, Red for Offline). Status is also viewable via an icon that appears on the Station (Black “X” indicating that a station is busy, grey phone symbol indicating that a station is in a call). Since a standalone list of all stations is not available via the Windows client, the hardware tree is the only place all stations within the current instance can be viewed at once.   Licensing Licensing of the Zenitel integration is based on the number of stations. Instances may be licensed for any number of specified Stations and thus, the system will not allow Stations within the instance to exceed the amount in which it’s licensed. If the instance is not licensed for any stations, the “Intercom” section in the Hardware Provisioning tab will not be visible.

Issue Can a MN-Sx differential setpoint be defined using the WPT Hardware wizard? Environment MNL or MNB controller with any MN-Sx sensor Cause Project specification requires that all temperature setpoints for a site be fixed and the facility users be allowed to adjust the setpoint  with a relative positive or negative offset. Resolution In the Workplace Tech Tool use the hardware wizard to configure the setpoint with an initial value of 0.0, one decimal place and no limits. Configuring the setpoint in this manner allows the setpoint to be changed over the range of -99.0 to +999 without limit. If limits are required by specification, such as a +/- 3 degree limit, the setpoint value from the sensor would need to be passed through a Limit control object to prevent extreme setpoint offset adjustment.

Issue How to use secondary values in programmable points. How to use forecast in programmable points. Environment BAS SIGMA Cause Some objects in Sigma and BAS have secondary values: Time Schedule - minutes to next switch (when the time schedule is going to change state) is displayed. An example of this is to bring on the heating plant 30 minutes before an AHU starts. Optimiser - minutes to next switch (when the optimiser is going to change state) is displayed. An example of this is to bring on the boiler plant 30 minutes before an VT cct starts. Rotation - the lead load no. is displayed. An example of this is to determine the lead load when a modulating burner signal is used. DO and DI - the hours run is displayed. An example of this is to do pump changeover on hours run. Resolution Example: For a Time schedule: 10 xflo =  P100 (timeschedule object) forecast 20 if P100 off and xflo < 30.0 then return true "Plant PreHeat" 30 if P100 on then return true "Time On" 40 return false "Time Off"   For a Rotation object with 2 loads: 10 xflo = P120 (rotation object) forecast 20 if aflo=1.0 then return true "Boiler1 Lead" 30 if aflo=2.0 then return true "Boiler2 Lead" 40 return false "false" Note: aflo is used as a global variable to another object in the same controller, if not required then substitute with xflo.

Issue Since the MZ18 is only 180N torque spec, is there a higher torque version available? Environment MZ18 in various versions. Cause Some applications require a higher torque actuator. Resolution Unfortunately, the MZ18 is only available in a 180N version through Schneider Electric.

Issue Unable to use SE8650 to control heat pump with a two Stages Furnace (auxiliary heat) Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause Only one output is available in the SE8650 for Auxiliary heating Resolution A simple solution would be to Wire both Furnace W1 and W2 to the SE8650 W1 terminal, and both will be on at the same time Both furnace stages will be activated as a single stage from the same output Or a more advanced option would be to use a LUA Script to control the second stage of Auxiliary heating. See the below example using the SE8650 UO11 terminal  

Issue Live Eventview not showing name after upgrade. Environment CyberStation Cause Unsure. Resolution The problem went away when the database was updated with enhanced alarm delivery turned on.  

Issue Every time the trendlog data should be viewed an alarm saying" The digital signature does not match, values might not be reliable". How can we avoid this? Environment Vista 4.4.2 Cause In old Vista versions like Vista 4.4.x we had something called Digital signature to check that the data in the SQL database had not been tampered with. This have been taken away in later Vista version as it slowed down and caused problems with trendlogs. The alarm indicates that someone have done something in the SQL database and the digital signature does not match.   Resolution It is possible to turn off the Digital signature in the Vista server setup under the SQL tab and then restart the Vista server. Then Vista will not do this check and the alarm should not appear.

Issue Could not start the TAC Xenta 102-AX LonWorks PlugIn, due to an Error message. Product Line EcoStruxure Building Operation. Environment EcoStruxure Building Operation Workstation. TAC Xenta 102 AX Cause EcoStruxure Building Operation does not support online PlugIns, as LNS is running in the background, without any communication port.. If selecting to Synchronize (Upload or Download) you will get an error message. Resolution Select "Skip" synchronize.