Building Automation Knowledge Base

Issue Unable to install I/NET Seven after downloading software from Buildings Business Extranet. Gets error "unable to open, file is corrupt" when using WINzip Environment Windows XP Windows Vista Windows 7 Windows Server 2003 WinZip Inet 2.30 or below WinRAR   Cause Software was created in a number of parts which all parts needed to be downloaded before unpacking was attempted. WinZip is not a valid software to unpack the Inet install files downloaded from the Buildings Business Extranet. (now ecobuildings) Resolution Downloading all parts of the I/NET software from the Buildings Business Extranet Make sure all files are in the same folder. You will need to use WinRAR to unzip the files Download from here http://filehippo.com/download_winrar_32/ You must unzip the files before trying to run the install, if you open part 1 of the files this will automatically unzip all parts of the software, once all files have been unzips the install will work NOTE: This was an issue with Inet software versions 2.30 and below, all new version can be downloaded and unzipped without issue from the ecobuildings website.

Issue Lan Tap Overflow message received in AMT Environment All versions of I/NET Software Cause The message capacity of a LAN Tap has been exceeded and they are now being FI/FO (First In, First Out) mode, meaning that the first message that came in will be the first one that goes out. When this happens, the LAN Tap Overflow message is displayed in AMT. Resolution To resolve this issue, verify the following: Open up AMT and look at the Messages and see if there are any controller that having issues Verify that address and correspond that with the Host or Link Tap that it is coming from. Rectify the issue, whether it is communications or power and the error should go away.

Issue Unable to communicate to a Hand-Held Console (HHC) on Windows 7 Product Line TAC INET Environment Windows 7 HHC Cause Com Port settings not working with the HHC Resolution To resolve this issue, change the following port setting that is used to communicate to the HHC. DCB is set for Even Parity Flow Control is disabled Stop bits is 2 Baud Rate is 1200

Issue Where is the I/NET Host Tool located? Environment All versions of I/NET Cause Unable to get the Host Tool to download for a system that has a valid CD and Key. Resolution The Host Tool is located on the original CD or could be downloaded from The Exchange Download Center . If it is not there then follow these steps if a CD with the required version is available: Place the CD into the PC and open up Windows Explorer Browse the CD and  go into the Support Folder Open up the Host Tool folder and in there is a Host Tool file Download it on the PC and execute it to install the Host Tool.

Issue Leakage voltage on relays Environment I/Net Seven versions using SCU 1284's. Cause There is a small leakage current through the integrated MOV transient suppressor across the NC and NO contacts on the four relays that are used to control the door locks. Resolution If the relay is connected to a very high impedance (electronic) device input where it is falsely detecting as a relay ON condition, there are two things that can be done: 1. Place a 10,000 Ohm resistor on the device input to ground (or relay output to ground) 2. Move to one of the other unsuppressed relays ( relay 3, 4, 7 or 😎

Issue Is IPv6 supported with I/Net and SE Vista Controllers? Environment NPR2000 Xenta 527-NPR, 527, 731, 913 Cause IPv6 with I/NET and Vista Controllers Resolution  I/NET and Vista Controllers DO NOT support IPv6

Issue Using Access Initiated Control to trigger an event sequence Environment I/NET Seven 7798 Cause Custom door applications sometimes require several steps to be initiated on a reader entry Resolution Create in Internal DO point (Point1) where 0 = off and 1 = ON, The scan interval should be shorted than the expected time between 2 card reads at the door. Add a Calculation to point1 that sets it equal to 0. [C0 where C0=0] Add an event extension to the point that triggers your desired event sequence on the specified state of ON Create an AIC that starts point1 on a reader Entry Create your event sequence with the desired programming. The effect should be that a reader entry causes Point1 to turn on triggering the event sequence

Issue  Temporary groups can't get a PM time, only AM Environment I/NET Cause The time are using US settings AM/PM on for example a European PC Windows don't use AM/PM Resolution Enter Control Panel and choose Regional and Language Settings On first tab click Customize Choose tab "Time"  Set AM and PM symbol to AM and PM Click OK Restart I/NET IO server and try again.

