Building Automation Knowledge Base

Issue When configuring a SmartConnector, the custom assembly cannot be seen in the Add Processor Configuration tab.   Product Line EcoStruxure Building Operation Environment Microsoft Windows Server 2012 and newer, Windows 10 Cause Microsoft Windows Server Unsigned or unknown certificates Some files need to be "unblocked" after download in order to avoid security warnings from tools like Visual Studio about potentially unsafe content.   This is because the dll’s for the custom processor have been downloaded from an internet based source.   Otherwise, all the required dll’s for the solution may not be available in the service installation directory (normally “C:\Program Files (x86)\Schneider Electric\SmartConnector”). This information can be seen in the SmartConnector log file. SmartConnector will log an error when going to the point of adding a new processor if it can’t find a reference. It will point to the assembly which is missing. Microsoft Windows 10 The service needs to be restarted once the dlls for the custom processor have been added in the service installation directory. (“C:\Program Files (x86)\Schneider Electric\SmartConnector”) Resolution Microsoft Windows Server range To "unblock" a file, Right-click it in Windows Explorer Choose Properties from the context menu Click the Unblock button in the lower right-hand corner of the resulting dialog Hit OK or Apply Important: ZIP files should be "unblocked" before their contents are extracted. Note: Depending on the security policy level on the system, you may need to perform the same action for the DDLs once uncompressed. Microsoft Windows 10 To restart the service by Opening the service windows Select the SmartconnectorService entry Either click on the Restart button, or Stop then start

Issue How to place an order for more LNS credits to allow LNS plug-ins to work and to be able to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available.   To order more LNS credits: Go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, Click the Copy to Clipboard button to copy the PC key generated by LNS Server License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard. Click next and paste the application key into the field titled "Application Key". Click Finish.

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue Access Denied NO access at the door Product Line Access Expert Environment Win Server 2012 R2 and above Cause 1) The cardholder does not have sufficient Access Levels assigned. 2) The Max access levels has been reached by the intelligent controller. 3) The access levels were not successfully downloaded to the controller. Resolution To resolve this, the following steps need to be followed: 1. Ensure that the access levels contains a door group which consists of the trouble reader. 2. Check that the person has the correct access level assignment, 3. Try saving the access level again so that it is pushed to the controller. 4. If possible, issue a reboot command to the intelligent device to ensure database synchronization. OR if the system database limit on access levels has been reached, take the following steps. Verify the user has permissions on the Role Go to the General Configuration Select System Settings Select the Hardware Tab on the bottom Change the Max Access Level to a higher level than the default (100). Save and Reboot the controller for the changes to take effect

Issue If a Xenta 913 with SNVT(s) is added as a Lon device to an Automation Server Lonworks network the commission process fails in the last step with error 0 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server TAC Xenta 913 TAC Xenta 700 Cause This is a bug in the Xenta Server firmware. Resolution This issue will be fixed in Xenta 913 firmware version 5.1.9, however  hotfixes have been made for 5.1.8 and can be requested from PSS (TACXenta913-5.1.8.15 and TACXenta700-5.1.8.47). Note: All data will be lost in the Xenta Server when applying the hotfix.

