Building Automation Knowledge Base

Issue Cannot enter a "." (period) into an Object Name of an application drawing using WorkPlace Tech 5.7.4 and newer.  It was possible with previous versions. Has this ability been removed? Environment WorkPlace Tech 5.7.4 and newer Cause The change to not allow a period in an Object Name was to make WorkPlace Tech compatible with StruxureWare. Resolution If a period must be use in an Object Name, do the following:  Open Notepad. Type the desired name (including period). Copy and paste it into the object's name.

Issue Can a door switch input be configured to operate without the input resistor? Can supervised inputs be configured to work without an input resistor? Environment NetController ACX5720 ACX5740 AC_1 AC_1 Plus Cause When designing or troubleshooting a security access job, it is important to know if the hardware requirements are absolutely mandatory. Resolution Within the Continuum door object class, the input type is not selectable - it is a supervised input. As supervisory inputs they require an input resistor to be installed.

Issue Declaration of Conformity Environment Continuum hardware Declaration of Conformity Cause Location of Declaration of Conformity Resolution Regulatory Compliance on The Exchange

Issue In a Graphic panel configured with a background image and several controls including a combo box control when the list is exposed (pulled down) it snaps back closed before a selection can be made. Environment CyberStation Cause Interaction between combo box control and other graphic object components such as back ground image can cause the combo box control to behave inappropriately. For example, an overlap of the combo box control with other controls and/or images in the canvas may cause the issue. Resolution Switch graphic to design mode and re-arrange controls and images until combo box works as expected.

