Building Automation Knowledge Base

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 How to create a Binary Input or Digital Input on a MPM controller Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause When a Binary Input is created, the object does not work. There is no documentation on how to create a Binary Input Resolution In order to use a Binary Input, both the BI object and the corresponding Analog Input AI object must be added from the object list. For example, if you need to use BI3 with a dry contact, you will also need to add AI3 and toggle its "input type" to Ohms, then save the object. You also need to keep the object in the object list. With regards to “Input type” for the Binary Inputs: (the "input type" property is in the AI object) -When set in Volts, anything >= 2VDC will be considered a 1 status.                                    anything < 2VDC will be conspired a 0 status. -When set in Ohms, anything < 10kOhm will be considered a 1 status.                                      anything >= 10KOhm will be considered a 0 status. Note: When "Input type" is set to ohms, a dry contact must be used for the BI to work properly. BO1 and BO2 of the MPM can be used for example, but not the relays of the TE2 as they are not dry contacts by design.

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 can I control a dual duct VAV box with Xenta controllers? Environment Xenta 102-AX Dual Duct heating/cooling Cause The Xenta 102-AX is an application specific controller designed to vary the volume and outlet temperature of a single terminal unit. It does not, by default, control a dual duct, where a constant source of cold air and hot air and delivered in separate ducts. Resolution You could conceivably use a single Xenta 102-AX with the airflow pickup on the discharge of the box instead of the inlet. Then connect the hot deck damper as a 2-out PWM heat stage. A more elegant solution is to use a pair of Xenta 102-AX controllers. One 102-AX is connected to the cool deck and setup normally. Either its heating airflow setpoint is set to match the cooling low flow or heating airflow is set to 0 if you wish the cool deck to shut off in heat. The "Effective Setpoint Source" must be set to "Norm of Heating and Cooling Setpoints" so that the setpoint sent to the hot deck controller will not bounce from heating to cooling when room conditions change. For this reason, it might be preferable to use an STR-202 so that there is no digital display to confuse the occupant. The second 102-AX is connected to the hot deck, space temp is bound from the first and nvoeffectivesp is bound from the first to nvisetpoint of the second. Configure input 1 as a duct temp and connect a 4.7Kohm resistor from it to ground. This will simulate a duct temp of 110°F and keep it in warmup mode. As with the cool deck, you have a choice whether to set the warmup low flow to 0 or to some minimum position. Set your occupied setpoints to the same values as the cool deck controller. (It's actually using them in the setpoint calculation, but for simplicity's sake, set them the same. For a more complete description, consult the reference manual concerning nviSetpoint.) You should also bind nvoOccupancyStatus from the cool box to nviOccCmd on the hot deck box. That way if someone puts the box in to after hours override, they'll both operate. As mentioned before, the room sensor (STR-200/202/250) is connected to the cooldeck controller. You'll need to connect 3 conductors to a 1/8"TRS jack to the hotdeck controller in order to connect the MSTAT for calibration purposes. Otherwise you'll have to crawl into the ceiling to connect it. This arrangement is based on having airflow sensors on the inlets of both the cold and hot deck.

Issue The calectro smoke detektor has too long pipe to fit Environment Calectro Smoke detektor Venturi pipe Cause The Venturi pipe is long, but also possible to cut Resolution You can cut the Venturi pipe to size but you must only cut it from the end that does not have the sleeve. See Installation instruction for more information.  

Issue Is there a limitation to the size the database can be on a Single User system in Continuum? Product Line Andover Continuum Environment Single User Continuum system MSDE database Cause Microsoft has put a limitation in the size of the MSDE database. Once you hit this limitation your Single User Continuum system will not operate properly. Resolution The size limitation is 2 Gb. It may be possible to recover after hitting this limit by removing un-needed log entries from the database, but this is not always a guarantee you will be able to recover the database. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation. From this point you can remove any unwanted logs and shrink the database. Then you can back up the database and restore it back to the Single User system. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation and convert the Single User system to a LAN installation. Finally if all the above do not work for your system you will have to restore from the last known good backup of the database. See Microsoft Database size Limitations and Continuum for SQL Express information.

Issue Sub Device unable to come online when added to an SSC Controller on a system. When the controller that is offline is selected the save option is not available. Product Line Access Expert Environment Access Expert in Cloud or Premise Installations Microsoft Windows 7, Windows 8, Server 2012, Server 2014 Cause The controller is not  configured correctly (MR50) The controllers IP address is incorrectly configured,  or is not saved or made active on the system. (MR 51E) Resolution To resolve this, the following steps need to be followed: Add the interface type to the SSC Configure the interface for DHCP, Static or MAC address (MR51e) Once complete, select Save or Save & Close to save to the controller If multiple devices are being added, follow previous steps 1-3 above then:  Open up the Live Monitoring Window to check the status of the controller If the devices show offline, Right Click on the controller and select Reboot The Live Monitoring Window will show what is actually being sent to the controller Once completed the status will change to reflect what state the controller is in If correct it will be Online (Green), if not check the configuration again

