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 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 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 MR-VAV-AX (ASC) as Standalone Product Line TAC INET Environment MR-VAV-AX Cause Air balance must be done to calibrate the airflow sensor on the MR-VAV-AX. Resolution Download Tech Tip 072   Equipment: Air Balancing Hood or Manometer and Digital Thermometer.   Assumptions: The MR is powered up. An I/STAT, or an M/STAT is plugged into the service port of a S/STAT or W/STAT, which is plugged into the MR-VAV-AX. The AHU is running. The Space sensor is installed. The Duct static pressure is constant. The dip switches are set properly for the desired VAV configuration. (See TCON 147) You have a Pocket Reference Card (TCON 149). You are familiar with the use and operation of the I/STAT / M/STAT with respect to navigating the Service mode to various mnemonics’ menus. (See TCON 147)   Initial Setup You should notice that two things have already happened: The MR is in the unoccupied mode. The setpoint adjust has defaulted to "-5", making the setpoint display appear low. For the MR to work in a Standalone mode the use of an off-board time clock for the occupied and unoccupied times is recommended. It should be connected to the "Local Occ" point(TB5 input #2 to TB5 ground.) The "Occ" mnemonic under Unit Parameters must be set to ONE for the "Local Occ" point to be used. If the MRs are to be left in the occupied mode indefinitely, install a jumper across the "Local Occ" point instead of using the time clock contacts. Connect the jumper to (TB5 input #2 to TB5 ground.) Using the I/STAT or M/STAT go to Set Temp and increase the value by 5°. This will get the Setpoint Adj. back to zero.   "Cooling Low Flow" (CLF - min. CFM) and "Cooling High Flow" (CHF - max. CFM) Setup Put the I/STAT or M/STAT into the Service Mode. Go to "AP", select "CLF", (the value displayed is "multiplied by" 1000 so 0.24 is 240). Enter the minimum CFM by using the arrow keys to position the LED for the digit to be changed and enter the value by using the "+" and "-" keys. Notice the decimal position will not move. You are entering the value "multiplied by" 1000. Refer to the Pocket Reference Card (TCON 149), paragraph 5. Usually the minimum air flow value can be found on the Mechanical box schedule drawings. The lowest reading that the ASC’s sensor can sense is about .03" to .05" of Water Column(W.C.) Therefore, the "CLF" must be set above this level. If the ASC is required to control in that range, it will tend to oscillate. Select "CHF" and enter the maximum CFM for this box at 1" W.C., this can be found on the DeltaP to CFM graph that is associated with this VAV box’s pickup device, or the box schedule may also provide the maximum cfm value.   Central Plant Heat "Heating Low Flow" (HLF) and "Heating High Flow" (HHF) Setup Use only if Central Plant Heat is required and setup Unit Parameter’s(UP) CPH set to "1". An open contact at Input 3 will indicate that the Central Plant Heat mode is on. A closed contact indicates CPH is off. Using the procedure described above for "CLF" and "CHF" instead select "HLF" and "HHF" and enter the desired Low and High Flow CFM values for the Heating Mode. Otherwise go to the next section. NOTE: If you have a auxiliary stage of heat, it will not be energized unless the CFM input is reading at least 80% of the "HLF" setting.   Calibrate the flow pickup: Go to Unit Parameter "UP", select "dd" (duct diameter). Enter the duct diameter this will enable the MR to calculate the Pickup Factor "PF" for us. NOTE: It is recommended that you begin with the value provided by the VAV Manufacturer for the pickup factor. Then calibrate if necessary using the following procedure. Go to "AP", select "PPF" (pickup factor calibration). The MR will drive the box open and modulate the damper to maintain the "CHF" level. This may take 5 - 10 minutes. NOTE: The stroke time is defined using the Damper Stroke (ds) parameter. The ASC provides several means of synchronizing the point with the physical damper position. 1. When this point is controlled to a value of 0, the decrease pulse will be on for 125% of the damper stroke. 2. When this point is controlled to a value of 100, the increase pulse will be on for 125% of the damper stroke. 3. When the damper stroke duration is modified, the decrease pulse will be on for 125% of the damper stroke. 4. When the power is cycled on the ASC, the decrease pulse will be on for 125% of the damper stroke. 5. Any time the ASC is the target of an Update_ASC or a Copy_Parms, the decrease pulse will be on for 125% of the damper stroke. After the reading has settled out, take a reading with a Hood or Manometer, which has been setup, and measure the actual CFM and enter that value now into the I/STAT-M/STAT using the Select and change buttons. The software has entered a unique Pick-up Factor "PF" in the MR for this box.   Calibrate space temperature (if necessary): To calibrate the Space Sensor while in the Service Mode, go to "oP" Operational Parameters. Select "CSS" (calibrate space sensor). Measure the actual temperature with a digital thermometer and enter the value. If your box has no heat or has a fan with electric heat. You’re finished. Go to the next box.   Hot water coil: If you have a hot water valve on your box and the stroke time is not 600 seconds: Go to "UP" (Unit Parameters) and select "Ho", Heating Output. Select1 for 1-OutPWM, 2 for 2 Out-PWM(Floating), or 3 for Duty Cycle 1 output. Go to "UP" Unit Parameters and select "HS" (heating stroke) and enter the actual stroke time in seconds.   Air Balance: If you require closely calibrated CFM readings proceed with the following steps: Go to "AP" (Airflow Parameters) Select "CPL" (calibrate low flow) and the damper will begin to close. Remember, the damper motor may take 3 minutes to get to the Cooling Low Flow setpoint. With a Hood, measure the total air flow and enter the measured CFM value. Select "CPH" (calibrate high flow). The damper will drive open to the Cooling High Flow setpoint. (remember the damper motor has a 185 sec stroke). When the reading stabilizes, take your measured CFM reading and enter it now. This procedure will de-calibrate the CFM input from the 0-1"readings to compensate for box, pickup, or hood irregularities/errors. Caution: When the decision is made to connect the MR-VAV-AX to a MRI or MCI please note the following: Avoid updating the MCI or ASC after initial setup as this will delete any MCI resident calculations, ATS, etc. that you may have added off-line that are residing at the same point addresses that the MR-VAV-AX is using. There are a variety of box types and a variety of other things that can be change if your application requires it. (Refer to TCON147)

Issue Set a failsafe for points in a DCU with the HHC Environment I/NET site Cause How to set a failsafe for points in a DCU with the HHC : Resolution Through the HHC is the only way to do this. Refer to TCON 073 for details on this procedure for each point type.

Issue Is it possible to integrate Schlage products with Security Expert? Product Line Security Expert Environment Security Expert Server (vv4.2.259.19 and above) SP-C controller Firmware (v2.08.923 and above) Cause Unable to migrate or convert a legacy access control system which has Schlage devices integrated to Security Expert Resolution With Security Expert Software (v4.2.259.19 and above) and SP-C firmware (v2.08.923 and above), the integration of Schlage devices (AD300 and AD400) with Security Expert software is supported.  It is always recommended to use the latest Security Expert Version and SP-C firmware version to avoid any known issues. For more information regarding the, Schlage Integration with Security Expert, download the attachment.  Refer to Security Expert Allegion Smart Reader Integration 

Issue Does the STR-250 work on Micro Regulators (MR)? Environment I/NET Seven STR-250, I/STAT, M/STAT I/SITE Controller and Micro Regulators (MR) Cause The STR-250 Wall Module is the replacement for the commonly referred to I/STAT sensor, still referenced in I/NET documentation.  The I/STAT is no longer available.  Resolution The STR-250 sensor is the replacement for the I/NET I/STAT, so installation and configuration for the STR-250 is as per this I/STAT. There are two documents that will provide assistance with this TCON126 and TCON299 (Chapter 21). The STR-250 full functionality must be installed on the I/STAT port of any I/NET device and configured as detailed in the above documents. Only one I/STAT port exists per MR. The M/STAT is still available and is used as the hardware tool for configuring the controller settings on all supported I/STAT devices, such as, all Micro Regulators (MR) variants, I/Site LAN Controller (Model 7728) and Xenta 102-AX. 

Issue Where should door connection be made on a SCU1284 Termination, Terminal number, PIN, SCU1284 Environment I/Net SCU1284 Cause What output to use for door contact Resolution This information is taken from TCON 312.  

Issue Clarification on dip switch six and station addressing for the SCU1200, SCU1280, or SCU1284 Product Line TAC INET Environment I/NET Seven with Access Control using an SCU SCU1200, SCU1280, or SCU1284 Cause Clarification on SCU and dip switch settings being open, enabled for dual or single station addressing (2 or 4 doors) Resolution If the Device Type is SCU1200, SCU1280, or SCU1284: set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON). In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode. Though the TCON312 shows the dip switches for 1-6, there is still a bit of clarity which can be provided on how that looks on an actual SCU. The example from the TCON is shown here: And this is a photo below of an SCU which is setup as 0101 with dual addressing since Dip Switch 6 is in Dual Address mode shown in the picture below. When penetrating down to it using Edit, Host Computer, Network Configuration, SCU 1284 is shown with 2 Points with door addresses: 010108 Door1 010109 Door2 010208 Door3 010209 Door4 After checking MCU Configuration, I added the points in the Network configuration. The main point here is that Dip Switch 6 is up on the Open side of the Switch bar shown in red which is the dual point and 4 door configuration.   Note: Concerning the numbering scheme for addressing the SCU, it is important to number your SCUs with an address then skip the next number so in the event you dual addressing for four doors, the second address is available. Don't use addresses 28, 29,30, and 31 as those are reserved for the Remote Arming Terminal.  Overlooking this can result in future headaches of moving SCUs around in the addressing scheme which is never recommended. Example for a site containing 4 SCU door controllers: SCUa address 2, SCUb Address 4, SCUc Address 6, SCUd Address 8.  Another example configuration: One reader inputs to READER1 and READER2? Here is that wiring example. In order to use more than the first eight inputs on the SCU, you must configure the SCU as a double-address controller. When you enable the double-address mode (DIP switch S1-6 = ON), inputs 1 through 8 are monitored on the selected subLAN address (i.e., the primary address) and inputs 9 through 12 are monitored on the next consecutive subLAN address (i.e., the secondary address). The input points are defined in the I/NET host using two separate SCU controller assignments, the first providing eight input point definitions and the second providing 4 input point definitions. The SCU’s outputs are also divided across two LAN addresses when the SCU is operating in the double-address mode. The first four outputs are assigned to bit offsets 00 through 03 on the SCU’s primary address. The last four outputs are assigned to bit offsets 00 through 03 on the SCU’s secondary address.

