Modernization Guide for N2 Controllers - Facility Explorer Code No. LIT Issued December 5, 2014

Transcription

1 Code No. LIT Issued December 5, 01 Refer to the QuickLIT website for the most up-to-date version of this document. Introduction...3 Choosing the Right Strategy...3 Scenario 1: Legacy N Controller Fails...3 Scenario : Small Expansion...3 Scenario 3: System Modernization... Applying FX-PC Controllers as Replacements for Legacy N Controllers...5 General Differences and Considerations...6 Mounting...6 Input and Output (I/O) Interfaces...6 Zone Bus Not Supported...6 XT Bus Not Supported...7 I/O Wiring...7 N Field Bus Network Wiring...7 Setting the N Controller Address to be Greater than Programming Tools and Control Logic...8 Downloading and Commissioning...10 Integration into N Supervisor...10 Specific Device Differences and Considerations...1 Replacing VMA1xx Series Variable Air Volume Modular Controllers...13 Footprint Considerations...13 Point Comparison...13 I/O Expansion Comparison...1 Room Sensor Comparisons...1 Control Logic Configuration...15 N Device and Point Configuration...15 N Supervisor Configuration...16 Replacing DX-9100 Extended Digital Controllers...17 Footprint Considerations...17 Wiring Connections Comparison...18 Point Comparison...0 Additional Considerations...3 Display Comparison...3 Control Logic Configuration...3 N Device and Point Configuration...3 N Supervisor Configuration... Replacing UNT Unitary Controllers...5 Footprint Considerations...5 Wiring Connections Comparison...7 Point Comparison...8 RLY Relay Module Considerations...9 Zone Bus Considerations...30 Room Sensor Comparisons...31 Control Logic Configuration...31 N Device and Point Configuration...3 N Supervisor Configuration...33 Replacing VAV1xx Variable Air Volume Box Controllers

2 Footprint Comparison...35 Wiring Connections Comparison...37 Point Comparison...0 Zone Bus Considerations...0 Room Sensor Comparisons...1 Control Logic Configuration... Zone Terminal Unit Considerations... N Device and Point Configuration... N Supervisor Configuration...3 Replacing AHU Air Handling Unit Controllers... Footprint Comparison... Wiring Connections Comparison...6 Point Comparison...7 RLY Relay Module Considerations...9 Function Module (FMK) Considerations...50 Zone Bus Considerations...50 Zone Terminal Unit Considerations...50 Control Logic Configuration...50 N Device and Point Configuration...50 N Supervisor Configuration...51 Demolition and Disposal...5 Converting to BACnet MS/TP Field Bus...5 Device Addressing...5 Control Configuration for BACnet MS/TP...5 Reusing Existing N Wiring for BACnet MS/TP...53

3 Introduction At FX-PCT Release 10.1, a new enhancement was added enabling the FX-PC controller field bus to be configured for either BACnet MS/TP or N networking protocol. This feature allows you to use certain FX-PC controllers as field replacements for legacy Metasys, Facilitator, or Facility Explorer branded N controllers (hereafter referred to as legacy N controllers). Many of these legacy N controllers are no longer in production, making direct replacement no longer feasible. Customers with legacy N controllers installed in their building can benefit from N-capable FX-PC controllers, because they enable cost-effective replacement and expansion of their installed base of controllers by avoiding major control system renovation. These same customers also benefit from the more modern FX-PC controller technology, including state-based control, event-driven logic, and automatic tuning. In addition, the ability to switch the FX-PC controllers back to BACnet MS/TP provides customers with a cost-effective upgrade path to a modern, higher performance field bus technology. The modernization guide is intended to help you choose and implement the most appropriate strategy for your customer. Also, this guide describes the key installation and configuration differences between the two families of controllers to help you prevent, minimize, and overcome installation and configuration challenges. Choosing the Right Strategy Replacement of legacy N controllers is driven by one of three scenarios. We recommend that you work with your customer to develop a modernization plan (even if that plan is implemented in the future). With a modernization plan in place, you can better manage emergency replacement or small expansion scenarios. Scenario 1: Legacy N Controller Fails In this scenario, a legacy N controller fails, either electronically or mechanically. The customer needs to replace just one controller. Consider the following options: Option 1: Replace the legacy N controller with an FX-PC controller configured for N. See Applying FX-PC Controllers as Replacements for Legacy N Controllers for the key challenges to this option. Option : You may find Option 1 too challenging or not cost effective for just one controller. If so, consider finding a direct replacement. Many legacy N controllers are no longer in production. However, you may find direct replacements through sources other than new production. For example, you may find a direct replacement in the truck inventory of a service technician or through a Johnson Controls distributor who has an inventory of legacy N controllers. Also, the Johnson Controls Repair Center has an inventory of refurbished legacy N controllers, as they offer repair and return capability for these devices. Option 3: If the failed controller is used in a critical application and the situation is extremely time-sensitive, then you should consider moving a similar controller (if available) from a less critical application and temporarily using it as a replacement. Then implement either Option 1 or when time permits. Scenario : Small Expansion In this scenario, your customer is planning to remodel their space, subdivide or rearrange existing space, or expand their facility. As a result, their plan requires adding to their Building Automation System (BAS) either new equipment or existing equipment that was not previously connected to the BAS. Option 1: If only one or two new controllers are needed as additions to an existing N bus, you should consider adding FX-PC controllers and configuring them for N protocol. Option : If many new controllers are needed, you should consider modernizing their BAS to use BACnet MS/TP. This option involves replacing the N supervisor with a BACnet supervisor, adding FX-PC controllers to operate the new or existing equipment, and configuring the FX-PC controllers for BACnet protocol. Note: If the existing N supervisor also supports managing BACnet MS/TP networks, then the supervisor may not need to be replaced. 3

4 Scenario 3: System Modernization In this scenario, the customer has an N-based BAS and has previously replaced legacy N controllers with N-configured FX-PC controllers as a part of an earlier replacement scenario. Now the customer is contemplating future risk and the cost and disruption of more legacy N controller replacements. Option 1: You should consider modernizing the BAS to use BACnet MS/TP protocol. This option requires replacing the N supervisor with a BACnet supervisor, switching the existing N-configured FX-PC controllers to BACnet, and replacing the remaining legacy N controllers with BACnet-configured FX-PC controllers. Note: If the existing N supervisor also supports managing BACnet MS/TP networks, then the supervisor may not need to be replaced. See Converting to BACnet MS/TP Field Bus for the key challenges to this option.

5 Applying FX-PC Controllers as Replacements for Legacy N Controllers To apply FX-PC controllers as replacements for legacy N controllers, you need to consider the following: Installation Location Identify how and where the legacy N controller is physically mounted and wired. Determine if the existing controller enclosure is suitable for the replacement FX-PC controller by identifying the amount of space available. If the replacement requires the addition of an FX-PCX to match point count, additional enclosure space is required. Be sure that rework of a controller installation conforms to all local codes. For example, certain models of legacy controllers used spade lugs connectors; the replacement controllers use screw terminals. Starting in 005, the National Electrical Code (NEC) Article 09 mandates specific detail marking in control enclosures. This requirement applies to any enclosures replaced or expanded to hold the FX-PC products and accessories. I/O Profile Identify the number and types of all input and output devices connected to the legacy N controller, including the signal types required to interface them. Sequence of Operation Obtain the expected sequence of operation from the legacy N controllers. Use one of the following methods: Use the legacy N controller s programming tool (HVACPro or GX Tool) to upload the legacy N controller s application file. If you are unable to upload the exact file from the target controller (for example, if the controller does not power up), then obtain a saved backup file from the project archives. If you are unable to obtain the exact file, then consider uploading a nearby controller with the same or similar application. If you are unable to upload or obtain an exact or similar application file, then analyze the mechanical equipment characteristics and control sequence from visual inspection or job documentation and then confirm the expected sequence of operation with the customer. N Supervisor Integration Identify which type of N supervisor (for example, NCM, N30, Companion, Facilitator, NAE, or FX Supervisory Controller) is providing supervisory control over the legacy N controller. Identify all control features and services (for example, scheduling, optimal start/stop, alarming, trending, interlocking, global data sharing, supervisory code [LCT, GPL, JC Basic], or graphics) the N supervisor is applying to the legacy N controller. 5

