Danfoss ECA 85 Operating instructions

Danfoss
Brand
Danfoss
Model
ECA 85
Type
Operating instructions
INSTRUCTION FOR M-BUS TO LON GATEWAY
ECA 85
M-BUS to LON Gateway
User Manual
BC-HM VI.7F.R1.02 / 087R9582 ã Danfoss 00/09
TABLE OF CONTENTS:
1. INTRODUCTION....................................................................................................................................................... 3
2. GETTING STARTED WITH THE M-BUS TO LON GATEWAY ........................................................................ 4
2.1 INSTALLATION OF THE M-BUS TO LON GATEWAY............................................................................................ 4
2.2 STARTING UP........................................................................................................................................................ 4
2.3 CONNECTION BETWEEN ECL AND HEAT METER / BINDING OF SNVT’S........................................................... 5
2.4 STARTING UP........................................................................................................................................................ 5
2.5 XIF-FILE ............................................................................................................................................................... 5
3. NODE OBJECT......................................................................................................................................................... 6
3.1 NODE OBJECT NETWORK VARIABLES.................................................................................................................. 7
3.1.1 Nv 1. Node request: Input......................................................................................................................... 7
3.1.2 Nv 2. Node status: Output........................................................................................................................ 7
3.1.3 Nv 3. Setting time and date: Input........................................................................................................... 8
4. HEAT METER OBJECT........................................................................................................................................... 9
4.1 HEATMETER OBJECT NETWORK VARIABLES...................................................................................................... 10
4.1.1 Nv 4. Set time for Update Rate on LON Network: Input.................................................................. 11
4.1.2 Nv 5. Accumulated Energy / Total energy consumption: Output.................................................... 11
4.1.3 Nv 6. Accumulated Volume / Total flow volume: Output.................................................................. 11
4.1.4 Nv 7. Actual Power consumption / Momentary Power: Output....................................................... 11
4.1.5 Nv 8. Actual Volume / Momentary Flow: Output............................................................................... 12
4.1.6 Nv 9. Actual Flow Temperature: Output............................................................................................. 12
4.1.7 Nv 10. Actual Return Temperature: Output....................................................................................... 12
4.1.8 Nv 11. Actual difference temperature: Output................................................................................... 12
4.1.9 Nv 12. Total ON time in the Heatmeter: Output................................................................................ 13
4.1.10 Nv 13. Update rate set in the Heatmeter: Output. ............................................................................ 13
4.1.11 Nv 14. Time and date set in heatmeter: Output................................................................................ 13
4.1.12 Nv 15. Manufacture ID: Output............................................................................................................ 13
4.1.13 Nv 16. Heatmeter ID: Output............................................................................................................... 14
4.1.14 Nv 17. Customer number Output........................................................................................................ 14
2 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
1. Introduction
This M-Bus / LON Gateway is based on Echelons LonWorks. The M-BUS to LON
Gateway is developed according to the standard for M-BUS Heat Meters CEN/TC 176, EN
1434-3.
The following instruction describes the parameters that can be communicated between a
LonWorks network and different M-BUS Heat Meters. The build-up of the physical network
is not described.
The instructions are divided into three main sections:
1. The Lonmark Node object is used to the extent that functions are supported in the M-
BUS to LON Gateway. The functions from the node object supported in M-BUS to LON
Gateway are described in section 3, “Node object”.
2. The basic parameters behind Heat Meters are described separately in the section on
the Heat Meter object.
The M-Bus to LON Gateway is normally used in two different applications (Figure 1):
1. In stand-alone applications with a single controller where there is a demand for
limitation of either the maximum flow or the maximum energy consumption.
2. In systems with visualisation option where it should be possible to view all the
data from the heat meter via a LON Network. The data that is possible to view
are e.g.: Flow temperatures, actual flow/energy, accumulated flow/energy, etc. It
must be noted that in such configuration connected to a visualisation computer it
is still possible locally to make limitation of either flow or energy.
ECL 2000
Terminator
LON
Bindings
M-Bus to
LON Gateway
Heat Meter
M-Bus
To other equipment or
main station
230 V a.c.
Figure 1 Application example set-up.
BC-HM VI.7F.R1.02 ã Danfoss 00/09 3
2. Getting started with the M-BUS to LON Gateway
The M-BUS to LON Gateway is converting the data processed in a Heat Meter with M-BUS interface
to the respective SNVT’s to be used on a LONWorks network.
The Gateway can be divided into three parts:
1. The LON part which consists of the LON components and which takes care of the physical
interface to the LON Network.
2. The converter part which is a microprocessor taking care of the calculations between the M-Bus
data format and the LON data format.
3. The M-Bus part which consists of the M-Bus components and takes care of the physical interface
to the M-Bus Heat Meter.
The M-BUS to LON Gateway is for the time being only working with heatmeters of Danfoss type:
Infocal 5 and heatmeters from Kamstrup type: MULTICAL
âIII.
2.1 Installation of the M-BUS to LON Gateway
Network Management Tools use an interface definition of the M-Bus to LON Gateway application to
generate network configuration information and to install the M-Bus to LON Gateway on a network.
The interface definition may either be read from the M-Bus to LON Gateway, or from an External
Interface File (*.xif). The *.xif-file contains a complete definition of the M-Bus to LON Gateway
network variable names and types, information about messages, bit rate, and other information
needed to install the node on a network.
During installation, the network management tool can identify the M-Bus to LON Gateway in three
different ways:
When activating the Service Pin on the M-Bus to LON Gateway will send a Service Pin Message to
the network. The Service Pin Message contains the unique ID of the M-Bus to LON Gateway, called
the Neuron ID. The Network Management Tool uses the ID to identify the physical position of the
node in the network.
The M-Bus to LON Gateway is installed non-configured (no network image). The network
management tool uses a network management message to get the ID from the non-configured M-Bus
to LON Gateway. If there is more than one non-configured M-Bus to LON Gateway or other LON
devices the network management tool may send a Wink command to each non-configured M-Bus to
LON Gateway or other LON device, one at a time. M-Bus to LON Gateways or other LON devices,
which receives this message and are able to handle this will identify themselves. The M-Bus to LON
Gateway controls a light (LED), then it will turn on and off the light, when it receives a Wink command
to identify its physical location. An installer identifies the location of the winking M-Bus to LON
Gateway to the network management tool.
The installer can manually enter the Neuron ID to the network management tool through keyboard
entry.
2.2 Starting up
The LON to M-Bus Gateway is supplied without cables for power, LON and M-Bus connection.
The cable for 230 VAC has to be the type specified for the country of use.
Cables for the M-Bus connection: Please refer to the manual for the Heat Meter. Otherwise cable of
type: JYStY N*2*0.8 mm – maximum 50 meters can be used.
The Twisted pair cable for the LON Network, please refer to the manual found on the Danfoss
Internet:
Search for “LON Works in ECL 200/300 and 2000” on the link: www.bc.danfoss.com
The polarity is not fixed for neither the M-Bus- nor the LON connection.
4 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
2.3 Connection between ECL and Heat Meter / Binding of SNVT’s
It is possible to transfer the following types of data from the Heat Meter via the M-Bus to LON
Gateway to the ECL 2000 (and later on, to the ECL Comfort 200/300):
• Actual Flow: SNVT_flow_f – nviActFlow [l/s]
• Actual Energy/Power: SNVT_power_f – nviActPower [W]
• Accumulatede Energy: SNVT_elec_whr_f – nviAccEnergy [Wh]
NOTE:
The respective nvo from the M-Bus to LON Gateway MUST BE connected (bound) to the
respective nvi of the ECL with a Binding Tool Software installed on a PC connected to the
LON Network through an adapter in order to transfer the data from the Gateway to the ECL.
Only network variables of the same type can be connected (bound) together. Further
information can be found on Danfoss Building Controls Homepage. Search for “LON Works in
ECL 200/300 and 2000” on the link: www.bc.danfoss.com
There are many different binding tools available so please refer to the respective manual for the
binding tool used.
If you are using the Binding Tool “ALTO” from SYSMIK GmbH, the manual: ALTO Version 1.5:
Manual "ALTO - Getting started" can be downloaded in both English and German via Internet from
the following link: http://www.sysmik.de/e_index.html
.
2.4 Starting up
When starting up the M-Bus to LON Gateway, the default period of updating data from Heat Meter is
set to 1 minute. The default communication speed from Gateway to Heat Meter is set to 300 baud.
Pressing the Service Pin button on the front side, activates the Service Pin.
To reset the M-BUS to LON Gateway, the power has to be turned off for a short moment.
When a “wink” command is sent via the LONWorks Network, the LED on the front side will
flash.
2.5 XIF-file
The XIF-file is located on the Danfoss Internet and can be downloaded.
Before download, check the software version in the M-Bus to LON Gateway. The software version
can be read directly on the memory IC in the M-Bus to LON Gateway.
BC-HM VI.7F.R1.02 ã Danfoss 00/09 5
3. Node object
The node object is used for controlling and establishing the status of the node = M-Bus to LON
Gateway. It is thus possible to ask for and receive the status of the actual condition of the node.
Mandatory Nework
Optional network
Input
Network
Variables
Output
Network
Variables
Node Object
Type #0
nv 2
nvoStatus
SNVT_obj_status
nv 1
nviRequest
SNVT_obj_request
nv 3
nviTimeSet
SNVT_time_stamp
Figure 1 Node object
Table 1 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 2 SNVT Output.
NV nr
Name SNVT Type
(SNVT Index)
Class Description
2 NvoStatus SNVT_obj_status Ram Status of node
6 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
3.1 Node Object network variables
3.1.1 Nv 1. Node request: Input
Network input SNVT_obj_request nviRequest;
SNVT Number: 92. Internal index: 0.
Measurement: Object Request
Type Category: Structure.
Type Size: 3 bytes.
The following parameters are supported:
Value Identifier Notes
0 RQ_NORMAL not used
1 RQ_DISABLED not used
2 RQ_UPDATE_STATUS Report object status in nvoStatus.
3 RQ_SELF_TEST Self test runs and updates nvoStatus.
4 RQ_UPDATE_ALARM not used
5 RQ_REPORT_MASK not used
6 RQ_OVERRIDE 1 manual reading of data on M-bus slave
7 RQ_ENABLE not used
8 RQ_RMV_OVERRIDE not used
9 RQ_CLEAR_STATUS Clear object status (nvoStatus).
10 RQ_CLEAR_ALARM not used
11 RQ_ALARM_NOTIFY_ENABLED not used
12 RQ_ALARM_NOTIFY_DISABLED not used
13 RQ_MANUAL_CTRL not used
14 RQ_REMOTE_CTRL not used
15 RQ_PROGRAM not used
0xFF RQ_NUL Value not available
3.1.2 Nv 2. Node status: Output
SNVT_obj_status nvoStatus
SNVT Number: 93. Internal index: 1.
Measurement: Object Status
Type Category: Structure
Type Size: 6 bytes
Field Definitions
Field Valid Range Notes
object_id 16-bit object ID Not used
invalid_id boolean0..1 Not used
invalid_request boolean0..1 Not used
disabled boolean0..1 Not used
out_of_limits boolean0..1 Not used
open_circuit boolean0..1 Not used
out_of_service boolean0..1 1 means object not functional no
contact to M-bus.
mechanical_fault boolean0..1 Not used
feedback_failure boolean0..1 1 No answer setting up the slave
over_range boolean0..1 1 means max range for
BC-HM VI.7F.R1.02 ã Danfoss 00/09 7
SNVT_time_min nviUpdate is
exceeded. This bit is cleared from
SNVT_obj_request nviRequesT
RQ_CLEAR_STATUS. or if a new valid
value is entered.
under_range boolean0..1 1 means min range for SNVT_time_min
nviUpdate is exceeded. This bit is
cleared from SNVT_obj_request
nviRequest RQ_CLEAR_STATUS or if
a new valid value is entered.
electrical_fault boolean0..1 1 Checksum or parity error
unable_to_measure boolean0..1 1 means I/O line failure, no contact to
M-bus
comm_failure boolean0..1 1 means network communications
failure
fail_self_test boolean0..1 1 means self test failed.
lf_test_in_progress boolean0..1 Not used.
locked_out boolean0..1 Not used.
manual_control boolean0..1 Not used.
in_alarm boolean0..1 Not used.
in_override boolean0..1 Not used.
report_mask boolean0..1 Not used.
programming_mode boolean0..1 Not used.
programming_fail boolean0..1 Not used.
alarm_notify_disabled boolean0..1 Not used.
3.1.3 Nv 3. Setting time and date: Input
SNVT_time_stamp nviTimeSet
SNVT Number: 84. Internal index: 2.
Measurement: Time Stamp
Type Category: Structure
Type Size: 7 bytes
Valid range
Year 2000 - 3000
Month 1-12
Day 1-31
Hour 0-23
Minute 0-59
8 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
4. Heat meter object
nv 4
nviUpdate_rate
SNVT_time_min
Heat met er Obj ect
nv 14
nvoTime
SNVT_time_stamp
nv 6
nvoAccFlow
SNVT_vol_f
nv 10
nvoReturn_temp
SNVT_temp_p
nv 9
nvoFlow_temp
SNVT_temp_p
nv 7
nvoActPower
SNVT_power_f
nv 5
nvoAccEnergy
SNVT_elec_whr_f
nv 8
nvoActFlow
SNVT_flow_f
nv 11
nvoTemp_di ff
SNVT_temp_p
nv 12
nvoOn_time
SNVT_time_f
nv 13
nvoUpdat eRate
SNVT_time_min
nv 15
nvoManufactureID
SNVT_count
nv 16
nvoID
SNVT_count_f
nv 17
nvoCustomer
SNVT_count_f
Figure 2 Heatmeter object.
BC-HM VI.7F.R1.02 ã Danfoss 00/09 9
Table 1 SNVT input details
NV nr
Name SNVT Type
(SNVT Index)
Description
4 nviUpdate_rate SNVT_timer_min Time between update of M-Bus data area 1 - 1000 minutes
Table 2 SNVT Output details
NV nr
Name SNVT Type
(SNVT Index)
Description
5 nvoAccEnergy SNVT_elec_whr_f Accumulated energy measured in Watt hours
6 nvoAccFlow SNVT_vol_f Accumulated flow measured in litre.
7 nvoActPower SNVT_power_f Actual Power measured in Watt.
8 nvoAct_flow SNVT_flow_f Actual flow measured in litre/second.
9 nvoFlow_temp SNVT_temp_p Actual flow temperature measured in ° Celsius.
10 nvoReturn_temp SNVT_temp_p Actual return temperature measured in ° Celsius.
11 nvoTemp_diff SNVT_temp_p Actual difference temperature measured in ° Celsius.
12 nvoOn_time SNVT_time_f The total number of ON time in heatmeter measured in sec.
13 nvoUpdateRate SNVT_time_min Update rate set in gateway measured in minutes.
14 nvoTime SNVT_time_stamp Time and date set in Heatmeter.
15 nvoManufactureID SNVT_count Manufacture ID number represented in decimal.
16 nvoID SNVT_count_f Heatmeter ID number in decimal.
17 nvoCustomer SNVT_count_f Customer number set in heatmeter represented in decimal.
4.1 Heatmeter object network variables.
Values measured on the heatmeter are only updated at the rate, which specified in nviUpdate_rate.
The time set in this nvi determines how often the Gateway will ask for new data in the Heat Meter. This
time must not be set too low if the Heat Meter is supplied with batteries, but if the ECL is using the Heat
Meter data for regulation/limitation of the flow or energy it also has to be set often enough. The
regulation / limitation function of the ECL naturally depends on the update rats specified in the
Gateway. If the poll time of the energy/flow SNVT’s in the ECL is set faster than the update rate on the
M-Bus, the SNVT’s will always be updated with the last read value on the M-Bus.
However we recommend the poll time on the ECL is set equal to ½ Update rate for the M-Bus.
Invalid data / no data on the LON bus can be caused of a missing support of data on the M-Bus from
the heatmeter.
10 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
4.1.1 Nv 4. Set time for Update Rate on LON Network: Input.
SNVT_time_min nviUpdate_rate
SNVT Number: 123. Internal index: 3.
Measurement: Minutes
Type Category: Fixed Point Scalar - unsigned long
Type Size: 2 bytes.
Valid Range (Resolution):
1 – 1000 minutes (1 minute) are accepted in the node.
Default value = 1 minute.
Values out of area will not be used in node, false value result in an over
range / under range bit will be set in the SNVT_obj_status nvoStatus. This
bit can cleared manually from SNVT_oj_request nviRequest 9
RQ_CLEAR_STATUS. Or by entering a new valid value.
4.1.2 Nv 5. Accumulated Energy / Total energy consumption: Output.
SNVT_elec_whr_f nvoAccEnergy
SNVT Number: 57. Internal index: 4
Measurement: Accumulated Energy
Type Category: Floating Point Scalar
Type Size: 4 bytes.
Valid Range (Resolution): 0 - 1E38 Watt hours.
The value –1E38 represents invalid data.
4.1.3 Nv 6. Accumulated Volume / Total flow volume: Output.
SNVT_vol_f nvoAccFlow
SNVT Number: 65. Internal index: 5.
Measurement: Accumulated flow.
Type Category: Floating Point Scalar.
Type Size: 4 bytes.
Valid Range (Resolution): 0 .. 1E38 l.
The value –1E38 represents invalid data.
4.1.4 Nv 7. Actual Power consumption / Momentary Power: Output.
SNVT_power_f nvoActPower
SNVT Number: 57. Internal index: 6.
Measurement: Power.
Type Category: Floating Point Scalar.
Type Size: 4 bytes.
Valid Range (Resolution): 0 .. 1E38 Watts.
BC-HM VI.7F.R1.02 ã Danfoss 00/09 11
The value –1E38 represents invalid data.
4.1.5 Nv 8. Actual Volume / Momentary Flow: Output.
SNVT_flow_f nvoActFlow.
SNVT Number: 53. Internal index: 7.
Measurement: Actual flow.
Type Category: Floating Point Scalar.
Type Size: 4 bytes.
Valid Range (Resolution): 0 - 1E38 l/sec.
The value –1E38 represents invalid data.
4.1.6 Nv 9. Actual Flow Temperature: Output.
SNVT_temp_p nvoFlow_temp
SNVT Number: 105. Internal index: 8.
Measurement: Temperature.
Type Category: Fixed Point Scalar - signed long.
Type Size: 2 bytes.
Valid Range (Resolution): -273.17 .. +327.66
°C (0.01 °C).
The value 0x7FFF hex represents invalid data.
4.1.7 Nv 10. Actual Return Temperature: Output.
SNVT_temp_p nvoReturn_temp
Internal index: 9.
The structure is the same as in 4.1.6 Nv 9. Actual Flow Temperature: Output.
4.1.8 Nv 11. Actual difference temperature: Output.
SNVT_temp_p nvoTemp_diff
Internal index: 10.
The structure is the same as in 4.1.6 Nv 9. Actual Flow Temperature: Output.
12 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
4.1.9 Nv 12. Total ON time in the Heatmeter: Output.
SNVT_time_f nvoOn_time
SNVT Number: 64. Internal index: 11.
Type Category: Floating Point Scalar.
Type Size: 4 bytes.
Valid Range (Resolution): 0 .. 1E38 sec.
The value -1E38 represents invalid data.
4.1.10 Nv 13. Update rate set in the Heatmeter: Output.
SNVT_time_min nvoUpdate_rate
SNVT Number: 64. Internal index: 12.
Type Category: Floating Point Scalar
Type Size: 4 bytes
Valid Range (Resolution): 0 .. 1E38 sec
The value -1E38 represents invalid data.
The actual ON time in the heatmeter is represented in seconds.
4.1.11 Nv 14. Time and date set in heatmeter: Output.
SNVT_time_stamp nvoTime
SNVT Number: 84. Internal index: 13.
Measurement: Time and date.
Type Category: Structure.
Type Size: 7 bytes.
Field Definitions
Field Units Valid Range Notes
year year 2000 .. 3000 (years AD) 0 means year not specified.
month month 0 .. 12 0 means month not specified
day day 0 .. 31 0 means day not specified
hour hour 0 .. 23 Only updated if supported in
heatmeter.
minute minute 0 .. 59 Only updated if supported in
heatmeter.
second second 0 .. 59. Seconds are not supported.
This field is updated if the informations are included in a normal reading from
the M-bus. Otherwise it is updated when time and date is set fro nviTimeSet.
4.1.12 Nv 15. Manufacture ID: Output.
SNVT_count nvoManufactureID
SNVT Number: 8. Internal index: 14.
BC-HM VI.7F.R1.02 ã Danfoss 00/09 13
Measurement: Event Count.
Type Category: Fixed Point Scalar - unsigned long.
Type Size: 2 bytes.
Valid Range (Resolution): 0 .. 65,535 counts (1 count).
Default value = 0.
Here the manufacture identification number is represented as a decimal
value.
4.1.13 Nv 16. Heatmeter ID: Output.
SNVT_count_f nvoID
SNVT Number: 51. Internal index: 15.
Measurement: Event Count.
Type Category: Floating Point Scalar.
Type Size: 4 bytes.
Valid Range (Resolution): 0 .. 1E38 counts.
-1E38 represents invalid value.
Here the Heatmeter identification number is represented as a decimal value.
4.1.14 Nv 17. Customer number Output.
SNVT_count_f nvoCustomer
SNVT Number: 51. Internal index: 16.
Measurement: Event Count.
Type Category: Floating Point Scalar.
Type Size: 4 bytes.
Valid Range (Resolution): 0 .. 1E38 counts.
-1E38 represents invalid value.
Here the Customer number set in the Heatmeter is represented as a
decimal value.
14 VI.7F.R1.02 ã Danfoss 00/09 BC-HM
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14

Danfoss ECA 85 Operating instructions

Danfoss
Brand
Danfoss
Model
ECA 85
Type
Operating instructions
Download PDF
report

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI

Related papers

Other documents