Building Automation Knowledge Base

Issue When downloading a project to a Xenta Server, an error says, "The Target System is of an old version. This XBuilder project requires the domino platform version to be >= 2.6.0" Product Line TAC INET, TAC Vista Environment XBuilder version 1.5.0 Xenta Server Xenta 511, 527, 913 Cause This error is caused by trying to download to a Xenta 511/527/913 that is not running the compatible system program for XBuilder version 1.5.0. Resolution Upgrade the device according to the following chart to correct this: Xenta Unit Version 511 2.3.0 527 1.1.0 913 2.0

Issue Xenta 527 Alarm will not reset Environment I/NET Seven Site Cause Issue with Xenta 527 Alarm will not reset Resolution Check the configuration of the alarm object and the Hysteresis configured. The default is 0.50 which is appropriate for whole numbers, but if the signal you are monitoring has decimals the Hysteresis may not be small enough to detect a return to normal state. For example differential room pressure which has a range of 0.06 to 0.20. In these situations use a Hysteresis of 0 to trigger a clear as soon as the value returns to a non alarm value.  

Issue The door reader, lock, and request to exit will all be working properly, but the shunt relay is not being energized. Environment I/NET Seven - v1.17 SCU1284 Cause SCU1284 shunt relay does not energize with door lock Resolution Go into the Door Properties (Access > Doors). Modify the associated door. The properties will have the shunt option grayed out (with no check) and the Elevator option will be white (with no check). Check the elevator option, and select ok. This will take you back to the Access > Doors screen. Modify the door again, and uncheck the elevator option. This should allow the shunt option to become "white" and checkable. If not, then after de-selecting the elevator option, hit ok again, and then modify the door again to select the shunt option. This has been corrected in later versions of I/NET Seven 2.xx.

Issue Error: "Error: Device does not refer to a COM port" when trying to download an application to a Xenta controller. Environment Vista Workstation LNS Network Cause This message is generated when the LonWorks network in the Vista database does not have a COM port (LNS port) defined. The problem occurs when Vista database has been "updated" with a second LNS database and is added to an existing database creates two LNS databases with only one communication port. The communication port in the Vista database can only be associated with a single LNS database. If trying to communicate to the first LNS database there will not be a communication port to use. Resolution Remove all objects added to the Vista database from the second LNS database Edit the properties for your existing LonWorks network. Browse the LNS port back into the "LTA Port" field. Using Vista Server Setup, create a new Vista database directory. Utilize the new database for your second LNS database. Note: Use a unique LNS database with each Vista database. Projects with multiple LNS databases must have a LTA, iLon, or L-IP configured for each LNS database.  

Issue Using "Module" display with a controller in Vista 4.4.0 Environment TAC Vista Workstation IV LON Devices Cause There are two options for how to display SCPTs and SNVTs in Workstation for a LON device. Resolution To change the way points are displayed for specific controller in Vista 4.4.0 or higher you can change the "Use Modules" option on that controller. Right click on the Controller and while holding down the "Shift" and "Ctrl" keys select the properties option. You will now see the "Use Modules" option in the list. With this option set to "on", the controller will display the SNVTs and SCPTs using functional blocks to separate them. With the option off the SNVTs and SCPTs will be displayed in a single group as a list. To get the setting to take effect, right click on the controller and select properties. On the XIF file tab browse to the XIF file of the controller. (The path must change for this to take effect.)  

Issue Modifying the Vista database to put all the points of a 102-AX into one folder to accommodate graphic pages that were built in Vista with versions of 4.4.0 or earlier. Environment Vista 4.4.0 Vista IV Cause When you upgrade to Vista 4.4.0, your database structure remains unchanged. Although 4.4.0 now displays SCPTs, you cannot see them on any LonWorks controllers yet. The process to access these is simple, but if you are not careful it will break any graphic pages, shortcuts, and other similar database access functions. Resolution To avoid the work of rebuilding your database follow these steps: Right click on the Vista Server object and select "Properties" while holding down "Shift" and "Ctrl". Change the LWUOPTION from a 0 to a 3. This will turn off Module display as a default and will avoid the change in database structure that will break graphics. For each controller that has SCPTs that you want to see right click on the controller and select properties. On the XIF file tab browse to the XIF file of the controller( typically found in C:\LonWorks\Import\TAC\X100\ for Xenta 100 controllers). Log out and back into Vista Workstation to see the changes. You will now have access to the SCPTs for each of the controllers you changed without breaking any graphic pages and shortcuts.  

Issue HID Proxpro with keypad Environment Applies to both I/NET and Continuum door controllers. Cause Information pertaining to the HID ProxPro   Resolution When ordering a keypad reader from HID, you need to make sure the Configuration Setting option is "09 - Buffer one key, add compliment, 8 bit message (Dorado)". Example: 5355 AGK 09 - ProxPro w/ Keypad If you are using the 5535 model reader on an Infinity ACX781 or ACX780 model controller you will need to order with Configuration Setting option 00.

Issue ZBuilder launches, displays the splash screen, and immediately minimizes. Environment ZBuilder Cause ZBuilder always launches minimized Resolution Do not wait for it to minimize to restore it. Click on the splash screen and that will prevent it from minimizing.

