Building Automation Knowledge Base

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 Upgrading a JACE-8000 or Edge-10 from 4.10U7 to 4.11 or 4.12 will prevent Niagara Daemon from starting.  You will be unable to connect via Workbench or Browser. Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Tridium Edge 10 Cause The software in builds 4.10u7 and later LTS builds (4.10u8, 4.10u9, 4.10u10) was released after 4.11 and 4.12 reached EOL.   4.10u7 contains a newer signing key that is not recognized by 4.11 and 4.12. Resolution When upgrading JACE-8000 and/or Edge 10 running 4.10 LTS builds 4.10u7 and later, please skip over 4.11 and 4.12 and instead upgrade to 4.13u3 or newer. Alternatively, you may apply the dist that reverts JACE-8000 to clean 4.9u1 state, or for Edge-10, the dist that reverts it to clean 4.7 state. You can then install 4.11u2 or 4.12u2, if that's the version you have to use.  If you've already attempted the commissioning operation and bricked a device, and have backups, you can connect to the debug port and use the factory reset process per the documentation.  For Edge 10, consult the section titled Factory Default Recovery  in the Niagara Edge 10 Install and Startup Guide.  For JACE-8000, consult the section titled Restoring factory defaults  in the JACE-8000 Backup and Restore Guide. If you are lacking any backups for the host, then before performing the factory reset, you should enable SSH/SFTP via the debug port, and then copy out the Station files using Filezilla or WinSCP or equivalent.  Reach out to your support channel if you have difficulty finding the location of station files. Typically, the files will be in a subfolder of /home/niagara/stations. The config.bog file will be keyring encrypted, and you'll have to reset it using the Bog File Protection Tool. See Editing the .bog file passphrase offline in the Niagara Platform Guide  for details on using the Bog File Protection Tool.  For details on using the debug port on JACE-8000, see Debug port  in the JACE-8000 Install and Startup Guide.  For details on using the debug port on Edge-10, see Connecting to the debug system shell  in the Niagara Edge 10 Install and Startup Guide.

Issue How to configure PCT memory in Hyper-V. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Hyper-V Cause There is more memory available but PCT 2.0 can't start more servers. Example: Users with over 8 GB of memory can't start more than 36 servers.  Resolution This is because the default memory is set to 8GB, approximately 36 servers. (8GB - 2GB)/.170 GB = 36 server. Open the Hyper-V Manager In the left panel, right-click on "pct" and select Settings. The Setting dialog box opens. In the left pane, under Hardware, select the Memory item. The memory settings open in the right panel. The RAM shows 8192 MB(8 GB * 1024 = 8192 MB), the "Enable Dynamic Memory box" is checked, the Minimum RAM is 8192 MB and the Maximum RAM is 262144 MB(256GB *1024 = 262144 MB).    Enter the amount of memory assigned to PCT, 10240 MB(10 GB) in the example. If the "Enable Dynamic Memory" box is unchecked, the memory assigned to PCT will be 10240 MB. If the "Enable Dynamic Memory" box is checked, the memory assigned to PCT will be between 8 GB and 10 GB(not 256 GB or other amount because the limitation is set at 10 GB from the RAM setting above). R&D recommends not using "Enable Dynamic Memory".   Helpful Link: PCT 2.0 memory usage calculation

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 A full backup immediately fails on the Automation Server.  Performing a configuration-only backup completes successfully. Product Line EcoStruxure Building Operation Environment Building Operation 3.x - first detected Building Operation Automation Server  Building Operation Automation Server Premium (AS-P) Building Automation Server AS-B Cause A directory under the DB folder, called tc [TypeCache], within the database of the Automation Server, had grown close to 1 GB in size.  The combination of this with the large TrendDb caused the backup failure with the following message seen in the trace log:    nsp.csc.bar.BarBackupOperation BarBackupOperation Execute failed with: Internal Server Error: Insufficient_Space_For_Backup (0x80008) in module Bar_Manager(51). "/<servername>": Insufficient space for backup, XXXXXXXXX bytes estimated for new backup but only XXXXX available   This tc directory contains types fetched from other servers that are used in runtime. These are loaded either from the local database or the tc directory. If a type for another server is not found in the tc directory when accessed, it will first be fetched from that server.   There may be other reasons for the backup failure, presenting this Insufficient_Space_For_Backup message in the trace.log. Clearing this Type Cache does not adversely affect the controller and can be cleared as the first step to see if this will allow the full backup to occur.    The issue has only been seen in Building Operation 3.x, if the issue is presented in a later revision or you continue to have failures, then contact your local support and reference this article.     Resolution To clear the Type Cache contents, follow these steps: Navigate to the RuntimeDBManager object under /System/Modules/RuntimeDBManager/ Right-click on the TypeCache object. Select Type Cache Clear All Attempt a full backup of the server again.  If failures continue to concur, then contact your local support

