Honeywell EXCEL 500, EXCEL 50, EXCEL 800 INTERFACE DESCRIPTION

Excel 50/500/800

LONWORKS® MECHANISMS

HONEYWELL EXCEL 5000 OPEN SYSTEM

INTERFACE DESCRIPTION

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

Trademark Information Echelon, LON, LONM

LonTalk, LonUsers, LonPoint, Neuron, 3120, 3150, the Echelon logo, the LONM logo, and the LonUsers logo are trademarks of Echelon Corporation registered in the United States and other countries. LonLink, LonResponse, LonSupport, and LonMaker are trademarks of Echelon Corporation.

ARK

, LONW

ORKS

, LonBuilder, NodeBuilder, LonManager,

ARK

EN0B-0270GE51 R0307 2

Excel 50/500/800 LONW

ORKS

Mechanisms

CONTENTS

Revision overview ........................................................................................................................................................................ 5

Excel 5000 LONWORKS System Architecture ........................................................................................................................... 6

Excel 50/500 Firmware Version 2.04.xx.................................................................... 6

Building Management Functionality...................................................................... 6

Excel 50/500 Firmware Version 2.06.xx and Excel 800............................................ 7

Building Management Functionality...................................................................... 7

Compatibility of Excel 50/500/800 Controllers and Distributed I/O Modules........................................................................... 8

Freely Programmable LonWorks Excel 50/500/800 Controllers ............................................................................................. 11

Number of NVs supported ...................................................................................... 11

Memory Requirements ....................................................................................... 11

Extending the Number of Physical I/Os using NVs............................................. 12

Node Object NVs .................................................................................................... 13

Activating and Configuring LonWorks plus BMF ................................................ 16

Standard NVs ......................................................................................................... 17

Network Interface Program ID ................................................................................ 19

External Network Interface File (XIF)...................................................................... 20

Binding and Mapping NVs ...................................................................................... 20

Binding Options.................................................................................................. 20

Mapping Options ................................................................................................ 22

Data Priority of NVs and Data-Points...................................................................... 26

Data-Point Types for NV Mapping .......................................................................... 27

Boardless Data-Points ............................................................................................ 27

Conversion of Data-Points to NVs .......................................................................... 27

NV-BOOSTER® ..................................................................................................... 27

Device Heartbeat Activation.................................................................................... 29

Bit-Field NVs........................................................................................................... 29

Restoring Binding Information................................................................................. 30

Excel 500 with Firmware Version 2.04.xx........................................................... 30

Excel 50/500 and CARE 4.xx with Firmware Versions 2.06.00 through 2.06.03 30

Excel 800 and CARE 7.2.xx / Excel 50/500 and CARE 4.xx with Firmware

Version 2.06.04 .................................................................................................. 30

System Alarms Defined for LONW

Distributed I/O Modules ............................................................................................................................................................. 33

Handling with Excel 50/500 Firmware Version 2.04.xx ........................................... 33

Operating Modes of Distributed I/O Modules ..................................................... 33

Autobinding (Excel 500, only)............................................................................. 33

Assignment (Excel 500, only)............................................................................. 34

Manual Binding .................................................................................................. 35

Use of E-Vision .................................................................................................. 35

Handling with Excel 50/500 Firmware Version 2.06.xx and CARE 4.xx.................. 35

Distributed I/O Node Object NVs ............................................................................ 36

Summary of Distributed I/O NVs............................................................................. 37

Excel 800 LON I/O Node Object NVs ..................................................................... 40

Distributed I/O Plug-Ins........................................................................................... 40

Guidelines for Specifying LONW

LONW

ORKS

System Engineering ................................................................................................................................................ 45

ORKS

Excel 500 Systems....................................................................................................... 41

Determining the Operating Mode of a New LonWorks System............................... 41

Implications of Changes to an Existing LONW

Application Changes............................................................................................... 43

Download Scenarios and Impacts........................................................................... 43

Effects of Hardware/Software Resetting ................................................................. 44

LONW

ORKS

Network Layout .................................................................................... 45

LONW

ORKS

Bus Termination............................................................................... 47

Network Segment Load Management..................................................................... 48

Total Network Segment Load............................................................................. 49

Minimization Measures....................................................................................... 51

XFLx22x and XL50/500 Response Times............................................................... 52

New Application Opportunities ........................................................................... 52

Excel 50/500/800 Limitations .................................................................................. 53

Firmware Version-Independent Limitations ........................................................ 53

Firmware Version-Dependent Limitations........................................................... 53

Dial-Up Access Options.......................................................................................... 54

Option 1: Dial-Up Access without Using a C-Bus............................................... 54

Option 2: Dial-Up Access Using a C-Bus ........................................................... 55

ORKS

Applications............................................... 32

ORKS

System.................................... 42

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

Option 3: Dial-Up Access via LonWorks plus BMF............................................. 55

Option 4: Dial-Up Access Using an SLTA to Connect a Modem ........................55

Applicable Literature.................................................................................................................................................................. 55

Abbreviations and Acronyms .................................................................................................................................................... 55

Index ............................................................................................................................................................................................ 58

EN0B-0270GE51 R0307 4

Excel 50/500/800 LONW

ORKS

Mechanisms

REVISION OVERVIEW

The following pages have been changed from the previous issue of this document:

page change

Throughout The entire document has been updated to include Excel 800.

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

EXCEL 5000 LONWORKS SYSTEM ARCHITECTURE

Excel 50/500 Firmware Version 2.04.xx

Beginning with Excel 50/500 firmware version 2.04.xx, the capabilities of the controllers were greatly expanded:

• Excel 500 controllers, including the XC5210C (whose CPU module features an expanded RAM) and the Excel 500 Smart controller (XCL5010), can now operate in open L definitions of the terms "open," "shared," and "local").

• Distributed I/O modules were made LonMark-compliant and also capable of use in L

ONWORKS

• Excel 50 controllers (which, in L applications) can now also be used as freely-programmable controllers.

• Freely-programmable Excel 50/500 controllers can now communicate with the Excel 10 family of controllers as well as with third-party L

• Excel 50/500 controllers now support standard L the L

ONMARK

ONWORKS

also fully documented in the node’s self-documentation.

ONWORKS

systems (see Table 3 and Table 4 on page 9 for

networks independently of Excel 500 controllers.

ONWORKS

, could operate only with configurable

ONWORKS

NVs according to

devices.

Interoperability Guidelines. Such NVs can be bound using any

network management tool (LNS-based or non-LNS-based), and are

Building Management Functionality

Table 1 summarizes the Building Management Functionality (BMF) available under firmware version 2.04.xx via either direct C-bus connection or dial-up. See also section "Dial-Up Access Options" on page 54.

Table 1. BMF via directly-connected C-Bus or via Dial-up (2.04.xx)

BMF EBI SymmetrE XBS/XBSi

time programs access dial-up / C-bus dial-up / C-bus dial-up / C-bus

alarms access dial-up / C-bus dial-up / C-bus dial-up / C-bus

trends access dial-up / C-bus dial-up / C-bus dial-up / C-bus

parameters access dial-up / C-bus dial-up / C-bus dial-up / C-bus

application download dial-up / C-bus dial-up / C-bus dial-up / C-bus

firmware download1 dial-up / C-bus dial-up / C-bus dial-up / C-bus

bus-wide MMI C-bus C-bus C-bus

With the exception of the controller currently operating via the modem.

Fig. 1 presents the Excel 5000 architecture under firmware version 2.04.xx.

Ethernet (TCP/IP)

Enterprise

C-Bus

Buildings Integrator

group (=same bus name) of

max. 30 controllers

XL50XL50

XC5010 XCL5010 XL50XL50XL50

w/ modem

(CNEP)

XBS

direct hardwire connections

group (=same bus name) of

C-Bus

w/ modem

max. 30 controllers

dial-up

Internet Explorer

(CNEP)

C-Bus

group (=same bus name) of

max. 30 controllers

w/ modem

SymmetrE

(CNEP)

XL50XL50XL50

LonWorks (LonTalk)

3rd-party products

XL10 FCU

XL10

VAV

Fig. 1. Excel 5000 architecture (firmware version 2.04.xx)

EN0B-0270GE51 R0307 6

XL10

Smart VAV

XL10 Chilled Ceiling

XL10

Hydronic

XL10 CVAHU, UVC, I/O

Smart

I/O Module

Distributed I/O Module

FISS LION

linear

valves

and

actuators

pressure/

temperature

sensors

inverters

Excel 50/500/800 LONW

ORKS

Mechanisms

Excel 50/500 Firmware Version 2.06.xx and Excel 800

Beginning with Excel 50/500 firmware version 2.06.xx, and with Excel 800, the capabilities of the controllers were further expanded:

• Besides such L based) as LonMaker for Windows, CARE, too, can now also be used to perform the L products.

• In the case of Excel 50/500/800 controllers, Building Management Functionality is available via direct hardware connections to L up to L

ONWORKS

Table 2 summarizes the Building Management Functionality (BMF) available under firmware version 2.06.xx / 3.xx.xx via either direct L See also section "Dial-Up Access Options" on page 54.

Table 2. BMF via directly-connected LonWorks or Dial-up (2.06.xx or higher)

BMF EBI SymmetrE XBS/XBSi

time program access dial-up / LonWorks dial-up / LonWorks dial-up, only

alarms access dial-up / LonWorks dial-up / LonWorks dial-up, only

trends access dial-up / LonWorks dial-up / LonWorks dial-up, only

parameter access dial-up / LonWorks dial-up / LonWorks dial-up, only

application download dial-up / LonWorks dial-up / LonWorks dial-up, only

firmware download n.a. n.a. n.a.

bus-wide MMI n.a. n.a. n.a.

Fig. 2 presents the Excel 5000 architecture under firmware version 2.06.xx /

3.xx.xx.

Ethernet (TCP/IP)

Enterprise

Buildings

Integrator

direct hardwire connection

group (=same bus ID) of

max. 30 controllers

XL50XL50

w/ modem

ONWORKS

