Building Automation Knowledge Base

Issue Connecting from a TAC Vista Remote Workstation says "Ensure that TAC Vista Server is started" error, even though DCOM is set correctly Environment Vista Server Remote Workstation PCs in a network workgroup, not a domain Cause Connecting a TAC Vista Remote Workstation to a TAC Vista Server where both PCs are in workgroup rather than a domain. Resolution It is important to set the right DCOM permissions AND also remember that the Administrator password has to be the same on both PCs.

Issue New Door Attributes KeyPadString and KeyPadCommand in ACX57xx Environment Information about the new door attributes and configuration helps users with the capability. Cause ACX57xx Continuum V1.82 Resolution New Door Attributes KeyPadString and KeyPadCommand in ACX57xx in latest versions of Continuum Requires versions of Continuum V1.82 or above and Rev 1.1xxxxx ACX Entering an Input String at a Keypad for Use in PE Programs From a keypad connected to an ACX2 door, you (the user) may also send additional data to the controller, which in turn passes it to a Plain English (PE) program for execution in an Andover Continuum control application. This capability enables you to use the keypad to send input to a PE program for any purpose. For example: A user can enter a string that a PE program uses to turn lights or fans on or off, or to control other HVAC equipment. A user can enter a string indicating the user’s purpose for entering an area. The PE program can capture this information as input to a PE program for tracking reasons for activity in a secure area.  Handling String Input at the ACX2 controller Before you can use the keypad for PE program input, you must create a Plain English program that processes the string entered at the keypad and returns a value to the system based on the entry. The ACX2 door contains two attributes that are used by the PE program KeypadString door attribute. Your PE program reads this attribute to obtain the content of the string entered at the keypad. KeypadCommand door attribute. Your PE program sets this numeric value to provide feedback via the reader/keypad LEDs to the person entering the keypad code about the status of the operation. Other commands are also sent to the door via the KeypadCommand attribute such as enabling or disabling Keypad Input. Entering String Input from Keypad The process for entering string input at a keypad has the following steps: The user presents a valid access card and/or PIN (if a PIN is required) to the door reader. The controller for this reader accepts the user’s credentials, and the door unlocks. Within three seconds of the door unlocking, the user enters two consecutive asterisks ( ** ) at the keypad to enter escape sequence mode. The keypad LED flashes slowly to indicate that it is waiting for input. The user enters a numeric string of up to 30 characters (not including the two asterisks), and then terminates the string with the pound sign (#). For example: **10# or **6986310# The door makes the string available to a PE program via its KeypadString attribute. Entry Rules for String Input The following rules apply to using a keypad connected to a door to enter string input:   After the door unlocks for a valid access, if more than 3 seconds elapse before the user enters two asterisks, the door exits escape sequence mode. The user must begin the process for string input again. If a user enters more than 30 characters (not including the first two asterisks), the door detects when the 31st digit is entered. The door then replaces the 30th character with T to indicate Tamper, and sends the string to its KeypadString attribute (no # is needed). Subsequent characters entered as part of the string are ignored. For example, if the user enters **123456789012345678901234567890123, the door sends 12345678901234567890123456789T to its KeypadString attribute. The user can enter asterisks within the string if needed. These asterisks are converted to periods when sent to the door’s KeypadString attribute. For example: 69*8*6310 is converted to 69.8.6310 when sent to the door’s KeypadString attribute. If more than 4 seconds elapse between keystrokes, the door exits escape sequence mode. The user must begin the process for string input again. If a user presents an access card to the card reader while the door is in escape sequence mode, the door exits escape sequence mode. The user must egin the process for string input again. PE Feedback to the Door After the PE program receives the string input and interprets its value, the PE program assigns an appropriate value to the door’s KeypadCommand attribute. One of the following values is transmitted back to the door through its KeypadCommand attribute: 0 - Disable keypad Input at the door. 1 - Clear string. 2 - Recognize the escape sequence entry (success). 3 - Do not recognize the escape sequence entry (fail). 255 - Enable keypad Input at the door. NOTE: Clearing the string in the door using the Clear String command is recommended after each string input in escape sequence mode. Based on the numeric value returned to the door through the KeypadCommand attribute, the PE program uses the reader LEDs to indicate to the user whether or not the string input is valid or invalid. The LED pattern to indicate valid/invalid entry is the same as the selected access control LED pattern used to indicate valid/invalid card and PIN entry. Sample PE Program The PE program in the following example is used to unlock a door for unrestricted access for the amount of time specified in the Keypad Input String. For instance, at the door, the user enters 100*3600, the "*" gets translated to "." (period) so the keypad input string contains 100.3600. The program recognizes 100 as the door timed unlock code and 3600 as the time to unlock the door for (in seconds, 3600 is the number of seconds in an hour), thus entering 100*3600 at the keypad instructs the PE program to unlock the door for an hour. 'This program processes the 'Timed Unlock' keypad code (100) entered at a door's keypad 'The form of the code is 100.xxx where 100 is the command identifier and xxx is the amount of time 'to unlock the door for. String Str Numeric KypdCode, DrUnlockTime, SeparatorPos Line Init   Jetway1 KeypadCommand = 255 'Enable door for keypad input string   Jetway1 KeypadCommand = 1 'Clear any previous keypad input string Goto WaitForKypdCode Line WaitForKypdCode   'Wait here until something goes in the keypad string   If len(Jetway1 KeypadString) > 0 then Goto ProcessKypdCode Line ProcessKypdCode   'The string should contain 2 fields separated by a period   'Get the keypad code identifier which is to the left of the separator   SeparatorPos = search(Jetway1 KeypadString, ".")   Str = left(Jetway1 KeypadString, SeparatorPos)   KypdCode =StrToNum(Str)   'Now get the unlock time value which is to the right of the separator   Str = right(Jetway1 KeypadString, (len(Jetway1 KeypadString) - SeparatorPos))   DrUnlockTime = StrToNum(Str)   'The only keypad code this program handles is the time unlock (100)   If KypdCode = 100 and DrUnlockTime > 0 then Goto UnlockDoor Else Goto InvalidKypdCode Line UnlockDoor   Jetway1 KeypadCommand = 2 'Flash the valid access LED pattern to give   'feedback that the code has been accepted   Jetway1 TimeUnlock = DrUnlockTime 'Unlock the door for the time specified   'in the keypad code   Goto ClearStr Line InvalidKypdCode Jetway1 KeypadCommand = 3 'Flash the invalid attempt LED pattern to give   'feedback that the code is invalid   Goto ClearStr Line ClearStr   Jetway1 KeypadCommand = 1 'Clear the keypad input string   Goto WaitForKypdCode

Issue Getting error message in Vista that Menta is in 'stand alone' mode and cannot edit the .MTA Environment Vista Menta Cause This happens usually when Menta has previously been installed on the system in a "stand alone" fashion and then Vista was installed at a later time. Resolution Go to Start > Run and type "regedit" to open the Registry Editor Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > TAC > TAC Menta Double click the key named StandAlone. Change the value data to "No"   For a 64 bit OS, the path in the Registry Editor is HKEY_LOCAL_MACHINE>SOFTWARE>Wow6432Node>TAC Menta

Issue Tried to add a holiday event to a Niagara R2 calendar and received the error: "Cannot add entry" /tridium/props/error.properties#error.E_CALENDAR_FULL Environment Niagara R2 Cause There is a 50-event limit hard coded into the R2 schedule object. Resolution One solution is to use multiple Calendar objects.

Issue Issues with some portions of Vista 5.1 on Microsoft Windows Vista Environment Microsoft Windows Vista TAC ToolPack TAC Signature TAC Webstation TAC OPC Server for Danduc Cause Not all portions of Vista 5.1 are supported on Microsoft Windows Vista. Resolution While TAC Vista supports Windows Vista in release 5.1.0 the following programs are not supported: TAC Toolpack TAC Signature TAC Webstation TAC OPC Server for Danduc Note: This is still true for version 5.1.1 despite this only being stated in the Vista 5.1.0 release notice.  

Issue Site 0 on DLA Applications Environment I/NET site Cause For future expansion of the system, address 0 has been reserved when implementing DLA (Distributed Link Architecture). This causes the Host to distinguish when making contact with an NPR, whether it is set up for DLA or not. There are certain flags that are set in this configuration internally by each device on the way it will communicate with other Hosts and NPRs Resolution It is recommended that address zero("0") be used for Non DLA applications and 1 to 63 for DLA. This should be implemented just to avoid conflicts with existing sites. Furthermore, it is also necessary to clear out the Routing tables for each device that this is being incorporated on.

Issue Pin Pad Functionality on HID Readers Environment I/NET site with HID Pin Pad Cause Incorrect wiring in the PIN Pad Resolution Using the PIN Pad function in HID Card Reader applications requires that the D1 and D0 wires be terminated on terminal 3 and 5 respectively. If regular door modes are being used i.e. Secr/Unlk/Lock then this does not affect how the DPU interprets the card read. If PIN is being used for Arm/Disarm or gain entry, then this termination needs to be addressed. If terminated improperly, a valid card read will be seen at the reader but a Deny Entry t/o will be registered in the Transaction Window of AMT and the desired function will not be accomplished.

Issue Trend Log Values in Xenta Server are not displayed in Trend graph but there are values if you select view data. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause If the PC time and the Xenta Server times have gotten off, it may appear that there is no data for the selected time interval. Resolution Check that you have to same date and time settings in the Xenta Server and in the PC that you are viewing the trend chart in.

Issue In trend log page in Xenta Server I only see the name for one of the Y-Axis even though I have defined the name and range for both Y1 and Y2 Environment Xenta Server Xenta 511, 527, 711, 731 Trend Chart Cause If you want to display both Y-Axes 1 and 2 you have to have at least 2 logs in the chart. Resolution To see the 2nd Y-Axis you have to use it. Select the log that you want to use the 2nd Y-Axis and change the Display settings.

Issue Menu pull downs missing from WorkPlace Tech 5.7.1 after installing the Belkin Bluetooth adapter. Environment WorkPlace Tech 5.7.1 Belkin Bluetooth adapter Cause For Visio 2007, un-check the box for Send to Bluetooth. For Visio 2003, un-check the box for COM add-ins. Resolution Field offices have reported an issue after installing the Belkin Bluetooth adapter for use with the MNB-ROAM-IA. The problem is that Workplace Tech menu pull downs are missing (Project, Application); additionally, all of the Workplace Tech options are missing from the Tools pull down ( Configure Communications, Browse Devices, WorkPlace Commissioning Tool, etc.) One result of this problem is that the user cannot re-configure WorkPlace Tech for LON communications, or any other BACnet communications. WorkPlace Tech 5.7.1 with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Trust Center Select Add-ins. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for Send to Bluetooth. Click OK to apply. Close Visio. Open WPT, all menu items should be there. Workplace Tech 5.7.1 with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Click OK to apply. Close Visio 2003. Open WPT, all menu items should be there.

Issue Is there a way in a Niagara R2 UNC station to display the current date and time on a graphic? Environment Niagara R2 UNC station Cause There is a standard program object that can be used to expose the elements of the UNC time and date. Resolution The program object is found in the remote library under tridiumx in the "LIB" jar file.  The program object is "DateTimeDiscreteComponents.sns" found under the muxDemux folder in the "programObjects" folder. To use this object, copy it to the desired container in the station database then create links to the desired date or time elements. The following elements are exposed as values that can be linked to other similar type objects or to GxText objects: dateTime (as DateTimeType) date (as DateType) time (as TimeType) timeAmPmString (as String) weekday (as WeekdayEnum) month (as MonthEnum) SecsToday (as FlowtStatusType) The following elements are exposed as integers that can be linked to other objects that accept integer value links or to GxText objects: year day hour minute second When considering the use of this program object, remember that for best performance there should be no more than 100 custom program objects used in a UNC station database.

Issue How many trended points can exist in a Niagara R2 Enterprise Server station? Environment Niagara R2 Enterprise Server Cause Information on the number of trended points allows in a Niagara R2 Enterprise Server station. Resolution There is no “recommended” point count or intervals. Each trend sample gets added to the app database (located in the C:\niagara \stations \app folder). When this folder gets too large, the Enterprise Server's performance will be affected. The work around is to move or purge the app folder on a periodic basis.  

Issue Having issues accessing a remote BACnet network on a Niagara R2 UNC. Environment Niagara R2 UNC BACnet network Cause Configure the Niagara R2 UNC as a BBMD device. Resolution When attempting to access a remote BACnet network from a computer over the Internet, the Niagara R2 UNC on the network must be set up as a BBMD device.  Then, in the Commissioning Tool, configure communications so that the computer is accessing the remote network, using the IP address of the UNC set up as a BBMD.

Issue How to make configuration changes to a Niagara R2 UNC with the WorkPlace Commissioning Tool. Environment Niagara R2 UNC WorkPlace Commissioning Tool Cause WorkPlace Commissioning Tool can't change Niagara R2 UNC configuration. Resolution Even though the UNC appears in the WorkPlace Commissioning Tool, configuration changes cannot be made.  Any changes must be made with Workplace Pro.

Issue What models of Bluetooth adapters are supported with WorkPlace Tech for use with the BACnet Roam-IA MS/TP interface? Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.7.1 or newer MNB-ROAM-IA BACnet MS/TP adapter Cause Many of the available BlueTooth adapters do not support serial communication emulation at 115,200 baud as is required by the Roam-IA BACnet MS/TP interface. Resolution Approved USB Bluetooth Adapter for systems that do not currently have a Bluetooth facility, can be easily added by purchasing an approved external Bluetooth adapter. At a minimum, the adapter used MUST BE CAPABLE OF serial communication emulation at a rate of 115,200 baud. Some of the less expensive adapters are only capable of 57,600 baud. For use with WorkPlace Tech, the tested and approved external Bluetooth adapter is the Belkin USB adapter (330 Feet), Model F8T012 – UPC Code: 7 22868 61581 2. Although other external adapters may work, use of this adapter is required for resolving product support issues. Update: As of 6/19/2009 The Belkin Bluetooth adapter model F8T012 is obsolete and has been replaced by the Belkin USB Bluetooth Adapter Model F8T017  – UPC Code: 7 22868 67681 3.

Issue What are the proper steps in upgrading an I/A Series WorkPlace Pro site? Environment WorkPlace Pro Cause Instructions on upgrading an I/A Series WorkPlace Pro site Resolution The published upgrade instructions can be found on F-27334 TAC I/A Series® R2.301.522 Installation Instructions. However, there is another method. Using the existing version of WorkPlace Pro backup ALL of the UNC and Server databases into the XML format. Copy the stations containing the XML to the desired WPP revision. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, this will allow you to repair them with out affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This will save you time later if you need to reload the UNC.) Now you can install the new desired revision into the Server, copy all of the stations into the new stations folder. Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC you will be ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. What it will do is backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. The only problem you may encounter would be on old Lon jobs. Some of the enumerated SNVT definitions were change by Echelon about the time we released WPP 431. If you run into the problem, the XML can typically be edited to resolve them.

