Danfoss LonWorks in the ECL Comfort Operating instructions

Brand: Danfoss

Model: LonWorks in the ECL Comfort

Type: Operating instructions

ECA 82 LONworks for ECL Comfort 200/300

ECA 82

LONworks in the ECL Comfort 200/300

Instruction

BC-HM

VI.7F.C3.02 / 087R9522

ãDanfoss

02/02

Table of Contents

1 Introduction..................................................................................................5

1.1 Scope..............................................................................................................5

1.2 About the implementation in the LONworks protocol..............................5

1.3 General information......................................................................................5

1.4 ECA 82 compatibility with other options card...........................................5

2 Getting started.............................................................................................6

2.1 Installation......................................................................................................6

2.2 Starting up......................................................................................................7

2.3 XIF file.............................................................................................................8

3 Node object ..................................................................................................9

3.1 Mandatory network variables....................................................................10

3.1.1 1. Node request: Input................................................................. 10

3.1.2 3. Setting time and date: Input .................................................... 11

3.1.3 2. Node status: Output ................................................................ 11

3.1.4 4. Alarm: Output .......................................................................... 11

4 Electronic controller object ...................................................................15

4.1 5 & 11 Set points concerning circuit I & II: Input...................................17

4.2 8. Setpoints concerning hotwater setting: input .....................................17

4.3 15 & 16 Control of valves and mode: Input ............................................18

4.4 21 Control of pumps: input ........................................................................18

4.5 55. Control of the weekplan ......................................................................19

4.6 34 & 36 Actual power input from node in the network. Input...............21

4.7 36 & 37 Actual flow input from a node in the network. Input ...............21

4.8 Handling energy and flow input from the network. ................................21

4.8.1 Setting Time Constants ............................................................... 22

4.8.2 Setting the Flow or Energy Reference......................................... 22

4.9 53 Outdoor temperature input...................................................................23

4.10 54 Outdoor temperature input...................................................................24

4.11 General handling of outdoor temperature input.....................................24

4.12 6, 7 & 17- 20 & 46 - 49 Temperature sensors 1 - 10: Output ..............24

Page 2 of 51

4.13 9 & 12 Setpoint concerning circuit I & II: Output....................................25

4.14 10. Setpoints concerning hotwater setting: Output................................26

4.15 13 & 14 Status of valves, optimiser status and Relative Humidity......26

4.16 22. Reading off time and date: Output ....................................................27

4.17 33 Pump status ...........................................................................................27

4.18 56 Reporting weekplan in ECL Comfort. Output....................................28

4.19 57 & 58 Controller mode status circuit I & II. Output.............................28

4.20 42 & 43 Actual power delivered from pulse module. Output................29

4.21 44 & 45 Actual flow delivered from pulse module. Output ..................29

4.22 27 - 30 Sensor references 3 - 6. Output..................................................29

5 Manufacture-defined section.................................................................31

5.1 23 & 24. Analog outputs 1 & 2: Input.......................................................32

5.2 25 & 26. Analog inputs 1 & 2: Output ......................................................32

5.3 19 & 20. Parameter command and response. .......................................32

5.3.1 Learn field ................................................................................... 33

5.3.2 Selector field ............................................................................... 33

5.3.3 Value field ................................................................................... 33

5.3.4 Parameters grey side of ECL card circuit I. ................................. 36

5.3.5 Parameters yellow side of ECL card circuit I. .............................. 37

5.3.6 Parameters grey side of ECL card circuit II. ................................ 39

5.3.7 Parameters yellow side of ECL card circuit II. ............................. 40

5.3.8 ECL Comfort status information. ................................................. 40

5.3.8.1 Selector 250 details..................................................................... 40

5.3.8.2 Selector 251 details..................................................................... 41

5.3.8.3 Selector 252 details..................................................................... 41

5.3.9 ECA 82 set-up and details........................................................... 41

