Building Automation Knowledge Base

  Issue After transitioning TAC INET Access to Security Expert, SP-C health status shows the message "Ring-loop failure at reader expander".   Product Line EcoStruxure Security Expert, TAC INET Environment  Security Expert SP-C   TAC INET Access Control Cause This message indicates that the ring-loop connection is not made.  For the ring-loop connection, the opposite end of the INET subLAN must be connected to Reader 2 on the SP-C. Resolution This message can be ignored if an INET subLAN loop is not used. The Ring-loop Failure error can be avoided by running a jumper wire from Reader 1 pin D0 to Reader 2 pin D0, and another jumper wire from Reader 1 pin D1 to Reader 2 pin D1 on the SP-C that is hosting the INET subLAN If an INET subLAN loop is used, this message indicates a break in the ring loop.    Reference Guide I/NET Access Control Transition to EcoStruxure™ Security Expert (Hardware            Guidelines for Transitioning from I/NET Page 23)

Issue I have an I/NET Controller with a forgotten DCU password. How can I recover it? Product Line TAC INET Environment I/NET Seven Site Cause A DCU password was set on the I/NET Controller and has been forgotten. Resolution Send an email to your local support. Include a copy of the current save file for the controller in question. Support will advise you on the password. Recommendation: For future use, either remove any controller passwords or record them in a secure location where they can be retrieved easily.

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Understanding how to check the firmware version of the USB-485-I/NET adapter and upgrade it to the latest version. Product Line TAC I/NET, EcoStruxure Building Operation Environment Building Operation I/NET USB-485 I/F Building Operation Automation Server Building Operation Automation Server Premium Cause If the firmware version of an I/Net USB interface is at an older firmware version then it may need to be updated. Please check the Exchange website for the latest firmware version Note: If the USB adapter is not at least at firmware version 1.02 then the system may experience communication issues in which I/Net values are not updating in EcoStruxure Building Operation or Automation Servers may be dropping offline.  In some cases, the Enterprise Server can lock up due to the older firmware in the I/Net USB adapter. Resolution To download the latest "USB-485-Inet Firmware Update Utility" click here. To Verify the Current Adapter Firmware Version in EBO 2.0 and Higher Right click the I/Net Interface is the System Tree of WorkStation and choose Properties. Down towards the bottom of the Basic tab you will find the Firmware Version.   To Verify the Current Adapter Firmware Version in SBO 1.9 and Lower Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Do not hold the pushbutton in on the USB Interface. Run the firmware executable. Press Enter. It will display: "Found USB Device on COMX" and will display the hardware version, software version, and the firmware date. It will then say, "Press Enter to begin the upgrade.  Note: Pressing Enter here will only repeat the hardware and firmware versions. The process to Upgrade the Adapter Firmware Note: If the I/Net USB adapter is already plugged into the laptop from checking the firmware version as described above, then to start the upgrade process USB cable will need to be unplugged from the laptop. Then follow the steps below. While holding down the pushbutton of the I/Net USB adapter, unplug the adapter's USB cable from the AS/AS-P and plug it into your laptop. After it is plugged into the laptop, release the pushbutton.  You will see that the LEDs on the interface are not flashing. On the laptop, run the firmware executable. After the command window opens, press Enter to start the update process. It should display "Unprogrammed device located" followed by "Device programmed successfully". Next, it will say "Found USB Device on COMX" and show the hardware version, firmware version, and the firmware date. Press Esc to close the command window.  The firmware upgrade is now complete. Note: Some laptops will not recognize the USB Interface and will not assign it a Com port.  If this is the case you will still be able to upgrade the firmware.  But instead of giving the Com port the and the firmware version after the upgrade is complete, it will show "Unable to find USB Device".   Also, you would not be able to check the firmware version prior to upgrading as mentioned above.  To correct this you must install the 7801 Tap.inf driver.  Click here to download the 7801 Tap.inf drivers. To install the 7801 Tap.inf drivers: Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Go into Device Manager and find the I/Net USB Interface.  It will have an error because of no driver. Right-click on it and choose to Update Driver Software... Select Browse my computer for driver software and browse to the 7801 Tap.inf file. Then follow the instructions above.