Issue How to interpret a M-Bus point details in a VX communication log such as External Temp [C] {1:0:0}. Environment Xenta Server 913 Cause The  External Temp [C] {1:0:0} message is providing important information about the point. External Temp = Field Type [C] = Unit {1 = Storage # :0: = Sub-Unit 0} = Tariff # Resolution Use the details of the communication log message to correct configuration problems in the device editor. MVAL External Temp [C] {1:0:0} value not required This message provides device details that a point exists, but the Device Editor is not looking for it. !MVAL External Temp [C] {2:0:0} =not received A point is expected but was not found.

Issue Compressor will not activate blocking the cooling or heating of the Xenta 121-HP. Environment Xenta 121-HP Cause A compressor temperature lockout exists in the Xenta 121-HP application. The lockout has a minimum and maximum temperature the source signal must be between for the compressor to activate. The source signal changes depending on whether the application uses a air source or a water source. Air Source - nviOutdoorTemp Water Source - nviSourceTemp Resolution Ensure that the source temperature signal is between the compressor lockout minimum and maximum.

Issue Workstation is alarming that the SQL has reached the 4G limitation, but the Version of SQLServer is a Full version which is unlimited in size. SQL should be able to grow until the hard drive capacity is reached. There seems to be normal functionality of the SQL Server and there are not any $queues building. Environment SQL Vista 5 Cause When Vista is installed, The parameter how large SQL can be is written into the properties of $Backup_LDB. If a Free version of SQL is used, such as the one included in Vista, A limit of 4G or 3820MB is written to this Value. Even if you Install a Full Version of SQL at a later date, this Alarm Limit will remain. Resolution In Workstation, select the Vista Server, this displays the contents of the Vista Server in the Main pane. In the Main pane, double-click on the object $Backup_LDB, this displays the properties of $Backup_LDB in a new window. In the $Backup_LDB property window, Scroll to the last property, "DB Size Alarm Limit (MB)" Increase this value to a higher logical value of your choice considering limitations of the system hard drive space. Note: 1 Gb = 1024 Mb, 1 Mb = 1/1024 Gb and 1 Mb = 0.0009765625 Gb

Issue The priority attribute was not specified as configurable. (Subsystem: NS Connections, #11) lcaErrConnPriNotConfigurable An attempt was made to modify the priority attribute; that attribute was not specified as configurable. For network variables, the priority keyword may be included as part of the connection information in the Neuron C variable declaration.  The config and nonconfig keywords specify whether the priority designation can be modified with a network management tool. The default is config. The priority keyword affects output or polled input network variables.  Please refer to the Neuron C Reference Guide for more information. Environment LonMaker Cause Applying a connection description to a new binding that causes a connection error, such as applying a connection description with the priority attribute set to a connection that does not support it, causes this error message to be displayed. Subsequent attempts to add any connection with the default connection description will result in the same error message. Resolution Exit LonMaker Re-open the LonMaker tool.  Then add the connection.  Alternatively, explicitly select a valid connection description other than "Default."

Issue Setpoint button may break if forced outside of movement range. Environment STR-106 Cause Excessive force used to turn setpoint button outside of movement range. Resolution Report faulty unit through Warranty Claim System. Replacement button carries component no 372069900.

Issue What is the maximum number of site codes that can be loaded into a Continuum system? Environment AC-1 and AC-1 Plus modules Cause Network design limitations Resolution There is no limit to the number of site codes that can be loaded in a Continuum system.  However, each door can contain a maximum of four (4) site codes.  In the case of an AC-1 module, if it loses communication with its associated Netcontroller, it will only allow access from the first two fields.

Issue Xenta 104-A ships from factory with a resistor on terminals 7 and 8 Environment Xenta 104-A Cause Terminal 8 is input U1, which is used by the controller for outside air temperature in the economizer calculation. Resolution The resistor is 1.8kΩ A temperature sensor on U1 would be a 1.8kΩ thermistor, if this input was being used. The resistor is a place holder to keep the unit out of economizer during initial setup if a thermistor is not going to be used.

Issue Offline Xenta 401 Not Generating Alarms Environment Xenta 401 Xenta Group Cause Xenta Group Master is offline Resolution Determine if the Group Master is offline In the Vista System Plug-in TAC Network Pane, the Xenta Group Master will be the only controller in the Xenta Group that is underlined Determine if this controller is offline in LonMaker or NL220 If the group Master or any of the Xenta devices in that Xenta Group show an " * ", you will need to download application and parameters Change the Group Master to a more reliable controller Determine which controller in the Xenta group has the least amount of potential traffic In the Vista System Plug-in TAC Network Pane, Right-Click on this device and select "Set as Master". Download Application and Parameters to any device that shows and " * " after this change.

Issue Trend logs not working after upgrading from Vista 4.2.5 to Vista 5.1.6. Environment Vista 4.2.5 Vista 5.1.6 Non-english regional settings. Cause When upgrading from a Vista version older than 4.5.0, it is recommended (in the latest TPA) to upgrade first to Vista 4.5.0 and then to Vista 5.1.6. However with non-english /US regional settings this can cause problems, such as the trend logs not being upgraded and, due to this, not working. Resolution Follow these 2 simple steps: Change the regional setting to "Location" US and set the language to English (United States). Upgrade directly to Vista 5.1.6 (not via 4.5.0.)

Issue Get "Invalid Data" error message when trying to change an Xenta Trendlog's setting from Man-On to Auto in Vista workstation. Environment Windows 2003 & XP (confirmed - possibly other operating systems). TAC Vista Workstation/Server 5.1.4. Cause Unknown. Resolution Upgrade to TAC Vista 5.1.6. This issue has been resolved in this version.

Issue Have (10) i2885-V-WL (Wireless Infinet) which need to be changed to regular RS-485 hard-wired (Infinet). How is this done? Environment CX9680 i2885-V-WL Cause Have (10) i2885-V-WL (Wireless Infinet) which need to be changed to regular RS-485 hard-wired (Infinet). How is this done? Resolution Simply flash any Infinet II –V VAV Controller from a wireless Infinet to a wired Infinet II or even to a wired BACnet or Wireless BACnet –VAV controller in just one step. The –V VAV Series are the first Andover Continuum controllers to allow a change in the controller operating system with a simple firmware upgrade. The hardware model number doesn't change. For example, an 866-V will always be an 866-V, but through software that same 866-V can change in firmware from an i2866-V to a b3866-V-WL with one upgrade in the field. Also, the i2 -V controller firmware type can be identified using two onboard LEDs (i.e. wired vs. wireless, BACnet vs. Infinet). Notes: The Roam-IO2 cannot be used to flash a wireless controller to a wired one. The Roam-IO2 cannot communicate to a wireless controller. Non -V controllers should not be flashed in the field. Trying to do this runs the risk of turning the controller into a brick.  To flash non-V controllers, send them to repair.

Issue Cannot upgrade the OS of i2 controller with the error message of "Controller Type Mismatch" . Environment NetController (bCX9640) InfinetController (i2xxx) Cause When upgrading the i2 controller to the latest version AND the version of NetController (bCX9640) is couple of versions older than the i2 controllers new version. Resolution Upgrade the NetController to the latest version of OS first, reload the NetController, reload the i2 controller and then upgrade the i2 controller to the latest version.

Issue The need to know what voltages will a Sigma controller operates under. Environment Sigma Power Voltage Input Cause The need to know what voltages will a Sigma controller operates under. Resolution For Sigma controller the specification for the power supply is shown as: Supply voltage. . . . . . . . . . . . . . . . . . . . .230Vac ±10%. Supply frequency. . . . . . . . . . . . . . . . . . .50/60Hz ±10% Power consumption. . . . . . . . . . . . . . . . .25VA maximum

Issue When installing the site .plf license, Privilege Administrator states it is missing Developer Extension and terminates the installation. Environment Privilege Administrator / Licenser Developer Extension PLDevExt.pde Cause An error occurred during the installation of Privilege License Software where the Developer Extension was not executed. Resolution Manually execute the Developer Extension. Navigate using Windows Explorer to ..\System32\PLDevExt.pde Double click the PLDevExt.pde Restart Privilege Administrator Install site license by double clicking your .plf file Verify the licensed  TAC software starts successfully

Issue Documentation on the MSC-V-400 Microsmart controller. Environment Microsmart controller MSC-V-400 Cause n/a Resolution Click here to view a datasheet on the MSC-V-400.

Issue UNC was upgraded to R2 release 529 from an older version and when the station was started, the following error message was displayed in the Standard Output Window: ---------- Station Starting:   THU MAR 26 14:43:09 2009 ---------- Tridium Niagara Station, r2.301.529.v1 [GafbBldg857] ERROR: Reading FlexSnvtTempSetpt [3928] FlexSnvtTempSetpt#link: 60 *************************************************************** FATAL: Cannot boot station from sns java.io.UTFDataFormatException   Environment UNC-520 with release 522 or 529 software installed. Cause Incompatibility in the FlexSnvtTempSetpt object between the release 514 and release 529 versions of the jar file. Resolution The best way to correct this issue is to perform a manual upgrade of the existing version 514 station. Use the release 514 WorkPlace Pro "Admin Tool" DbAdmin function to backup the running station and get the station as a .sns file to the computer. Use the DbAdmin function to convert the station from .sns to .xml. In the release 529 installation folder, use the AdminInstall command to start the release 529 version of the NiagaraD service. Copy the station folder containing the station to be upgraded from the release 514 stations folder to the release 529 stations folder. Start the release 529 AdminTool and open the Localhost. Highlight the station to be converted. Select the DbAdmin tab and use the convert local function to convert the station from .xml to .sns The converted station is now ready to be installed into the UNC that has already been loaded with I/A Series R2 release 529 software. This same procedure can be used to convert a 514 station to 532 by substituting release 532 for the release 529 references. above.