Issue How to sound a buzzer when a Request To Exit (REX) button is pressed on a Continuum Access system? The inputs to a door are not defined as regular Infinity inputs so how can they be programmed by Plain English programming? Environment ACX57xx (ACX5740, ACX5720) and AC-1 IOU modules (AC-1, AC-1A, AC-1 Plus) Cause When engineering an access control project, there is sometimes the requirement to sound a buzzer or turn on a light when the door is unlocked, or when a Request To Exit button is pressed, as the input points used within the door object configuration are not defined as a regular Infinity Inputs, so how to achieve this functionality? Resolution To use a Request To Exit (REX) switch on any of the ACX controllers or AC1 Modules:  It has to be a supervised input wired with the appropriate resistors in one of the 6 standard configurations defined in the installation guides (All available on the Extranet). You can not use a simple digital input switch without resistors. Incorrect circuitry or missing resistors will result in a Trouble indication on the door. The REX input is not a regular Continuum input point as it is defined within the door configuration, as it is not a Infinity input point directly accessible from Plain English but can be read via the "ExitRequest" attribute of the door. To sound a buzzer from the from the door there are 3 options: Use the existing door output and slave a buzzer circuit from the output that drives the Magnetic lock, so will sound when the door unlocks. If you want the buzzer to sound when the REX button is pressed then use a button with a 2 pole switch (2 separate contacts): Wire one to the REX input with appropriate resistors. Wire the other switch to a spare Input Configure it as either a Digital input or a Supervised input with resistors. This point can be used in your PE programming to drive the buzzer output. The third option is to use a Plain English program to read the "ExitRequest" attribute of the door and turn on an output for a defined time. The ExitRequest attribute may only be on for a short period of time so the program must be constantly looking for this attribute to change as well as keeping the controller Scan time low.  

Issue After launching WebClient logon screen appears but attempt to logon results in "Webclient is unavailable"  Product Line Andover Continuum Environment Windows Vista Windows 7 WebClient Cause Incorrect Internet Information Services (IIS) configuration. Resolution 1. Open Internet Information Services Manager 2. Expand the Computer Name in left pane and click on Application Pools in treeview 3.  Select DefaultAppPool and click Set Application Pool Defaults 4. In Application Pool Defaults dialogbox select Identity under Process Model. A selection control should appear in the second column. Click this button 5. Under Built-in account select Network Service in the dropdown listbox. Click OK 6. Click OK button in Application Pool Defaults dialogbox

Issue Some TGML javascript functions that work correctly in Vista Workstation stop working in Vista Webstation or break graphic performance. The following errors have occurred. Please correct these errors and/or contact the system administrator. An unexpected exception has occurred: Object reference not set to an instance of an object. System.NullReferenceException at TAC.WebStation.Modules.Graphics.TgmlLinkPage.CreateLinkData(TACOSTgmlPicture tgmlPicture, String oID) at TAC.WebStation.Modules.Graphics.TgmlLinkPage.GetLinkList(TACOSTgmlPicture tgmlPicture, String[] oIDs) at TAC.WebStation.Modules.Graphics.TgmlLinkPage.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Product Line TAC Vista Environment Vista Webstation 5.x.x Graphic Editor TGML 1.x.x Cause Due to the differences in Vista Workstation and Vista Webstation being viewed through internet browsers some TGML javascript functions will not function, function as expected, or cause your TGML graphic page to be unusable resulting in a Java error message. Resolution To make TGML graphic pages compatible with Vista Webstation remove the following functions: getDate getYear getMonth getDay getHour getMinute getSecond To make TGML graphic pages compatible with Vista Webstation adjust the unexpected behavior of the following functions: setTimer - this function cannot be used in the OnDocumentLoad event getStatus - this function will always return a value of 2 invoke - this function can only be used on links, not bindings.

Issue Should managed switches be set to half duplex or full duplex? Prorduct Line Andover Continuum Environment Continuum Cyberstation 2nd Generation Controllers BCX 4040, 4000, 9640 NC2 9680 ACX 5740, 5720 1st Generation Controllers CMX 9924 CX 9900, 9901, 9940 Cause Configuration for managed switches. Resolution Most sites will have managed switches set for Auto Sensing 10/100 For sites that must use a designated configuration, our 1st generation controllers communicate 10 half duplex while the 2nd generation controllers communicate 100 full duplex.

