pvyleta / ebusd-brink-hru

Collection of Brink HRU configuration files for ebusd
GNU General Public License v3.0
2 stars 1 forks source link

ebusd configuration help #4

Open DromeNor opened 1 month ago

DromeNor commented 1 month ago

Hi Petr, I'm new and I don't really understand how to configure the ebusd to read\write the parameters of my Renovent Excellent 300. I bought the v5 shield adapter and connected it in parallel to the same cables that go into the air control. Is this correct as a physical connection?

Brink Excellent 300 SW 108.08.0001 I try whit know slave 3c file and olso with specific version but same result.

The ebusd daemon runs on docker as a container with this compose.

ebusd: image: john30/ebusd networks: default: ipv4_address: 172.18.0.13 container_name: ebusd volumes:

2024-05-31 12:23:33.694 [bus notice] device status: transport opened 2024-05-31 12:23:33.695 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 192.168.2.58:9999, TCP, enhanced 2024-05-31 12:23:33.700 [bus notice] bus started with own address 31/36 2024-05-31 12:23:33.700 [bus notice] signal acquired 2024-05-31 12:23:33.701 [mqtt notice] connection established 2024-05-31 12:23:33.725 [bus notice] device status: reset, supports info 2024-05-31 12:23:33.770 [bus notice] device status: extra info: firmware 1.1[451a].1[451a], jumpers 0x0b 2024-05-31 12:23:33.872 [bus notice] new master 1f, master count 2 2024-05-31 12:23:36.535 [bus notice] new master 37, master count 3 2024-05-31 12:23:36.536 [update notice] received read Excellent300 PosizioneVentilatore QQ=1f: Reduced 2024-05-31 12:23:41.553 [update notice] received read Excellent300 PosizioneVentilatore QQ=1f: Reduced 2024-05-31 12:23:43.700 [main notice] starting initial broadcast scan 2024-05-31 12:23:43.859 [bus error] send to fe: ERR: wrong symbol received, retry 2024-05-31 12:23:43.978 [bus error] send to fe: ERR: SYN received, retry 2024-05-31 12:23:44.167 [bus error] send to fe: ERR: read timeout 2024-05-31 12:23:44.167 [main error] initial scan failed: ERR: read timeout 2024-05-31 12:23:46.525 [update notice] received read Excellent300 PosizioneVentilatore QQ=1f: Reduced 2024-05-31 12:23:48.311 [update notice] received unknown MS cmd: 1f3c40ca0101 / 06000100733000 2024-05-31 12:23:49.897 [bus error] poll Excellent300 CondizioniIngressoDiContatto1 failed: ERR: read timeout 2024-05-31 12:23:51.487 [update notice] received read Excellent300 PosizioneVentilatore QQ=1f: Reduced 2024-05-31 12:23:54.168 [main notice] starting initial broadcast scan 2024-05-31 12:23:54.356 [bus error] send to fe: ERR: SYN received, retry 2024-05-31 12:23:54.505 [bus error] send to fe: ERR: read timeout, retry 2024-05-31 12:23:54.655 [bus error] send to fe: ERR: read timeout 2024-05-31 12:23:54.655 [main error] initial scan failed: ERR: read timeout 2024-05-31 12:23:55.126 [bus error] poll Excellent300 CondizioniIngressoDiContatto2 failed: ERR: read timeout 2024-05-31 12:23:56.970 [update notice] received read Excellent300 PosizioneVentilatore QQ=1f: Reduced 2024-05-31 12:24:01.110 [bus error] poll Excellent300 CronologiaDegliErrori failed: ERR: SYN received 2024-05-31 12:24:01.932 [update notice] received read Excellent300 PosizioneVentilatore QQ=1f: Reduced 2024-05-31 12:24:04.656 [main notice] starting initial broadcast scan 2024-05-31 12:24:04.791 [bus error] send to fe: ERR: read timeout, retry

basically I only receive FanPosition while everything else goes into error. I try olso disconnect the airControll but same result. Do you have any advice?

pvyleta commented 1 month ago

I bought the v5 shield adapter and connected it in parallel to the same cables that go into the air control. Is this correct as a physical connection?

I think the physical connection is correct, since you can see some messages. strange that nothing else is read. I suggest to enable even debug log level, connect air control, and see what messages ebusd reads that the air control sends to the unit.