Building Automation Knowledge Base

Issue Need the UL Listings for Xenta Product Line Product Line TAC IA Series, TAC INET, TAC Vista Environment Xenta Cause UL Listings for Xenta Product Line Resolution Go to Exchange Online and log in Search for "TAC Vista UL Listings" (Example, Click Here) You can find more information in Xenta Hardware UL 864 Listing.

Issue In some projects there is demand for importing a large number of individuals from an existing spreadsheet for individual information at one time. Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft SQL Server Management Studio Express Cause In some cases the customers have a spreadsheet or database of employees and/or users which they want to quickly import into their I/NET Seven Access control database. Resolution The whole process is to import the data from the excel file to the IDWorksView table of SQL database of I/NET. The steps below needs to be followed: Prepare the Microsoft SQL Server Management Studio Express. Click here to down this tool for version 2005 free of charge. If for version 2008, click here to download. Then install this tool. Download the individual spreadsheet Excel template and SQL script here. Save to the C:\. Ensure that the Tenant, Group have been added in I/NET already. Also ensure that all the card numbers in the spreadsheet don't conflict the ones already in I/NET. Enter the individual information into this template. If there are photos for individuals, the folder of the photos also need to be entered. Open the Microsoft SQL Server Management Studio Express and connect to the database. Find the InetDb database, and open the SQL script just downloaded from the File menu. Click Execute to run the script. Then if without any problems, the successful result will be shown in the output message window. The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality.  There is also a method that download the imported data without any operation in I/NET software by a function called Automatic DPU Restore. Refer to Automatic DPU Restore and Individuals added via Datacard ID Works are not getting access to doors for detailed information about how to set Automatic DPU Restore in I/NET. This is the method using SQL Server Management Studio Express. The Microsoft Access can also be used to do the importing work. Refer to How to import a large number of Individuals into an I/NET Access Control database for detailed information.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Want to be able to import a list of individuals quickly without having to retype all the details from a spreadsheet or text file again into I/NET Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft Access 2003 Microsoft Access 2007 Cause Customers usually have a spreadsheet or database of employees and / or users which they want to quickly import into their I/NET Seven Access control database.  The process below describes how to do this along with its limitations. Resolution Process to import Individuals via the IDWorksView table using Microsoft Access 2003 / 2007 The import process will NOT update any existing data; it will only add new entries and leave existing entries as they were.  So this is typically a process used for a new installation.  If you are attempting to import into an existing Access control database with individuals then it is strongly recommended to backup your I/NET SQL database. It is also strongly recommended you test this in an ‘offline’ state, that is, it is not connected to any physical controllers until you are comfortable that the process provides the desired results. The same limitations that apply with ID Works (Refer to TCON 301 Chapter 5) apply to this import process. TAC I/NET Seven (not just I/O Server) must be running on the server specified in TAC I/NET Seven’s ODBC data source in order for records created or modified from ID Works to be downloaded to affected DPUs. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record. You cannot disable an individual’s card without disabling the individual. You cannot create a new group or a new tenant.  All Tenant and Group information must already exist in I/NET You cannot make an individual’s record be DPU resident. You cannot assign a decimal card number to an individual. You cannot set an individual’s APB scheme (that is, hard, soft, or graced anti-pass back). You cannot assign a PIN to an individual. The steps to import are as follows: Download ZIP file containing necessary files here. If you are using Microsoft Access 2007 use the following files Format customer data into the Excel template (dbo_IdWorksView.xlt in the ZIP file) or provide this to the customer to complete the Employee details.  Pay attention to required data shown in the comments for each title cell. Open db1.mdb file in the ZIP file using Microsoft Access 2003 /  idworks.accdb if using Microsoft Access 2007. Double click (open) the table dbo_IdWorksView to establish the connection to I/NET on the respective machine.  You may be prompted for login details – you must use the ‘sa’ login and password installed on the PC. If successful you should see any individuals that already exist in the database (unless blank).  Close the table. If you are using Microsoft Access 2007 Click Here to view the changes for steps 6 though to 8. Right–click in any of the white space and select Import (or go to File>Get External Data>Import) Browse to the location of the Excel Spreadsheet, saved in step 2, containing the data to be imported.  Be sure to change the File Type to *.xls otherwise you will not find the file.  Select the file. Import wizard should appear, now select the following options within the import wizard: Select the Check box “First row contains column headings..” Select Next Select “In an Existing Table” and select the table from the drop down list – there should only be one there. dbo_IdWorksView. Select Next. Select Finish. Be patient – the process can take a few minutes based on the number of entries that you are trying to import.  Once imported you should receive a message indicating that the import was completed.  Select OK. If you have images referenced in your import file, be sure that the Images are in place before modifying ANY individual in I/NET.  Otherwise the image path will be deleted.  The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality. There is also a way to realize this function using Microsoft SQL Server Management Studio Express instead of Microsoft Access. See How to Import a Large Number of Individuals from Excel to I/NET SQL Database at One Time for more information. 

