Issue Do 3rd party BACnet MSTP devices count as nodes on a BCX controller that is node limited? Environment BCX controller Third-party BACnet MSTP devices Cause Knowing the information will ensure there is not more node than the BCX controller specifies. Resolution Yes they do count as nodes. If you do go over the node count you will see operational problems with the BCX BACnet controller. The BCX controller will scan lock when it tries to perform a time sync to the MSTP network. Modbus nodes communicating via xDriver are not part of the node count.

Issue In an SCU1284 what is the "DO" addressing scheme for a Single Address unit. Environment I/NET site with Access Control Cause desire to know the DO addressing scheme Resolution The "DO" addressing scheme on a Single Address SCU 1284 is DOxx00 thru DOxx07

Issue In an SCU1284 with a dual address what is the addressing scheme for the "DO's"? Environment I/NET site with Access Control Cause Addressing issue with SCU1284 Resolution In the Dual Address mode of the SCU1284 the "DO's" addressing scheme is as follows First four relays are associated with the first address DOxx00 thru DOxx03. The Last four relays are associated with the second address DOyy00 thru DOyy03

Issue A system with NIC852 keys has difficulty getting the Loytec Ports to come online after an upgrade to Vista 5.0.3. Environment Vista 5.0.3 NIC852 Loytec Ports Orion Stack Cause There was a product enhancement with 5.0.3 that Loytec PCI-709 network interfaces were replaced by NIC709-PCI100 (Vista Orion stack) Resolution Upgrade the LCONFIG software to the newest 3.0.1 version. This software is available from http://www.loytec.com.  

Issue Vista WebApps install incorrectly claiming that IIS is not installed Environment Windows IIS Cause On some custom configurations of Windows we have seen where Internet Information Services (IIS) is running on another driver letter and Vista WebApps is not finding the IIS operating directory and claiming that IIS is not installed. Resolution Open the Registry Editor (Start > Run > regedit) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\InetStp\ for the PathWWWRoot key. This registry key should show the directory that IIS is using for storage of the web server. (Default is C:\inetpub\wwwroot\) Correct the registry key with the correct path and the install should now succeed.

Issue What Andover Continuum Controllers support the TCP protocol in lieu of UDP? Environment Continuum Controllers Cause Require the controller to support TCP protocol. Resolution The only Andover Continuum Controllers that support the TCP protocol in lieu of UDP is the CX9702,BCX9640 and the ACX II models 5720, 5740.

Issue "Field Unit Not Configured" when commissioning controller or network under a Xenta Server Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The LonWorks Network object is not recognized correctly by the Xenta Server. Resolution Create a new device "Communication Port - Echelon - LTA". Drag the "LonWorks Network" object on to the LTA port. Then drag the "LonWorks Network" object back on to the Xenta Server object.

Issue How can the instance number be changed in a Viconics BACnet thermostat? Environment Viconics BACnet thermostat Cause No visible button to enter configuration Resolution The ID or instance number is 7x000(x=series model)+ Mac address. The Mac address can be defined from the front of the unit. Press the white "config" button in the lower right hand corner of the circuit board once. Then keep hitting "no" until "Com Addr" is displayed and hit yes. Use up/down keys to set the address. For units with no white "config" button: VT7200 series press and hold the button (OVERRIDE) for 8 seconds VT7300 series press and hold the middle button (°C/F or OVERRIDE) for 8 seconds. VT7600 series press and hold the button (MENU) for 8 seconds Then press no until "com addr" displays, then press yes and use the up/down button to change it.

Issue The notification Servlet does not work in the Enterprise Server station Environment Enterprise Server station Cause NotificationServlet settings and SWID to the output object. Resolution Double check to make sure the SWID to the output object is correct. Set the NotificationServlet - properties - config - "activeCommand" to emergencyActive or manualActive and the "inactiveCommand" to emergencyInactive or manualInactive. The "activeInactiveText" for the BO can be modified to make that more meaningful.   Reboot the UNC to make these changes take effect.

Issue Unable to use the "Put" command from the DB Admin tab of the Admin Tool in Workplace Pro.  Cannot select file buttons. Environment Workplace Pro UNC series Cause UNC must be in idle. Resolution The "Put" command can only be used to import a database to an "idle" UNC. To idle a running UNC, uncheck it's "Auto Start" box and reboot.

Issue Clearing IP address in the 527 routing table Product Line TAC INET Environment I/NET TCP/IP Cause Routing Tables build themselves by self discovery. Resolution Routing tables build themselves by self-discovery on the network. If there is more than one device/host PC, similar function(s) may need to be performed on each device. Telnet utility for Host PCs, I/NET NPR2000 are examples. NOTE: Anytime you use the I/NET Command Line: inet(space) and the command you want to use for example; inet ip. Steps to clear a 527 routing table. Log into X527 with your web browser. Select the utilities folder. Select I/NET folder. Select I/NET Command Line. Make sure the word inet is in the command line and press submit. Then type inet delall to delete all the routing tables for the Xenta 527. You can type in inet help and this command will list all the all Web Shell Commands. ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all listsv ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records  

Issue Using Vista Classic with the Xenta 121 controller and ZBuilder will not open from Workstation Environment Vista Classic network Vista Workstation ZBuilder Xenta 121 Cause ZBuilder can not open if there are any spaces in the: Vista Server name Port name LonWorks network name LonWorks group name Xenta controller name Resolution Verify that there are not any spaces in any object names within the network. Always use _ (underscore) instead of spaces.  

