anton eder gmbh - eder heizung · eder control-electronics: multicontrol basic circuit board, type...

Instruction manual

Modbus RTUfield bus module

ANTON EDER GMBHWeyerstraße 350

A-5733 Bramberg

www.eder-heizung.at

Ver.06/2020-en

Table of contents

Table of contents

1. General

1.1 Description

. Scope of delivery2

3. Bus module

3.1. Hardware ports, switches

3.1.1. Connector to Modbus network (1. interface)RTU RS

3.1.2. Connector supply voltage

3.1.3. Connector to multicontrol electronics (2. interface)RS

3.1.4. Power supply

3.2. indicator lightsLED

3.3. Switches

3.3.1. Termination (1. and 2. serial interface)

3.3.2. Rotary coding switches Modbus- , S4 (High) + S5 (Low)ID

3.3.3. Rotary coding switches S6 + S7 (serial interface to device)EDER

4. Mounting

5. Wiring diagram

5.1. Legend

5.2. Wiring diagram - connection of the bus module

6. Commissioning

6.1. Activation of the bus module in multicontrol device set-up

6.2. Configuration of the bus module

7. Data transfer

7.1. General

7.1.1. data transfer from the multicontrol device to the Modbus- masterRTU

7.1.2. data transfer from the Modbus master to the multicontrol deviceRTU

7.2. Data types

7.3. Bit significance

7.4. Bus module Modbus Output Register

7.5. Bus module Modbus Input Register

8. Notes

2

DisclaimerWe improve our products permanently and so we reserve the right to make modifications

anytime and without previous announcements. We do not assume any guarantee for the

correctness and completeness of this document.

Any claims, particularly claims for damages and loss of profit or financial losses must be

excluded!

1. General

1.1. Description

The Modbus field bus module (hereinafter called „bus module”) enables the connection ofRTUthe multicontrol resp. topcontrol series control electronics to a Modbus network.EDER RTU

In this application the bus module is a gateway and acts as Modbus Slave. It can be used withRTUevery Modbus Master which complies to the Modbus standard.RTU RTUThe connection between the multicontrol control electronics and the bus module is made via theRS PP232 interface of the multicontrol processor board ( ).

The Modbus interface of the bus module transfers data acc. to the Modbus protocol.RTU

The Modbus address of the bus module is set via two rotary coding switches (S4 / S5)

The usage resp. the implementation of the bus module presupposes that the user is familiar withthe commissioning and the programming of Modbus devices.The bus module acts as „ module”.IO

1. General

ECONECON

NOTE!

Figures in this document can vary due to model and configuration of the deliveredmulticontrol device.

i

ECON

INFORMATION!

This document refers to multicontrol and topcontrol series devices with software versionV1.26 of the processor board. Different software versions can lead to slight differences inoperation resp. the version of the device. To ensure an appropriate function of the busmodule, the software version of the processor board must be V1.22 or higher!

i

3

2. Scope of delivery

2. Scope of delivery

instruction manual

connection cable

cable gland PG13,5

ECONECON

NOTE!

The data transfer of the 232 interface of the multicontrol processor board is describedRSin chapters 7.4. and 7.5.Sending of the data from the 232 interface happens acc. to 7.4.RSReceiving of the data at the 232 interface happens acc. to 7.5.RSThis way of data transfer can also be used without a field bus module but with anappropriate 232 remote station or with suitable converters from 232 to the requiredRS RSphysical interface (e.g. with a converter 232 to 485).RS RS

i

Ver.04/2018-en

instruction manual

Modbus RTUfield bus module

ANTON EDER GMBHWeyerstraße 350

A-5733 Bramberg

www.eder-heizung.at

bus module bus module holding plate

incl. mounting screws

4

3. Bus module

3. Bus module

3.1. Hardware ports, switches

3.1.1. Connector to Modbus network (1. interface)RTU RS

The plug ”-X1” is available on the top side of the device. The 4-pin screw-type connector (-X1:terminal 4 ... 7) is used for connecting to the Modbus -network.RTU

The 3-pin screw-type connector (-X1: terminal 1 ... 3) is not used (internally necessary duringinitial configuration of the busmodule using it‘s config mode: S4 & S5 in position„ ”).FF

Pin assignement -X1 (3-pole + 4-pole screw-type plug connector)

plug -X1 (RS485 Modbus interface, terminal 4 ... 7)

plug -X2 (supply voltage)

rotary coding switchModbus-IDS4 (High) S5 (Low)

plug -X3 (RS232 interface)

Pin No. Name Function

1 Rx232 not required

2 Tx232 not required

3 AP GND- not required

4 Rx422+ (485+) Receive signal

5 Rx422- (485-) Receive signal

6 Tx 422+ (485+) Transmit signal

7 Tx 422- (485-) Transmit signal

5

3.1.2. Connector supply voltage

Pin assignment -X2 (4-pole screw-type plug connector; bottom side, back)

3.1.3. Connector to multicontrol electronics (2. interface)RS

The plug ”-X3" for the serial 232 interface (connection to the multicontrol/topcontrolRSprocessor board) is available on the bottom side of the device.