5.3.9.1 Software version in ECA 82. ....................................................... 41

5.3.9.2 SendHeartBeat............................................................................ 41

5.3.9.3 Voltage update. ........................................................................... 42

5.3.9.4 ECL checks for adjustments........................................................ 42

5.3.9.5 Application loaded in the ECL Comfort........................................ 42

5.3.10 Alarm limit configuration. ............................................................. 43

5.3.11 Accumulated energy or flow pre load. ......................................... 44

6 Rules of thumb for network design in heating systems................45

6.1 Considerations before implementation of communication. ..................45

6.1.1 What are the basic needs for information.................................... 45

6.1.2 What's the final number of nodes in the network......................... 46

6.1.2.1 Parallel network........................................................................... 47

Page 3 of 51

6.1.2.2 Backbone network....................................................................... 47

6.1.3 Bandwidth considerations. .......................................................... 47

6.1.3.1 Total number of controllers in network. ....................................... 49

6.2 Update of SNVT from ECL Comfort........................................................ 51

6.2.1 Minimise copy of data on the network. ........................................ 51

Page 4 of 51

1 Introduction

1.1 Scope.

This ECA 82 option for ECL Comfort is based on EchelonsÒ LONworksÒ.

The ECA 82 can be used in ECL Comfort 200 and 300, the notation ECL Comfort

is used from here.

1.2 About the implementation in the LONworks protocol.

The following instruction describes the parameters that can be communicated

between a LONworks network and ECL Comfort. The build-up of the physical

network is not described. For further information's see Echelons homepage:

http://www.echelon.com/.

The instruction is divided into three main sections:

1. The Lonmark ® Node object is used to the extent that functions are supported

in ECL Comfort. The functions from the node object that are supported in ECL

Comfort are described in “Node object”.

2. The basic parameters behind weather compensation are described separately

in the section on the weather compensator object.

3. Parameters that are special for ECL Comfort are described separately in the

manufacture-defined section.

1.3 General information.

1. The possibilities for communication depend on the application loaded in the

ECL Comfort. This ECA 82 is designed to fit all applications card. Hardware

configuration settings and future parameters might not be supported.

2. Only one kind of communication can be used in the ECL Comfort. It is not

possible to run RS232 together with ECA82 communication.

1.4 ECA 82 compatibility with other options card.

ECA 80 ECA 81 ECA 83 ECA 84 ECA 85 ECA 86 ECA 87 ECA 88

Yes No Yes No Yes Yes No Yes

Page 5 of 51

2 Getting started

The ECA 82 can be used together with ECL Comfort 200 and 300. It is not

possible to use the ECA 82 on ECL Comfort 100.

Further information on the operation of ECL Comfort is contained in the instruction

supplied with the ECL Card.

2.1 Installation

Step 1:

Dismount the cover plate B on the back of the ECL Comfort using a small slice

cutter nipper.

Step 2:

Mount the ECA82 in the slides and press it gently into the connector on the ECL

Comfort print board.

Page 6 of 51

Step 3:

Mount the new cover plate B, which is delivered with the option card.

Pin connection:

· 1: LON data 1. Left side pin of the connector.

· 2: Middle pin of the connector. Do not use!

· 3: LON data 2. Right side pin of the connector.

The FTT10 transceiver is based on a balanced bus. LON data 1 and 2 can be

reversed.

2.2 Starting up

When starting up the ECA 82, a period of about 30 seconds will elapse during

which the database from the controller will be copied. During this starting up period

it is not possible to come into contact with the ECA 82, neither from ECL Comfort

nor from the network. The starting-up period will occur on the reset/power up

controller/ECA 82, and when an application change is made in ECL Comfort.

After starting up, the following parameters can be activated via the ECL Comfort

HMI:

· Parameter 196 in circuit I is the service pin.

· Parameter 197 in circuit I is the ECA 82 reset.

Parameter 196 and 197 can be can access by scrolling down through the

