Building Automation Knowledge Base

Issue Triggering a default value to internal AO points when the value is reset to 0 Product Line TAC INET Environment I/NET Seven Event Sequence 0 Cause #A controller will run Event Sequence 0 any time one of these changes occurs: Power up Controller reset Database restore Internal AO point values will default to 0 (zero). If this AO point is used as a setpoint in a DDC loop, this could cause issues. Resolution Option 1 Use Event Sequence 0 to set internal setpoint values to a default value following power loss, reset, or restore. When connected to the controller, navigate to Edit > Controller > Event Sequences Click on Seq 0 and choose "Add." Sequence 0 is reserved to run on reset. Add an action Action: Output (or Output with lock) Delay: Defaults to 0 Point: AO that is used for the setpoint Skip/Value: Desired default setpoint value. Below is an example of what an Event Sequence 0 looks like of an Internal AO used as a setpoint. In this example anytime Event Sequence 0 runs, it will output a value of  75 degrees. Option 2 Open up Event Sequences. Add event 0 to the list. Event sequence number 0 runs at a power up, after a reset of controller power or a database restore of the DCU. Modify event sequence 0. Put every interanal "AO" setpoint in this event with a default value that is safe to operate at. 

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue Blank screens seen when starting WorkStation, Device Administrator, License Administrator and Software Administrator Product Line EcoStruxure Building Operation Environment Windows 10 Cause Graphics Card Driver Issue In this case there was a "Intel(R) HD Graphics 4600" graphics card (this is the Intel Core i7-4790 CPU built-in graphics card) and there was a dedicated "NVIDIA GeForce GT 630" graphics card which was in the end also the culprit because it was the one with the outdated graphics driver, the Intel one didn't required an update. Resolution Update Display Drivers Fix for Windows 10 Professional Version 1803 below Start Computer Management Go to Display adaptors and update driver  Search online for drivers  Verify with second run after driver update if newest driver is installed 

Issue User can’t disable the fan in heating mode Product Line EcoStruxure Building Expert Environment   SER7000 | SER8000 Cause  Misconfiguration of the thermostat Resolution SER7300 In some application, the device may control baseboard heat or different controls and the user may want to stop the fan in heating mode. The user shall set the Pulsed HT parameter to ON and Fan Cont to Off Auto and this will solve the issue. SER8300 The user shall set Fan Cont to Off Auto and this will solve the issue.

Issue Wind Up Inhibit WUH Product Line Satchwell Sigma Environment BAS BAS2000 BAS2800 BAS2800+ Sigma Cause In Sigma a control object is displaying WUH as reason for state (RFS). However, it cannot be found on the objects attributes in Object Editor Resolution The site was likely to have been upgraded from BAS. In BAS, the Wind Up Inhibit (WUH) was used to prevent Control objects from continuing to operate (the integral action would continue to act and increase or decrease the control output) when the plant was in an 'off' state. In Sigma, WUH is no longer used, therefore there is no reference to it within the object when edited. However, during a BAS to Sigma upgrade, the reference is retained and then becomes inaccessible. The controller will display WUH as a reason for state when the control object is displayed in Sigma or EBO. To correct, record the parameters and delete the control object, re-create and restore the same parameters.

