Cp-wm-vav honeywell

•

CP-US-WM-VAV

•

CP-WM-VAV

Attention

Resolution of the PT1000 sensor: 1 Fahrenheit or

0.6 Centigrade.

Do not use the datapoint associated cp-wm-vav honeywell PT1000 in

control logic which requires a resolution less than

1 Fahrenheit.

The analog input with PT1000 can be used in

control loops only when connected to

CPO-VAV2A via a transducer with 0-10V rating.

Additionally, you must use the ComfortPoint Cp-wm-vav honeywell tool to define custom characteristics which

matches the selected transducer.

The PT1000 sensors connected directly with

CPO-VAV2A can be used only for monitoring ut austin vav purposes.

The connection between CPO-VAV2A and wall modules are

illustrated in Figure 15 through Figure 21.

1

COM

2

SENSOR

3

SETPOINT

T7460

4

BYP/FAN

Terminals

5

LED

6

BYP/RTN

7

LED/RTN

Figure 15 Connection of T7460 with the CPO-VAV2A

1

COM

2

SENSOR

3

SETPOINT

T7560

4

BYP/FAN

Terminals

5

LED

6

Bypass**

7

Humidity

8

24 Vac

Figure 16 Connection of T7560 with CPO-VAV2A

Attention

The CPO-VAV2A controller does not control the

LCD display of the T7560 Wall module. It handles

the temperature sensor input, Bypass/Fan, or Fan

Control Input. The LCD Display must not be used

to cp-wm-vav honeywell the Effective Occupancy state of the

controller.

1

AGND

2

Temp

VAV

3

Set Point

Terminals

4

ByPass/Fan

5

LED

1

AGND

2

Temp

VAV

3

Set Point

Terminals

4

ByPass/Fan

5

LED

COM

CO2 Output 0.10V

24 VAC/DC

C7110D

NTC 20kOhm

Terminals

SETPT. 1.10kOhm

LED INPUT

OCCUPANCY

Figure 17 Connection of C7710D with CPO-VAV2A

V+

Com AC/DC

TEMP

C7262A

TEMP

Terminals

OUT1: CO2

OUT2: CO2

RELAY NO

RELAY NO

Figure 18 Connection of C7262A with CPO-VAV2A

Common

Setpoint

MSTP+

CP-CM

Temperature Sensor

Terminals

MSTP-

24 Vac/dc input

Figure 19 Connection of CP-CM with CPO-VAV2A

24 Vac/dc input

Occupancy

(24Vac input contact)

Temperature Sensor

CP-WM

Terminals

Setpoint

FAN/Bypass

Common

Figure 20 Connection of CP-WM-VAV with CPO-VAV2A

Figure 21 Connection of TR40 and TR42 with CPO-VAV2A

9

TERMINAL SETTINGS

1

A1

1

2

AGND

2

AGND

VAV

3

3

Temp

Terminals

4

4

Set Point

5

5

ByPass/Fan

6

6

LED

7

1

1

A1

2

2

AGND

3

3

AGND

VAV

4

4

Temp

Terminals

5

Set Point

6

ByPass/Fan

7

LED

1

1

AGND

2

2

Temp

VAV

3

3

Set Point

Terminals

4

ByPass/Fan

5

LED

6

1

1

AGND

2

2

Temp

VAV

3

Set Point

Terminals

3

ByPass/Fan

4

LED

5

6

EN1B-0022 IE10 R0717

Spyder® LON programmable VAV controllers are free topology transceiver (FTT) LonMark® compliant trox vav box designed to control HVAC equipment. These controllers provide many options and advanced system features that allow state-of-the-art commercial building control. Each controller is programmable and configurable using the Niagara Framework® software. Spyder LON controllers require the Spyder programmable feature to be licensed in the WEBpro workbench tool and the Webs-AX™ JACE® Controller for programming and downloading. Spyder LON Models are also available as individually licensed controllers (ILC). The ILC versions are identical in design and capability in every detail except for the licensing. The built-in individual licensing of the Spyder ILCs cp-wm-vav honeywell them to be programmed and trox vav box with any brand of the Niagara Workbench or JACE controller. The controllers are for use in variable air volume (VAV) applications. Each controller contains a host microcontroller cp-wm-vav honeywell run the main HVAC application and a second microcontroller for LonWorks® network communications. Each controller provides flexible universal inputs for external sensors, digital inputs, and a combination of analog outputs and digital outputs.

• Uses the Echelon® LonWorks network protocol
• Free topology transceiver (FTT) high-speed 78 kilobit communications network
• Capable of standalone operation, but can also use LonWorks Bus network communications.
• Sylk™ bus for use with Sylk-enabled sensors
• 120 controllers per Q7751A,B Router when configured as a repeater
• Function block engine allows the application designer to program the controller to perform a wide variety of HVAC applications
• Significant event notification, periodic update capability, and failure detect (FD) when network inputs fail to be detected within their configurable time frame
• Built-in zone control functions include a remote wall module interface and a cp-wm-vav honeywell user access to airflow sensor inputs
• All wiring connections are made to removable terminal blocks to simplify controller installation and replacement

• UL/cUL (E87741) Listed under UL916 (Standard for Open Energy Management Equipment) with Plenum Rating
• CSA (LR95329-3) Listed
• Meets FCC Part 15, Subpart B, Class B (Radiated Emissions) Requirements
• Canada: C108.8 (Radiated Emissions)
• EU: EN 61000-6-1; 2001 (EU Immunity), EN 61000-6-3; 2001 (EU Emissions)

cp-wm-vav honeywell is not really hardware specific, and can do petty much anything, to the limits of the programmer's skills. It would bee an absolutely wonderful solution if it wasn't locked down to just the branch guys. We have finally got a good working relationship with our branch, and I have poetry much full control of the system, and am making improvements daily.


Add for your particular problem, you might want to continue the migration to ebi, as it is a good system, and the migration from XBSi is relatively painless. You can then do a slow migration to another hardware. No reason to necessarily stick with a Honeywell vav controller. You're looking at only needing access to a couple points per controller, and EBI has optional licensing for pretty much everything out there(BACNet,LON,N2). That said, Honeywell, asa parent company, make something of just about everything, from alerton bacnet based stuff, Honeywell branded lon stuff, cbus based excellibe, etc. all of which can be brought into EBI, and made to interoperate.