parameters on the installer page (grey page) with the arrow down key.

The parameters can be activated/deactivated with the +/- keys (see instructions for

application card).

At wink command, the display will flash until any key on ECL Comfort is pressed.

When updating parameters in ECL Comfort the values must bee in a workable

range. If they fall outside the range, they will be rejected.

Page 7 of 51

2.3 XIF file

The XIF file can be found on the internet

Before using a xif file check out the software version in the ECA 82. The software

version can be read directly on the memory IC on the ECA 82 card see Figure 1

and Table 1. Software version can also be found using the network in parameter

nviParamCmd/nvoParamResp, selector 1000 see 5.3.9.1 Software version in ECA

82.

Using the ECA82 require a XIF file which fit the software version.

See software

version on the

backside of the

ECA 82

Figure 1 Find ECA 82 software version.

Table 1 ECA 82 software versions and XIF file.

ECA 82 software

version

Text on IC label XIF file name

1.0 087B1564 VER 1.0 ECL10.XIF

1.1 087B1564 VER 1.1 ECL11.XIF

1.2 087B1564 VER 1.2 ECL12.XIF

1.3 087B1564 VER 1.3 ECL13.XIF

1.4 087B1564 VER 1.4 ECL14.XIF

1.5 087B1564 VER 1.5 ECL15.XIF

1.6 087B1564 VER 1.6 ECL16.XIF

The XIF file can also be loaded directly from the ECA 82 via the LON network

using e.g. LONMaker for windows ®.

The XIF files can be downloaded from the internet:

http://bc.danfoss.com/htm/download_area.asp

Page 8 of 51

3 Node object

The node object is used for controlling and establishing the status of the node. It is

thus possible to ask for and receive the status of the actual condition of the node.

Mandatory Nework variables

Optional network variables

Input

Network

Variables

Output

Network

Variables

Node Object

Type #0

nv 2

nvoStatus

SNVT_obj_status

nv 1

nviRequest

SNVT_obj_request

nv 4

nvoAlarm

SNVT_alarm

nv 3

nviTimeSet

SNVT_time_stamp

Figure 2: Node object

Table 2: SNVT input

NV NR

Name SNVT Type

(SNVT Index)

Class Description

1 nviRequest SNVT_obj_request Ram Request object status

3 nviTimeSet SNVT_time_stamp Ram Set time and date

Table 3: SNVT output

NV NR

Name SNVT Type

(SNVT Index)

Class Description

2 nvoStatus SNVT_obj_status Ram Status of node

4 nvoAlarm SNVT_Alarm Ram Alarm reporting

Page 9 of 51

3.1 Mandatory network variables

3.1.1 1. Node request: Input

network input SNVT_obj_request nviRequest;

Valid range

The following parameters are supported:

0: RQ_NORMAL: Set controller in normal mode after override (manual mode). The

following functions are only active in manual mode.

SNVT_setting nviValve_1 & 2. (Valve control)

SNVT_state nviControl. (Pump control)

Returning to normal from manual mode set circuit I and II in automatic mode.

1: RQ_DISABLED: Not supported.

2: RQ_UPDATE_STATUS. Update object status: nvo_obj_status and nvoTime.

3: RQ_SELF_TEST: Not supported.

4: RQ_UPDATE_ALARM. Sends actual status on nvoAlarm out on the network via

SNVT_alarm (alarm on/off).

5: RQ_REPORT_MASK: Not supported.

6: RQ_OVERRIDE. Not supported.

7: RQ_ENABLE: Not supported.

8: RQ_RMV_OVERRIDE. Not supported

9: RQ_CLEAR_STATUS: Delete all bits in SNVT_obj_status nvoStatus.

10: RQ_CLEAR_ALARM: Delete alarms entered in nvoAlarm SNVT_alarm

11: RQ_ALARM_NOTIFY_ENABLED: Enable alarm reporting in nvoAlarm.

