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 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 How to export histories from a Niagara G3 ENC to a Niagara G3 Enterprise Network Server (ENS) Environment I/A Series G3 (Niagara) ENC and Enterprise Network Server (ENS). Cause Technical tip. Resolution To export a history to the ENS, expand the ENC's Niagara network and locate the ENS station. Expand the station, right-click Histories, and choose "View > Niagara History Export Manager"  Click the "Discover" button to discover the histories in the ENC station. Highlight the desired histories, and click the "Add" button. Select the desired Execution Time (Daily, Manual, Interval), set the "Enabled" field to True, then click OK.  Send initial history data to the ENS by clicking on the "Archive" button. In the Nav tree, open the ENS station. Expand the server's History folder. Verify that the histories from the ENC station are there.

Issue The Workplace Tech Tool 4.0 Engineering Guide (F-27254), Chapter 3 - "S-Link Sensor Tags", states "PBOccMode" is 0 following a download or reset.  This is incorrect.  Following a download or reset, the PBOccMode tag comes back as NA. Environment Lon and BACnet controllers with MN stats Cause error in documentation Resolution There is a work around if a 0 is required following a download or reset. If the existing logic is not able to handle the "NA", then link PBOccMode into Input[1] of a two input "Priority Object". Set Input[2] to a constant of 0. The Priority object will output a 0 following a download or reset.

Issue When creating piping graphics using the Niagara G3 kitPxHvac palette, how can elbows and tees be lined up exactly? Environment Niagara G3 Cause To line up pipe and elbow, snap option must be turned off. Resolution Turn off “snap” and place the objects close to each other. Then, while holding down the “Ctrl” button, use the arrow keys to move the selected pipe or elbow until it lines up perfectly.

Issue Editing any time schedule weekly charts in Vista Webstation 4.5 results in the schedule being ON ALL DAY regardless of what changes were specified in the editor. Environment TAC Vista Webstation 4.5 Cause Webstation is configured to use the wrong ASP.NET version. Resolution Open IIS Manager Open the properties window of the Webstation application by right clicking on it. On the ASP.NET tab change the version to 1.1.4322 and click OK. Stop the website and restart it in IIS Manager and the problem will now be fixed.  

Issue The Niagara G3 Microsmart Driver Installation and Configuration Guide (F-27523) lists "Applicable Documentation" on page iv. Is that documentation available for download? Environment Niagara G3 MicroSmart Drive (Installation and Configuration Guide) Cause Manuals (F-25695, SOFT-MCN-101) are not available. Resolution Two documents in the list are obsolete and were inadvertently listed as available. They are: DCT MicroSmart Reference Manual (F-25695) MicroSmart Application Manual (SOFT-MCN-101). The remaining documents are available in iPortal > Publication Zone.

Issue Crystal Reports in I/NET Seven Version 2.21 Environment I/NET Seven version 2.21 Crystal Reports XI Cause Beginning with I/NET Seven version 2.21, the I/Net Seven Reports application uses Crystal Reports XI as the reporting engine. Resolution In order to create and run reports using Seven Reports, you must first install Crystal Reports XI support files unto your PC. An installation program named SetupCrystalReportsXI.exe is included on I/Net’s installation disk for this purpose. When you execute this file, Microsoft Installer will launch and the necessary support files will be loaded onto your PC. We recommend that you install Crystal Reports XI support files immediately after completing the I/NET Seven host software installation. If you forget to install the support files, you will receive the following message when you launch Seven Reports: Crystal Reports Support files must be installed. Run CrystalReportsX1_Support Files.msi found on the Support Folder on the CD. If you see this message, click OK and install the support files from I/Net’s installation disk. To install Crystal Reports XI support files: Prepare to install the support files as follows: Close all other applications running on your system, including virus-checking software. Insert the I/NET Seven CD-ROM into your CD-ROM drive. If I/Net’s Setup program automatically launches, cancel it at the first screen that offers a Cancel button. Explore the CD-ROM and locate the following folder: d:\Support\SevenReports\CR_XI (where d: is the letter designation of your CD-ROM drive) Within this folder, execute the following file:SetupCrystalReportsXI.exe. This causes Microsoft Installer to launch and begin installing the support files. Follow the onscreen prompts to complete the installation process.