6 General Differences and Considerations This section details the general differences that exist between the legacy N controllers and FX-PC controllers. For unique differences based on the specific model of legacy N controller being replaced, see Specific Device Differences and Considerations. Mounting FX-PC controllers are not physically identical to legacy N controllers and have a different mounting footprint. As a result, when using FX-PC controllers to replace legacy N controllers, ensure that the intended mounting location (for example, if reusing the existing control panel) has enough space to accommodate the FX-PC controller. See Specific Device Differences and Considerations for specific dimensions for legacy N controllers and their suggested FX-PC controller replacements. Note: Depending on the I/O count used on the legacy N controller, two or more physical controllers (an FX-PCG/FX-PCX combination) may be needed to replace a single N controller. Input and Output (I/O) Interfaces FX-PC controllers have different numbers and types of onboard I/O than legacy N controllers. Which replacement FX-PC you select depends on how the legacy N controller was applied in the field and how many I/Os were actually used by the legacy N controller. For more information, see Specific Device Differences and Considerations to understand the onboard I/O differences between legacy N controllers and FX-PC controllers. FX-PC controllers feature flexible input interfaces, allowing these controllers to support most of the same sensors supported. However, some room sensors (for example, TE /1, TE-67xx, or TE-67xx) that are used with legacy N controllers feature modular (phone) jack connections. These sensors require adaptation for use with the FX-PC controllers. See Specific Device Differences and Considerations. Zone Bus Not Supported Legacy UNT, VAV, AHU, and VMA100 controllers supported a Zone Bus for connecting to: TMZ Series network room sensors TE-77 Series wireless temperature sensor and receivers ZTU Zone Terminal Units M100C Series networked actuators FX-PC controllers do not support the Zone Bus and do not support these devices. Instead, FX-PC controllers feature a different technology bus called the Sensor Actuator (SA) bus to connect NS Series Network Sensors, FX-DIS1710 Local Display/Keypads, and FX-PCX Expansion I/O Modules. When using an FX-PC controller to replace a legacy N controller that uses a TMZ sensor, you must also replace the TMZ sensor with an NS Series Network Sensor. Make note of any wiring change or modifications needed when using a new sensor. The NS sensor provides many of the same functions as the TMZ sensor, including zone temperature sensing, zone temperature setpoint adjustment, and LCD display. However, the NS sensor is housed in an enclosure that has a different user interface. For example, the NS sensor features a dial to adjust the zone temperature setpoint, whereas the TMZ features a pushbutton keypad. As a result, we recommend you work with your customer to help them and their building s occupants understand how to use the adjustment features of the new NS sensor. When using an FX-PC controller to replace a legacy N controller which uses a TE-77xx wireless transmitter/receiver, you must also replace the TE-77xx with the Facility Explorer One-to-One Wireless Room Sensing System. For more information, refer to the Facility Explorer One-to-One Wireless Room Sensing System Product Bulletin (LIT ). When using an FX-PC controller to replace a legacy N controller that uses a ZTU Zone Terminal Unit, you must replace it with an FX-DIS1710 Local Display/Keypad. 6

7 When using an FX-PC controller to replace a legacy N controller that uses an M100C zone bus actuator, you must replace the actuator with a non-networked actuator. For dampers, use the M9100/M900 Series. For valves, use the VA7800/VA-7150 Series. To control the new actuator, use an available analog output or configurable output on the FX-PC controller. If none are available, add an FX-PCX Expansion I/O Module. XT Bus Not Supported Legacy DX-9100 Extended Digital Controllers supported an optional XT Extension Module with associated XP Expansion I/O Modules to expand the DX-9100's input and output interfaces. FX-PC controllers do not support the XT/XP modules. Instead, for I/O expansion, the FX-PC controllers support the SA bus for connecting FX-PCs to IOM Expansion I/O modules. When using an FX-PC controller to replace a DX-9100 controller, you must also replace the XT/XP modules. Either use available I/O interfaces on the FX-PC main controller or add FX-PCX Expansion I/O modules. I/O Wiring Several differences exist between the I/O wiring connections of the FX-PC controllers and the legacy N controllers. Most FX-PC controllers have terminals that use screw type I/O wiring connections, except for FX-PCV models, which have spade terminals. Most legacy N controllers use spade lug type I/O wiring connections. You may need to modify the ends of the existing I/O wiring accordingly. Also, FX-PC controller wiring terminal locations may not line up with the existing wiring. To align wires to the corresponding FX-PC controller, you many need to: reroute wire from the enclosure terminal block to the FX-PC controller add longer wires to many of the controller terminals splice additional length onto existing wire if your installation does not have a terminal block When modifying the I/O wiring to accommodate the replacement FX-PC controller, follow these recommendations, whenever possible: use the same color insulation to preserve wiring standards use wire of the same material and gauge never splice copper to aluminum conductors without using an appropriate aluminum to copper conductor use positive mechanical connections in all splices follow splice manufacturer's instructions and crimp tool recommendations carefully consider using soldered connections if the enclosure location allows completely insulate each individual splice to protect from electrical shorts and corrosion use shrink-sleeve tubing, which provides a more reliable insulation than adhesive tape in most applications N Field Bus Network Wiring When configured for N, FX-PC controllers conform to N field bus networking standards. When using an N-configured FX-PC controller to replace a legacy N controller on an N field bus, you can expect the same network performance. However, if the installation s existing N network is already heavily loaded or is frequently reporting off-line devices, then you should take steps to improve the network performance before replacing legacy N controllers with FX-PC controllers. Refer to the N Communication Technical Bulletin (LIT ) and follow all N field bus networking rules, including those for: segment and total line length end-of-line terminations number of devices per segment, between repeaters 7

8 Setting the N Controller Address to be Greater than 17 N-configured FX-PC controllers support the full range of possible N device addresses supported by the N protocol standard (1-55); however, they require special configuration for addresses above 17. Note: This special configuration is required because FX-PC controller addresses above 17 were originally intended for use with the Wireless Field Bus system. To set the FX-PC controller's N address to be greater than 17, follow these steps: 1. Disconnect the VAC supply from the FX-PC controller.. Remove the FC Bus connector from the FX-PC controller. 3. Set the FX-PC controller's address DIP switch to the desired N address.. Set the address switch segment labeled 18 to OFF. Figure 1: Switch Setting for Address 19 with 18 Segment OFF 5. Reconnect the VAC supply to the controller. 6. Using an FX-PCT tool connection at the FX-PC controller s SA bus, download the firmware and N-configured controller application file. The download process prompts you to confirm switching the communication protocol to N. 7. Click OK to accept. 8. After the download has completed, disconnect the VAC supply to the FX-PC controller. 9. Set the address switch segment labeled 18 to ON. 10. Reattach the FC Bus connector to the FX-PC controller. 11. Reconnect the VAC supply to the FX-PC controller. Programming Tools and Control Logic FX-PCT is the programming and commissioning tool for the FX-PC controller family, and its control logic capabilities are similar but not identical to those of the legacy N controller programming tools (for example, HVACPro and GX Tool). No utilities are available to convert the legacy N controller's logic to be usable by FX-PCT, and as a result, you need to recreate the control logic for the replacement FX-PC controller using FX-PCT. Recreating a UNT, VAV, VMA, or AHU controller application that was programmed with HVACPro should be straightforward. The FX-PCT System Selection Wizard and Sideloop Wizard provide control logic creation capabilities that are nearly identical to HVACPro's Question and Answer (Q&A) wizard and Sideloop wizard. Figure shows how to begin configuring a new system in the tool. Figure 3 shows the N Compatibility Options in the System Selection Tree. 8

9 Figure : New System Figure 3: N Compatibility Options 9

10 Recreating a DX-9100 control application that was programmed with the GX Tool is more challenging. The GX Tool was a custom programming tool which allowed the programmer to create custom control logic by connecting together various predefined logic modules to its I/O. FX-PCT provides a similar custom programming interface using predefined logic modules, but its logic modules are significantly different from the GX Tool's. Also, the FX-PCT programming canvas is significantly different from the GX-Tool's. At FX-PCT Release 10.1, a new Global Sequencer logic module was added that provides similar functionality as the GX Tool's Sequencer and Binary Sequencer modules. The control application programmed by FX-PCT is significantly more advanced, containing modern control advancements such as state-based control, event-driven logic, and automatic tuning. Note: The N Compatibility Options option button does not appear for Central Heating, Central Cooling Plants, and Simple Central Plants because these systems typically use custom logic. For more information on programming and downloading controllers using FX-PCT 10.1, refer to the Controller Tool Help (LIT ). Downloading and Commissioning Legacy N controllers support local application downloading and commissioning using the appropriate programming and commissioning tool hosted on a computer (for example, HVACPro or GX Tool), the computer's serial interface, and an RS-3 to RS-85 adapter (for example, the MM-CVT or IU-9100 or Zone Bus adapter). FX-PC controllers also support local downloading and commissioning; however, they require a different technology. For local downloading and commissioning, FX-PC controllers require that FX-PCT is hosted on a computer with a Bluetooth interface or a third-party Bluetooth interface, and that an FX-BTCVT Bluetooth Commissioning Converter is connected to the FX-PC controller's SA Bus. NCM and NAE Series supervisory devices contain a feature called Passthrough, which enables you to remotely download and commission legacy N controllers. NCM and NAE Passthrough do not support N-configured FX-PC controllers. When you use an FX-PC controller to replace a legacy N controller that is supervised by an NCM or NAE, you lose the capability to use Passthrough to remotely download and commission the N-configured controller. You and your customers need to be aware that programming and commissioning the N-configured FX-PC controller must be performed onsite with access to the FX-PC controller's SA bus connection. Integration into N Supervisor When using FX-PC controllers to replace legacy N controllers, the N supervisor's configuration may be impacted. The legacy N controller families have existed through several generations of N supervisors. Depending on the timing of the original installation, legacy N controllers may be supervised by one of many types and brands of N supervisors, including the NCM, NAE, N30, Companion, Facilitator, and FX Supervisory Controllers. N-configured FX-PC controllers should work with all Johnson Controls N supervisors. However, you must consider certain configuration steps to ensure the system operates as expected after the replacement. In many instances, you can reconfigure the N supervisor online. However, some changes may require off-line configuration and a supervisory controller download. Therefore, you may need to have the appropriate tool such as System Configuration Tool (SCT) for NAEs, Project Builder for N30s, and FX Workbench for FX Supervisory Controllers. A legacy N controller is mapped into an N supervisor by defining in its database the controller's N device type, N point types, and N point addresses. At FX-PCT Release 10.1, an N Mapping feature was added, allowing you to configure this information to resemble that of the legacy N controller being replaced. N Device Type: With the FX-PCT N Mapping feature, you can define the FX-PC controller's N device type to be a UNT, AHU, VAV, or VND to match the legacy N controller being replaced. For example, consider a situation where you are replacing a UNT controller, and it is mapped into the N supervisor as a UNT N device type. With the N Mapping feature, you can configure the FX-PC controller to have a UNT N device type to match the N supervisor's definition. 10