12: RQ_ALARM_NOTIFY_DISABLED: Disable alarm reporting in nvoAlarm.

13: RQ_MANUAL_CTRL. Set controller in manual mode in all circuits. *

14: RQ_REMOTE_CTRL: Not supported.

15: RQ_PROGRAM: Not supported.

* = Note: If the controller is parked in line B at users side (yellow) the valve and

pump status is overridden by the controller, in order to give the locally positioned

user a possibility make a manual override of the controller HMI. The override from

controller HMI can be avoided in ECL Comfort 300 by removing the smart card

from controller. Without smart card the controller will lock the keyboard after 5

minutes. Line B users side is designed to secure that a manual control can be

done locally directly without distortions form the network.

Manual control affect both controller circuits. If the controller is in manual mode

and a new mode circuit 1 is chosen from nviValve_1 the controller mode for circuit

will be set to automatic mode. In shift from manual mode the not chosen circuit will

be set to automatic mode.

Page 10 of 51

3.1.2 3. Setting time and date: Input

network input SNVT_time_stamp nviTimeset;

Here, the actual time and date entered in the ECL can be set.

Valid Range

Year 1996 - 2026

Month 1-12

Day 1-31 *

Hour 0-23

Minute 0-59

*The number of days depends on the month. If an attempt is made to set more

days than there are in the month, the request will be rejected and nvoAlarm

SNVT_ALARM is updated (The alarm function have to be enabled to get an alarm

see 3.1.1).

3.1.3 2. Node status: Output

network output SNVT_obj_status nvoStatus;

SNVT uses this input to report on the node status.

The following points are supported:

· Over_range: Set if an input value from the network is higher than the max.

permissible value.

· Under_range: Set if an input value from the network is under the min.

permissible value.

· Manual_control: Set if the controller has been set in manual mode from the

network, or if the controller is set in manual mode from ECL Comfort HMI. Use

the SNVT in 4.3 to return from manual mode.

· In_alarm: Set if an alarm has been set.

· In_override: Set if the controller overrides between day/night from the network.

· alarm_notify_disabled: Alarm reporting in nvoAlarm disabled.

3.1.4 4. Alarm: Output

network output SNVT_Alarm nvoAlarm;

The possibilities for alarm reporting are:

· Input value from SNVT out of range alarm.

· Alarm on all physical sensors

· Alarm sensor - reference 2-8.

· Alarm on relative humidity level.

· Bit reporting of 19 alarm conditions simultaneously.

Page 11 of 51

· Indication of sensor - reference alarm on time: 0 min, 10 min, 30 min and 60

min.

· Time and date for last registered alarm occurrence.

· History buffer with the latest 4 different SNVT alarm indexes.

The alarm function is enabled from nviRequest.RQ_ALARM_NOTIFY_ENABLE

and disabled from nviRequest.RQ_ALARM_NOTIFY_DISABLE

All alarm levels are configured in 5.3.10 Alarm limit configuration

If via nviTimeSet SNVT_time_stamp an illegal date or year is entered, an alarm

type 1 will be activated and year or day shows the illegal value.

Location:

Here the temperature values that generate alarms are reported. The value is a

signed integer.

Location [0] = Alarm value for sensor 1.

Location [1] = Alarm value for sensor/reference 2.

Location [2] = Alarm value for sensor/reference 3.

Location [3] = Alarm value for sensor/reference 4.

Location [4] = Alarm value for sensor/reference 5.

Location [5] = Alarm value for sensor/reference 6.

Alarm type:

Value Identifier Notes

0 AL_NO_CONDITION No alarm condition present.

1 AL_ALM_CONDITION Invalid value set in nviTimeset.

9 AL_LOW_LMT_ALM_1 Alarm low limit alarm 1: Attempt to set parameter

under legal value.

10 AL_LOW_LMT_ALM_2 Alarm low limit alarm 2: Value under configured

level has expired.