Issue Are there resources for configuring a 7750 Building Manager? Product Line TAC INET Environment I/NET site Cause The Building Manager (BM) is based on a zoned programming approach. Zones are groups of points in a system which control related equipment. A good example of a zone would be a group of points that control the lighting, heating and air conditioning for a tenant that occupies 1 floor in a multi-story building. The major function of the building manager is to give the tenant control over this equipment (through a user friendly telephone interface) and to be able to accumulate statistics to be used for billing normal and after-hours energy usage. Resolution Good sources: TCON098 TCON209 (7-28 through 7-38) TCON237 (7-28 through 7-39) Tech Tip 038

Issue TAC Xenta Server webpage does not work smoothly. A typical example is when you try to change a value. The small dialog that should pop up to change a value might pop up and immediately disappear. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment TAC Xenta Severs Xenta 511, 527, 701, 711, 721, 731, 913 TAC Vista 5 Webstation Cause Using unsupported version of Java may cause various issues. For example, Xenta server webpage does not display smoothly, time schedule does not show up or can not be edited, etc. Resolution Below is the Java compatibility matrix of TAC Vista 5.   5.1.9 5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Java 1.5 update 06               X X X X X X X Java 1.6 update 11           X X               Java 1.6 update 17            X 1                 Java 1.6 update 20 X X X X X                   Java 1.7 update 51 X                           1  TAC Xenta Server 5XX/7XX/913 SP1. Log into The Exchange and then click here to download the full Vista Compatibility Matrix. To uninstall an unsupported version of Java and install the supported version, refer to Xenta Server webpage automatically logs out while waiting for Java to load.

