Building Automation Knowledge Base

Issue MSDE and the install of I/NET Seven and Vista 4.3.1 version software. Environment Single computer with both I/NET Seven and Vista software. Cause MSDE and instance Resolution MSDE does not allow an unnamed instance to overwrite a named instance of MSDE. I/NET Seven MSDE installs at this time an "Un-Named" instance. Vista 4.3.1 installs a "Named" instance. The work around: Install I/NET Seven first then install Vista 4.3.1. This will be corrected in future release of I/NET Seven.

Issue AMT is Displaying Link 200 and a partial point address. Environment I/NET site Cause Error Message AMT is Displaying Link 200 and a partial point address Resolution AMT can report a LINK 200 + a partial point address. When this occurs the system has defaulted to an error handling code to let the system programmer know that there is a hardware addressing conflict in a direct connect system. To correct this; open active profile in the I/NET configuration editor and modify the link configuration editor. The error generally occurs when the host hardware address is different then the actual hardware address. For example: 7801 Tap is addressed "0" and the Host hardware address is something other than "0". When connecting to a Host/Link/Lan tap (either a 78010 that connect directly to the controller lan or an emulated 78010 on a controller), the hardware address is always 0 and cannot be any different. Please read TAP and Repeater TCON 101 for a more detailed explanation on configuration parameters.

Issue Order of Operations for Creating a New Detail in ProjectBuilder 2 Environment I/NET or Vista site Cause Desire for a Order of Operations for Creating a New Detail in ProjectBuilder 2 Resolution Drag and drop a blank Placeholder onto the page from the TAC Device or TAC Wiring Details stencil. Create the detail drawing on the paper space in Visio. Make sure the drawing is the appropriate size to fit in the blank Placeholder. Select all of the detail drawing and copy it to the clipboard. Select the blank Placeholder that has been dropped on the paper space in Visio. Select Open Placeholder from the Visio Edit Menu. After the blank Placeholder has been opened, select Paste Special from the Visio Edit Menu. While in the Paste Special window, select Picture (Enhanced Metafile) and select OK Position the detail drawing in the Placeholder. Close the group window. Once back in the Visio window, RMA on the new Detail and select Edit Detail Info. Enter the Detail Name in the Name field and the Detail Description (Manufacturer) in the Description field, select OK. RMA on the new Detail and select Format/Special. Change the Name field from “Placeholder” to the exact Detail Name used two steps earlier. RMA on the new Detail and select Shape/Custom Properties. This drop down box should be blank. Select the type of shape from the list that this detail can be associated to. It might be necessary to change this property during the course of the drawing to be able to associate the detail to more than one kind of shape. Select OK. If you wish to save this detail, put a stencil into the edit mode by left clicking on the stencil icon in the top left hand corner of the stencil window and choosing edit. Copy the new detail and paste it into the stencil in edit mode. In the stencil set, RMA on the new detail and select Master Properties. In the Name field, enter the same name as you did for Detail Name earlier. In the Prompt field, on the first line put the Manufacturer and on the second line put the Detail Description used earlier. Take the stencil out of the edit mode by left clicking on the stencil icon in the top left hand corner of the stencil window and choosing edit. When prompted whether or not to save changes, click yes.

Issue Xenta 5/7/9xx locks up during boot up sequence. Plugged into the service terminal (RS-232-B) during the boot up sequence, it can be observed that it stops processing on the "InstallDrivers" command. In some situations the error log produces the 49154 error code. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In some situations the error log produces the 49154 error code. If the Xenta 511/527/913 is not booting correctly and stops processing on the "InstallDrivers" command, visible via a Hyperterminal connection, the cause typically is that the Xenta controller is underpowered. Resolution The Xenta controller can survive some drop in power after the initial boot up sequence, but it vulnerable to an insufficient power supply during the boot up sequence. To avoid this problem simply provide the Xenta controller with a stable power within the documented range. The 49154 error code is typically an issue with the power coming to the Xenta, the transformer or something, and a smaller chance of a short from the LAN which is causing this power instability. Mark said they can recycle the power, the Xenta comes back and works for a bit, then the same error. Check the transformer, then with a replacement Xenta in hand, upgrade firmware if possible. If not able, replace Xenta and if not to expensive, replace transformer at same time. 

Issue If you are using OPC Server for I/NET on a computer with Windows XP with SP2 you may have some difficulty connecting to the OPC Server from another computer. Environment OPC Server for I/NET Windows XP SP2 Cause Incorrect DCOM settings will prevent a connection from another PC. Resolution Start > Run > dcomcnfg Right click My Computer found under Component Services, Computers. Click on the COM Security tab. Click the Edit Limits on the Launch and Activation permissions. Add ANONYMOUS LOGON with remote launch and remote activation permissions.  

Issue Loaded I/NET Seven revision 2.10 for the first time on a PC and reports come up with an error that "Server has not yet been opened" Environment I/NET site Cause Loaded I/NET Seven revision 2.10 for the first time on a PC and reports come up with an error that "Server has not yet been opened" Resolution There are a couple of items that needs to be checked to get this working again and there is a workaround to it as well. First, check these items: Verify that TCP/IP is checked in the Active profile in I/O Server Configuration. Using Windows Explorer, open C/Program Files/MSSQL Server/80/Tools/Binn/SVRNETCN.exe, double click and verify that the TCP/IP is listed in the Named Pipes in the Enabled Protocols window. If it is not, then please enable it by selecting the Enable button; this moves it over to the other column. Now restart I/Net and try the reports again, they should be working now. The work around to this is to install an older version of I/NET, version 2.01 or 2.02 first on the PC and then upgrade to 2.10. Do remember that you would have to Un-install/Re-install MSDE again. When prompted to upgrade to Service Pack 4, select the Yes Option. Once this is done and the upgrade is complete, start I/NET and try running Seven Reports again.

Issue Write priority in XBuilder stops BACnet device from receiving a value from a Xenta 913 Environment Xenta 913 BACnet Cause BACnet has a feature in the communication called write priority. This feature allows multiple devices to write to a single address and allow the receiving device know which value it should use. By default the write priority in the Xenta 913 is "12". If you are trying to communicate with a BACnet device that uses a lower numerical write priority (higher logical priority) then the value being written to the BACnet device from the Xenta 913 will be ignored. For example if trying to communicate with an Andover bCX1 controller you will want to use a write priority of "10".   Resolution Find out the write priority of the BacNET device you are trying to communicate with Click on the BACnet MS-TP Master (or BACnet IP Client) in XBuilder Enter the write priority. 

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 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 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 527/913 Hostname in I/NET Environment I/NET site using Xenta Cause getting generic serial number station name using 527/913 Hostname in I/NET Resolution The Xenta 527/913 will show up in the Station Summary report in I/NET, but if you have not configured it correctly it will show up with a generic serial number station name. To define this name you need to specify the hostname of the Xenta controller. This can be done with the setip command with HyperTerminal or via the Web Page in the Configuration\Network\TCP/IP page. Once you have changed this setting you will need to reboot your Xenta controller for the change to take effect.