Building Automation Knowledge Base

Issue When logging on to the Report Manager or Report Builder to manage, create or install custom report packs, the following error is shown: User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed Environment WebReports Cause This is a known issue with Microsoft Reporting Services when User Account Control (UAC) is enabled on the server. By default the local administrators are only given the role of "Content Manager", which does not allow for all operations. The easy solution is to disable UAC, but below is the solution for how to solve it without disabling UAC. For further reference, refer to the following discussion. Resolution 1. Launch Internet Explorer as administrator (right click the shortcut and click "Run as administrator"). 2. Open the Report Manager on the local server using "localhost" in the URL. E.g. if the URL is normally http://server_name/Reports_SQLEXPRESS you need to enter http://localhost/Reports_SQLEXPRESS 3. Click "Folder Settings" 4. Click "Edit" next to the "BUILTIN\Administrators" 5. Check all the options and click "Apply"

Issue During initial setup, the incorrect ethernet IP address or subnet mask was entered.  Now when rebooting the UNC, I cannot reconnect to it using the I/A Series R2 Admin Tool.  How can the incorrect information be changed? Environment UNC-520 or UNC-410 Cause Network connectivity cannot be established if the IP address or subnet mask was entered incorrectly.  Likewise, if an invalid subnet mask is entered, the UNC may not boot completely (or at all). Resolution The following information is provided in more detail in the section "Determining Network Settings", subsection "JACE-4/5" of chapter 3 of the Niagara Networking & Connectivity Guide.  This document is provided with and installed with the I/A Series (Niagara) R2 software. Required hardware: Serial Cable Terminal Emulator software on computer (such as "Hyperterminal" or "Putty") Procedure: Configure the Terminal Emulator to run at 9600 baud, 8 bits, one stop bit, no parity, hardware flow control Jumper the upper two pins of the Console "MODE" connector,  located in the upper right corner of the UNC-520 circuit board (See photo at right). Connect the terminal emulator via a UNCC-405 serial cable to port COM1 on the UNC and power-cycle the UNC. Wait for the UNC to complete its bootup process (do not break out of the boot process). Check the displayed information to determine what IP address and subnet mask was entered. Power cycle the UNC and when the console display shows "Press any key to stop auto-boot"., press the space bar. Follow the procedure in the section "Determining Network Settings", subsection "JACE-4/5" of Chapter 3 of the Niagara Networking and Connectivity Guide for the procedure to step through the settings changing them if necessary.  Please note that the figure 3-8 may not include all lines of information shown for your UNC. If the serial console is showing any errors after you have verified the IP address / Subnet mask entries, please provide product support with a text copy of the serial console output showing the error messages.

Issue Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network. Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconics Cause Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network. Resolution By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115. The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs. The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat. One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system. For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009. A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility. For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Issue TAC Vista SQL maintenance repeatedly fails. Not just once or twice, but on every attempt. Microsoft Management Studio View of error Vista Workstation view of error Environment TAC Vista 5.1.7 or newer. Cause The SQL maintenance feature was added to Vista in version 5.1.7, to regularly database defragment the database and prevent the follow-on effects of a fragmented database. This scheduled maintenance can fail for a number of reasons. Resolution Start by  taking a DSS writer server log using TACOS Tweak. Follow the steps below to do this. Goto the TAC Vista installation folder (C:\Program Files (x86)\Schneider Electric\TAC Vista 5.1.9 by default on 64-bit machines). Locate TacosTweak and double-click on it. Click on the "Category" drop-down box and select "DSS (Registry)". Locate the "DSS Server - Log Level" entry and increase the log level to "7" by entering the value in the value field and clicking the "Set" button. Locate the "DSS Server - Log file" entry and chose an appropriate path. Launch "TAC Vista Server Setup" and go to the SQL maintenance tab. Locate the "Run SQL Maintenance now" checkbox and check it. Click on "OK" or "Apply". Locate the DSS server log file and open it with a text viewer/editor. Search the log file for the following text "Maintenance Task - Starting" and check that the date time stamp is approximately when the "Run SQL Maintenance now" button was pressed. Examine the file carefully and follow the file line for line from this point until you reach "[ERROR] Fatal error : SQL Exception : Incorrect syntax near '('. NOTE: Contact Product Support Services if you are unable to interpret the log file or see another type of error than that described above. Once confirmed, launch Microsoft SQL Server Management Studio and follow the steps below: Locate the "taclogdata" database. Right-click on it and select "Properties"  Locate the "Options" tab and set the compatibilty level to SQL 2008 (or SQL 2005 if that is the installed version). Don't forget to set the DSS Server log level back to "5"!   A tool to simplify this process can be found here. Please note that this is not an official Schneider Electric utility.  