11 AL_HIGH_LMT_ALM_1 Alarm high limits alarm 1: Attempt to set

parameter higher than legal value.

12 AL_HIGH_LMT_ALM_2 Alarm high limits alarm 2: Value higher than

configured level has expired.

0xFF AL_NUL Value not available

Priority level:

Value Identifier Notes

0 PR_LEVEL_0 Lowest alarm priority level. Alarm reported on Sensor -

Reference 2-8 value.

1 PR_LEVEL_1 Alarm reports Sensor - Reference 2-8 value has been

active for 10 minutes.

2 PR_LEVEL_2 Alarm reports Sensor - Reference 2-8 value has been

active for 30 minutes.

Page 12 of 51

3 PR_LEVEL_3 Highest alarm priority level. Alarm reports Sensor -

Reference 2-8 value has been active for 60 minutes.

0xff PR_NULL No alarms present on Sensor - reference 2-8.

index_to_SNVT Here the SNVT index to the latest expired alarm is presented.

Value[4] This field is used for alarm reporting. Each alarm status is represented by

1 bit. 1 means alarm on, 0 means alarm off. 19 alarms can be reported the

structure for decoding the alarm report can be read in Table 4 - Table 7.

Table 4 nvoAlarm.value [0]

NvoAlarm.value

[0] bit nr:

Alarm status at: Alarm limit configured in

selector:

0 Temperature sensor 1 1018

1 Temperature sensor 2 1019

2 Temperature sensor 3 1020

3 Temperature sensor 4 1021

4 Temperature sensor 5 1022

5 Temperature sensor 6 1023

6 Temperature sensor 7 (ECA 86) 1024

7 Temperature sensor 8 (ECA 86) 1025

Table 5 nvoAlarm.value [1]

NvoAlarm.value

[1] bit nr:

Alarm status at: Alarm limit configured in

selector:

0 Temperature sensor 9 (ECA 86) 1026

1 Temperature sensor 10 (ECA 86) 1027

2 Sensor 2 - reference 2 1028

3 Sensor 3 - reference 3 1029

4 Sensor 4 - reference 4 1030

5 Sensor 5 - reference 5 1031

6 Sensor 6 - reference 6 1032

7 Sensor 7 - reference 7 (ECA 86) 1033

Table 6 nvoAlarm.value [2]

NvoAlarm.value

[2] bit nr:

Alarm status at: Alarm limit configured in:

0 Sensor 8 - reference 8 (ECA 86) Selector 1034

1 Relative humidity 1 (ECA 62) Selector 1035

2 Relative humidity 2 (ECA 62) Selector 1036

3 - 7 Reserved bits Do not use this information!

Table 7 nvoAlarm.value [3]

NvoAlarm.value

[3] bit nr:

Alarm status at: Alarm generated in:

0 - 7 Reserved byte Do not use this information!

Page 13 of 51

year, month, day, hour, minute:

Here the time for the latest alarm experience is reported. The time is taken from

the ECL Comfort watch.

alarm_limit[4]

This is a 4 value buffer that indicates the latest different 4 alarms occurrence. The

SNVT index is added to the buffer when a new alarm expires.

Update.

Sensor 1-6: 2 * SendHeartBeat. Default 10 sec.

Sensor - Reference 2-6: 4 * SendHeartBeat. Default 20 sec.

Sensor 6-10 and Sensor - reference 7 and 8 (ECA 86): 8 * SendHeartBeat. Default

40 sec.

Clear alarm status.

The entire alarm status can be cleared using nviRequest.RQ_CLEAR_alarm(10),

see 3.1.1 for further information.

Page 14 of 51

4 Electronic controller object

Here the parameters necessary to provide weather compensation are described.

The values involved are divided into mandatory network variables and optional

network variables.

nviTSetptRoom_1

SNVT tem

set

15, 16

nviValve_1 & 2

SNVT_setting

Network

Variables

Out

Network

Variables

ECL Comfort