Issue Receiving the following error when attempting to navigate to the Xenta web interface. "TAC C503Boot/x.x.x.x not configured". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 511, 527, 555 Xenta Server 701, 721, 731 Cause Device web interface has stopped working or flash drive / hard disk has been corrupted on the Xenta Server. Resolution Attempt the following steps to resolve this problem: Try restarting the device and see if the unit comes back online, remember to wait 1-2 minutes for the unit to restart.  Check the RUN LED on the panel, if the LED is a solid green this indicates the device is running normally, and your access should be restored. If the LED is RED, solid or flashing this would indicate a problem with the device. Attempt to restore or upgrade the device to the latest firmware.    You can download the latest firmware version from the Schneider Electric Exchange. If this fails then then reference Xenta Server "Run" light is solid red with no communication via Ethernet.

Issue Receive Error: "Unexpected file format" when attempting to open Graphic Page Environment I/NET Seven 2.41 graphic pages Cause When creating, modifying and saving graphics in revision 2.41 and then attempting to open these graphic pages in previous versions of I/NET this error "unexpected file format" is presented. Resolution This issue has been rectified in 2.41A and above. I/NET Software are available for licensed Partners to download on The Exchange Download Center.

Issue Using the same power supply (transformer) for a Xenta 527 and a 7798 I/Site LAN comes down and there is no communication to any other devices. Environment Xenta 527 7798 I/Site 7798C 7798B Cause This is because it has blown the RS-232 expansion board on the 7798 I/Site due to a voltage overload The Xenta 527 must be powered with either half wave AC Power or DC power.  (Half wave power connects earth ground 1 leg of the AC power to the controller.) The 7798B and the 7798C can use either full way power or DC power. It is recommended to use a separate power supply for each device Resolution If required you can power the 7798C and the Xenta 527 on the same DC power supply, provided all devices are properly grounded.  This is not recommended as each devices specifies a separate power supply. To correctly wire these devices follow these instructions. You will need to send your damaged 7798 in for repair Add a second transformer or power supply to power the 7798 controller Ensure that the Xenta 527 is properly grounded. Please reference TCON190 (page 15)  for the 7798B or TCON311 (page 9)  for the 7798C wiring diagrams.  Reference this cut sheet for the Xenta 527 which shows that G0 must be grounded.