Issue The StruxureWare Building Operation BACnet digital value is seen as being in alarm Product Line EcoStruxure Building Operation Environment BACnet Digital Value Alarm Cause Having created a BACnet Digital Value under the BACnet Interface / Application. When the digital value is "Enabled" (Active Text), the IN ALARM status flag is set. This causes the third party device to show it as being in alarm. Resolution From v3.0, EcoStruxure Building Operation is BACnet standard at protocol revision 14 so this is not an issue. The text below was written for earlier versions and is valid for v2.0 and earlier. It is not possible to disable the evaluation of intrinsic alarming on BACnet points (which updates the status flags and event state properties). Not updating status flags and event state (according to the alarm-value) was identified by the BACnet Test Lab as a compliance issue with the BACnet standard at protocol revision 6 – the revision SBO implements. The essence of the issue is that we are not allowed to have the intrinsic alarming properties, but not use them – updating the object state according to its configuration. The feature to disable intrinsic alarming (an alarm disable property) was introduced at a more advanced protocol revision (13), which is not currently not available for SmartStruxure. A possible workaround for the issue, if the value periodically changes between active and inactive: set the time-delay (which is measured in seconds) to a large value. If the delay is longer than the amount of time the value spends in what would be the alarm state, then evaluation is avoided. A value of 32,000,000 for example delays evaluation for a little more than a year. NOTE - make sure to set the time delay while status flag in-alarm is false, and event-state is normal, otherwise it would take a year to get out of the alarm state.

Issue TAC Xenta 527 - Embedded Web Server Product Line TAC INET, TAC Vista Environment I/NET Seven or Vista site Cause Need information concerning the TAC Xenta 527 - Embedded Web Server Resolution Information Technology Brief: The TAC Xenta® 527 is a web based presentation system for TAC Vista LONWORKS and I/NET Seven® networks. In addition, to supplementing the host workstation interface with web access, the TAC Xenta 527 can also be used as the sole operator interface into I/NET Seven and TAC Vista LONWORKS systems. A single Xenta 527 will handle small to midsized systems, and several devices can be used to handle larger networks. The web pages are based on standard Internet technology as HTML and Java™ Applets. Alarms can be forwarded as e-mail. Please use the following link: Xenta 527-23 June.doc