Pin assignment -X3 (3-pole screw-type plug connector)

3.1.4. Power supply

The bus module must be powered with 10-33 . The voltage supply is made through theVDC4-pole screw-plug connector -X2 at the bottom side of the device.Please note that the bus module must not be operated with voltage.AC

3.2. indicator lightsLED

The bus module features 8 s with the following significance:LED

Description Color Significance

LED (Bus) Power green Supply voltage 2. interfaceRS

LED (Bus) State red/green Interface state 2. interfaceRS

LED Power green Supply voltage

LED State red/green General error bus module

LED 1 / 2 / 4 / 8 (Error Nr / SelectID )

green The error number is displayed ( s flash,LEDonly important if the ”state”LEDsimultaneously lights red)

3. Bus module


1 UB (Pwr) 10..33 Volt supply voltage / DC

2 0 V (Pwr) 0 Volt supply voltage / DC

3 Rx Debug not required

4 Tx Debug not required


1 Rx 232 Receive signal

2 Tx 232 Transmit signal

3 AP GND- Application Ground

4 ... 7 RS RS422 ( 485) not required

6

3.3. Switches

The bus module features 8 switches (on its front side) with the following functions:

3.3.1. Termination (1. and 2. serial interface)

If the bus module is operated as the physically first or last device in a 485-bus or as 422, thereRSmust be a bus termination at this bus module. In order to do this the termination switch is set toposition . The resistor (150 ) integrated in the bus module is activated.ON �

In all other cases, the switch remains in position .OFF

3.3.2. Rotary coding switch Modbus- , S4 (High) + S5 (Low)ID

With these two switches the bus module‘s Modbus address is set in hexadecimal notation(01h...F7h).Setting of the Modbus address:The Modbus address is set in hexadecimal digits 01h…F7h (matches the Modbus addresses1 ... 247 decimal).

Example:Modbus- 26 decimal = 1A hexadecimalIDThe switch ”Modbus- High” must be set to 1 and the switch ”Modbus- Low” must be set toID IDA. If the rotary coding switch is set to a value between 1 and 247, the bus module uses thisModbus- (translation from decimal to hexadecimal see the following table).ID

3. Bus module

Name Description

Termination Rx422 (Application) Switchable Rx422-terminating resistor for 1. serialinterface (Modbus side)

Termination Tx422 (Application) Switchable Tx422- or 485-terminating resistor forRS1. serial interface (Modbus side)

Rotary coding switch S4 ID High for 1. serial interface (Modbus side)

Rotary coding switch S5 ID Low for 1. serial interface (Modbus side)

Rotary coding switch S6 ID High for 2. serial interface (not relevant)

Rotary coding switch S7 ID Low for 2. serial interface (not relevant)

Termination Rx422 (Fieldbus) Switchable Rx422-terminating resistor for 2. serialinterface

Termination Tx422 (Fieldbus) Switchable Tx422- or 485-terminating resistor forRS2. serial interface

7

Translation table from decimal to hexadecimal:

3.3.3. Rotary coding switches S6 + S7 (serial interface to device)EDER

The setting of these two switches is not relevant for the application which is explained in thisdocument. Ideally the switches should be left in position ”00” (both S6 and S7 in position ”0”).

3. Bus module

coding-switch„S4" (high)

coding-switch„S5" (low)

Adress „hex” Adress „dec”

0 1 01h 1

0 2 02h 2

... ... ... ...

0 9 09h 9

0 A 0Ah 10

0 B 0Bh 11

... ... ... ...

0 F 0Fh 15

1 0 10h 16

... ... ... ...

1 A 01A 26

... ... ... ...

7 D 7Dh 125

... ... ... ...

F 7 F7h 247

8

4. Mounting

Step 1Dismantle the cover - Open the 4 fasteners and lift the cover until it unhinges at the upper

hangers and pull it forward.

Step 2Disconnect power supply to multicontrol device.

CAUTION! It must be ensured that the disconnection of the power supply is allowed,depending on the actual operating situation of the multicontrol device. This is especiallyimportant if the device is already in operation and the bus module must be retrofitted.

Step 3Open the operating panel (release the 4 plastic screws (1) ) and replace the blind cap in the

bottom part of the operating panel with the delivered PG13,5 cable gland (2).

4. Mounting

fig.: multicontrol

fig.: picocontrol

1

1

2

3

1

1

2

fig.: multicontrol fig.: picocontrol

1

1

9

2

Step 4Plug the connection cable into the bus module and place the module into the bottom part of the

operating panel.

Attach the 232-plug of the connection cable (4-pole plug with coding pins) into the not usedRS

socket at the processor board (labelled with 232).RS

Insert the Modbus cable through the 13,5 cable gland (mounted in step 3) and plug it into thePG

4-pole plug X1 (Pin 04 .. 07) (connection see 3.1.3).

multi/topcontrol-devices:

4-pole plug (-X2)

3-pole plug (-X3)

4-pole connection to the multicontrolbasic circuit board (remains unchanged)

Modbus cableto Modbus RTUMaster (on site)

4. Mounting

bus module

