Maverick I Commercial Packaged Rooftop Systems Protocol ......Each data point accessible from a BACnet network is described with a table that gives the Object Identifier, Property

Engineering Data ED 15125-3

Group: Controls

Part Number: ED 15125

Date: July 2013

Supersedes: ED 15125-2

© 2014 Daikin Applied

Maverick I™

Commercial Packaged Rooftop Systems

Protocol Information

BACnet® Networks

LONWORKS® Networks

2

2 ED 15125-3

Table of Contents

Table of Contents ........................................................................... 2 Revision History ........................................................................................... 3 Reference Documents ................................................................................... 3 Notice ........................................................................................................... 4 Limited Warranty ......................................................................................... 4 Introduction .................................................................................... 5 Unit Controller Data Points .......................................................................... 5 Protocols Supported ..................................................................................... 5 Basic Protocol Information ............................................................ 6 Setting Network Communication Parameters ............................................... 6 BACnet Networks ........................................................................................ 6 Unit Controller Device Object ...................................................................... 7 BACnet Network Integration ........................................................................ 8 LONWORKS Networks ................................................................................ 10 Minimum Integration Requirments .............................................. 14 Set up the Unit Controller for Network Control ......................................... 14 Display Important Data Points.................................................................... 14 Network Off ............................................................................................... 14 Network Occupancy Scheduling ................................................................ 14 Unit Controller Sequence of Operation ...................................................... 14 Comprehensive Data Point Tables .............................................. 15 BACnet Standard Objects ........................................................................... 15 LONWORKS Variables ................................................................................ 17 Detailed Data Point Information .................................................. 20 Application Mode ....................................................................................... 20 Cooling Capacity ........................................................................................ 22 Discharge Air Temperature ........................................................................ 23 Economizer Capacity ................................................................................. 23 Effective Setpoint ....................................................................................... 23 Local Space Temperature Setpoint ............................................................. 24 Room Sensor Setpoint Enable .................................................................... 24 Emergency Override ................................................................................... 25 Indoor Fan Occupancy ............................................................................... 26 Heating Capacity Primary .......................................................................... 27 Heating Capacity Secondary ...................................................................... 27 Local OA Temperature ............................................................................... 27 Local Space Temperature ........................................................................... 28 Minimum Send Time .................................................................................. 28 Object Request ........................................................................................... 28 Object Status .............................................................................................. 30 Effective Occupancy .................................................................................. 31 Occupancy Mode (Occupany Schedule Override) ...................................... 32 Occupancy Schedule .................................................................................. 33 Occupancy Schedule Override Setpoint ..................................................... 34 Occupied Cooling Setpoint ......................................................................... 35 Occupied Heating Setpoint ......................................................................... 36 Effective Outdoor Air Temperature ............................................................ 36 Remote Outdoor Air Temperature .............................................................. 37

Receive Heartbeat ...................................................................................... 37 Return Air Temperature ............................................................................. 38 Return/Exhaust Fan Capacity ..................................................................... 38 Send Heartbeat ........................................................................................... 39 Communication Module Software Version ................................................ 39 Application Version ................................................................................... 39 Integrated Furnace Controller Software Version ........................................ 40 Honeywell Economizer Software Version .................................................. 40 Location ..................................................................................................... 40 Local Space CO2 ........................................................................................ 41 Remote Space IAQ ..................................................................................... 41 Effective Space Temperature...................................................................... 42 Remote Space Temperature ........................................................................ 42 Effective Supply Fan Capacity ................................................................... 42 Economizer Enable .................................................................................... 43 Demand Control Ventilation Limit ............................................................. 44 Ventilation Limit ........................................................................................ 44 Space CO2 High Limit Setpoint ................................................................. 45 Exhaust On/Off Setpoint ............................................................................ 45 Remote Space Temperature Spt Adjust ...................................................... 46 Unit State ................................................................................................... 46 BACnet Unit Support ................................................................................. 48 Unoccupied Cooling Setpoint ..................................................................... 49 Unoccupied Heating Setpoint ..................................................................... 50 Space RH Configuration Setpoint .............................................................. 50 Field Input 1 ............................................................................................... 51 Field Input 2 ............................................................................................... 51 Field Input 2 Configuration ........................................................................ 52 Alarms .......................................................................................... 55 Alarm Table ............................................................................................... 55 Alarm Monitoring ...................................................................................... 58 Alarm Clearing ........................................................................................... 59 Objects ....................................................................................................... 59 BACnet Device Management ....................................................... 61 DeviceCommunicationControl - Disable .................................................... 61 DeviceCommunicationControl - Enable ..................................................... 61 ReinitializeDevice (Reset) .......................................................................... 61 Appendix A: Protocol Implementation Conformance Statement (PICS) .................................................. 62 BACnet Protocol Implementation Conformance Statement ....................... 62 Product Description .................................................................................... 62 BACnet Standardized Device Profile ......................................................... 62 Standard Object Types Supported .............................................................. 63 Data Link Layer Options ............................................................................ 63 Segmentation Capability ............................................................................ 63 Device Address Binding ............................................................................. 63 Networking Options ................................................................................... 64 Character Sets Supported ........................................................................... 64

ED 15125-2 3

Revision History ED15125 April 2010 Preliminary release.

ED15125-1 September 2010 - Corrected discrepancy with Occ Mode to match detailed data section.

ED15125-2 November 2012 - Changed Control Temperature Alarm from a Problem (195) to a fault (244).

- Alarms that are not recognized by the communication boards are now passed through

instead of sending alarm 1.

- Added a network point to allow the network to command the indoor fan to either 1) run

in continuous mode, 2) cycle on only when in heating or cooling or 3) run continuously

when in occupied and cycle when unoccupied.

- Added network points for two field inputs that are located on the unit control board.

Field input 1 is always a temperature. The unit type for Field input 2 is configurable.

The value from the unit control is always a voltage from 0 to 10 volts. It can be

configured for one of five unit types. It includes configurations for the unit type, low

range and high range.

- Updated wording in Economizer Enable section and added an enumeration to disable

all economizer functionality. This was done to support a change in the unit control. The

unit control now supports Disabled Free Cooling, Enabled Free Cooling or Disable all

Economizer Functionality.

- Added a network point for the Space Relative Humidity Configuration Setpoint.

-Fixed reference to OM 1077 in Reference Docs table

-Updated Daikin logo and associated references.

- Corrected an error in the description of which BACnet object numbers are needed to

clear all and clear one alarm. The object numbers in the table of the same section and of

the main table were correct.

ED15125-3 July 2013 - change definition of nviIndoorFanOcc in document from SNVT_state to UNVTIndoorFanOcc.

The software didn’t change.

Reference Documents Number Company Title Source

078-0014-01E LONMARK Interoperability

Association

LONMARK Layers 1-6 Interoperability Guidelines,

Version 3.4

www.lonmark.org

078-0120-01E LONMARK Interoperability

Association

LONMARK Application Layer Interoperability

Guidelines, Version 3.4

www.lonmark.org

078-0156-01G Echelon® Corporation LONWORKS® FTT-10A Free Topology Transceiver

Users Guide

www.echelon.com

8500_20 LONMARK Interoperability

Association

Space Comfort Controller Functional Profile www.lonmark.org

OM 1077 Daikin Applied Unit Controller Operation Manual –Maverick I

Commercial Rooftop Systems www.DaikinApplied.com

ED 15126 Daikin Applied Maverick I Unit Controller Protocol Conformance

Implementation Statement (PICS) - BACnet

www.DaikinApplied.com

IM 999 Daikin Applied Maverick I Packaged Rooftop Systems- LonWorks

Communication Module Installation Manual


IM 1000 Daikin Applied Maverick I Packaged Rooftop Systems- BACnet

Communication Module Installation Manual


http://www.lonmark.org/


http://www.echelon.com/


http://www.daikinapplied.com/




4 ED 15125-3

Notice © 2012 Daikin Applied, Minneapolis MN. All rights reserved throughout the world

Daikin Applied reserves the right to change any information contained herein without prior notice. The user is responsible

for determining whether this product is appropriate for his or her application.

The following are trademarks or registered trademarks of their respective companies: BACnet from American Society

of Heating, Refrigerating and Air-Conditioning Engineers, Inc. Echelon, LONWORKS, LONMARK, and LonTalk from

Honeywell, Echelon Corporation, Windows from Microsoft Corporation, and Daikin and Maverick I from Daikin Applied.

Limited Warranty Consult your local Daikin Representative for warranty details. Refer to Form 933-430285Y. To find your local Daikin

Representative, go to www.DaikinApplied.com.


ED 15125-2 5

Introduction

This document contains the necessary information you need to incorporate a Maverick I™

Commercial Packaged Rooftop

(Model MPS) into your building automation system. It lists all BACnet® properties, LONWORKS

® variables, and

corresponding unit Controller data points. It also contains the BACnet Protocol Implementation Conformance Statement

(PICS). BACnet and LONWORKS terms are not defined. Refer to the respective specifications for definitions and details.

Unit Controller Data Points The Maverick I Rooftop Unit Controller (RTU-C) contains data points or unit variables that are accessible from four user

interfaces: the unit keypad, BACnet IP, BACnet Ethernet, BACnet MS/TP or a LONWORKS network. Not all points are

accessible from each interface. This manual lists all important data points and the corresponding path for each applicable

interface. Refer to the applicable Operation Manual for keypad details. See Reference Documents section for supporting

literature. This manual contains the network details necessary to incorporate the unit Controller into your network.

Protocols Supported The Maverick I Rooftop Unit Controller can be configured in either an interoperable BACnet or LONWORKS network. The

controller must have the corresponding network communication module installed. There are two network communication

modules: one for BACnet and one for LONWORKS. The BACnet module supports BACnet IP, BACnet Ethernet, and

BACnet MS/TP (Master/Slave Token Passing). The LONWORKS module supports the LonMark® SCC (Space Comfort

Controller for rooftop) functional profile.

BACnet Protocol BACnet is a standard communication protocol for Building Automation and Control Networks developed by the American

National Standards Institute (ANSI) and American Society of Heating, Refrigeration and Air-conditioning Engineers

(ASHRAE) specified in ANSI/ASHRAE standard 135-2004. It addresses all aspects of the various systems that are applied

to building control systems. BACnet provides the communication infrastructure needed to integrate products manufactured

by different vendors and to integrate building services that are now independent.

The Maverick I Unit Controller is tested according to the BACnet Testing Laboratory (BTL) Test Plan. It is designed to

meet the requirements of the BACnet Standard (ANSI/ASHRAE 135-2004) as stated in the Protocol Implementation and

Conformance Statement (PICS). However, it is not BTL listed. The PICS is located at the end of this manual.

LONWORKS Networks A control network specification for information exchange built upon the use of LonTalk for transmitting data developed by

the Echelon Corporation.

LonTalk Protocol A protocol developed and owned by the Echelon Corporation. It describes how information should be transmitted between

devices on a control network.

LonMark Certification LonMark certification is an official acknowledgement by the LonMark Interoperability Association that a product

communicates using the LonTalk protocol and transmits and receives data per a standard LonMark functional profile. The

Maverick I Rooftop Unit Controller is LonMark 3.4 certified.

6 ED 15125-3

Basic Protocol Information

Setting Network Communication Parameters Table 1 below describes the network parameters that should be configured so that the unit controller communcates properly

with the BAS. There are various protocol options (BACnet IP/Ethernet, BACnet MS/TP or LONWORKS). Parameters are

set differently depending on which communication module is ordered and shipped with the unit. Table 1 shows the factory

default values.

The BACnet Communicaiton Module (BCM) configuration tool, a web-based user interface, can be used to configure and

address the BACnet parameters shown in Table 1 (See BACnet Communication Module Installation Manual, IM 1000,

available on www.DaikinApplied.com,).

Table 1. Parameter Settings

Parameter Name BACnet IP/Ethernet BACnet MS/TP LONWORKS

IP Address 172.16.5.8 N/A N/A

IP Subnet Mask 255.255.0.0 N/A N/A

UDP Port Number 47808 N/A N/A

IP Router Address (Gateway)

0.0.0.0 N/A N/A

MSTP MAC Address

N/A 0 N/A

MSTP Baud Rate N/A 19200 N/A

Type BACnet IP or BACnet Ethernet

BACnet MS/TP LonWorks

Device Instance Number

47065 3002* N/A

Max Master N/A 1 N/A

Max Info Frames N/A 127 N/A

Max APDU Length

BACnet IP:1024

BACnet Ethernet: 1472

480 N/A

Device Object Name

1

RTU_CXXXXXXXXX RTU_CXXXXXXXXX N/A

*The default Device Instance Number for BACnet MS/TP is 3002 plus the MAC address.

BACnet Networks BACnet Objects Maverick I Rooftop Unit Controllers incorporate standard BACnet object types (i.e., object types defined in the BACnet

Standard) that conform to the BACnet Standard. Each object has properties that control unit variables or data points. Some

object types occur more than once in the Maverick I Rooftop Unit Controller; each occurrence or instance has different

properties and controls different unit variables or data points. Each instance is designated with a unique instance index.

Some properties can be adjusted (read/write properties, e.g., setpoints) from the network and others can only be interrogated

(read-only properties, e.g., status information).

Each data point accessible from a BACnet network is described with a table that gives the Object Identifier, Property

Identifier, Full BACnet Reference or path, and the Name enumeration of the property.

Note: The Maverick I Rooftop Unit Controller has been programmed with a Receive Heartbeat function for certain

BACnet variables. If BACnet has not written to these values before, the Receive Heartbeat timer expires

(default=0.0 seconds) then the variables will revert to either the default or to the value of the attached sensor. The

Receive Heartbeat timer can be changed through the BACnet network. Setting the Receive Heartbeat value to

zero (0) disables this feature.




ED 15125-2 7

Example of BACnet Data Point

BACnet Object Identifier Property

Object Type Type ID Instance Name ID

Binary Value 5 1 Present_Value 85

Full Reference

RTU_C#########.ExhFanState.Present_Value

Enumeration

0 = Off

1 = On

Object Identifier Object Identifiers are each designated with an Object type as defined in the BACnet specification. The first column of the

data point definition gives the object type. This object happens to be Return/Exhaust Fan Status.

The object identifier is a property of the object that you can read from the object. The name of the property is

“Object_Identifier” and the property identifier is 85.

Each object in the Maverick I Rooftop Unit Controller has a unique identifier. BACnet object identifiers are two-part

numbers of BACnet Object Identifier data type. The first part identifies the object type (the first 10 bits of the 32-bit

BACnet Object Identifier [See ANSI/ASHRAE 135-2004 BACnet A Data Communication Protocol for Building

Automation and Control Networks]). The first column of the data point definition gives the object type. The second part

identifies the instances of that particular object type (the last 22 bits of the 32-bit BACnet Object Identifier).

The object identifier is shown in the data points listing as two numbers. The first number is shown in the Type ID column

and designates the Object type enumeration. The second number is shown in the Instance column and designates the

instance of that particular object type.

The object identifier is a property of the object that you can read from the object code. The name of the property is

“Object_Identifier” and the property identifier is 85. The ASHRAE BACnet specification reserves the first 128 numbers for

ASHRAE defined objects. Manufacturers may define additional object types and assign a number above 127 as long as they

conform to the requirements of the ASHRAE BACnet specification.

Each object also has a name. Object names are character strings. The object name is a property of the object that you can

read from the object. The name of the property is “Object_Name” and the property identifier is 77.

Objects are sometimes referred to as an object type and instance number as they are in the BACnet specification. The