Issue Error says, "Can not connect to Vista Server" when logging in to Workstation with a certain user. Other users work fine. Environment Vista Workstation Cause If the Authority is set to “No Access” on the global object $SYSTEM, the user can not log in to TAC Vista Workstation. Resolution Log into Vista Workstation using an account that is a member of the $Administrators group (System). Navigate to the root TAC Vista folder in the folders view. Right click on the $System object and select Authority Make sure the Access control list has $Administrators set for Full Control (All) and Everyone set for Read (R). If the authority has been completely removed and logging in even as an Administrator has been disabled, contact Product Support to re-establish a log in to the database.

Issue CyberStation key cannot be found when a laptop is removed from its docking station, but when it is connected to the docking station, it finds the key without problem. Environment Cyberstation key Laptops with docking stations Cause Sentinel driver must be installed while the laptop is disconnected from the docking station. Resolution Remove the laptop from its docking station Uninstall the Sentinel driver from Add/Remove programs in Windows control panel Reinstall the driver while the laptop is disconnected from the docking station

Issue Why are only three tabs viewable when the Properties page of a MNB controller is opened using version 5.7.1 (and newer) of the WorkPlace Commissioning Tool? Environment MNB controller WorkPlace Commissioning Tool Cause Beginning with version 5.7.1 of the WorkPlace Commissioning tool, only a subset of the controller configuration data is requested when initially browsing for BACnet devices using the selected communications protocol. Without additional information, the "Device Properties" program module does not know what kind of device (controller model) is being accessed. Without the model information, only the generic "General", "BBMD" and "Advanced" device information tabs are displayed. This is the same information displayed when third-party BACnet controllers are accessed. Resolution There are two options for acquiring the additional "Extended Device Data". Turn on the "Auto Acquire Extended Data" option.  WorkPlace Commissioning Tool will automatically request the extended data for those devices shown in the device list. Right-click the specific device entry in the list and select "Refresh" from the displayed menu.   Once the extended data has been retrieved from a BACnet device, the Properties window for that device will display with all the appropriate property tabs shown.

