Building Automation Knowledge Base

Issue In Tree Tech Revision 3.1,  received  "Error in FCSINIT - Use the TaskBar to find its window and check the error". Environment TAC I/A Series Tree Tech, Revision 3.1 Cause TreeTech 3.1 will only function with communication ports 1 through 9.  Ports above 9 result in "Error in FCSINIT - Use the TaskBar to find its window and check the error".   Resolution Select a communications port in the valid range from 1 through 9.

Issue Wants to know the correct termination specification for each different I/O modules and different IOU networks. Environment NC1 - CX9900, CX9940 NC2 - CX9680 IOU modules Cause Different type of terminations are required for different type of I/O modules (ACC-LON and FTT-10A) and different topologies (Bus topology, Free topology and Doubly terminated Bus topology). Resolution ACC-LON  requires two 120 ohm resistors at both ends of the bus. One between pin 1&2 of the I/O module on the NetController side and the other one between pin 1&2 of the I/O module at the last node of the bus. FTT-10A Free topology requires one 52.3 ohm resistor between pin 1&2 at any place on the bus. FTT-10A Doubly terminated bus topology requires two 105 ohm resistors.  One between pin 1&2 of the I/O module on the NetController side and the other one between pin 1&2 of the I/O module at the last node of the bus.

Issue Creating a bacnet schedule to control a 3rd party device generates the error:  “Bacnet operation rejected generated in response to a confirmed request apdu in which the service choice field specifies an unknown or unsupported service”  Environment Continuum 3rd party bacnet device Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The bacnet error occurs when dynamic creating of schedules is not supported in the 3rd party device and the packet gets rejected. Resolution An ethereal capture from the Cyberstation will show the packet getting rejected. A work around for this is to use a BCX to create the schedule and communicate to the 3rd party device.

Issue What is the required version of .NET framework and ASP.NET for TAC Vista software? Product Line TAC Vista Environment Vista 4.x.x Vista WebApps 4.x.x Vista 5.x.x Vista WebApps 5.x.x Cause Microsoft .NET framework is a core technology used by Vista software. ASP.NET is used by Vista Webapps for web presentation through Internet Information Services. With the many versions of .NET framework available from Microsoft it can be unclear which to install or ensure is available for Vista software. A new release of .NET framework is not necessarily supported by TAC Vista software until design changes have occurred in subsequent releases. Resolution Use this compatibility chart to ensure the proper version of .NET framework and ASP.net are installed: Vista Version .NET Framework Version ASP.NET Version 4.3.0 1.1 sp1 1.1 4.3.1 1.1 sp1 1.1 4.4.0 1.1 sp1 1.1 4.4.1 1.1 sp1 1.1 4.4.2 1.1 sp1 1.1 4.5.0 1.1 sp1 1.1 5.0.0 2.0 2.0 5.0.1 2.0 2.0 5.0.2 2.0 2.0 5.0.3 2.0 2.0  5.1.0 3.0 2.0 5.1.1 3.0 2.0  5.1.2 3.0 2.0 5.1.3 3.0 2.0 5.1.4 3.0 2.0 5.1.5 4.0 4.0 Note: A higher version of installation package might be present on the computer. To confirm the presence of the lower versions also being available review the C:\Windows\Microsoft.NET\Framework\ directory. The Microsoft.NET framework is available for install from Microsoft's website (http://www.microsoft.com/net/)

Issue Unable to access door schedule from an I/NET Graphic.  Attempts to modify the schedule bring up the time schedule point extension for the point instead of the door ATS. Environment I/NET Graphics Cause When adding a door to a graphic page you can either add it using the Point tool or the Door Tool. If you are using the point tool you will only be able to edit point extensions from the graphics page.  If you wish to use Access features you must use the Door Tool Resolution Edit the graphics page Right click on the point object and click properties. A Discrete Point Drawing Styles Window will pop up.  Note the Point Address Click Cancel Select I/NET>Doors to activate the I/NET Door Tool Click next to the point object and select the appropriate door. Click okay Right click on the door and select Properties. Configure the Door Point Drawing Styles as desired. If desired, delete the Discrete Point  object from the graphics page. Save your work and View the Graphics page To modify the ATS, right click on the Door and select Door Schedules.

Issue Is there an Xdriver for the purpose of using comm1 as an BACnet over MSTP for this netcontroller BCX 9640 and still use comm2 as Infinet?   Environment BCX 4040 BCX 9640 Cause Supported feature to use Bacnet MSTP on a BCX 9640 on Comm1 via x-driver Resolution There is no x-driver to allow MSTP Bacnet communications on a BCX 9640 NOTE: Suggestion would be to use a BCX 4040 and Comm2 for MSTP Bacnet Communications.

Issue Most TAC Plug-ins come with the Toolpack and are installed into the correct drive and available to be registered through an LNS management tool, like LonMaker or NL220.  This article describes the steps to follow if a new plug-in has been downloaded and needs to be added to the system. Environment LNS Plug-ins Viconics Stat Plug-In Cause In order for a plug-in to be used, it must first be downloaded, installed, and registered.  But sometimes merely placing it in the correct directory will not allow for the LNS tool to register the plug-in. Resolution Download the plug-in .exe file Place the file into C:\LonWorks\Apps\TAC directory Double click the .exe file.  This brings up a dialog with options to register/unregister the new plug-in. Register the plug-in. Launch LonMaker or NL220 The plug-in should be available to be registered in the LNS management tool.