Issue When viewing graphics in Enterprise Server values are flashing in and out. Product Line TAC IA Series Environment R2 Niagara Cause When viewing the UNC's workspace editor, the values are ok, but in the Enterprise Server links are active and inactive. Resolution The Enterprise Server stations have to be configured with different ports to run simultaneously. Please consult Two stations running concurrently on a Niagara R2 computer or stop second station from running.

Issue Using a card reader to Unlock and Secure a Building Product Line TAC INET Environment I/NET Seven 7798 Cause Site requests the ability to have a user card in at the beginning of the day locking the door and card out at the end of the day unlocking the building Resolution Create and AIC triggered from the card reader to start an event sequence as outlined in Using AIC to trigger an event sequence The AIC should trigger an event sequence (sequence1) Line 1 of sequence1 should be skip if 0, looking to see if the door is lock and skipping to sequence2 Line 2 of sequence1 should be skip if non-0, looking to see if the door is unlocked ad skipping to sequence3 Sequence 2 should unlock the door(s) Sequence 3 should lock the door(s) You may need to change the delays until you get an acceptable response. Ideally Line 1 of sequence 1 should be delayed long enough for the door to return to lock after the reader entry. As an option you could have sequence 1 check the status of the door. A badge read when the door is closed unlocks the door(s). A badge read when the door is open locks the door(s).

Issue Direction of data transfers between Xenta Servers is important in versions 5.1.4 and later.  Stable communication over TCP/IP, UDP requires management of the data flow.  In XBuilder 5.1.6 and later, it will give an error on any connection objects not created using this standard: "It is not allowed to connect a signal to an output that results in a write over the IP network." Product Line TAC Vista Environment Xenta Servers v 5.1.4 and later XBuilder Cause Properly managing data flow will cause the TAC Xenta Server to poll for data, rather than accept an asynchronous write command. This will result in a more stable TCP/IP connection. Resolution See TAC Vista 5.1.5 Release Notes for more information. When importing another TAC XBuilder project to the current TAC XBuilder project in order to create data point transmission between two TAC Xenta Servers, make sure to import the data producing project into the consuming project. In the above example, because Xenta Server A is sending the Outside Air Temperature point to Xenta Server B, it is Xenta Server B's XBuilder project that should be edited.   In XBuilder, right-click on IP Backbone under the Network pane Select New > Other Projects Network In this example, Browse the sending project, Xenta Server A, into the receiving project, Xenta Server B Bind all data using connection objects into the receiving project's network. If bi-directional data flow is desired, the same steps must be performed on Xenta Server A's XBuilder project. The proper way to connect signals in this scenario can be found in Polling data over IP from the System pane of a 700 project.

Issue Set up a two wire LTS80 Lini-Temp sensor on a 7756 PCU on the lower board Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7756 PCU lower board Cause Lini-temp is a type of temperature sensor that is compatible with the I/NET product line. Resolution For Fahrenheit: M = 0.0274669 B = -459.8 10k ohm resistor in slot "A" Remember, the lower board has a different resolution than the upper board. See Set up a two wire LTS80 Lini-Temp sensor on a 7756 PCU on the upper board for details on the upper board. Refer to TCON 127: 7756 PCU Installation Guide for details

Issue Standard Output Window displays the following error:  Java.net.socketexception.reset Product Line TAC IA Series Environment R2 Niagara Cause The IP network has two NIC cards assigned the same address.  This results in a  Duplicate IP Resolution Use WireShark to Find the duplicate IP and re-assign a new ip to the server or UNC IP. For more detail see Using WireShark to analyse communications on an Ethernet network. 

Issue How to identify the Firmware / Software Version of an Xenta Controller Product Line TAC Vista Environment Firmware/Software Version of Xenta Controllers LonMaker Vista Cause The Firmware/Software Version of a Xenta Controller can be used for troubleshooting issues on site, or determining if an upgrade is required. Resolution The Application Specific Controller version Open LonMaker Right Click on the ASC and choose properties Select the Self-documentation tab Firmware/Software Version should appear in the bottom window The Programmable Controller version Open Vista Right Click on the Programmable Controller and choose properties Expand the window if necessary to expose the Information tab Select the Information tab Firmware/Software Version should appear as Software Version Please see Xenta Software current versions as of 10/2012 for most current released Xenta Software versions