Issue WorkPlace Tech "Application Menu" and some "Tools Menu" entries are missing or grayed out. When attempting to run the WorkPlace Tech Tool, Application Menu missing or grayed out. All WorkPlace Tech Tool related entries in the Tools menu are grayed out or missing.   Project Toolbars are not displayed.  Environment WorkPlace Tech Tool 4.0.x, 5.7.0 - 5.7.3 Microsoft Visio 2002, Visio 2003 or Visio 2007 Microsoft Windows XPsp2, XPsp3, Vista or Windows 7 Cause Various causes beyond the scope of this article. Resolution There are several different reasons why these entries are grayed out or missing and therefore not selectable. There are two parts to the procedure to correct the problem, disabling COM addins and deleting the Visio directory cache. The exact procedure depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Options. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for all third party add-ins. Click OK to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WorkPlace Tech, all menu items should be there. If some or all of the WorkPlace Tech Tool menu entries are still grayed out, repeat these steps, disabling all COM addins. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there. Workplace Tech with Visio 2002 Open Visio 2002 Open the Tools menu. Select Options, then Advanced. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2002. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\VISIO.BIN If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\VISIO.BIN Open Visio 2002 and wait while Visio updates its directory cache. The process is complete when the "Choose Drawing Type" window is displayed. Close Visio 2002 Open WPT, all menu items should be there.