Issue Can Pelco's Control Point Software run on the same PC as I/NET Seven Software? Product Line Pelco, TAC INET Environment All Windows OS I/NET Seven Software Pelco Control Point Software Cause The two software packages are not compatible with each other. Resolution Pelco's client software cannot be installed on the same PC that is running TAC I/NET Seven. See TCON 301 - Chapter 6.

Issue What is the part number for the velocity sensor (0-1.3") transducer that is connected to the VAV-UC? Environment I/NET Site Cause What is the part number for the velocity sensor (0-1.3") transducer that is connected to the VAV-UC? Resolution CFM velocity pressure transducer input 0-1.3" W.C part number is 603500-0002. Refer to TCON 069 for more details

Issue Site has installed and "Tuned" a few PIDs and Float (FLT) modules in the controller but is not able to tune the last module added. What may be wrong? (History – Tuning) Environment I/NET Site Cause Due to the memory required for the tuning function, there is a limit of four modules that can be contained in the history record of each controller. Resolution If an additional module is needed, an old one must be deleted first. For more information refer to the System Operator Guide or TCON 083.

Issue A 7700 and a 7740 are running DDC modules in I/NET 2000. Both DCUs have EPROMs (Non-MIPed). A "P-only" PID does not work. Environment I/NET 2000 Non-mipped EPROM Proportional-only PID control Cause P-Only mode is not available in the EPROM versions of the 7700 and 7740 DCUs. Resolution Use MIPs in these controllers to get this feature. Refer to TCON 206 or TCON 237, Direct Digital Control for more information.

