Building Automation Knowledge Base

Issue Connecting an ARA 659 Esbe actuator to a Satchwell  CZT 5305 controller. Environment Esbe ARA 659 ARA 600 Series Wiring Cause Confirmation of the actuator wiring connections to the controller. Resolution The actuator is connected as follows; CZT 5305 - Esbe ARA 659 actuator. Terminal 36/37 - 24 volts (Brown wire). Terminal 35 - 0 volts (Blue wire). Terminal 19 - 0-10 volt (Black wire).- Heating actuator. Terminal 20 - 0-10 volt (Black wire).- Cooling actuator. To review the CZT 5305 datasheet please click HERE. To review the ARA 600 series datasheet please click HERE.

Issue Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.

Issue Replacement actuator for the STL-SR valve Product Line Field Devices Environment STL-SR Cause Replacement actuator for a STL-SR valve Resolution A M800 actuator or MV15B-24 or MV15B-230 actuator can be used to replace the actuator on the STL-SR valve series. Click here for the STL-SR datasheet. Notes: The original actuator e.g. M5CP, may have had a potentiometer fitted to provide position feedback to the controller. There is no direct replacement, the controller, actuator and valve may have to be changed. As a workaround, The M800 provides a 2-10V feedback, using a signal conditioner this could be converted to a resistive feedback. The original actuator may have had end switches fitted, order end switches to suit the replacement actuator. The M800 when used in floating control mode (dip switch 2= On) requires 4 wires. The original actuator used 3 wires to provide floating control.

Issue How to set up ID Works 6.5 in Windows 7 64-bit. Product Line TAC INET Environment ID Works version 6.5 I/Net Seven rev 2.4X SQL2008 R2 (Full) SQL2008 R2 Express Cause Normally this is needed for an upgrade or a new install of ID Works and I/Net Seven on a new Windows 7 64-bit PC. Resolution See ID Works Win7 64-bit Setup.pdf for step by step instructions for setup.

Issue There are no minimum current or wetting currents shown on the datasheets. Product Line EcoStruxure Buildings Operation Environment DO-FA-12 and DO-FA-12-H IP-IO Form A, B and C relay contacts Cause The relay outputs are not working since the minimum or wetting current was not maintained and the contacts of the relays have filmed up giving incorrect control. Resolution There are several relays used across this range of controllers and to ensure good low current operation, the minimum or wetting current should be 1milliamp at 5volts or greater. Wetting current is the minimum electric current needing to flow through a contact to break through the surface film resistance of a contact. It is typically far below the contact's nominal maximum current rating. It should also be noted that these controllers may be monitoring third party devices through their status or fault relays. An example of this would be an IP-IO monitoring a VFD for status. The IP-IO inputs will supply 3milliamp at 24volts. To ensure good lifetime operation of this output from the VFD, ensure this is within the VFDs range of minimum or wetting current.

Issue How to search for points, names, or descriptions in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The EcoStruxure Building Operation search feature can be performed on an entire database or on individual controllers / folders. This can help reduce the amount of time it takes to locate multiple points when creating mirrored points. Resolution How to search for specific names in EcoStruxure Building Operation Right click on the folder, object, or controller you would like to search in and click "Search. Note: When the search is narrowed down to specific areas of the database it will be able to complete the search faster than performing a full database search." In the search field type in the name that you are looking for. In this example the search is for snvt*. This will locate all points underneath the controller that begin with snvt in the point name. After a few seconds, depending on the size of the search area, the results will be displayed in the window to the right. In order to filter the search further, you can set different search parameters under the search field.

