Building Automation Knowledge Base

Issue Upgrading CyberStation from v1.7 to 1.93.  The instructions say to use \Continuum\CyberKeyWriter2.exe to upgrade the key (dongle). The program is not there. Environment CyberStation v1.7 Cause Upgrading CyberStation from v1.7 to 1.93.  The instructions say to use \Continuum\CyberKeyWriter2.exe to upgrade the key (dongle). The program is not there. Resolution CyberStation v1.7 had CyberKeyWriter.exe not CyberKeyWriter2.exe. CyberKeyWriter2.exe will be added to the \Continuum directory during the upgrade. Once the upgrade to the new version of CyberStation is done, use CyberKeyWriter2.exe and the Key Code from the Repair Dept to upgrade the key.  

Issue A UNC-6x0 has stopped functioning.  Since it is obsolete and cannot be repaired, will a Niagara R2 Soft Jace replace the UNC-6x0 and integrate directly to a Microsmart trunk? Environment Niagara R2 DMS / Microsmart Cause The UNC-6x0 was installed stand-alone.  There is no Enterprise Server nor other UNC available. Resolution The Soft Jace cannot be licensed for I/A legacy drivers including the Microsmart driver.

Issue Can Andover Continuum and Vista be installed on the same computer? Product Line Andover Continuum, TAC Vista Environment Windows computer with desire to install both iBMS (intelligent Building Management System)  Cause Single computer with desire to install both Andover Continuum and TAC Vista  Resolution Vista and Continuum cannot run on the same computer. Even if it is the latest Windows version. There are a couple of problems right up front, the License dongle, required by Continuum, can only be a single license dongle. In other words, only one dongle per computer. If Continuum sees a second dongle for license in the computer, there are problems. Second issue is the SQL, the two programs, Vista and Continuum have different install methods and therefore are not compatible. Continuum uses a V1/x strict compatibility install, where Vista uses the default Latin install. Note: Unofficially, sites have been reported as using VMWare to install both in the virtual environment. This of course is not supported, but has been done and is a possible solution. By the time the software is purchased and all possible problems have been addressed, it may be equal to using a second computer or laptop for the other system. Officially though, both systems on the same computer is not supported. 

Issue What are the pull up resistors on the universal inputs used for? Environment IOU modules i2 devices b3 devices Cause Information on the pull up resistors selection switch. Resolution The pull up resistors on the inputs are used to configure the input impedance, for example on the 810 series i2/b3 field controllers the input impedance can be 30.1K ohms referenced to 10.000 V or 10 M ohms referenced to ground with the input reference resistor switch set to OUT Pull up resistors are configured via the DIP switch located in the general area of the inputs, each small switch corresponds to the input with the same number. If an input is either a thermistor or a digital input, switch its input reference resistor switch to IN. (switch ON) If you require that the input be high impedance (10 M ohms), set its input reference resistor switch to OUT. (switch OFF)

Issue When saving a PE program that uses embedded Continuum functions such as SendEmail() , it errors when checking / compiling the program and shows the error message of "Unsupported feature".   Environment Netcontroller (CX9xxx) InfinetController(i1 , i2xxx) BACnet controller (BCX, b4920, b3xxx) Cause This happens when using the controller specific functions such as SendEmail() in the Program object not the InfinityProgram object. Resolution Create a new InfinityProgram object in the controller , copy the source code and save.  It will check successfully and save the program in the controller. After it is saved successfully, delete the problematic Program object from the controller.

Issue Error Generating License Request Cookie, Error code 0x1009 when generating license request under Windows 7 Generating a license request for the BACnet Service Tool under Windows 7 requires string value in the window's registry. Environment Windows 7 BACnet Service Tool Cause Windows 7 environment Resolution Follow the following procedure to add a new String Value for the ProductId. Click on the windows start button and enter regedit in the 'Search programs and files' field. Expand HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows. (for 32 bit machine). For 64 bit machine expand HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows. Right click on CurrentVersion and create a new String Value. Change the default name to ProductId and put any string in the value. NOTE: After the tool generates the license request, the path given to the location of the file must be pre-pended with C:\Users\usernamehere\AppData\Local\VirtualStore