Electronic controller object

nvoTime

SNVT_time_stamp

nviTSetptRoom_2

SNVT_temp_setpt

nvoTSetptRoom_1

SNVT

tem

set

17-20

nvoSensorNr_3 - 6

SNVT_temp

nviTSetptH W

SNVT tem

set

nvoTSetptHW

SNVT tem

set

6, 7

nvoSensorNr_1 - 2

SNVT_temp

nvoSetptRoom_2

SNVT_temp_setpt

nviControl

SNVT_state

nvoWeekplan

SNVT_str_asc

nvoControl

SNVT_state

nviWeekplan

SNVT_str_asc

34, 36

nviActPower_1 & 2

SNVT_power_f

13, 14

nvoValve_1 & 2

SNVT_setting

35, 37

nviActFlow_1 & 2

SNVT_flow_f

42, 43

nvoActPower_1 & 2

SNVT_power_f

44, 45

nvoActFlow_1 & 2

SNVT_flow_f

46-49

nvoSensorNr_7 - 10

SNVT_temp

27-30

nvoRef_Nr_3 - 6

SNVT_temp

nviOutdoortemp

SNVT_temp

nviOutdoortemp_p

SNVT_temp_p

57, 58

nvoMode_1 & 2

SNVT_hvac_mode

Figure 3: Object details

Page 15 of 51

Table 8: SNVT input

NV NR

(index)

Name SNVT Type

Description

5 nviSetptRoom_1 SNVT_temp_s

etpt

Setpoints concerning circuit I

8 nviSetptHW SNVT_temp_s

etpt

Hot water setpoint.

11 nviSetptRoom_2 SNVT_temp_s

etpt

Setpoints concerning circuit II

15, 16 nviValve_1 & 2 SNVT_setting Control of valves (triac)

21 nviControl SNVT_state Control of pumps (relays)

55 nviWeekplan SNVT_str_asc Setting of weekplan all circuits

34, 36 nviActPower_1 & 2 SNVT_power_f Power input from LON device (heatmeter).

35, 37 nviActFlow_1 & 2 SNVT_flow_f Flow input from LON device (flowmeter).

53 nviOutdoortemp SNVT_temp Outdoor temperature input from LON

network.

54 nviOutdoortemp_p SNVT_temp_p Outdoor temperature input from LON

network.

Table 9: SNVT output details

(index

)

Name SNVT Type

Send

Heart

Beat

Description

6, 7 nvoSensorNr_1 –

SNVT_temp *2 Sensor values

9 nvoTSetptRoom_1 SNVT_temp_setpt No Setpoints concerning circuit I

10 nvoTSetptHW SNVT_temp_setpt No Setpoints concerning hotwater.

12 nvoTSetptRoom_2 SNVT_temp_setpt No Setpoints concerning circuit II.

13,

nvoValve_1 & 2 SNVT_setting 5 sec Status of valves

up/down/stopped.

17-20 nvoSensorNr_3 –

SNVT_temp *2 Sensor values 3 - 6.

22 nvoTime SNVT_time_stamp *8 Time and date set in ECL

Comfort

33 nvoControl SNVT_state 5 sec Status of pumps (relays).

56 nvoWeekplan SNVT_str_asc No Weekplan setting in all circuits.

57,

nvoMode_1 & 2 SNVT_hvac_mode 5 sec Controller mode circuit I & II

42,

nvoActPower_1&

SNVT_power_f *8 Actual power

44,

nvoActFlow_1 & 2 SNVT_flow_f *8 Actual flow

46-49 nvoSensorNr_7-10 SNVT_temp *8 Sensor values from ECA 86

27-30 nvoRef_Nr_3 - 6 SNVT_temp *4 References for sensor 3 - 6.

The SendHeartBeat value can be adjusted in 5.3.9.2 page 41.

Page 16 of 51

4.1 5 & 11 Set points concerning circuit I & II: Input