holding plate

plug -X1 (Pin 04 .. 07)4-pole plug (RS232) bus module

connection cable

cable glandPG13,5

10

picocontrol-devices:

Step 5Reassemble the components in reverse order (cover operating panel (close the 4 plastic screws) ,

cover/plate) and supply the device with power again.

5. Wiring diagram

5.1. Legend

4-pole connection to the multicontrolbasic circuit board (remains unchanged)

drawn: 04.10.2016 Blassnig

reviewed:

approved:

size: A4 Revision: -

-A1

-A2

-A11 Modbus field bus moduleRTU

LEGEND

Wiring diagram - addition Modbus RTU

marking description

eder control-electronics: multicontrol basic circuit board, type 200331

eder control-electronics: processor board multi/topcontrol, type 10ABCO

4. mounting / 5. wiring diagram

4-pole plug (-X2)

3-pole plug (-X3)

bus module

holding plate

4-pole plug (RS232) bus module

connection cable

Modbus cableto Modbus RTUMaster (on site)

plug -X1 (Pin 04 .. 07)

cable glandPG13,5

11

5. Wiring diagram

5.2. Wiring diagram - connection of the bus module

12

6. Commissioning

6.1. Activation of the bus module in multicontrol device set-up

Go to user level 3.

User level 3 can be unlocked in menu “settings” - “code input”

code for user level 3:

User level 3 - menu structure:

user level 3 Grayed-out menu items already are accessible in lower user levels and described there

/))) actions/))) settings* /))) ...* .))) device set-up* /))) ...* .))) communication* /))) ...

* .))) Busmodule/Webmodul activate!�

/))) manual mode.))) code input

6.2. Configuration of the bus module

user level 3 Grayed-out menu items already are accessible in lower user levels and described there

/))) actions/))) settings* /))) ...* /))) Busmodule/Webmodul 1)

* * /))) enable receiving* * /))) enable device 2)

* * .))) ext. setpoint 2,3)

* .))) .../))) manual mode.))) code input

1) only if bus module is enabled

2) only if receiving is enabled

3) only in topcontrol

6. Commissioning

F1F1 F2F2

�� !

13

user level 3 settings Busmodule/Webmodul� � �

enable receiving „no” (default setting)

Data reception via the bus module is deactivated.

All data sent from Modbus to the multicontrol control via the bus

module are not considered.

„yes”Enables the data reception from Modbus. All data sent from Modbus

to the multicontrol control via the bus module are processed. This

will allow the execution of specified actions via the Modbus.

Details to the data reception see chapter 7.5. bus module Modbus

Input Register.

enable device „no” (default setting)

The enabling of the device via the bus module is deactivated.

„yes”The enabling of the device via the bus module is activated.

Thus the device function can be disabled resp. enabled via the bus

module.

General information on device enabling:If device enabling is locked, the multicontrol control electronics detects the external

deactivation and all components like pumps and valves are switched off. Though the

measurement of pressure, level, temperature as well as the output of all messages remain

activated. Among all other messages (e.g. analog signalling, binary signalling) the contacts

”warning” and ”fault” also remain functional.

The deactivation of the device function via device enabling can easily be recognized by the

green flashing (one-second intervals) at key 1. This allows to recognize immediately that theLED

device is even switched on via the key 1 but it is locked externally via the device enabling.

The following table shows the enabling of the device function depending on the possible

settings and status requests.

6. Commissioning

14

Table: Enabling of the device function

6. Commissioning

enable contactactivated(settings ->

device set-up ->enable contact)

[ is available /not available ]

enable contactstatus

(potential freecontact, Pin 82 at

basic circuit board)

[ On / Off ]

device enabling -bus activated

(settings ->busmodule ->enable device)

[ Yes / No ]

device enablingbus status

[ True / False ]

device functionenabled

[ Yes / No ]

not available Off No False Yes

not available Off No True Yes

not available Off Yes False No

not available Off Yes True Yes

not available On No False Yes

not available On No True Yes

not available On Yes False No

not available On Yes True Yes

available Off No False No

available Off No True No

available Off Yes False No

available Off Yes True No

available On No False Yes

available On No True Yes

available On Yes False No

available On Yes True Yes

ECON

INFORMATION!

The operation on the device with the keys 0 and 1 always has priority.If the device is deactivated with the key 0 and the red next to the key lights, theLEDdevice function is always deactivated, independent from the status of the enable contactor the bus.

i

15

ext. „no” (default setting)setpoint 1)

External setting of the setpoint of the upper working pressure via the

bus module is deactivated.

All setpoint values sent from the bus module are not considered by

the topcontrol control electronics.

„yes”External setting of the setpoint of the upper working pressure via the

bus module is activated.

All setpoint values sent from the bus module are considered by the

topcontrol control electronics and set for the upper working

pressure.

Details to the external setting of the setpoint see instruction manual

”topcontrol as a supplement to , -_1” - chapter 6 -TCM MCK MCM

external setpoint.

1) only in topcontrol

ECONECON

NOTE!

The external setting of the setpoint is only available in topcontrol series devices!