example object above would be: Binary Value, Instance 1.

Property Identifier Each object has a number of properties or attributes. Each property has a unique identifier of BACnet Property Identifier

data type. Property identifiers are an enumerated set; a number identifies each member. The Property Identifier enumeration

number is shown in the Property ID column. In the example above the property identifier is 85.

Property Name Each property also has a unique name. Property names are character strings and shown in the Property Name column. In the

example above the property name is Present Value.

Full Reference The full reference is the path of the property within the network where the Maverick I Rooftop Unit Controller resides. It is

a character string equivalent to the object identifier and the property identifier. In the example above the full reference is

RTU_C#########.FanOutput.Present Value.

Enumerated Values Some properties are standard data types and some are enumerated sets. If the property value is an enumerated set, all

enumerated values and corresponding meaning are given in the Enumeration column of the data point listing.

Unit Controller Device Object Each BACnet compatible device must have one and only one BACnet Device Object.

Device Object Identifier The Maverick I Rooftop Unit Controller Device Object Identifier uniquely specifies the unit within the network. The device

object type for all devices is fixed by ASHRAE at 8. Therefore the device object instance number must be unique. The

initial Device Object identifier is set at manufacturing. The device object identifier can be read from the Maverick I Rooftop

Unit Controller. The name of the property is “Object_Identifier” and the property identifier is 75. The initial device object

instance number is 3002.

8 ED 15125-3

CAUTION

If another device in the network already has this object identifier (instance number), you must change the instance number of one device object, so that all devices in the network have a unique device identifier.

Device Object Name The device object name specifies a device and must be unique in the network. The device object name for the Maverick I

Rooftop Unit Controller device is RTU_C#########, where ######### is the device instance of the Unit Controller. The

device object name must be unique throughout the entire network. If there are multiple Unit Controllers on the network, the

device object name of each Unit Controller must be changed to have a unique device object name. To make the device

object name unique, change the device instance, which must also be unique on the network. All objects include the device