Issue Clicking a graphic page link fails to open any graphic page, but when opening the path using the System Tree of the server that contains the graphic page, successfully allows the link to open the graphic page. When opening the same page using WebStation, the graphic pages all open successfully. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation 1.9.x or below. Cause Typically having 'dead links' or unresolved binds in any graphic page is the reason for the issue. WorkStation pre-loads all objects of the references to the graphics. This call (CSP GetObjects) fails since (at least) one path of the objects points to a server that does not exist. Unfortunately the protocol can't return the objects that do exist and WorkStation then marks all these objects as non-existent and fails to open the respective binding. This operation cannot be corrected in this version of WorkStation and requires an upgrade to 2.x or above to correct this. Resolution Two options are available Correct/remove all link bindings that are shown with unresolved references to invalid server paths. Example showing an Unresolved Binding Upgrading to Building Operation 2.0 or higher will also resolve this issue.

Issue There is a performance issue affecting the Infinet bus under an AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Cause Product Support has requested a Trace log with increased reporting for use in troubleshooting the Infinet bus.  Resolution 1. Under the System Tree in Workstation, expand the Modules folder.        2. In the Module folder, under the Trace folder expand the Loggers folder.   3. Under Loggers, navigate to the following modules. nsp.pin.BACnet.Continuum nsp.BACnet.Continuum (EBO versions 2.0 and below only). 4.  Right click on each module to expose the module Properties and increase the reporting level to Trace.     5. Just below the Loggers folder, right click on the Trace Settings folder.   6. In the context menu under Trace Settings, select Get trace log.     The Trace log will appear as a text file in a text editor.  Save the log to an appropriate folder.   Be sure to return the reporting level on all modules to Information once you are finished gathering the logs.   Leaving the reporting level at Trace will fill up the Trace logs with Infinet log entries leaving very little room for anything else. 

Issue Experiencing issues with I/O modules that may include: Backplane failure causing modules to assume wrong module ID Input filtering problems on RTD modules Stability due to electrical noise Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation StruxureWare Building Operation Automation Server I/O Modules Cause The latest I/O module firmware version will correct known issues while also ensuring that the system is up to date and compliant. Resolution The latest I/O module firmware can be located on the Exchange by searching for I/O Module firmware. Each firmware download zip file will contain a ReadMe file that explains what was corrected in that version.  Refer to Upgrading SmartStruxure IO Module Firmware for the procedure to upgrade the I/O module firmware. 

Issue Values are coming into Vista without issue but do not update on the graphics in the Xenta 7XX. Product Line TAC Vista Environment Workstation Graphics Xenta Server 701, 711, 721, 731 Cause If there is a Xenta Server in the database, when connection objects are not used to bind values between a controller and a Menta program in the Xenta Server, this graphic update can occur. It can also be because of the XIF for a device being formatted incorrectly. If the procedure below doesn't solve the issue, refer to LON device can communicate in Vista, but fails in a Xenta Server / XBuilder Resolution There are two options to correct this issue: Re-engineer the XBuilder project to use connection objects between the controller and the Menta program in the Xenta controller. The control task speed of the Menta program in the XBuilder project can be changed to a lower speed setting.

Issue Unable to use a Feature of Power Monitoring Expert due to license limitation.    Environment Power Manager Power Monitoring Expert Cause Open the PME Management console Select Help>About You should see the active License Modules as shown below. You may or may not also see additional features that are part of the 90 day trial.   Resolution Contact your sales representative to purchase the additional licenses

Issue BACnet alarm state doesn't update when the monitored variable triggers the alarm in PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause BACnet alarms require a live device to send alarms to EBO. Since PCT doesn't have any live devices, BACnet alarms don't work in PCT. Resolution The BACnet alarm feature is not supported in PCT.

