abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Vitogate 300 and Vitodens 222F

Hi,

I have been trying to connect the Vitodens 222F with Loxone trough modbus RTU for the last 2 weeks. I have managed to read some data, but can not set the flow temperature or set the DHW temperature. It seems that the Viessmann people in our country (Slovenia) dont know how to do it and are refusing any help from their site. I have tryed a lot (...........) of holding register and input registers and nothing seems to work. 

Can anyone point out exactly what registers should be addresed to make the Vitodens obey comands. It als looks like it whants to stay with the display parameters and does not do anything...

 

Thanks,

Christian

 

8 ANTWORTEN 8


Hello LangeCh,


wich Vitogate do you have exactly? Do you have the datapoint-list? Are you a programmer?


Best wishes °be

Hi Benjamin,
I have saved the datapoint list from the Vitogate300. Not sure how to attach the file. I am IT+automation expert.
Datapoints:
https://drive.google.com/file/d/1zeVkVcmczihc1mfBRNS1gZhM6dJ9UvT3/view?usp=sharing

Thanks,
Christian

The control unit is Vitotronic 200 H02C, and it is direct heating. Guess that would mean A1 only.

Please post the serialnumber of your Vitogate 300.

And what´s exactly the problem by setting the DHW temperature or the flow temperature?

Best wishes °be

I currently don't have the serial number as the units (2 installations) are installed and the heating is already running. I do have the invoice for the Vitogate300. The data on the invoice is Vitogate 300 + LON module Vitotronic 200 (H01 KW6). I have also installed the latest firmware ( Release 2.1.1.0 ) a week ago.

No reaction and can not read: (read-write registers)
2306 HO-2 Set room temperature standard mode A1M1
2307 HO-4 Set room temperature reduced mode A1M1
2321 HO-90 External set room temperature standard A1M1
2323 HO-6 Operating mode A1M1
A303 HO-102 Set boiler water temperature
A383 HO-33 Set flow temperature systems/boilers

Can write and read (but does not affect anything)
6300 HO-48 Set DHW temperature

Read only that works
810 IN-42 Flow temperature A1M1
5525 IN-23 Outside temperature


Not on the datapoint list, but doing something

IN-2 ---> returns the room temp. that in on the display of the Vidodens222

A bit of the log file:
00019437 192.168.22.3 08:59:37.972 08:59:37.562 LNK Debug Modbus invalid response 09d85761, Modbus-address: 4, IO-address: 4, Exception-Code 02: Illegal Data Address
00019469 192.168.22.3 08:59:38.483 08:59:38.093 LNK Debug Modbus invalid response 09d85761, Modbus-address: 4, IO-address: 2, Exception-Code 02: Illegal Data Address
00019501 192.168.22.3 08:59:39.836 08:59:39.435 LNK send modbus actor to 09D85761. Modbus-address: 4, IO-address: 2, Data: 180
00019502 192.168.22.3 08:59:39.855 08:59:39.463 LNK Debug Modbus invalid response 09d85761, Modbus-address: 4, IO-address: 2, Exception-Code 02: Illegal Data Address

I have managed to set up a lot of Modbus installations and it all worked fine, here I am stuck..... Thinking if there is a setting to allow external control.

Thanks,
Christian


I need the serialnumber.

Please send us a screenshot of your programm to customer-care@viessmann.com and we will check it. But it´s better you contact our collegaues at your country again. They can send you a technical wich could help you.

Best wishes °be

Hi,
the local Viessmann installer has sent me the serial of the Vitodens, guess I'll have to go on site to get the serial of the Vitogate unit. As soon as I have it I will let you know.
https://drive.google.com/file/d/198x4JontvOyvhY_GUtgdTJuRJHjKZCdw/view?usp=sharing

Christian

I have managed to get acces to the vitogate over Internet: Can grand you access if needed:
LOG:
15.03.19 06:24:15 Drv.modtyS3: ConfigReadWords - Input 2 in module 4 not configured!
15.03.19 06:24:15 Drv.modtyS3: SND 04 84 02 D2 C0
15.03.19 06:24:15 Drv.modtyS3: REC 04 04 00 1D 00 01 A1 99
15.03.19 06:24:15 Drv.modtyS3: ConfigReadWords - Value of Input 29 in module 4 is (still) invalid!
15.03.19 06:24:15 Drv.modtyS3: SND 04 04 02 FF FF 74 80
15.03.19 06:24:16 Drv.modtyS3: REC 03 06 00 00 00 00 88 28
15.03.19 06:24:16 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:16 Drv.modtyS3: REC 03 06 00 00 00 00 88 28
15.03.19 06:24:16 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:16 Drv.modtyS3: REC 04 06 00 02 00 16 A9 91
15.03.19 06:24:16 Drv.modtyS3: SND 04 06 00 02 00 16 A9 91
15.03.19 06:24:17 Drv.modtyS3: REC 04 04 00 16 00 01 D0 5B
15.03.19 06:24:17 Drv.modtyS3: SND 04 04 02 00 0B 34 F7
15.03.19 06:24:17 Drv.modtyS3: REC 04 04 00 2B 00 01 41 97
15.03.19 06:24:17 Drv.modtyS3: ConfigReadWords - Input 43 in module 4 not configured!
15.03.19 06:24:17 Drv.modtyS3: SND 04 84 02 D2 C0
15.03.19 06:24:17 Drv.modtyS3: REC 03 04 00 02 00 01 91 E8
15.03.19 06:24:17 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:18 Drv.modtyS3: RESYNC (frame timeout 1078 ms), discard 7 bytes
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 00 01 00 01 61 E8
15.03.19 06:24:18 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 02 00 00 C0 F0 03
15.03.19 06:24:18 Drv.modtyS3: skip frame (04), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (04), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (01), unexpected function 71
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC E9 03 04 02 00 16 41 3E
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 00 00 00 01 30 28
15.03.19 06:24:18 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 02 00 00 C0 F0 03
15.03.19 06:24:18 Drv.modtyS3: skip frame (04), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (06), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (01), unexpected function D0
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 29 03 04 02 00 00 C0 F0
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 00 07 00 01 81 E9
15.03.19 06:24:18 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 02 00 00 C0 F0 03
15.03.19 06:24:18 Drv.modtyS3: skip frame (04), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (08), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (01), unexpected function B1
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC EA 03 04 02 00 00 C0 F0
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 00 09 00 01 E0 2A
15.03.19 06:24:18 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 02 00 00 C0 F0 03
15.03.19 06:24:18 Drv.modtyS3: skip frame (04), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (0A), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 01 10 2A 03 04 02 00 00 C0
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC F0 03 04 00 0B 00 01 41
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC EA 03 04 02 00 00 C0 F0
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 00 03 00 01 C0 28
15.03.19 06:24:18 Drv.modtyS3: Request for concurrent module 3
15.03.19 06:24:18 Drv.modtyS3: Checksum Error (Datagramme follows)
15.03.19 06:24:18 Drv.modtyS3: REC 03 04 02 00 05 00 F3 03
15.03.19 06:24:18 Drv.modtyS3: skip frame (04), unexpected function 00
15.03.19 06:24:18 Drv.modtyS3: skip frame (16), unexpected function 00
Top-Lösungsautoren