Building Automation Knowledge Base

Issue CX 9200 comm4 has 5 wires instead of 3, so the wires have to be jumpered to work with RS-485 Environment CX 9200 Xdriver Cause The issue with comm4 is that it is a 4 wire RS-485 interface and the xdriver ends up attempting to decode its own messages Resolution Sometimes this scenario will work, but other times values do not come across properly. Alternatives for this would be:  Use a media converter which may do a better job of jumpering the signal Move the xdriver to a different port

Issue A university customer has two personnel "types" - faculty/staff and student. They would like to link a different Personnel Manager profile to each type of personnel so that when the record is edited it opens using that profile. Can this be done? Environment CyberStation Personnel Manager Cause A university customer has two personnel "types" - faculty/staff and student. They would like to link a different Personnel Manager profile to each type of personnel so that when the record is edited it opens using that profile. Can this be done? Resolution Unfortunately, this is not a feature in the current (v1.93) or older CyberStation versions. You can open the Personnel Manager and then switch to a different profile and enter the personnel data, but that profile is not linked to the saved record. So, subsequent editing of the record will open in the default (current) profile.

Issue Is there any need to set up external alarms, trends or Time schedules for Programmable Xenta controllers if I use a LNS system? Environment TAC Vista LNS TAC Xenta 301, Xenta 302, TAC Xenta 401 TAC Xenta 281, Xenta 282, Xenta 283 Cause Differences in classic and LNS scenario Resolution No there are no need to set up any external alarms, the proprietary communication still works.

Issue What wall module (room sensor) to use for the TAC Vista series controllers Environment TAC Xenta 101, Xenta 102, Xenta 103, Xenta 104 TAC Xenta 301, Xenta 302, TAC Xenta281,  Xenta 282, Xenta 283 TAC Xenta 401 Cause Need to know what sensors to use Resolution Use the Sensor selection tool

Issue Unable to edit an object because fields are grayed out. Environment CyberStation Cause Object is edit locked. When an object is opened for edit the object is locked in order to give the process editing the object exclusive access to it. If an object editor shows an asterisk next to the name it indicates that the object is current under editing by another process. Resolution Wait for the process that has a lock on the object to complete. If the object is locked because of an unexpected Continuum shutdown while the object was under edit follow these steps to unlock it: In the Continuum Explorer right click the object's name and select properties. In the Current Status tab, click on the 'Force Object to Unlocked' button. Click OK to exit.

Issue When using an MNL controller to accumulate a usage total, the output appears to reset when the pulse rate gets too low. Environment MNL family of controllers Cause As designed, if the pulse rate is too low, the output goes to zero. The Pulse Counter function of the Binary Input object is designed to calculate a pulse rate value and a total pulse count value.  Due to mathematical restraints within the processor of the controller, if the interval between pulses is too low, the pulse rate output goes to zero.  Resolution The standard Lon controllers (MNL-50, 100, 110, 130, 150, 200, VAV) handle pulse rates down to a minimum pulse rate of 1 pulse per minute.  If the pulse rate falls below one pulse per minute, i.e., less than one OFF to ON transition per minute, the pulse rate output will go to zero until the next pair of OFF to ON transitions that occur within one minute. For the MNL-800 controller, the minimum pulse rate is one pulse every 4 minutes.

Issue How to find the installation log file when SQL install fails during installation of Vista Server. Product Line TAC Vista Environment Vista 5.x.x SQL Server 2005 SQL Server 2008 Cause The SQL Server is installed with a silent install and error messages can only be found in the created installation log file. Resolution SQL Server 2005 Browse to C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt SQL Server 2008 Browse to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt Search the file using keywords "error" and "failed" to find the nature of any installation problems.

Issue Error javax.baja.sys.NoSuchSlotException: textOverride when activating KitPx "Export' button for pdf in G3 version 3.6. Environment I/A Series G3 (version 3.6) Cause KitPx 'Export' button included on a canvas as part of a ReportPx.  Activating the 'Export' button causes the export to pdf to fail with the following exception ... javax.baja.sys.NoSuchSlotException: textOverride. Resolution Upgrade the pdf module to 3.6.38 or higher. The zip file (pdf-3.6.38.zip) can be downloaded from The Exchange Download Center.