Issue Convert Key Card Translation table to a Large Number and then remove the Key Card Table entry from I/NET. Product Line TAC INET Environment I/NET site with Access Control Cause The process described will allow you to do this conversion on an active system without causing the Idisc to fail during process. Resolution For example take the Key card translation table below: With this Individual editor: Make an excel spread sheet that performs this calculation multiple times, or you can do it one at a time manually. The information needed for this calculation is located in the Key Card Table and Individuals editor. Source Number (from Key card table) Individual Number (from Individual editor) Target Number (from Key card table) Decimal Number (from Individual Editor) Source Number + Individual Number - Target Number = Decimal Number Source Number Individual Number Target Number Decimal Number 67806444 00001 1 67806444 67806444 00002 1 67806445 67806444 00003 1 67806446 67806444 00004 1 67806447 67806444 00005 1 67806448   Go into the Individual editor and modify an individual entry Take the calculated decimal number from the calculation above and add it into the Decimal Number area. The I/NET program will calculate the Hex number automatically. This Hex number should be the same as the bottom of the Idisc itself. Note: ONLY delete the Key table lines after you completed the entire tenant conversion. This will insure that all people will get into and out of the building. Note: These changes can be done on an active system. This is the process of adding NEW people in the system that has existing Key Card Translation table and you want to enter the NEW Disk as large numbers. Go into the access Individuals editor and Add a new person. It is not permitted to back-fill any existing Individual Numbers. In the example above Individuals 00001, 00003, and 00004 are defined. It is not possible to add Individual 00002. Go to the end of the Individuals list and choose the last number + 1 number. Set the Individual Number then place the cursor on the middle box and touch the new disc to the wand. This will place the Hex number in that box from the Idisc. The Hex number and Decimal number are listed in the Individual Parameters. Complete the process by filling out the rest of the Individuals editor.

Issue You get an error, "Unable to load the .Net control for this page." when trying to open a schedule in WebClient. Product Line Andover Continuum Environment webClient Cause The problem is that the .Net zone permissions are not set on the browser machines. Resolution Depending on the revision of the WebClient the procedure for correcting this on the browsing machines is different. If you are running WebClient version 1.73 or below then refer to the WebClient installation guide on setting the .Net zone permissions. If you are running WebClient version 1.74 or higher, which uses .Net 2.0, the procedure is different. Below is the procedure that will need to be performed on the browser machines at the command prompt to set the .Net Zone Permissions for .Net 2.0. The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success You should then be able to open the .Net 2.0 editors on your web.client browser machine. In some cases adding the webclient IIS PC to the trusted sites in the browser is needed Internet Explorer> Internet Options> Security> Click Trusted Sites> Click Sites Type in http://your server name/webclient and click Add (i.e your server name is specific to your install) Deselect the checkbox for 'Require server verification (https:) for all sites in this zone Click Ok, Ok Close explorer and access webclient schedules Note: Every browser PC that will be accessing schedules needs to have the caspol commands run on it. Download a batch file that can be run on each PC (Rename the .txt file to .bat and run at a DOS prompt  C:\> caspolwebclient.bat)   Note: When using 1.94 SP1 check the application pools .net version selected Name .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic 4.0 Classic .NET AppPool 2.0 Default AppPool  2.0 WebClient  4.0 Note: If .net framework 4.5.x has recently been installed on browser PCs, see Webclient Cannot open .net editor with .NET Framework - 'There was an error trying to create the .NET control for this page'.