name and a period “.” (RTU_C#########.) preceding the object name.

The device object name is also available to the network in the device. The property name is “Object_Name” and property

identifier is 77. The device object name can only be made unique by changing the device instance. The RTU_C portion of

the device name can only be changed via the BCM configuration interface (see BACnet Communication Module

Installation Manual, IM 1000 for details).

Device Object Properties The device object contains many other informative properties as shown in Table 2.

Table 2. Maverick I Rooftop Device Object Properties

Property Identifier Value Data Type

Object Identifier 75 BACnetObjectIdentifier

Object Name 77 RTU_C#########. CharacterString

Object Type 79 8 BACnetObjectType

System Status 112

Vendor Name 121 Daikin Applied CharacterString

Vendor Identifier 120 3 Unsigned16

Model Name 70 RTU_C CharacterString

Firmware Version 44 Variable CharacterString

Application Software Revision 12 Variable CharacterString

Location 58 CharacterString

Protocol_Version 98 1 Unsigned

Protocol_Revision 139 4 Unsigned

Protocol_Services_Supported 97 BACnetServicesSupported

Object_List 76 BACnetArray[N] of BACnetObjectIdentifier

Max_APDU_Length_Accepted 62 Variable Unsigned 16

Segmentation_Supported 107 No-Segmentation Unsigned

APDU_Timeout 11 Variable Unsigned

Number_Of_APDU_Retries 73 Variable Unsigned

Device_Address_Binding 30 List of BACnetAddressBinding

Database_Revision 155 1 Unsigned

BACnet Network Integration Access to Properties Object properties are accessible from the network by specifying the device object identifier, object identifier, and the

property identifier. To access a property, you must specify the object identifier including the device object identifier or the

object name including the device object name and the property identifier.

BACnet Communication Module IP Addressing Defaults The BACnet/Internet Protocol (BACnet/IP) address of the BACnet Communication Module for the Maverick I Rooftop

Unit Controller in a BACnet/IP network consists of the four-octet Internet Protocol address followed by the two-octet UDP

(User Datagram Protocol) Port Number. The BACnet/IP address is a six-octet value analogous to a MAC (Media Access

Control) address. The IP address portion of the BACnet/IP address must be unique in the BACnet/IP network segment.

Maverick I Rooftop Unit Controller defaults are:

UDP Port Number: 47808 (BAC0 in hexadecimal)

Internet Protocol Subnet Mask: 255.255.0.0

!

ED 15125-2 9

IP Address: 172.16.5.8.

The BACnet Communication Module supports DHCP (Dynamic Host Configuration Protocol) IP addressing. By

default, this feature is disabled. To configure the BACnet Communication Module to use the DHCP feature, write

0.0.0.0 as the IP address using the BCM Configuration Tool’s web-based user interface.

The Maverick I Rooftop Unit Controller can be incorporated into a BACnet/IP network dedicated to BACnet devices only

or an Ethernet network shared with BACnet devices and other devices.

Shared Ethernet Networks (LAN) Integration Integrating the Maverick I Rooftop Unit Controller into a shared Ethernet LAN requires close cooperation with the network

administrator of the shared Ethernet network. The steps are as follows:

Obtain the IP Subnet Mask of the shared network from the network administrator.

Obtain the static IP Addresses for all Maverick I Rooftop Unit Controllers you are integrating into the shared network.

Obtain the address of an IP Router or Gateway to use for sending IP messages to and from the BACnet IP subnets.

Once you have these, refer to Setting Maverick I Rooftop Unit Controller Communication Parameters in the Basic

Protocol Information section of this document.

The communication type variable must be set to BACnet Ethernet for BACnet communication to take place. The

default value for this property is BACnet IP.

BACnet MS/TP Network Configuration A number of network configurations in the Maverick I Rooftop Unit Controller in a BACnet MS/TP Local Area Network

(LAN) are set via the BACnet Communication Module (BCM) configuration tool, a web-based user interface (See BACnet

Communicaiton Module Installation Manual, IM 1000. Please refer to Setting Maverick I Rooftop Unit Controller

Communication Parameters in the Basic Protocol Information section of this document. Configurations include:

The BACnet MS/TP device address (Media Access Control [MAC] address). The default MAC Address is 0. This

address must be unique and is determined during installation. After you set the MAC address you must cycle power

(turn the controller off and then on again) to the controller in order for the new address to take effect.

The default data transmission rate is set to 19200 bps (baud). If necessary, change the baud rate to 9600, 19200, 38400,

or 76800

The communication type variable must be set to BACnet MS/TP. The default value for this property is BACnet IP.

BACnet Communication LEDs The TX LED appears green when the communicaiton module is transmitting data to the BACnet network. The RX LED

appears green when the communication module is receiving data from the BACnet network. If both LEDs are on

simulatenously, then communication is not established. Table 3 describes the LED activity (See IM 1000 for physical

location of LEDs on the BACnet communication module.)

Table 3. LED Description of BACnet Activity

LED LED Color Description

Modbus TX Green LED flashes when data is being transmitted from the BACnet Communication Module to the unit

controller

Modbus RX Yellow LED flashes when data is being sent to the BACnet Communication from the unit controller

MS/TP TX Green LED flashes when data is being transmitted via the MS/TP network

MS/TP RX Yellow LED flashes when data is received via the MS/TP network

Power Green This LED remains on when power is applied to the BACnet Communication Module

D7 Green Ethernet activity LED

Maverick I Rooftop Unit Controller Configuration The Maverick I Rooftop Unit Controller is ready to operate with the default values of the various parameters. Default

values may be changed with the Maverick I Unit Controller keypad or via the network (See Maverick I Unit Controller OM

1047 for default values and keypad operating instructions.)

Use the BACnet reset button to reset the BACnet addressing and configuration parameters back to factory defaults. Press

and hold the reset button for five seconds to perform this function (see IM 1000 for details.)

10 ED 15125-3

Data Integrity The integrity of some data depends on a valid network connection to maintain current values. The following data points

require valid network updates within the Receive Heartbeat time (if not 0 seconds). If the data points shown in the table

below are not updated within the receive heartbeat time then the Maverick I Rooftop Unit Controller reverts to the default

values of the variable or to the value of the attached sensor. Table 4 defines the effect on BACnet network variables if the

Receive Heartbeat timer should expire without having been updated.

Table 4. Receive Heartbeat Variables and Behavior upon Expiration – BACnet

Data Point BACnet Variable Action when Heartbeat Timer Expires Without Update

Occupancy Scheduler Input OccState Powerup (3)

Application Mode ApplicCmd Auto (5)

Remote Discharge Fan Capacity Setpoint SupFanCapInput Invalid (0x7FFF)

Remote Space Temperature SpaceTempInput Invalid (0x7FFF)

Economizer Enable EconEnable Auto (0xFF)

Space Indoor Air Quality (IAQ) SpaceIAQInput Invalid (0x7FFF)

LONWORKS Networks LONWORKS technology, developed by Echelon

® Corporation, is the basis for LonMark interoperable systems. This

technology is independent of the communications media. The LonMark Interoperable Association has developed standards

for interoperable LONWORKS technology systems. In particular they have published standards for the Space Comfort

Controller (SCC) functional profile. These profiles specify a number of mandatory and optional standard network variables

and standard configuration parameters. This manual defines these variables and parameters available in the Maverick I

Rooftop Unit Controller.

Compatibility The Maverick I Rooftop Unit Controller with the LONWORKS communications module operates in accordance with the SCC

functional profile of the LonMark Interoperability standard.

LONWORKS Communication LEDs Table 5 describes the various LEDs available on the LONWORKS communicaiton module as well as a description of their

function (See IM 999 for physical location of LEDs on the LONWORKS communication module.)

Table 5. LED Description of LONWORKS Activity

LED LED Color Descrption

SRVC Yellow This LED flashes approximately once a second when device is not commissioned. This

LED activates when the Service pin is pressed. Otherwise, this LED is off when the

device is commissioned but the Service pin has not been pressed.

WINK Green Winking is used to identify control on the network. The Wink LED will flash 2

times/second for 5 seconds when control is winking. When not winking, the WINK LED

flashes off for 0.1 second every five seconds. This indicates that the application is

functioning properly.

STAT Green The Status LED flashes when the unit controller transmits a request. When

communicating properly with the unit controller, it flashes 6 times/second or faster. If

communication between the unit controller and communication module is not responding

properly, it flashes slower (approximately once per second) and the error LED will flash.

ERR Red The Error LED flashes when there is a mis-communication between the unit controller

and communication module.

PWR Green The LED remains steady on when power is applied to the communication module.

LONWORKS Variables Maverick I Rooftop Unit Controllers incorporate LONWORKS network variables to access unit data points. The controller

uses LONWORKS Standard Network Variable Types (SNVT) from each profile. Some data points can be adjusted (input

network variables, nvi) (read/write attributes, e.g., setpoints) from the network and others can only be interrogated (output

ED 15125-2 11

network variables, nvo) (read only attributes, e.g., status information). Configuration variables (nci) are included with the

read/write attributes.

Each data point accessible from a LONWORKS network is described with a table that gives the LONWORKS Name, Profile,

SNVT Type, and SNVT Index. If the variable is a configuration variable the table also includes the SCPT Reference and the

SCPT Index.

Example of LONWORKS Data Point LONWORKS Name Profile Uses Heartbeat SNVT Type SNVT Index

nvoLocalOATemp SCC Yes SNVT_temp_p 105

LONWORKS Name

Each network variable has a name that you use to access the data point. This is the name of the variable from the profile. In

the example above the name network variable is nvoLocalOATemp.

Profile

The profile column designates the Maverick I communication module that incorporates this network variable. The variable

itself may not be a standard component of that particular profile, but the communications module does implement and it is

available to the network.

SNVT Type This column gives the name of the standard network variable type from the master list.

SNVT Index This column gives the number of the standard network variable type from the master list.

SCPT Reference This column gives the name of the Standard Configuration Parameter Type (SCPT) from the master list.

SCPT Index This column gives the number of the Standard Configuration Parameter Type (SCPT) from the master list.

Network Considerations

Network Topology

Each Maverick I LONWORKS communicaiton module is equipped with an FTT-10A transceiver for network

communications. This transceiver allows for (1) free topology network wiring schemes using twisted pair (unshielded) cable

and (2) polarity insensitive connections at each node. These features greatly simplify installation and reduce network

commissioning problems. Additional nodes may be added with little regard to existing cable routing.

Free Topology Restrictions

Although free topology wiring is very flexible, there are restrictions (see below). Refer to the Echelon FTT-10A User’s

Guide for details.

1. The maximum number of nodes per segment is 64.

2. The maximum total bus length depends on the wire size:

Wire Size Maximum Node-to-Node Length Maximum Cable Length

24 AWG 820 ft (250 m) 1476 ft (450 m)

22 AWG 1312 ft (400 m) 1640 ft (500 m)

16 AWG 1640 ft (500 m) 1640 ft (500 m)

The longest cable path between any possible pair of nodes on a segment must not exceed the maximum node-to-node

distance. If two or more paths exist between a pair of nodes (e.g., a loop topology), the longest path should be considered.

Note that in a bus topology, the longest node-to-node distance is equal to the total cable length.

1. The total length of all cable in a segment must not exceed the maximum total cable length.

2. One termination is required in each segment. It may be located anywhere along the segment.

12 ED 15125-3

LonWorks Network Addressing

Every Neuron Chip has a unique 48-bit Neuron ID or physical address. This address is generally used only at initial

installation or for diagnostic purposes. For normal network operation, a device address is used.

Device addresses are defined at the time of network configuration. All device addresses have three parts. The first part is the

Domain ID, designating the domain. Devices must be in the same domain in order to communicate with each other. The

second part is the Subnet ID that specifies a collection of up to 127 devices that are on a single channel or a set of channels

connected by repeaters. There may be up to 255 subnets in a domain. The third part is the Node ID that identifies an

individual device within the subnet.

A group is a logical collection of devices within a domain. Groups are assembled with regard for their physical location in

the domain. There may be up to 256 groups in domain. A group address is the address that identifies all devices of the

group. There may be any number of devices in a group when unacknowledged messaging is used. Groups are limited to 64

devices if acknowledged messaging is used. A broadcast address identifies all devices within a subnet or domain.

Commissioning the Network

Pressing the service pin, switch on the LONWORKS Communication Module, generates a service pin message, which

contains the Neuron ID and the program code identification of the node. A service pin message is a network message that is

generated by a node and broadcast on the network. It can be used to commission the LONWORKS network.

A network configuration tool maps device Neuron IDs to the domain/subnet/node logical addressing scheme when it creates

the network image, the logical network addresses and connection information for all devices (nodes) on the network.

External Interface File (XIF) and NXE Files

LonMark guidelines specify exact documentation rules so that proprietary configuration tools are not required to

commission and configure LONWORKS devices. The LONWORKS Communication Module is self-documenting so that any

network management tool can obtain most of the information needed over the network to connect it into the system and to

configure and manage it. An External Interface File (a specially formatted PC text file with an extension .XIF) is also

available so that any network tool can design and configure it prior to installation. The NXE file contains the application

image that is downloaded into the LONWORKS Communicaiton Module. The XIF and NXE files are available on

www.DaikinApplied.com.

Resource Files

Resource Files provide definitions of functional profiles, type definitions, enumerations, and formats that can be used by

network configuration tools such as Echelon’s LonMaker® program. The Maverick I Rooftop Unit Controller supports the

standard SCC functional profile. Additionally, certain Daikin-specific variables are defined for use with the Maverick I

Rooftop Unit Controller. The Resource Files define the format of how these Daikin-specific variables are displayed when

using a tool such as LonMaker. The Resource Files are available on both www.lonmark.org and www.DaikinApplied.com.

Configuring the Unit Controller The Maverick I Rooftop Unit Controller is ready to operate with the default values of the various parameters. Many default

values may be changed with the unit’s keypad or via the network. See the appropriate operation manual for default values

and keypad operating instructions. See Reference Documents section.








ED 15125-2 13

Data Integrity The integrity of some data depends on a valid network connection to maintain current values. The following data points

require a valid network connection if bound. If data points listed in Table 4 are not received within a specified time, then the

controller reverts to local control. In the case of the LONWORKS communciation module, the variables will revert to their

default values.

Table 6. LONWORKS Receive Heartbeat Variables

Data Point LONWORKS Variable Action when Heartbeat Timer Expires Without Update

Occupancy Scheduler Input nviOccSchedule.current_state Powerup (0xFF)

Application Mode nviApplicMode Auto (0x00)

Remote Space Temperature nviSpaceTemp Invalid (0x7FFF)

Outdoor Temperature nviOutdoorTemp Invalid (0x7FFF)

Economizer Enable nviEconEnable Auto (0xFF)

Space Indoor Air Quality (IAQ) nviSpaceIAQ Invalid (0x7FFF)

14 ED 15125-3

Minimum Integration Requirments

Once the Maverick I unit has been integrated into the network, unit operation can then be monitored and controlled via the

BAS. This section provides basic information and outlines a procedure to set up the unit for network control.

Set up the Unit Controller for Network Control A single BACnet or LONWORKS communication module can be field installed on the Maverick I Rooftop Unit Controller.

No communciaiton module is required if the Maverick I unit is operating stand-alone. The unit controller does not require

configuration in order to establish network communication.

Display Important Data Points Typical workstation displays of Maverick I Rooftop Unit Controller attributes include the following significant data points

(page number of detailed description in parenthesis).

Table 7. Significant Data Points

Configuration Temperatures/Pressures Setpoints Clear Alarms

Unit State (46)

Discharge Air Temperature

(23)

Unoccupied Cooling Setpoint (48) Clear Alarms(59)

Application Mode (20) Return Air Temperature (38) Occupied Cooling Setpoint (35)

Effective Occupancy (31) Effective Outdoor Air

Temperature (36)

Occupied Heating Setpoint (36)

Occupancy Mode (32) Unoccupied Heating Setpoint (50)

You can display any number of additional data points based on job requirements or individual preference. See the

LONWORKS Variables section for all available LONWORKS Variables. See the BACnet Standard Objections for all available

BACnet Objects. For a more detailed description of all available data points, see the Detailed Data Point Information

section.

Network Off The unit can be turned off over the network by writing to the (2) Application Mode. Writing AUTO to Application Mode

allows the unit Controller to determine its mode of operation based on input conditions. Writing OFF to Application Mode

shuts down the unit, etc.

The Emergency Override Mode Flag can also be used to shut down the unit from the network.

Network Occupancy Scheduling Using the keypad, set OCCPCY OVERR SP to Network. Schedule unit operation over the network with the Occupancy

Schedule network input. Switching from OCC, UNOCC, BYPASS (TntOvrd), or AUTO commands the unit into the mode

you select.

Unit Controller Sequence of Operation The sequence of operation for a Maverick I Rooftop Unit Controller depends on the control type. Refer to the Maverick I

Unit Controller OM 1047, available on www.DaikinApplied.com, for sequence of operation details.


ED 15125-2 15

Comprehensive Data Point Tables

The following data point tables contain the significant parameters available via the BACnet and LonWorks protocols. There

is a separate table for BACnet objects and LonWorks variables. Network parameters that appear in multiple locations on

the keypad are only listed in the location they first appear on the keypad. Only the items applicable to the specific unit

configuration appear on the keypad menu display.

CAUTION

Please note that anytime a command is written to a network configuration parameter, or to a BACnet object that controls a configuration parameter, this information is stored in the unit controller's EEPROM/FLASH memory. Recognize that writing to the unit controller's EEPROM/FLASH memory is an operation that has a finite limit. For this reason the number of writes made to configuration parameters, or BACnet objects linked to configuration parameters, must be limited in order to avoid damage to the unit controller.

BACnet Standard Objects

Network Control Property

Page

Read Or

Read/Write

Object Type

Instance Description

System

Unit State1. 46 R MSV 15 1=Off, 2=Start, 4=FanOnly, 6=Htg, 7=Econo, 8=Clg

BACnet Unit Support2 48 R/W MSV 16 BACnet network communicates in English or Metric units.

Cooling Capacity 22 R AV 1 cooling capacity (%)

Heating Capacity Primary 27 R AV 2 heating capacity primary (%)

Heating Capacity Secondary 27 R AV 44 heating capacity secondary (%)

Economizer Capacity 23 R AV 15 Feedback value (%)

Effective Supply Fan Capacity 42 R AI 8 Current effective supply fan capacity (%)

Return/Exhaust Fan Capacity 38 R AI 10 Current return or exhaust fan capacity (%)

Application Mode 20 R/W MSV 5 1=Off, 2=HeatOnly, 3=CoolOnly, 4=FanOnly, 5=Auto

Emergency Override 25 R/W MSV 10 1=Normal, 2=Shutdown

Indoor Fan Occupancy2 26 R/W MSV 49 1 = Continous Mode

2 = Cycle On in Heating/Cooling

3 = Continous in Occupied and Cycle in Unoccupied

Occupancy

Effective Occupancy 31 R MSV 6 1=Occ, 2=Unocc, 3=TntOvrd

Occupancy Schedule

33 R/W MSV 8 .current_state: 1=Occ, 2=Unocc, 3=NUL (Powerup)

“Next State” field NOT USED

“Time To Next State” field NOT USED

Occupancy Mode 32 R/W MSV 7 1=Occ, 2=Unocc, 3=TntOvrd, 4=NUL(Auto)

Occupancy Schedule Override

Setpoint2

34 R/W AV 3 Used when Occupancy Mode is set to Standby. This is the amount of

time that the unit operates in the Bypass mode.

Temperature

Effective Space Temperature 42 R AI 3 Current effective space temperature.

Local Space Temperature 28 R AV 4 Current reading of the local sensor

Remote Space Temperature 42 R/W AV 28 Network input of Space Temp

Effective Outdoor Air Temperature 36 R AI 4 Current effective temperature being used.

Local OA Temperature 27 R AV 5 Current reading of the local sensor

Remote Outdoor Air Temperature 37 R/W AV 29 Network input of Outdoor Air Temp (–10°C to 50°C)

Discharge Air Temperature 23 R AI 1 Current reading of sensor

Return Air Temperature 38 R AI 2 Current reading of sensor

Space Temperature Setpoints

Effective Setpoint 23 R AV 50 Current enable setpoint which the unit will use.

Local Space Temperature Setpoint 24 R AV 51 Current reading of the local space sensor

Room Sensor Setpoint Enable2 24 R/W BV 65 Enable the use of the local hardwired setpoint adjustment

Remote Space Temperature Spt

Adjust 46 R/W AV 56

!

16 ED 15125-3


Page

Read Or

Read/Write

Object Type

Instance Description

Occupied Cooling Setpoint2 35 R/W AV 9 Occupied Cooling Setpoint

Occupied Heating Setpoint2 36 R/W AV 11 Occupied Heating Setpoint

Unoccupied Cooling Setpoint2 48 R/W AV 10 Unoccupied Cooling Setpoint

Unoccupied Heating Setpoint2 50 R/W AV 12 Unoccupied Heating Setpoint

Economizer

Economizer Enable 43 R/W MSV 32 1 = Disable Free Cooling, Enable Ventilation

2 = Enable Free Cooling, Enable Ventilation

3 = Auto (unit control decides)

4 = Disable All Economizer Functionality

Demand Control Ventilation

Limit2

44 R/W AV 53 Sets the minimum position setpoint when CO2 override control is used.

Ventilation Limit2 44 R/W AV 54 Sets the maximum position setpoint when CO2 override control is

used.

Local Space CO2 41 R AI 13 This variable provides the concentration of CO2 in the space (PPM).

Remote Space IAQ 41 R/W AV 31 This input may be set by the network and is used for minimum OA

damper control (500-2000 PPM).

Space CO2 High Limit Setpoint2 45 R/W AV 48 500-2000ppm

Exhaust On/Off Setpoint2 45 R/W AV 55 0-100%

Dehumidification

Space RH Configuration Setpoint 2

50 R/W AV 65 This is the configuration setpoint used for dehumidification.

Field Inputs

Field Input 1 50 R AV 61 This is the value from the unit controls field input 1. Field Input 1 is

always a temperature value.

Field Input 2 51 R AV 62 This is the value from the unit controls field input 2. The unit type, low

range and high range are all configurable.

Field Input 2 Low Volt Range2 52 R AV 63 This configures the low voltage range for the value from the unit

controls field input 2.

Field Input 2 High Volt Range2 52 R AV 64 This configures the high voltage range for the value from the unit

controls field input 2.

Alarm Handling

Current Alarm 60 R AV 27 See the Alarm Table.

Clear All Alarms 59 R/W BV 66 Clears all active alarms.

Clear One Alarm 59 R/W AV 57 Clears the alarm that corresponds to the value entered.

Device Management

Receive Heartbeat2 37 R/W AV 43

Communication Module Software Version

39 R Device 8

Application Version 39 R Device 8 Application_Software_Version property of device object.

Integrated Furnace Controller

Software Version

40 R AV 45

Honeywell Economizer Software

Version

40 R AV 46

Location 2 40 R Device 8 Sets descriptive physical location information for the associated

functional block or device

1. When the keypad display menu item “Unit State” is in Standby mode, the corresponding BACnet property “Unit

Property” displays “Off” from the BAS. 2.

Parameter is stored in EEPROM/FLASH in either the communication module or in the unit controller. Writes to

this parameter must be limited.

ED 15125-2 17

LONWORKS Variables The following table contains the significant variables available via the LONWORKS protocol. Parameters that appear in

multiple locations on the keypad are only listed in the location they first appear on the keypad. Only the items applicable to

the specific unit configuration appear on the keypad menu display.

CAUTION



Variable Name Page

SNVT/SCPT Index

Description

System

Unit State1. nvoUnitStatus 46 112 1=HEAT, 3=COOL, 6=OFF, 9=FAN_ONLY,

10=ECONMY, 14=DEHUMID, 0xFF=NUL

Cooling Capacity nvoUnitStatus 22 112 nvoUnitStatus.cool_output(%)

Heating Capacity Primary nvoUnitStatus 27 112 nvoUnitStatus.heat_output_primary(%)

Heating Capacity Secondary nvoUnitStatus 27 112 nvoUnitStatus.heat_output_secondary(%)

Economizer Capacity nvoUnitStatus 23 112 nvoUnitStatus.econ_output (%)

Effective Supply Fan Capacity nvoUnitStatus 42 112 Current effective supply fan capacity (%)

nvoUnitStatus.fan_output (%)

Return/Exhaust Fan Capacity nvoExhFanStatus 38 95 .value Current return or exhaust fan capacity (%)

Application Mode nviApplicMode 20 108 0=AUTO, 1=HEAT, 3=COOL, 6=OFF,

9=FAN_ONLY, 0xFF=NUL

Emergency Override nviEmergOverride 25 103 0=NORMAL, 4=SHUTDOWN (other states not used)

Indoor Fan Occupancy2 nviIndoorFanOcc 26 95 0 = Continous Mode



Occupancy

Effective Occupancy nvoEffectOccup 31 109 0=OCCUPIED, 1=UNOCCUPIED, 2=BYPASS,

3=STANDBY, 0xFF=NUL

Occupancy Schedule nviOccSchedule 33 128 nviOccSchedule.current_state

0=OCCUPIED, 1=UNOCCUPIED, 0xFF=NUL

(Powerup)

Occupancy Mode nviOccManCmd 32 109 0=OCCUPIED, 1=UNOCCUPIED, 2= BYPASS,

0xFF=NUL (AUTO)


Setpoint2

nciBypassTime 34 107/34 Used when nviOccManCmd is set to Standby.The

amount of time that the unit operates in the Bypass

mode

Temperature

Effective Space Temperature nvoSpaceTemp 42 105 Current effective space temperature.

Local Space Temperature nvoLocalSpaceTmp 28 105 Current reading of the local space sensor

Remote Space Temperature nviSpaceTemp 42 105 Network input of Space Temp

Effective Outdoor Air Temperature nvoOutdoorTemp 36 105 Current effective temperature being used.

Local OA Temperature nvoLocalOATemp 27 105 Current reading of the local outdoor air temperature

sensor

Remote Outdoor Air Temperature nviOutdoorTemp 37 105 Network input of Outdoor Air Temp

Discharge Air Temperature nvoDischAirTemp 23 105 Current reading of sensor

Return Air Temperature nvoRATemp 38 105 Current reading of sensor

Space Temperature Setpoints

Effective Setpoint nvoEffectSetpt 23 105 Current enable setpoint which the unit will use.

Local Space Temperature Setpoint nvoSetpoint 24 105 Local setpoint output

Room Sensor Setpoint Enable2 UCPTlocalSptEnable 24 95 Enable the use of the local hardwired setpoint

!

18 ED 15125-3


Variable Name Page

SNVT/SCPT Index

Description

adjustment

Remote Space Temperature Spt Adjust nviSetpoint 46 105 Adjusts effective heat enable and effective cool enable

setpoint via the network. Effective Heat SP = nviSetpoint – 0.5 (Occupied_Cool

– Occupied_Heat).

Effective Cool SP = nviSetpoint + 0.5 (Occupied_Cool – Occupied_Heat).

Occupied Cooling Setpoint2 nciSetpoints

SCPTsetPnts 35 106/60 Occupied Cooling Setpoint

Occupied Heating Setpoint2 nciSetpoints

SCPTsetPnts 36 106/60 Occupied Heating Setpoint

Unoccupied Cooling Setpoint2 nciSetpoints

SCPTsetPnts 48 106/60 Unoccupied Cooling Setpoint

Unoccupied Heating Setpoint2 nciSetpoints

SCPTsetPnts

50 106/60 Unoccupied Heating Setpoint

Economizer

Economizer Enable nviEconEnable 43 95 Enables/disables economizer functionality via the [state,

value] field.

[0, 200] = Disable All Economizer Functionality

[0, 0..199] = Disable Free Cooling, Enable Ventilation

[1, n/a] = Enable Free Cooling, Enable Ventilation

[-1,n/a] =Auto (unit control decides)

Demand Control Ventilation Limit2 nviMinVentLim 44 81 Sets the minimum position setpoint when CO2 override

control is used.

Ventilation Limit2 nviMaxVentLim 44 81 Sets the maxnimum position setpoint when CO2

override control is used.

Local Space CO2 nvoSpaceCO2 41 29 0-2000ppm

Remote Space IAQ nviSpaceIAQ 41 29 This input may be set by the network and is used for

minimum OA damper control (0-2000 PPM).

Space CO2 High Limit Setpoint2 nciSpaceCO2Lim 45 29 0-2000ppm

Exhaust On/Off Setpoint2 nciExhaustSpt 45 81 0-100%

Dehumidification

Space RH Configuration Setpoint2 nviSpaceRHSetpt 50 36 This is the configuration setpoint used for

dehumidification.

Field Inputs

Field Input 1 nvoFieldInput1 50 105 This is the value from the unit controls field input 1.

It’s always a temperature value.

Field Input 2 nvoFieldInput2 51 81 This is the value from the unit controls field input 2.

The SNVT type is configurable using nciField2Type.

Configurable Input 2 Type2 UCPTfieldInput 52 N/A This configures low range and high range for

nvoFieldInput2.

Alarm Handling

Current Alarm nvoUnitStatus 60 112 nvoUnitStatus.in_alarm. See the Alarm Table.

Clear All Alarms nviClearAllAlarm 59 8 Clears all clearable active alarms.

Clear One Alarm nviClear1Alarm 59 8 Clears the clearable active alarm that corresponds to the

value entered.

Device Management

Receive Heartbeat2 nciRcvHrtBt

SCPTmaxRcvTime 37 107/48

Send Heartbeat2 nciSndHrtBt

SCPTmaxSendTime 39 107/49

Minimum Send Time2 nciMinOutTm

SCPTminSendTime 28 107/52 Defines min period of time between automatic network

variable output time (reducing traffic on network)

Communication Module Software Version

UCPTcommDevMajVer &

UCPTcommDevMinVer

39 165 and 166 Device Majorand minor Version Numbers

Application Version UCPTunitDevMajVer &

UCPTunitDevMinVer

39 165 and 166

ED 15125-2 19


Variable Name Page

SNVT/SCPT Index

Description

Integrated Furnace Controller Software

Version

UCPTifcDevMajVer &

UCPTifcDevMinVer

40 165 and 166

Honeywell Economizer Software

Version

UCPTeconDevMajVer

& UCPTeconDevMinVer

40 165 and 166

Location2 (nciLocation) 40 36/17 Sets descriptive physical location information for the

associated functional block or device

Object Status nvoStatus 30 92 This variable is part of the Node Object and reports the

status of the requested functional block in the device.

Object Request nviRequest 28 93 This variable is part of the Node Object and requests a

particular mode for a particular funcational block in the

device. Only the required RQ_NORMAL, RP_UPDATE_STATUS AND RQ_REPORT_MASK

are implemented.

1. When the keypad display menu item “Unit State” is in Standby mode, the corresponding LONWORKS variable “Unit

Property” displays “Off” from the BAS. 2.

Parameter is stored in EEPROM/FLASH in either the communication module or in the unit controller. Writes to

this parameter must be limited.

20 ED 15125-3

Detailed Data Point Information

The data points or properties (attributes) defined in this section reference data that is generated in the Maverick I Rooftop

Unit Controller. Table 8 below defines the differences among versions of both BACnet and LonWorks communication

modules. It also indicates the compatible versions of Maverick I unit controller and communication module software.

Table 8. BACnet and LonWorks Software Version History

BACnet Object

BACnet Software Version

LonWorks Variable

LonWorks Software Version

Compatible Unit

Controller

Software Version

Description (Function)

MSV

49 2.00 nviIndoorFanOcc 2.00 1.5+

Added a network point to allow the network to

command the indoor fan to either 1) run in

continuous mode, 2) cycle on only when in heating