Issue Different Continuum products are approved to different approval standards and where are copies of these certificates held? Product Line Andover Continuum Environment All Hardware products: Standards listings to UL, BTL C-Tick, CE Cause Copies of the approval certificate or clarification on the different standards are required. Resolution The Agency listings each controller is approved against are defined on the datasheet, for more information see How do I get the part numbers and datasheets for Continuum products?. An example of the approvals for the bCX1 controllers are: UL/CUL 916, UL 864 9th Edition, FCC CFR 47 Part 15, ICES-003, EN55022, AS/NZS 3548, Class A, VCCI, EN61000-6-1, CE   All of the Regulatory Compliance documents including: UL, CUL, ISO,  European CE Certificates, Australia/ New Zealand  C-Tick Certificates and WSP Cert can be downloaded from The Exchange Download Center -  Regulatory Compliance   Confirmation of BACnet testing can be seen at the BTL website: http://www.bacnetinternational.net/btl/ European Standards - Continuum has been tested to the following as part of the 89/336/EEC Electromagnetic Compatibility Directive and over the years the standards have changed. Emissions -Continuum is tested against EN55022-Class A This is the emission standard for Information Technology equipment and another emission standard is the EN50081-1 but this is a generic emission level and less stringent than the IT standard that Continuum complies with. Immunity - These standards have changed over the years, older controllers were tested against the International IEC1000-4 and we state the specific levels our controllers are tested against, then when it was released in 2000 we used the EN50082-1 standard which replaced the IEC standard in Europe. But newer controllers have now been tested against the EN61000-6-2  standard that have since replaced the other immunity standards.    There is also the EN60730-1 standard that Continuum is approved to, this defines the standard controls specifications it can perform. These standards are required for us to apply the CE marking to our products.