11 Note: DX and FX-PCV controllers cannot be directly mapped as before and must now be defined as VND devices. N Point Information: With the FX-PCT N Mapping feature, you can define the FX-PC controller's application points so that the N Short Name, Point Type, and Point Address match those of the legacy N controller being replaced. For example, consider a situation where you are replacing a legacy UNT1x1 controller, and its Zone Temperature application point is mapped into the N supervisor with a short name of ZN-T, and point type and address of AI-1. With the N Mapping feature, you can configure the FX-PC controller's Zone Temperature application point to have the same ZN-T, AI-1 information to match the N supervisor's definition. Note: This functionality helps minimize the reconfiguration (device and point mapping) needed at the N supervisor, but may not be appropriate for all replacement situations. See Specific Device Differences and Considerations for more information. Even with the N Mapping feature, the N supervisor's database may still require some changes. The FX-PC controller's application may not include all of the same application points as the legacy N controller being replaced. For example, some legacy N controller application points have no equivalent in FX-PC controllers. Therefore, the N supervisor reports these points as offline unless they are unmapped (deleted) from the N supervisor's database. Also, some legacy N controller application points may be defined differently in FX-PC controllers, which would require remapping the FX-PC controller's N points in the N supervisor. This remapping may in turn require other configuration changes to the N supervisor, including changes to trend and alarm extensions, bound connections to graphics, and source and destination connections to system-wide control logic. Although the N-configured FX-PC controller is functionally similar to the legacy N controller it replaces, any changes to point mapping and associated changes to supervisory functionality may cause some confusion for your customers and operators. For example: The operator interface for adjusting the standby and unoccupied zone setpoints for VMA1xx controllers uses offset values, which are added to or subtracted from the zone setpoint; whereas the interface for adjusting the standby and unoccupied zone setpoints for FX-PC controllers is their actual, discrete values. N Open Override command to an FX-PC controller object value does not persist after power cycle. Commands to a Default Value attribute do not persist after a power cycle. Writing to a point in the FX-PC controller through the N network integration changes the present value of the attribute but does not write the value to non-volatile memory. This means that the new value is not persisted following a power cycle of the FX-PC controller. The workaround is to use the Setpoint command to update the value in non-volatile memory. Be sure to introduce the changes to your customer and the system operators accordingly. 11

12 Specific Device Differences and Considerations Table 1 shows the legacy N controllers that can be functionally replaced with FX-PC controllers, along with a suggested FX-PC controller replacement. Table 1: Suggested Replacement for Legacy N Controllers Legacy N Controller Model Suggested FX-PC Controller Replacement VMA1xx DX-9100 UNT1xx UNT11xx VAV1xx plus EDA/ATP AHU FX-PCV183 FX-PCA3611 plus PCX (to meet I/O) FX-PCG16xx FX-PCG6xx FX-PCV183 for VAV box applications FX-PCG16xx for Expansion I/O applications FX-PCA3611 plus FX-PCX (to meet I/O) 1

13 Replacing VMA1xx Series Variable Air Volume Modular Controllers The VMA1xx Series Variable Air Volume Modular controller was used extensively for VAV box control. The VMA1xx featured the integration of a differential pressure sensor and rotating actuator into the controller package to reduce its overall mounting footprint and simplify installation. The recommended FX-PC Series replacement controller model for the VMA1xx is the FX-PCV183. See the following sections for key differences. Footprint Considerations The FX-PCV183 has a slightly larger footprint than the VMA1xx. Replacement in the same enclosure space is possible. However, it may be tight for some installations. The location of the retaining screw for the FX-PCV183 controller is further away from the actuator shaft than on the VMA1xx. Figure : Footprint Considerations Table : VMA1xx and FX-PC Replacement Dimensions Dimension VMA1xx FX-PCV183 Height Width Depth 153 mm (6 in.) 10 mm ( in.) 10 mm ( in.) 165 mm (6.5 in) 15 mm (.9 in.) 73 mm (.9 in.) Point Comparison Table 3: VMA1xx to FX-PC Controller Point Comparison VMA110 VMA10 FX-PCV183 FX-PCX711 Termination Type Space lugs Spade lugs Spade lugs Screw terminals Analog Inputs 0 0 Binary Inputs Universal Inputs Analog Outputs 0 0 Binary Outputs Configurable Outputs

14 Table 3: VMA1xx to FX-PC Controller Point Comparison VMA110 VMA10 FX-PCV183 FX-PCX711 Universal Outputs Relay Outputs Table : VMA1xx to FX-PC Controller Point Comparison VMA1xx Point Characteristic FX-PC Controller Point Type Type Characteristic AI RTD Temp. Elem. (1k Ni, Si, Pt, or k NTC) UI Resistance temperature detector (RTD) (1k Ni, 1k Pt, A99B Si) 0-10 VDC Transducer 1.6k ohm Setpoint Potentiometers Negative temperature coefficient (NTC) (10k Type L,.5k Type ) Voltage Mode, 0 10 VDC Current Mode, 0 ma Resistive Mode, 0 k ohm BI Dry contact UI Dry Contact Maintained Mode BI Dry Contact Maintained Mode AO 0-10 VDC at 10 ma AO Voltage Mode, 0 10 VDC CO Voltage Mode, 0 10 VDC UO Voltage Mode, 0 10 VDC BO VAC Triac at 0.5A BO VAC triac CO I/O Expansion Comparison Beginning with FX-PCT Release 10.1, the FX-PCV183 controller can use FX-PCX Expansion I/O Modules for I/O expansion on the Sensor Actuator (SA) Bus. Room Sensor Comparisons Table 5: Room Sensor Comparisons Attribute VMA1xx FX-PCV183 Implication Network Sensors Supported TMZ Series Zone Sensors NS Series Network Sensors Replace TMZ with NS sensor. Wireless Sensors Supported TE-77 Wireless Room Sensor Transmitter/Receiver FX-WRZ7860 One-to-One Wireless Sensing System Replace TE-77 with FX-WRZ7860 One-to-One Wireless Sensing System. WRS-TTxx FX-WRZ7860 One-to-One Wireless Sensing System Replace WRS-TTxx with FX-WRZ7860 One-to-One Wireless Sensing System. Analog Sensors Supported TE-67 and TE-68 Series TE-77 and TE-68 Series Reusing sensors is possible. 1 1 Some room sensors (TE and -1, TE-67xx, and TE-67xx) featured modular (phone) jack connections and require adaptation for use with the FX-PCG controllers. 1

15 If you reuse a TE-67xx or TE-68xx Series sensor, be aware that the single setpoint or no setpoint models feature an LED, but the FX-PCG controller does not support the LED. As a result, you need to change the sensor's DIP switch settings as follows: If Temporary Occupied function is required for the application, set the DIP switch positions on the back of the sensor to down, up, and down (LED disabled, but Sensor and Push Button enabled). If Temporary Occupied function is not required, set the DIP switch positions to down, down, and down (LED and PB disabled). Figure 5: TE-67xx and TE-68xx Sensor DIP Switch Setting Dual setpoint sensor models do not feature an LED, and as a result, you should not need to change the DIP switch settings. Control Logic Configuration Table 6: Control Logic Comparison Attribute UNT FX-PCG Implication Programming Tool HVACPro FX-PCT Recreate the UNT s control logic with FX-PCT. Control Logic Q/A Session for fan coils, unit vents, packaged rooftops, and heat pumps Sideloop Session System Selection Wizard for fan coils, unit vents, packaged rooftops, and heat pumps Sideloop Wizard Recreating the UNT's control logic should be straightforward by using the FX-PCT System Selection Wizard or Sideloop Wizard. N Device and Point Configuration Legacy VMA1xx controllers identified themselves to their N supervisor as a VMA device type. The FX-PCV183 does not support identifying itself to its N supervisor as a VMA device type. As a result, you must use the FX-PCT's N Mapping interface to set the FX-PCV183 controller's device type to VND and reconfigure the N supervisor so that the FX-PCV controller is mapped as a VND device. 15