or cooling or 3) run continuously when in occupied

and cycle when unoccupied.

AV 61

2.00 nvoFieldInput1 2.00 1.5+ Added a network point that reports a value from the

unit controls field input 1. This point is always a

temperature value.

AV 62

2.00 nvoFieldInput2 2.00 1.5+ Added a network point that reports a value from the

unit controls field input 2. The unit type is

configurable.

AV 63 2.00 - - 1.5+ Added a network point that configures the low

range for nvoFieldInput2.

AV 64 2.00 - - 1.5+ Added a network point that configures the high

range for nvoFieldInput2.

- - UCPTfieldInput 2.00 1.5+ Added a network point that configures the low

range and high range for nvoFieldInput2.

MSV

32

2.00 nviEconEnable 2.00 2.1+ Added an enumeration to the network point that

disable all economizer functionality. The unit

control now supports Disabled Free Cooling,

Enabled Free Cooling or Disable all Economizer

Functionality

AV 65 2.00 nviSpaceRHSetpt 2.00 1.5+ Added a network point that can set the Space

Relative Humidity Configuration Setpoint.

Application Mode Keypad Menu Path Effective Occupancy /Occupied Mode

This read/write attribute sets the unit in an application mode. In any type of operating environment, if the Application Mode

is set to “Off”, the rooftop unit will be turned off and remain off. In the unit controller, this setting has priority over any

other setting or source of occupancy. When operating in a communicating environment, Application Mode must be set to

Auto, Fan Only, Heat Only or Cool Only. Additionally, the keypad can set the Application Mode to Control By

Thermostat. In this mode the network occupancy parameters are ignored.

Measurement Units Data Type Valid Range Uses Heartbeat Default Value

Mode N/A Unsigned Enumerated Yes Auto

ED 15125-2 21



Multi-State Value 19 5 Present_Value 85

Full Reference

RTU_C#########.ApplicCmd.Present_Value

Enumeration

1 = Off

2 = Heat

3 = Cool

4 = Fan Only

5 = Auto

LONWORKS LONWORKS Name Profile Uses Heartbeat SNVT Type SNVT Index

nviApplicMode DAC, SCC Yes SNVT_hvac_mode 108

Enumeration Definitions Value Identifier Notes

0 HVAC_AUTO Controller automatically changes between application modes

1 HVAC_HEAT Heating only 0

2 HVAC_MRNG_WRMUP Not supported – reverts to HVAC_AUTO

3 HVAC_COOL Cooling only

4 HVAC_NIGHT_PURGE Not supported – reverts to HVAC_AUTO

5 HVAC_PRE_COOL Not supported – reverts to HVAC_AUTO

6 HVAC_OFF Controller not controlling outputs

7 HVAC_TEST Not supported – reverts to HVAC_AUTO

8 HVAC_EMERG_HEAT Not supported – reverts to HVAC_AUTO

9 HVAC_FAN_ONLY Air not conditioned, fan turned on

10 HVAC_FREE_COOL Not supported – reverts to HVAC_AUTO

11 HVAC_ICE Not supported – reverts to HVAC_AUTO

12 HVAC_MAX_HEAT Not supported – reverts to HVAC_AUTO

13 HVAC_ECONOMY Not supported – reverts to HVAC_AUTO

14 HVAC_DEHUMID Not supported – reverts to HVAC_AUTO

15 HVAC_CALIBRATE Not supported – reverts to HVAC_AUTO

16 HVAC_EMERG_COOL Not supported – reverts to HVAC_AUTO

17 HVAC_EMERG_STEAM Not supported – reverts to HVAC_AUTO

0xFF HVAC_NUL Powerup

22 ED 15125-3

Enumeration Correspondence

BACnet LONWORKS

5 Auto 0 HVAC_AUTO

2 Heat Only 1 HVAC_HEAT

2 Heat Only 2 HVAC_MRNG_WRMUP (not used)

3 Cool Only 3 HVAC_COOL

3 Cool Only 4 HVAC_NIGHT_PURGE (not used)

3 Cool Only 5 HVAC_PRE_COOL (not used)

1 Off 6 HVAC_OFF

5 Auto 7 HVAC_TEST (not used)

2 Heat Only 8 HVAC_EMERG_HEAT (not used)

4 Fan Only 9 HVAC_FAN_ONLY

3 Cool Only 10 HVAC_FREE_COOL (not used)

5 Auto 11 HVAC_ICE (not used)

5 Auto 12 HVAC_MAX HEAT (not used)

6 Econo 13 HVAC_ECONOMY (not used)

7 Dehumid 14 HVAC_ DEHUMID (not used)

5 Auto 15 HVAC_CALIBRATE (not used)

5 Auto 16 HVAC_EMERG_COOL (not used)

5 Auto 17 HVAC_EMERG_STEAM (not used)

5 Auto 0xFF HVAC_NUL

1 Writing a state that is not used, causes the controller to control as if Auto was selected.

Cooling Capacity Keypad Menu Path Unit Status/Capacity Cooling

This read-only property indicates the current percentage of unit maximum cooling capacity.

The BACnet property only applies to the subject data point. The LONWORKS variable covers six other data points: Unit

State, Heating Capacity Primary, Heating Capacity Secondary, Effective Supply Fan Capacity, Economizer Capacity, and In

Alarm.

Measurement Units Data Type Valid Range Default Value

Percent % Real

LONWORKS: Structure

0-100% N/A



Analog Value 2 1 Present_Value 85

Full Reference

RTU_C#########. CoolOutput.Present_Value


nvoUnitStatus.cool_output SCC Yes SNVT_hvac_status 112

ED 15125-2 23

Discharge Air Temperature Keypad Menu Path Temperaure/Disch Air Temp

This read-only property indicates the current reading of the unit discharge air temperature sensor.


Temperature °F / °C Real -40.0°C…80.0°C

-40.0°F…176.0°F

N/A



Analog Input 0 1 Present_Value 85

Full Reference

RTU_C#########.DischAirTemp.Present_Value


nvoDischAirTemp DAC, SCC Yes SNVT_temp_p 105

Economizer Capacity Keypad Menu Path Economizer/Eff.Eco.Position

This read-only attribute indicates the current economizer capacity.

The BACnet property reads only the subject attribute; however the LONWORKS variable is only a part of the LONWORKS

Unit Status network variable. See Unit State for details of LONWORKS network variable.

The BACnet property only applies to the subject data point. The LONWORKS variable covers six other data points: Unit

State, Cooling Capacity, Heating Capacity Primary, Heating Capacity Secondary, Effective Supply Fan Capacity, and In

Alarm.


Percent Percent Real

LONWORKS: Structure

0…100% N/A




Full Reference

RTU_C#########.EconOutput.Present_Value

LonWorks LONWORKS Name Profile Uses Heartbeat SNVT Type SNVT Index

nvoUnitStatus.econ_output DAC, SCC Yes SNVT_hvac_status 112

Effective Setpoint Keypad Menu Path SetPoints /Eff. Temp. SP

This read-only attribute monitors the effective temperature setpoint. It is always set equal to the current controlling setpoint

(that was last calculated) depending on the current unit operating state (i.e. cooling or heating).

The Effective Setpoint Output depends on the Occupied Cooling Setpoint, the Occupied Heating Setpoint, and Temperature

Setpoint Input. If the Temperature Setpoint Input (nviSetpoint) is set to a valid value:

Effective Cooling Enable Setpoint = Temperature Setpoint Input

+½(Occupied Cooling Enable Setpoint–Occupied Heating Enable Setpoint)

Effective Heating Enable Setpoint = Temperature Setpoint Input

-½(Occupied Cooling Enable Setpoint–Occupied Heating Enable Setpoint)

The Effective Setpoint Output (nvoEffectSetpt) equals Effective Heating Enable Setpoint when the control temperature is

less than Occupied Heating Enable Setpoint + [1/2(Occupied Cooling Enable Setpoint–Occupied Heating Enable Setpoint)]. It is

24 ED 15125-3

set equal to the Effective Cooling Enable Setpoint when the control temperature is greater than the Occupied Cooling Enable Setpoint –

[1/2(Occupied Cooling Enable Setpoint–Occupied Heating Enable Setpoint)].

If the Temperature Setpoint Input (nviSetpoint) is set to an invalid value:

Effective Cooling Enable Setpoint = Occupied Cooling Enable Setpoint

Effective Heating Enable Setpoint = Occupied Heating Enable Setpoint


Temperature °F / °C Real 5.0°C…35.0°C

40.0°F…95.0°F

N/A




Full Reference

RTU_C#########.EffectSetpt.Present_Value

LONWORKS LONWORKS Name Profile Uses Heartbeat SNVT Type Number

nvoEffectSetpt SCC Yes SNVT_temp_p 105

Local Space Temperature Setpoint Keypad Menu Path Setpoints/Setpoint Adjust.

This read-only attribute monitors the local temperature setpoint. It is always set equal to the current local setpoint.


Temperature °F / °C Real 10.0°C…35.0°C

50.0°F…95.0°F

NA




Full Reference

RTU_C#########.Setpoint.Present_Value

LONWORKS LONWORKS Name Profile Uses Heartbeat SNVT Type Number

nvoSetpoint SCC Yes SNVT_temp_p 105

Room Sensor Setpoint Enable Keypad Menu Path Setpoints/Setpoint Adj Enable

This read/write property is used to enable or disable the local hardwired setpoint adjustment mounted on the room sensor.

CAUTION


!

ED 15125-2 25


State NA Unsigned Enumerated Enabled



Binary Value 5 65 Present Value 85

Full Reference

RTU_C#########.LocSetptEnable.Present_Value

LONWORKS LONWORKS Name Profile SNVT Type SNVT Index UCPT Reference

UCPTlocalSptEnable SCC n/a n/a UCPTlocalSptEnable

Valid Range

value Room Sensor Setpoint Enable

0 Remote (Disabled)

1 Local (Enabled)

Emergency Override This read/write property shuts off the Maverick I Rooftop Unit Controller. If this property is set to Shutdown, the Maverick

I Rooftop Unit Controller cannot start based on a time clock or any other means. The only way to start the Maverick I

Rooftop Unit Controller is to change the value to Normal.

If a value other than EMERG_SHUTDOWN (4), is written, this variable reverts back to 0.


N/A N/A Unsigned Enumerated No Normal




Full Reference

RTU_C#########.EmergOverride.Present_Value

Enumeration

1 = Normal

2 = Shutdown


nviEmergOverride DAC, SCC No SNVT_hvac_emerg 103

Enumeration Definitions

Value Identifier Notes

0 EMERG_NORMAL No emergency mode

1 EMERG_PRESSURIZE Emergency pressurize mode (not used)

2 EMERG_DEPRESSURIZE Emergency depressurize mode (not used)

3 EMERG_PURGE Emergency purge mode (not used)

4 EMERG_SHUTDOWN Emergency shutdown mode

5 EMERG_FIRE (not used)

0xFF EMERG_NUL Value not available

26 ED 15125-3


BACnet Lon

1 Normal 0 EMERG_NORMAL

1 Normal 1 EMERG_PRESSURIZE

1 Normal 2 EMERG_DEPRESSURIZE

1 Normal 3 EMERG_PURGE

2 Shutdown 4 EMERG_SHUTDOWN

1 Normal 5 EMERG_FIRE

1 Normal 0xFF EMERG_NUL

Indoor Fan Occupancy Keypad Menu Path Mode / Indoor Fan Mode

Depending on the occupancy, this read/write property controls the cycling of the indoor fan. It can be set to run in

continous mode, cycle on only when in heating/cooling or run continuously when in occupied and cycle in unoccupied.

CAUTION



N/A N/A Unsigned Enumerated No Unit control

value




Full Reference

RTU_C#########.IndoorFanOcc.Present_Value

Enumeration

1 = Continous Mode



LONWORKS LONWORKS Name Profile Uses Heartbeat UNVT Type SNVT Index

nviIndoorFanOcc No UNVTIndoorFanOcc 95


nviIndoorFanOcc Identifier Notes

0 INDOORFAN_CONT Continous Mode

1 INDOORFAN_CYCLE Cycle On in Heating/Cooling

2 INDOORFAN_CONT_IN_OCC Continous in Occupied and Cycle in Unoccupied


BACnet LONWORKS

1 Continous Mode 0 INDOORFAN_CONT

2 Cycle On in Heating/Cooling 1 INDOORFAN_CYCLE

3 Continous in Occupied and Cycle in Unoccupied 2 INDOORFAN_CONT_IN_OCC

!

ED 15125-2 27

Heating Capacity Primary Keypad Menu Path Unit Status/CAPY:Prim/Sec

This read-only attribute indicates the current percentage of unit primary maximum heating capacity.