Issue Initiate Xenta 102-AX service pin messages (Neuron ID) from an M/STAT It is not required to hit the service pin button on the Xenta 102-AX itself, this can be done remotely from the room stat, provided it has an M/STAT jack (STR-250). Environment Xenta 102-AX M/STAT Cause If the Xenta 102-AX is installed up in the ceiling out of arms reach (which is typical) it can be cumbersome to get to each board to press the service pin button. Resolution Plug in an M-STAT to the room sensor (assuming you ordered the sensors with the M-STAT jack) Hold the service button in for about 5 seconds. This will tell the controller to broadcast its Neuron ID.

Issue Unoccupied mode on an Xenta 102-ES is really shutdown mode. Unoccupied setpoints are not maintained in the unoccupied mode. Heat and damper are forced to 0%. Standby setpoints are used in the unoccupied mode. Environment Xenta 102-ES Cause The structure of SCPTsetpoints includes unoccupied setpoints. That is the only reason they are available for a Xenta 102-ES. Resolution If the controller is in occupied or bypass mode, it uses the occupied setpoints. All other modes use the standby setpoints. When unoccupied, all heat operations are forced to minimum (locked out) and so is the damper. In the end, standby mode may provide more desirable results than unoccupied.

Issue How do I select an actuator and valve combination? Environment Actuator Valve Cause Select the correct actuator and valve part numbers. Resolution Refer to the TAC Catalog F-27414-*. Read the section on valve part numbers. Select the valve body needed. Refer to Catalog F-27382-*. Read through the actuator selection for MA, MC, MF, MK, MM, Mp, and MS to identify the desired actuator. Refer to TAC Catalog F-27414-*. find the page with the chosen actuator valve combination. Verify from the close off table that the actuator will meet the valve performance requirements. Turn to the actuator assembly code table and select the assembly code needed to complete the valve assembly number. ie: Vx-XXXX-XXX-X-XX. Order valve. If valve is not available as a factory assembly, order the individual parts and field assemble. The valve close off table provides the correct linkage kit required to couple the actuator and valve body, not all actuators require linkage kits.

Issue Recover deleted graphic files Environment Vista Server TGML Graphics Cause You can recover graphic files deleted from your Vista database. Resolution TAC Vista stores a cache for quicker opening of graphic files. C:\Documents and Settings\your_initials\Local Settings\Temp\TemporaryGraphicFiles C:\Documents and Settings\your_initials\Local Settings\Temp\TgmlCache

Issue After creating a new station using the "New Station Wizard" in Niagara G3 Workbench, it fails to copy into the ENC using the "Station Copier". This error message appears: "The local station database file config.bog is currently in use, and cannot be copied". Environment Niagara G3 Workbench Cause It's because a "Save Bog" was not done. Resolution Go back to Workbench and open the station, make a change and do a "Save Bog". The station should now copy without issue.

Issue Cross Reference of Obsolete Field Devices to Current Schneider Electric Field Devices. Environment Field device replacement Cause Unknown replacement for obsolete field device part number Resolution There is an Online Cross Reference Guide located on our Schneider Electric Buildings Website. Enter the old part number into the field for part to cross reference & click on the search button not the ENTER key. The ENTER Key clears the part number entry. The Manufacturer's name is not required for a product search. Contact Product Support when no cross reference is found for additional help.

Issue The MNB-1000 mounting base, manufactured before January 2009, does it comply with the UL 864 standard? Environment MNB-BASE-1000 UL 864 Cause Information on MNB-1000 compliant with the UL 864 standard. Resolution The MNB-BASE-1000 has electronics on it that cannot be used for smoke control if it has a manufactured date prior to receiving UL 864 certification (January 2009).

Issue Opening java or TGML graphics is very slow or they don't open at all. You may also have various java error popups. Environment TGML Graphics Cause The Java applet is limited to the amount of memory it is allowed to use. This will also limit how much memory java or TGML graphics are allowed to use, and can slow the rendering. Resolution It is possible to expand the amount of memory the Java applet has access to, and that seems to help in some cases. To increase this memory, do the following: Open the Control Panel in Windows and double click on "Java" Click the tab "Java" In "Java Applet Runtime Settings", choose "View" Find the most recent Java version runtime line (1.6.0_11) and double click on the "Java Runtime Parameters" box and add "-Xmx300m". This sets the Java maximum heap size to 300 MB. For some unknown reason, some computers with large amounts of installed memory are limited to how much memory they can assign to their Java VM. If you experience problems, just reduce the "300" to some smaller number (like 250, 200, 150, etc). However some computers have no problems setting the value to "1000". This procedure must be done to each computer individually. Also, remember to close all Internet Explorer windows for the changes to take affect.