Issue When you view a Xenta Log through Vista you get estimated values in the Log. Product Line TAC Vista Environment Vista 4.x.x Vista 5.x.x Cause If the site has many Xenta logs in 200,300 or 400 controllers you maybe exceeding the limit for trend uploads to Vista. The maximum limit is 4 uploads of Xenta logs per minute to Vista. If you exceed this value estimated values may appear in the Xenta logs. Here is a link to a white paper description on this topic TAC Xenta Trend Logs Whitepaper Resolution Here are some steps to check if the estimated values are caused from excessive Xenta trend upload.   Calculate the amount of uploads that are occurring in the database. As an example if a Xenta log is set to store information in the controller for 1 hour and upload at 80% full. This equates to 0.8 uploads per hour or 0.013 uploads per minute. If you work out this rate for all the xenta logs in the database you can then calculate how many uploads are occurring per minute. To extract all the Xenta Logs in the Vista database follow these steps also shown in the video. From TAC Vista workstation select View and then Search from the toolbar. select the browse option for the field "Type of devices or objects" Expand the heading labeled Files. Expand the heading labeled Trend Logs under the Files heading. Expand the heading labeled Trend Log Vista under the Trend Log heading Check the Trend Log Xenta box Select OK In the Property value dropdown list select the" Log size byte " option. This is the Xenta Log duration in seconds. Select the search Button The search results now show all the Xenta Logs. You may need to uncheck the "interrupt search if more than 1000 results" to capture all Xenta trends In the Search output Pane right mouse click and select "Additional properties" Expand the list and select "Retrieve at % Full option" The Search results then show all Xenta trends with Xenta Log duration and retrieve % full. Copy this list in Excel and calculate the uploads per minute from this Database. Below is an image showing the data pasted into Excel, displaying the equation to calculate the upload per minute value per log:  If you find your total "uploads per minute" exceed 4 then reducing this may remove the estimated values. Some ways to do this are. Extend the Xenta log storage time in the Xenta device if memory permits. Change the upload percentage to a greater number if it has been decreased below 80%  Increase the Xenta sample rate which will allow for the Xenta storage to be extended as in point 1.

Issue Configuration help for doors on a 1284, 7920, or 7910 Setting up Access Control on an SCU or DPU Can’t remember if Dip Switch 7 is up for the Card Number equals Individual Number without a MIP on the DPU or was that Card Translation Checked box the issue Product Line TAC INET Environment I/NET Seven Access Control SCU 1284, DPU 7920, DPU 7910 Cause Configuration errors or failure to remember how to properly configure the door editor Resolution SCU 1284 Yes → Large Number Format Yes → In Door Editor, CHECK Using Card Translation     ↓No   ↓No             Card Number equals individual scheme Yes → In Door Editor, UNcheck Using Card Translation     7920 Yes → MIP Board Yes → Using Large Numbers Yes → In Door Editor, CHECK Using Card Translation ↓No   ↓No   ↓No             In Door Editor, UNcheck Using Card Translation         EPROM Yes → Large number format Yes → Dip Switch 7 on         ↓No             Card Number = Individual Number Yes → Dip Switch 7 off 7910 Yes → EPROM Yes → Large number format Yes → Dip Switch 7 on         ↓No             Card Number = Individual Number Yes → Dip Switch 7 off

Issue A Niagara G3 station (version 3.5.25) reports the following error in the Application Director Output (full text version of error): ERROR [10:41:43 09-Mar-12 CST][sys.engine] Cannot start component: false {ok} javax.baja.sys.IllegalNameException: Illegal name "booleanSwitch.invalidInSwitch".    at javax.baja.naming.SlotPath.verifyValidName(SlotPath.java)    at javax.baja.sys.BFacets.make(BFacets.java)    at javax.baja.status.BStatus.make(BStatus.java)    at javax.baja.status.BStatus.make(BStatus.java)    at com.tridium.kitControl.util.BBooleanSwitch.onExecute(BBooleanSwitch.java)    at javax.baja.control.BControlPoint.doExecute(BControlPoint.java)    at javax.baja.control.BControlPoint.fw(BControlPoint.java)    at com.tridium.sys.engine.EngineUtil.descendantsStarted(EngineUtil.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java) Product Line TAC IA Series Environment Niagara G3 Cause There is a known issue with version 3.5.34.2 of the kitControl module:  An error occurs when "null" is used as the value for "inSwitch" Resolution Upgrade to version 3.5.39 of the kitControl module.  Click here to download a copy or visit niagara-central.com (downloads).

Issue Unable to utilize auxiliary contact on SE7000 Product Line EcoStruxure Building Expert Environment   SE7000 Cause Misunderstanding of wiring and configuration steps for the auxiliary output Resolution SE7600 The Aux contact will provide 24 Vac to end devices such as; exhaust fans, valves, economizers, pumps…The contact will operate in conjunction with occupancy command of the thermostat. SE7200 | SE7300 The auxiliary output on terminal BO5 terminal 6 and BO5 terminal 7 is a dry contact that require 24 Vac loop to operate. The output will operate accordingly to configuration and control end devices. Auxiliary contact function and configuration