The BACnet property reads only the subject attribute and only applies to the subject data point.

The LONWORKS variable is only a part of the LONWORKS Unit Status network variable. See Unit State for details of

LONWORKS network variable. The LONWORKS variable covers six other data points: Unit State, Effective Supply Fan

Capacity, Secondary Heating Capacity, Economizer Capacity, and In Alarm.


Heating Capacity

Primary

Percent BACnet: Real

LonWorks: Structure

0.0…100.0% N/A




Full Reference

RTU_C#########.HeatOutput.Present_Value

LONWORKS LonWorks Name Profile Uses Heartbeat SNVT Type SNVT Index

nvoUnitStatus.heat_output_primary DAC, SCC Yes SNVT_hvac_status 112

Heating Capacity Secondary Keypad Menu Path Unit Status/CAPY:Prim/Sec

This read-only attribute indicates the current percentage of unit secondary maximum heating capacity.



LONWORKS network variable. The LONWORKS variable covers six other data points: Unit State, Effective Supply Fan

Capacity, Secondary Heating Capacity, Economizer Capacity, and In Alarm.


Heating Capacity

Secondary

Percent BACnet: Real

LonWorks: Structure

0.0…100.0% N/A




Full Reference

RTU_C#########.HeatOutputSec.Present_Value

LONWORKS LonWorks Name Profile Uses Heartbeat SNVT Type SNVT Index

nvoUnitStatus.heat_output_secondary DAC, SCC Yes SNVT_hvac_status 112

Local OA Temperature Keypad Menu Path Temperature/Outside Air Temp

This read-only attribute indicates the current outdoor air temperature from the local outdoor air temperature sensor



-40.0°F…176.0°F

N/A

28 ED 15125-3




Full Reference

RTU_C#########.LocalOAT.Present_Value


nvoLocalOATemp DAC, SCC Yes SNVT_temp_p 105

Local Space Temperature Keypad Menu Path Temperature/Space Temp

This read-only attribute indicates the current space air temperature from the local space air temperature sensor.



-40.0°F…176.0°F

N/A




Full Reference

RTU_C#########.LocalSpaceT.Present_Value


nvoLocalSpaceTmp SCC Yes SNVT_temp_p 105

Minimum Send Time This read/write configuration property defines the minimum period of time between automatic network variable output

transmissions.

CAUTION



Time Seconds Real 0.0…6553.4 sec 0 Seconds

BACnet No BACnet equivalent.

LONWORKS LONWORKS Name Profile SNVT Type SNVT Index SCPT Reference SCPT Index

nciMinOutTm DAC, SCC SNVT_time_sec 107 SCPTminSendTime 52

Object Request This input network variable provides the mechanism to request an operation or a mode for a functional block within a

device.

!

ED 15125-2 29

A request consists of an object ID (the object_id field) and an object request (the object_request field). The object ID is the

functional block index for a functional block on the device. The Node Object functional block is index zero. The remaining

functional blocks are numbered sequentially, starting with one.

The following functions are supported:

RQ_NORMAL – If the specified functional block was in the disabled or overridden state, this request cancels that

state, and returns the functional block to normal operation. If the functional block was already in the normal state, a

request to enter the normal state is not an error. After device reset, the state of functional blocks on the device is

application-specific. An RQ_NORMAL request that specifies the Node Object functional block index is a request for

all functional blocks in the device to leave the disabled and overridden states.

RQ_UPDATE_STATUS – Requests the status of the specified functional block to be sent to the nvoStatus output

network variable. The state of the functional block is unchanged. An RQ_ UPDATE_STATUS request that specifies

the Node Object functional block is a request for the status of the device and all functional blocks on the device. The

status bits of the Node Object (with the exception of invalid_request and invalid_id) are defined to be the inclusive-

OR of the status bits of all the other functional blocks in the device; with the possible addition of error conditions and

other conditions attributed to the device as a whole, rather than to any individual functional block. For example, if

29eedb_failure is supported for the Node Object, then it should be set when reporting the Node Object functional block

status whenever any of the functional blocks in the device reports communications failure, as well as when there is a

communications failure at the device level.

RQ_REPORT_MASK – Requests a status mask reporting the status bits that are supported by the specified functional

block to be sent to the nvoStatus output network variable. A one bit in the status mask means that the device may set

the corresponding bit in the object status when the condition defined for that bit occurs. A zero bit in the status mask

means that the bit is never set by the device.


Object Request N/A Structure N/A No N/A

BACnet

No BACnet equivalent

LonWorks LonWorks Name Profile Uses Heartbeat SNVT Type SNVT Number

nviRequest Node Object No SNVT_obj_status 93

Structure

typedef struct {

unsigned long object_id;

object_request_t object_request;

} SNVT_obj_ request

Enumeration Definitions (object_request_t)


0 RQ_NORMAL Enable object and remove override

1 RQ_DISABLED Disable object (not supported)

2 RQ_UPDATE_STATUS Report object status

3 RQ_SELF_TEST Perform object self-test (not supported)

4 RQ_UPDATE_ALARM Update alarm status (not supported)

5 RQ_REPORT_MASK Report status bit mask

6 RQ_OVERRIDE Override object (not supported)

30 ED 15125-3


7 RQ_ENABLE Enable object (not supported)

8 RQ_RMV_OVERRIDE Remove object override (not supported)

9 RQ_CLEAR_STATUS Clear object status (not supported)

10 RQ_CLEAR_ALARM Clear object alarm (not supported)

11 RQ_ALARM_NOTIFY_ENABLED Enable alarm notification (not supported)

12 RQ_ALARM_NOTIFY_DISABLED Disable alarm notification (not supported)

13 RQ_MANUAL_CTRL Enable object for manual control (not supported)

14 RQ_REMOTE_CTRL Enable object for remote control (not supported)

15 RQ_PROGRAM Enable programming of special configuration properties (not

supported)

16 RQ_CLEAR_RESET Clear reset-complete flag (reset_complete) (not supported)

17 RQ_RESET Execute reset-sequence of object (not supported)

-1(0xFF) OC_NUL Invalid Value

Object Status This output network variable reports the status for any functional block on a device. It is also used to report the status of the

entire device and all functional blocks on the device. A status update consists of an object ID (the object_id field) and

multiple status fields. The object ID is the functional block index as described under nviRequest. If the object ID is zero,

the status of the device itself and all functional blocks on the device is reported. The status fields are one-bit bitfields. The

only supported status fields are the report_mask, invalid_id, and invalid_request fields; all other status fields are not

supported.

invalid_request – Set to one if an unsupported request code is received on the nviRequest input network variable.

invalid_id – Set to one if a request is received for a functional block index that is not defined in the device. No further

checking of the request code is required when set to one.

report_mask Set to one if an RQ_REPORT_MASK request is received by the nviRequest input network variable,

and the nvoStatus output network variable is set to contain the status mask. The status mask is an nvoStatus value that

describes the status bits that are supported beyond the three mandatory status bits. The status mask consists of all fields

in the nvoStatus output network variable, with the exception of the report_mask, invalid_id, and invalid_request

fields. A one bit in the mask means that the functional block may set the corresponding bit in the nvoStatus output

network variable when the condition defined for that bit occurs. A zero bit means that the functional block may never

set the bit.


Object Status N/A Structure N/A N/A

BACnet

No BACnet equivalent

LONWORKS LonWorks Name Profile Uses Heartbeat SNVT Type SNVT Number

nvoStatus Node Object No SNVT_obj_request 92

Structure

typedef struct {

unsigned long object_id;

unsigned invalid_id;

unsigned invalid_request;

unsigned disabled;

unsigned out_of_limits;

unsigned open_circuit;

unsigned out_of_service;

ED 15125-2 31

unsigned mechanical fault;

unsigned feedback_failure;

unsigned over_range;

unsigned under_range;

unsigned electrical_fault;

unsigned unable_to_measure;

unsigned 31eedb_failure;

unsigned fail_self_test;

unsigned self_test_in_progress;

unsigned locked_out;

unsigned manual_control;

unsigned in_alarm;

unsigned in_override;

unsigned report_mask;

unsigned programming_mode;

unsigned programming_fail;

unsigned alarm_notify_disabled;

unsigned reset_complete;

unsigned reserved2;

} SNVT_obj_status

Effective Occupancy Keypad Menu Path Effect.Occupancy

This read-only property indicates which occupancy mode the unit is actually using. The unit controller calculates this. If

the Occupancy Override Setpoint (not settable via the network) is set to Network then the unit controller must calculate the

mode according to the Effective Occupancy Output state table in the LonMark Space Comfort Controller document (see

www.lonmark.org). The following is a modified state table based on that table.


(nviOccManCmd)

register 7

(See Notes 1 and 2)

Occupancy Schedule

(nviOccSchedule)

register 19

Effective Occupancy

(nvoEffectOccup)

register 18

Occupied Don’t Care Occupied

Unoccupied Don’t Care Unoccupied

Bypass Occupied Occupied

Bypass Unoccupied Bypass

Bypass NUL Occupied

NUL Occupied Occupied

NUL Unoccupied Unoccupied

NUL NUL Occupied

Note 1: Bypass can be initiated by Occupancy Schedule Override transitioning to Bypass. It remains in Bypass for the duration of the Local Bypass Time. The timer is reinitiated by another transition of the Occupancy Schedule Override to Bypass.

Note 2: If the bypass timer needs to be reset and the Occupancy Schedule Override is already in Bypass, then the communication module must a) set the

Occupancy Schedule Override to Occupied, b) read the Occupancy Schedule Override register and verify that it is set to Occupied, then c) set the

Occupancy Schedule Override to Bypass.


Occupancy N/A Unsigned Enumerated N/A




Full Reference

RTU_C#########.EffectOcc.Present_Value

32 ED 15125-3

Enumeration

1. Occupied

2. Unoccupied

3. Bypass


nvoEffectOccup DAC, SCC Yes SNVT_occupancy 109



0 OC_OCCUPIED Area is occupied

1 OC_UNOCCUPIED Area is unoccupied

2 OC_BYPASS Area is temporarily occupied for the bypass period

3 OC_STANDBY Value not available

0xFF OC_NUL Value not available


BACnet LONWORKS

1 Occupied 0 OC_OCCUPIED

2 Unoccupied 1 OC_UNOCCUPIED

3 Bypass 2 OC_BYPASS

1 Occupied 3 OC_STANDBY

1 Occupied 0xFF OC_NUL

Occupancy Mode (Occupany Schedule Override) This read/write property sets the Maverick I Rooftop Unit Controller Occupancy Mode. It overrides the occupancy

schedule that the unit is using. Occupancy Schedule Override has priority over Occupancy Schedule Input. It is typically

sent by a wall-mounted occupant-interface module or a supervisory controller to manually control occupancy modes, or to

override the scheduled occupancy. This input is also used with Occupancy Schedule Input to determine the Effective

Occupancy Mode. Refer to Effective Occupancy for more information.

This property is used to place the unit from Unoccuppied Mode to Bypass Mode. If the Timed Override button on the room

sensor is pressed while the unit is in the Unoccupied mode, or if this network property changes from Unoccupied to Bypass,

then the occupancy changes to Bypass and the bypass timer (see Occupancy Schedule Override Setpoint) starts counting

down. When the timer reaches zero, occupancy changes back to Unoccupied. Additional bypass requests (made by

pressing the Timed Override button or by changing this property to Occupied then back to Bypass) resets the Bypass timer

to the maximum value. Set Occupancy Schedule Override Setpoint to zero to disable the bypass feature.

The unit operates the same way in the Bypass Mode as it does in the Occupied Mode. In Bypass Mode, the unit uses the

occupied heating and cooling setpoints.

For LONWORKS, this network variable input should never be bound to a network variable that uses a Send Heartbeat

function.


Mode N/A Unsigned Enumerated No Auto




Full Reference

RTU_C#########.OccManCmd.Present_Value

ED 15125-2 33

Enumeration

1 = Occ

2 = Unocc

3 = Bypass

4 = NUL (Auto)


nviOccManCmd DAC, SCC No SNVT_occupancy 109

LONWORKS Enumeration Definitions




2 OC_BYPASS Area is temporarily occupied for the bypass period

3 OC_STANDBY Value not available

0xFF OC_NUL Default after power-up (Auto)


BACnet LONWORKS



3 Bypass 2 OC_BYPASS

1 Occupied 3 OC_ STANDBY

4 NUL 0xFF OC_NUL

Occupancy Schedule This input network variable is used to schedule a group of rooftop units that are coupled to one occupancy schedule. For

example, there could be four rooftop units for a small office building and all four units could be tied to the same occupancy

schedule starting at 8:00 AM and ending at 5:00 PM, Monday through Friday.

This read/write property commands the occupancy function of the Maverick I Rooftop Unit Controller when Occupancy

Mode is set to NUL (Auto). It is typically sent by a scheduler or a supervisory node. SNVT_tod_event is a structure

containing three parts.

Current_state, (required)

Next_state (not used)

Time_to_next_state (not used)

This network variable is used in conjunction with Optimal Start. This network variable can only be set via the network.


State N/A Unsigned

LONWORKS:

structured

Enumerated Yes 0xFF (NUL),




Full Reference

RTU_C#########. OccState.Present_Value

Enumeration

1=Occ

2=Unocc

3=NUL (Powerup)

34 ED 15125-3


nviOccSchedule DAC, SCC Yes SNVT_tod_event 128

Structure

typedef struct {

occup_t Current_state; See Below

occup_t next_state; Not Used

unsigned long time_to_next_state; Not Used

}SNVT_tod_event

Field Definitions

Field Data Point Reference Units Valid Range Notes

current_state Occupancy Scheduler Input occup_t current scheduled occupancy state

next_state Occupancy Scheduler Next occup_t FIELD NOT USED

time_to_next_state Occupancy Scheduler Time Minutes 0 to 65534 FIELD NOT USED

Enumeration Definitions (occup_t) Value Identifier Notes



2 OC_BYPASS Not Used

3 OC_STANDBY Not Used

0xFF OC_NUL Default after power-up

Enumeration Correspondence BACnet LONWORKS



1 Occupied 2 OC_BYPASS

1 Occupied 3 OC_STANDBY

3 NUL 0xFF OC_NUL

Occupancy Schedule Override Setpoint Keypad Menu Path Time Delays/ Ten. Over. Time

This read/write configuration property defines the amount of time that the unit operates in the Bypass mode. Writing 0

disables the feature.

CAUTION

Please note that anytime a command is written to a network configuration parameter, or to a BACnet object that controls a configuration parameter, this information is stored in the unit controller's EEPROM/FLASH memory. Recognize that writing to the unit controller's EEPROM/FLASH memory is an operation that has a finite limit. For this reason the number of writes made to configuration parameters, or BACnet objects linked to configuration parameters,

!

ED 15125-2 35

must be limited in order to avoid damage to the unit controller.


Time Minutes Real 0…360 min 120



Analog Value 2 3 Present Value 85

Full Reference

RTU_C#########.OccSchOverrideSP.Present_Value


nciBypassTime SCC SNVT_time_min 107 SCPTbypassTime 34

Occupied Cooling Setpoint Keypad Menu Path Setpoint/Occ Cool SP

This read/write configuration property sets the Occupied Cooling Setpoint.

The BACnet property only applies to the subject data point. The LONWORKS variable is a structure that covers three other

data points: Unoccupied Cooling Setpoint, Occupied Heating Setpoint, and Unoccupied Heating Setpoint.

CAUTION



Temperature °F/°C Real

LONWORKS:

structured