The external setting via the bus module has priority over the analog external setting ofthe setpoint. Independent from the analog external setting (device set-up ext.�

setpoint) the set value of the bus gets used as setpoint for the upper working pressure.

i

6. Commissioning

16

7. Data transfer

7.1. General

The bus module supports data transfer in both directions (sending and receiving).

Modbus telegrams of the on-site urgently necessary Modbus master get answered. The bus

module acts as a slave and is absolutely passive on the Modbus. It responds only on demand of

the master.

CAUTION!Simultaneous sending and receiving is not permitted. The period between the sequential

transfer cycles must be at least 1 second, independent from the direction. Otherwise problems

with the data processing and malfunctions of the multicontrol device can occur.

Modbus interface data:RTUphysical interface: 485Rs

baud rate: 9,6 kbit/s1)

1) The baud rate of the Modbus interface of the bus module is set to 9,6 kbit/s ex factory. If a different baud rateRTU

is desired in the course of project planning, the configuration of the bus module must be changed - changing of

the configuration only in consultation with the technical department.EDER

Possible baud rates of the interface: 9600, 19200, 38400, 57600, 115200.

7.1.1. Data transfer from the multicontrol device to the Modbus masterRTU 2)

The processor board of the multicontrol device sends data in one-second intervals via its 232RS

interface to the 232 interface of the bus module. This requires the activation of the dataRS

transfer (see 6.1. Activation of the bus module in multicontrol device set-up).

Data transfer from the processor board to the bus module:interface type: 232Rs

transfer rate: 38,4 kbit/s

protocol: transparent, see 7.4. and 7.5.

start bit: 1

data bit: 8

stop bit: 1

parity: none

number of data bytes / transfer cycle: 192 Byte

7. Data transfer

17

The bus module transfers the data (192 Byte, received via the 232 interface and stored in aRS

buffer) on request to the Modbus master.RTU

The buffered data get updated (overwritten) if new data are sent by the processor board.

Deletion of the buffered data happens only in voltage-free state.

7.1.2. Data transfer from the Modbus master to the multicontrol deviceRTU 2)

The data transfer from the Modbus master to the bus module and subsequently to the

multicontrol processor board enables the execution of specified actions and the setting of

setpoint values. This requires the enabled receiving of the processor board (see 6.2.).

The data transfer to the bus modules must be projected on the Modbus masters side. During

project development it must be considered that exact 32 Bytes (acc. to the specifications of data

register 2) must be transfered per transfer cycle (see 7.5. Bus module Input Register). Time

interval between 2 cycles: at least 1 second!

It is recommended to send the currently desired data periodically from the Modbus master to the

bus module and to change the value of the "Byte 31: Send trigger" each time the data is sent.

Every change from byte 31 to the value sent before reliably triggers a transmission of the data

from the bus module to the multicontrol processor board. In the case of external setpoint

specification, it is also recommended that the Modbus master periodically compares the actual

setpoint received from the bus module with the setpoint sent by it, as these must be identical

after successful acceptance.

Actions (e.g. fault acknowledgement) are performed by changing the signal state from " " toOFF

" ". After the action has been performed, the signal status must be reset to " " (Keying:ON OFF

e.g. 2 s to ON and then again to OFF)

2 A Modbus master could be a Modbus compatible control system or a superior building management system.)This Modbus master is never in scope of delivery of - it always must be provided and projected on site.EDER

NOTE!

On Modbus side there must be intended 192 Byte for data receiving resp. 32 Byte fordata sending. Data sending is optional and accordingly also the related projectdevelopment.

Modbus control components are never in scope of delivery of EDER. These componentsmust be provided and projected on site.

i

7. Data transfer

18

7. Data transfer

7.2. Data types

Standardised data types:Register (16-Bit). According to the Modbus specification, for each register the High-Byte istransferred first, followed by the Low-Byte.Extended data bytes:32-Bit integer and 32-Bit float are transferred as 2 successive 16-Bit registers.

7.3. Bit significance

All multibyte data types are transferred as (Most Significant Byte).MSB

At compound data types ( 16, 16, 32) the first sent Byte is always classified as .SI UI UI MSB

Examples:Byte 0/1 (Register 0) ... binary signalling / binary status requests

... Byte 0 (High-Byte): 0 0 0 0 1 0 0 1 (bin), equivalent to 9 (dec) x 256 = 2304--> (warning existing & pump 1 is running)

... Byte 1 (Low-Byte): 0 0 0 0 0 0 1 0 (bin), equivalent to 2 (dec)--> (device function ext. enable contact status)

... Register 0 input value (dec): 2304 + 2 = 2306

Byte 6/7 (Register 3) ... current plant pressure [bar *100]

... Byte 6 (High-Byte): 0 0 0 0 1 1 0 0 (bin), equivalent to 12 (dec) x 256 = 3072

... Byte 7 (Low-Byte): 1 0 1 1 1 1 0 0 (bin), equivalent to 188 (dec)

... Register 3 input value (dec): 3072 + 188 = 3260 --> 32,6 bar

0 0 0 0 1 1 0 0

MSB LSB

msb lsb