Issue Connection details for the MZ20A / MZ20A-R actuator. Product Line Field Devices Environment MZ20A-R Wiring Connections Cause How do the cable colours relate to the connection numbers on an MZ20A / MZ20A-R actuator? Resolution The MZ20A / MZ20A-R actuator connection details are shown below.   For the actuator data sheet please click .HERE

Issue The standard opened Unifact Pro stencil provides items for BB83 range of Unifact Pro controllers and does not provide items for older Unifact Pro range. Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma Environment VisiSat NCP Palm Unifact Pro Cause As standard the automatically open stencils do not provide items for the older BB*2 Unifact Pro range. Resolution The current range of Unifact Pros are presented in the standard Unifact Pro stencil. The obsolete Unifact Pro range (BB*2) are not presented in this stencil, a different stencil needs to be added, to provide the older BB*2 Unifact Pros, before there available to use on the drawing. Visio 2003/2007 Go to the Visio menu Click File Click Stencil Click Open Stencil Navigate to C:\Satchwell\Binary\VisiSat\EN\Visio Select the Obsolete.vss stencil You will then have the opportunity to choose one of the older range of Unifact Pro controllers. Visio 2010 Under shapes click More Shapes Click Open Stencil Navigate to C:\Satchwell\Binary\VisiSat\EN\Visio Select the Obsolete.vss stencil These stencils are installed during the VisiSat installation process. If for whatever reason your computer no longer has this file, to save you reinstalling VisiSat, you can download a copy of the VisiSat 2.1 Build 196 (200, 201) obsolete stencil from here. You can store the stencil anywhere on your system and use it, VisiSat's default storage locations is under “C:\Satchwell\Binary\VisiSat\EN\Visio”

Issue PSI / XPSI Revision 4.0 will not tunnel, nor will it connect via modem. Product Line TAC IA Series Environment PSI / XPSI Revision 4.0 Cause Not supported in this release. Resolution Upgrade to PSI / XPSI Revision 4.1, which the file PSIv4.10.zip is available for download on The Exchange Download Center. Click here to see the Release Notes included in the zip file.

Issue Having issues integrating an EM4300 Zigbee power meter with an MPM Product Line EcoStruxure Building Expert Environment Multi Purpose Manager (MPM) EM4300 Cause Procedure only available in Building Expert Guide Resolution In order to establish communication with the EM4300 Zigbee power meter, the following procedure must be followed: 1. Login to Building Expert. 2. In Explorer tab, click Add Devices. A new window opens. 3. Select EM4300. 4. Click the Add Devices button. Building Expert automatically adds an EM4300 Device to your project. 5. In the Explorer tab select the ZigBee Configuration (ZBC1) object. 6. Click on Edit Settings and check the Treat Extended Network ID as a Hexadecimal box. Note: Validation of the Extended Network ID field changes based on this checkbox. For the EM4300, the Extended Network ID is a 16 digit hexadecimal string, where the last 8 characters must be precisely 04015E10 and the first 8 characters are user-defined. Note that the first 8 characters must be unique from one ZigBee network to the other if using multiple MPMs configured as ZigBee Coordinators in the same deployment or building. Note: The “Treat Extended Network ID as Hexadecimal” box must be checked. Note: Ensure the Stack Profile used is ZigBee Pro and the selected Security Profile is Home Automation. 7. In the Devices pane, select the EM4300. 8. Click on the ZigBee EM4300 Configuration (ZEM1) object. 9. Click the Bind button. 10. Once the device appears in the dialog window, select it and click on the Bind Device button 11. The table now displays the binding information of the device. 12. Select the required points and click Save. Note: Selecting a point automatically checks the COV checkbox. The COV boxed are non-editable. Commissining multiple EM4300 devices: When integrating multiple EM4300s and if you notice that the EM4300 device has joined the wrong network, you have the ability to remove it and make it join the correct one. Follow the procedure below. 1. In the Explorer tab Select the ZigBee Discovery (ZBD1) object. 2. Click the Scan button to find devices. 3. The table below will list all the discovered ZigBee devices, specifying whether or not they are bound.