network input SNVT_temp_setpt nviTSetptRoom_1;

network input SNVT_temp_setpt nviTSetptRoom_2;

Field Definitions

Field Parameter Valid Range Resolution

occupied_cool Proportional band 1.00.. 250.00 K 1.00

standby_cool Parallel displacement -9.00 .. 9.00 K 1.00

unoccupied_cool Summer cut out 10.00 .. 30.00 °C 1.00

occupied_heat Setpoint comfort period 10.00 .. 30.00 °C 1.00

standby_heat Heat curve 0.20 .. 3.40 0.10

unoccupied_heat Setpoint reduced period 10.00 .. 30.00 °C 1.00

Validation of data.

If input is set to at value outside the valid area, the setting is ignored in ECL

Comfort and nvoTSetptRoom_1 or 2. The error is reported in

nvoStatus.under_range / over_range is set.

Default value.

Default value set in the SNVT: All fields = 0 at start-up.

4.2 8. Setpoints concerning hotwater setting: input

network input SNVT_temp_setpt nviTSetptHW;

Field Definitions

Field Parameter Valid Range Resolution

occupied_cool Hot water temp. Differential 1.00 .. 250.00 °C 1.00

standby_cool Charging temp. - Relative 1.00 .. 30.00 K 1.00

unoccupied_cool Differential 1 - Cut-out temp. 1.00 .. 30.00 K 1.00

occupied_heat Setpoint comfort period 10.00 .. 110.00 °C 1.00

standby_heat Differential 2 - Cut-in temp. 1.00 .. 30.00 K 1.00

unoccupied_heat Setpoint reduced period 10.00 .. 110.00 °C 1.00

Default value

Default value set in the SNVT: All fields = 0 at start-up.

Page 17 of 51

4.3 15 & 16 Control of valves and mode: Input

network input SNVT_setting nviValve_1;

network input SNVT_setting nviValve_2;

From here the valve and controller mode can be controlled.

nviValve_1 control valve 1 (triac 1 and 2) and the controller mode circuit I.

nviValve_2 control valve 2 (triac 3 and 4) and the controller mode circuit II.

function:

0 SET OFF => Night mode

1 SET ON => day mode

2 SET DOWN => valve down

3 SET UP => valve up

4 SET STOP => stop valve

5 SET STATE => automatic mode

6 SET NUL => standby mode

setting

: Not used.

rotation

: Not used.

Note. The valve can only be controlled if the controller is in manual mode.

Manual mode (for all circuits) can be entered in nviRequest, see 3.1.1.1. Node

request: Input.

4.4 21 Control of pumps: input

network input SNVT_state nviControl;

From here the pumps (relay) can be controlled.

Type of relay: NC (normally closed).

Valid range

For all values: 1 = relay on, (no connection), 0 = relay off, (connection).

Bit 0: Standard relay 1

Bit 1: Standard relay 2

Bit 2: Standard relay 3

Other values are not supported.

Relays placed on options card (ECA 80 & ECA 86) can't be controlled from the

ECA 82. The application in ECL Comfort always control options relays.

Page 18 of 51

Note: The pumps can only be controlled if the controller is in manual mode.

Manual mode (for all circuits) can be entered in nviRequest, see 3.1.1.1. Node

request: Input page 10 or directly at the ECL Comfort.

In some applications the ECL Comfort overwrite the specified setting from the

network. In sequence controller's (C75) non-valid relay combinations is overwritten

by the ECL Comfort. Don’t use this override function in application F05 and F06.

4.5 55. Control of the weekplan

network input SNVT_str_asc nviWeekplan;

From here new weekplan can be set and the actual weekplan already set in

controller can be requested.

Request status of the weekplan already set in controller for readout in

nvoWeekplan.

Field ascii[0] - ascii[29] must contain the value 0x00;

Field ascii[30] must contain an value indicating which weekplan to report.

Table 10 Request weekplan setting