SI 16 (e.g. Byte 6/7)

1 0 1 1 1 1 0 00 0 0 1 0 1 1 0 0 0 1 0 0 0 0 0Byte 5 Byte 6 Byte 7 Byte 8

......

CAUTION!

The multicontrol processor board doesn‘t check the sent resp. the received data. In caseof an incorrect Modbus project development, malfunction or breakdown of the datatransfer, malfunctions of the multicontrol device can occur. This is particularly relevant forthe external setpoint setting via Modbus.

19

7. Data transfer

20

7.4. Bus module Modbus Output RegisterRTU(data register 1)

The data register 1 shows the organisation of the data in the memory area of the

bus module which can be read via a read command (04H Read Input Registers) of

the Modbus- Master. All Multibyte data types are organised as (MostRTU MSB

Significant Byte).

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 0 binary signals UI 8

Bit 0warning existing1 = warning

ON OFF,

Bit 1fault existing1 = fault

ON OFF,

Bit 2makeup in operation1 = makeup ON

ON OFF,

Bit 3pump 1 in operation1 = pump 1 ON

ON OFF,

Bit 4pump 2 in operation1 = pump 2 ON

ON OFF,

Bit 5fast degassing1 = started

ON OFF,

Bit 6 -

Bit 7 -

Byte 1 binary status requests UI 8

Bit 0enable device via ext. enable contact1 = enabled

ON OFF,

Bit 1device operation status (ext. enable contact)1 = enabled (active)

ON OFF,

Bit 2enable device via activatedBUS1 = enabled

ON OFF,

Bit 3device operation status (bus)1 = enabled (active)

ON OFF,

0

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 1 binary status requests UI 8

Bit 4from V1.26: busmodule/webmodule: receivingdisabled1 = disabled

Bit 5

from V1.26: : external setpoint: activatedTCand invalid (hence replaced by substitutevalue)1 = activated and invalid

Bit 6 -

Bit 7 -

Byte 2 to : breakdown send data byte 0MC BMS UI 8

Bit 0reset faults1 = faults has been reset

ON OFF,

Bit 1reset warnings1 = warnings has been reset

ON OFF,

Bit 2makeup : reset amountMCF1 = makeup amount has been reset

ON OFF,

Bit 3makeup : one-time fillingMCF1 = one-time filling has been started

ON OFF,

Bit 4degassing: start fast degassing1 = fast degassing has been started

ON OFF,

Bit 5 -

Bit 6 -

Bit 7 -

Byte 3

Bit 0 … 3 = on-site handle--> 0 = main display--> 1 = message level--> 2 = display level--> 3 = user levelBit 4 … 7 = current user level--> 0 = user level 2--> 1 = user level 3--> 2 = user level 4--> 3 = user level 5

UI 8

1

0

7. Data transfer

21

TC ... only with topcontrol

7. Data transfer

22


Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

13 Byte 26

TC: external setpoint: upper working pressure:source0 = no ext. setpoint1 = ext. setpoint: analog input (4-20 mA)2 = ext. Setpoint from busmodule

UI 8

13 Byte 27

TC:operating mode valves0 = redundancy mode1 = valve Y3 only2 = valve Y4 only3 = staggered mode4 = parallel mode

UI 8

14 Byte 28/29current pressure vessel 1 bottom 1uPLvalue range: -300 … + 1300

SI 16 mbar

15 Byte 30/31current pressure vessel 1 top 1oPLvalue range: -300 … + 1300

SI 16 mbar

16 Byte 32/33current pressure vessel 2 bottom 2uPLvalue range: -300 … + 1300

SI 16 mbar

17 Byte 34/35current pressure vessel 2 top 2oPLvalue range: -300 … + 1300

SI 16 mbar

18 Byte 36/37current temperature of the multicontrolprocessor board

SI 16 °C (*100)

19 Byte 38/39maximum temperature of the multicontrolprocessor board

SI 16 °C (*100)

20 Byte 40/41minimum temperature of the multicontrolprocessor board

SI 16 °C (*100)

21 Byte 42/43software versione.g.: 126 = version 1.26

SI 16

22 Byte 44

language pack0 = lang. pack a1 = lang. pack b2 = lang. Pack c…

UI 8

7. Data transfer

23


Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

22 Byte 45

device type0 = -SMCK1 = -D (-twin)MCK2 = -M (-twin)MCK3 = -S1MCM4 = -D1 (-twin)MCM5 = -M1 (-twin)MCM6 = -S2-S9MCM7 = -D2-D9 (-twin)MCM8 = -M2-M9 (-twin)MCM9 = -S-xx-xMCM10 = -D-xx-x (-twin)MCM11 = -M-xx-x (-twin)MCM12 = -S2-12-2TCM13 = -D2-12-2TCM14 = -M2-12-2TCM15 = -D2-12-2-twinTCM16 = -M2-12-2-twinTCM17 = -S3-23-6TCM18 = -D3-23-6TCM19 = -M3-23-6TCM20 = -D3-23-6-twinTCM21 = -M3-23-6-twinTCM22 = -S7-13-5TCM23 = -D7-13-5TCM24 = -M7-13-5TCM25 = -D7-13-5-twinTCM26 = -M7-13-5-twinTCM27 = -S9-24-0TCM28 = -D9-24-0TCM29 = -M9-24-0TCM30 = -D9-24-0-twinTCM31 = -M9-24-0-twinTCM32 = -Sxx-xTCM33 = -Dxx-xTCM34 = -Mxx-xTCM35 = -Dxx-x-twinTCM36 = -Mxx-x-twinTCM37 = -SMCA38 = -S1MCC39 = -D1 (-twin)MCC40 = -M1 (-twin)MCC41 = -SPCK