16 Figure 6: Using FX-PCT to Set the FX-PCV183 Device Type to VND Additionally, the FX-PCT System Selection Wizard for the Single Duct VAV Box (VAV-SD) application automatically defines the FX-PCV183 controller's N point mapping table to resemble the VMA1xx controller's N point map. Doing so eliminates the need to change the N supervisor's point mapping configuration. All other VAV box control applications (for example, dual duct applications) require you to use the FX-PCT N Mapping interface to manually create the N point mapping table. N Supervisor Configuration As described previously, the FX-PCV183 does not support identifying itself to an N supervisor as a VMA device type. As a result, you must reconfigure the N supervisor so that it is mapped as a VND device. Also, if the FX-PCV183 N point mapping does not exactly match its N supervisor's point mapping, then you need to reconfigure the N supervisor so that it does. The procedure for performing these changes depends on the type of N supervisor. For an N30 type N supervisor, perform these changes offline using the Project Builder tool. Refer to the Project Builder User's Guide (LIT-69305). For an NAE type N supervisor, perform these changes offline using the System Configuration Tool (SCT). Refer to N Integration with the NAE Technical Bulletin (LIT ). For an NCM type N supervisor, changing the NCM database requires you to delete the old hardware and define the new hardware. The incremental DDL compile method (@NC+) using the DELETE keyword simplifies the NCM database change. GPL and JC Basic processes may not need to be recompiled. Refer to the DDL Programmer's Manual (LIT ). For an FX Supervisory Controller type N supervisor, perform these changes offline using FX Workbench. Refer to the FX Workbench User's Guide (LIT ). For replacements that switch to VND Device Type, point mapping is unrestricted. To make the FX-PCV183 replacement operation as similar as possible to the old VMA1xx device: Select a Supervisor Object Type that matches the replaced controller point. For multi-state objects, select an appropriate States Text table. Use the Supervisor Object Definition to restrict commands. 16

17 Replacing DX-9100 Extended Digital Controllers The DX-9100 Extended Digital Controller, like its predecessor, the Lab and Central Plant (LCP) controller, was used most popularly for central plant and air handling unit control; however, its flexible programmability enabled it to be applied to a wide variety of equipment control applications, especially those requiring custom configurations. Also, its onboard real-time clock and operator interface made it popular for stand-alone equipment control applications. The recommended FX-PC replacement controller model for the DX-9100 is the FX-PCA3611. See the following sections for key differences. Note: This section includes details for the N versions of the DX-9100 only. Although replacement of the LONWORKS NE devices face many of the same challenges, you must replace devices such as the DX-911 (TP78 topology) and DX-900 (FTT topology) with LN Series programmable LONWORKS controllers. Footprint Considerations The external terminals on the base of DX-9100 makes it about inches taller but about one inch narrower than the FX-PCA3611. Replacement in the same enclosure space may be possible when not using all of the I/Os on the DX. Special consideration is required for DX-9100 Series controllers that mount on the face of an enclosure. You may need to find a retrofit solution such as using a new panel enclosure. Figure 7: Footprint Considerations - FX-PCA3611 Table 7: DX-9100 and FX-PCA3611 Replacement Dimensions Dimension DX-9100x FX-PCA3611 Height Width Depth 00 mm (7.9 in.) 18 mm (7. in.) 100 mm (3.9 in.) 150 mm (5.9 in.) 0 mm (8.7 in.) 57.5 mm (.3 in.) Consider that the onboard I/O count for an FX-PCA3611 is slightly less than a DX As a result, you may need to add an FX-PCX Expansion I/O Module even if the old installation did not use XT/XP extension modules. Installations that used one or more extension module sets may need extensive rearranging to accommodate the equivalent point count FX-PCXs. Some space is regained as the XT communication module is removed. 17

18 Figure 8: Footprint Considerations - FX-PCX3711 Table 8: XT/XP and FX-PCX Replacement Dimensions Dimension XT Plus 1 XPs XT Plus XPs FX-PCX3711 Height 118 mm (.65 in.) 118 mm (.65 in.) 150 mm (5.9 in.) Width 1 10 mm (5.5 in.) 350 mm (13.8 in.) 90 mm (3.5 in.) Depth 57 mm (.5 in.) 57 mm (.5 in.) 53 mm (.1 in.) 1 Each XT or XP module is 70 mm (.76 in.) wide. Wiring Connections Comparison Table 9: Wiring Connection Similarities, Differences and Implications Attribute DX-9100 FX-PCA3611 Implication I/O Wiring Connection Location See Figure 9. See Figure 9. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCA3611 I/O wiring connection points. If not, you need to lengthen the I/O wiring. Connection Type Fixed screw terminal connectors Fixed screw terminal connectors No change is necessary. N Wiring Connection Location See Figure 9. See Figure 9. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCA3611 wiring connection points. If not, you need to lengthen the I/O wiring. Connection Type -wire removable screw terminal connector -wire removable screw terminal connector Replace the DX-9100's N wiring connector with the FX-PCA3611's wiring connecter. 18

19 Table 9: Wiring Connection Similarities, Differences and Implications Attribute DX-9100 FX-PCA3611 Implication Power Supply Wiring Connection Location See Figure 9. See Figure 9. You can reuse the existing power supply wiring if the existing wiring is long enough to reach the FX-PCA3611 power supply connection point. If not, you need to lengthen the I/O wiring. Connection Type Fixed, -wire screw terminal connector Removable, -wire screw terminal connector No change is necessary. Figure 9: Comparison between DX-9100 and FX-PCA3611 Controllers' Wiring Connection Locations 19

20 Point Comparison Table 10: DX Point Comparison Code Number Termination AI Type DX DX Screw Terminal Screw Terminal 8 8 Expansion Modules used with XT communications interface: XP-910 XP-9103 XP-910 XP-9105 XP Expansion modules used with XTM communications interface: XPA-81 XPB-81 XPL-01 XPE-01 XPE-0 XPT-01 XPT-861 Screw Terminal Screw Terminal 6 BI AO 8 BO RO 3 Table 11: FX-PCA/FX-PCX Point Comparison Code Termination Universal BI Number Type Inputs (UI) AO BO Configurable Outputs (CO) Universal Outputs (UO) RO FX-PCA611 Screw Terminal FX-PCA FX-PCA

21 Table 11: FX-PCA/FX-PCX Point Comparison Code Number Termination Type Universal Inputs (UI) BI AO BO Configurable Outputs (CO) Universal Outputs (UO) RO FX-PCX1711 FX-PCX711 F Screw Terminal FX-PCX71 8 FX-PCX3711 FX-PCX FX-PCX FX-PCX FX-PCX1711 FX-PCX711 Table 1: DX/XP Point Comparison DX/XP Point Type Characteristics FX-PCA/FX-PCX Point Type Characteristics AI RTD (Ni1000, Pt1000, A99) 0-10 VDC (300k minimum impedance) 0/-0 ma (100 ohm impedance) UI Resistance temperature detector (RTD) (1k NI, 1k PT, A99B SI) Negative temperature coefficient (NTC) (10k Type L,.5k Type ) Voltage Mode, 0 10 VDC Current Mode, 0 ma Resistive Mode, 0 k ohm DI Potential-free contacts UI Dry Contact Maintained Mode Transition counter function: maximum 10 Hz BI Dry Contact Maintained Mode Pulse Counter/Accumulator Mode (High Speed), 100 Hz AO Version 1: [AO1-] AO Voltage Mode, 0 10 VDC 0-10 VDC (maximum 10 ma) Current Mode, 0 ma 0/-0 ma (maximum 500 ohm) CO Voltage Mode, 0 10 VDC Version 0-10 VDC (AO1- and AO9-15) 0/-0 ma (AO1- and AO9-10 only) UO Analog Output, Voltage Mode, 0 10 VDC Analog Output, Current Mode, 0 ma DO Triac VAC, 0.5 ampere continuous (0.8 ampere peak) BO CO VAC Triac UO Binary Output Mode, VAC/DC FET 1