4.4°C…37.7°C

40°F…100.0°F

LonWorks: 40°F…95.0°F

72°F / 22°C




Full Reference

RTU_C#########.OccCoolSP.Present_Value

LONWORKS LONWORKS Name Profile SCPT Reference SCPT Index SNVT Type SNVT Index

nciSetpoints.Occupied_Cool SCC SCPTsetPnts 60 SNVT_temp_setpt 106

Structure

typedef struct {

signed long occupied_cool;

signed long standby_cool; Not Used

signed long unoccupied_cool;

signed long occupied_heat;

signed long standby_heat; Not Used

signed long unoccupied_heat;

} SNVT_temp_setpt;

!

36 ED 15125-3

Occupied Heating Setpoint Keypad Menu Path Setpoint/Occ Heat SP

This read/write configuration property sets the Occupied Heating Setpoint.

The BACnet property only applies to the subject data point. The LONWORKS variable covers three other data points:

Occupied Cooling Setpoint, Unoccupied Cooling Setpoint, and Unoccupied Heating Setpoint.

CAUTION



Temperature °F/°C Real

LONWORKS:

structured

2.2°C…35.5°C

36.0°F…96.0 °F

LonWorks: 36°F…91.0°F

68°F / 20°C




Full Reference

RTU_C#########. OccHeatSetpt.Present_Value


nciSetpoints.occupied_heat SCC SCPTsetPnts 60 SNVT_temp_setpt 106

Structure

typedef struct {



signed long unoccupied_cool;



signed long unoccupied_heat;

} SNVT_temp_setpt;

Effective Outdoor Air Temperature Keypad Menu Path Temperatures/Eff Out Air Temp

This output network variable indicates the current value of the Outdoor Air Temperature for monitoring purposes. This

value reflects the network input nviOutdoorTemp (if valid) or the value from a locally wired sensor.


Temperature °F/°C Real -40.0°C…80.0°C

-40.0°F…176.0°F

N/A

!

ED 15125-2 37




Full Reference

RTU_C#########. EffectOAT.Present_Value


nvoOutdoorTemp DAC, SCC Yes SNVT_temp_p 105

Remote Outdoor Air Temperature This input network variable is the measured Outdoor Air Temperature. Either a network sensor or a supervisory controller

typically provides the value. When an outdoor air temperature sensor is locally wired to the unit controller, the

nviOutdoorTemp has priority if a valid value is present.


Temperature °F/°C Real -40°C…50°C

-40°F…122°F

Yes 327.67 (0x7FFF)




Full Reference

RTU_C#########. OutdoorTempInput.Present_Value


nviOutdoorTemp DAC, SCC Yes SNVT_temp_p 105

Receive Heartbeat This read/write configuration property defines the maximum time that elapses after the last update to a specified network

variable input before the communication module reverts to it default values.

CAUTION



Time Seconds Real 0.0…6553.4 sec 0.0 seconds




Full Reference

RTU_C#########. ReceiveHrtBt.Present_Value

!

38 ED 15125-3


nciRcvHrtBt DAC, SCC SNVT_time_sec 107 SCPTmaxRcvTime 48

Return Air Temperature Keypad Menu Path Temperatures/Return Air Temp

This read-only attribute indicates the current reading from the Maverick I unit return air temperature sensor. This value is

used for control purposes.


Temperature F / °C Real -40.0°C…80.0°C

-40.0°F…176.0°F

N/A




Full Reference

RTU_C#########. EffectRAT.Present_Value


nvoRATemp DAC, SCC

Yes SNVT_temp_p 105

Return/Exhaust Fan Capacity This read-only attribute indicates the current return fan or exhaust fan capacity. This output network variable is used to

monitor the status of the exhaust fan. If there is only on/off control, the expected capacity is 0% for off and 100% for on. If

there is modulating fan speed control, the range is 0% to 100% (fan off to full speed). LONWORKS Only: When a value of 1

.. 200 is read then set the state field to 1, otherewise set it to 0.


Fan Capacity Percent Real

LONWORKS: Structure

0…100% N/A




Full Reference

RTU_C#########. ExhFanCap.Present_Value


nvoExhFanStatus.value DAC, SCC Yes SNVT_switch N/A

typedef struct {

unsigned value; 0–100%

signed state; 0=Off

1=On

} SNVT_switch;

ED 15125-2 39

Send Heartbeat This read/write configuration property defines maximum period of time that expires before the specified network variable

output is automatically updated.

CAUTION



Time Seconds Real 0.0…6553.4 sec 0.0 seconds

BACnet No BACnet equivalent.


nciSndHrtBt DAC, SCC SNVT_time_sec 107 SCPTmaxSendTime 49

Communication Module Software Version This read configuration property is used to identify the application software, version and revision that have been installed in

the communication module.


N/A N/A Real 0 .. 0xFFFF NA



Device 8 Variable Firmware_Revision 44

Full Reference

Firmware_Revision

LONWORKS LONWORKS Name Profile SNVT Type SCPT Reference SCPT Index

UCPTcommDevMajVer &

UCPTcommDevMinVer

DAC, SCC N/A SCPT 165 and 166

Application Version Keypad Menu Path General Information /Software Version

This read only attribute reflects the current Application Version of the Maverick I Rooftop Unit Controller.


N/A N/A Real N/A N/A



Device 8 Variable Application_Software_Version 12

Full Reference

RTU_C#########. Application_Software_Version

!

40 ED 15125-3


UCPTunitDevMajVer

&

UCPTunitDevMinVer

DAC, SCC N/A SCPT 165 and 166

Integrated Furnace Controller Software Version Keypad Menu Path Furnace Ctrl/IFC Revision

This read only configuration property is used to identify the application software, version, and revision that have been

installed in the integrated furnace controller.






Full Reference

RTU_C#########. Integrated_Furnace_Controller_Software_Version.Present_Value


UCPTifcDevMajVer &

UCPTifcDevMinVer DAC, SCC N/A SCPT 165 and 166

Honeywell Economizer Software Version Keypad Menu Path Economizer /Econ Firm Vers

This read configuration property is used to identify the application software, version and revision that have been installed in

the Honeywell Economizer.






Full Reference

RTU_C#########. Honeywell_ Economizer_Software_Version.Present_Value


UCPTeconDevMajVer &

UCPTeconDevMinVer DAC, SCC N/A SCPT 165 and 166

Location This read/write configuration property is used to describe the location of the unit.

CAUTION

Please note that anytime a command is written to a network configuration parameter, or to a BACnet object that controls a configuration parameter, this information is stored in the unit controller's EEPROM/FLASH memory. Recognize that writing to the unit controller's EEPROM/FLASH memory is an operation that has a finite limit. For this

!

ED 15125-2 41

reason the number of writes made to configuration parameters, or BACnet objects linked to configuration parameters, must be limited in order to avoid damage to the unit controller.


Name character ASCII character any 0



Device 8 Variable Location 58

Full Reference

RTU_C#########. Location


nciLocation DAC, SCC SNVT_str_asc 36 SCPTlocation 17

Local Space CO2 This read-only attribute indicates the current space CO2 level from an optional space CO2 sensor. This value reflects the

network input nviSpaceIAQ (if valid) or the value from a locally wired sensor.


Concentration Ppm Real 0…2000 ppm

N/A




Full Reference

RTU_C#########. EffectSpaceCO2.Present_Value


nvoSpaceCO2 SCC, DAC Yes SNVT_ppm 29

Remote Space IAQ Keypad Menu Path Economizer /Ext.DCV Level

This read/write attribute indicates the current space CO2 level from the network. This value takes priority over a locally

wired sensor. The unit controller only passes this value to the Economizer Logic Module (ELM). It does not set or

otherwise command this value.


Concentration Ppm Real 0…2000 ppm Yes 32767

(0x7FFF)




Full Reference

RTU_C#########.SpaceIAQInput.Present_Value


nviSpaceIAQ SCC, DAC Yes SNVT_ppm 29

42 ED 15125-3

LONWORKS: Set to 0 to set invalid.

Effective Space Temperature Keypad Menu Path Temperatures/Eff Space Temp

This read-only attribute indicates the current value of the Space Temperature for monitoring purposes. This value reflects

the network input nviSpaceTemp (if valid) or the value from a locally wired sensor.



-40.0°F…140.0°F

N/A




Full Reference

RTU_C#########. EffectSpaceT.Present_Value


nvoSpaceTemp SCC Yes SNVT_temp_p 105

Remote Space Temperature This read/write attribute indicates the current space or zone temperature that is written from the network. If this network

value becomes unreliable, the temperature reverts to the value provided by the attached Space Temperature sensor.


Remote Space

Temperature

°F / °C Real -10.0°C…50.0°C

14.0°F…122.0°F Yes 327.67 (0x7FFF)




Full Reference

RTU_C#########. SpaceTempInput.Present_Value


nviSpaceTemp SCC Yes SNVT_temp_p 105

Effective Supply Fan Capacity Keypad Menu Path Unit Status/Indoor Fan (ON then 100%, OFF then 0%)

This read-only attribute indicates the current Discharge Fan Capacity.



LONWORKS network variable. The LONWORKS variable covers six other data points: Unit State, Primary Heating Capacity,

Outdoor Air Damper Position, In Alarm and Secondary Heating Capacity (not used).


Fan Capacity Percent Real

LONWORKS: Structure

BACnet: 0…100%

LONWORKS: 0…100%

N/A

ED 15125-2 43




Full Reference

RTU_C#########. FanOutput.Present_Value


nvoUnitStatus.fan_output DAC, SCC Yes SNVT_hvac_status 112

Economizer Enable This read/write configuration property enables or disables economizer functionality for free cooling and also for ventilation

for indoor air quality (IAQ). This property can be set to free cooling disabled and ventilation enabled, both free cooling

and ventilation enabled, both free cooling and ventilation disabled or Auto. When set to Auto, then the unit control decides;

this will cause the unit control to enable free cooling and enable ventilation.

The LONWORKS point nviEconEnable has two properties; a State and a Value field. In version 1.5 only the state field is

referenced. In version 2+, both fields are referenced.


State NA Unsigned

LONWORKS: Structure

Enumerated Auto




Full Reference

RTU_C#########.EconEnable.Present_Value

Enumeration

1 = Disable Free Cooling, Enable Ventilation

2 = Enable Free Cooling, Enable Ventilation

3 = Auto (unit control decides)

4 = Disable All Economizer Functionality

LONWORKS LONWORKS Name Profile Uses Heartbeat SCPT Reference SCPT Index SNVT Type SNVT Index

nviEconEnable DAC, SCC Yes NA NA SNVT_switch 95

Structure

typedef struct {

unsigned value;

signed state;

} SNVT_switch;

Valid Range (LonWorks Version 2.0+)

State Value Economizer

0 200 Disable All Economizer Functionality (unit control v2.x+)

Auto (unit control v1.5)

0 0..199 Disable Free Cooling, Enable Ventilation (unit control v2.x+)

Disable All Economizer Functionality (unit control v1.5)

44 ED 15125-3

1 N/A Enable Free Cooling, Enable Ventilation

-1

0xFF

(255)

N/A Auto (unit control decides)

Valid Range (LonWorks Version 1.5)

State Value Economizer

0 N/A Disable All Economizer Functionality (unit control v1.x)

Disable Free Cooling, Enable Ventilation (unit control v2.x+)

1 N/A Enable Free Cooling, Enable Ventilation

-1

0xFF

(255)

N/A Auto (unit control decides)

Demand Control Ventilation Limit Keypad Menu Path Economizer/Econ. DCV Limit

This read/write attribute indicates the current Demand Control Ventilation Limit from the network.

CAUTION



Percent Percent Real 0…100% 32,767 (0x7FFF)




Full Reference

RTU_C#########. DemandControlVentLimit.Present_Value


nviMinVentLim DAC, SCC No SNVT_lev_percent 81

Ventilation Limit This read/write attribute indicates the current Ventilation Limit from the network.

CAUTION


!

!

ED 15125-2 45


Percent Percent Real 0…100% 32,767 (0x7FFF)




Full Reference

RTU_C#########. VentLimit.Present_Value


nviMaxVentLim DAC, SCC No SNVT_lev_percent 81

Space CO2 High Limit Setpoint Keypad Menu Path Economizer/DCV Level Setpt.

This read/write configuration property sets the space CO2 Setpoint level. Network accepts a value 0, 500-2000 ppm.

Writing 0 disables the CO2 limit function of the unit controller.

CAUTION



Concentration Ppm Real 0, 500…2000 ppm 0




Full Reference

RTU_C#########.SpaceCO2HighLimitSpt.Present Value

LONWORKS LONWORKS Name Profile Uses Heartbeat SCPT Type SCPT Index

nciSpaceCO2Lim DAC, SCC No SCPTlimitCO2 42

Exhaust On/Off Setpoint Keypad Menu Path Economizer/Econ.Exh. ON/OFF

This read/write configuration property is used to set the setpoint on the economizer that turns the exhaust fan off and on

depending on the position of the damper.

CAUTION


!

!

46 ED 15125-3


Percent % Real 0…100% 25% = 5000




Full Reference

RTU_C#########. ExhOnOffSetpt.Present_Value

LONWORKS LONWORKS Name Profile SCPT Reference SCPT

Index SNVT Type SNVT

Index

nciExhaustSpt DAC, SCC SCPTminReturnExhaustFanCapacity 60 SNVT_lev_percent 81

Remote Space Temperature Spt Adjust This read/write property is used in both BACnet and LONWORKS networks. If the value is valid and Room Sensor Setpoint

Enable is set to Disabled (Network) then it is used in the calculation of the Effective Setpoint Output, otherwise the

Effective Setpoint Output does not depend on this value.

Note: This value does not affect unoccupied setpoints.


Temperature °C/ °F Real 10.0°C…35.0°C

50.0°F…95.0°F No 32,767 (0x7FFF)




Full Reference

RTU_C#########.RemoteSpaceSetpt.Present_Value


nviSetpoint SCC No SNVT_temp_p 105

Unit State Keypad Menu Path Unit Status/Mode

This read-only property indicates the current unit operating status information. Note that when “Unit State” displays

“Standby” at the keypad, the corresponding “Unit State” parameter displays “Off” from the BAS.


Unit State N/A BACnet: unsigned

LONWORKS: Structures

Enumerated N/A




ED 15125-2 47

Full Reference

RTU_C#########. UnitStatus.Present_Value

Enumeration

1=Off

2=Start

3=Recirc

4=Fan Only

5=MinDAT

6=Htg

7=Econo

8=Clg

LONWORKS LONWORKS Name Profile Uses Heartbeat SNVT Type SNVT Number

nvoUnitStatus.Mode DAC, SCC Yes SNVT_hvac_status 112

Structure typedef struct {

Hvac_t mode;

Signed long heat_output_primary;

Signed long heat_output_secondary;

Signed long cool_output;

signed long econ_output;

signed long Fan_output;

Unsigned in_alarm;

} SNVT_hvac_status;

Field Definitions

Field Data Point Reference Valid Range Notes

Mode See below Enumerated compatible with

SNVT_hvac_mode

Heat_output_primary Primary Heating Capacity -163.83 .. +163.83% (% of full scale) primary heat output

Heat_output_secondary Secondary Heating Capacity -163.83 .. +163.83% (% of full scale) secondary heat output

Cool_output Cooling Capacity -163.83 .. +163.83% (% of full scale) cooling output

Econ_output Out Door Air Damper Position -163.83 .. +163.83% (% of full scale) economizer output

Fan_output Discharge Fan Capacity -163.83 .. +163.83% (% of full scale) fan output