UI 8

7. Data transfer

24

7. Data transfer

25


Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

23/24 Byte 46...49pump 1 operating hoursCAUTION: displayed in seconds!

UI 32 s

25/26 Byte 50...53pump 2 operating hoursCAUTION: displayed in seconds!

UI 32 s

27 Byte 54/55 -

28 Byte 56/57level L1value range: 0 … 100

SI 16 %

29 Byte 58/59level L2value range: 0 … 100

SI 16 %

Byte 60

operating mode pumps0 = redundancy mode1 = pump M1 only2 = pump M2 only3 = staggered mode4 = parallel mode

UI 8

Byte 61current priority pump0 = pump 1; 1 = pump 2

UI 8

Byte 62

operating mode level0 = automatic change1 = level L1 only2 = level L2 only

UI 8

Byte 63

operating mode makeup0 = amount-controlled1 = uncontrolled2 = time-controlled

UI 8

Byte 64

degassing: current operating stage0 = locked1 = pressure build-up2 = degassing3 = break4 = open valve5 = overpressure

UI 8

Byte 65TC: current preferred valve0 = valve Y31 = valve Y4

UI 8

30

31

32

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

33 Byte 66/67level start makeupvalue range: 0 … 100

SI 16 %

34 Byte 68/69level stop makeupvalue range: 0 … 100

SI 16 %

35/36 Byte 70...73 entire makeup amount up to now 32 lUI

37 Byte 74/75 makeup: remaining amount 16 lSI

38/39 Byte 76...79 makeup: remaining time 32 sUI

40/41 Byte 80...83 water treatment: remaining capacity 32 lUI

42/43 Byte 84...87degassing: remaining time of the currentoperating phasedisplayed in seconds

UI 32 s

44/45 Byte 88...91degassing: operating hoursdisplayed in seconds

UI 32 s

46 Byte 92/93P1min: set limitset value in menu "monitoring"value range: 0 … 4000

SI 16 bar (*100)

47 Byte 94/95P1max: set limitset value in menu "monitoring"value range: 0 … 4000

SI 16 bar (*100)

48 Byte 96/97Lmin: set limitset value in menu "monitoring"value range: 0 … 100

SI 16 %

Byte 98 UI 8

Bit 0P1min: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 1P1max: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 2L1min: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

49

7. Data transfer

26

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 99 UI 8

Bit 0 -

Bit 1 -

Bit 2 -

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

50 Byte 100/101Lmax: set limitSetting value in the "monitoring" menuvalue range: 0 … 100

SI 16 %

51 Byte 102/103T1min: set limitSetting value in the "monitoring" menuvalue range: -500 … +1200

SI 16 °C (*10)

52 Byte 104/105T1max: set limitSetting value in the "monitoring" menuvalue range: -500 … +1200

SI 16 °C (*10)

Byte 106 UI 8

Bit 0Lmax: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 1T1min: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 2T1max: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

49

53

7. Data transfer

27

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 107 UI 8

Bit 0 -

Bit 1 -

Bit 2 -

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

54 Byte 108/109T2min: set limitSetting value in the "monitoring" menuvalue range: -500 … +1200

SI 16 °C (*10)

55 Byte 110/111T2max: set limitSetting value in the "monitoring" menuvalue range: -500 … +1200

SI 16 °C (*10)

Byte 112 UI 8

Bit 0T2min: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 1T2max: current state ( , Alert)OK1 = Alert

OK, Alert

Bit 2 -

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

Byte 113 UI 8

Bit 0 -

Bit 1 -

Bit 2 -

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

56

53

7. Data transfer

28

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 114 UI 8

Bit 0TC: overflow valve 1 coupling0 = output „Off“ valves close mechanically

ON OFF,

Bit 1TC: overflow valve 1 open1 = overflow valve opens

ON OFF,

Bit 2TC: overflow valve 1 close1 = overflow valve closes

ON OFF,

Bit 3TC: overflow valve 2 coupling0 = output „Off“ valves close mechanically

ON OFF,

Bit 4TC: overflow valve 2 open1 = overflow valve opens

ON OFF,

Bit 5TC: overflow valve 2 close1 = overflow valve closes

ON OFF,

Bit 6 -

Bit 7 -

Byte 115 UI 8

Bit 0MCA: switching valve open1 = switching valve opens

ON OFF,

Bit 1MCA: switching valve close1 = switching valve closes

ON OFF,

Bit 2 -

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

Byte 116MCA: operating mode0 = contact controlled1 = press.controlled