Issue Turning off automatic plug-in registration when LonMaker is opened Environment Echelon LonMaker Plug-Ins Cause By default, LonMaker automatically registers any unregistered plug-ins when a drawing is opened. It can cause a major delay in starting up a drawing if it is restored onto another PC where the plug-ins don't need to be registered and is better to leave that as an option to the individual users. Resolution The option in LonMaker is enabled by default as are the other startup options (network interface, onnet/offnet). Uncheck "Register all unregistered plug-ins when re-opening this drawing" Check "Skip this prompt when re-opening this drawing" There won't be any unwanted plug-ins registered to the LM drawing and LonMaker will launch a little faster, as well.

Issue Running Equalization on a PC that has SP4 (Service Pack 4) and the clients are unable to connect to the File Master Environment PC that has SP4 Cause There is a protocol setting that needs to be enabled for this to occur. Resolution The following steps show the path to MSQL Server where the protocol resides and how to get it enabled. Open Windows Explorer and go to C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNTCN.exe. Double click on this file and enable the following files, Named Pipes and TCP/IP. Apply the changes and then close the editor SQL Server Network Utility.  

Issue Installing MSDE or upgrading I/NET on a PC that has SP4 (Service Pack 4) and an editor comes up displaying the ports that will be disabled when the program is installed, then goes away. Environment I/NET Seven Windows SP4 MSSQL Server Cause  Ports in the MSSQL Server need to be enabled. Resolution Open Windows Explorer and go to C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNTCN.exe. Double click on this file and enable the following files, Named Pipes and TCP/IP. Apply the changes and then close the editor SQL Server Network Utility.  