in_alarm In Alarm 0 = No Alarm

1-99 = Warning

100-199 = Problem

200-255 = Fault

Any non-zero value

means unit is in alarm1

1The value assigned to each alarm is the same for both BACnet and LONWORKS applications. For these enumerations, refer to Current Alarm section.

LONWORKS (Mode) Enumeration Definitions

Enumeration Definitions (hvac_t) Value Identifier Notes

0 HVAC_AUTO Not Used

1 HVAC_HEAT Unit State is Heat

2 HVAC_MRNG_WRMUP Not Used

3 HVAC_COOL Unit State is Cool

4 HVAC_NIGHT_PURGE Not Used

5 HVAC_PRE_COOL Not Used

6 HVAC_OFF Unit State is either Off, Startup, or Standby

7 HVAC_TEST Not Used

8 HVAC_EMERG_HEAT Not Used

9 HVAC_FAN_ONLY Air not conditioned, fan turned on

10 HVAC_FREE_COOL Not Used

48 ED 15125-3

11 HVAC_ICE Not Used

12 HVAC_MAX_HEAT Not Used

13 HVAC_ECONOMY Not Used

14 HVAC_DEHUMID Not Used

15 HVAC_CALIBRATE Not Used

16 HVAC_EMERG_COOL Not Used

17 HVAC_EMERG_STEAM Not Used

0xFF HVAC_NUL Off (control powerup)


BACnet LONWORKS

2 Start 0 HVAC_AUTO (not used)

6 Htg 1 HVAC_HEAT

2 Start 2 HVAC_MRNG_WRMUP(not used)

8 Clg 3 HVAC_COOL

2 Start 4 HVAC_NIGHT_PURGE(not used)

2 Start 5 HVAC_PRE_COOL(not used)

1 Off 6 HVAC_OFF

2 Start 7 HVAC_TEST(not used)

2 Start 8 HVAC_EMERG_HEAT(not used)

4 Fan Only 9 HVAC_FAN_ONLY

2 Start 10 HVAC_FREE_COOL(not used)

2 Start 11 HVAC_ICE(not used)

2 Start 12 HVAC_MAX_HEAT(not used)

7 Econo 13 HVAC_ECONOMY

2 Start 14 HVAC_DEHUMID

2 Start 15 HVAC_CALIBRATE(not used)

2 Start 16 HVAC_EMERG_COOL(not used)

2 Start 17 HVAC_EMERG_STEAM(not used)

2 Start 0xFF MODBUS Register reads 0xFF then BACnet converts to Start

BACnet Unit Support This is a BACnet-only parameter that sets the units that are sent from the communication module to the BACnet network.

Units can be either metric or English.

CAUTION



Unit Support N/A BACnet: Unsigned

LONWORKS: Structures

Metric

English

Metric

!

ED 15125-2 49



Multistate Value 19 16 Present_Value 85

Full Reference

RTU_C#########. UnitSupport.Present_Value

Enumeration

1 = Metric

2 = English

LONWORKS No LONWORKS equivalent.

Unoccupied Cooling Setpoint Keypad Menu Path Setpoints/Unc Cool SP

This read/write configuration property sets the temperature above which the Maverick I Rooftop Unit Controller starts and

provides cooling (night setup) during unoccupied periods. An optional space temperature sensor is required for unoccupied

cooling operation. The BACnet property only applies to the subject data point. The LONWORKS variable is a structure that

covers three other data points: Unoccupied Cooling Setpoint, Occupied Heating Setpoint, and Unoccupied Heating Setpoint.

CAUTION



Temperature F / °C Real

LONWORKS:

Structures

4.4°C…37.7°C

40.0°F…100.0°F

LonWorks: 40.0°F…95.0°F

85°F / 29.44°C




Full Reference

RTU_C#########. UnoccCoolSetpt.Present_Value


nciSetpoints.unoccupied_cool SCC SCPTsetPnts 60 SNVT_temp_setpt 106

Structure

typedef struct {



signed long Unoccupied_cool;



signed long Unoccupied_heat;

} SNVT_temp_setpt;

!

50 ED 15125-3

Unoccupied Heating Setpoint Keypad Menu Path Setpoints/Unc Heat SP

This read/write configuration property sets the temperature above which the Maverick I Rooftop Unit Comptroller starts up

and provides unoccupied heating (night setback). An optional space temperature sensor is required for unoccupied heating.

The BACnet property only applies to the subject data point. The LONWORKS variable is a structure that covers three other

data points: Unoccupied Cooling Setpoint, Occupied Heating Setpoint, and Unoccupied Heating Setpoint.

CAUTION



Temperature F / °C Real

LONWORKS:

Structures

2.2°C…35.5°C

36.0°F…96.0°F

LonWorks: 36.0°F…91.0°F

55°F / 12.7°C




Full Reference

RTU_C#########. UnoccHeatSetpt.Present_Value


nciSetpoints.unoccupied_heat SCC SCPTsetPnts 60 SNVT_ temp_setpt 106

Structure

typedef struct {

signed long Occupied_cool;


signed long Unoccupied_cool;

signed long Occupied_heat;


signed long Unoccupied_heat;

} SNVT_temp_setpt;

Space RH Configuration Setpoint Keypad Menu Path Dehumidification/ Dehumidification Setpt.

This is the read/write configuration property that the network can use to set the space relative humidity configuration

setpoint from the network. Writing 0 disables the dehumidification.function in the controller. This configuration setpoint

does not have a corresponding relative humidity network input or relative humidity setpoint input. The relative humidity is

read by the Field Input 2 hardwired input on the unit control board. To read the relative humidity value, Field Input 2 must

be configured for ‘percent’ units. See Field Input 2 Configuration for details for selecting units. This parameter is saved in

EEPROM (Flash) memory; therefore, the number of writes to it must be limited in order to avoid damage to the unit

controller.

CAUTION

Please note that anytime a command is written to a network configuration parameter, or to a BACnet object that controls a configuration parameter, this information is stored in the unit controller's EEPROM/FLASH memory.

!

!

ED 15125-2 51

Recognize that writing to the unit controller's EEPROM/FLASH memory is an operation that has a finite limit. For this reason the number of writes made to configuration parameters, or BACnet objects linked to configuration parameters, must be limited in order to avoid damage to the unit controller.


Relative Humidity % Real 0-100% 0%




Full Reference

RTU_C#########.SpaceRHCfgSpt.Present Value

LONWORKS LONWORKS Name Profile Uses Heartbeat SCPT Type SCPT Index

nviSpaceRHSetpt SCC No SCPThumSetpt 36

Field Input 1 Keypad Menu Path Temperature / Field Config 1

This read-only attribute indicates the current value of the field input 1, located on the Maverick I unit controller.



-40.0°F…176.0°F

N/A




Full Reference

RTU_C#########. FieldInput1.Present_Value

LONWORKS

LONWORKS Name Profile Uses Heartbeat SNVT Type Number

nvo FieldInput1 No SNVT_temp_p 105

Field Input 2 Keypad Menu Path Temperature / Field Config 2

This read-only attribute indicates the current value of the field configurable input 2 that is located on theh Maverick I unit

controller. It is configured by using Field Input 2 Configuration. The unit type can be configured to be one of the

following: percent, flow, temperature, PPM or pressure.

The low range and high range are configured by using Field Input 2 Configuration.

52 ED 15125-3


percent

flow

flow

temperature

temperature

PPM

pressure

pressure

% (default)

liters/sec (metric)

CFM (Imp)

°C (metric)

°F (Imp)

PPM

Pascals (metric)

IWC (Imp)

Real -500000 … 500000

N/A

BACnet In BACnet, the unit type is configured by writing to this objects (AV 62) engineering unit type property.

Object Identifier Property



Full Reference

RTU_C#########. FieldInput2.Present_Value

Units BACnet Eng Units

% (default)

liters/sec (metric)

CFM (Imp)

°C (metric)

°F (Imp)

PPM

Pascals (metric)

IWC (Imp)

98

87

84

62

64

96

53

58

LONWORKS In LonWorks, the unit type is configured by writing to the nvoFieldInput2 type property.

This variable can be configured to be one of the following SNVT types. The BAS or other LonWorks-compatible tool (i.e

LonMaker) can be used to select the SNVT type. To select SNVT type with the LonMaker Browser, right click on

nvoFieldInput2 and select Change Type. Right click on Change Format to select format (SI, US).

LONWORKS Name Profile Uses Heartbeat SNVT Type Number

nvo FieldInput2 No SNVT_lev_percent

SNVT_flow

SNVT_flow_p

SNVT_temp_p

SNVT_ppm

SNVT_press_p

81

15

161

105

29

113

Field Input 2 Configuration Keypad Menu Path N/A

These read/write configuration properties configure the low scaled value and high scaled value for Field Input 2. In

BACnet, the unit type is configured by writing to this objects (AV 62) engineering unit type property. In LonWorks, the

unit type is configured by writing to the nvoFieldInput2 type property. These parameters are saved EEPROM (Flash)

memory; therefore, the number of writes to them must be limited in order to avoid damage to the unit controller.

Calculating the scaled value for a given voltage:

ED 15125-2 53

The input voltage from the field input 2 port, mounted on the unit control, is a voltage from 0 to 10 volts. The voltage value

must be scaled to the desired units. The LowVoltRange is the desire scaled value at 0 volts. The HighVoltRange is the

desire scaled value at 10 volts.

LonWorks Only: These values must be entered in SI units. This is because all values are sent over the LonWorks network

are in SI units and, if needed, are converted to non-SI units by the receiving unit.

The input voltage versus scaled value is assumed to be linear.

Scaled Value = (InputVoltage / 10 volts) * (HighVoltRange – LowVoltRange) + LowVoltRange

Note: for inverted voltage signal inputs the LowVoltRange value will be larger than the HighVoltRange value.

CAUTION


LowVoltRange:


User Defined User Defined.

Same as the The

Units property

follows the Units

property in the Field

Input 2 object.

Real -500000…500000 No 0 %

HighVoltRange: Measurement Units Data Type Valid Range Uses Heartbeat Default Value

User Defined User Defined.

Same as the The

Units property

follows the Units

property in the Field

Input 2 object.

Real -500000…500000 No 100 %

!

10 volts

0 volts

Low Volt Range High Volt Range

5 volts Input

Voltage

Scaled Value

54 ED 15125-3




Full Reference

RTU_C#########. FieldInput2LowVoltRange.Present_Value

Object Identifier Property



Full Reference

RTU_C#########. FieldInput2HighVoltRange.Present_Value

LONWORKS LONWORKS Name Profile SNVT Type SNVT Index UCPT Reference

UCPTfieldInput SCC n/a n/a UCPTfieldInput

Structure

typedef struct {

float LowVoltRange;

float HighVoltRange;

} UNVT_field_input;

ED 15125-2 55

Alarms

Alarms are divided into three categories - Warnings, Problems, and Faults. These categories are prioritized with the

Warnings being the least important and Faults being of the highest importance. When a unit enters into a fault alarm, the

unit shuts down and requires a manual reset or power cycle before the unit will start again*. The following alarms are

available. Alarms can be cleared by the network in two ways; by clearing each alarm individually or by clearing all alarms

at the same time. The following sections describe the alarm categories, alarm monitoring, and alarm clearing.

Note that an exception to this is the Low Voltage fault. The Low Voltage fault shuts down all relays, but, the fault will

become inactive and relays will function as normal when the voltage returns to acceptable levels.

Alarm Category Alarm Number Range Action

Warning 1..99 Warnings will not alter and will not shutdown the unit

Problem 100..199 Problem alarms will alter the unit operation

Shutdown Fault 200..254 When the unit controller receives a fault alarm the unit

responds by shutting down

Alarm Table The following alarm numbers shall be used for alarms. The priorities of the alarms are defined by the alarm code number.

The higher the alarm code number, the higher its priority. If an alarm is sent that is not in this table then the unit control has

sent an alarm that the communication module doesn’t recognize. In communication module versions before v2.00, alarm

code 1 is sent if the communication module receives an alarm from the unit control that it doesn’t recognized. In

communication module v2.00 and higher, if the alarm is not recognized, then the alarm number is sent through. Therefore,

the communication module may send out an alarm that is not in this table.

Alarm Designation Alarm Level

Alarm Code

Description

No Active Alarm 0

Unspecified Alarms Warning 1 In communication module versions before v2.00, alarm code

1 is sent if the alarm is not recognized. In communication

module v2.00 and higher, if the alarm is not recognized, then

the alarm number is sent.

Clogged Filter Warning-CFS Warning 24 RTU-C displays warning.

Running Blower Fault- Air Flow

Switch Stuck Warning

28 Switch indicates airflow when fan commanded off.

Condenser Coil 1 Temperature Out of

Range Warning

30 No defrost operation, but unit continues to operate in either

heating or cooling.

Condenser Coil 2 Temperature Out of

Range Warning


heating or cooling.

Discharge Air Temperature Out of

Range Warning

32 If the sensor has ever been installed to the unit, the alarm

will be set if it becomes unavailable.

Invalid Thermostat selection Warning 42 Indicates that a combination of thermostat inputs is invalid.

LOW FLAME SENSE Warning 44 IFC flashes error code on LED, transmits the warning

through the network, but otherwise operates normally

Low Discharge Air Temp-DAT Warning 71 Threshold is 40°F

High Return Air Temp-RAT Warning 72 Threshold is 120°F.

Return Air Sensor Fail-RAT Warning 81 If the sensor has ever been installed to the unit, the alarm


Discharge Air Sensor Fail-DAT Warning 82 If the sensor has ever been installed to the unit, the alarm


Comm Module Miscommunication Warning 90 Communication module indicates miscommunication with

the RTU-C.

RTU-C Miscommunication with IFC Warning 91 RTU-C indicates miscommunication with the IFC.

Internal Control Fault – RTU-C Warning 93 An internal fault occured in the RTU-C.

Internal Control Fault – IFC Warning 94 An internal fault occured in the IFC.

56 ED 15125-3


Alarm Code

Description

FLAME LOST Problem 101 If lost 17 times within single call for heat, locks out for 1

hour. Otherwise retry ignition.

Low Voltage Circuit 2 Problem 104 Comfort Alert Code 9. Shutdown circuit 2 and wait for

voltage to return to operational levels

Low Voltage Circuit 1 Problem 105 Comfort Alert Code 9. Shutdown circuit 1 and wait for

voltage to return to operational levels

Lockout Temperature – cooling Problem 110 When the outdoor temperature drops below the cooling

lockout temperature setpoint, the unit will prevent the

compressor from operating in cool mode.

Lockout Temperature – heating Problem 111 When the outdoor temperature exceeds the heating lockout

temperature setpoint, the unit will prevent any source of heat

from operating.

Condenser Coil 2 Temp Sensor Fail-

OCT2 Problem


heating or cooling

Condenser Coil 1 Temp Sensor Fail-

OCT1 Problem

121 1. No defrost operation, but unit continues to operate in either

heating or cooling.

ELM - OAE Sensor Fail Problem 122 Can prevent the operation of the Economizer.

ELM - RAE Sensor Fail Problem 123 Can prevent the operation of the Economizer.

ELM - MAT Sensor Fail Problem 124 Can prevent the operation of the Economizer.

ELM – CO2 Sensor Fail Problem 125 Can prevent the operation of the Economizer.

ELM Actuator Fault Problem 126 Can prevent the operation of the Economizer.

MANUAL RESET LIMIT SWITCH

OPEN Problem

129 IFC Runs blower for off delay, inducer for post-purge time

