Closed Streifix closed 10 months ago
I have a vaillant VRC700/6 controlling a VSC206/4-5 90 E. I am using an eBus adapter shield version 5.
The problem: ebusd doesn't detect my vaillant devices correctly. ebusctl info gives me:
version: ebusd 23.2.23.2-10-g76184c76 update check: revision 23.2 available device: 192.168.34.5:9999 signal: acquired symbol rate: 46 max symbol rate: 175 min arbitration micros: 12 max arbitration micros: 247 min symbol latency: 12 max symbol latency: 53 scan: finished reconnects: 0 masters: 2 messages: 1 conditional: 0 poll: 0 update: 0 address 10: master #2 address 31: master #8, ebusd address 36: slave #8, ebusd, scanning
Looking at the hex dump of the messages (ebusd-logfile), I see a lot of 'c6' even inserted in the maybe correct readouts of the bus messages:
2023-09-30 12:38:32.046 [bus notice] <c6 2023-09-30 12:38:32.088 [bus notice] <c6 2023-09-30 12:38:32.129 [bus notice] <c6 2023-09-30 12:38:32.178 [bus notice] <c6 2023-09-30 12:38:32.218 [bus notice] <c6 2023-09-30 12:38:32.310 [bus notice] <1008c6b5110101c68900094947c79010445600003bc7a800c6 2023-09-30 12:38:32.359 [bus notice] <c6 2023-09-30 12:38:32.399 [bus notice] <c6 2023-09-30 12:38:32.447 [bus notice] <c6 2023-09-30 12:38:32.489 [bus notice] <c6 2023-09-30 12:38:32.582 [bus notice] <1008c6b51009000000c7bfc7bfc7bf01000026000101c69a00c6 2023-09-30 12:38:32.630 [bus notice] <c6 2023-09-30 12:38:32.679 [bus notice] <c6
What could be the reason for not recognizing the vaillant hardware?
Günter
wrong ebusd device string, it is missing the "ens:" prefix as documented
I have a vaillant VRC700/6 controlling a VSC206/4-5 90 E. I am using an eBus adapter shield version 5.
The problem: ebusd doesn't detect my vaillant devices correctly. ebusctl info gives me:
version: ebusd 23.2.23.2-10-g76184c76 update check: revision 23.2 available device: 192.168.34.5:9999 signal: acquired symbol rate: 46 max symbol rate: 175 min arbitration micros: 12 max arbitration micros: 247 min symbol latency: 12 max symbol latency: 53 scan: finished reconnects: 0 masters: 2 messages: 1 conditional: 0 poll: 0 update: 0 address 10: master #2 address 31: master #8, ebusd address 36: slave #8, ebusd, scanning
Looking at the hex dump of the messages (ebusd-logfile), I see a lot of 'c6' even inserted in the maybe correct readouts of the bus messages:
2023-09-30 12:38:32.046 [bus notice] <c6 2023-09-30 12:38:32.088 [bus notice] <c6 2023-09-30 12:38:32.129 [bus notice] <c6 2023-09-30 12:38:32.178 [bus notice] <c6 2023-09-30 12:38:32.218 [bus notice] <c6 2023-09-30 12:38:32.310 [bus notice] <1008c6b5110101c68900094947c79010445600003bc7a800c6 2023-09-30 12:38:32.359 [bus notice] <c6 2023-09-30 12:38:32.399 [bus notice] <c6 2023-09-30 12:38:32.447 [bus notice] <c6 2023-09-30 12:38:32.489 [bus notice] <c6 2023-09-30 12:38:32.582 [bus notice] <1008c6b51009000000c7bfc7bfc7bf01000026000101c69a00c6 2023-09-30 12:38:32.630 [bus notice] <c6 2023-09-30 12:38:32.679 [bus notice] <c6
What could be the reason for not recognizing the vaillant hardware?
Günter