Issue SigmaX was installed but will not open. Sigma will not seat a client and BAS 2800+ is looking for a dongle. Product Line Satchwell Sigma Environment Sigma SigmaX BAS 2800+ tools Cause SigmaX requires an unlocking code. Resolution SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded.   With the release of SigmaX 7.0.9 the following procedure is no longer required and will not be available in 2017 If you are a Schneider Electric employee you register your PCID number via Lotus Notes, or use the SigmaX Registration Portal if you do not have Lotus Notes. Finding PCID: The SigmaX PCID number for your SigmaX installation is provided by running t.he "RegSigmaX.exe" program (C). The "RegSigmaX.exe" program (B) is located under "C:\SigmaX\Bin" (A).     For Schneider Electric employees with Lotus Notes The engineer must be on the Schneider Electric network via VPN or office to be able to follow the steps below. From the Lotus Notes client, From the top menu, choose File then Application or Ctrl + O to bring up the Open application dialog box.   Click on the down arrow to the right of "Look in:" text area and choose AAGB0010.GB.Schneider-Electric.com/A/SVR/Schneider from the list.  If it doesn't exist, then either type it in or select another server and modify the entry. The list in the scrollable window should look like the picture above.  Scroll down the list until you see a directory called "apps".   Double click on this entry.  Scroll down the new list until you see "Sigma X Registration 2015" Select the entry and then click on Bookmark.  From the next dialog box, choose "Bookmark bar" from the "Add to" list. See below.     will appear in their bookmark bar or Open list.  To access the application, click on the icon.     For partners and Schneider Electric employees without Lotus Notes 1. Go to https://sigmaxregistration.schneider-electric.com to register all new SigmaX code   2. Log in If you do not have access you will need to register using one of the options provided on the landing page If you do not know your access details, you will need to communicate with your local sales representative   3. From the left hand side, select "Sigma Registration"   4. Click "Continue" to continue to the registration page   5. Enter the information required A - Check the correct name is displayed. B - Check the correct email address is shown, edit the address if it is incorrect. (The unlocking code will be sent to this email address) C - Enter your office region. D - Add the product identity number. E/F - Select whether the unlocking being requested is either an addition or a replacement. G - You can leave a comment regarding the request. H - Submit the request.   Once your unlocking code has been approved (normally within the hour), you will receive an email with your new unlocking code. Once you have registered your PCID number, you should receive an email each December with the next year’s unlocking code. Download the instructions as PDF

Issue Which Continuum controllers support RAS via modem connection? Environment CyberStation CX9900 CX9940 CX9680 CX9640 CX9200 CX9924 Cause Not all Continuum controllers support modem connection. Resolution The access point for a remote site is the controller that is configured with a modem that is used to establish a communication link with the remote CyberStation. Only the following Continuum controllers can act as access points for remote sites. CX9900, CX9940, CX9680, CX9640, CX9200, CX9924. Note that other controllers communicating with the access point controller via ethernet can fully participate in RAS communications as the access point controller will route messages to/from its peers.

Issue Sigma IC-GEN 4.05 SEB and supported operating systems Environment Sigma IC-GEN release 4.05 SEB Cause New installation of IC-GEN and customer wants to know the latest version and its supported operating system(s). Resolution The latest version of Sigma IC-GEN is Sigma IC-GEN 4.05 SEB. Release 4.05 SEB IC-GEN provides rebranding to Schneider Electric. There are no other changes except for new build and release numbers. This release is shown as Sigma IC-GEN Build 3.43.07 in the installer, uninstaller and ‘About’ box. This release supersedes the previous Release 3.17 for IC-GEN (shown as Build 3.34.12 in the About box and Build 3.34.24 when uninstalling). This version is supported to run on Microsoft Windows XP Professional (32-bit) and Microsoft Windows 2000. (Microsoft Windows Vista and Windows 7 are not supported) Refer to 'Sigma Release 4.05 SEB IC-GEN' release notes for details. The IC-GEN 4.05 SEB software can be downloaded from the Exchange Extranet. Once logged on, go to 'Products' > 'Satchwell' > 'Sigma' > 'Downloads' > 'Upgrades and Software'. The release note can be downloaded from 'Products' > 'Satchwell' > 'Sigma' > 'Release Notes' > 'Options'.

Issue Public values, inputs and outputs of a Menta object defined in a Xenta 700 XBuilder project are displaying their values in Workstation as [Invalid Address]. When the value is double- clicked, the following error appears: Error in property Value. Read operation failed. Product Line TAC Vista Environment Vista Workstation Xenta Servers Xenta 701, 711, 721, 731 XBuilder Menta Cause The Menta object is not connected to a task. Therefore the Menta application is not being executed. Resolution In XBuilder, generate the project. Check the output window Generate tab for a warning that states "This Menta Object is not connected to a task" Double click the warning. The offending Menta object is highlighted. Drag and drop the Menta object into a Control Task folder in the Network Pane > TAC_Xenta_7xx > Control Tasks Regenerate and send the project to target. Menta object values should now report valid values.

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the statistics from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)