Issue Adding a BCX1-CR-32-INF controller into Cyberstation and the drop down list does not show this as an option Environment BCX1-CR-32-INF CyberStation Cause In CyberStation when adding a controller to the system the drop down list will only show Model numbers and will not show the part number. Resolution See below for examples: BCX1 Router Only Model Number = 4000 BCX1 Bacnet Version Model Number = 4040 BCX1 Onsite Version Model Number = 4020 BCX1 Infinet Version Model Number = 9640  8Meg Netcontroller Model Number = 9900 4Meg Netcontroller Model Number = 9940 2nd Gen Netcontroller Model Number = 9680 ACX2 (8 Door) Model Number = 5740 ACX2 (4 Door) Model Number = 5720

Issue Run to file fails after an upgrade to versions 1.74 and above. You no longer can write to file using the run command. Environment Cause Enable write to file Resolution Instructions to enable write to file: 1. Create a workstation program named "Test1": (Example) Line Here1 Print "Hello There" Print PowerUpTime Stop Open the configuration and make it a fall thru program IMPORTANT check the "Run on any workstation box" The Run on any workstation required is what was changed from prior versions 2.Create another workstation program (Sample Program) Line There2 Run test1 to "c:\TestPEOut.txt" Goto There3 Line There3 If TS > 9 then Goto There2 Line E Stop

Issue How can two MicroNet 2000 MN-FLO or MN-FLO3T VAV controllers share data? Environment MicroNet 2000 MN-FLO / MN-FLO3T Cause Sharing data between the devices require MicroNet Integrator. Resolution Sharing data between two (or more) MicroNet controllers requires a MicroNet Integrator. Even if the integrator is not communicating to a GCM/DMS, it is still required to facilitate data sharing on the U-bus. The only system configuration, not involving an integrator, is stand-alone mode. Peer-to-peer data sharing is not possible. See the MicroNet 2000 Family Fundamentals Guide (F-25711) and review the chapter on System Configurations.

Issue Trend Log pages, Time Object pages, Alarm pages and Value pages in a TAC Xenta 721 project. Environment TAC Xenta 721 Cause XBuilder allows for the creation of some additional objects in a Xenta 721 project for use with the OP7, not to be visible in a web browser or Vista Workstation. Resolution In the XBuilder 5.1.0 you can add Trend Log pages, Time Object pages, Alarm pages and Value pages in a TAC Xenta 721 project. These pages are only for use in the OP7. Unfortunately, they are visible in the TAC Vista database and the pages do not work in Vista. If you use IE to browse the Xenta 721, you can not see the pages. These pages should not be visible in TAC Vista. This was reported as a bug and will be corrected in later versions.

Issue If you are integrating LON to I/NET with a Xenta 527 or Xenta 913, you may run into a unit conversion problem in the integration process. Product Line TAC INET, TAC Vista Environment I2V I/NET LON Integration Xenta 527, Xenta 913 System Program Version 5.0.0 or higher XBuilder 5.0.0 or higher Cause When integrating LON to I/NET, all data will make its way to I/NET in SI units. Resolution View the units of the points on the LON side of the connection object in XBuilder. On temperature, for example, XBuilder uses the unit "F" to show Fahrenheit on a temperature signal. However this temperature value will show up in I/NET in Centigrade.  Engineering units on the AO point in the I/NET controller will have to be "F" to mirror the unit on the LON signal in XBuilder. These two units have to match exactly, and they are case sensitive. When the engineering units match on both points, I/NET will convert to the correct value. If the value on the I/NET side is left blank, it will just pass on the Celsius value. There are limitations to this conversion since I/NET has a four-character limit and some units in XBuilder will exceed this. Pressure, for example, will have to be sent in Pascals or PSI. 

Issue After upgrading Vista, upon opening reports you receive the error "Report is of a previous format. Please try updating the database again." Environment Upgraded Vista Workstation Reports Cause Version property may need to be set for each report that needs to be upgraded. Resolution Upgrade the current database. You may have to change the Version property for each report that needs to be upgraded. Right-click on the report, select Properties while pressing down CTRL + SHIFT. This opens the 'advanced' properties dialog. If Version is 1 change it to 0. Run regedit to open the Registry Editor. Open 'HKEY_LOCAL_MACHINE\SOFTWARE\TAC AB\TAC Vista\4.2' (Select folder that matches your version of Vista) and locate the key 'UpgradeReports'. Set this value to 1. (0 means do not upgrade.) Start Vista Server and the reports in the database should be upgraded properly. The file UpgradeReportsLog.txt in the database folder $log contains detailed information about the upgrade process.  

Issue Can the profile in a MNL standard LonMark controller be changed in the field?  For example, can a MNL-20RH3 (heat pump profile) be changed to a MNL-20RS3 (satellite 3 profile)? Environment MNL standard LonMark controllers Cause The LonMark Profile is stored in the controller's firmware. Resolution No, the LonMark Profile cannot be modified.

Issue How do I change a CX-9200 or a CX-99xx to a CX-9680 (Netcontroller II) Environment Cyberstation CX-9200 CX-99xx CX-9680 Cause Controller has changed and need to change the controller model number in Cyberstation. Resolution If you are Using Cyberstation V1.74 with SP2, or Cyberstation V1.81 or greater, all you need to do to accomplish this change is to edit the existing controller (CX9200 or CX99xx). In the controller Type dropdown menu, select 9680 and OK the change. When you save the change you will be prompted with a warning that this change is not reversible. Once you OK that, the database will change all the appropriate system objects to be compatible with the Netcontroller II including system variables. The replacement CX9680 can then be reloaded from the Cyberstation and the conversion is complete.