Building Automation Knowledge Base

Issue The A and B Channels used to communicate to Sublan devices need to interface with FOI (Fiber Optic Interface) devices, but not sure what speed it communicates on or what setting it should be. Environment I/NET Seven Controller Lan on a 7793 MCI. Cause Setting up a 7793 Controller to communicate to a FOI. Resolution On a 7793 MCI, there are several ports that are used for communication to various devices. These ports are: A standard synchronous RS485 controller LAN Port. Two standard asynchronous RS485 sub-LAN Ports. Two asynchronous RS232 ports, one used for the HHC Console and the other for Direct Connect to a PC. An optional plug on-board with an RS232 synchronous connection used for an external modem.

Issue Adding/Removing areas to personnel objects via XSTL file in Personnel Import Utility Product Line Andover Continuum Environment CyberStation Personnel Import Utility CX99xx CX9702 CX9680 ACX57xx ACX7xx Cause Need a way to add/remove areas to personnel objects via the XSLT transformation file in the Personnel Import Utility. Resolution Use the choose/when tags to conditionally assign the area based on the value of another attribute. In the example below the Lab1 area is ONLY assigned to personnel objects whose state of residence is Massachusetts while the Lobby area is assigned unconditionally. This method can also be used to remove areas from the personnel object, as the record is completely overridden on import, not assigning an area has the same effect as removing it. <AreaLinks> <AreaLink> <AreaId><![CDATA[Root\Lobby]]></AreaId> <SchedId>Full Path To Schedule Here</SchedId> <State>Enabled</State> <Preload>False</Preload> <ClearanceLevel>0</ClearanceLevel> </AreaLink> <xsl:choose> <xsl:when test="StateOfResidence='Massachusetts'"> <AreaLink> <AreaId><![CDATA[Root\Lab1]]></AreaId> <SchedId>Full Path To Schedule Here</SchedId> <State>Enabled</State> <Preload>False</Preload> <ClearanceLevel>0</ClearanceLevel> </AreaLink> </xsl:when> </xsl:choose> </AreaLinks>

Issue The "Log Backup" tab doesn't appear under the "properties" dialogue window for Vista Server. Environment Vista 4.3 or newer Vista 5.X.X Cause The "Log backup" tab is not displayed when the option "Custom" is selected in TAC Vista server setup, under the SQL Server tab. As stated in the help file for Tac Vista Server setup:  "When you select Custom SQL configuration, the integrated log database backup/restore functions in TAC Vista will be disabled". This means that a backup will have to be carried out in SQL Studio (Express). Resolution 1. Download and install SQL management studio express from Microsoft website. 2. Start the program and find the database taclogdata (or the name you have chosen for the database in TAC Vista server setup). 3. Right-click on the database; select "Tasks" and then "Backup". 4. In the dialogue window that appears, check the details and select an appropriate destination for the backup file. 5. Click "OK". The SQL database should now be backed up.

Issue Excessive alarms coming into Vista Workstation from change of state objects Environment Vista Cause Alarm parameters may be set to be too sensitive for the hardware they are monitoring. Resolution Change of State Parameters: Right Click on the Change of State Object Select Properties Click on the Alarms Tab Change the High and Low Alarm limits to decrease potential alarms Increase the minimum change to increase the deviation required for an alarm to trip.

Issue Some SNVTs from .XIF file are not added to TAC Vista SNVT with - in the name is not added in TAC Vista Some SNVTS from the .XIF file are missing in TAC Vista Environment TAC Vista Cause TAC Vista can't handle dashes (-) in object names. If the SNVT has a - in the name it will not be added in TAC Vista Resolution Open the XIF file with a text editor Change the name of the SNVT (take out the -) Save the XIF file and re-read it into TAC Vista.

Issue How do I upgrade a CX9400 to a 9680? Environment Continuum CX9400 9680 Windows XP Windows Server 2003 Windows Server 2008 Cause Continuum Versions 1.90 and below do not have a direct procedure for upgrading a CX 9400. Resolution Upgrade Continuum to 1.91 or above which allows a selection to upgrade the CX 9400 to 9680. This procedure makes the appropriate changes to the database.  Upgrading a CX 9400 without the direct convert option (Continuum 1.90 or less) has to be done manually by exporting and importing dump files. There are a differences between these 2 controllers and there is a potential for database problems. Manual manipulation requires a large amount of work which takes a considerable amount of time.

Issue What is the difference between the NL220I and NL220M dongle. Product Line Other, TAC Vista Environment Newron NL220 Cause There are two types of NL220 dongles, (install) and M(maintenance).  Each type have their own specific functionality.  The correct dongle should be selected to avoid issues at a later time. Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case. Resolution Newron NL220 functionality.   Administration (Engineering) mode will allow the following (NL220I): Creating a project Adding network infrastructure devices Adding LonWorks devices – application specific devices as well as programmable devices Installing and commissioning network infrastructure devices Installing and commissioning LonWorks devices Creating SNVT and tag bindings Configuring devices using the generic browser and device specific plug-ins Managing devices Deleting devices Replacing devices Maintenance mode will allow the following (NL220M): Configuring existing devices using the generic browser and device specific plug-ins Managing devices Replacing devices   Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case.