Issue Direct Connect Xenta 527-NPR or 527 Web Server through I/NET Environment I/NET site Cause Direct Connect a Xenta 527-NPR or 527 Web Server through I/NET Resolution Are you using a Xenta 527-NPR or 527 Web Server and want to direct connect to it through I/NET and not having any luck? There are a couple of things that you need to set up in the unit for serial communication to I/NET through Port A (RS 232). The Xenta 527 NPR is set at factory default (RS232 Port A). The following steps should get you through this: Start I/Net and create a profile for the NPR (Net Plus Router) in I/O Server, then make this active. Verify that you have the correct cable to hook up from the serial port of the PC to Port A (RS 232) on the unit. (L1: RJ45 to RJ45 part # 0-073-0817). Connect them together. At this time you will need to start X Builder, if you don’t have it already, then you need to download it from the Exchange Extranet. The path is TAC Vista > Engineering Tools > TAC XBuilder > TAC XBuilder 1.5 (or latest revision). Download this to the PC. Start XBuilder through Programs > TAC > TAC Tool > XBuilder. Once started, select File\ New Project\(Project Name)\Location (default)\Project Template (select 527 Project), call it 527 NPR or whatever makes sense to you. At the settings Editor, just hit the OK button. Once the Editor comes up, in the Network frame, expand the TAC_Xenta_527. Right Click on the RS232-485A selection, click on Add then select I/NET. If you click on the TAC_Xenta_527, you will see all the settings that you have originally set up through Hyper Terminal or you can put those in at this time. Now select the Generate Icon or press F10 to generate the file. In the bottom of your project you would see a message that says Xbuilder – 0 error(s), 0 warning (s). This indicates that your project is now complete without errors. Now select the Rocket Ship Icon or press F11 to transfer the file to the unit. Once completed, restart or cycle power on the 527. Go to I/Net\Edit\Host Computer\Network Configuration and your 527 will show up in the Link Summary. At this time you can save the link, penetrate it and save the controllers etc. the old fashioned way. At this time you should be able to work on your system through a direct connect on a Xenta 527 NPR/Webserver unit.

Issue Battery Back up for DPUs Environment I/NET site Cause Information concerning the Battery Back up for DPUs Resolution Whenever a DPU battery is being replaced, it should be with the same 4V Yuasa battery that the boards came with or supplied from TAC. The reason for this is that we know what the amount of current is drawn from the circuitry to power up or charge these batteries after a power loss has occurred and the battery has discharged. If the batteries are replaced by larger ones, then the internal circuitry now has to compensate for that extra amount of current being drawn. In so doing, it will result in unforeseeable problems. Based on the amount of DPUs that are being powered by a Transformer, it is not recommended to have more than 4 DPUs per one Power supply if it is being shared. Ideally each DPU should have its own Transformer but there are instances where it can be shared, based on the VA of the transformer.  

Issue Battery Back up for MIPs and Controllers Environment I/NET site Cause Explaining the Battery Back up for MIPs and Controllers Resolution Controllers that are using MIPs like the 7700 series, once added to the baseboard now holds the database and it is backed up by the battery on this card. The onboard battery is now used only for clock power. MIPs on the taps however do not, since they only hold the Bin file for the respective types and no save file or database.

Issue Cards are being read, but no transactions are being displayed in the AMT Window on a Direct Connect. Product Line TAC INET Environment I/NET Seven Card Reader AMT Cause Hardware address must be set to 0 when using direct connect Resolution Open the I/O Server Modify the active profile Modify the Link Configuration Verify that the Hardware Address is set to 0 Software Address can be 0 as well but you can change this is if you like Save the changes and restart I/O Server. Open AMT, Transactions Window, read a card and verify that it is being updated with card reads.

Issue Requirement to powering DPU’s / SCU's with DC Power Environment DPU 7900 Series; 7910, 7920, 7930 and 7940 SCU 1200 Series; 1284, 1280 and 1200 Cause The majority of times that a user powers up a DPU / SCU is usually with 24V AC. However, DC power can also be used as an alternate. Resolution Series 7900 DPU's: The wiring to this can be two fold, it can be done just like the AC with pins 1 and 2 to power from the XFMR. However by doing it this way, the full 24V will be not be delivered to the unit. The recommended way to do this would be to hook either wire 1 to Power and wire 2 to ground or wire 2 to power and wire 1 to ground. This way you will get the full 24V delivered to the unit. SCU 1200 Series: For these units you would connect the +24V positive lead to TB1-1 and the negative lead to TB1-3 (which also must be connected to earth ground). Assuming you have sufficient 24Vdc current supplied, all the reader supply current output ratings would apply. The same local 24VDC source could be connected to more than one SCU in the same enclosure.

Issue Windows User's Account for logging into I/NET Environment I/NET Seven 2.11 and above Cause With the release of I/NET Seven 2.11, there is a new feature where the user can utilize the Windows User’s Account to log into I/NET. Resolution Select Edit Host Computer Passwords from I/NET's main menu to open the Host Password editor. Select Add to open the Host Passwords Assignments editor. In the Name field, use up to 30 characters to define the user's Windows account name. Use the following syntax for this field: machine_name\user_name or domain_name\user_name The entry in the Name field must exactly match the user's Windows account name. The following characters cannot be used within the name: " / []: | =, + *? < >. The Password and Confirmation fields become inactive and are not used for this type of account. Skip these fields. Continue filling in the other fields and assigning functions to the account. If necessary, refer to the Host Passwords Assignments editor for instructions. Once this is set up, select Log Off, then Log On again and check the box for Current Windows User and the current user will be logged on automatically.

Issue An error occurred while installing DSS: Cannot Start Service Product Line TAC Vista Environment DSS Vista Installation Cause This error can be found when installing Vista 4.3.x or higher after selecting Vista Administration of the SQL database. In the Application Event Log you will have an error stating the following: Cannot start service DSSWriterService on Computer '.'. --Stacktrace- at System.ServiceProcess.ServiceController.Start(String[[,args) at System.ServiceProcess.ServiceController.Start() at TAC.DSS.Install.ServiceInstallTask.Install() --End of stacktrace-- The reason this is happening is because when you selected to have Vista Administrate your SQL database it created local PC accounts (TACA_PCNAME and TACM_PCNAME). The TACA_PCNAME account is used to start the TAC DSS Writer Service and that account does not have access to the file to launch it. The access problems are typically caused by installing Vista on Windows Server 2003 and the "Authenticated Users" group has been removed from the User group on the PC. Resolution Click "Yes" at the install prompt and let the installation complete. Right Click on My Computer, and select "Manage". Navigate to Groups found in System Tools\Local Users and Groups. Double Click the "Users" group. Click the "Add" button. Click the "Locations" button and select your PC at the top of the list and then "OK". Type in TACA_PCNAME and click "OK". Note: This error should only occur if you have a non default security scheme on the network or PC. You should consult the IT department to make sure the TACA_PCNAME account will not be removed from the User group which will cause this problem to return.

Issue There is no explicit documentation which explains methods of wiring an STR sensor to an Xenta 100, 280 or 300 other than which wires connect to which terminals. If OP power wires are in the same bundled cable being used for the sensor and override button and potentiometer, it can cause temperature swings in the readings. Environment Xenta Operator's Panel (OP) Xenta Programmable controllers Xenta 281, 282, 283, 301, 302, 401 Cause The problem is that when you connect either one of those wires for OP power to the controller, you have created a capacitor between the signal wire and the OP power. This can cause temperature swings of typically 0.5°F and up to 2.5 or 3°F. Resolution Ideally you'll separate that pair of wires from the others by at least a few inches from the bundle. Even if they are in the same conduit, the reading will still be better with OP power on a separate pair from the bundled cable. Twisted temp sensor wire is also preferable for minimizing this effect. What about the sensors that are already connected this way? You can eliminate most of the variation by installing a 33 microFarad capacitor on the thermistor input terminals of the Xenta in parallel with the sensor. This should be a 10V or higher, low leakage cap (e.g. tantalum) and you should be careful to observe the polarity.

Issue Calculate proportional band from Control > PI > gain values Environment Xenta 121 ZBuilder Cause The gain value in ZBuilder is a unitless value representing the inverse of the proportional band in °C. The maximum value for gain is 32.7675. Resolution 100/gain = proportional band °C If the gain is set to 25, then the proportional band is 4°C (7.2°F, diff). Because the maximum gain value is 32.7675, the smallest possible proportional band is 3.05°C (5.49°F, diff).