Issue When setting up a Continuum Workstation or a CX/ bCX controller some IT departments wish to use DHCP (Dynamic Host Configuration Protocol) allocation of IP addresses. Environment Cyberstation workstations and all Ethernet level controllers (CX9200, CX9400, CX9702, CX9900, bCX1, ACX5740, ACX5720, CX9680. Cause Continuum Workstations and Controllers do not support DHCP addressing. Resolution A fixed and unique IP address and subnet mask must be allocated in every controller and workstation, this value must also be entered in the database in offline editing for all controllers. For routed networks the correct address for the Default Router must also be entered in each controller and the database. When creating a new workstation, once the Workstation initialization has completed and the Workstation has started, verify that in Offline Editing that the IP address for the workstation matches the fixed IP address as defined in the Windows Network card settings.

Issue How to read and write from/to files using PE Product Line Andover Continuum Environment CyberStation Plain English Cause Site needed a CSV report of personnel accessing the building that included access event information such as time stamp, door, area, card number BUT also data such as employee number etc., a simple list view could not be used since list views can only show data from ONE table in the ContinuumDB. Resolution Sample CyberStation program that reads/writes from/to file and aggregate data from different tables in the ContinuumDB IMPORTANT: PE Program is provided as a sample proof of concept ONLY and it is not to be taken as a complete working solution. REQUIREMENTS: Create STRINGS ReportEventsPath and T_A_Path in the CyberStation where the program will run and set to the path to the input and output files respectively, the input file must exist, the output file will be automatically created if it doesn’t exist. PROGRAM CODE: 'This Cyberstation program takes as an input a CSV file generated from an Access Event list 'and creates a second file with the EMPLOYEE NUMBER added. 'Program is FALL-THRU and NOT autostart 'IMPORTANT 'The Input file MUST be formatted like this... 'AccessEvent 'PersonId,TimeStamp,CardNumber,AreaId 'Root\MyPersonnel\Meran_Abe,3/31/2014 10:16:11 PM,3540,Root\MyAreas\Area1 File inputFILE, outputFILE String 132 DATALINE, RESULT, theEMPLOYEE, empNUMBER, localSTR Numeric CHARSREAD, CHARSWRITTEN, OK, RECORDLINE Numeric DEBUG_FLAG Line INITIALIZE DEBUG_FLAG = 0 'SET THIS TO 1 TO HAVE PROGRAM PRINT DEBUG INFO Line OPENING RESULT = "" RECORDLINE = 0 CHARSREAD = 0 If OpenFile(ReportEventsPath, ReadOnly, inputFILE) = Failure then 'OPEN THE INPUT FILE TO READ FROM RESULT = "COULD NOT OPEN inputFILE FILE" Goto FAILING Endif If OpenFile(T_A_Path, WriteOnly, outputFILE) = Failure then 'OPEN THE OUTPUT FILE TO WRITE TO RESULT = "COULD NOT OPEN outputFILE FILE" Goto FAILING Else Goto COPYING Endif Line COPYING RECORDLINE = RECORDLINE + 1 If DEBUG_FLAG then Print "Record line = " ; RECORDLINE If RECORDLINE = 1 then OK = ReadFile(inputFILE, DATALINE, 132, CHARSREAD, "|10") 'READ FIRST LINE FROM THE INPUT FILE UP TO THE LF Else OK = ReadFile(inputFILE, DATALINE, 132, CHARSREAD, "|13") 'READ ONE LINE FROM THE INPUT FILE UP TO THE CR Endif If OK = Failure then RESULT = "COULD NOT READ FILE" Goto FAILING Else If DEBUG_FLAG then Print "Read..." ; DATALINE If OK = Eof then RESULT = "END OF FILE" Goto CLOSING Endif Endif 'INSERT THE EMPLOYEE NUMBER If RECORDLINE = 2 then empNUMBER = "EmpNumber" 'MODIFY THE HEADER WITH THE NAME OF THE FIELD(S) WE ARE ADDING If RECORDLINE > 2 then theEMPLOYEE = (left(DATALINE, search(DATALINE, ","))) theEMPLOYEE = (left(theEMPLOYEE, (search(theEMPLOYEE, ",") - 1))) 'FOR EACH LINE IN THE INPUT FILE GET THE PATH TO THE PERSONNEL OBJECT Print getname(theEMPLOYEE ; " EmpNumber") to empNUMBER 'AND GET THE EMPLOYEE NUMBER Endif 'WRITE THE LINE WITH THE ADDED NEW FIELD(S) TO THE OUTPUT FILE If RECORDLINE = 1 then Print DATALINE ; chr(10) to localSTR Else Print DATALINE ; "," ; empNUMBER ; chr(10) to localSTR Endif OK = WriteFile(outputFILE, localSTR, 132, CHARSWRITTEN) If OK = Failure then RESULT = "COULD NOT WRITE FILE" Goto FAILING Else If DEBUG_FLAG then Print "Wrote..." ; localSTR Print "CHARSWRITTEN=" ; CHARSWRITTEN Endif 'POINT TO THE NEXT LINE IN THE FILES If RECORDLINE = 1 then If PositionFile(inputFILE, 1, FileCurrent) = Failure then Goto CLOSING 'ADVANCE PAST THE LF Else If PositionFile(inputFILE, 2, FileCurrent) = Failure then Goto CLOSING 'ADVANCE PAST THE CR and LF Endif If PositionFile(outputFILE, 0, FileCurrent) = Failure then Goto CLOSING 'WRITE AT THE CURRENT FILE LOCATION Goto COPYING 'GO DO THE NEXT LINE Endif Line FAILING 'SOMETHING WENT WRONG If DEBUG_FLAG then Print RESULT Goto CLOSING Line CLOSING 'CLOSE THE FILES If CloseFile(inputFILE) is Failure then RESULT = "COULD NOT CLOSE FILE" If CloseFile(outputFILE) is Failure then RESULT = "COULD NOT CLOSE FILE" If DEBUG_FLAG then PEDebug = PEDebug + 1 'IF DEBUGGING INCREMENTED PEDebug MEANS NO ERRORS Stop Line E 'HANDLE RUNTIME ERROR If DEBUG_FLAG then Print RESULT PEDebug = 666 Endif CloseFile(inputFILE) CloseFile(outputFILE) Stop After the program runs if the input file looks like: 'AccessEvent 'PersonId,TimeStamp,CardNumber,AreaId 'Root\MyPersonnel\Meran_Abe,3/31/2014 10:16:11 PM,3540,Root\MyAreas\Area1 The output file will be: 'AccessEvent, 'PersonId,TimeStamp,CardNumber,AreaId,EmpNumber, 'Root\MyPersonnel\Meran_Abe,3/31/2014 10:16:11 PM,3540,Root\MyAreas\Area1,12345  

Issue Keypad installed in environment where the local language needs to be used instead of the default English. Product Line EcoStruxure Security Expert. Environment Security Expert SX-KLCS Cause Unsure how to change the language settings on the keypad. Resolution You can change the language used by the keypad by setting the default language in controllers configuration. Go to Sites | Controllers, select the Configuration tab, and change the ‘Default Language’ dropdown. One you have set your desired language and downloaded the changes to the controller, Users logging into a keypad connected to this controller will see messages in the selected language.

Issue When opening an OGC graphic using Vista Webstation as a window inside StruxureWare Webstation, the OGC graphic shows "Loading..." with a small cross in the upper left corner, and the graphic never loads. Product Line EcoStruxure Building Operation Environment TAC Vista Webstation Building Operation Webstation   Cause The authentication in the communication between the browser and Vista Webstation is based on sessions and cookies. Due to a security setting on some sites, the initial cookie can not be set in the browser, and the authentication between the OGC graphic page showed in the browser and the web server therefore fails. If the graphic is opened in full screen (see below) or in a new window it will load, and subsequently all OGC graphics will work until the browser is restarted. Button to open the graphic in full screen Resolution On each PC that needs to access the OGC graphics using StruxureWare Webstation do the following: 1. Open Internet Explorer settings by clicking the gear in the upper right corner 2. Click "Privacy" and then "Sites" 3. Write the address of Vista Webstation (e.g. http://ip_address/webstation), click "Allow" and "OK" 4. Restart Internet Explorer   Note: This solution also applies to following issue; After clicking  a Vista Webstation url (direct link to a TGML graphic) in SBO Webstation from a Windows Server 2012 PC using Internet Explorer 11, Vista Webstation is expanding to fill the entire screen (it doesn't stay in the right hand window of SBO Webstation)

Issue Users need a way to identify all Forced Variables without manually inspecting each point. The goal is to have a summary view—not via Reports Server—but directly accessible on the Automation Server (AS) or Enterprise Server (ES). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no built-in summary page in versions 1.4.1 and older that lists all Forced Variables. This makes it time-consuming to locate which points are currently forced. Resolution You can locate Forced Variables using the system tree in the Workstation. Navigate to: ES/Servers/AS/System/Modules/RuntimeDBManager/VariableManager/Variables Ensure the isForced column is enabled to view which variables are forced. Additional Notes: This method provides a quick overview without needing to open each individual point. It is especially useful for troubleshooting and auditing system behavior.

Issue An SP-RDM2 will be used to add doors to an I/NET-transitioned site. The readers connected to the SP-RDM2 will need to read Hex Card Number credentials. Product Line EcoStruxure Security Expert, TAC INET Environment Security Expert Controller (SP-C) Security Expert Reader Module (SP-RDM2). Cause After transitioning an INET site to Security Expert, you may find it necessary to add one or more new doors. In Security Expert, you add doors to your system by attaching one or more SP-RDM2 modules to the RS-485 bus of an SP-C (up to two doors per SP-RDM2). That is still true for the transitioned system; however, some configuration tasks must be performed to allow the SP-RDM2 to coexist with the SCUs and DCUs that are already communicating with the SP-C.  You will also configure the SP-RDM2 to use the custom Hex Card Number credential you created as part of the INET transition process. Resolution For an SP-RDM2 module to work in conjunction with I/NET modules it must be configured in a specific way. You will need: SP-C firmware 2.08 build 911 or later SP-RDM2 firmware 1.12 build 546 or later Configuring the SP-RDM2: To the existing transitioned I/NET site, add a new Reader Expander for the additional SP-RDM2 reader module. (Note that the last reader expander defined in your existing system may be assigned to a dual-address SCU. If this is the case, make sure the address you assign to the SP-RDM2 is at least two addresses higher than the SCU to avoid address conflict.)  Set the Reader 1 Format and the Reader 2 Format to "Custom Credential". (Note that if the Port 1 Network Type or Port 2 Network Type is set to "Schneider Electric RS485" then this will need to be changed to "Wiegand" to allow you to set the reader format; it is greyed out otherwise. The network type can be set back to "Schneider Electric RS485" afterward.) Set the Port 1 Network Type and Port 2 Network Type according to the type of readers that are connected. In order to correctly convert the card read to the hexadecimal credential format that is programmed for the users, the reader expander must know what card format is being presented. This is done using commands. For the reader on port 1, add the command "R1RawFmt = #" where # is one of the descriptions shown in the table below. Similarly for the reader on port 2, add the command "R2RawFmt = #" where # is one of the descriptions shown in the table below.  If the command is absent, then Wiegand 26 is used as a default. Command Card Type R1RawFmt = Wiegand 26 26-bit Wiegand R1RawFmt = Wiegand 32 32-bit Wiegand R1RawFmt = Wiegand 34 34-bit Wiegand R1RawFmt = Wiegand 66 66-bit Wiegand R1RawFmt = Custom Wiegand Any Wiegand card - parity check is skipped Additionally, the SP-C controller must know which reader expanders to expect on the I/NET network and which reader expanders to expect on the Security Expert module comms network. By default, if the controller command "INET = true" is present in the SP-C, then all modules are considered to be on the I/NET network. Adding an SP-RDM2 to the Security Expert module comms network with no additional commands will result in partial operation but there will be problems. To use a mixture of I/NET modules and Security Expert modules, a command must be added to the programming of all I/NET modules. This command is: "HardwareType = INET" If this command has never been added to any module, and the command "INET = true" is present in the SP-C, then all modules are treated as I/NET. This maintains backward compatibility with existing sites. As soon as the "HardwareType = INET" command has been added to even one module, then it must be added to the programming of all I/NET modules from then on for the site to function as expected. Configuring the SP-RDM Doors to Accept Hex Card Number Credentials Create a new Door Type for reading cards as a Hex Card Number credential and configure it as follows. In the Entry section on the General tab, set the Entry Reading Mode to "Custom". In the Entry Credential Types section, add the "Hex Card Number" credential type. Save the Door Type. Configure each door on the SP-RDM2 to use the new Door Type as follows: In the Setup section on the General tab of the door, set the Door Type to the name of the Door Type you just created in step 1. Save the door.

Issue When importing I/NET sav files into an XBuilder project, it will try to reconcile unknown Engineering Units in I/NET with recognized units in XBuilder.  If these units are set incorrectly by accident, there is a process for correcting them. Associate Unit Please associate the unrecognized unit with a unit known to XBuilder. If you do not want an association for this unit, select "NoCategory", which will result in that all signals having this unit will be displayed as having no unit. Product Line TAC INET, TAC Vista Environment Xenta 527, 731, 913 I2V I/NET sav files Cause Engineering unit Associate unit dialog accidentally set wrong units, or need to set a defined unit to "No Category" to avoid conversion issues in an integration. Resolution Locate the XBuilder project directory In the root project directory is a filed called UserDefUnits.txt If there are not many units defined, this file can be deleted.  It will then be recreated in its entirety the next time a batch of sav files are added to the XBuilder project. If there are many definitions that need to be preserved, this file can be edited. Erroneous entries can be deleted, or edited if the correct XBuilder unit definitions are known.  Example file below: ; *** UserDefUnits.txt *** ; User defined conversion of units to TAC XBuilder/Domino units ; degF=F Browse the sav files into the project again.  This will prompt the user to define the unknown units again, and the correct selection can be made and stored in the UserDefUnits.txt file.

Issue When editing a personnel object an error is received "Input string was not in a correct format" using 1.82 or 1.90. Environment Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Microsoft released .Net 2.0 SP2 which caused an issue with our code in the personnel area. Resolution The version of Continuum you are using will determine the solution you need to use. 1.82 - Uninstall .net 2.0 SP2 1.90- Install the following hotfix  Click here to download The issue was corrected in 1.91.

Issue Add Xenta trend log is grayed out when right clicking on point in a programmable Xenta controller and selecting Create Trend Log. Environment Xenta Programmable Controller Menta Cause There are no available trend logs in the Menta application. There have to be empty trend logs in Menta for this to work. Resolution Edit the file In Menta Go to Options > Trend Logs Click on the 'up arrow' to increase the number of available trend logs. Save the application to the Vista Database Download to the controller.

Issue Get error message "Could not open or load translation table" when trying to save a Menta file after having edit it in StruxureWare Building Operation. Environment StruxureWare Building Operation version 1.2. Cause Error in the installation of the German Language pack. Resolution Reinstall the language pack.

Issue Is it possible to connect eComission SmartX controller mobile application to a SmartX controller with no WiFi available in the building and BLE(Bluetooth) not turned on in the SmartX controller. Product Line EcoStruxure Building Operation Environment Building Operation eCommisioning Tool Building Operation Room Controller (RPC) Building Operation Multi-purpose Controller (MPC)   Cause The eCommission SmartX controllers mobile application supports device connection through BACnet Wi-Fi and wireless Bluetooth connection. Resolution Install eCommission SmartX controllers on a computer, connect to the SmartX controller using an IP cable connected directly from the computer to the SmartX controller and enable Bluetooth on the SmartX controller.   Disconnect IP cable from the SmartX controller if there is one connected. Restart the SmartX controller, since it can’t reach the DHCP server it will get an IP address in the range of 169.254.x.x. Make sure the computer IP address is in the same IP range as the SmartX controller. Connect the IP cable directly from the computer to port 2 in the SmartX controller. Start eComission SmartX controller mobile application and connect to the SmartX controller. For details please see the video.

Issue The Sum Alarm will not trigger when monitoring other Sum Alarms. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server  Building Operation Enterprise Server Cause The Sum Alarm is ignoring other Sum alarms for detection of alarm criteria. Resolution There are two options to resolve this. Configure a 2nd SUM alarm to use criteria that triggers on any of the points that would have triggered the Sum alarm you want to monitor and the other points. You can create a Change of State Alarm to monitor the alarm state of the 1st Sum Alarm. The second Sum alarm can then detect that the Change of State alarm is active. (It might be practical to hide the Change of State alarm by setting the priority to a low value and filter your default alarm view to exclude it in order to avoid double alarm entries in the alarm view of Workstation)