Issue Browsing between different records in the Security Expert Client is slow. It takes a longer than normal amount of time to see records update. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause There are a large number of unacknowledged alarms being stored in the SecurityExpertEvents database. When the Security Expert Client starts up it will process all of these unacknowledged alarms which can impact browsing the database. Resolution To resolve the immediate problem: 1. Reduce the size of the SecurityExpertEvents database by reducing the overall number of events that will be stored. Setting up automatic event purging and backup helps keep this in check. Under Global | Global Settings | General change the Purge Events older than from the default setting of "Never" to another value from the drop down menu. To backup these events before being purged, ensure the Generate Differential Events Backup option is checked. This is the default setting. 2. If there are more alarms to be acknowledged than can be done manually then contact Product Support mentioning this Knowledge Base Article. Remote access to the site and SQL Server will be required.   To minimize this from happening again: 1. Reduce the amount of events that are setup as alarms. Remove any alarms that are setup for All Events and review any configured alarms to ensure those events are required to be generating alarms. Double check all Inputs and Trouble Inputs to see if they have the Log to Event Buffer option enabled. Not all inputs will require this for normal operation and in some cases having this enabled can result in a large number of unwanted events being logged. This, in addition to an alarm setup to monitor the All Events event filter, is a recipe for disaster resulting in a large number of alarms being generated in a short amount of time. 2. Ensure that a large number of unacknowledged alarms are not allowed to build up over time. Alarms are not able to automatically acknowledged and will stay in the active alarms list until an operator acknowledges them. Operators need to acknowledge alarms on a regular basis. Note that it is possible to batch acknowledge blocks of alarms at one time in the Security Expert Client by doing a multiple selection then right-click acknowledge alarm. Note: If your system has already built up a large number of unacknowledged alarms and you want to quickly acknowledge them all at once to get back to a manageable starting point, then please raise a Support Case with your local Customer Care Centre and Product Support can assist in doing this with a 'one time' SQL Query direct to the Security Expert Database.

Issue Is it possible to command the outputs on an MP-C controller before it has been commissioned in EBO? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause It is necessary to verify the field device wiring and control prior to the MP-C controller being brought online. Resolution The following video demonstrates how temporary outputs can be created and controlled in an MP-C controller without the use of a front end system.

Issue Workplace Tech error POP-UP "Server Busy.... action can't be completed because the other program is busy. Choose 'switch to' to activate the busy program and correct the problem."  when trying to configure communications.   Environment Workplace Tech Tool, revision 5.x  OpenLDV 3.40 OpenLDV 4.0 Cause Possible causes: 1. Multiple versions of Echelon drivers installed. 2. WinPcap may have been uninstalled, quarantined, or blocked. Resolution Only one version of LDV32.DLL should exist on the system and it should be the latest version.  WorkPlace Tech 5.7 and later uses OpenLDV 3.40 or OpenLDV 4.0. Verify the following: OpenLDV 3.40 or later is the only Echelon driver installed in the Windows Control Panel Add/Remove Programs dialog.  If the LonWorks PCLTA-20/PCC-10/PCLTA-10 for Windows is installed, do the following: From the Control Panel, Add/Remove programs, uninstall the OpenLDV driver Uninstall the PCLTA-20/PCC-10/PCLTA-10 for Windows driver. Reinstall the OpenLDV driver. Search the hard drive to locate all LDV32.DLL files on the pc.   Make certain all the LDV32.DLL files found are the same version as is found in the \LonWorks\Bin folder.    Verify the LON Flow Balance still communicates, if applicable. Verify winpcap 4.1.2 installed.  Use the link below to download and install WinPcap, if required.  http://www.winpcap.org/install/default.htm  UNCHECK THE FOLLOWING DURING INSTALLATION, UNLESS YOU HAVE UAC (User Account Control, in Windows 7 and Windows Vista) ENABLED!  If UAC is enabled, the checkbox should be CHECKED!