Issue Links to the Technical Tips Papers Product Line TAC INET Environment I/NET Seven Tech Tip Cause Formerly only available on the FTP site, now available in the Knowledge Base. Resolution Tech Tips linked below. Tech Tip 001   System S7000 Upgrade to I/NET 7700 Tech Tip 002   Calculated Point and Docutrend Operator Rankings Tech Tip 003   MIP01 Memory Interface Processor Installation Tech Tip 005   I/NET 7700 Printer Enhancements Tech Tip 006   Use of LAN Repeater on I/NET 7700 Tech Tip 007   I/NET System Messages Tech Tip 009   I/NET 7700 Setup Tech Tip 010   ICI HHC Memory Addresses Tech Tip 011   S/90 Purging Visitors Tech Tip 012   Shipping MIP Products Tech Tip 013   Mechanical Door Interlock Wiring Tech Tip 014   S90 Graphics PCX File Requirements Tech Tip 015   Indala Reader Card Types Tech Tip 016   New RAM Configuration for MIP Tech Tip 017   Transient Protection On DPUs with I/Disc Tech Tip 018   I/NET 7700 Taps and Building Managers Bias Straps Tech Tip 019   Docutrend and Hard Disk Space Tech Tip 020   Docutrend Reports Tech Tip 021   ADAA Tap Addresses Tech Tip 022   Docutrend:Number of Days of Report Tech Tip 023   S/90 Memory Requirements Tech Tip 024   ADAA System Messages and Docutrend Setup Tech Tip 025   I/NET 7700 Work-Arounds and Known Problems Tech Tip 026   I/NET 7700 Controllers BOOT ROM Compatibility Tech Tip 027   S/90 Color Mapping Tech Tip 028   Controller Battery Back-up Tech Tip 029   I/NET 7700 Host Sign-on/off and Host Lost/restored Messages Tech Tip 030   MR Minimum Trip and Close Tech Tip 031   I/Disc Installation Method Tech Tip 032   ADAA S7000 to I/NET 7700 Upgrade Tech Tip 033   I/DISC Reader Maintenance Tech Tip 034   UCI/UC Use of Bit Offset 08 & 09 Tech Tip 035   MR Memory Usage Tech Tip 036   DPI, MRI & MCI Memory Allocation Tech Tip 037   WIRING AND CONFIGURING CSI CONTROLLERS Tech Tip 038   Programming the 7750 Building Manager Tech Tip 039   7910 and 7920 DPU Memory Usage Tech Tip 040   Lantastic 6.0 Installation for use with S/90 Tech Tip 041   Using pcANYWHERE 5.0 with S/90 Tech Tip 042   MR Memory Usage Correction Tech Tip 043   “P” only Mode of Operation for PID Modules Tech Tip 044   I/STAT Functionality Tech Tip 045   I/NET 7700 Backup Station Tech Tip 046   S/90 and RDTAP Dial Tech Tip 047   Mixing Different Types of ADAA TAPs Tech Tip 048   Universal Asynchronous Receiver-Transmitter Chips Tech Tip 049   Special Days Tech Tip 050   Supervised Inputs Tech Tip 051   I/NET 7700 Ethernet LAN System Tech Tip 052   I/NET 7700 Modem Compatibility Tech Tip 053   I/NET 7700 Modem Compatibility Update Tech Tip 054   SETTING UP THE SITE TAP EDITOR TO CALL A PAGER Tech Tip 055   History Recall Report to DBF File Output Tech Tip 056   Use of I/NET 7700 Message Masking Tech Tip 057   LTS80 Series Lini-Temp Sensors Tech Tip 058   MR55X with Kavlico Transducer Tech Tip 059   I/NET 7700 Controller Interface Cabling Tech Tip 060   Use of DC/DM Points with Sub-Lan Devices MRs and UCs Tech Tip 061   AI and PI Fractional Digits Tech Tip 062   PID and Control Point Tech Tip 066   Momentary Release & Automatic Time Schdl. Release w/ I/NET 7700 used w/ Elevator Tech Tip 063   I/NET Personnel Reports Tech Tip 064   Watermark's in S/90 Video Badging Tech Tip 065   System 90 and Video Badging System Installation Tech Tip 067   12 Steps to I/NET Access Control Tech Tip 068   Application to Disable the “1-OPEN” state of a Supervised DI point Tech Tip 069   TTS100 SERIES THERMISTOR SENSORS Tech Tip 070   BATCH FILES FOR REMOTE SITE GRAPHICS PAGES Tech Tip 071   Access Control Doc-to-DIF Report Tech Tip 072   Standalone MR-VAV-AX Start-up Tech Tip 073   I/NET 7700 Modem Compatibility Tech Tip 074   SETPOINT ADJUSTMENT DEVICE PROGRAMMING Tech Tip 075   Using Belimo NM24 Actuator with MR-ASC’s Tech Tip 076   Running I/NET 4 on a Windows95 Tech Tip 077   How to Convert an Idisc Number Tech Tip 078   How to program a Modem without the use of a TerminalEmulator Tech Tip 079   COMMONLY ASKED ASC QUESTIONS Tech Tip 080   S/90 ACI/DACI Battery Life Tech Tip 081   Integrated I/NET Video Badging Requirements for Single PC Systems Tech Tip 082   How to program Forced Door & Door Open Too Long Alarms Tech Tip 083   How to get started with Integrated I/NET Video Badging