22 Table 1: DX/XP Point Comparison DX/XP Point Type Characteristics FX-PCA/FX-PCX Point Type Characteristics RO XP9107: Latching relays RO Signal mode: Maintained XPL-01: Latching relays, manual override Startup OFF State Enable: False Single-Pole, Single-Throw: UL 916:1/ hp 10 VAC, 1/ hp 0 VAC; 360 VA Pilot Duty at 10/0 VAC (B300); 3 A Non-inductive -0 VAC; EN 60730: 6 () A N.O. or N.C. only RO XPE-01: Electrically maintained, manual override RO Signal mode: Maintained Startup OFF State Enable: True RO XPE-0: On/Off or pulse, manual override (common supply) RO Signal mode: Start Stop Startup OFF State Enable: True

23 Additional Considerations When using active sensors, be sure that the FX-PC controller and I/O module can provide sufficient current at the voltage required by transmitters. Current mode of Universal Input range is limited to -0 ma. The FX-PC controller does not support the 0-0 ma Analog Input range. FX-PC controller power requirements are greater than DX Recalculate power requirements for all replacement configurations. Include any auxiliary devices that are also powered by the DX-9100 or its transformer. Remember to include power requirement for any FX-DIS1710 module when calculating transformer capacity. The DX family used a slightly different communication protocol. The FX-PC family controllers use the N Open protocol. The real-time clock and alarm functions available in FX-PC controllers support many stand-alone applications. Display Comparison The DX-9100 featured an onboard LCD display and an optional DT9100 display unit. You can partially duplicate the local display functionality by replacing it with an FX-DIS1710. However, the FX-DIS1710 does not provide access to real-time clock functions (such as scheduling, trending, and alarming). Table 13: Differences between DX-9100 Front Panel Display, DT-9100 Local Display, and FX-DIS1710 Function/Feature DX Front Panel DT-9100 Local Display FX-DIS1710 Show attached expansion module points Yes Programmable Yes Password protection No Programmable Single user I/O Override capability LCP Key inserted Programmable Yes Setpoint adjustment LCP Key inserted Programmable Yes Display Real Time Clock, Calendar, Exception Days, Daylight Saving Time Yes Display date and time only Display date and time only Adjust Clock and Schedule functions LCP Key inserted No No Control Logic Configuration Table 1: Control Logic Comparison Attribute DX-9100 FX-PCA3611 Implication Programming Tool GX-Tool FX-PCT You can recreate the DX-9100's control logic with FX-PCT, but it requires custom programming using a different programming tool interface. Programming Modules Sequencer Global Sequencer Binary Sequencer DX-9100 applications created with the GX Tool cannot be duplicated using the FX-PCT System Selection Wizard. As a result, you must recreate the control application using the FX-PCT custom programming capabilities. N Device and Point Configuration DX-9100 controllers identify themselves to their N supervisor as a Sys91 device type. The FX-PCA3611 does not support identifying itself to its N supervisor as a Sys91 device type. As a result, you must use the FX-PCT N Mapping interface to set the FX-PCA3611 controller s device type to VND, and reconfigure the N supervisor so that it is mapped as a VND device. See N Supervisor Configuration for more information. In addition, you must use the FX-PCT N Mapping interface to manually create the N point mapping table. 3

24 N Supervisor Configuration As described previously, the FX-PC controllers do not support identifying themselves to an N supervisor as a SyS91 device type. As a result, you must reconfigure the N supervisor so that the FX-PC controller is mapped as a VND device. Also, if the FX-PCA3611 N point mapping does not exactly match its N supervisor point mapping, then you need to reconfigure the N supervisor so that it does match the supervisor point mapping. The procedure for performing these changes depends on the type of N supervisor. For an N30 type N supervisor, perform these changes offline using the Project Builder tool. Refer to the Project Builder User's Guide (LIT-69305). For an NAE type N supervisor, perform these changes offline using the System Configuration Tool (SCT). Refer to N Integration with the NAE Technical Bulletin (LIT ). For an NCM type N supervisor, changing the NCM database requires you to delete the old hardware and define the new hardware. The incremental DDL compile method (@NC+) using the DELETE keyword simplifies the NCM database change. GPL and JC Basic processes may not need to be recompiled. Refer to the DDL Programmer's Manual (LIT ). For an FX Supervisory Controller type N supervisor, perform these changes offline using FX Workbench. Refer to the FX Workbench User's Guide (LIT ). For replacements that switch to VND Device Type, point mapping is unrestricted. To make the FX-PCA3611 replacement operation as similar as possible to the old DX-9100 controllers: Select a Supervisor Object Type that matches the replaced controller point. For multi-state objects, select an appropriate States Text table. Use the Supervisor Object Definition to restrict commands.

25 Replacing UNT Unitary Controllers UNT Unitary Controllers were used extensively for controlling packaged rooftop and heat pump units, small air handling units, unit ventilators, fan coils, and other terminal units serving a single zone or room. They were also frequently used as I/O devices for generic monitoring and control. Various UNT models were offered, and they were applied to a wide range of applications. To replace a UNT controller in an application where only a few of its inputs are being used, we recommend using the FX-PCG1611 controller. To replace a UNT controller in an application where most or all of its inputs are being used, we recommend using the FX-PCG611 controller. If the FX-PCG controller does not have enough onboard I/O to meet the replacement application requirements, then add FX-PCX Expansion I/O Modules. Make note of any special application controllers such as for use in low or extended temperature applications. Contact your Johnson Controls representative or technical support group for recommendations. Footprint Considerations All models of UNT controllers have a footprint slightly larger than an FX-PCG1611 controller, so replacing a UNT with an FX-PCG1611 using the same enclosure space is highly probable. The FX-PCG611 is approximately 1 in. (.5 cm) wider than a UNT. As a result, if you use an FX-PCG611 to replace a UNT, be sure to verify that enough space is available in the enclosure. Figure 10: Dimensional Comparison of UNT versus FX-PCG1611 5

26 Figure 11: Dimension Comparison of UNT versus FX-PCG611 Table 15: Dimensional Comparison of UNT versus FX-PCG1611 and FX-PCG611 Dimension UNT (All Models) FX-PCG1611 FX-PCG611 Height 165 mm (6.5 in.) 150 mm (5 9 in.) 150 mm (5 9 in.) Width 163 mm (6. in.) 16 mm (6.5 in.) 190 mm (7.5 in.) Depth 56 mm (. in.) 5 mm (.1 in.) 5 mm (.1 in.) 6

27 Wiring Connections Comparison Table 16: Wiring Connection Similarities, Differences and Implications Attribute UNT FX-PCG Implication I/O Wiring Connection Location See Figure 1. See Figure 1. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCG I/O wiring connection points. If not, you need to lengthen the wiring. Connection Type N Wiring Spade lug connectors Fixed screw terminal connectors Remove spade lug connectors from I/O wiring. Connection Location See Figure 1. See Figure 1. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCG N connection point. If not, you need to lengthen the wiring. Connection Type Power Supply Wiring Removable, 3-wire screw terminal connector Removable, -wire screw terminal connector Replace the UNT's N wiring connector with the FX-PCGs. Connection Location See Figure 1. See Figure 1. You can reuse the existing power supply wiring if the existing wiring is long enough to reach the FX-PCG power supply connection point. If not, you need to lengthen the wiring. Connection Type Spade lug with removable -wire screw terminal connector Removable, 3-wire screw terminal connector Remove existing connectors from power. Figure 1: Wiring Layout Comparison of UNT versus FX-PCG 7

28 Point Comparison Table 17: UNT Point Comparison Code Number Termination Type AI BI AO BO RO UNT110/10 Spade Lug 6 8 UNT11/113 UNT111/11 6 UNT10 Screw Terminal 6 8 UNT11 6 UNT1108 UNT116 UNT11 Spade Lug with Removable Screw Terminal Option Table 18: FX-PCG Point Comparison Code Number 1 Termination Type Universal Inputs (UI) BI AO BO Configurable Outputs (CO) Universal Outputs (UO) RO FX-PCG1611 FX-PCG611 Screw Terminal FX- PCG711 FX-PCG71 Screw Terminal 8 FX-PCX Add FX-PCXs as required to match point count need. Table 19: UNT to FX-PCG/FX-PCX Controller Point Comparison UNT Point Type Characteristic FX-PCG/FX-PCX Point Type Characteristic AI RTD Temp. Elem. (NI, SI or PT) UI Resistance temperature detector (RTD) (1k NI, 1k PT, A99B SI) 0-10 VDC Transducer k ohm Setpoint Potentiometers Negative temperature coefficient (NTC) (10k Type L,.5k Type ) Voltage Mode, 0 10 VDC Current Mode, 0 ma Resistive Mode, 0 k ohm BI -Dry Contacts UI Dry Contact Maintained Mode BI-Accum. Input BI Dry Contact Maintained Mode Pulse Counter/Accumulator Mode (High Speed), 100 Hz AO 0 to 10 VDC at 10 ma AO Voltage Mode, 0 10 VDC Current Mode, 0 ma CO Voltage Mode, 0 10 VDC UO Voltage Mode, 0 10 VDC 8