Issue The requirement is to save a temperature taken at 10:00am, and to compare it with the temperature taken at 4:00pm. If the temperature was found to be lower at 4pm, then the output of the programmable object will be false, if the temperature is found to be higher, then the output will be true. Environment Sigma Programmable Object Program Prog Point Cause Assistance is required to create a suitable programmable object. Resolution The following programme will meet the requirements. 10 IF TIME = 10:00 THEN XINT = 1 20 IF TIME = 16:00 THEN XINT = 2 30 IF XINT UP THEN GOTO 50 40 GOTO 100 50 IF XINT = 1 THEN XFLO = POINT 1 60 IF XINT = 2 THEN YFLO = POINT 2 70 IF XINT <> 2 THEN GOTO 90 80 IF XFO > FLO THEN YINT = 1 ELSE YINT = 0 90 XINT = 0 100 IF YINT = 1 THEN RETURN TRUE "Higher" ELSE RETURN FALSE "Lower" Lines 10 and 20 establish if this is the first or second entry. Line 30 establishes that XINT has increased. Lines 50 and 60 store the two temperature values. Line 70 decides if the comparison should be made. Line 80 decides if the 4pm temperature is higher or lower than the 10am value.  

Issue Station was named incorrectly when first created.  Just copying the station folder or renaming the folder has no effect on the name of the station. Environment I/A Series R2 system (any version) Cause Station was named incorrectly when first created.  Did not realize name for the station did not match the desired naming convention used for the other stations in this facility. Resolution To rename a UNC station: Save the existing station database using the Admin Tool DbAdmin function. Use the Admin Tool DbAdmin function to get the station config.sys file and to convert it to an xml file (config.xml).  You will then have a config.sns and config.xml file in the existing station folder. Create the new named station folder under the stations folder under the current Niagara... installation folder. Copy the config.xml file from the existing station folder to the new station folder.  Copy any other folders that are under the existing station folder (graphics, etc) into the new station folder. Open the config.xml file (in the new station folder) with a TEXT or XML editor that can handle large files.  Two text editors that are know to work properly with large xml formatted text files are Notepad++ or EditPad.  These editors are both available for free via Internet. The existing station name typically first appears on lines 18 & 19 of the file.  Use the editor's Search and Replace function to globally change the existing station name to the new desired name.  Make sure that the there are no spaces or special characters in the new station name.  When specifying the existing station name, do not include the double-quote marks. Using the Admin Tool DbAdmin command, convert the edited config.xml file to config.sns. Use the Admin Tool "Install Station" function to load the edited station into the UNC.  

Issue Database Initialization Program Cannot Create a Database on the Server. Environment CyberStation v1.93 SQL Server 2008 R2 Windows 7 Pro Workstation Cause Database Initialization Program Cannot Create a Database on the Server. Resolution Server install went fine. CyberStation install went fine on new Windows 7 Pro Workstation. Could "see" server from the workstation. One or more of the items listed below maybe necessary to solve the problem: -Configure Write permissions on the server, specifically the folder where SQL server was installed.  -Make the workstation and the database server members of the same domain. -If using Windows Workgroup make sure the Workgroup in both the SQL server and the workstation machine have the same name, also make sure the user name and password is the same on both machines. -In the Continuum Database Initialization, in the server name field, enter the server's IP address instead of the name. -Also try creating another Windows user

Issue Tried to flash uprev the controller.  Continuum indicates "Initializing" but will go no further.  Environment BCX9640 Cause Unknown Resolution Method 1 Upgrade controller firmware using a RoamIO Method 2 Create a test Stand Alone Continuum DB. Bring the problem controller online on the test cyberstation. Flash uprev controller.

Issue The COM ports are defined and the communications works great but when the ENC is rebooted it is unable to start up the serial port (COM3), it says “COM3 is not a valid port”.  However, once the station is running COM3 can be typed in the drivers properties and it works fine.  Environment ENC, G3, Niagara Cause The station was loading the "Drivers" before the "Services".  The Services must come first to prepare the ports before the Drivers are loaded. Resolution Open the running station in Workbench, right click on Config and pull down to "Reorder".  Change the order to load the Services first, save the change and reboot the station. 

Issue XBuilder project will not download to the controller and there are no errors indicating other known issues with a download. It simply fails. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The Xenta controller may need to be recovered due to various software and hardware issues. XBuilder/Xenta firmware versions do not match Hardware or firmware failure requires hard reset Corrupted XBuilder project Fail-safe Resolution Check all software versions to ensure Vista, XBuilder, and Xenta Firmware all match. Correct any discrepancy by upgrading to the latest version. Try to download the XBuilder project, if that does not work...   Run in failsafe mode by jumpering pins 9 and 10 before power up. Try to download the XBuilder project, if that does not work...   From Hyperterminal DSH prompt do a FORMAT command. Correct the IP Address Download a new System Program to the controller. Try to download the XBuilder project, if that does not work...   Download a "blank" XBuilder project to ensure the project is not the root of the problem. Try to download the XBuilder project, if that does not work...   The controller may be bad. Replace the controller.