Issue Have two LNS databases and need to share values between them. Environment Lonmaker Newron NL220 Vista Cause As the two LNS networks are not connected you cannot bind values between them. You can use a Object transfer in Vista or a Loytec L-Proxy controller Resolution The main difference between the two methods is the object transfer is PC based and the Loytec option is field based.  Object Transfer option: Add an object transfer as described in the Chapter 14 of the TAC Vista Technical Manual. L-Proxy Loytec controller option: This product will reside on both LNS channels and can be setup to transfer values across networks. Here is a link to the product . From here scroll down to find the L-Proxy Datasheet

Issue Alarms in UNC are not archiving to the Enterprise Server. Environment I/A Series R2 Universal Network Controller (UNC) and Enterprise Server Cause The UNC station and Enterprise Server station has their NotificationService 'archiveMode' property set to 'archive_disabled'. This is the default selection and it prevents notification from happening. Resolution Change the default settings in the UNC station and Enterprise Server:  Set the UNC station's NotificationService 'archiveMode' to 'archive_remote'. Set the Enterprise Server station's NotificationService 'archiveMode' to 'archive_local'. (The “archive_local” selection is valid only if the station is running the DatabaseService) The following have to be also correct in order for alarms archiving to happen: AddressBook entries should be properly setup in the Enterprise Server and UNC stations. Refer to Page 1-15 and 1-16 of the Niagara Standard Programming Reference for further information.  Supervisor checkbox in the UNC's NotificationService 'alarmArchiveAddress' property should be checked. NotificationClass(s) in the NotificationService container in both the UNC station and the Enterprise Server station have to be the same.

Issue How can I tell what versions of .Net are installed on my PC?  When I look at the Add/Remove programs, the C:\Windows\Microsoft.NET\Framework folder and the system information report I see different versions. Environment CyberStation Continuum Database Server WebClient MicroSoft Windows Windows XP Windows Vista Windows 2000 Windows Server Cause When installing Continuum Cyberstation or WebClient it is important to know what version of Microsoft .NET is installed on the workstation PC or server machine.  It can be difficult to tell which version of MicroSoft .Net are installed on a CyberStation PC, WebClient server or Continuum database server hardware. Resolution The following link describes how to determine which versions and service pack levels of the Microsoft .NET Framework are installed. http://support.microsoft.com/kb/318785

Issue Getting error when adding 2 doors, Infinity controller error value does not apply to attribute Environment CyberStation CX9900 CX9680 ACX781 ACX701 Access Control Cause Version of the controller is 2.1x which is an Infinity version Resolution Chip change the controller to the correct Continuum version, 1.500012