Issue Supplemental Documentation on the Menta SEQ (sequence) block Environment Menta Cause The document is intended to clarify the inputs and configuration parameters of the Menta SEQ block and when/how to use them. Resolution Click here to download a copy of this document in PDF format Click here to download the example Menta macro   Supplemental Documentation: Menta SEQ   A Brief Overview of Sequence Block The Sequence block is used to start N of M stages based on a percentage input. Each stage is represented by a single bit in the output of the block which requires calculation to determine if each stage is off or on. The Sequence block also provides the ability to rotate the stages, specify a delay between multiple stages activating, and a hysteresis to adjust the activation or deactivation of stages. The Sequence block is ideal for rotating operating stages that have high frequency of change. It is not the proper block to use for run time balancing between multiple stages. Input of the SEQ Block The input expects a 0-100 value where a 0 represents zero stages active and 100 represents all stages are active. Configuration Parameters of the SEQ Block Stages The number of stages to activate at 100% input. Rotate Rotation Flag. If Rotate is set to 0 then the first stage will always be active if 1 stage is required. If Rotate is set to 1 then the first stage to activate will be the first stage to deactivate. Period Time delay(ms) between multiple stages activating. Hysteresis Hysteresis is used to offset the activation or deactivation % for each stage. If the Hysteresis is positive then it will shift the activation % higher by that amount. If the Hysteresis is negative then it will shift the deactivation % lower by that amount. Normal Operation of 4 Stages:    Stage 1 Activation Stage 2 Activation Stage 3 Activation Stage 4 Activation Input 20% 40% 60% 80%  Hysteresis of 10%    Stage 1 Activation Stage 2 Activation Stage 3 Activation Stage 4 Activation Input 30% 50% 70% 90%  Hysteresis of -15%    Stage 1 Deactivation Stage 2 Deactivation Stage 3 Deactivation Stage 4 Deactivation Input 5% 25% 45% 65% Output of the SEQ Block The number of stages active is based on the following formula: Active Stages = ((Maximum Stages +1) * Input) / 100 The number of active stages is then encoded into an Integer as the output of the SEQ block where each bit represents whether each stage is active or inactive. Since this is a single value it must be decoded using expression blocks to detect if each bit is active.

Issue Cannot see third-party LON devices when using the I/A Series Lon Device Manager to find and learn the devices on the LON Network.  The third party devices are known to be defined with a specific Lonworks Domain address. When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers with specific a Lonworks Domain address, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the third-party device. Environment I/A Series R2 (Niagara) WorkPlace Pro UNC 520 Third party LON controllers Cause When a third-party network management tool is used to define and configure / commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Perform the following steps using WorkPlace Pro to configure the LON interface of the UNC and to learn the LON network. Open the Netmgmt page for the Local Lon Device then set the domain length and domainId to match the domain address of the device.  Apply the changes.  (See example here). Open the Properties page for the LocalLonDevice and select the Engineering tab.  Set the subnetId to match the subnet address of the devices.  (See example here). Recommission the Local Lon Device. Use the Lonworks Device Manager to find and learn the devices on the LON network.

Issue AVU2201 Replacement Product Line Field Device Environment AVU2201 Cause AVU2201 obsolescence, replacement required. Resolution The replacement actuator is the MZ300S-24F actuator.

Issue How is the MAC ID for an AS calculated? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause MAC ID for an Automation Server calculation Resolution A Mac address ID of an IP level Automation Server is made up a 48 bits. The first 3 bytes are unique to each vendors organization and has a unique IEEE 3 octet identifier. The last 3 bytes are created by the individual companies and EBO's last 3 bytes are automatically pulled down from a database to a buffer in the product level test equipment where one is assigned for each tested AS, printed at the side sticker and logged in the Trace test report. Example  00-50-06-00-D0-15

Issue WorkPlace Tech revision 5.7.7 installed on a Windows Server 2003, 64-bit machine, receives the following error: Environment WorkPlace Tech Tool version 5.7.7 Windows 2003 Server, 32 bit or 64-bit Windows 2008 Server, 32 bit or 64 bit (multiple processors) Cause WorkPlace Tech Tool (WPT) is not supported on computers with Windows Server operating systems, nor on computers with 64-bit operating systems. Resolution Install on an approved hardware platform, per the Installation Instructions.