Issue TAC Graphic Clipart library is a collection of clipart to use as a starting point for an image based graphic page. There are pieces for building air handler ductwork, controlled equipment, dampers and actuators, and water side equipment. Product Line TAC INET, TAC Vista Environment I/NET gpg graphic Vista ogc graphic Cause Without libraries to build a background image for HVAC equipment, it can be difficult to create user-friendly graphic pages to display dynamic data.  In a graphic editor that relies on bitmaps or jpgs to build the airflow diagrams, floor plans, water side diagrams, etc, this library can be used as a starting point. Resolution Download the attached .zip file. Unzip the contents to a location on the hard drive of the computer that will be used to edit the graphic pages. Browse the contents of the .zip file.  It will be separated into logical folders.

Issue Documentation for architectural design for illustration, explanation, sales presentations, or other medium Environment Schneider Electric office, partner office, or other site needing documentation Cause Inability to find literature and need to explain, illustrate, or define issues. Please find the links below for each of the product lines. Resolution Continuum: download architectural Flyer:  pdf   jpg  INET: download  architectural Flyer Vista:  download architectural flyer pdf   jpg  I/NET and Vista together pdf

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 This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell DxT sensors are replaced by STR600, STP660, STD600, STO600 type T with shunt, and use the Satchwell T range chart Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding INET, IA, the document Thermistor Types Tables (Veris Industries) is available.  The 1k Balco resistance chart is also available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

  Issue It is not clear if an INET SubLAN device, such as an MCU, is counted as a connected device for licensing purposes. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation version 7.0 onwards Cause With the re-introduction of INET in EBO 7.0, it is unclear how INET SubLAN devices contribute to the connected device license count.  Resolution INET SubLAN devices below a host INET device increase the connected device count. As a result, a connected device license is required for each SubLAN device. Ensure that your system has sufficient connected device licenses to accommodate all INET SubLAN devices added under host INET controllers.

Issue An SP-RDM2 will be used to add doors to an I/NET-transitioned site. The readers connected to the SP-RDM2 will need to read Hex Card Number credentials. Product Line EcoStruxure Security Expert, TAC INET Environment Security Expert Controller (SP-C) Security Expert Reader Module (SP-RDM2). Cause After transitioning an INET site to Security Expert, you may find it necessary to add one or more new doors. In Security Expert, you add doors to your system by attaching one or more SP-RDM2 modules to the RS-485 bus of an SP-C (up to two doors per SP-RDM2). That is still true for the transitioned system; however, some configuration tasks must be performed to allow the SP-RDM2 to coexist with the SCUs and DCUs that are already communicating with the SP-C.  You will also configure the SP-RDM2 to use the custom Hex Card Number credential you created as part of the INET transition process. Resolution For an SP-RDM2 module to work in conjunction with I/NET modules it must be configured in a specific way. You will need: SP-C firmware 2.08 build 911 or later SP-RDM2 firmware 1.12 build 546 or later Configuring the SP-RDM2: To the existing transitioned I/NET site, add a new Reader Expander for the additional SP-RDM2 reader module. (Note that the last reader expander defined in your existing system may be assigned to a dual-address SCU. If this is the case, make sure the address you assign to the SP-RDM2 is at least two addresses higher than the SCU to avoid address conflict.)  Set the Reader 1 Format and the Reader 2 Format to "Custom Credential". (Note that if the Port 1 Network Type or Port 2 Network Type is set to "Schneider Electric RS485" then this will need to be changed to "Wiegand" to allow you to set the reader format; it is greyed out otherwise. The network type can be set back to "Schneider Electric RS485" afterward.) Set the Port 1 Network Type and Port 2 Network Type according to the type of readers that are connected. In order to correctly convert the card read to the hexadecimal credential format that is programmed for the users, the reader expander must know what card format is being presented. This is done using commands. For the reader on port 1, add the command "R1RawFmt = #" where # is one of the descriptions shown in the table below. Similarly for the reader on port 2, add the command "R2RawFmt = #" where # is one of the descriptions shown in the table below.  If the command is absent, then Wiegand 26 is used as a default. Command Card Type R1RawFmt = Wiegand 26 26-bit Wiegand R1RawFmt = Wiegand 32 32-bit Wiegand R1RawFmt = Wiegand 34 34-bit Wiegand R1RawFmt = Wiegand 66 66-bit Wiegand R1RawFmt = Custom Wiegand Any Wiegand card - parity check is skipped Additionally, the SP-C controller must know which reader expanders to expect on the I/NET network and which reader expanders to expect on the Security Expert module comms network. By default, if the controller command "INET = true" is present in the SP-C, then all modules are considered to be on the I/NET network. Adding an SP-RDM2 to the Security Expert module comms network with no additional commands will result in partial operation but there will be problems. To use a mixture of I/NET modules and Security Expert modules, a command must be added to the programming of all I/NET modules. This command is: "HardwareType = INET" If this command has never been added to any module, and the command "INET = true" is present in the SP-C, then all modules are treated as I/NET. This maintains backward compatibility with existing sites. As soon as the "HardwareType = INET" command has been added to even one module, then it must be added to the programming of all I/NET modules from then on for the site to function as expected. Configuring the SP-RDM Doors to Accept Hex Card Number Credentials Create a new Door Type for reading cards as a Hex Card Number credential and configure it as follows. In the Entry section on the General tab, set the Entry Reading Mode to "Custom". In the Entry Credential Types section, add the "Hex Card Number" credential type. Save the Door Type. Configure each door on the SP-RDM2 to use the new Door Type as follows: In the Setup section on the General tab of the door, set the Door Type to the name of the Door Type you just created in step 1. Save the door.

  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 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 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 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 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.

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

Issue Spare Addresses for use as internal points on an SCU 1284 dual address Product Line TAC INET Environment I/NET Access Control SCU1284 dual address mode Cause What are the ramifications of using the spare point addresses for internal points in an SCU 1284 Resolution Note! It's generally not recommended to use the available address on a subLAN. Addresses marked as "Internal" in the MCU configuration are reserved for internal software points. However, it's crucial to consider that doing so may limit the potential expansion of the subLAN to utilize these addresses in the future.   When a SCU1284 is set to dual channel, it only uses 12 inputs, 8 outputs, and 4 reader points.  Here is a list of all software points and their uses:   XX00 DI - XX03 DI Hardware Inputs used by doors XX04 DI - XX07 DI Spare Hardware Inputs XX08 DI & XX09 DI SCU tamper and power monitoring points XX00 DO - XX03 DO Hardware Outputs XX04 DO - XX07 DO Spare software only points XX08 DO & XX09 DO Reader Points YY00 DI - YY03 DI Hardware Inputs used by doors YY04 DI - YY09 DI Spare software only points YY00 DO - YY03 DO Hardware Outputs YY04 DO - YY07 DO Spare software only points YY08 DO & YY09 DO Reader Points   See the following documentation: TCON312-0910.book (schneider-electric.com)