Issue Problems with alarms or configuring alarms in Vista Environment TAC Vista Workstation Cause Improper alarm configuration Resolution Here are steps to configure each part of the Alarm  in Vista. Change of State Object - This is the source of the alarm. Right click on a folder in Vista and select New > Object > Change of State Name the object Double click on the object to modify it Provide a description of the alarm and set a priority level if required. Click on the Object Tab and select the Object to Monitor and the Reference property Click on the Alarm Tab Select an Alarm processing control.  These should be located under the TAC Vista Root object. The default is $Alr_Cntrl Fill in the appropriate text field.  Note: "Text for" fields are text issued as the result of the alarm. "Triggering" text should only be used when monitoring a string value. Set Low and High Limit for the alarm to occur Set Minimum change: This is the smallest deviation required to trip an alarm when using numeric values. Alarm Receiver Objects - These objects route alarms that are intended to go outside of Vista. There are 3 types: Print, file, and Mail (email) Right click on a folder in Vista Workstation and select New>Object>Alarm Receiver - E-Mail (or applicable type Name The Object Double Click on the Object to modify it In the General Tab provide the description and appropriate information for your alarm type (email recipient) In the Alarm Fields Tab, select the fields you wish to appear in the printout or email If you are using Alarm Receiver - Video you will need to set the video settings in the General tab and select cameras to record in the Video Cameras Tab Click Okay Alarm Control Group - This allows us to control distribution of an alarm.  Multiple control Groups will allow multiple distribution lists.  From Vista Workstation, right click on the TAC Vista folder (Alarm Control Objects can only be created here) Select New > Object > Alarm Control Name the Object Double Click on the Object to modify it Enter a description Click "Add" and browse to the desired Alarm Receivers Click on the Acknowledge tab and configure appropriate parameters Click on the Time Control Here you can browse to a time variable that will determine when to use the Alternate Receivers list Add Alternate receivers Click OK

Issue Trying to control the deadband of a Loop object Environment CyberStation BCX I2 B3 Cause There is no deadband attribute of a Loop object in Continuum Resolution What is exposed are the PID parameters: Controlled Variable Controlled Variable units COV Increment Proportional Value and Units Integral Value and Units Derivative Value and Units Bias Action Having the system in control for each mode is efficient unless the building itself is not very energy efficient. If that is the case, then I would limit any optimal start times to no more than 2 or 3 hours. If no optimal start/stop is being used, then just enabling and disabling the loops within his +/- 3 deg window should be sufficient.

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 Forced Door and Door Open Too Long Alarms not Showing up in Controller Summary Environment I/NET Cause Request to exit device is being activate triggering  valid entry rather than a forced door. Incorrect Message Type Settings Incorrect Masking Settings Resolution Request to exit device is being activate triggering  valid entry rather than a forced door. Connect to the controller Select Edit>Controller>Doors Modify the door Change the Door Release Switch to "None" Test The door Re-set the Door Release Switch to correct setting and troubleshoot hardware Incorrect Message Type Settings Connect to the controller Select Edit>Controller>Doors Modify the door Verify that the Message type for Forced Door and DOTL are set to "Alarm" Verify the Masking for the Door Test The Alarm Incorrect Masking Settings Connect to the controller Select Edit>Controller>Resident I/O Modify the Reader Point for the door Ensure that making is selected and that there is a message priority and an Alarm Priority. (This should match the previously noted settings from the Door editor) Test The Alarm

Issue Video is not displaying or it's displaying with a black screen when using Continuum 1.81, 1.90 and 1.91 with Digital Sentry 4.3 or 7.x Environment Continuum 1.81 Continuum 1.90 Continuum 1.91 Digital Sentry Windows XP Windows Server 2003 Windows Server 2008 Cause Continuum 1.81, 1.90 or 1.91 is incompatible with the Digital Sentry API 4.3 or 7.x  Resolution Use the Digital Sentry version 4.2 Download and install DSConnex hotfix CAUTION: Installing the hotfix for Digital Sentry 7.x slows down videolayout and videomonitor with Digital Sentry units that have v4.2 installed. Increase the amount of virtual memory on the PC to 4096. NOTE: the files that were contained in the hotfix were incorporated into 1.92 and above

Issue DC1100 / DC1400 Outside Occupation message is displayed and Plant is not operating. Environment DC1100 / DC1400 Discrete Controller. Cause Heating Time Schedule is in an OFF period. Remote Override has been activated. Controller Current Time is incorrect. Room Sensor does not display a value or is not listed. Resolution Check Heating Time Schedule OFF time. If Heating Time Schedule OFF time is earlier than the Controller Actual Time then condition displayed is correct. If Heating Time Schedule OFF time is later than the Controller Actual Time then condition displayed is incorrect. Check presence of Drayton DC1100 Remote Switch Unit. This can be confirmed by presence of wire connected to Controller Terminal 9. Check / amend setting of Drayton DC1100 Remote Switch Unit in order to test accuracy of message displayed. Check presence of bespoke Remote Override Control Unit This can be confirmed by presence of wire connected to Controller Terminal 9. A 33K Resistor should also be visible wired between Controller Terminal 9 and Terminal 7 Check / amend setting of Remote Override Control Unit in order to test accuracy of message displayed. N.B. The Drayton DC1100 Remote Switch Unit is common to both DC1100 and DC1400 installations. If the DC1100/1400 is used as an Optimiser, check the room sensor is connected and reading. Rectify the issue, a coldstart may be required to reconfigure the controller.

Issue Using an Analogue Input card to display Digital Inputs when no Digital Input channels are available. Environment Sigma Analogue Input cards. Cause There are no Digital Input channels available. Resolution An Analogue Input card cannot be used directly as a Digital Input card. A work around for this is to configure an Analogue Input to act as a Digital Input. Programme an Analogue Input object in Sigma. In Sigma System Manager create a lookup table, using an appropriate free number. Input Output 0 1 15 0 20 0 Add the above Lookup table to the Analogue Input object. In Sigma System Manager create a Short Text such as On/Off =%2.f Add the new short text number to the Analogue Input object. Across the Analogue Input channel fit a 1000 ohm resistor, this will be in parallel with the Digital Input connections. When the Digital Input changes state, Sigma will display either 1 or 0.

Issue TGML Script has stopped working after upgrading to Vista 5.1.5 Nothing happens when clicking on a button in a TGML graphic - it worked in Vista 5.1.4  Environment Vista 5.1.5 Graphics Editor TGML 1.1.5 Cause  The TGML language is now case sensitive to increase performance, which may result in upgrading issues. Resolution Check the script and ensure that all keywords such as Visible and Hidden have capital letters if the corresponding object attribute starts with a capital letter.

Issue What is the procedure to upgrade an existing I/A Series Enterprise Network Server to a newer release of the G3 software? Environment Existing I/A Series G3 ENS installation. Newer release of the G3 software to be installed. Cause Upgrade Resolution Back up existing ENS station. Open the Application Director in the existing version of WorkBench and stop the running station then close Workbench. Install new release of the I/A Series G3 software by running the setup.exe program from the distribution file set (expanded zip file or CD). If the installer prompts to allow copying of settings from previous installation, allow the copy to proceed. At the end of the installation process, allow the installer to start the new Niagara Daemon but not Workbench. Under the Stations folder in the old installation of the G3 software, locate the folder for the station that was being run. Copy the entire folder locate in step 5 from the Stations folder of the old installation to the Stations folder of the new installation. Start the new version of the Workbench, then use the Application Director to start the copied station.