Issue Unable to relay Email not working Product Line TAC Vista Environment Vista SMTP Cause If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Resolution Go to Vista Server settings At the email tab set proper authentication (TAC Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site For more information on troubleshooting sending emails from a Vista server, see Troubleshooting Sending Emails from a Vista Server.

Issue Set up a two wire LTS80 Lini-Temp sensor on a 7756 PCU on the upper board Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7756 PCU upper board Cause Lini-temp is a type of temperature sensor that is compatible with the I/NET product line. Resolution For Fahrenheit: m = 0.21978 b = -459.6 For Centigrade: m = 0.1221 b = -273.0 J22 to 15 VDC 10k ohm resistor in slot "A" Remember, the lower board has a different resolution than the upper board. See Set up a two wire LTS80 Lini-Temp sensor on a 7756 PCU on the lower board for details on the lower board. Refer to TCON 127: 7756 PCU Installation Guide for details

Issue Moving / transferring VisiSat license(s) from a PC to another Product Line Satchwell MicroNet Environment Satchwell VisiSat 2.0 / 2.1 Cause There may be a need to replace your VisiSat PC or to transfer licenses to be used on another PC. The procedure below explains how to export a license file for each license on the existing PC, which you then transfer and import into the new PC. Resolution Refer to Moving VisiSat Licenses which has been extracted from the VisiSat Engineering Guide for the procedure to move / transfer the VisiSat 2.1 licenses. Refer to Transferring VisiSat version 2.0 license to Computer running VisiSat 2.1.

Issue Creating a Desktop or Start Menu icon for I/NET Host Tool Product Line TAC Vista Environment I/NET Seven Host Tool Cause In some cases instead of using the Vista Workstation menu option "Tools > I/NET Host Tool", it is sometimes more efficient to start the I/NET Host Tool from either a shortcut or link on a graphics page. Once this shortcut has been created it can be easily linked too to provide this functionality. Resolution To create a Desktop icon or Start Menu entry for the I/NET Host Tool: Use the Start Menu to find the I/NET launch Icon (All Programs\INET\INET) Right click and select "Send To -> Desktop (create shortcut)". Right click on the Desktop Icon and select properties. In the general tab change the first field from INET to INET Host Tool. In the Shortcut tab add "/vista" to the Target field so the final result is: "C:\Program Files\INET Seven\INetW.exe" /vista You can now place the icon anywhere on your desktop or in your start menu. TAC Vista Server must be started, and in some cases Workstation must have been started and logged in at least once and before using this shortcut or an error message about I/NET being unregistered will be encountered. Also refer to Incorrect or missing I/NET Host Tool license for additional information when running a full version of I/NET on the same PC.

Issue How long and what topology can the IOU bus be on a Netcontroller? Product Line Andover Continuum Environment IOU Modules Netcontroller Cause Maximum cable distances and topologies required. Resolution The Standard RS485 modules can only be connected in a bus (Daisy Chain) topology, no star or "T" topology can be used. The maximum distance from the Netcontroller to the last module in the bus is 600M using a low capacitance cable like the Belden 9729. If you have to create a free topology network with a star or "T" topology then you must use FTT-10A Netcontroller and IOU Modules. See What is the advantage of having a Doubly Bus Terminated Topology segment VS Free Topology in a LON FTT 10A setup? for details on the FTT-10A module wiring or the I/O System Reference Guide for further installation details.

Issue Once the controllers UTC setting is set and and committed in the Controller Configuration webpage, when they are rechecked they have returned to the default setting of 0. Product Line Andover Continuum Environment CX99xx CX9680 ACX57xx BCX9640 BCX9680 CX9702 Cause This is a known issue. Resolution Since the controllers UTC setting cannot be set properly from the controller web page, it must be set from a Plain English program in the controller.  See Set the UTCOffset of a controller using a PE program.

Issue When Webstation is opened, no images are shown and formatting (styling) is missing. Product Line TAC Vista Environment Webstation Cause The Webstation application doesn't have access to or can't parse the stylesheet. Resolution 1: Uninstall Webstation (including hotfixes) 2: Install Webstation by right clicking the installer and selecting "Run as administrator" 3: Run "Webstation Corrections"

Issue When points show Old Data some processes may cause equipment to shut down. Product Line TAC INET Environment I/NET Cause When a value is out of range in I/NET, any control referencing it will also be out of range.  For systems with communications issues this can be a problem for indirect points such as Outside Air Temp. DDC modules contain a Failsafe Output Control Point which can also over come this obstacle. Resolution Refer to What does it mean when a point goes "OLD" in I/NET? with information on how to prevent points from going "Old".  If the point continues to go old you can use this process to account for the old point: For this example assume that you are monitoring OAT with an indirect point Connect to the controller with the indirect point that is going old. (OAT) Create a duplicate of this point that is internal.  Call it "OAT_mirror" ensure that it has a relatively short scan interval Add a Calculation to OAT_mirror Use this expression: AV(P0,P1)   Set P0 as OAT Set P1 as OAT_mirror Click okay Change any control logic referencing OAT so that it references OAT_mirror Results: The AVG calc function will ignore any old value.  This means that while the OAT point is valid the OAT_mirror will quickly change to equal to it. When the OAT point goes old the OAT_mirror point will retain it's current value until the OAT point is no longer old. For information about triggering an alarm when a point goes old, view Triggering an alarm or message if a point goes old in I/NET For further Indirect Point "Old Data" Filtering Techniques read I/NET Indirect Point "Old Data" Filtering Techniques

Issue A modem is already connected to a remote site's tap. Settings in the modem need to be changed. Can this be done by dialing into the modem in its present configuration? Product Line TAC INET Environment I/NET remote site communicating via dialup modem Cause The remote site's modem needs to be connected to a PC or Laptop. Resolution No, a modem can not be configured by using its present configurations. Windows HyperTerminal is suggested to edit modem settings.  Refer to TCON 226 (Dial Applications) and TCON 101 (Taps and Repeaters). For emulated tap set up, refer to the appropriate Controller TCON. Issue A new SCU 1284 out of the box that you are setting up and it shows up with an * in Netcon. Product Line TAC INET Environment SCU 1284 Netcon Cause SCU's manufactured before 2009:  There is really nothing wrong with the SCU itself, but there may be an Eprom on the board that is not the correct one. It is the one that is used for the SCU 1280. Newer SCU's: This is generally caused by an incorrect setting in the MCU configuration Resolution Verify that you have the correct MCU configuration settings.  An SCU 1284 should be set to DPU.  An SCU 1280 or 1200 should be set to DIO.  Check Network configuration to see if the issue has cleared up. If it has not cleared up try the following: Delete the item from Network Configuration and allow it to repopulate. Ensure that the DIP switch is set to the correct address. Follow the instructions to reset the SCU located in Reset Instructions for 1200 Series SCU.  Then reload the bin file. If you are still having issues then the best option is to send that unit back and have it replaced with another.

Issue A modem is already connected to a remote site's tap. Settings in the modem need to be changed. Can this be done by dialing into the modem in its present configuration? Product Line TAC INET Environment I/NET remote site communicating via dialup modem Cause The remote site's modem needs to be connected to a PC or Laptop. Resolution No, a modem can not be configured by using its present configurations. Windows HyperTerminal is suggested to edit modem settings.  Refer to TCON 226 (Dial Applications) and TCON 101 (Taps and Repeaters). For emulated tap set up, refer to the appropriate Controller TCON.