Issue Does Modbus TCP/IP xDriver opens socket connection per each device or the gateway of the devices? Environment NetController - CX9900, CX9940, CX9680, bCX9640. BACnet Controller - bCX4040. Cause As some Modbus TCP/IP gateways have the limitation of maximum TCP/IP connections, if Modbus TCP/IP xDriver opens a socket per modbus device and keeps it open, the gateway might run into a problem due to the limited number of socket connections. Resolution The Modbus TCP/IP xDriver opens one(1) socket connection per server not device. So for a gateway that has a number of devices, the Modbus TCP/IP xDriver only uses one(1) socket connection.

Issue Using an MNB-ROAM-IA, cannot connect WorkPlace Tech Commissioning Tool to a controller; receive error message  “ Cannot open communication port: Error code 5” Environment MNB-ROAM-IA adapter, either Bluetooth or serial cable connection WorkPlace Tech Suite software ( WorkPlace Tech Tool, Commissioning Tool, Flow Balance Tool), revision 5.7.1 and newer I/A Series MNB controller (MNB-70, MNB-300, MNB-V1, MNB-V2, MNB-1000) S-Link Sensor (MN-S1, MN-S1HT, MN-S2, MN-S2HT, MN-S3, MN-S3HT, MN-S4, MN-S4HT, MN-S4-FCS, MN-S4HT-FCS, MN-S5,   MN-S5HT) Cause A poor mechanical connection between the plug (on the cable connected to the MNB-ROAM-IA) and the MS/TP jack on the MNB- controller or on the MN-Sx can prevent the software from connecting to the controller. Resolution Make sure the mechanical connection between the plug and the MS/TP jack is secure. The plug should connect at a right-angle to the jack, and be completely inserted.  When connecting via the MN-Sx sensor, make sure that the back portion of the plug does not hang up on the sensor cover, preventing full insertion.

Issue Reloading controller and receiving "Invalid Handle ID" error Environment Continuum Cyberstation BCX 4040 B3 controllers CX controllers i2 controllers Cause Most common cause is points already in the controller and/or bring controller from a different site/location and trying to reload while controller already has points in it. Resolution Reset controller Reload controller Backup controller flash memory

Issue CX9702:  appears to be powered up but showing offline in infinity programming Environment Continuum Cyberstation CX 9702 Cause Cannot communicate with 9702. Resolution Burn marks on then controller indicating overvoltage Send to repair.

Issue Receiving "Invalid Object context" error when saving a program Environment BCX 4040 B3 8xx -V Plain English Cause Receiving "Invalid Object context" error when saving a program Resolution Update B3 controllers with latest firmware version for Continuum Cyberstation version

Issue Cannot find third party bacnet gateway devices Environment BCX 3rd party bacnet gateway devices Cause Configuration issue will not allow proper communications on Bacnet protocol Resolution The third party Bacnet Gateway devices were setup as foreign device registration and not properly configured. Foreign Device registration is not needed on a single subnet bacnet setup. Disabled foreign device registration and Bacnet communications is now properly established. Also check that the correct subnet mask has been entered for the network

Issue I/NET Host Tool Initialization Error saying this version of I/NET is unregistered Product Line TAC INET, TAC Vista Environment I/NET Vista 5.1.5 Cause Vista and licensing must be installed before I/NET host tool Resolution Ensure that you are installing I/NET Host Tool and not a full copy of I/NET.  If you wish to run a full version of I/NET you will need to purchase that as a separate license. The In House Engineering Dongle does not include a license for I/NET host tool. Download I/NET Host Tool The I/NET Host Tool is also included a separate executable on the I/NET CD Uninstall I/NET Host Tool Go to Control Panel > Add & Remove Programs Remove I/NET Seven Remove Microsoft SQL Desk Top Engine (MSDE) Go to Windows Explorer > Program Files Delete any remaining I/NET Seven files and any remaining MS SQL files Re-install I/NET Host tool Ensure that the Vista License Server is running Extract the installation files from the .zip file Run setup.exe If you are using a Dongle or a Vista License that does not include I/NET host tool you will be prompted for License Key that must be purchased. If you believe you have received this prompt in error, contact Product Support.