Issue "Database error. (Subsystem: LNS, #25)[DB#-2506]" After clicking OK there may be another error: "The global database is not open. (Subsystem: LNS, #64)". When the Echelon LonMaker Design Manager opened, there is nothing in the Database Name field. Product Line TAC Vista Environment LonMaker Vista LNS Cause This error can occur when ports that the LNS Database is trying to use are already being used by other applications. The ports in question are 6001 and 6002. Resolution To check which application is using these ports, use the following DOS command: netstat -bn Once you know which application is using ports 6001 and 6002, shut that application down and relaunch LonMaker or your LNS-based application. For further information refer to Echelon Support article kb481

Issue Using Schneider Electric actuators with competitors' globe valves Product Line Field Devices Environment Schneider Electric actuators (Americas field devices) 3rd party globe valves Cause To replace 3rd party / competitor valve actuators with Schneider Electric valve actuators, a linkage / adapter may be required to install the Schneider Electric actuator onto the 3rd party / competitor valve.  Resolution Refer to the AV-800 Series Competitive Globe Valve Adapters Selection Guide for a list of adapter kits, recommended Schneider Electric actuators and supported 3rd party / competitors' globe valves (Johnson Controls, Siemens, Honeywell).  The Selection Guide can also be downloaded from the Publication Zone with iPortal. If you do not have access to the iPortal, use the guest access credentials. Once you have logged on, go to 'Links' > 'Publication Zone'.  Installation instructions showing assembly drawings can be downloaded here.