Issue Creating new stations in Niagara G3 for an ENC and Enterprise Network Server (ENS) Environment Niagara G3 (all versions) Cause Limited training on Niagara G3 and working with an ENC-520 in the office Resolution To create a station (ENC or ENS): In Workbench, go to Tools > New Station to open the New Station Wizard. To load a station in ENC: Open the Platform of the ENC Open Station Copier, and copy the desired station into the ENC.  After the ENC re-boots, you can open the newly loaded ENC station To start an ENS: Open the Platform of the Ent. Server station Open the Application Director Highlight the desired station, and click Start.  When the station Status displays "Running", you can open the newly created Ent. Server station

Issue When running a batch file to run an application located at C:\ from a Workstation program, Windows 7 attempts to run the application in the following location. c:\progra~1\mocros~1\office14>plink.exe Environment Windows 7 CyberStation WebClient Shell Batch Cause Cannot successfully launch external application via a batch file using Plain English Shell command. Resolution Begin the batch file by specifying the fill path location.  For example: --------------------------------------- CD\ plink.exe ---------------------------------------

Issue Can the Roam IO/2 be used to create points in a controller? Environment Roam IO/2 Cause Ability to create points with the Roam IO/2 Resolution The Roam IO/2 device cannot be used to create points, but is designed to modify attributes of points that have been created by the Continuum system.

Issue Niagara R2 GxText to indicate override (change color magenta) when linked object is in an override condition. Environment Niagara R2 Cause Application Resolution There are various objects in the programLib jar that can be used to detect and indicate when an object is in an override condition. The hvac folder contains the AoCheckForOverride and BoCheckForOverride objects. These can be used to detect an override condition and set a boolean flag if an override condition exists. The programLib util folder contains the ColorOvBinary and ColorOvFloat objects. Connect the priority input to the object being overridden and the object will change color when an override condition exists. In addition, the Active Text can be modified as required and connected to a GxText on a graphic.  The linked GxText will change color when the override occurs.