Issue Browsing the device in a Lonworks network tool, the SNVT shows the correct value, but in Vista, the value is incorrect and showing the default value. Environment NL220 and Lonmaker. Vista Cause The XIF file as been corrupted. This can occur sometimes if the System Plug-in has an error in the update process. Resolution The first thing to check is that the point in Vista is the correct point when related to the SNVT being referenced. If this is correct, then a good sign to look for is duplicate names in the Function block. If there are duplicate names this indicates a corrupt XIF. The only solution is to delete the device and re-add it. Once the device has been deleted, also remove the template so the new correct template is imported. If the template is not deleted, the network management software will use the same corrupt XIF file.

Issue 'Make Active' button grayed out in I/NET Configuration Profile Can not change my active I/NET (configuration) profile. Environment I/NET Seven 2.40 and above Cause The INetIoSrv.exe application must be shutdown before you can make any other configuration profile active.  This change was made in I/NET Seven version 2.40 and above. Resolution To enable this button the INetIoSrv.exe (IO Server) application must be shutdown.   Ensure I/NET, AMT and the IO Server are not running Start 'I/NET Configuration Profiles' editor Select desired profile and select Make Active If I/NET has every been running as a service on the PC, you will need to verify that the service is not running. You may need to re-register and stop the service.

Issue Remote Alarm Manager 2.0, RAM 2.0 when first started after an install starts up in Demo mode. Environment Sigma, Micronet, Vista Cause RAM 2.0 has been installed and the RAM Console is started, RAM starts up in Demo mode and gives a 2hr trial period. Resolution This is correct. The demo mode will disappear when the Input interface e.g. Sigma R4 is created and at this point the customers dongle or the engineers PC ID code is read.

Issue How many DUIC-5P-12V units can be used simultaneously on a MNL-800? Environment MNL-800 Cause Application-specific requirement for multiple contact status monitoring Resolution According to Smartware Technologies (www.smartwaretech.com), the makers of the device, up to four DUIC-5P-12V units can be connected to a MNL-800 simultaneously. 

Issue Microsoft Hotfix changes the HostId on I/A Series (Niagara) R2 and G3 Enterprise Server or Engineering workstations. See TPA-IA-11-0007.00 for details. Product Line TAC IA Series Environment I/A Series R2 and G3: All 32-bit versions of software installed on 64-bit versions of Windows 7, or Windows Server 2008 R2. Cause Microsoft recently released a hotfix for an issue that affects machines running x64 versions of Windows 7 and Windows Server 2008 R2, described in knowledge base article 2603229. The Windows registry contains entries to designate the organization and owner name that correspond to the computer. Each of these registry entries has a 32-bit and 64-bit version. Prior to applying the hotfix, when the OS was installed and setup for the first time, only the 64-bit version of the registry entries were written, leaving the 32-bit registry entries at the factory default value. I/A Series software HostIds are generated from multiple pieces of information gathered from the registry and hardware components of the host platform. The changes made by this Microsoft hotfix will cause the HostId to change on Windows 7 x64 or Windows Server 2008 R2 x64 machines running 32-bit I/A Series G3 or R2 software. Resolution See TPA-IA-11-0007.00 for recommended solution. NOTE: The TPA indicates that the patch is in the I/A Series G3 "Recovery Files" folder.  The files are version dependent and are located in the Release 3.4.64, Release 3.4.67,  Release 3.5.34, Release 3.5.39 or Release 3.6.31 folder, as appropriate for the specified version.  For other versions, option #1 must be used.

Issue SQL server install fails due to password complexity rules. Environment Microsoft SQL Server 2008 Vista 5.1.4 or higher Cause Microsoft SQL Server 2008 by default has higher password complexity rules then previous versions of SQL Server. Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters. Passwords must be at least six characters in length. Passwords must contain characters from three of the following four categories: Latin uppercase characters (A through Z). Latin lowercase characters (a through z). Base 10 digits (0 through 9). Non-alphabetic characters. Resolution When installing Microsoft SQL Server 2008 select a SA password that complies with the complexity rules.