Field ascii[30] value Weekplan area

0x10 Weekdays in circuit I

0x11 Weekend in circuit I

0x20 Weekdays in circuit II

0x21 Weekend in circuit II and all days

circuit 3

The week plan is build up in ½ hour intervals. The week plan can contain a

maximum of 3 periods a day. Each field ascii[0] - [29] is a char build of 8 bit. Each

of these bit represents ½ hour in the week plan. The exact position can be found

using Table 11.

Page 19 of 51

Table 11 Weekday decoding

Field ascii[30] = 0x10 or 0x20 ascii[30] = 0x11 Ascii[30] = 0x21

ascii[0] Monday 3.59 - 0.00 Saturday 3.59 - 0.00 Saturday 3.59 - 0.00

ascii[1] Monday 7.59 - 4.00 Saturday 7.59 - 4.00 Saturday 7.59 - 4.00

ascii[2] Monday 11.59 - 8.00 Saturday 11.59 - 8.00 Saturday 11.59 - 8.00

ascii[3] Monday 15.59 - 12.00 Saturday 15.59 - 12.00 Saturday 15.59 - 12.00

ascii[4] Monday 19.59 - 16.00 Saturday 19.59 - 16.00 Saturday 19.59 - 16.00

ascii[5] Monday 23.59 - 20.00 Saturday 23.59 - 20.00 Saturday 23.59 - 20.00

ascii[6] Tuesday 3.59 - 0.00 Sunday 3.59 - 0.00 Sunday 3.59 - 0.00

ascii[7] Tuesday 7.59 - 4.00 Sunday 7.59 - 4.00 Sunday 7.59 - 4.00

ascii[8] Tuesday 11.59 - 8.00 Sunday 11.59 - 8.00 Sunday 11.59 - 8.00

ascii[9] Tuesday 15.59 - 12.00 Sunday 15.59 - 12.00 Sunday 15.59 - 12.00

ascii[10] Tuesday 19.59 - 16.00 Sunday 19.59 - 16.00 Sunday 19.59 - 16.00

ascii[11] Tuesday 23.59 - 20.00 Sunday 23.59 - 20.00 Sunday 23.59 - 20.00

ascii[12] Wednesday 3.59 - 0.00 All days 3.59 - 0.00

Circuit 3

ascii[13] Wednesday 7.59 - 4.00 All days 7.59 - 4.00

Circuit 3

ascii[14] Wednesday 11.59 - 8.00 All days 11.59 - 8.00

Circuit 3

ascii[15] Wednesday 15.59 - 12.00 All days 15.59 - 12.00

Circuit 3

ascii[16] Wednesday 19.59 - 16.00 All days 19.59 - 16.00

Circuit 3

ascii[17] Wednesday 23.59 - 20.00 All days 23.59 - 20.00

Circuit 3

ascii[18] Thursday 3.59 - 0.00

ascii[19] Thursday 7.59 - 4.00

ascii[20] Thursday 11.59 - 8.00

ascii[21] Thursday 15.59 - 12.00

ascii[22] Thursday 19.59 - 16.00

ascii[23] Thursday 23.59 - 20.00

ascii[24] Friday 3.59 - 0.00

ascii[25] Friday 7.59 - 4.00

ascii[26] Friday 11.59 - 8.00

ascii[27] Friday 15.59 - 12.00

ascii[28] Friday 19.59 - 16.00

ascii[29] Friday 23.59 - 20.00

ascii[30] Information about the circuit for which the data apply see Table 10 for

decoding.

Error codes are reported in nvoWeekplan see 4.18 page 28.

Error causes: No value set in ascii[30] or to many periods set in a day.

Page 20 of 51

Page is loading ...

Danfoss LonWorks in the ECL Comfort Operating instructions

Danfoss LonWorks in the ECL Comfort Operating instructions

Danfoss LonWorks in the ECL Comfort Operating instructions

Related papers

Other documents