Issue The Drayton Theta YBM3 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBM3 Cause The Drayton Theta YBM3 Valve Body / Actuator assembly is obsolete.> Resolution OVERVIEW The Drayton Theta YBM3 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM3 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM3 Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  The YBM3 Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here. N.B. The YBM3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M4 – M1 made to M4 when YBM3 Fully Closed (230Vac) Terminal M5 – M2 made to M5 when YBM3 Fully Open (230Vac) Where external wiring is connected to YBM3 Transfer Switch Terminals M4 or M5 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here. Where external wiring is connected to YBL3 Terminal M4 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 230Vac power source Terminal S2 (Normally Closed) - connect to 230Vac device previously connected to YBL3 Terminal M4 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M5 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 230Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 230Vac device previously connected to YBL3 Terminal M5   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM3 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

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 How to configure the relative path permissions Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause Relative path permissions help configure the path permission for multiple modules (i.e.100 AS-Ps) or many different folders Resolution Here's how to give 'read-only' analog value permissions for 2 separate folders: 1. Go to Relative path permissions. Select the type of permissions desired (Full permissions for Analog Value/ NO permissions for Digital Value) 2. Go to the Local Account Group and select the Permissions tab. Under Path Permissions, add (+) the created path permissions to the desired folders. 'Folder' and 'Folder 2' are selected to have the same path permissions. Save and apply configuration.   3. When viewing the system tree, both 'Folder' and 'Folder 2' have read permission for Analog Value

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.

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 Self-Registration Error while installing Remote Workstation (some of the "dll" files are not installed). The following files did not self-register or unregister. Environment TAC Vista 5.0.X Remote Workstation Cause When uninstalling the TAC Vista Remote Workstation some of the "dll" files will not un-install from "TAC Shared" folder (Find the TAC Shared folder in "C:\Program Files\Common Files). Due to this, while reinstalling the Remote Workstation pop-up an error-"Self-Registration" and few "dll" cannot install, then the Installation terminates. Resolution Uninstall the Remote Workstation. Delete the TAC Shared folder from C:\Program Files\Common Files Reinstall Remote Workstation. Note: Install .NET Framework 2.0 before installing the Remote Workstation software.

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.

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 Services for assistance. Issue Not possible to see live values in a Xenta 700 Menta program from web interface or TAC Vista Can't see Menta online values in Xenta Server Control Applications graphical view The Menta application displays fine, but it's not possible to see the live values (true/false et c) Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause This is an uncommon error and the cause is not known, however it may occur when copying a HFB block within or between X700 Menta applications. Resolution In the Xbuilder projects folder, find the file [project name]\TargetImage\configdb\menta\mentablocks.xml and open it in Internet Explorer. Search for Menta blocks that have CodIndex='0' and note (copy) the GUID of those (for example 3C02F735-E375-45d0-99A8-6CFC402DE5D0). Now open the file [project name].xbp518 (in the project's root folder) with notepad or similar and search for these GUID(s). Note the Menta block(s) name (before the GUID) and the menta block type (just after the GUID), for example HFDI. Close all previously opened files (no save). Open the Xbuilder project normally, and open/edit the troublesome MTA. Search for the menta block(s) name and check that it also is the same block type (most likely a HFB block), then delete it. Create the block again with the same name (no copying from similar blocks!). Save and download the project to the X700. Now it should work fine viewing the live values in Control Applications. If still same issue, redo step 1-7, there may be other blocks with CodIndex='0'.   Note: If you can't see the Menta application at all it's likely a different error, see Can't see the Xenta Server Menta program online in the browser.

Issue Error importing a StruxureWare Building Operation export file. Below is an example of the error.  ERROR: Import failed to commit changeset transaction with an exception. RecoverableException: /home/ci/ci-build/rb-rb-1.8.1-system/source/server/nsp_servers/csc/changesetmanager/source/ChangeSetTransaction.cpp(1442) Invalid Data Error: File_Extension_Not_Permitted (0x10048) in module Security_Manager(74). "Not permitted to store the file "htgseqintro.wmv" with the current Document Policy." - Stack Environment StruxureWare Building Operation 1.8 Cause The export file contains a document file extension that is not permitted in the Document Policy Permitted File Extensions Resolution The file extension has to be added to the Permitted File Extensions list. See Adding a File Extension to the Permitted File Extensions List on Web Help. For the error example shown in the issue of this article, the extension wmv has to be added to the Document Policy Permitted File Extensions. list. 

Issue Where to find the domain ID of a LonWorks Network underneath a LonWorks Interface in a Building Operation network. The domain can also be changed in this same location. Product Line EcoStruxure Building Operation Environment Building Operation workstation Cause If the domain ID of a LonWorks network needs to be changed or known for some reason it can be done through the properties of the LonWorks Network. Resolution Right click on the LonWorks Network underneath the LonWorks Local Interface. Click Properties. Click on the Advanced tab and look at the Domain table for Network Interface. The value in the first row of the ID column is the domain ID in decimal form. In order to change the domain ID, use the Addressing entry field "Domain ID Length" to enter the new Domain. Click OK.

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 When a XIF file contains NCI's (SCPT's and UCPT's) default values (NVVAL) must be described in the XIF file. In some cases if NCI's are present, but some or all NVVAL initializers are missing commissioning the device will fail. For information regarding NCI's that are part of a FILE definition, please refer to Understanding the FILE part of a XIF file. Product Line EcoStruxure Building Operation, TAC Vista Environment LonWorks XIF Cause When commissioning a device default values to configuration variables must be assigned. If the tool (TAC Vista, SmartStruxure, LonMaker, NL220) does not know what default value to assign, it can cause an error. Resolution Make sure all NCI's have proper initializers defined. Read XIF file - NVVAL initializers.pdf guide as reference. Here is an example of a NVVAL section: VAR nciHrtBtRcv 2 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,48; 107 * 1 4 0 2 0 0 VAR nciHrtBtSnd 3 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,49; 107 * 1 4 0 2 0 0 VAR nciLocation 4 0 0 0 1 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,17; 36 * 1 4 0 31 0 0 VAR nciDeviceName 5 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,6\x80,3; 36 * 1 4 0 31 0 0 NVVAL #VAR nciHrtBtRcv \x00,\x00 #VAR nciHrtBtSnd \x00,\x00 #VAR nciLocation = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00 #VAR nciDeviceName = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00

Issue TAC Vista Web Settings > Preferences > Login and Logout > Automatic Logout (An inactive user is automatically logged out after a specified period of time) Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Set the logout time to less than 5 minutes Set the logout time to more than 30 minutes. Customize the logout time to something other than specified intervals.  Environment Vista 5.1.5 Webstation TAC Vista Web Settings Cause Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Resolution Navigate to C:\Inetpub\wwwroot\TACVistaWeb515 Open the file web.config. Use, for example, Notepad2 (Do not use wordpad as it formats the file differently) Search for "sessionState" Change the "Timeout" for the SessionState to the desired logout time in minutes Save the file 

Issue Satchwell MBX 3-port Rotary Shoe Valve Body Open / Close status determination from Spindle position. Environment Satchwell MBX 3-port Rotary Shoe Valve Body installations. Cause Satchwell MBX 3-port Rotary Shoe Valve Body is installed in pipework and Open / Close status cannot be determined by observing Valve Body Shoe positions. Resolution The Satchwell MBX 3-port Rotary Shoe Valve Body Spindle protrudes through the side of the Valve Body. The position of the Valve Body Shoes may be determined by observing the angle of the Slot in the end of the Valve Body Spindle. If the slot is ( \ )  then Valve Body is fully open to Port 2 If the slot is ( / )  then Valve Body is fully open to Port 3 If the slot is ( | )  then Valve Body is half open to Port 2 and half open to Port 3 With the Spindle Slot in the 10 o'clock position the Valve Body is fully open to flow and fully closed to bypass. With the Spindle Slot in the 2 o'clock position the Valve Body is fully open to bypass and fully closed to flow.   With the Spindle Slot in the Vertical position the Valve Body is half open to flow and half open to bypass.   Please check the latest catalog for current equipment.

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 Unable to read any public signals from TAC Xenta 300/400/280 in a TAC Xenta 511, but SNVTs from TAC Xenta 100 controllers are fine. Environment Xenta Programmables Xenta 511 Xenta 100 series ASCs Cause The TAC Xenta 511 is not a member of the TAC Vista group. Resolution Go to the System plug-in Choose LNS Network >Create group bindings.