Issue Need to change from the Small Number Format (Card Number) to the Large Number Format (Facility Code + Card Number). Requirement for Security Expert Transitions with I/NET Hardware.   Badging card on SCU1284 Reader using Security Expert, the reader event displays "Format error RD xx Port x Error Number of Bits" From Security Expert Client Events Product Line TAC INET, EcoStruxure Security Expert Environment I/NET Seven Security Expert Transitions Cause The I/NET system is limited to a maximum number of access cards, 32,000 per Tenant.  If a larger number is required, then I/NET must be configured to use large card numbers.  The Large card number format described in the Resolution MUST be completed before transitioning from I/NET to Security Expert and utilizing the I/NET SCU hardware as detailed in the Transition Guide Security Expert - INet Access Control to Security Expert - Reference Guide. Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this, use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Wiegand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can determine the Decimal number of the first card in the system (e.g., Card #970 Facility code 199) is the Decimal number 13042634, using a 26-bit Wiegand Excel spreadsheet.  This number will become the Source number in the Key/Card Translation table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the I/NET Seven Access Control editor.  This table will be removed after running the provided SQL Script.  The Key/Card Translation must contain: Source - Decimal number calculated in Step 3 above (13042634) Target - First Individual number shown in the Tenant (970) Count - Number of Individuals as shown in the Tenant (10000) Tenant - Tenant number this translation refers to (1) If there are multiple Tenants, then this process MUST be repeated for each Tenant Tenant Editor and Key/Card Translation Editor Shut down I/NET completely and run the attached SQL Script. Then once the script runs then, restart I/NET and look in the Individual Parameters editor, as shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify a Hex number and the decimal number matching that from the Excel spreadsheet (Step 3) is seen in the Individual Editor Card section. NOTE: There may be multiple card entries here; the Last entry shown is that entered by the SQL Script.  It will depend on whether an existing Card entry was entered for the Individuals before running the SQL Script.  To have large numbers working on a site DipSw #7 has to be turned ON for the 7910/7920 DPUs. For the SCU1284 in the door editor, at the top center of that editor, there is a check box, "Card Translation," which has to be enabled for large numbers to work in the SCUs. An SLI “SAV” should then be done because that is where the Card numbers and Door settings are stored. Then perform an SLI restore. Followed by a DPU restore to all of the door controllers. NOTE: Steps 6d. and 6e. are NOT required when performing the transition to Security Expert as this information will be performed by the SP-C.   

Issue How to use an LTS80 (Lini-Temp) sensor on a 7716 as a two-circuit.  Product Line TAC INET Environment I/NET Site Cause How to use an LTS80 (Lini-Temp) sensor on a 7716 as a two-circuit.  Resolution Place a 10K ohm,1/8 watt resistor in the corresponding resistor "A" position. Jumper J22 to 15V For Fahrenheit, M = 0.21978, B = -459.6 For Celsius, M = 0.12210, B = -273.0 Using the first input on TB1 as an example, place the white lead of the sensor on terminal 1, place the orange on terminal 3 (+V)

Issue Can I use an LTS80 Lini-Temp sensor on an MR or ASC? Product Line TAC INET Environment MR ASC LTS80 Lini-Temp sensor Cause MRs and ASCs were not designed to use the Lini-Temp. Resolution This is not recommended. The accuracy is not good.

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7728 PCU Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7728 PCU 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 10k ohm resistor in slot "A" Refer to TCON 114: Model 7728 Series I/SITE I/O Controllers Installation Guide for details.

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7700 DCU Product Line TAC INET Environment 7700 DCU LTS80 Lini-Temp sensor Cause Conversion coefficients must be set to read temperatures properly. Resolution For Fahrenheit: M = 0.17582 B = -279.4 For Centigrade: M= 0.09768 B = -173.0 Refer to TCON 095 for Resistor(s) 41-55 to clip (suggest you clip only one side)

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7716 PCU Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7716 PCU 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" Refer to TCON 096: 7716 PCU Installation Guide for details

Issue Set up a two wire LTS80 Lini-Temp sensor on a UC Product Line TAC INET Environment UC microcontroller LTS80 Lini-Temp sensor Cause Conversion coefficients must be set to properly read temperatures. Resolution For Fahrenheit: M = 0.4235 B = 32.0 For Centigrade: M= 0.2353 B = 0.0 The sensor's white (WHT) wire goes to AI-X of the UC input, and the orange (ORN) wire goes to +15v of the UC input. Refer to TCON 069 for details.

Issue Direct substitute for the obsolete CSI Lini-Temp sensors Product Line TAC INET Environment I/NET Cause Need a part number to replace a discontinued part Resolution Yes, there is a direct substitute for the 2-wire and 3-wire versions of the old Lini-Temp sensors. The company is ACI (Automation Components Inc.). For this substitute, use the ACI/592-10K Series sensors attached. Their website is located at http://www.workaci.com/. If you are not sure what ACI Product matches the old CSI product, their Customer Service or Sales Engineers are knowledgeable in the CSI Product line. They will be glad to help you with your selection.  

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7718 PCU Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7718 PCU 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 J31 to 15 VDC 10k ohm resistor in slot "A" Refer to TCON 106: 7718 PCU Installation Guide for details

Issue What purpose does Scan Interval serve on the point? Product Line TAC INET Environment All versions of I/NET software. Cause Understanding the Scan Interval on I/NET Points. Resolution The Scan Interval determines the length of time that elapses between scans. The controller scans the point based on the value set here (1-255 secs) and then updates the state/value on the screen. Common Concerns for Choosing Scan Intervals. The Scan rate determines how often the point display is updated in either the controller summary or a graphics page. The fastest the page will update is based on the Monitor refresh interval set in the Host Configuration Editor. The Scan interval determines when the calculation on a point is run. This means if the point has a 10-second scan interval, the calculation will only be run every 10 seconds. It is advisable to only use calculations that do not require running faster than that, as it can waste system resources. If you have a situation where logic requires an immediate response, use DDC or an event sequence. The Scan interval is used to determine when an indirect point goes OLD.  It will go old if the indirect point requests data from the global point and does not receive it after two scans.  Global and indirect points should typically have higher scan rate values.   The Scan Interval does not affect how often a global point broadcasts data. This is determined by the broadcast change in the counts setting or by a change of value for a discrete point. Higher values are usually better when dealing with scan intervals. This prevents hunting in DDC and the accumulation of old data. Whenever one point references another, these points should have identical scan rates. Problems have been reported on systems where the receiving point scans faster than the sending point. When dealing with points that send or receive data from outside of the physical device, consideration should be made to ensure all points on a given LAN segment are not broadcasting at the same time. The ideal solution is to use prime numbers for scan intervals on this type of point. For more information on Global and Indirect Points, see I/NET Global and Indirect Points Overview and Recommendations  

Issue I/NET Server (Remote Client Configuration) can not connect to I/NET network even though the workstations (other Hosts) can. All workstations (I/NET hosts) transactions are not updating, but alarms and messages are. Product Line TAC INET Environment I/NET Seven Remote Client Configuration Remote Desktop / Terminal Services Cause Unless the Remote Desktop is configured for a single user session, it's extremely likely that multiple instances of the INetIoSrv.exe will be established. This will cause issues with I/NET, such as described above. It is strongly recommended that an alternative method of remote connection be used. Resolution An alternative remote connection should be used. We recommend VNC, Ultra VNC, WinVNC, or a similar protocol. This will ensure that multiple user terminal sessions do not open. Remote Desktop can also be configured for single-user operation, but the above software packages are the preferred remote connection method. See the following external site on "How to force a single session Remote Desktop session per user." http://remotedesktoprdp.com/Force-Single-Session-Allow-Multiple-Sessions-Per-User.aspx  

Issue Configuring a Xenta 527/NPR - Combo Product Line TAC INET Environment I/NET site with a Xenta 527 End of Commercialization of TAC INET Building Management System Products Cause How to configure a Xenta 527/NPR - Combo Resolution When setting up a Xenta 527 NPR or Combo Unit for the first time, there are six basic steps to commissioning the Xenta 527/NPR-Combo. These steps are described below. Connect the Xenta 527/NPR-Combo to 24 VAC power. Refer to the TAC Xenta 527 Installation Instructions (0FL-3956). Connect a PC to the Xenta 527/NPR-Combo. Attach a serial cable from the computer’s COM port to the RS-232 B port on the front of the Xenta 527/NPR-Combo. Refer to TAC Xenta 511/527/911/913 Handbook (0-004-7870) for complete instructions. Set the Xenta 527/NPR-Combo's communication parameters. Start a Hyper Terminal Session on your PC. Once the cable is connected, it will display the 527's default information. Note: The factory default login/password is root/root, at the dsh> prompt, type inethost then enter. Now add your I/NET information for reference host, etc. Restart the unit, when the "dsh>" prompt appears, type setip then enter this command will let you set its IP address and other basic parameters. Note: Refer to TAC Xenta Server Manual - TAC Xenta 527/NPR-Combo Supplement (0-004-7682-1) Chapters 3 & 5 for instructions. Once completed restart the unit again. Connect the Xenta 527/NPR-Combo to the Ethernet. Attach the Xenta 527/NPR-Combo to the network at the necessary location. Refer to Chapter 4, “Connecting the Xenta 527/NPR-Combo to your Network. Now ping the unit through the cmd prompt on your PC to verify that communications is taking place on the Network. If necessary, load the Xenta 527/NPR-Combo’s software. Note: The Xenta 527/NPR-Combo is delivered from the factory with preloaded software. If you need to reload this software, you can download it from the EcoXpert website. Before installing downloaded software, review its release information to verify compatibility with your hardware. Configure the Xenta 527/NPR-Combo to communicate with I/NET. In order for the Xenta 527/NPR-Combo to communicate with I/NET devices from across an Ethernet, you must first define basic communication parameters. Tip: You can now access the I/O configuration editor by opening NP Routers. From the Netplus Router Summary, select the router, modify it, and print the configuration for your records or the customers. Once these steps are followed, your unit should be online, communicating to the Network, and seeing all your controllers at this site.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C    Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C Cause I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B.  If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software.   Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C.  If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important:  Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board.  If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.

Issue How to identify what ports are being used on a PC. Product Line All product Lines. Environment Any Windows OS Cause Running multiple applications on the same PC without managing TCP/UDP port assignments can lead to conflicts. Resolution TCPView will help you identify all ports and services to each application. Download from Microsoft's website http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx Detailed instructions are available at the site.