UI 8

Byte 117

from V1.26: : current operating stageMCA0 = off1 = makeup2 = circulation3 = pause circulation4 = locked5 = diverter valve Y5: open6 = diverter valve Y5: close

UI 8

58

57

57

7. Data transfer

29

TC MCA... only with topcontrol / ... only with multicontrol autofill

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

59/60 Byte 118..121electronics: operating hoursdisplayed in seconds

UI 32 s

61 Byte 122/123 vessel code 16SI

Byte 124 UI 8

Bit 0makeup available1 = Yes

YES NO,

Bit 1sensor T2 available1 = Yes

YES NO,

Bit 2level measurement L2 available1 = Yes

YES NO,

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

62 Byte 125

water treatment: configuration0 = not available1 = softening 6MWE2 = softening 12MWE3 = desalination 2MVE4 = desalination 4MVE

UI 8

Byte 126

degassing: operating mode0 = off1 = as per timer progr.2 = always enabled

UI 8

Byte 127

from V1.23: degassing device set-up0 = not available1 = pump degassing2 = degassing module

UI 8

63

62

62

7. Data transfer

30

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

64 Byte 128/129blocking temp.T1Setting value in the "degassing" menuvalue range: -500 … +400

SI 16 °C (*10)

65 Byte 130/131temperat. Limit T1Setting value in the "degassing" menuvalue range: -500 … +950

SI 16 °C (*10)

66 Byte 132/133blocking temp.T2Setting value in the "degassing" menuvalue range: -500 … +400

SI 16 °C (*10)

67 Byte 134/135temperat. Limit T2Setting value in the "degassing" menuvalue range: -500 … +950

SI 16 °C (*10)

Byte 136 free 8UI

Byte 137 free 8UI

Byte 138 free 8UI

Byte 139 free 8UI

Byte 140 free 8UI

Byte 141 free 8UI

Byte 142 free 8UI

Byte 143 free 8UI

68

69

70

71

7. Data transfer

31

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 144 UI 8

Bit 0 W11: time changed due to daylight saving , AlertOK

Bit 1 E1: data link error to basic circuit board , AlertOK

Bit 2 E7: write error I2C basic circuit board , AlertOK

Bit 3 E20: write error I2C module: binary signalling , AlertOK

Bit 4 E18: write error I2C module: analog sign. , AlertOK

Bit 5 E4: read error I2C basic circuit board , AlertOK

Bit 6 E19: read error I2C module: binary signalling , AlertOK

Bit 7 E17: read error I2C module analog sign. , AlertOK

Byte 145 UI 8

Bit 0 E13: transmitter 1o meas. signal too low , AlertPL OK

Bit 1 E12: transmitter 1o meas. signal too high , AlertPL OK

Bit 2 E15: transmitter 1u meas. signal too low , AlertPL OK

Bit 3 E14: transmitter 1u meas. signal too high , AlertPL OK

Bit 4 E11: transmitter P1 meas. signal too low , AlertOK

Bit 5 E10: transmitter P1 meas. signal too high , AlertOK

Bit 6 E8: temperature sensor T1 short circuit , AlertOK

Bit 7 E9: temperature sensor T1 break , AlertOK

Byte 146 UI 8

Bit 0 E21: temperature sensor T2 short circuit , AlertOK

Bit 1 E22: temperature sensor T2 break , AlertOK

Bit 2 E2: pump M1 start failed , AlertOK

Bit 3 E3: pump M1 stop failed , AlertOK

Bit 4 E23: pump M2 start failed , AlertOK

Bit 5 E24: pump M2 stop failed , AlertOK

Bit 6 E26: makeup amount exceeded , AlertMCF OK

Bit 7 W16: makeup remain. amount <20% , AlertMCF OK

Byte 147 UI 8

Bit 0 W17: softening remain. capacity <20% , AlertMWE OK

Bit 1 E28: softening change cartridge , AlertMWE OK

Bit 2 W4: temperature limit sensor T1 exceeded , AlertOK

Bit 3 W13: temperature limit sensor T2 exceeded , AlertOK

Bit 4 W2: manual mode at least 1 output , AlertOK

Bit 5 E16: dry run protection has been activated , AlertOK

Bit 6 E30: transmitter 2o meas. signal too low , AlertPL OK

Bit 7 E29: transmitter 2o meas. signal too high , AlertPL OK

72

73

7. Data transfer

32

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 148 UI 8

Bit 0 E32: transmitter 2u meas. signal too low , AlertPL OK

Bit 1 E31: transmitter 2u meas. signal too high , AlertPL OK

Bit 2 E0: device is disabled , AlertOK

Bit 3 E34: sms-module: pin code wrong , AlertOK

Bit 4 E35: sms-module: sim card error , AlertOK

Bit 5 E33: sms-module: no response , AlertOK

Bit 6 W19: sms-module: no network , AlertOK

Bit 7 W8: monitoring: P1min under-run , AlertOK

Byte 149 UI 8

Bit 0 W7: monitoring: P1max over-run , AlertOK

Bit 1 W6: monitoring: Lmin under-run , AlertOK