Issue I/O modules that cannot be successfully commissioned Is there a procedure to test these or any resets or checks to do before sending the IOU back for repairs?   Environment CX96xx I/O Module Cause Unable to commission I/O module. Resolution FLASHING STATUS LIGHT This indicates that the Neuron chip in the module has undergone a partial commissioning and that it has calculated an invalid checksum in its flash chip.  This could happen due to communications problems on the IOU bus, either during module commissioning or during a NetController reload (which also de-commissions and re-commissions the modules). If you are experiencing this problem, do not return the modules to the Repair department. We have added a routine in the NetController to automatically detect and correct this condition. You can download the new NetController flash file and upgrade your NetController in the field. This will automatically correct any IOU modules that have this condition. To avoid this issue, you should also verify that your controllers and IOU modules are installed per the installation instructions, paying careful attention to bus topology, bus terminations, network cable, and grounding. Please note when adding multiple IOU modules that exhibit the behavior described above, to add and commission the modules onto the system one at a time.  SOLID STATUS LIGHT This indicates that the IOU module application flash is not present in the module. This could happen either due to the conditions described above or by a failure during the flash upgrade process.  These modules can be corrected in the field using one of the manual procedures described below: If the module was already commissioned on the NetController If the NetController has the module information in its memory, you should be able to flash the IOU firmware by editing the IOU object and selecting the “Update IOU” button. Then select the correct flash file for that module. If the module will not upgrade Connect the faulty module to a CX9xxx. With CyberStation online, create an IOU module.  Specify IOU number but not module ID. Save and close  the editor disregarding the error message. Set CyberStation offline. Edit the IOU module object inserting the module ID. Save and close the editor. Set CyberStation back online. Open the IOU module object, re-insert the module ID, select the Uprev button, and select a .upd file. When the uprev completes, commission the module. TAC product development has made a correction to this issue Click Here  in firmware version 1.530023. You should also read Technical Bulletin #1041 to make sure that you are using the correct IOU file.  

Issue I/A Series R2 (Niagara) Unable to Install Vykon Alarm Service (VAS) Client in Windows 2000 Environment Environment I/A Series R2 (Niagara) Windows 2000 Vykon Alarm Service 3.90 Cause Windows 2000 installer is not compatible with Vykon Alarm Service 3.90 Resolution As a work-around: Unzip VAS 3.90 file Create a new folder named VAS Client 3.90 under Program Files\Tridium Copy Overlay folder with all contents to VAS Client 3.90 folder Right Click Vykon Alarm Service.exe select Send to / Desktop (create Shortcut) Run by clicking new shortcut created in Step 4 

Issue Using Lon Tunnel with Lon Flow Balance Tool Environment Lon Flow Balance (MNL-FLOW-BAL) all versions R2 Niagara Lon Tunnel Client G3 Niagara Lon Tunnel Client Cause Not applicable Resolution No, the Lon Tunnel Application (Niagara Application Tunneling) is not compatible with the Lon Flow Balance Tool.  A direct connection (PCMCIA card or USB Lon Adaptor) must be present between the Lon VAV controller and the Lon Flow Balance Application.  Also, LON1 is the only adapter address supported.  

Issue The factory uses the number of field failure returns to evaluate product quality.  The analysis of returned product has the potential to produce extensive information about how the product is performing and also reveal areas for improvement. Environment All controllers in following product lines:  MNB, MNL, Niagara, Network 8000, Micronet 2000. Cause Lately, many of the returned controllers, after factory-testing, have resulted in "no fault found", and a high percentage of these controllers have little to no explanation of the failure witnessed in the field. This makes it difficult to investigate the returned product further. Resolution Include the following information with all controller returns: A detailed description of the reason for return The name of the site from where the controller was removed The name and contact information of the field technician who determined the unit was defective The field technician will only be contacted if absolutely necessary. Write the above information on a "returned goods" identification tag (part number F-24802) and attach a tag to each returned controller.  The tags are available via the Publication Zone through iPortal at no charge. For more information on returning product to the factory, review the following technical product advisories: TPA-PSSG-09-0003.00  Return Process Improvement TPA-RKFD-10-0005.00  Return Process Improvements

Issue Unable to connect a TGML link to a I/NET Time Schedule, Trend Configuration, Point Control, or Alarm Configuration page. Environment Xbuilder 5.x.x Cause The link of a TGML graphics page must be linked to a System pane object or URL. Resolution Use a Links Page object as an intermediary Create a new page -> Links page Set the Visible property to False. Drag the I/NET specific page on the Link of the Link Page. Drag the Link page object on to the Graphics page link.

Issue How to enable Xdriver on a CX9200 Environment Continuum Cyberstation CX9200 Cause When Infinity chips are installed on a CX9200 controller, it will not accept the XDriver upgrade cookie.  Attempting to change the commport configuration to Xdriver will return an error "Invalid Mode." Continuum chips are needed to properly apply the cookie. The controller can then be returned to Infinity by replacing the Continuum chip set. The Xdriver can then be used. Most commonly, the issue is due to the Infinity chip set not allowing the XDriver upgrade, but the chip set is not properly identified before the Xdriver upgrade is attempted. Resolution Enable an XDriver on an Infinity CX9200 must be accomplished from a dumb terminal connection: Log on to the controller via Hyperterminal Load -o -m with the XDriver cookie file provided by the repair department. Go to the Hyperterminal Transfer pull down menu and select "Send to Text File" and select the file as provided by Repair. Hit Enter to start the transfer. Send to database from the Continuum Explorer and only select the specific CX9200 controller. When the upgrade has completed, power down the controller, then repower the controller. Verify that the ACCSetEEVal string point in the CX9200 has been created. Check the Options tab of the Continuum controller editor and verify that the commport has been properly enabled for XDriver.