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 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. 

Issue Having issues adding a SNVT to an existing controller in a NL220 system? Or possibly a new device template is not showing up after the .xif change? Environment NL220 Cause In some cases, when you are uninstalling (or decommissioning) a controller, it get into an unconfigured state, not allowing it to take a download.   Resolution Take the database offnet Use the Tools drop down and Uncheck the "Attached to Network" option. Do an "uninstall" or decommission the controller Browse in the Menta file with the new SNVT to the System Plug-in and NL220 should have a new device template for the controller.   

Issue Can the Network 8000 Microflo or CVV-80000 series controller be integrated using the Niagara R2 GCM driver? Environment Niagara R2 Network 8000 CVV-80000 Cause Information on integrating Network 8000 Microflo or CVV-80000 series using GCM driver Resolution Yes. Architecturally, it connects to the GCS bus of a GCM-84000 controller. The GCM database will contain VVBOX blocks which interact with the Microflo controllers. The VVBOX block can be read from and written to using GcmGeneric objects in a UNC station.

Issue What BACnet Command priority does a Cyberstation program use in changing value of BACnet points? Environment Cyberstation Cause Change the value of BACnet points Resolution When you use the WriteProperty() function, you must use the BACnet path of the object for WriteProperty() function. - If the priority# is given in the WriteProperty() function, it sets the value of the point with the given priority#. - If the priority# is not given in the WriteProperty() function, it sets the value with priority#16 by default. When you don't use WriteProperty() function. - If you use BACnet path ( Ex; BACnetDevices\BCXName\MyNum = 12.340), it sets the value with the priority# that is defined in the attribute of BACnet Command Priority for Cyberstation Programs in the BACnet Preferences. - If you use Infinity path ( Ex; MyNetworkName\BCXName\MyNum = 12.340), it sets the value with priority# 10 by default.

Issue When "learning" an MNB controller into a Niagara R2 UNC station that has an MN-Sx sensor, a read failure occurs and several WARNING messages appear  in the Standard Output Window. These errors did not occur in uploads with BACnet jar files previous to 527i. Environment MNB controller Niagara R2 UNC station MN-Sx sensor BACnet jar file (527i) Cause A change that occurred in the 527i BACnet jar file. Resolution These messages occur with BACnet jar file 527i and later and are legitimate. They are a result of uploading the S_LK_Display1 object. The read failure for description property occurs because there is no description in this object and the subsequent warnings are because Niagara R2 does not support the files listed. This was true of previous BACnet jars as well but was not reported.