Issue Proper way to 'activate' portions of Personnel Import Utility (PIU) XSL files. Product Line Andover Continuum Environment CyberStation with PIU Cause Difficulty in getting transformation file to import records Resolution Transformation files used with the PIU are located in the \Continuum directory. These are XSL files and are built in a way that features are commented out in the file and those features can be 'activated' by uncommenting. XSL is a language for expressing style sheets. An XSL style sheet is a file that describes how to display an XML document of a given type. When the XSL files are opened with Internet Explorer (IE) you see color-coding and bold text. The bold text is activated, the light grey is not. You can only view the code in IE, not edit it. Use an advanced text editor like Notepad ++ (https://notepad-plus-plus.org/) and you can easily see and edit the file to activate portions of it. Note: Make sure when 'activating" the syntax option in the file by removing the leading  - <!--   you also remove the trailing   --> .  The following is what the file CSVToContinuumTransformation.xsl looks like.   <?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:TAC="http://www.tac.com/TAC" extension-element-prefixes="msxsl" exclude-result-prefixes="TAC"> <!-- - define the Javascript or C# or VBScript functions that you want to include within a msxsl:script element. - language indicates the scripting language - implements-prefix gives the namespace prefix that you declared for your function (i.e. TAC) - Use the functions where ever you want. For example <alias> <xsl:value-of select="TAC:today()" /> </alias> --> <msxsl:script language="C#" implements-prefix="TAC"> <!-- it's often helpful to use a CDATA section so you don't have to worry about escaping less-than signs or anything --> <![CDATA[ public string today() { return "abcdefs"; } ]]> </msxsl:script> <!-- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes"/>--> <xsl:template match="SourceUsers"> <SourceUsers> <xsl:apply-templates select="SourceUser"/> </SourceUsers> </xsl:template> <!-- Need to include only the mapped personnel attributes or if every thing everything is added remove the ones that are included below in XSLT tags--> <xsl:template match="SourceUser"> <!-- You can declare variables, parameters --> <xsl:param name="allPhoneNumbers" select="HomePhone"/> <xsl:copy> <xsl:copy-of select="ADA|Address|AllowEntEntEgr|Blood|CardNumber|CardType|City|Country|DateOfBirth|DefaultClearanceLevel| Department|DepartmentCode|EmergencyContact|EmergencyPhone|EmpNumber|ExecutivePrivilege|ExpirationDate|EyeColor| FirstName|HairColor|Height|HomePhone|Info1|Info2|Info3|Info4|Info5|Info6|JobTitle|LastName|LicenseNumber| LostCard|MiddleName|NonABACardNumber|OfficeLocation|ParkingSticker|PIN|SecurityLevel|Sex|SiteCode| SocSecNo|StateOfResidence|StartDate|Supervisor|VehicleInfo|Visitor|Weight|WorkPhone|Zip|FipsAgencyCode|FipsOrgId| FipsSystemCode|FipsCredentialNumber|FipsCredentialSeries|FipsOrgId|FipsCredentialIssue|FipsOrgCategory|FipsPersonId| FipsPersonOrgAssociation|FipsPivState|FipsPivControlled|FipsExpirationDate|PhotoFile|Signature|ResponseTransaction|State|FipsHmac"/> <!--<Adding OwnerFolder to personnel object. This is must other wise it won't create or update any objects>--> <OwnerFolder>Root\CardHolders</OwnerFolder> <!--<Adding OwnerFolder to personnel object end>--> <!--<Alias is necessary to create or update object and it should be unique in the system>--> <Alias> <!-- By default, we'll use the employeeNumber + samaccountname as an alias (16 chars max). --> <!-- On newer systems, the logon name is userPrincipalName --> <!-- One Way --> <!-- <xsl:value-of select="concat(samaccountname,EmpNumber)"/> --> <!--<xsl:value-of select="concat(FirstName,LastName)"/>--> <!--In IDMS system Serial Number is a unique number. Use this as Alias added to a Character or a group of characters to generate a valid alias. See the Example --> <xsl:value-of select="concat(FirstName,LastName)"/> <!--<xsl:choose> <xsl:when test="string-length(EmpNumber)=0"> <xsl:value-of select="samaccountname"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="concat(LastName,EmpNumber)"/> </xsl:otherwise> </xsl:choose> --> <!-- Other Ways --> <!-- This option combines the last name and EmpNumber --> <!--<xsl:value-of select="concat(substring(LastName,1,12),substring(EmpNumber,2,5))"/>--> <!-- This option combines the EmpNumber last and first name from CyberStation --> <!--<xsl:value-of select="concat(EmpNumber,FirstName,LastName)"/> --> <!-- This option combines the last name and FirstName --> <!--<xsl:value-of select="concat(LastName, FirstName)"/>--> </Alias> <!-- Example of using User defined functions --> <!-- <alias> <xsl:value-of select="TAC:today()" /> </alias>--> <!--<Adding departmentcode DepartmentCode to personnel object if it contains only numbers>--> <!--<<xsl:value-of select="number(department)"/>--> <!-- <DepartmentCode><xsl:number value="Department" /></DepartmentCode> --> <!--<Adding CardType>--> <!--<CardType>AC4plus432</CardType>--> <!--<Adding SiteCode>--> <!--<SiteCode>15</SiteCode>--> <!--<Adding Signature, PhotoFile, FingerPrint use firstname.jpg or Lastname.jpg or Firstname+LastName.jpg. Use the combination depending upon the jpg files stored on the hard drive. A few examples below >--> <!--<Adding Signature>--> <!--<Signature>D:\picsForSri\signatures\LISASIG.BMP</Signature>--> <!--<Signature> <xsl:value-of select="concat('D:\',FirstName,'.jpg')"/> </Signature>--> <!--<Signature> <xsl:value-of select="concat('c:\',Lastname,'.jpg')"/> </Signature>--> <!--<Adding FingerPrint>--> <!--<FingerPrint>D:\picsForSri\Fingerprints\Finger.jpg</FingerPrint>--> <!--<Adding photofile>--> <!--<PhotoFile>D:\picsForSri\pics\Elmer1.jpg</PhotoFile>--> <!--Assigning default areas to the imported personnel--> <!-- To implement Area Links, uncomment the section below before the <AreaLinks> tag and after the </AreaLinks> tag--> <!-- To add more areas, copy the <AreaLink></AreaLink> tags and everything between them and paste after the first </AreaLink> tag--> <!-- State can be Enabled or Disabled, Preload is Workstation Only and can be True or False, AreaId example - Root\MyPersonnelFolder. --> <!-- This is line 1 of 2 to remove to implement Area Links <AreaLinks> <AreaLink> <AreaId><![CDATA[Full Path To Area Here]]></AreaId> <SchedId>Full Path To Schedule Here</SchedId> <State>Enabled</State> <Preload>False</Preload> <ClearanceLevel>0</ClearanceLevel> </AreaLink> </AreaLinks> This is line 2 of 2 to implement Area Links --> <!--<Adding Templates to personnel object>--> <!--<Adding Templates to personnel object with Department name>--> <!--<RefTemplate> <xsl:value-of select="concat('Root\Templates\Personnel Templates\', Department)"/> </RefTemplate>--> <!--<Adding Templates to personnel object based on department>--> <!--<Can do the same way with departmentCode DepartmentCode>--> <!--<xsl:value-of select=AreaTemplate1000/> same as <xsl:text>AreaTemplate1000</xsl:text>--> <!--<RefTemplate> <xsl:choose> <xsl:when test="StateOfResidence='MA'"> <xsl:text>Root\Templates\Personnel Templates\AllAccess</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='NY'"> <xsl:text>Root\Templates\Personnel Templates\PowerUser</xsl:text> </xsl:when> <xsl:otherwise> <xsl:text>Root\Templates\Personnel Templates\StandardUser</xsl:text> </xsl:otherwise> </xsl:choose> </RefTemplate>--> <!--<Adding one personnel Template to personnel object >--> <!--<RefTemplate> Root\Templates\Personnel Templates\PT1</RefTemplate>--> <!--Template> <xsl:choose> <xsl:when test="StateOfResidence='MA'"> <xsl:text>Root\Templates\Personnel Templates\All Access</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='PA'"> <xsl:text>Root\Templates\Personnel Templates\Power User</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='NY'"> <xsl:text>Root\Templates\Personnel Templates\Standard User</xsl:text> </xsl:when> </xsl:choose> </RefTemplate>--> <!--<Adding one personnel Template to personnel object >--> <RefTemplate>Root\Templates\Personnel Templates\Standard User</RefTemplate>--> <!-- Manipulate states--> <!-- If the attribute is using here don't add it at the <xsl:copy-of select--> <!-- <StateOfResidence> <xsl:choose> <xsl:when test="StateOfResidence='Massachusetts'"> <xsl:text>MA</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='New Hampshire'"> <xsl:text>NH</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='Washington DC'"> <xsl:text>DC</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='Connecticut'"> <xsl:text>CT</xsl:text> </xsl:when> <xsl:otherwise> <xsl:value-of select="StateOfResidence"/> </xsl:otherwise> </xsl:choose> </StateOfResidence>--> <!-- Manipulate phone numbers--> <!--</telephonenumberFormat>--> <!-- <WorkPhone> <xsl:choose> <xsl:when test="contains(WorkPhone,'-')"> <xsl:value-of select="WorkPhone"/> </xsl:when> <xsl:when test="string-length(WorkPhone)=0"> <xsl:value-of select="WorkPhone"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="concat(substring(WorkPhone,1,3),'-',substring(WorkPhone,4,3),'-',substring(WorkPhone,7,4))"/> </xsl:otherwise> </xsl:choose> </WorkPhone> --> <!--Replacing the linefeed in the adress --> <!-- Unicode of linefeed &#xA; (is line break \n), Unicode of tab &#x9;--> <!-- <xsl:value-of select="translate(Address, '\n', ' ')"/> Won't work --> <!-- <Address> <xsl:value-of select="translate(Address, '&#xA;', ' ')"/> </Address> --> <!--************************************************************** --> <!--These are the examples of how to parse Multi valued Active Directory attributes after mapping them to Continuum attributes --> <!-- Use Continuum attributes names instead of these dummy attribute names, variables names can be at as your wish --> <!-- This example takes the first element from the list, it shows the use of a variable --> <!--<HomePhone> <xsl:variable name="phoneNumbers" select='HomePhone'/> <xsl:value-of select="substring-before($phoneNumbers, ',')"/> </HomePhone>--> <!-- This example takes the second element from the list. --> <!-- It uses a param at the top of the file. after the line <xsl:template match="SourceUser">--> <!--Or use a local variable between phone2 tags<xsl:variable name="allPhoneNumbers" select='HomePhone'/>--> <!-- <Phone2> <xsl:variable name="after-first-comma" select='substring-after($allPhoneNumbers,",")'/> <xsl:variable name="second-comma" select='substring-before($after-first-comma,",")'/> <xsl:value-of select="$second-comma"/> </Phone2> --> <!-- This example outputs a xml tag if the element exists in the list --> <!-- <memberOf> <xsl:variable name="memberGroups" select="memberOf"/> <xsl:if test="contains($memberGroups, 'Engineering')"> Engineering Lab1 </xsl:if> </memberOf> --> <!--************************************************************** --> </xsl:copy> </xsl:template> </xsl:stylesheet>

Issue Device Template for trane Uc800 Product Line TAC Vista Environment Xbuilder Xenta Server MODBUS Cause Device Template Required Resolution Here is a MODBUS device Template for a TRANE UC800

Issue Microsoft no longer allows OEM computer manufacturers to install Microsoft® Windows Server 2003 or Microsoft® Windows Server 2003 on OEM computers.  Is there a valid legal and legitimate workaround for running software products that are not compatible with Microsoft® Windows Server 2008? Product Line TAC IA Series Environment New server class computer that was purchased pre-loaded with Microsoft® Windows Server 2008 or Microsoft® Windows Server 2008 R2 I/A Series software that runs only on Microsoft® Windows Server 2003 such as: I/A Series (Niagara) R2 - all releases I/A Series (Niagara) G3 - all releases prior to 3.6.x Cause Microsoft® Windows Server 2003 is no longer available on new computers. Resolution Downgrade the Microsoft® Windows Server 2008 to Microsoft® Windows Server 2003 According to the Windows Server License supplied with all versions of Microsoft® Windows Server 2008 (including R2), the license grants the customer the right to run an earlier level or edition of Windows Server.  Microsoft permits this downgrade because many customers need to continue using old versions of Windows Server for compatibility reasons. More information is available in this Microsoft document.

Issue Configuring the Xenta 102-AX to accept a 4-20 mA CO2 sensor input on Universal Input 3.  A negative value is required on the CO2 offset value, but it is not possible to edit the scaling of the input in StruxureWare. Product Line EcoStruxure Building Operation Environment Xenta 102-AX 4-20 mA output CO2 sensor SmartStruxure Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input.  The best option is to always buy a CO2 sensor that is compatible.  However, if 4-20 mA CO2 sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20 mA CO2 sensor with a 0-2000 ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to None Wire the CO2 sensor and a 250Ω resistor across U3 and M.  This converts the 4-20 mA signal to 1-5V. In SBO WorkStation, create a Function Block program to convert the 0 to 100 % signal to ppm.  (You can import the Function Block program here). Edit Bindings on the CO2 Curve program and bind the nvoUnvInput3/Value.lev_percent from the UnivIn3Sense folder of the 102-AX to the CO2_RAW of the CO2 Curve program. Bind the CO2 from the CO2 Curve program to nviCO2/Value.ppm that is in the UnivIn3Sense folder of the 102-AX. At this point, if you have values entered in for the Airflow Reset or CO2 Low Limit and CO2 High Limit then the Airflow reset will be active and operational. Also, if you have multiple CO2 sensors on multiple 102-AXs then you don't have to have a CO2 Curve Function Block program for each one.  You can just edit the existing CO2 Curve program and copy/paste the exiting Function Block program multiple times in the same Function Block program.  You would just need to rename each public point with a unique name.  Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid).

Issue When only the MSDE version of I/NET Seven is installed there is no way to automatically backup the entire SQL Database at scheduled intervals. Product Line TAC INET Environment TAC I/NET Seven running on Windows XP using Microsoft MSDE SQL Server. Cause When only the MSDE version of I/NET Seven is installed there is no way to automatically backup the entire SQL Database at scheduled intervals. Resolution A batch file BackupInetDb.bat has been developed to allow users to create a Scheduled Task within Windows which launches the batch file with the appropriate command line switches. Click here to download the zip file which contains the BackupInetDb.bat and instructions on how to configure an automated backup.