Issue AMT message "Time-sync failed" Environment I/NET Seven AMT Cause The Time-sync failed message indicates that an attempt to sync time with a DCU has failed. Resolution Time synchronization is a function of DCU Synchronization. This is only intended for use with direct-connect, TCP/IP or AD/AA communication. If your site is using Integrated Dial or NPR Dial connection, this explains the alarm and must be deactivated. To View the systems DCU synchronization settings. Log into I/NET and select Edit>Host Computer>Network functions. From there you can select a link via a dropdown menu view the "Sync" setting for each controller. If Sync is enable on any controller that are offline or no longer exist, disable synchronization (and any other Host function)  If time sync is not desired, it can be disable which will also remove the alarm. If time DCU synchronization is desired, This is likely an indication of a communication failure. Determine if this has occurred on an entire Controller LAN or just a single controller. Use this as a starting point and work towards the PC looking for communication errors.  

Issue Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are supported by enabling the WoW64 optional feature. NOTE: These are general instructions for utilizing the WoW64 function. Not all Schneider Software will be able to run in an emulated environment. If uncertain, please check with Product Support Services to ensure proper installation. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows Server 2008 R2 WoW64 feature. All 64bit OS Cause If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. WoW64 option in in undesired state. Resolution If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component that is installed by default on R2 releases. You can save resources by removing the feature if you are not going to be running 32-bit applications on your Server Core install. Install the WoW64 Execution Layer using the following command: dism /online /enable-feature /featurename:ServerCore-WOW64 If your solution has a .NET 32-bit dependency, then also invoke the following sequence: dism /online /enable-feature /featurename:NetFx2-ServerCore dism /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 Note: In Windows Server 2008 R2 RC1, WoW64 is enabled by default. If you don't want WoW64 enabled, just disable the feature as follows:  dism /online /disable-feature /featurename:ServerCore-WOW64

Issue Generating a Xbuilder project results in the error message "The size of the generated project is xxxx KB, which exceeds the maximum size 8192 KB". Environment Xbuilder 5.x.x Cause The generated project size exceeds the maximum limit due to the following reasons: The project contents made up of graphic pages, inserted networks (LON, I/NET, etc), large images (BMP, GIF, etc), or imported files in the UserTargetImage directory cause the project to exceed the limit. The option "Send Project backup file to target device" is checked and this causes pushes the project size over the limit. Resolution Generate the Xbuilder project to see how far above the limit the project currently is. Open the Project\Settings and uncheck the "Send Project backup file to target device" and regenerate the project to see the difference in file size. If the size difference is significant then check for large files in the project directory that should not be sent to the device such as project or device documentation files such as PDFs. Remove these files from the Xbuilder project directory and generate the project again.  Search the Xbuilder project directory for the largest size files such as graphic pages and try to find way to reduce the size by converting background image formats that will result in smaller file sizes. Example convert BMP file to PNG or JPG format.

Issue Xenta 913 will not communicate with the Bacnet device. Wireshark does not show any packets between 913 and Bacnet device Environment Xenta 913 Cause The Xenta 913 has been installed on a TCP/IP network with a switch between the Xenta 913 and Bacnet device. Resolution A basic switch does not pass broadcast messages that a Xenta 913 uses to talk to Bacnet device. The solution to this issue is to replace the switch with a Hub or use a managed switch. If a managed switch is used it will need to be configured to pass broadcast messages from the Xenta 913 to the Bacnet device.

Issue Error: "Tenant X individuals for door LLSSPPBB DO exceeds 24,000" when attempting to select additional doors within Tenant Editor Product Line TAC INET Environment I/NET Seven 2.15 and above DPU / SCU Firmware 3.23 and below Cause SCU / DPU firmware revision 3.3 and lower only supports 24,000 individuals per door, even though the I/NET Software (I/NET Seven 2.15 and above) allows you to allocate 32,000 per tenant.  This is why it is important to maintain consistency between I/NET Software Revisions and Hardware firmware. The I/NET Seven 2.xx Compatibility Matrix lists this information. Resolution To allow the controllers to support more than 24,000 individuals per door the firmware in the DPU / SCU must be at revision 3.24 or above. This firmware is included with I/NET Seven Revision 2.15 or above. Although TAC I/NET supports up to 32,000 individuals per tenant, the model type and revision date of a tenant's door controllers will ultimately determine how many individuals will be supported. The following table shows the capacity of various door controllers. For any door controller with revision 2.2x or later firmware, you would have to define multiple tenants in order to reach the door controller’s maximum storage capacity. Firmware Revision Door Controller Maximum Number of Individuals 2.1x and earlier  DPU7910, DPU7920 Up to 24,000 per door 2.2x to 3.23 DPU7910, DPU7920 without DPU48K Up to 48,000 per controller   DPU7910, DPU7920 with DPU48K Up to 48,000 per door 1 3.24 and later DPU7920 with DPU48K, SCU 1284 Up to 64,000 per door 1   1 Typically, the total number of individuals for a selected door cannot exceed 32,000. However, if one of the two doors controlled by a DPU is not being used (that is, no individuals are assigned to the door), you can assign up to 64,000 individuals to the door that is being used. This also requires the use of more than one tenant since no single tenant can have more than 32,000 individuals.  Refer to TCON300-06/11 Chapter 9-62 for further information.