and locks out for one hour

Open Circuit 2 Problem 131 Comfort Alert Code 5.

Cicuit 2 shutdown and retry after ASCD.

Open Circuit 1 Problem 132 Comfort Alert Code 5.

Circuit 1 shutdown and retry after ASCD.

PRESSURE SWITCH 2 CLOSED Problem 133 Leave inducer de-energized until pressure switch open

PRESSURE SWITCH 1 CLOSED Problem 134 Leave inducer de-energized until pressure switch open

PRESSURE SWITCH 2 OPEN Problem 135 Energize inducer indefinitely until pressure switch closes or

call for heat goes away.

PRESSURE SWITCH 1 OPEN Problem 136 Energize inducer indefinitely until pressure switch closes or

call for heat goes away.

AC Low Pressure Switch 2 Trip-LP2 Problem 137 If the low pressure switch trips 3 times within 120 minutes

of operation during the same call for cooling or heating

operation, the control will lock out compressor and outdoor

fan operation. If the lock-out due to low pressure occurs at

an outdoor ambient temperature below 5 °F, the control will

automatically exit the lock-out mode when the outdoor

ambient temperature rises above 5 °F.

AC Low Pressure Switch 1 Trip-LP1 Problem 138 If the low pressure switch trips 3 times within 120 minutes

of operation during the same call for cooling or heating

operation, the control will lock out compressor and outdoor

fan operation. If the lock-out due to low pressure occurs at

an outdoor ambient temperature below 5 °F, the control will

automatically exit the lock-out mode when the outdoor

ambient temperature rises above 5 °F.

Welded Contactor Circuit 2 Problem 141 Comfort Alert Code 8

Run outdoor and indoor fans continuously for circuit 2 and

change mode of operation to Unoccupied Auto. This

procedure prevents the ambient from reaching extreme

temperatures.

ED 15125-2 57


Alarm Code

Description

Welded Contactor Circuit 1 Problem 142 Comfort Alert Code 8

Run outdoor and indoor fans continuously for circuit 2 and

change mode of operation to Unoccupied Auto. This

procedure prevents the ambient from reaching extreme

temperatures.

Freeze Sensor 2 Out of Range -FS2 Problem 144 When reading the temperature below 42°F continuously for

15 minutes, the control shutdowns compressor and runs

indoor fan continuously. After 15 minutes of continuous

reading above 47°F, the control recovers from the alarm and

resumes operation.

Freeze Sensor 1 Out of Range -FS1 Problem 145 When reading the temperature below 42°F continuously for

15 minutes, the control shutdowns compressor and runs

indoor fan continuously. After 15 minutes of continuous

reading above 47°F, the control recovers from the alarm and

resumes operation.

Freeze Sensor #2 Fail-FS2 Problem 146 Occurs when sensors are either open or shorted. This can

prevent the operation of the compressors

Freeze Sensor #1 Fail-FS1 Problem 147 (described above)

AC HI Pressure Switch 2 Trip-HP2 Problem 148 The RTU-C control recognizes an open high pressure switch

after two seconds from its occurrence. Since the high

pressure switch is wired in series with the compressor relay,

the compressor shutdowns immediately. The outdoor fan

finishes its delay off time and it also shutdowns, until the

pressure switch is closed again AND the anti-short cycle

delay is expired. Three occurrences of a high pressure

switch within the same call will lock the circuit out. The

lockout is reset by removing the call.

AC HI Pressure Switch 1 Trip-HP1 Problem 149 (described above)

Locked Rotor Circuit 1 Problem 151 Comfort Alert Code 4.

Circuit 1 shutdown.

Missing Phase Circuit 1 Problem 152 Comfort Alert Code 6

Circuit 1 shutdown

Reverse Phase Circuit 1 Problem 153 Comfort Alert Code 7

Circuit 1 shutdown.

Locked Rotor Circuit 2 Problem 154 Comfort Alert Code 4.

Circuit 2 shutdown.

Missing Phase Circuit 2 Problem 155 Comfort Alert Code 6

Circuit 2 shutdown

Reverse Phase Circuit 2 Problem 156 Comfort Alert Code 7

Circuit 2 shutdown.

Low Pressure – Circuit 2 Problem –

Lockout Problem

158 Clearable: Can be cleared via the network. This fault can

also automatically reset if the call for cooling is removed.

Low Pressure – Circuit 1 Problem –

Lockout Problem



High Pressure– Circuit 2 Problem –

Lockout Problem



High Pressure– Circuit 1 Problem –

Lockout Problem



MAIN LIMIT OPEN Problem 170 IFC Main Limit Open. To clear must cycle power or wait

for 1 hour delay.

GAS VALVE SERVO CIRCUIT

OPEN Problem

171 Modulating furnace only

GAS VALVE SERVO FAULT Problem 172 Modulating furnace only

NO GAS VALVE FEEDBACK Problem 173 Modulating furnace only

FAILED IGNITION Problem 174 IFC locks out for 1 hour

58 ED 15125-3


Alarm Code

Description

UNEXPECTED FLAME Problem 175 IFC Energizes inducer and main blower. Locks out for 1

hour.

Space Sensor Alarm Problem 185 If the space sensor fails open or shorted, the space sensor

alarm will be set, but the control will continue to operate

using the return air sensor in place of the space sensor. If

the control has never sensed a valid space sensor input, it

will assume no space sensor is present to be used, and not

set the space sensor alarm. If a valid space sensor input is

ever detected, the control will set a non-volatile flag to

indicate the control should have and use a space sensor.

When the non-volatile flag is set, the control will detect

space sensor alarm conditions.

Outdoor Air Temperature Sensor Fail-

OAT Problem

188 Control changes defrost to time x temperature mode. The

heat source continues to be heat pump, independently of the

outdoor air temperature. Additional heat sources are also

available in case the demand is not satisfied.

Low Voltage Fault 201 De-energize all relay outputs. The fault will become

inactive and relays will function as normal when the voltage

returns to acceptable levels.

Blower Fault - Blower Not Running-

FP Fault 208 Complete unit shutdown. Clearable: Can be cleared via the

network.

Space Sensor & Return Sensor Fail Fault 244 Leave indoor fan running if requested. Do not allow cooling

or heating functions. Cannot be cleared via the network.

Smoke Detection (Selectable Fault

Response) Fault 248 RTU-C reads the smoke detection input as open -- complete

shutdown. Cannot be cleared via the network.

Emergency Stop Fault Fault 250 Complete shutdown. Cannot be cleared via the network.

Alarm Monitoring The Maverick I Unit Controller provides individual alarm identification through a unique value for each alarm. Alarms in a

Maverick Rooftop Unit Controller are sorted by the severity of the alarm. The value assigned to each alarm is the same for

both BACnet and LONWORKS applications.

BACnet Alarms within a Maverick I Rooftop Unit Controller can be monitored by using the Current Alarm (AV 27) attribute. This

attribute displays a value that corresponds to the highest priority alarm that is active. It is possible to have multiple active

alarms, but only the highest priority is displayed in this attribute. For example, if there is a simultaneous Dirty Filter

Warning (value of 24) and a Blower Not Running alarm (value of 208), then the Blower Not Running alarm (value of 208)

will display in the Present_Value of AV because it is the higher priority alarm of the two. Once the Blower Not Running

alarm condition is corrected and the alarm is cleared, the next highest priority active alarm value (in this example, value of

24 for Dirty Filter alarm) is displayed. The values for all alarms are described in the Alarm Table. If the Current Alarm

(AV 27) displays a zero in the Present_Value property, there are no active alarms.

LONWORKS Alarms within a Maverick I Rooftop Unit Controller can be monitored individually by using the In Alarm attribute. The In

Alarm attribute is part of the Unit Status Network Variable Output (i.e. nvoUnitStatus.in_alarm). This attribute displays a

value that corresponds to the highest priority alarm that is active. It is possible to have multiple active alarms, but only the

highest priority is displayed in this attribute. For example, if there is a simultaneous Dirty Filter Warning (value of 24) and

a Blower Not Running alarm (value of 208), then the Blower Not Running alarm (value of 208) will display in

nvoUnitStatus.in_alarm because it is the higher priority alarm of the two. Once the Blower Not Running condition is

corrected and the fault is cleared, the next priority active alarm value (in this example, value of 24 for Dirty Filter alarm) is

displayed. The values for all alarms are described in the Alarm section. If the attribute nvoUnitStatus.in_alarm displays a

zero, there are no active alarms.

ED 15125-2 59

Alarm Clearing Clearable active alarms are alarms that 1) are designated as clearable the Alarm Table, 2) have become active and 3) the

condition that caused the alarm is no longer active.

BACnet Alarms can be cleared via BACnet by using either of two BACnet objects. To clear all clearable active alarms, change the

Present_Value property of Binary Value 66 (Clear All Alarms) to 1. To clear one clearable active alarm, change the

Present_Value property of Analog Value 57 (Clear One Alarm) to the value of the alarm you want to clear.

LONWORKS

Clearable active alarms can be cleared using either of two Network Variable Inputs (nviClear1Alarm or nviClearAllAlarm)

of type SNVT_count. To clear all clearable active alarms, change nviClearAllAlarm to 1. To clear one clearable active

alarm, change nviClear1Alarm to the value of the alarm you want to clear.

Objects Clear All Alarms This read/write property clears all clearable active alarms. Writing 1 to this variable clears all clearable active alarms. This

variable reverts back to 0 when the alarms clear.


Alarms NA BACnet: unsigned

LONWORKS: Structure

Enumerated 0



Binary Value 5 66 Present Value 85

Full Reference

RTU_C#########.ClearAllAlarms.Present Value

LONWORKS LONWORKS Name Profile SNVT Type SNVT Number

nviClearAllAlarm DAC, SCC SNVT_count 8

Clear One Alarm This read/write property clears one clearable active alarm. To clear a particular alarm, write the value corresponding to that

alarm to this variable. This variable reverts back to 0 when the alarm clears.


Alarms NA BACnet: unsigned

LONWORKS: Structure

Enumerated 0




Full Reference

RTU_C#########.ClearOneAlarm.Present Value

Property Value

See alarms and alarm codes in Alarm

Table.

LONWORKS LONWORKS Name Profile SNVT Type SNVT Number

nviClear1Alarm DAC, SCC SNVT_count 8

60 ED 15125-3

Current Alarm This read-only attribute indicates the highest active alarm.



LONWORKS network variable. The LONWORKS variable covers six other data points: Unit State, Primary Heating Capacity,

Secondary Heating Capacity (not used), Discharge Fan Capacity, and Outdoor Air Damper Position.


Alarms N/A BACnet: unsigned

LONWORKS: Structure

Enumerated N/A




Full Reference

RTU_C#########. Alarm.Present_Value

Enumeration

See alarms and alarm codes in Alarm Table.


nvoUnitStatus.in_alarm DAC,

SCC

Yes SNVT_hvac_status 112

Property Value

See alarms and alarm codes in Alarm Table.

ED 15125-2 61

BACnet Device Management

The following functions are specific to the BACnet device. These functions are used for maintenance and testing. A network

management tool is typically used to issue the network commands.

DeviceCommunicationControl - Disable The purpose of this command is to reduce network traffic for diagnostic testing of the BACnet network. When the BACnet

Communication module receives a network command to Disable communications it stops communicating information to the

network. An optional time may be specified for how long to suspend communications. The unit continues to operate during

the Disabled state. A password of 1234 is required.

DeviceCommunicationControl - Enable When the BACnet Communication module receives a network command to Enable communications, it resumes

communicating information to/from the network. A password of 1234 is required.

ReinitializeDevice (Reset) The BACnet Communication module is capable of receiving a network ReinitializeDevice command to reboot itself (cold

start or warm start). The functionality of a cold and warm start is the same and simply reboots the BACnet

Communication Module. Reinitialize Device is implemented with a non-changeable password of 1234.

62 ED 15125-3

Appendix A: Protocol Implementation Conformance Statement (PICS)

This section contains the Protocol Implementation Conformance Statement (PICS) for the Maverick I Rooftop Unit

Controller as required by ANSI/ASHRAE (American National Standards Institute/American Society of Heating,

Refrigeration, and Air Conditioning Engineers) Standard 135-2004, BACnet; A Data Communication Protocol for Building

Automation and Control Networks.

BACnet Protocol Implementation Conformance Statement Date: March 2012

Vendor Name: Daikin Applied

Product Name: Rooftop Unit Controller

Product Model Number: RTU-C

Applications Software Version: 2.00

Firmware Revision: 2.04

BACnet Protocol Revision: Version 1

Revision 4

Product Description The Maverick I Rooftop Unit Controller with optional BACnet Communication Module is a microprocessor-based

controller designed to integrate into BACnet building automation systems.

The controller provides normal temperature, static pressure and ventilation control and alarm monitoring with alarm-

specific component shutdown in critical system conditions. Access to temperatures, pressures, operating states, alarms, and

control parameters are available through an equipment-mounted keypad/display and the BACnet control network.

BACnet Standardized Device Profile BACnet Operator Workstation (B-OWS)

BACnet Building Controller (B-BC)

BACnet Advanced Application Specific Controller (B-AAC)

BACnet Application Specific Controller (B-ASC)

BACnet Smart Sensor (B-SS)

BACnet Smart Actuator (B-SA)

Refer to the section below entitled BACnet Interoperability Building Blocks (BIBBs) Supported for a complete listing of

BIBBS.

ED 15125-2 63

BACnet Interoperability Building Blocks (BIBBs) Supported BIBB Name Designation

Data Sharing – ReadProperty – B DS-RP-B

Data Sharing – ReadPropertyMultiple – B DS-RPM-B

Data Sharing – WriteProperty – B DS-WP-B

Data Sharing – WritePropertyMultiple – B DS-WPM-B

Device Management – Dynamic Device Binding – B DM-DDB-B

Device Management – Dynamic Object Binding – B DM-DOB-B

Device Management – Dynamic Communication Control – B DM-DCC-B

Device Management – ReinitializeDevice – B DM-RD-B

Standard Object Types Supported

Object-Type

Cre

ata

ble

Dele

teab

le

Optional Properties Supported Writable Properties Not Required To Be Writable

Analog Input Description

Reliability

Min_Pres_Value

Max_Pres_Value

Analog Value Description

Reliability

Present_Value

Binary Value Description

Reliability

Inactive_Text

Active_Text

Present_Value

Device Location Location

Multi-State Value Description

Reliability

State_Text

Present_Value

Note: Although all the above standard object types are supported they may not be used.

Data Link Layer Options BACnet IP, (Annex J)

ISO 8802-3, Ethernet (Clause 7)

MS/TP master (Clause 9), baud rate(s): 9600, 19200, 38400 & 76800

Segmentation Capability Segmented requests supported Window Size:

Segmented responses supported Window Size:

Device Address Binding Static Device Binding

Yes

No

64 ED 15125-3

Networking Options Router, Clause 6 – List all routing configureations, e.g., ARCNET-Ethernet, Ethernet-MS/TP,

etc.

Annex H, BACnet Tunneling Router over IP

BACnet/IP Broadcase Management Device (BBMD)

Does the BBMD Support registration by Foreign Devices? Yes No

Character Sets Supported ANSI X3.4 IBM

/Microsoft

DBCS ISO 8859-1

ISO 10646 (UCS-2) ISO 10646 (UCS-4) JIS C 6226

Note: Support for multiple character sets does not imply they can be supported simultaneously.

This document contains the most current product information as of this printing. For the most current product

information, please go to www.DaikinApplied.com.