Issue The "BACnet device proxy base" type is missing in the Search type after EBO 4.0 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Building Operation SmartX Living Space Sensor BACnet B3 IA SE8000 VT8000 Cause The "BACnet device proxy base" was removed from EBO 5.x and later. Resolution To search for a specific type, add individual type to "Include types" For example 'BACnet device' will return all 3rd party (generic) BACnet devices. 'SpaceLogic Series Device' will return all MP and RP devices. Sample Search all BACnet devices(excluding AS/ES) XML attached

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 Page 1031 of the hardware reference guide only states wire cross-sectional area: 0.34 to 2.5 mm 2 (22 to 14 AWG) and not the number of wires allowed to terminate. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24V Building Operation Room Controller (RPC) 230V Cause Documentation clarification. Resolution It is OK to terminate up to 2 wires into each terminal as long as the total area of the wires does not exceed 2.5mm 2 .  

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 One or more inputs on the SP-ACX will randomly report as open for a brief moment (a second or less), This can result in unauthorized door access if for example the input is associated with a door Exit Request. Product Line EcoStruxure Security Expert Environment SP-ACX Cause Electrical noise in wiring Resolution Increase the Alarm input speed, issue has been seen with Alarm input speed set to 0, increasing the input speed to 1 second typically resolves the problem.

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 Extending a User/Cardholder Expiry Date Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Steps needed to Extend an Expiry date for a cardholder Resolution In Access Expert, there needs to be a way to extend cards that are about to expire after the default time has been entered initially. This can be done for single users or badge types depending on the circumstances. The following steps describe how this can be accomplished:   Open and log on to the Users instance Once opened, select Access Control and click on the List Tab then select View Expiring Cards A list will appear that shows all the cards that are about to expire based on the parameters entered When this list comes up, Select the Extend All button to bring up the Editor that will extend the time Enter the New Expiry Date that allows the card to function accordingly Click OK and the cards listed will then have the New Expiry Date listed    

  Issue Understanding the EP1501 and LP1501 downstream device limitations Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Downstream device limitations determine how many upstream controllers are required when using these controllers Resolution When choosing to use the EP1501 or LP1501, knowing the limitations of the downstream devices plays an important part in determining the number of controllers needed for a job. The limitation is 8 I/O devices, so if the downstream controller is an MR 50 then a total of 9 readers including the onboard reader can be utilized. Keep in mind that no matter what the mixture is, including MR51e's or MR52's, a total amount of 17 readers can be used or licensed on these controllers  

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.  

Issue How to configure two room sensors in ZBuilder. Product Line EcoStruxure Building Operation Environment ZBuilder Cause It is possible to configure TAC Xenta 121 or TAC Xenta 122 to use two room sensors via the ZBuilder tool. Resolution In Zbuilder, under the tab Configuration, under Room unit, select the type of sensor you are going to use. Select the tab I/O Setup,  Right click on the sensor and select Duplicate. Move the sensors to the input you are going to use.   At the end of this session you will be able to: Configure TAC Xenta 121/122 to use two room sensors. Understand that the nvoSpaceTemp value is calculated as average value of the two sensors. Understand that it is not possible to see the actual value of a single sensor when using two sensors.    

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.

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 Confirming compatible Modbus data types available for a Sigma IC3 Modbus Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) IC3 Modbus Cause The use of 64-bit is not mentioned in documentation Resolution 16-bit registers are supported with all versions of Sigma. From Sigma release 4 05 SEB (Build 3_43_18) 32-bit registers are supported. 62-bit registers are not supported with Sigma IC3.   The ba077 Modbus 32-bit application note provides information on the engineering of 32-bit registers. https://ecoxpert.se.com/search?documentUUID=74eaf0dd-fbd9-4429-9c82-eb205aa9be07&title=BA077%20Modbus%2032%20Bit%20Values%20-%20Satchwell%20-%20Application%20Note Sigma 4.06 IC3 Modbus Firmware and Release Note https://ecoxpert.se.com/search?documentUUID=cb99b073-d9ab-400e-8e67-2f8343447768&title=Sigma%204.06%20IC3-Modbus%20Firmware%20-%20Release%20Notes Sigma IC3 Modbus 1.n.2 firmware is the latest available version https://ecoxpert.se.com/search?documentUUID=02d88785-9d13-4184-b74a-d1a0b5ce7edd&title=Sigma%20IC3%20Modbus%201.n.2%20-%20Firmware    

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 IP Controller is getting incorrect overrides at Priority 16. The room control unit is writing to Priority 16 which is then writing to multiple setpoints with a zero (0) value in the function block program, causing programming to fail. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Even though priority 16 and the Value can sometimes be synonymous, they are still separate Objects The room control unit is writing to Priority 16 AND the Value has been set to Zero.   The value is set to 0  Writing directly to priority 16 from the room control unit Resolution The best practice would be to:  Bind to the Value Object from the room control unit and also set the retain level under Value rather than biding to and setting Retain level on Priority 16

Issue After Sigma transition into EBO, upon alarm and alarm clear there is no requirement to acknowledge the alarm. In the Sigma Interface, the object alarm 'Type of Acknowledgement is set to 'No' and cannot be changed. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Priorities are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm acknowledgement type is set to a specific type. If no alarm priorities are set for acknowledgement in Sigma, then this is repeated in EBO.    To change to 'Single' so that alarms and alarm clears are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Acknowledgement Groups   Redistribute the alarm priorities into the the different acknowledgement groups as per the site requirement. The image below shows the default view on a new install of Sigma.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'Extended', then the KB article Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm will explain how to change this.

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 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 What is the purpose of the battery/coin clip on some of the I/NET Hardware Product Line TAC INET Environment TAC INET Hardware  7718, 7716, 7798C  Cause The initial development path plan was to include an additional feature to allow communication with Dallas Semiconductor ID tag/coin, similar to that used with the I/NET Access Control I/DISC.  This development was never implemented Resolution This battery/coin tag serves no active purpose or functionality