Bit 2 W5: monitoring: Lmax over-run , AlertOK

Bit 3 W10: monitoring: T1min under-run , AlertOK

Bit 4 W9: monitoring: T1max over-run , AlertOK

Bit 5 W15: monitoring: T2min under-run , AlertOK

Bit 6 W14: monitoring: T2max over-run , AlertOK

Bit 7 E5: max. run-time pump M1 exceeded , AlertOK

Byte 150 UI 8

Bit 0 E25: max. run-time pump M2 exceeded , AlertOK

Bit 1 E6: too many pump requests per period , AlertOK

Bit 2 E27: makeup: max. run-time exceeded , AlertOK

Bit 3 W3: accomplish periodic maintenance , AlertOK

Bit 4 W12: underpressure in vessel 1 ( 1o) , AlertPL OK

Bit 5 W18: underpressure in vessel 2 ( 2o) , AlertPL OK

Bit 6 E36: pump M1 error , AlertOK

Bit 7 E37: pump M2 error , AlertOK

Byte 151 UI 8

Bit 0 E38: write error analog module: 0 , AlertAO OK

Bit 1 E39: read error analog module: 0 , AlertAO OK

Bit 2 E40: external setpoint meas.signal too low , AlertOK

Bit 3 E41: external setpoint meas.signal too high , AlertOK

Bit 4 W20: demineral. remaMVE in.capacity <20% , AlertOK

Bit 5 E42: demineral. change cartridge , AlertMVE OK

Bit 6 W21: blocking temp. T1 sensor T1 below , AlertOK

Bit 7 W22: blocking temp. T2 sensor T2 below , AlertOK

74

75

7. Data transfer

33

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 152 UI 8

Bit 0 E43: ext. fault via digital input ! , AlertOK

Bit 1 W23: ext.warning via digital input ! , AlertOK

Bit 2 message 67 , AlertOK






Byte 153 UI 8









Byte 154 UI 8









Byte 155 UI 8









76

77

7. Data transfer

34

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 156 free 8UI

Byte 157 free 8UI

Byte 158 free 8UI

Byte 159 free 8UI

Byte 160 free 8UI

Byte 161 free 8UI

Byte 162 free 8UI

Byte 163 free 8UI

Byte 164 free 8UI

Byte 165 free 8UI

Byte 166 free 8UI

Byte 167 free 8UI

Byte 168 free 8UI

Byte 169 free 8UI

Byte 170 free 8UI

Byte 171 free 8UI

Byte 172 free 8UI

Byte 173 free 8UI

Byte 174 free 8UI

Byte 175 free 8UI

Byte 176 free 8UI

Byte 177 free 8UI

Byte 178 free 8UI

Byte 179 free 8UI

Byte 180 free 8UI

Byte 181 free 8UI

Byte 182 free 8UI

Byte 183 free 8UI

Byte 184 free 8UI

Byte 185 free 8UI

Byte 186 free 8UI

Byte 187 free 8UI

Byte 188 free 8UI

Byte 189 free 8UI

Byte 190 free 8UI

Byte 191 free 8UI95

86

87

88

89

90

91

92

93

94

85

78

79

80

81

82

83

84

7. Data transfer

35

7. Data transfer

36

7.5. Bus module Modbus Input Register(data register 2)

The data register 2 shows the organisation of the data in the memory area of the bus

module which can be sent via a write command (10H Write Multiple Registers) from the

Modbus master to the bus module. All Multibyte data types are organised asRTU MSB

(Most Significant Byte).

Reg.Nr.

Byte // Bit

Descriptiondatatype

unit /status

Byte 0 binary remote acknowledgement UI 8

Bit 0reset fault messages1 = fault messages get reset

ON OFF,

Bit 1reset warning messages1 = warning messages get reset

ON OFF,

Bit 2makeup : reset amountMCF1 = makeup amount gets reset

ON OFF,

Bit 3makeup : one-time fillingMCF1 = one-time filling gets executed

ON OFF,

Bit 4degassing: start fast degassing1 = fast degassing gets started

ON OFF,

Bit 5 -

Bit 6 -

Bit 7 -

Byte 1 UI 8

Bit 0

device function enabling via bus: Off-On1 = device enabling via bus is active.Note: only effective, if "device functionenabling via bus enabled" ist set.

ON OFF,

Bit 1

Bit 2 -

Bit 3 -

Bit 4 -

Bit 5 -

Bit 6 -

Bit 7 -

Byte 2 free 8UI

Byte 3 free 8UI

0

1

7. Data transfer

37


aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Notes

8. Notes

38

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Notes

8. Notes

39

ANTON EDER GMBHA-9909 Leisach 52Tel.: +43 (0) 4852 644 77Fax: +43 (0) 4852 644 77-20

[email protected]:

Branch office A-5733 Bramberg | Weyerstraße 350 | Tel.: +43 (0) 6566 7366Branch office A-1230 Wien | Gorskistraße 15 | Tel.: +43 (0) 1 985 37 30

anton eder gmbh - eder heizung · eder control-electronics: multicontrol basic circuit board, type...

Documents