network management tools (LNS-based or non-LNS-

binding of Honeywell and 3rd-party LONW

systems. See following section.

XBS

XC5010 XCL5010 XL50XL50XL50

w/ modem

ORKS

ONWORKS

systems or via dial-

Building Management Functionality

dial-up

group (=same bus ID) of

max. 30 controllers

ONWORKS

Internet Explorer SymmetrE

connection or dial-up.

group (=same bus ID) of

max. 30 controllers

XL800 XL800 XL50

w/ modem

Synopsis

direct hardwire connections

LonWorks (LonTalk)

3rd-party products

XL10

FCU

XL10

VAV

XL10

Smart VAV

XL10 Chilled Ceiling

XL10

Hydronic

XL10 CVAHU, UVC, I/O

Smart

I/O Module

Distributed I/O Module

FISS LION

linear

valves

and

actuators

pressure/

temperature

sensors

inverters

Fig. 2. Excel 5000 architecture (firmware version 2.06.xx and Excel 800)

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

COMPATIBILITY OF EXCEL 50/500/800 CONTROLLERS AND DISTRIBUTED I/O

MODULES

IMPORTANT:

Excel 800 controllers feature fully open L Excel 50/500 controllers bearing the L L

ONWORKS

open L

functionality. Due to RAM limitations of the 3120B1 Neuron chip,

ONWORKS

functionality is not supported in earlier models (week 44 in 2000 = date code: 0044 or earlier) of Excel 50/500 controllers containing that chip.

In the case of Excel 50/500 controllers, CARE will not support the engineering of a L

ONWORKS

network interface if the user selects a controller or an application module containing any L 3120E5. The controller will reject the download of application files containing the L

ONWORKS

network interface (*.ymp; *.ynv; *.ycv) if any LONW other than 3120E5 is detected (even if the download source is XBS / XI584 / CARE). In this case, an alarm message “HW Config. Failure” is also generated.

ONWORKS

ONMARK

ONWORKS

functionality. Further, all

logo feature fully open

chip other than the

ORKS

chip

ONMARK

identification LONM

Devices which comply with the L there is no L above without the name “L

The XC5010C bears the L FL, and XD50-FCL feature the L application module. The XFL52xB modules bear the L sticker. In addition, all of the aforementioned hardware features the L symbol on the unit package label.

Table 3 provides an overview of the L freely programmable Excel 50 controllers.

NOTE: Configurable L

ARK

-approved devices are identified with the following logos:

ONMARK

Fig. 3. L

Object profile are identified with the LONM

ONMARK

ONWORKS

ONMARK

logos

Interoperability guidelines but for which

ARK

symbol shown

”.

symbol on the front label. The XCL5010, XD50-

ONMARK

symbol on the warning label of the

ONWORKS

ONMARK

functionality of the Excel 500 and

logo on the type

ONMARK

applications for the Excel 50 (applications requiring a particular application module [e.g. XD50-FL-AH03-EN] and configured by Lizard) are L

ONMARK

-compliant, so this feature is affected by neither the new V2.04.xx, V2.05.xx, or V2.06.xx firmware nor the new 3120E5 Neuron chip. Upgrading either the firmware or the Neuron chip (via an enhanced application module) is possible but not necessary.

EN0B-0270GE51 R0307 8

Excel 50/500/800 LONW

ORKS

Mechanisms

Table 3. Controller compatibility (non-LONM

controller type controller firmware

ARK

CPUs/application modules, date code later than week 44 in 2000)

open

LONW

ORKS

functionality

CPU autobinding1 with

XFL52x XFL52xB

CARE LONW

binding

ORKS

LM4W

binding

2.00.xx – 2.03.xx not possible local local not possible not possible

XC5010C, XCL5010

2.04.xx not possible local local/shared not possible not possible

2.06.xx not possible local local/shared not possible not possible

XD50-FL, XD50-FCL 2.04.xx – 2.06.xx not possible not possible not possible not possible not possible

XD50-FL-xxxx-yy2, XD50-FCL-xxxx-yy

The term "local" refers to an operating mode in which a maximum of 16 modules are assigned (automatically) to each controller

and only a single controller is connected to each L

2.00.xx – 2.05.xx possible not possible not possible possible possible

2.06.xx possible not possible not possible possible possible

ONWORKS

bus. The term "shared" means that a maximum of 16 modules are assigned (manually) to each controller, but that multiple controllers can be connected to a single L The term "open" refers to an open L

ONWORKS

bus.

system, i.e. the use of CARE to generate a LONM

ARK

-compliant external interface file (XIF) capable of providing NVs which can be bound to other devices (Excel 50 or Excel 10 controllers, third-party devices); further, the limitation of max. 16 modules per controller can also be exceeded. See also section "Determining the Operating Mode of a New LonWorks System" on page 41 for more-detailed information on these operating modes.

"xxxx-yy" stands for configurable applications, e.g. AH03-EN.

Table 4. Controller compatibility (LONM

controller type controller firmware

XCL8010A2

3.00.xx in use not possible not possible possible possible

3.00.xx not in use not possible not possible not possible not possible

ARK

CPUs/application modules, date code later than week 44 in 2000)

open

LONW

ORKS

functionality

CPU autobinding1 with

XFL52x XFL52xB

CARE LONW

binding

ORKS

LM4W

binding

2.00.xx – 2.03.xx not possible local local not possible not possible

2.04.xx in use not possible shared/open not possible possible XC5010C, XCL5210C, XCL5010

2.04.xx not in use local local/shared not possible possible

2.06.xx in use not possible not possible possible possible

2.06.xx not in use local local/shared not possible not possible

2.04.xx – 2.05.xx in use not possible open not possible possible

XD50-FL, XD50-FCL

2.04.xx – 2.05.xx not in use not possible not possible not possible not possible

2.06.xx in use not possible not possible possible possible

2.06.xx not in use not possible not possible not possible not possible

2.00.xx – 2.05.xx in use not possible not possible not possible possible

XD50-FL-xxxx-yy3, XD50-FCL-xxxx-yy

2.00.xx – 2.05.xx not in use not possible not possible not possible not possible

2.06.xx in use not possible not possible possible possible

2.06.xx not in use not possible not possible not possible not possible

The term "local" refers to an operating mode in which a maximum of 16 modules are assigned (automatically) to each controller

and only a single controller is connected to each L

ONWORKS

bus. The term "shared" means that a maximum of 16 modules are assigned (manually) to each controller, but that multiple controllers can be connected to a single L The term "open" refers to an open L

ONWORKS

bus.

system, i.e. the use of CARE to generate a LONM

ARK

The XCL8010A is likewise not capable of CPU autobinding with Excel 800 I/O modules.

"xxxx-yy" stands for configurable applications.

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

Table 5. Distributed I/O module compatibility

LONW

ORKS

Distributed I/O modules

XFL521, XFL522A, XFL523, XFL524A

Excel 500

V2.00.xx to V2.03.xx

1 controller to which Dist. I/O modules are assigned on single L

ONWORKS

bus; op.

mode: local

Functionality, by controller firmware version

Excel 500

V2.04.xx

1 controller to which Dist. I/O modules are assigned on single L

ONWORKS

bus; op.

mode: local

1 controller to which Dist. I/O modules are assigned on single L mode: local

Excel 500

V2.06.xx

ONWORKS

bus; op.

Excel 800

V3.00.xx

not supported

1 controller to which Dist.

XFL521B, XFL522B, XFL523B, XFL524B

XFL821A, XFL822A,

I/O modules are assigned on single L

ONWORKS

enable this backwardscompatible mode

bus (to

for XFL52xB modules, press L

ONWORKS

service pin while turning HEX switch); op. mode: local

not possible

Full LONW

ORKS

functionality: Multiple Dist. I/O modules and multiple controllers possible on single L

ONWORKS

bus; op.

mode: open

not possible

XFL823A, XFL824A

To cancel the backwards-compatible mode for XFL52xB modules (date code: 0044 or later), thus allowing full LONW

functionality, press and hold down the L

Excel 500 controller with Neuron 3120E5 chip required!

ONWORKS

service pin for at least 3 seconds.

Full L

ONWORKS

functionality: Multiple Dist. I/O modules and multiple controllers possible on single L

ONWORKS

mode: open

Full LONW functionality: Multiple Dist. I/O modules and multiple controllers possible on single L

ONWORKS

mode: open

bus; op.

ORKS

bus; op.

Full L

ONWORKS

functionality: Multiple

Dist. I/O modules and multiple controllers possible on single L

ONWORKS

bus; op.

mode: open

Full L

ONWORKS

functionality: Multiple

Dist. I/O modules and multiple controllers possible on single L

ONWORKS

bus; op.

mode: open

ORKS

NOTE: The compatibility of Distributed I/O Modules featuring manual overrides is not affected by the firmware version or the

Neuron chip version.

EN0B-0270GE51 R0307 10

Excel 50/500/800 LONW

ORKS

Mechanisms

FREELY PROGRAMMABLE LONWORKS EXCEL 50/500/800 CONTROLLERS

Number of NVs supported

Excel 50: The Excel 50's network interface can contain up to 46 NVs (in addition to the Node

Object's NVs).

The Excel 50 will reject applications having more than 46 NVs. In this case, the following system alarm will be issued:

Alarm number: 61; alarm text: “Too many Globals”

Excel 500: The Excel 500's network interface can contain up to 512 NVs (in addition to the

Node Object's NVs).

The Excel 500 supports 128 physical data-points (I/Os) and 256 pseudo datapoints. Every data-point can be mapped to an input NV, or to an output NV, or to both. The data-points can be mapped to a maximum of 512 L theoretical maximum of 381 physical data-points (I/Os) are supported via NVs.

Excel 800: The Excel 800's network interface can contain up to 512 NVs (in addition to the

Node Object's NVs).

The Excel 800 supports 381 data-points in a random mix of physical and pseudo data-points. Every data-point can be mapped to an input NV, or to an output NV, or to both. The data-points can be mapped to a maximum of 512 L

ONWORKS

NVs. A

NVs.

Memory Requirements

The memory requirements (in bytes) can be calculated by adding together the memory requirements attributable to the following individual items:

Default texts (ASPECD, descriptors, alarm texts, engineering units, status texts): The maximum

memory allotted to default texts is 21,780 bytes

On-line changes to the time program All annual programs are automatically erased by the controller when they turn more

than one year old. The maximum memory allotted to on-line changes to the time program is 4,096 bytes.

The time program, itself The first switching point requires 12 bytes, and each additional switching point with

the same switching time requires another 6 bytes. A time interval with an exception day program in the annual program requires 9 bytes. A holiday with an exception day program in the holiday list requires 2 bytes. A today exception for a point requires 17 bytes. A day program requires 21 bytes X no. of switching points X 12. Thus, the total time program requires 35 bytes + (size, in bytes, of all day programs) + (no. of today exceptions X 17 bytes) + (no. of time intervals with an exception X 9 bytes) + (no. of holidays with an exception X 2 bytes).

The CARE application program Assuming one time program, five control loops, five switching tables, CARE

(including RAL, RAP, RAT, RAZ) will require 10,000 bytes. Assuming several time programs, ten control loops, ten switching tables, CARE will require 20,000 bytes.

NOTE: The use of complex ModAL XFMs can further boost that portion of the

memory requirements attributable to the control loops.

Data-points Each data-point requires 67 bytes.

NVs Memory requirements depend upon the number of structural components (n) of

each NV. The maximum memory allotted for all NVs is 2,048 bytes. The NVdependent memory requirements can be calculated as follows: (number of NVs) X (3 bytes + (n X 3 bytes)) For example: Given 100 NVs with four structural components per NV: 100 X (3 bytes + (4 X 3 bytes)) = 1500 bytes

Many-to-one (M-T-O) bindings The memory requirements of many-to-one bindings depends upon the number of

NVs and the number of structural components (n) per NV. The maximum memory requirements due to all many-to-one bindings = 12,800 bytes. The actual memory requirements depend upon whether the NVs are analog or digital, and can be

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

calculated as follows: no. of analog NVs X (9 bytes + no. of analog M-T-O X (4 bytes + 4 bytes)) + no. of digital NVs X (9 bytes + no. of digital M-T-O X (4 bytes + 1 byte) Example: Given ten analog NVs and five digital NVs, each with 20 M-T-O, 10 X (9 bytes + 20 X (4 bytes + 4 bytes) + 5 X (9 bytes + 20 X (4 bytes + 1 byte) = 1690 + 545 = 2235 The maximum memory allotted for all many-to-one bindings is 12,800 bytes.

The remote trend buffer Each trend entry requires 47 bytes. Centrals A, B, and C can each contain a

maximum of 100 trend entries. Further, unused application memory (if any) can be allotted to Central A, thus enabling it to contain more than 100 trend entries. The number of additional trend entries which central A can contain = (128 Kbytes – application size in Kbytes) X 1,024 bytes / 47 bytes

Size constraints, Excel 50/500/600 If the memory requirements amount to less than 110 KB, then the size is OK.

If the memory requirements amount to between 110 and 128 KB and the RAL is greater than 18 KB (in which case RAL will run from the flash memory), then the size is OK.

If the memory requirements amount to between 110 and 128 KB and the RAL is less than 18 KB and the rest of the application is less than 110 KB, then the size is OK.

If the memory requirements amount to between 110 and 128 KB and the RAL is less than 18 KB and the rest of the application is greater than 110 KB, then the application is too large and must be reduced.

If the memory requirements exceed 128 KB, then the application size must be reduced (e.g. by lowering the complexity of the application by reducing the number of or simplifying control loops).

Size constraints, Excel 800 The application without RACL must not exceed 100 KB.

The RACL must not exceed 128 KB.

The application plus RACL must not exceed 192 KB.

Extending the Number of Physical I/Os using NVs

General Typically, one NV will be needed for each physical input and two NVs for each

physical output.

Excel 50 It is possible to extend the number of physical I/Os to more than 22. This is done by

mapping pseudo data-points to one or more of the 46 NVs, and then binding these NVs to physical I/Os on the L

This will allow for

• 46 additional physical inputs, or

• 23 additional physical outputs, or

• a mixture of inputs and outputs.

Excel 500 It is possible to extend the number of physical I/Os to more than 128. This is done

by mapping pseudo data-points to one or more of the 512 NVs, and then binding these NVs to physical I/Os on the L

Note that the 256 pseudo-points available must be split between usage for the application (e.g. set-points or 3 additional physical I/Os. Typically, these pseudo-points are split equally between the two usages.

This will allow for

• 125 additional physical inputs, or

• 62 additional physical outputs, or

• a mixture of inputs and outputs.

Excel 800 It is possible to have a maximum of about 200 physical L

the same principles regarding extending the number of physical I/Os and splitting usage apply as described above for Excel 500.

ONWORKS

-party LONW

network.

ORKS

integration) and usage for

ONWORKS

I/Os. Otherwise,

EN0B-0270GE51 R0307 12

Excel 50/500/800 LONW

ORKS

Mechanisms

Node Object NVs

Fig. 4 presents controller Node Object NVs, categorized according to whether they are mandatory or optional and listing optional configuration properties.

Controller Node Object

type no. 0

input

NV 0

NV 1

input

NV 7

NV 1

input

input NV 2

NV 1

input

input NV 3

NV 1

input

input NV 4

NV 1

nviRequest

SNVT_obj_request

nviRequest

UNVT_uword

SNVT_obj_request

nviRequest

SNVT_time_sec

SNVT_obj_request

nviRequest

SNVT_time_sec

SNVT_obj_request

nviRequest

SNVT_str_asc

SNVT_obj_request

nviRequest

nviInUse

nciHrtBtRcv

nciHrtBtSnd

nciLocation

mandatory

Network

Variables

optional

Network

Variables

optional

configuration

properties

output

NV 1

output

NV 8

output NV 10

output NV 11

input

output

NV 6

NV 1

input

output

NV 9

NV 1

nvoStatus

SNVT_obj_status

nvoAlarm

UNVT_alarm

nvoLocalTime

USNVT_time_stamp

nvoDayOfWeek

SNVT_date_day

nroPgmVer

nviRequest

UNVT_pgm_id

SNVT_obj_request

nroOsVersion

nviRequest

SNVT_str_asc

SNVT_obj_request

nviRequest

input

input NV 5

NV 1

input

NV 12

NV 1

nciDeviceName

SNVT_str_asc

SNVT_obj_request

nciXL500BusSetup

nviRequest

UNVT_XL500BusSetup

SNVT_obj_request

Fig. 4. Controller node object NVs

Table 6 presents information on the L L

ONWORKS

Excel 50/500 controller.

ONWORKS

Node Object NVs in each

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

Table 6. Node Object NVs (left)

NV Field NV Type States / engineering units + range Value

Index

0 nviRequest object_id SNVT_obj_request

RQ_NORMAL RQ_DISABLED

nviRequest object_request SNVT_obj_request

1 nvoStatus SNVT_obj_status

2 nciHrtBtRcv

3 nciHrtBtSnd

4 nciLocation

5 nciDeviceName

6 nroPgmVer id UNVT_pgm_id

nroPgmVer major_ver UNVT_pgm_id 0 nroPgmVer minor_ver UNVT_pgm_id 0 nroPgmVer bug_ver UNVT_pgm_id 0 nroPgmVer node_type UNVT_pgm_id 0

7 nviInUse UNVT_uword

8 nvoAlarm UNVT_alarm

9 nroOsVersion SNVT_str_ascii

10 nvoLocalTime year SNVT_time_stamp

nvoLocalTime month SNVT_time_stamp 0 to 12 nvoLocalTime day SNVT_time_stamp 0 to 31 nvoLocalTime hour SNVT_time_stamp 0 to 23 nvoLocalTime minute SNVT_time_stamp 0 to 59 nvoLocalTime second SNVT_time_stamp 0 to 59

11 nvoDayOfWeek SNVT_date_day

12 nciXL500BusSetup message code BYTE 0 to 99 0x4D nciXL500BusSetup bus ID BYTE 0xFF nciXL500BusSetup controller no. BYTE 0xFF nciXL500BusSetup heartbeat BYTE 0x14 seconds nciXL500BusSetup domain BYTE 0x00 nciXL500BusSetup dom. ID length BYTE 0xFF / unused nciXL500BusSetup dom. ID value BYTE 0

nciXL800BusSetup?

SCPTmaxRcvTime (SNVT_time_sec)

SCPTmaxSendTime (SNVT_time_sec)

SCPTlocation (SNVT_str_asc)

SCPToemType (SNVT_str_asc)

RQ_UPDATE_STATUS RQ_SELF_TEST RQ_UPDATE_ALARM RQ_REPORT_MASK

10 to 150 seconds

empty string

NO_ALARM ALARM_WARM_BOOT ALARM_RACL_ERROR ALARM_POWER_FAIL ALARM_APPLICATION_STOPPED RETURN_TO_NORMAL

0 to 3000

DAY_SUN DAY_MON DAY_TUE DAY_WED DAY_THU DAY_FRI DAY_SAT DAY_NUL

0 1 2 3 4 5

Initialized by CARE (90s default)

Initialized by CARE (60s default)

initialized from controller name in application (unless changed by a LONW tool)

Initialized by CARE

initialized to 65,535 at startup

0 1 2 3 4 128_U

0 1 2 3 4 5 6 0xFF

ORKS

EN0B-0270GE51 R0307 14

Excel 50/500/800 LONW

ORKS

Mechanisms

Table 3. Node Object NVs (right)

Comments

This input NV belongs to the Node Object and provides the mechanism for requesting a particular object within a node. See above, but for object status.

This output NV reports the status of the controller upon request through nviRequest. If bound, a change of data will be sent. If not bound, the data is updated internally, only, and can be polled. This is the configuration property used to control the maximum time that elapses after the last update to certain NVs before these input NVs adopt their default values. For each input NV, CARE can be used to set whether an NV is to be checked according to nciHrtBtRcv, and all mapped NVs are checked in this way by default. If the controller does not receive an update within the specified interval, it will try to poll the output NV from the source device. In this way, the heartbeat mechanism also works for nodes without periodic updates. If the polling also fails, the data-point mapped to this NV is set to NO RESPONSE and the invalid value (if specified) is adopted. If the value of nciHrtBtRcv is changed using a L This is the configuration property used to control the maximum time that expires before the controller automatically sends the current values of certain NVs, even if its value did not change. This provides a heartbeat output NV that can be used by the destination objects to ensure that the node is still healthy. CARE can set whether an NV is to be sent periodically, and all mapped NVs are sent in this way by default. If the value of nciHrtBtSnd is changed using a LONW saved as well. Contains an empty string of 31 bytes that can be used to store installation location information.

Controller or application module name (up to 18 characters). If it is changed by a LONW application changes too, and if the application is saved to Flash memory, the name is saved as well.

Program version ID identifies the LONW program ID. not used not used not used not used This is initialized to 0xFFFF at start-up. It is then set by an engineering tool or other supervisory node that is “logged-on” to the node to prevent concurrent access by two such devices. When the updating of a node's configuration is finished, the initial value is restored. This input NV is stored in RAM and is lost after a restart. When bound, this output NV will be sent whenever a system or application alarm condition occurs. Alarm values 5 through 127 are for application alarms, where data-point alarms are mapped to nvoAlarm using CARE (TRUE for alarm status and FALSE for OK status, with application alarm number assigned). The alarm is added to RETURN_TO_NORMAL (128) when the alarm condition is no longer true.

Contains the controller firmware version number. The current local time of the controller, updated every minute (seconds field always equals 0). When the real-time clock of the controller is changed, it may take up to one minute until that change is reflected in the output NV. See above. See above. See above. See above. See above. Updated with the current day enumerator, typically at midnight. When the real-time clock of the controller is changed, it may take up to one minute until that change is reflected in the output NV.

The message code can be changed in the event of trouble with 3rd-party devices. The bus ID distinguishes between virtual C-buses (0x00 = physical C-bus active, 0xFF = initialized by controller). The controller number is the same as the C-bus controller number (0x00 = communication disabled, 0xFF = initialized by controller). The heartbeat is the time between wink messages. The domain is a flag (0 = 1st domain or 1 = 2nd domain). The domain ID length is valid only for the 2nd domain. The domain ID value is valid only for the 2nd domain.

ONWORKS

network management tool, and if the application is saved to Flash memory, the value is saved as well.

ORKS

network management tool, and if the application is saved to Flash memory, the value is

ORKS

network management tool, the name in the

ORKS

application running in each controller (unique for each controller). Also called network interface

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

Activating and Configuring LonWorks plus BMF

With XL50/500 firmware 2.06.xx and higher, and with Excel 800, the node object will support the configuration property nciXL500BusSetup.

This configuration property defines whether the XL50/500/800 supports

• C-bus and/or standard L

• L

ONWORKS

complete L

plus Building Management Functionality (which employs the

ONTALK

In the event that you opt for L instead, you should use NVs for communication between Excel 50/500/800 controllers. The purpose of this restriction is to limit the traffic load on the L

ONWORKS

bus by avoiding frequent message updating and broadcast messaging

in the Excel 50/500/800 controllers.

CARE-related actions When creating an application using CARE 4.01.03 and higher (or, for Excel 800,

CARE 7.2.xx), you will be called upon to define each individual bus (i.e. group of max. 30 controllers with the same bus ID) as communicating either by means of Cbus and standard L

ONWORKS

the other. This is done in CARE by clicking the (automatically generated) name of each individual bus appearing beneath "Bus", going to the "Properties" pane, and selecting the desired radio button: Select either "C-Bus" for C-bus and standard L

ONWORKS

or "LON-Bus" for LONW

"LON-Bus", CARE will then automatically do the following two things:

• ensure that the LONW

• ensure that no two buses in the same L

ID.

ONWORKS

protocol, including telegrams of the type "explicit message").

ONWORKS

on one hand or by means of LONW

ORKS

bus contains not more than 30 controllers;

plus BMF, global points should not be used;

ORKS

plus BMF on

ORKS

plus BMF, as appropriate. If you choose

ONWORKS

network have the same bus

Lizard If you have created a configurable Excel 50 application using Lizard, you must

define the bus ID using either one of the following two procedures:

• setting the bus ID during the MMI's start-up sequence or

• using EBI, Excelon, or any LON tool to edit the ”bus ID” byte in the

configuration property nciXL500BusSetup.

NOTE: Downloading an application created using CARE 4.01.03 will overwrite the

results of any such procedure.

Table 7. nciXL500BusSetup

attribute type default remark

Message Code BYTE 0x4D

changeable in case of trouble with

party devices

distinguish virtual C-buses

bus ID BYTE 0xFF

0x00 = physical C-bus active 0xFF = initialized by controller same as C-bus Controller no.

controller number BYTE 0xFF

0x00 = communication disabled

0xFF = initialized by controller heartbeat BYTE 0x14 sec time between wink messages domain BYTE 0x00 flag, 0=1st domain or 1=2nd domain

domain ID length BYTE

0xFF / unused

only for 2nd domain

domain ID value BYTE[6] 0 only for 2nd domain

LonWorks Bus ID priority handling Excel 800 and Excel 50/500 firmware 2.06.00 through 2.06.03: The L

ONWORKS

Bus ID setting residing in the controller has priority over and will override any L

ONWORKS

XL50/500 firmware 2.06.04: The L priority over and will override any L

Bus ID setting set using CARE.

ONWORKS

Bus ID setting set using CARE has

Bus ID setting residing in the

controller.

EN0B-0270GE51 R0307 16

Excel 50/500/800 LONW

ORKS

Mechanisms

Standard NVs

Table 8 list the standard LONW controller firmware version 2.06.xx onwards, NVs having a SNVT index of 132 and higher are also supported.

SNVT index

1 SNVT_amp amps 0.1 A 0x7FFF 2 SNVT_amp_mil1 milliamps 0.1 mA 0x7FFF 3 SNVT_angle rads 0.01 rad 0xFFFF 4 SNVT_angle_vel rads per sec 0.1 rad/sec 0x7FFF 5 SNVT_btu_kilo thousands of BTU's 1 KBTU 0xFFFF 6 SNVT_btu_mega millions of BTU's 1 MBTU 0xFFFF 7 SNVT_char_ascii ASCII characters 1 character 8 SNVT_count event count 1 0xFFFF

9 SNVT_count_inc event count 1 0x7FFF 11 SNVT_date_day day names 1 0xFF 13 SNVT_elec_kwh kilowatt-hours 1 kWh 0xFFFF 14 SNVT_elec_whr watt-hours 0.1 Wh 0xFFFF 15 SNVT_flow liters per second 1 l/sec 0xFFFF 16 SNVT_flow_mil milliliters per second 1 ml/sec 0xFFFF 17 SNVT_length meters 0.1 m 0xFFFF 18 SNVT_length_kilo kilometers 0.1 km 0xFFFF 19 SNVT_length_micr microns 0.1 microns 0xFFFF 20 SNVT_length_mil millimeters 0.1 mm 0xFFFF 21 SNVT_lev_cont percentage 0.5 % 0xFF 22 SNVT_lev_disc level names 1 0xFF 23 SNVT_mass grams 0.1 g 0xFFFF 24 SNVT_mass_kilo kilograms 0.1 kg 0xFFFF 25 SNVT_mass_mega tons 0.1 ton 0xFFFF 26 SNVT_mass_mil milligrams 0.1 mg 0xFFFF 27 SNVT_power watts 0.1 W 0xFFFF 28 SNVT_power_kilo kilowatts 0.1 kW 0xFFFF 29 SNVT_ppm parts per million 1 ppm 0xFFFF 30 SNVT_press kilopascals 0.1 kPa 0x7FFF 31 SNVT_res ohms 0.1 Ohm 0xFFFF 32 SNVT_res_kilo kilo-ohms 0.1 kOhm 0xFFFF 33 SNVT_sound_db decibels 0.01 dB 0x7FFF 34 SNVT_speed meters / second 0.1 m/s 0xFFFF 35 SNVT_speed_mil millimeters / second 0.001 m/s 0xFFFF 36 SNVT_str_asc used in Node Object

38 SNVT_telcom

39 SNVT_temp degrees Celsius 0.1 °C 0xFFFF 41 SNVT_vol liters 0.1 liter 0xFFFF 42 SNVT_vol_kilo kiloliters 0.1 kl 0xFFFF 43 SNVT_vol_mil milliliters 0.1 ml 0xFFFF 44 SNVT_volt volts 0.1 V 0x7FFF 45 SNVT_volt_dbmv decibels*millivolts 0.1 db mV 0x7FFF 46 SNVT_volt_kilo kilovolts 0.1 kV 0x7FFF 47 SNVT_volt_mil millivolts 0.1 mV 0x7FFF 48 SNVT_amp_f amps 1 A 0x7F000000 49 SNVT_angle_f rads 1 rad 0x7F000000 50 SNVT_angle_vel_f rads per second 1 rad/sec 0x7F000000 51 SNVT_count_f dimensionless 1 0x7F000000 52 SNVT_count_inc_f dimensionless 1 0x7F000000 53 SNVT_flow_f liters per second float value 0x7F000000 54 SNVT_length_f meters 1 m 0x7F000000 55 SNVT_lev_cont_f percentage 1% 0x7F000000 56 SNVT_mass_f grams 1 0x7F000000 57 SNVT_power_f watts float value 0x7F000000 58 SNVT_ppm_f parts per million float value 0x7F000000

name units/description resolution invalid value

ORKS

NVs (SNVTs) supported for mapping. From

Table 8. Supported SNVTs

telecomm state names

⎯

1 0xFF

EN0B-0270GE51 R0307

Excel 50/500/800 LONW

ORKS

Mechanisms

SNVT

index

59 SNVT_press_f Pascals float value 0x7F000000 60 SNVT_res_f ohms float value 0x7F000000 61 SNVT_sound_db_f decibels float value 0x7F000000 62 SNVT_speed_f meters per second float value 0x7F000000 63 SNVT_temp_f degrees Celsius float value 0x7F000000 64 SNVT_time_f seconds float value 0x7F000000 65 SNVT_vol_f liters float value 0x7F000000 66 SNVT_volt_f volts float value 0x7F000000 67 SNVT_btu_f British Thermal Units float value 0x7F000000 68 SNVT_elec_whr_f watt-hours float value 0x7F000000

69 SNVT_config_src

70 SNVT_color structured 71 SNVT_grammage grams / sq. meter 0.1 g/m2 0xFFFF 72 SNVT_grammage_f grams / sq. meter float value 0x7F000000 75 SNVT_freq_f Hertz float value 0x7F000000 76 SNVT_freq_hz Hertz 0.1 Hz 0xFFFF 77 SNVT_freq_kilohz kilohertz 0.1 kHz 0xFFFF 78 SNVT_freq_milhz megahertz 0.1 mHz 0xFFFF 79 SNVT_lux lux 1 lux 0xFFFF 81 SNVT_lev_percent % of full-scale / ppm 0.005 0x7FFF 82 SNVT_multiplier -- -- 0xFFFF 84 SNVT_time_stamp structured Per NV field 85 SNVT_zerospan structured Per NV field 87 SNVT_elapsed_tm structured Per NV field 91 SNVT_muldiv structured Per NV field 92 SNVT_obj_request structured 93 SNVT_obj_status structured

95 SNVT_switch

97 SNVT_override dimensionless 1 0xFF 98 SNVT_pwr_fact multiplier 0.00005 0x7FFF

99 SNVT_per_fact_f multiplier float value 0x7F000000 100 SNVT_density kilograms / meter3 0.5 kg/m3 0xFFFF 101 SNVT_density_f kilograms / meter3 float value 0x7F000000 102 SNVT_rpm revolutions / minute 1 0xFFFF

103 SNVT_hvac_emerg

104 SNVT_angle_deg degrees of arc 0.02 deg 0x7FFF 105 SNVT_temp_p degrees Celsius 0.01 °C 0x7FFF 106 SNVT_temp_setpt structured Per NV field 107 SNVT_time_sec seconds 0.1 sec 0xFFFF 108 SNVT_hvac_mode HVAC mode names 1 0xFF

109 SNVT_occupancy

110 SNVT_area square millimeters 200 mm2 0xFFFF 111 SNVT_hvac_overid structured 0xFF 112 SNVT_hvac_status structured 0xFF 113 SNVT_angle_deg degrees of arc 0.02 deg 0x7FFF 115 SNVT_scene structured Per NV field 116 SNVT_scene_cfg structured Per NV field 117 SNVT_setting structured Per NV field 118 SNVT_evap_state evaporation states 1 0xFF

119 SNVT_therm_mode

120 SNVT_defr_mode defrost mode names 1 0xFF

121 SNVT_defr_term

122 SNVT_defr_state defrost state names 1 0xFF 123 SNVT_time_min minutes 1 0xFFFF 124 SNVT_time_hour hours 1 0xFFFF 125 SNVT_ph acidity 0.001 pH 0x7FFF 126 SNVT_ph_f acidity (pH) float value 0x7F000000

name units/description resolution invalid value

dimensionless (defining selfinstallation)

structured, but mapped with a single data-point

emergency mode names

occupancy mode names

thermostat mode names

defrost termination names

0xFF

⎯

⎯ ⎯

0xXXFF

1 0xFF

EN0B-0270GE51 R0307 18

+ 42 hidden pages