Issue Unable to get I/NET to install on Military Bases. Environment Windows 7 and Windows Vista OS with I/NET Seven versions 2.40 and above. Cause The version of software that is being used by the military does not allow the password scheme to create the necessary permissions for correct functionality. Resolution Remove I/NET from the PC. Reconfigure the PC with the original version of Windows and or Vista Load I/NET on this version. Upgrade PC to Windows 7 Gold or Windows Vista Gold Once completed then restart I/NET again.

Issue Unable to use Calculations on a subLAN device on a 7793 Environment 7793 I/NET MR controllers Cause The 7793 does not pass data between the A and B channel. If your calculation is comparing a point on a different channel than where the calculation resides you will need to modify the sending points global level Resolution Connect to the controller Select Edit>Controller>Resident I/O Locate the Point you are using in your calculation Modify the point Set the Global Level to "LAN" Click OK Modify the point that has the calculation extension Change it to Internal Click OK

Issue 'Make Active' button grayed out in I/NET Configuration Profile Can not change my active I/NET (configuration) profile. Environment I/NET Seven 2.40 and above Cause The INetIoSrv.exe application must be shutdown before you can make any other configuration profile active.  This change was made in I/NET Seven version 2.40 and above. Resolution To enable this button the INetIoSrv.exe (IO Server) application must be shutdown.   Ensure I/NET, AMT and the IO Server are not running Start 'I/NET Configuration Profiles' editor Select desired profile and select Make Active If I/NET has every been running as a service on the PC, you will need to verify that the service is not running. You may need to re-register and stop the service.

Issue Parameters, configurations, calibrations and other settings are not stored within the M/STAT, I/STAT, or any of the STR series wall sensors with the exception of the STR-350. No data can be carried with the stat from one controller to another. Environment M/STAT I/STAT STR-150 STR-250 MR-VAV Xenta 102-AX Xenta 121 Xenta 104-A Various other STR series sensors and Xenta controllers Cause The aforementioned stats use only key code to communicate with their associated controllers and do not store any of their own parameters or settings. Resolution These stats may be moved from one controller to the another or a controller may be replaced while maintaining the original stat without carrying over any settings from the original controller.

Issue The Xenta 913 can only be used for both Modbus and BACnet at the same time if they are being used on separate ports or are both on the IP port. BACnet and Modbus can not both be used on the RS-485 A port at the same time. Environment Xenta 913 XBuilder BACnet Modbus   Cause Only the Ethernet 10 Base-T port on a Xenta 913 may have more than one interface at a time. Resolution The Xenta 913 may interface with BACnet and Modbus at the same time only if: The RS-485 A port is being used for Modbus and the Ethernet 10 Base-T port is being used for BACnet The RS-485 A port is being used for BACnet and the Ethernet 10 Base-T port is being used for  Modbus The Ethernet 10 Base-T port is being used for both BACnet and Modbus and the RS-485 A port is either unused or is being used for only BACnet or Modbus but not both The Xenta 913 may not interface with both BACnet and Modbus if they are both connected to the RS-485 A port.

Issue No link LED on a Desktop's and Laptop's Network Interface Card (NIC). Environment Windows OS Cause Network interface card has power management feature enabled.  This will shutdown the network interface card if no activity is present, battery is low on power, or battery is intermittent. Resolution Disable power management features under Device Manager Network Adapters. 

Issue DDC Lines show only inconsistently when viewed through a Xenta 527 Web Server Graphic Environment I/NET Xenta 527 5.1.3 and below Cause Issue corrected in 5.1.4 release Resolution Upgrade the Xenta 527 to the latest revision of I/NET or at least 5.1.4 Upgrade Xbuilder to the exact same revision Send the upgraded project files to the upgraded controller.