Issue Overall Tap Configuration Environment I/NET Seven Site Cause Need information on Tap Configuration Resolution When you update parameters in a Tap, the changes will take effect when you disconnect from the Tap. If the changes are made to a shared dial Tap, the changes will take effect when the last connected host disconnects from the Tap. Use the following steps to configure a Tap. Refer to TCON300, I/NET Seven Technical Reference Guide, for a description of Tap configuration parameters. Select Edit Tap Host (or Link, or LAN) from the main menu. The system displays the Host Tap Configuration editor. The Link Tap and LAN Tap configuration editors are similar. This procedure describes the differences. Assign a Tap Name to the Host, Link, or LAN tap (up to 16 characters). On site Taps, use the spindial to choose a LAN Address (0 to 63) to identify the tap address on the controller LAN. The LAN Address field applies only to site taps. Depending on the type of tap, do one of the following: On host and LAN taps use the spindial to choose a LAN Speed. On link taps use the spindial to choose a Speed. On dial taps choose a Tap speaker setting from the drop-down list (Off, Auto, or On). Use the Firmware Status parameters for information purposes only. These parameters show the current revision number and revision date. These fields are display only, you cannot edit them. Use the Distribution Parameters fields to specify distribution group number, message priority, and the message mask. Note: When utilizing dual Tap functions (site Tap and LAN Tap) in a 7716, 7718, 7728, or 7793 (configured as -03 or -06), the values entered under "Distribution Parameters" in one Tap editor are used by all Tap editors emulated within the same DCU. Only one set of "Control Parameters" have been provided in each DCU. Select the Distribution Group number (1–4) to match the distribution group of the host PCs to which you want the Tap to send messages. Set the Message Mask to match the mask(s) of the host PCs to which you want the Tap to send messages. Set the Message Priority to None, Routine, Priority, or Critical. The Percent Full field is for AD/AA LAN Taps only. It specifies the number of messages that will be stored in the LAN/Site Tap’s RAM, as a percent of the total available memory, before the Tap calls the host PC. This is a deferred dialing parameter for "Priority" alarms. The Time Interval field is for AD/AA LAN Taps only. It specifies the time interval that must transpire following a "priority" alarm before the LAN/Site Tap calls the host PC. This is a deferred dialing parameter for "Priority" alarms.

Issue Online Messages on an SLI Environment I/NET site Cause Messages coming from the Sub Lan Interface (SLI) Resolution A door controller (DPU) has a limited amount of memory space available for storing individual records and messages. "Resident in DPU" individual records are given priority in storage: they are never discarded. Transient (non-resident) individual records and messages are stored on a space-available basis. If a communication outage between the SLI and the door controller causes the door controller's memory capacity to be reached, older records must be discarded as new messages continue to be generated. All records are discarded on a first-in, first-out (FIFO) basis, so that the remaining records are the most recent ones. A "DPU queue ovflw" message will also be generated to warn that data was lost. Records are discarded in the following order: Transient individuals. Messages. If there are no more transient individuals to discard, routine messages will be lost. When communications between the SLI and the door controller are restored, the contents of the door controller's queue (including the "DPU queue ovflw" message) will be delivered, freeing memory in the door controller. The SLI continually requests messages from its door controllers. Retrieved messages are queued within the SLI until they can be sent to appropriate host workstation(s). When the SLI queue is full, it will continue to accept messages from door controllers (i.e., the SLI will not cause its door controllers to discard messages). With its memory queue full, the SLI will discard older messages as newer messages are received. This ensures that the remaining records are the most recent ones. A "DCU queue ovflw" message will be generated to warn that data was lost. When communications between the SLI and the host PC are restored, the contents of the SLI's queue (including the "DCU queue ovflw" message) will be delivered, freeing memory in the SLI. There is also a TPA-DALL-09-0001.00 that was written on this issue.