29 Table 19: UNT to FX-PCG/FX-PCX Controller Point Comparison UNT Point Type Characteristic FX-PCG/FX-PCX Point Type Characteristic BO VAC Triac at 0.5 A 1 BO VAC Triac CO RO VAC Relays at A, 13A Inrush (Class ) 3 RO (Single-Pole, Single-Throw: UL 916:1/ hp 10 VAC 1/ hp 0 VAC; 360 VA Pilot Duty at 10/0 VAC (B300); 3 A Non-inductive -0 VAC; EN 60730: 6 () A N.O. or N.C. only 1 UNT11n - Low Side Switching only - UNT1n - Low or High Side Common Selectable FX-PCGx611 - Low or High Side switching 3 UNT11nn Source sinking or dry contact (jumper selectable per output) RO available on FX-PCX711, FX-PCX3711 RLY Relay Module Considerations RLY relay modules were frequently added to the UNT controller's binary outputs. You can reuse RLY relay modules when you replace the UNT with an FX-PCG. Each RLY relay module must be wired to one FX-PCG binary or to one configurable output (configured for binary output mode). If both relays on one RLY relay module are used, the FX-PCG controller outputs must be configured identically. Alternatively, you can replace RLY relay modules with FX-PCX models with onboard relay outputs. 9

30 Figure 13: Connecting RLY Relay Modules to FX-PCG Controller Zone Bus Considerations UNT controllers support a Zone Bus for optionally connecting TMZ Series network room sensors, TE-77 Series wireless temperature sensor or receivers, a ZTU Zone Terminal Unit, and M100C Series networked actuators. FX-PC controllers do not support the Zone Bus, and accordingly do not support these devices. Instead, FX-PC controllers feature a Sensor Actuator (SA) bus for connecting NS Series Network Sensors, FX-DIS Local Display/Keypad, and FX-PCX Series Expansion I/O Modules. When using an FX-PC controller to replace a UNT controller that uses a TMZ sensor, you must also replace the TMZ sensor with an NS Series Network Sensor. The NS sensor provides many of the same functions as the TMZ sensor, including zone temperature sensing, zone temperature setpoint adjustment, and LCD display. However, the NS sensor is housed in an enclosure that has a different user interface. For example, the NS sensor features a dial to adjust the zone temperature setpoint, whereas the TMZ features a pushbutton keypad. As a result, we recommend you work with your customer to help them and their building's occupants understand how to use the adjustment features of the new NS sensor. When using an FX-PC controller to replace a UNT controller that uses a TE-77xx wireless transmitter/receiver, you must also replace the TE-77xx with the Facility Explorer One-to-One Wireless Room Sensing System. For more information, refer to the Facility Explorer One-to-One Wireless Room Sensing System Product Bulletin (LIT ). 30

31 When using an FX-PC controller to replace a UNT controller that uses a ZTU Zone Terminal Unit, you must replace the ZTU with an FX-DIS1710 Local Display/Keypad. You can partially duplicate the Zone Terminal Unit functionality with the FX-DIS1710. However, the FX-DIS1710 does not provide access to real-time clock functions such as scheduling, trending, and alarming. When using an FX-PC controller to replace a UNT controller that uses an M100C zone bus actuator, you must replace the actuator with a non-networked actuator. For dampers, use the M9100/M900 Series. For valves, use the VA7800/VA-7150 Series. To control the new actuator, use the available analog output or configurable output interfaces on the FX-PC controller. If none are available, add an FX-PCX Expansion I/O Module. Room Sensor Comparisons Table 0: Room Sensor Comparisons Attribute UNT FX-PCG Controller Implication Network Sensors Supported TMZ Series Zone Sensors NS Series Network Sensors Replace TMZ with NS sensor. Wireless Sensors Supported TE-77 Wireless Room Sensor Transmitter/Receiver FX-WRZ7860 One-to-One Wireless Sensing System Replace TE-77 with FX-WRZ7860 One-to-One Wireless Sensing System. WRS-TTxx FX-WRZ7860 One-to-One Wireless Sensing System Replace WRS-TTxx with FX-WRZ7860 One-to-One Wireless Sensing System. Analog Sensors Supported TE-77 and TE-78 Series TE-77 and TE-78 Series Reusing sensors is possible. 1 1 Some room sensors (TE and -1, TE-67xx, and TE-67xx) featured modular (phone) jack connections and require adaptation for use with the FX-PC controllers. If you reuse a TE-67xx or TE-68xx series sensor, be aware that the single setpoint or no setpoint models feature an LED, but the FX-PC controller does not support the LED. As a result, you need to change the sensor's DIP switch settings as follows: If Temporary Occupied function is required for the application, set the DIP switch positions on the back of the sensor to down, up, and down (LED disabled, but Sensor and Push Button enabled). The FX-PC controllers do not support the shorting of AI-1 to sense the Temp Occ button. If Temporary Occupied function is not required, set the DIP switch positions to down, down, and down (LED and PB disabled). Figure 1: TE-67xx and TE-68xx Sensor DIP Switch Setting Dual setpoint sensor models do not feature an LED. Therefore, you do not need to change the DIP switch settings. Control Logic Configuration Recreating a VMA1xx controller's application that was programmed with HVACPro should be straightforward. The FX-PCT System Selection Wizard and Sideloop Wizard provide control logic creation capabilities that are nearly identical to HVACPro's Question and Answer (Q&A) wizard and Sideloop wizard. 31

32 At Release 10.0, the FX-PCV183 controller featured N field bus networking (not switchable to BACnet MS/TP). Also at Release 10.0, pre-built, single-duct VAV box control applications files replaced VMA1xx controllers programmed with HVACPro. Those pre-built files contained control logic translators to make the FX-PCV183 controller's VAV box control application better resemble the VMA1xx controller's application created with HVACPro and minimize reconfiguration of the N supervisor. At Release 10.1, pre-built VAV box control applications are no longer provided. Instead, all control logic translators provided by the pre-built, single-duct VAV box control application files are now options that you can select using the FX-PCT System Selection Wizard. Select the N Compatibility Options section of the System Selection Wizard to choose the appropriate replacement application (see Figure 15). Figure 15: N Compatibility Options N Device and Point Configuration Legacy UNT controllers identify themselves to their N supervisor as a UNT device type. The FX-PCG supports identifying itself to its N supervisor as a UNT device type, which eliminates the need to change this setting in the N supervisor's configuration. To configure this capability, use the N Mapping feature of FX-PCT as show in Figure 16. 3

33 Figure 16: Compatibility Options Additionally, the FX-PCT System Selection Wizard for the Mixed Air Single Duct Air Handling Unit (MASD) application includes an option to automatically define the N mapping table to minimize N supervisor reconfiguration. All other applications require you to manually create the N Mapping Table. N Supervisor Configuration As described previously, you can configure the FX-PCG controller to identify itself to an N supervisor as a UNT device type. If you configure the FX-PCG this way, you do not need to reconfigure the N supervisor in this regard. Also, if you configure the MASD application to automatically generate the N mapping table, then you do not need to reconfigure the N supervisor in this regard. However, if the FX-PCG N point mapping does not exactly match its N supervisor's point mapping, then you need to reconfigure the N supervisor so that it does. The procedure for performing these changes depends on the type of N supervisor. For an N30 type N supervisor, perform these changes offline using the Project Builder tool. Refer to the Project Builder User's Guide (LIT-69305). For an NAE type N supervisor, perform these changes offline using the System Configuration Tool (SCT). Refer to N Integration with the NAE Technical Bulletin (LIT ). For an NCM type N supervisor, changing the NCM database requires you to delete the old hardware and define the new hardware. The incremental DDL compile method (@NC+) using the DELETE keyword simplifies the NCM database change. GPL and JC Basic processes may not need to be recompiled. Refer to the DDL Programmer's Manual (LIT ). For an FX Supervisory Controller type N supervisor, perform these changes offline using FX Workbench. Refer to the FX Workbench User's Guide (LIT ). 33

34 For replacements that switch to VND Device Type, point mapping is unrestricted. To make the FX-PCG replacement operation as similar as possible to the old UNT device: Select a Supervisor Object Type that matches the replaced controller point. For multi-state objects, select an appropriate States Text table. Use the Supervisor Object Definition to restrict commands. 3

35 Replacing VAV1xx Variable Air Volume Box Controllers VAV1xx Variable Air Volume Box Controllers were used extensively for controlling VAV boxes, and they were also frequently used as I/O devices for generic monitoring and control. To replace a VAV1xx controller in a VAV box application, we recommend using the FX-PCV183 controller. To replace a VAV1xx controller in an I/O expansion application, we recommend using the FX-PCG1611 controller. Footprint Comparison All models of VAV1xx have a footprint slightly larger than an FX-PCG controller. Replacing a VAV1xx with an FX-PCG1611 in an I/O application using the same enclosure space is highly probable. When used in a VAV box control application, the VAV1xx is typically connected to an EDA series actuator or an ATP series actuator/pressure transducer assembly. You need to replace both the VAV1xx and the EDA/ATP actuator with the FX-PCV183. The FX-PCV183 is mounted in place of the EDA/ATP actuator, so this dimensional comparison is key. The FX-PCV183 is slightly larger than the EDA/ATP. As a result, if you use an FX-PCV183 to replace a VAV1xx controller plus EDA/ATP actuator assembly, be sure to verify that enough space is available in the enclosure. Figure 17: Dimensional Comparison of VAV1xx versus FX-PCG

36 Figure 18: Dimension Comparison of VAV1xx versus FX-PCV183 Figure 19: Dimension Comparison of EDA/ATP versus FX-PCV183 Table 1: Dimensional Comparison of VAV1xx versus FX-PCG1611, and FX-PCV183 Dimension VAV1xx EDA/ATP Actuator FX-PCG1611 FX-PCV183 Height 165 mm (6.5 in.) 1.8 mm (5.7 in.) 150 mm (5.9 in.) 165 mm (6.5 in.) Width 163 mm (6. in.) mm (.0 in.) 16 mm (6.5 in.) 15 mm (.9 in.) Depth 56 mm (. in.) 59.1 mm (.3 in.) 5 mm (.1 in.) 73 mm (.9 in.) 36

37 Wiring Connections Comparison Table : Wiring Connection Similarities, Differences, and Implications Attribute VAV1xx FX-PCG Implication I/O Wiring Connection Location See Figure 0. See Figure 0. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCG's I/O wiring connection points. If not, you need to lengthen the wiring. Connection Type N Wiring Spade lug connectors Fixed screw terminal connectors Remove spade lug connectors from I/O wiring. Connection Location See Figure 0. See Figure 0. You can reuse the existing N wiring if the existing wiring is long enough to reach the FX-PCG's N connection point. If not, you need to lengthen the wiring. Connection Type Power Supply Wiring Removable, 3-wire screw terminal connector Removable, -wire screw terminal connector Replace the UNT's N wiring connector with the FX-PCG's N connection point. Connection Location See Figure 0. See Figure 0. You can reuse the existing power supply wiring if the existing wiring is long enough to reach the FX-PCG's power supply connection point. If not, you need to lengthen the wiring. Connection Type Spade lug with removable -wire screw terminal connector Removable, 3-wire screw terminal connector Remove existing connectors from power supply wiring and use FX-PCG's screw connector. 37

38 Figure 0: Wiring Layout Comparison of VAV1xx versus FX-PCG1611 Table 3: Wiring Connection Similarities, Differences, and Implications Attribute VAV1xx FX-PCV183 Implication I/O Wiring Connection Location See Figure 1. See Figure 1. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCV183's I/O wiring connection points. If not, you need to lengthen the wiring. Connection Type Spade lugs Spade lugs No change is necessary, but be careful when matching the I/O number. N Wiring Connection Location See Figure 1. See Figure 1. You can reuse the existing N wiring if the existing wiring is long enough to reach the FX-PCV183's N connection point. If not, you need to lengthen the wiring. Connection Type Removable 3-wire screw terminal connector Removable -wire screw terminal connector Remove connector from the existing N wiring and use the FX-PCV183's screw connector. Power Supply Wiring 38

39 Table 3: Wiring Connection Similarities, Differences, and Implications Attribute VAV1xx FX-PCV183 Implication Connection Location See Figure 1. See Figure 1. You can reuse the existing power supply wiring if the existing wiring is long enough to reach thefx-pcv183's power supply connection point. If not, you need to lengthen the wiring. Connection Type Spade lug with removable 3-wire screw terminal connector -wire removable screw terminal connector Remove existing connectors from power supply wiring and use FX-PCV183's screw connector. Figure 1: Wiring Comparison of VAV1xx versus FX-PCV183 39

40 Point Comparison Table : VAV Point Comparison Code Number Termination Type AI BI AO BO RO VAV110 Spade Lug 6 8 VAV111 6 VAV10 Screw Terminal 6 8 VAV11 6 Table 5: FX-PC Point Comparison Code Number Termination Type Universal Inputs (UI) BI AO BO Configurable Outputs (CO) Universal Outputs (UO) RO FX-PCG1611 Screw Terminal 1 3 FX-PCV183 Spade Lug 3 FX-PCX711 Screw Terminal Table 6: VAV to FX-PCV183 Controller Point Comparison UNT Point Type Characteristic FX-PCV183 Point Type Characteristic AI RTD Temp. Elem. (NI, SI or PT) UI Resistance temperature detector (RTD) (1k NI, 1k PT, A99B SI) 0-10 VDC Transducer k ohm Setpoint Potentiometers Negative temperature coefficient (NTC) (10k Type L,.5k Type ) Voltage Mode, 0 10 VDC Current Mode, 0 ma Resistive Mode, 0 k ohm BI -Dry Contacts UI Dry Contact Maintained Mode BI-Accum. Input BI Dry Contact Maintained Mode Pulse Counter/Accumulator Mode (High Speed), 100 Hz AO 0 to 10 VDC at 10 ma AO Voltage Mode, 0 10 VDC Current Mode, 0 ma CO Voltage Mode, 0 10 VDC UO Voltage Mode, 0 10 VDC BO VAC Triac at 0.5 A BO VAC Triac CO Zone Bus Considerations VAV1xx controllers support a Zone Bus for optionally connecting TMZ Series network room sensors, TE-77 Series wireless temperature sensors and receivers, and M100C Series networked actuators. FX-PC controllers do not support the Zone Bus, and accordingly do not support these devices. Instead, FX-PC controllers feature a different technology bus called the Sensor Actuator (SA) bus for connecting NS Series Network Sensors and FX-PCX Series Expansion I/O Modules. 0

41 When using an FX-PC controller to replace a VAV1xx controller that uses a TMZ sensor, you must also replace the TMZ sensor with an NS Series Network Sensor. The NS sensor provides many of the same functions as the TMZ sensor, including zone temperature sensing, zone temperature setpoint adjustment, and LCD display. However, the NS sensor is housed in an enclosure that has a different user interface. For example, the NS sensor features a dial to adjust the zone temperature setpoint, whereas the TMZ features a pushbutton keypad. As a result, we recommend you work with your customer to help them and their building's occupants understand how to use the adjustment features of the new NS sensor. When using an FX-PC controller to replace a VAV1xx controller that uses a TE-77xx wireless transmitter/receiver, you must also replace the TE-77xx with the Facility Explorer One-to-One Wireless Room Sensing System. For more information, refer to the Facility Explorer One-to-One Wireless Room Sensing System Product Bulletin (LIT ). When using an FX-PC controller to replace a UNT controller that uses an M100C zone bus actuator, you must replace the actuator with a non-networked actuator. For dampers, use the M9100/M900 Series. For valves, use the VA7800/VA-7150 Series. To control the new actuator, use the available analog output or configurable output interfaces on the FX-PC controller. If none are available, add an FX-PCX Expansion I/O Module. Room Sensor Comparisons Table 7: Room Sensor Comparisons Attribute VAV1xx FX-PCV183 Implication Network Sensors Supported TMZ Series Zone Sensors NS Series Network Sensors Replace TMZ with NS sensor. Wireless Sensors Supported TE-77 Wireless Room Sensor Transmitter/Receiver FX-WRZ7860 One-to-One Wireless Sensing System Replace TE-77 with FX-WRZ7860 One-to-One Wireless Sensing System. WRS-TTxx FX-WRZ7860 One-to-One Wireless Sensing System Replace WRS-TTxx with FX-WRZ7860 One-to-One Wireless Sensing System. Analog Sensors Supported TE-77 and TE-78 Series TE-77 and TE-78 Series Reusing sensors is possible. 1 1 Some room sensors (TE and -1, TE-67xx, and TE-67xx) featured modular (phone) jack connections and require adaptation for use with the FX-PC controllers. If you reuse a TE-67xx or TE-68xx series sensor, be aware that the single setpoint or no setpoint models feature an LED, but the FX-PC controller does not support the LED. As a result, you need to change the sensor's DIP switch settings as follows: If Temporary Occupied function is required for the application, set the DIP switch positions on the back of the sensor to down, up, and down (LED disabled, but Sensor and Push Button enabled). If Temporary Occupied function is not required, set the DIP switch positions to down, down, and down (LED and PB disabled). Figure : TE-67xx and TE-68xx Sensor DIP Switch Setting Dual setpoint sensor models do not feature an LED. Therefore, you do not need to change the DIP switch settings. 1

42 Control Logic Configuration Table 8: Control Logic Comparisons Attribute VAV1xx FX-PCV183 Implication Programming Tool HVACPro FX-PCT Recreate the VAV's control logic with FX-PCT. Control Logic Q/A Session for VAV Single Duct Sideloop Session System Selection Wizard for VAV Single Duct Sideloop Wizard Recreating the VAV's control logic should be straightforward by using the FX-PCT System Selection Wizard or Sideloop Wizard. Downloading Locally through the Zone Bus or N Bus using AS-CVPRO or MM-CVT or remotely using NAE Passthrough Locally through SA Bus using FX-BTCVT Bluetooth Commissioning Converter Must be onsite to download application using FX-PCT. Zone Terminal Unit Considerations The VAV1xx controller supported an optional ZTU Zone Terminal Unit, which is not compatible and cannot be used with FX-PC Controllers. You can partially duplicate the Zone Terminal Unit functionality by replacing it with an FX-DIS1710 Local Display/Keypad; however, the FX-DIS1710 does not provide access to real-time clock functions such as scheduling, trending, and alarming. N Device and Point Configuration Legacy VAV1xx controllers identify themselves to their N supervisor as a VAV device type. The FX-PCV and FX-PCG support identifying themselves to its N supervisor as a VAV device type, which eliminates the need to change this in the N supervisor's configuration. To configure this capability, use the N Mapping feature of FX-PCT to set the FX-PCV or FX-PCG controller's device type to VAV. Figure 3: Using FX-PCT to Set the FX-PC Controller's Device Type to VAV No utilities are available to automatically recreate the N Mapping Table, so you must manually recreate it using FX-PCT.

43 N Supervisor Configuration As described previously, you can configure the FX-PC controller to identify itself to an N supervisor as a VAV device type. If you configure the FX-PC controller this way, you do not need to reconfigure the N supervisor in this regard. If the FX-PC controller's N point mapping does not exactly match its N supervisor's point mapping, then you need to reconfigure the N supervisor so that it does. The procedure for performing these changes depends on the type of N supervisor. For an N30 type N supervisor, perform these changes offline using the Project Builder tool. Refer to the Project Builder User's Guide (LIT-69305). For an NAE type N supervisor, perform these changes offline using the System Configuration Tool (SCT). Refer to N Integration with the NAE Technical Bulletin (LIT ). For an NCM type N supervisor, changing the NCM database requires you to delete the old hardware and define the new hardware. The incremental DDL compile method (@NC+) using the DELETE keyword simplifies the NCM database change. GPL and JC Basic processes may not need to be recompiled. Refer to the DDL Programmer's Manual (LIT ). For an FX Supervisory Controller type N supervisor, perform these changes offline using FX Workbench. Refer to the FX Workbench User's Guide (LIT ). For replacements that switch to VND Device Type, point mapping is unrestricted. To make the FX-PCT controller replacement operation as similar as possible to the old VAV1xx device: Select a Supervisor Object Type that matches the replaced controller point For multi-state objects, select an appropriate States Text table Use the Supervisor Object Definition to restrict commands 3

44 Replacing AHU Air Handling Unit Controllers AHU controllers were used extensively for controlling air handling units, especially for complex units requiring more I/O interfaces than the UNT. Many FX-PC controller models can replace an AHU, but we recommend using the FX-PCA3611 because of its onboard I/O complement. If the FX-PCA3611 controller does not have enough onboard I/O to meet the replacement application requirements, then add FX-PCX Expansion I/O Modules. Footprint Comparison AHUs came mounted in two different configurations: a tower configuration and a three-high Universal Packaging Module (UPM). If the AHU is a tower configuration, you must replace the entire tower with a new control panel. If the AHU is in a UPM, there should be enough space for an FX-PCA3611. However, you may need to relocate auxiliary gear. The AHU controller's terminal board has a footprint slightly narrower but longer than an FX-PCA3611. Using the same enclosure space for replacement may require you to move auxiliary components, such as limit switches and electro-pneumatic transducers. Also, if an FX-PCX Expansion I/O Module is required to match the AHU's full I/O count, then additional enclosure space may be required.

45 Figure : Dimensional Comparison of AHU versus FX-PCA3611 plus FX-PCX3711 Table 9: Dimensional Comparison of AHU versus FX-PCA3611 and FX-PCX3711 Dimension AHU (All Models) FX-PCA3611 FX-PCX3711 Height 165 mm (6.5 in.) 150 mm (5.9 in.) 150 mm (5.9 in.) Width 163 mm (6. in.) 0 mm (8 7 in.) 190 mm (7.5 in.) Depth 56 mm (. in.) 57.5 mm (.3 in.) 53 mm (.1 in.) 5

46 Wiring Connections Comparison Table 30: Wiring Connection Similarities, Differences and Implications Attribute AHU FX-PCA3611 Implication I/O Wiring Connection Location See Figure 5. See Figure 5. You can reuse the existing I/O wiring if the existing wiring is long enough to reach the FX-PCA's I/O wiring connection points. If not, you need to lengthen the wiring. Connection Type N Wiring Fixed screw terminal connectors Fixed screw terminal connectors Remove spade lug connectors from I/O wiring. Connection Location See Figure 5. See Figure 5. You can reuse the existing N wiring if the existing wiring is long enough to reach the FX-PCA's N connection point. If not, you need to lengthen the wiring. Connection Type Power Supply Wiring Removable, 3-wire screw terminal connector Removable, -wire screw terminal connector Replace the AHU's N wiring connector with the FX-PCA. Connection Location See Figure 5. See Figure 5. You can reuse the existing power supply wiring if the existing wiring is long enough to reach the FX-PCA's power supply connection point. If not, you need to lengthen the wiring. Connection Type Removable 3-wire Molex connector Removable, 3-wire screw terminal connector Remove existing connectors from power supply wiring and use FX-PCA's screw connector. 6

47 Figure 5: Wiring Layout Comparison of AHU versus FX-PCA Point Comparison Code Number AHU10 RLY100 RLY050/00 Termination Type Spade Lug Cable Kit/Screw Terminal Analog Inputs (AI) 8 Binary Input (BI) 8 Analog Output (AO) 6 Binary Output (BO) 10 Relay Output (RO) 7

48 Code Number Termination Type Analog Inputs (AI) Binary Input (BI) Analog Output (AO) Binary Output (BO) Relay Output (RO) IAP IDP Cable Kit/Screw Terminal Uses one AI each Mounted in Function Module Kit (FMK10) OAP10/103 1 Uses one AO each M110C Zone Bus Damper and Valve Actuators 1 Replacement requires one AC, CO, or UO combined with external Electro-Pneumatic transducer. Table 31: FX-PCA and FX-PCX Point Comparison Code Number Termination Type Universal Input (UI) BI AO BO Configurable Output (CO) Universal Outputs (UO) RO FX-PCA611 FX-PCA61 Screw Terminals FX-PCA FX-PCX711 FX-PCX71 9 FX-PCX3711 Table 3: AHU/FX-PCA/FX-PCX Point Comparison AHU Point Type Characteristics FX-PCG/FX-PCX Point Type Characteristics AI RTD Temp. Elem. (NI, SI, or PT) 0-10 VDC Transducer 0 ma UI Resistance temperature detector (RTD) (1k NI, 1k PT, A99B SI), Voltage Mode, 0 10 VDC Current Mode, 0 ma BI 0-15 VDC Dry Contacts, TTL thresholds UI BI Dry Contact Maintained Mode Dry Contact Maintained Mode Pulse Counter/Accumulator Mode (High Speed), 100 Hz AO 0-10 VDC at 10 ma AO Current Mode, 0 ma 0-10 VDC (using 500 ohm resistor) Zone Bus (up to six M110CGA- actuators) CO UO Voltage Mode, 0 10 VDC Voltage Mode, 0 10 VDC Analog Output, Voltage Mode, 0 10 VDC Analog Output, Current Mode, 0 ma 8

49 Table 3: AHU/FX-PCA/FX-PCX Point Comparison AHU Point Type Characteristics FX-PCG/FX-PCX Point Type Characteristics BO VAC Triac at 0.5 A BO VAC Triac 1 CO UO Binary Output Mode, VAC/DC FET RO Optional relay kit 0 VAC at 5 amps RO Single-Pole, Single-Throw: UL 916:1/ hp 10 VAC, 1/ hp 0 VAC; 360 VA Pilot Duty at 10/0 VAC (B300); 3 A Non-inductive -0 VAC; EN 60730: 6 () A N.O. or N.C. only 1 All Triac configured BO and UO outputs are electrically isolated (capable of switching High or Low side). RLY Relay Module Considerations RLY relay modules are frequently added to the AHU controller's binary outputs. You can reuse RLY relay modules when replacing the AHU with an FX-PCA3611. You must wire each RLY relay module to one FX-PCA3611 binary or to one configurable output (configured for binary output mode). If both relays on one RLY relay module are used, you must configure the FX-PCA3611 controller outputs identically. Alternatively, you can replace RLY relay modules with FX-PCX models with onboard relay outputs. Figure 6: Connecting RLY Relay Modules to FX-PCA3611 Controller 9