Issue A 0-10 Vdc sensor will be wired into a MNL/MNB controller.  The voltage must be dropped from 0-10 Vdc to 0-5 Vdc to interface and read properly.  What's the part number for ordering the voltage divider used to achieve this task? Environment MNL controllers MNB controllers Cause Another manufacturer's sensor designed with a 0-10 Vdc control signal. Resolution The part number is AD-8961-220.  It is available for purchase via iPortal (http://iportal2.schneider-electric.com).  The controller analog input object would be set up as follows: Linput= 0.909 Vdc LScale= 0 Hinput= 4.545 Vdc HScale= 100  

Issue During Construction it may be required to use a temporary database to allow access control to function before the IP infrastructure is in place. Environment I/NET Seven Cause A temporary database has been used during construction. The end user has an existing database that the new links and doors must be added to. In some cases the temporary database may be required to be used while the building is occupied so a smooth transition between the two databases is required. Resolution Construction Phase Determine in advance the link information to be used for each new Xenta 527, and the full address for each door Determine who will access which doors within the new construction and add these individuals to new or existing groups accordingly Commission doors and add badges using the temporary database by using the available TAP on the SLI. If you use a crossover cable to connect to the Xenta 527, be sure to clear routing tables at the end of construction Ensure that each Xenta 527 has an available patch cable and Ethernet port installed Inform the IT department or installer that I/NET must have port 50069 open DO NOT leave the Xenta 527 plugged into the Ethernet port during construction If the building becomes occupied, add badges to the door using a temporary database connected via TAP If you are using multiple SLI's during the construction phase, it is important to ensure you are using only 1 access control Database.  Any other machine must have access control disabled to ensure cards are not removed from the system. If you have to add additional badges to any of the SLIs or change the temporary Database, you may need to do a station restore for the changes to take effect. Adding the New Links and Doors to the existing system Verify that the Ethernet port by each Xenta 527 is functional by using a laptop to "ping" the Primary Host workstation. The lights on the Xenta 527 may show active Ethernet communication before the new construction IP is connected to the Local network. Connect to each controller using your temporary database. Perform a station save.  If you have any issues, this will function as your restore point. Connect to the Xenta 527 and ensure that the reference Hosts and link information is correct. Connect the Xenta 527 to the Ethernet port and cycle power. At the Host PC, Select Edit>Host Computer>Network Configuration Save the new Xenta 527's, SLI's, SCUs and Doors Select Access>Tenant Add the Doors to the appropriate Tenant Select Access>Groups Give the appropriate Groups access to the correct doors Verify you have given access to all appropriate people.  You may wish to compare the System View of each door on your temporary to the System View of each door on the site database Connect to the controller Select Edit>Controller>Station Save To clear the old database you will need to take the controller to Boot. select Edit> Host computer> software Restore Load the Bin file to the appropriate controller, but hit cancel after 10K have downloaded Load the Bin file again, this time allow it to finish. Connect to the controller Select Edit>Controller>Station Restore Choose the SLI option Select Edit>Controller>Station Restore Choose the DPU option Select all DPUs and restore Once this process is completed test several badges. Repeat steps 12-21 for each SLI under this Xenta 527 Repeat this process for each Xenta 527

Issue What functions can you do in I/NET if you change the Windows users rights? Environment All versions of I/NET Seven Software Cause Changing the Windows users rights affects the way I/NET functions. Resolution   User Account I/NET Seven Operation Administrator Power User User Install I/NET Yes Yes No Remove I/NET Yes Yes No Upgrade I/NET Yes Yes No I/NET Configuration Yes Yes Yes         DBCreate Functions       Create db Yes Yes Yes Import I/NET 2X Yes Yes Yes Verify existing db Yes Yes Yes Remove existing db Yes Yes Yes Backup db Yes Yes Yes Restore db Yes No No Import Docutrend Archive Yes Yes Yes Upgrade db Yes Yes Yes         Seven Reports       View Yes Yes Yes Run Yes Yes Yes Configure Yes Yes Yes Save Yes Yes Yes Print Report Yes Yes Yes Mount Archive Yes Yes Yes View Archive Yes Yes Yes Run Archive Yes Yes Yes Print Archive Report Yes Yes Yes         Archive Configuration       Event Archive Configuration Yes Yes Yes Run Yes Yes Yes Trend Archive Configuration Yes Yes Yes Run Yes Yes Yes View Yes Yes Yes         I/O Server Configuration       Promote Filemaster Yes No No Demote Filemaster Yes No No Promote Client Yes No No Demote Client Yes No No   There are two components of security available to users of I/NET Seven: I/NET Seven passwords and Microsoft Windows user accounts. I/NET Seven passwords are specifically aimed at limiting a user’s access to features and functions within the I/NET Seven system. The restrictions imposed by I/NET Seven passwords are application-specific (i.e., they only affect the I/NET Seven system) and do not provide a replacement for domain security methods. Microsoft is very clear about the importance of limiting permissions to users in a network environment. The user account permissions that are standard in Windows 2000 and Windows XP allow full management of the computer to users with “Administrative” group membership or any group containing administrative permissions. The “Power User” group permissions allow users to install programs but restrict what these users can do to the operating system. The “User” group is the most secure because its operators cannot modify operating system settings or other users’ data. Microsoft clearly states that operators assigned to the User group may have trouble running legacy programs. This should pose no problem for I/NET users since I/NET Seven has been specifically developed to run on the Windows 2000 and XP operating system. Most functions of I/NET Seven including general system operation, AMT (alarms, messages, and transaction) processing, reporting (Seven Reports), and archiving are available to an operator assigned to the User group or any group with those permissions. However, these operators cannot install I/NET Seven or delete or upgrade its database. Seven Reports is password-protected but can be configured within I/NET Seven to allow automatic logon to operators of a Host PC. The above spreadsheet shows the functions/operations that can be performed by members of the Administrator, Power User, and User groups. For further information about Windows security, please refer to Microsoft Windows online help for more information about user accounts, permissions, and Microsoft Management Console best practices". https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc750076(v=technet.10)

Issue The wrong version of the .xif file is being used. Environment NL220 LonMaker Vista LonWorks Device XIF Cause The numbers/types of SNVTs in the file have changed. SNVTs have been added to an Xenta 500/700/913. Resolution Ensure that Vista Server is running. In Vista System Plug-In, in the LNS Network pane, right-click the LonWorks device object. Click Replace Click Next Keep default neuron ID. Click Next Select Upload From Device Click Next Click Ok Select the LonWorks device object and check that the SNVTs are available in the object view window

Issue There are times when random events require adding an exception for an Infinity schedule for the 2nd and 4th Thursday only The recurrence may also be for a certain day, week, month or year. Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Bacnet schedules/calendars and programs like Microsoft Outlook allow scheduling for the 2nd and 4th Thursday, so it seems like this should be allowed in the Infinet schedules. Resolution In Infinity type schedules contained in Netcontrollers and infinet devices, there isn't a way to automatically ask the schedule to come on at a given time based on the 2nd or 4th Thursday, i.e. a recurrence of a day, week, month or year. The specific date needs can be accessed by the yearly view and configured manually.

Issue Is it necessary to create a separate network for a site even if it is the only site outside of the eastern time zone? Environment Continuum UTC Time Zone Continuum Networks Cause Site is in a different time zone than the rest of the sites on the being brought into the Continuum system. Resolution While schedules can be mitigated locally and alarms be stamped with the time of occurrence with respect to the local time zone, neither of these are optimal ways to run Continuum.  Extended logs are not manageable when points are being logged in a controller in time zone A and then downloaded by a Cyberstation in time zone B. For this reason it is not advisable to have controllers that reside in different time zones under one Continuum Network.  Note: Extended logs are stored in the db with UTC time stamp and are interpreted by Cyberstation via reports or groups.

Issue A BCX PE program does not read / mirror value from its child 3rd party MSTP device (ALC IO6126).  The exact same PE program in workstation reads / mirrors value from the same 3rd party MSTP device correctly. When the PE uses just ReadProperty(BACnetDevices\BNet_2778\Dev100\Supply_temp), controller error log file shows message of "  0x8000001e - BACnet request timeout " & " 0xfffd001f -  BACnet error ".   Environment BACnet (BCX4040) ,  3rd party MSTP device ( ALC IO 6126 / IO6126 / Viconics ) Cause Case#1) The BCX's Foreign Device configuration page ( Foreign Device table ) was set up to have an IP address of a BBMD BCX on the same IP subnet by mistake. Case#2) The MSTP devices are consuming MSTP network resource by trying to send the token to non-existing MSTP device all the way up to ID127 as the BACMaxMaster attribute is set to 127. Resolution Case#1) BCX's Foreign Device Configuration / Table should be set up to have the IP address of the BBMD on the different IP subnet ( not the BBMD on the same IP subnet ).  Remove and zero out the Foreign Device Table of the problematic BBMD.  Case#2) Change the BACMaxMaster from the default value of 127 to the MacAddress of the last MSTP device on the network.

Issue Received error message indicating "Neuron application has stopped running.  Reinstall the NXE application file." "Service" LED on controller is solid red. Environment MNL family standard controller: MNL-5xx, MNL-10xx, MNL-15xx, MNL-20xx, MNL-11xx, MNL-13xx Cause MNL family standard  controller Neuron processor application PROM has failed or has been damaged. Controller installation manual states that if the Service LED is solid red, that the Neuron processor application is not running.  The document also indicates that the controller is not field repairable because the Neuron application is not field replaceable. Resolution Replace the controller.  The device is not repairable.

Issue After replacing an older revision MNL controller with a new one, WorkPlace Tech is unable to download the existing application file into the new controller reporting an error "The selected device is Invensys IA(x) ... controller, the application requires Invensys IA(y) ... controller".  In this error message the controller type info (...) will be the same in both parts of the message but the IA(x) and IA(y) part of the message is different.  Environment MNL-50 MNL-100 MNL-110, MNL-130, MNL-150, MNL-200, MNL-Vx Cause Replacement controller is of the same type but of a different version. This issue occurs any time a version 2 controller is replaced with a version 3 controller. for example, this error will occur if a MNL-V2RV2 controller is replaced by the newer version, MNL-V2RV3.   Resolution Open application in the WorkPlace Tech Tool. Open the Hardware Wizard and click the [Back] button to open the Controller Selection page. When the Controller Selection page has been opened, you will note that the [Older] tab has been displayed with the existing controller type displayed. Select the tab corresponding to the controller type, for example if replacing a MNL-V2RV2 controller, select the MNL-VAV tab. Select the model of the replacement controller, for example when replacing a MNL-V2RV2, the replacement is the MN-V2 [MNL-V2RV3]. Click the [Next] button to complete the selection of the replacement controller type then click the [Finish] button to close the Hardware Wizard. Recompile the application and download it to the replacement controller. If the controller is part of a LON network that has been commissioned by a LON Network Management tool, it will be necessary to replace the existing device object and commission the new controller.

Issue Browser Niagara Series G3 does not prompt user for login Environment Niagara G3 Cause User "guest" account if enabled, provides station access from a browser with no login required. Resolution If "guest" account is enabled, the password assigned to guest (if any) is ignored when accessing the station via a browser. However, if opening the station in Workbench as user guest, the password for guest is checked. Solution: Disable guest account