eBUS Adapter 3.0

[tlc]

I have only 2 heaters (and not 3 )
Vaillant uses a single ebus wire pair to connect all devices. I have attached the schematic (showing off my MS Paint skills ).

There is a single ebus line that connects ALL these devices.
In other words, all devices are connected in parallel to only one pair of ebus wires, according to the Vaillant installation manual, as follows:
- Heater 1 is connected directly to ebus line via the ebus +/- wires available on the heater's mainboard
- Heater 2 is connected to the SAME ebus wire via a VR 32 module connected internally inside the heater electronics box (which I suppose it is responsible for serializing/queuing the telegrams from/to the Heater 2 within the same ebus instance --> this allows up to 8 heaters to be connected to a single ebus, each of the last 7 heaters needing this VR 32 ebus coupler). The VR 32 has a rotary switch that allows the selection of an ID (from 0 to 15) which will identify Heater 2 messages on ebus.
- Calormatic 630 is also linked directly to the SAME ebus wire pair as the other 2 heaters.

The VR 32 is connected via the X31 connector on the mainboard of Heater 2.
With this wiring configuration, VRC 630 automatically recognizes the 2 heaters and enables a "Cascade" menu which allows setting up on/off timers between the 2 heaters and other cascade related settings.

My expectation is that a single ebus adapter attached to this unique ebus line should be able to decode all communication between all ebus participants.
However I ordered and paid 2 ebus adapters, just in case both will be necessary.

What I don't know (and will need to be tested) : how the Calormatic 630 controller behaves when I change for example "target flow temperature" via ebusd? Will it recognize the change? Or it will start sending messages with its own "target flow temperature" value?
Perhaps there are users around here using this Calormatic VRC 630 controller and who could share their experience? (no need to have 2+ heaters in "cascade" configuration - one heater should be enough).

Thanks again for your kindness and for your availability to help out,
Cristian

[galileo]

Vaillant uses a single ebus wire pair to connect all devices. I have attached the schematic

I think the schematic is not correct or not complete. See the attached excerpt of the VR32 manual.

It looks like the VR32 is some kind of "coupler" and "address translator" for the bus. It couples two physically separated e-Bus lines while translating
addresses from the secondary side to the primary side. The bus address where each VR32 is visible to the main bus can be selected by a rotary switch at the VR32 board

I assume that ebusd connected via a ebus-coupler to the primary eBUS lines will "see" all devices that are directly connected to the bus, as well as all devices that are behind the VR32 coupler(s)
but in the latter case with different addresses than they have on their local (secondary) eBus.
If this is true, in your case, ebusd should "see" two instances of heaters, probably with identical configuration but different addresses.

Please note that I have no experience with this configuration, my thoughts are only theoretical. Also I don't know if ebusd may have or may not have any issues with this config.
Maybe John can say something about it 

[tlc]

Thank you @galileo !

Actually the manual in German is different than the one in English and Romanian!
In these manuals there is no vrnetDIALOG device at all!
There is only VRC 630 + Heater 1 + (Heater 2, 3, 4...8 in cascade), all connected to the same hard line (see attached picture, taken from page 28 in the English manual : https://www.vaillant.co.uk/downloads/aproducts/controls/vrc-1/vrc-630-operating-and-installation-manual-1182551.pdf).

I fully agree with your assumption : the role of VR32 is to "serialize" all heaters on a single ebus (by allocating an unique ID which must be configured with unique values via the rotative switch on the VR32 board). So there is just one ebus which should need only one ebus adapter v3 to expose the ebus to the ebusd service.
The Calormatic 630 has only one ebus connector so it can manage only one ebus, which means that all 2 to 8 cascaded heaters are "merged" in the same Primary ebus with the help of the VR32 ebus coupler (this is the commercial name of the VR32 : ebus coupler).

There are at least two users with a similar configuration on the github ebusd forum (https://github.com/john30/ebusd/issues/198) - I posted there too. It is linked also to issue #109 : https://github.com/john30/ebusd/issues/109

@Nuc67UA
@MatthiasKunze

Guys, if you are present here as well, I'd appreciate your input, thanks!

In Issue 109 (https://github.com/john30/ebusd/issues/109) John confirms that at this moment the heaters behind VR32 are exposed to ebusd if parameter --latency=100000 is given.

Any help is more than welcome

Thank you all for your help
Cheers,
Cristian

[galileo]

Actually the manual in German is different than the one in English and Romanian!
In these manuals there is no vrnetDIALOG device at all!

The vrnetDIALOG is a connection to the Vaillant Server and then to your handy app.
Afaik this is only available in Germany and Austria.
Just think about that device as it can be replaced by our eBus Adapter / ebusd system.
And if you use the eBus Adapter 3.0, "latency" will not be an issue any more 

[tlc]

Great, this means that I have a good chance to manage all devices with a single v3 ebus adapter!
Anyway once I receive the ebus v3 adapters, I will be at your disposition as a "rat lab" for any tests with my particular "cascade" configuration (when I am at the location).

FYI, on the smart home side I am using an Openhab 2.5 instance running on a RPi 3b with a dedicated MQTT broker (mosquitto). So I will be using ebusd service and the Openhab ebus binding to interface with the Vaillant ebus.

[Wolle02]

Hallo liebes eBus-Team. Gestern habe ich den Adapter bekommen und heute angeschlossen. Leider laufe ich gleich in Probleme, weil der ebusd zwar scheinbar den Bus erkennt und auch Daten empfängt aber scheinbar sonst nichts empfängt oder decodieren kann.

Ich habe versucht mich genau an die Anleitungen unter ebusd.eu zu halten. Die Installation des ebusd habe ich über diese  Anleitung durchgeführt.
Als Startoptionen in der /etc/defaults/ebusd habe ich folgendes eingetragen:

Code Auswählen Erweitern

EBUSD_OPTS="--scanconfig -r --accesslevel=* --latency=20000 -d enh:/dev/ttyAMA0 --loglevel=debug --address=ff --mqttport=1883 --mqttjson --mqtthost=192.168.50.8 --mqtttopic=ebusd/%circuit/%name"
Die Einträge stammen von Reinhard aus dem Inbetriebnahmethread und den MQTT-Teil habe ich aus dem Fhem Wiki EBUS - MQTT2.

Im ebusd-Logilfe finde ich aber durchweg folgende Einträge:

Code Auswählen Erweitern

2021-01-30 11:40:45.176 [update info] received MS cmd: 1076b512030f0201 / 07008000f10112ff
2021-01-30 11:40:45.176 [update notice] received unknown MS cmd: 1076b512030f0201 / 07008000f10112ff
2021-01-30 11:40:45.480 [update info] received MS cmd: 1026b5230106 / 10ed010d0100800080008000800080503d
2021-01-30 11:40:45.480 [update notice] received unknown MS cmd: 1026b5230106 / 10ed010d0100800080008000800080503d
2021-01-30 11:40:45.777 [update info] received MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 11:40:45.777 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 11:40:45.953 [update info] received MS cmd: 7108b5110107 / 0a00910001083600000000
2021-01-30 11:40:45.954 [update notice] received unknown MS cmd: 7108b5110107 / 0a00910001083600000000
2021-01-30 11:40:46.091 [update info] received MS cmd: 1008b5100900003effffff060000 / 0101
2021-01-30 11:40:46.091 [update notice] received unknown MS cmd: 1008b5100900003effffff060000 / 0101
2021-01-30 11:40:46.404 [bus debug] ERR: read timeout during receive response, switching to skip
2021-01-30 11:40:46.865 [bus debug] ERR: read timeout during receive command, switching to skip
2021-01-30 11:40:47.139 [update info] received MS cmd: 1026b523040200013e / 020164
2021-01-30 11:40:47.139 [update notice] received unknown MS cmd: 1026b523040200013e / 020164
2021-01-30 11:40:49.105 [main debug] performing regular tasks
2021-01-30 11:40:49.216 [mqtt debug] publish ebusd/global/uptime 3745
2021-01-30 11:40:49.379 [update info] received MS cmd: 7108b5110107 / 0a00910001083600000000
2021-01-30 11:40:49.379 [update notice] received unknown MS cmd: 7108b5110107 / 0a00910001083600000000
2021-01-30 11:40:51.256 [update info] received MS cmd: 7108b51a0304f732 / 0ef707c0cfc07b3c00b01b20000000
2021-01-30 11:40:51.257 [update notice] received unknown MS cmd: 7108b51a0304f732 / 0ef707c0cfc07b3c00b01b20000000
2021-01-30 11:40:51.681 [update info] received MS cmd: 7108b51a0304f833 / 0ef800000082000000000000000000
2021-01-30 11:40:51.681 [update notice] received unknown MS cmd: 7108b51a0304f833 / 0ef800000082000000000000000000
2021-01-30 11:40:51.971 [update info] received MS cmd: 7108b5120e11f101f101c1010e021274040000 / 020232
2021-01-30 11:40:51.971 [update notice] received unknown MS cmd: 7108b5120e11f101f101c1010e021274040000 / 020232
2021-01-30 11:40:52.264 [update info] received MS cmd: 7108b51a0304f934 / 0ef9cf2000c0022101001800061800
2021-01-30 11:40:52.264 [update notice] received unknown MS cmd: 7108b51a0304f934 / 0ef9cf2000c0022101001800061800
2021-01-30 11:40:52.645 [update info] received MS cmd: 7108b51a0304fa35 / 0efa00000000000100b00000000000
2021-01-30 11:40:52.645 [update notice] received unknown MS cmd: 7108b51a0304fa35 / 0efa00000000000100b00000000000
2021-01-30 11:40:53.026 [update info] received MS cmd: 7108b51a0304fb36 / 0efb00000000000000000000000000
2021-01-30 11:40:53.026 [update notice] received unknown MS cmd: 7108b51a0304fb36 / 0efb00000000000000000000000000

Ein ebusctl info ergibt folgenden Output:

Code Auswählen Erweitern

pi@EbusPi:~ $ ebusctl info
version: ebusd 21.1.v21.1-12-gccfc025
update check: version 3.4 available
access: *
signal: acquired
symbol rate: 38
max symbol rate: 202
reconnects: 0
masters: 5
messages: 16
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11
address 10: master #2
address 13: master #12
address 18: slave #12
address 26: slave
address 71: master #9
address 76: slave #9



In Fhem habe ich nach der Anleitung EBUS - MQTT2 den MQTT2-Server angelegt und das MQTT2-Device, das als Bridge dient:

Code Auswählen Erweitern

Internals:
   CID        ebusd
   DEF        ebusd
   DEVICETOPIC MQTT2_ebusd
   FUUID      600b814d-f33f-bf2d-e150-9a44efc82b33ba02
   FVERSION   10_MQTT2_DEVICE.pm:0.235960/2021-01-23
   IODev      ebusMQTT
   LASTInputDev ebusMQTT
   MSGCNT     526
   NAME       MQTT2_ebusd
   NR         431
   STATE      Status:
1:true
Signal:
2:true
<br>Uptime: 0 000 01:07
   TYPE       MQTT2_DEVICE
   ebusMQTT_MSGCNT 526
   ebusMQTT_TIME 2021-01-30 11:45:53
   READINGS:
     2021-01-30 10:22:38   associatedWith  MQTT2_ebusd
     2021-01-23 02:58:23   attrTemplateVersion 20200824
     2021-01-30 10:22:38   datetime       
     2021-01-30 10:22:38   error           
     2021-01-30 11:45:53   formatedUptime  0 000 01:07
     2021-01-30 10:22:38   id             
     2021-01-30 10:22:38   queryexistence 
     2021-01-30 10:38:48   running         true
     2021-01-30 10:52:59   scan            "finished"
     2021-01-30 10:39:05   signal          true
     2021-01-30 10:22:38   signoflife     
     2021-01-30 10:22:37   state           getAll
     2021-01-30 10:40:50   updatecheck     "version 3.4 available"
     2021-01-30 11:45:53   uptime          4049
     2021-01-30 10:38:48   version         "ebusd 21.1.v21.1-12-gccfc025"
Attributes:
   IODev      ebusMQTT
   autocreate 1
   bridgeRegexp (ebus..*?)/(bai|\d+|cc|e7f|ehp|f\d\d|hc|he.|hmu|hwc|mc|mc.\d|omu|omu.\d|pms|rcc|rcc.\d|sc|sdr_p|solar|ui|uih|v\d\d|v81.\d|vd\d|vl\d|vr_\d\d|zeo)/.*:.* "$1_$2"
(ebus..*?)/(global|broadcast|general|scan([^/]*))/.*:.* "$1"
   comment    NOTE: additional templates and code have been downloaded from svn (contrib).
   devStateIcon 1.true:it_net 1.false:it_net@red  2.true:lan_rs485 2.false:lan_rs485@red
   icon       sani_boiler_temp
   model      eBus_daemon_splitter
   readingList ebusd/global/version:.* version
ebusd/global/running:.* running
ebusd/global/scan:.* scan
ebusd/global/uptime:.* uptime
ebusd/global/updatecheck:.* updatecheck
ebusd/global/signal:.* signal
ebusd/broadcast/datetime:.* datetime
ebusd/broadcast/error:.* error
ebusd/broadcast/id:.* id
ebusd/broadcast/queryexistence:.* queryexistence
ebusd/broadcast/signoflife:.* signoflife
ebusd/scan\x2e08/:.* scan.08
ebusd/scan\x2e15/:.* scan.15
ebusd/scan\x2e18/:.* scan.18
ebusd/scan\x2e26/:.* scan.26
ebusd/scan\x2e76/:.* scan.76
   room       EBus
   setList    getKnown:noArg ebusd/list onlyknown
  getAll:noArg ebusd/list
   stateFormat Status:
1:running
Signal:
2:signal
<br>Uptime: formatedUptime
   userReadings formatedUptime:uptime.* {my $m = ReadingsVal($name,"uptime",0)/60;; return sprintf "0 000 00:%02d", $m if $m < 60;; my $h = $m / 60;; $m %= 60;; return sprintf "0 000 %02d:%02d", $h, $m if $h < 24;; my $d = $h / 24;; $h %= 24;; return sprintf "0 %03d %02d:%02d", $d, $h, $m if $d <365;; my $y = $d / 365;; $d %= 365;; return sprintf "%d %03d %02d:%02d", $y, $d, $h, $m}

Hier sind auch einige Readings erkannt worden, aber es werden immer nur die Uptime-Readings aktualisiert und es werden auch durch das Autocreate keine neuen MQTT2-Devices je nach empfangenen Telegrammen angelegt.

Könnt ihr mir anhand dieser Infos helfen wo bei mir den Hase im Pfeffer liegt oder welche Infos braucht ihr ggf. noch?

Gruß
Wolle

[Wolle02]

Wenn ich das beim Lesen in den vielen Threads zu dem Thema jetzt richtig verstanden habe, werden bei mir keine CSV Dateien geladen. Ich habe gelesen, dass man beim RPi 4 die Latenzeinstellung auf 60000 hochdrehen soll; hab ich probiert, sogar mit 100000. Leider wird immer noch nichts geladen.

Ein

Code Auswählen Erweitern

ebusd --scanconfig --checkconfig bring als Ergebnis

Code Auswählen Erweitern

2021-01-30 16:42:29.805 [main notice] ebusd 21.1.v21.1-12-gccfc025 performing configuration check...
2021-01-30 16:42:29.962 [main notice] found messages: 11 (0 conditional on 0 conditions, 0 poll, 4 update)
2021-01-30 16:42:29.963 [main notice] ebusd stopped


Das Verzeichnis /etc/ebusd ist bei mir leer.

Ich bin jetzt etwas hilflos.....

[john30]

Könnt ihr mir anhand dieser Infos helfen wo bei mir den Hase im Pfeffer liegt oder welche Infos braucht ihr ggf. noch?

schau doch mal in das Logfile unter /var/log/ebusd zeitnah nach dem Start des Dienstes. Da müsste zu finden sein, warum nichts gescannt wird.

[john30]

Maybe John can say something about it 

sure I can!
The weird thing about the V32 coupler is that it only passed a very small number of message 1:1 (with address replacement) from one side to the other (b504 and b505 if I remember correctly).
But the really interesting stuff (all b5090d+b5090e) is just not working at all (as these address the coupler itself). Instead, the message definition has to be replaced by a completely different one and in addition to that, the timing is completely ruined.
I was really surprised to see that this device is working at all, as it is far away from being eBUS specification compliant.

[Wolle02]

Folgendes finde ich nach dem Start des ebusd im Log:

Code Auswählen Erweitern

2021-01-30 18:35:30.784 [main notice] ebusd 21.1.v21.1-12-gccfc025 started with auto scan
2021-01-30 18:35:30.784 [main info] loading configuration files from http://ebusd.eu/config/
2021-01-30 18:35:30.820 [main info] reading templates /
2021-01-30 18:35:30.860 [main info] read templates in /
2021-01-30 18:35:30.860 [main info] reading file memory.csv
2021-01-30 18:35:30.891 [main info] successfully read file memory.csv
2021-01-30 18:35:30.891 [main info] reading file broadcast.csv
2021-01-30 18:35:30.923 [main info] successfully read file broadcast.csv
2021-01-30 18:35:30.923 [main info] read config files
2021-01-30 18:35:30.924 [bus notice] bus started with own address ff/04
2021-01-30 18:35:30.924 [main info] registering data handlers
2021-01-30 18:35:30.924 [mqtt info] mosquitto version 1.5.7 (compiled with 1.4.10)
2021-01-30 18:35:30.928 [mqtt debug] connection requested
2021-01-30 18:35:30.928 [main info] registered data handlers
2021-01-30 18:35:30.972 [bus notice] signal acquired
2021-01-30 18:35:31.013 [mqtt notice] connection established
2021-01-30 18:35:31.013 [mqtt debug] publish ebusd/global/version "ebusd 21.1.v21.1-12-gccfc025"
2021-01-30 18:35:31.013 [mqtt debug] publish ebusd/global/running true
2021-01-30 18:35:31.181 [bus notice] new master 10, master count 1
2021-01-30 18:35:31.232 [bus notice] new master 71, master count 2
2021-01-30 18:35:31.232 [update info] received MS cmd: 1076b5110101 / 09423f3506ffff0000ff
2021-01-30 18:35:31.232 [update notice] received unknown MS cmd: 1076b5110101 / 09423f3506ffff0000ff
2021-01-30 18:35:31.462 [bus notice] new master 03, master count 3
2021-01-30 18:35:31.462 [update info] received MS cmd: 7108b5110107 / 0a16400101083600000000
2021-01-30 18:35:31.462 [update notice] received unknown MS cmd: 7108b5110107 / 0a16400101083600000000
2021-01-30 18:35:31.554 [update info] received MS cmd: 1076b512030f0201 / 07008000170212ff
2021-01-30 18:35:31.555 [update notice] received unknown MS cmd: 1076b512030f0201 / 07008000170212ff
2021-01-30 18:35:31.786 [bus notice] device status: reset
2021-01-30 18:35:31.855 [update info] received MS cmd: 1026b5230106 / 10f201100100800080008000800080503d
2021-01-30 18:35:31.855 [update notice] received unknown MS cmd: 1026b5230106 / 10f201100100800080008000800080503d
2021-01-30 18:35:32.152 [update info] received MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 18:35:32.152 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 18:35:32.417 [update info] received MS cmd: 1008b51009000048ffffff060000 / 0101
2021-01-30 18:35:32.417 [update notice] received unknown MS cmd: 1008b51009000048ffffff060000 / 0101
2021-01-30 18:35:32.796 [bus notice] new master 13, master count 4
2021-01-30 18:35:32.796 [update info] received MS cmd: 1018b51009000000ffffff050000 / 0101
2021-01-30 18:35:32.796 [update notice] received unknown MS cmd: 1018b51009000000ffffff050000 / 0101
2021-01-30 18:35:33.218 [update info] received MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 18:35:33.219 [update notice] received unknown MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 18:35:33.468 [update info] received MS cmd: 1026b5230402000145 / 020164
2021-01-30 18:35:33.468 [update notice] received unknown MS cmd: 1026b5230402000145 / 020164
2021-01-30 18:35:34.699 [update info] received MS cmd: 7108b5110107 / 0a16400101083600000000
2021-01-30 18:35:34.699 [update notice] received unknown MS cmd: 7108b5110107 / 0a16400101083600000000
2021-01-30 18:35:35.913 [update info] received MS cmd: 7108b5120e111702f901ee0126021274040000 / 020232
2021-01-30 18:35:35.913 [update notice] received unknown MS cmd: 7108b5120e111702f901ee0126021274040000 / 020232
2021-01-30 18:35:38.154 [update info] received MS cmd: 7108b5110107 / 0a16400101083600000000
2021-01-30 18:35:38.154 [update notice] received unknown MS cmd: 7108b5110107 / 0a16400101083600000000


Scheinbar wird da schon gescannt, aber nichts gefunden oder das richtige geladen.
Ich habe hier eine Vaillant Heizung mit ecoTec plus Gastherme und aroTherm Flex Wärmepumpe und einem VRC 700 Steuergerät. Gibt es dafür keine csv Files?
Was kann ich da tun?

[john30]

Folgendes finde ich nach dem Start des ebusd im Log:

das war zu kurz, da der scan der gesehenen Geräte mit gewisser Verzögerung startet. Und mach doch mal den Log level auf info, mit debug sieht man ja nichts mehr vor lauter messages

[Wolle02]

Und mach doch mal den Log level auf info, mit debug sieht man ja nichts mehr vor lauter messages

Sehr gerne. Die Einstellung hatte ich aus dem Inbetriebnahme-Thread, weil das da von Reinhart so vorgegeben bzw. empfohlen wurde. Da hab ich mich dann sicherheitshalber dran gehalten 

das war zu kurz, da der scan der gesehenen Geräte mit gewisser Verzögerung startet.

Hier dann mal ein längerer Logauszug mit Loglevel 'info' (wobei sich da an der Logmenge scheinbar nichts geändert hat):

Code Auswählen Erweitern

2021-01-30 19:10:52.439 [main notice] ebusd 21.1.v21.1-12-gccfc025 started with auto scan
2021-01-30 19:10:52.439 [main info] loading configuration files from http://ebusd.eu/config/
2021-01-30 19:10:52.477 [main info] reading templates /
2021-01-30 19:10:52.511 [main info] read templates in /
2021-01-30 19:10:52.511 [main info] reading file memory.csv
2021-01-30 19:10:52.552 [main info] successfully read file memory.csv
2021-01-30 19:10:52.552 [main info] reading file broadcast.csv
2021-01-30 19:10:52.586 [main info] successfully read file broadcast.csv
2021-01-30 19:10:52.586 [main info] read config files
2021-01-30 19:10:52.586 [bus notice] bus started with own address ff/04
2021-01-30 19:10:52.586 [main info] registering data handlers
2021-01-30 19:10:52.586 [mqtt info] mosquitto version 1.5.7 (compiled with 1.4.10)
2021-01-30 19:10:52.591 [main info] registered data handlers
2021-01-30 19:10:52.602 [bus error] device status: unexpected available enhanced following byte 1
2021-01-30 19:10:52.602 [bus notice] signal acquired
2021-01-30 19:10:52.681 [mqtt notice] connection established
2021-01-30 19:10:52.714 [bus notice] device status: reset
2021-01-30 19:10:53.741 [bus notice] new master 10, master count 1
2021-01-30 19:10:54.939 [bus notice] new master 03, master count 2
2021-01-30 19:10:54.940 [update info] received MS cmd: 1008b5110101 / 0949450080ffff0100ff
2021-01-30 19:10:54.940 [update notice] received unknown MS cmd: 1008b5110101 / 0949450080ffff0100ff
2021-01-30 19:10:55.200 [bus notice] new master 71, master count 3
2021-01-30 19:10:55.204 [update info] received MS cmd: 1076b5110101 / 0948451a06ffff0000ff
2021-01-30 19:10:55.204 [update notice] received unknown MS cmd: 1076b5110101 / 0948451a06ffff0000ff
2021-01-30 19:10:55.850 [update info] received MS cmd: 1076b512030f0201 / 07008000490212ff
2021-01-30 19:10:55.850 [update notice] received unknown MS cmd: 1076b512030f0201 / 07008000490212ff
2021-01-30 19:10:56.151 [update info] received MS cmd: 1026b5230106 / 103d024e0100800080008000800080503d
2021-01-30 19:10:56.151 [update notice] received unknown MS cmd: 1026b5230106 / 103d024e0100800080008000800080503d
2021-01-30 19:10:56.447 [update info] received MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 19:10:56.447 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 19:10:56.661 [update info] received BC cmd: 10feb505025c00
2021-01-30 19:10:56.661 [update notice] received unknown BC cmd: 10feb505025c00
2021-01-30 19:10:56.750 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:10:56.750 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:10:57.003 [bus notice] max. symbols per second: 114
2021-01-30 19:10:57.004 [update info] received MS cmd: 1008b51009000047ffffff060000 / 0101
2021-01-30 19:10:57.004 [update notice] received unknown MS cmd: 1008b51009000047ffffff060000 / 0101
2021-01-30 19:10:57.087 [update info] received MS cmd: 7108b5120e1149022c021c029c021274040000 / 020232
2021-01-30 19:10:57.088 [update notice] received unknown MS cmd: 7108b5120e1149022c021c029c021274040000 / 020232
2021-01-30 19:10:57.413 [bus notice] new master 13, master count 4
2021-01-30 19:10:57.413 [update info] received MS cmd: 1018b51009000000ffffff050000 / 0101
2021-01-30 19:10:57.413 [update notice] received unknown MS cmd: 1018b51009000000ffffff050000 / 0101
2021-01-30 19:10:57.681 [update info] received MS cmd: 1076b5040100 / 0a03591019300106211a06
2021-01-30 19:10:57.681 [update notice] received unknown MS cmd: 1076b5040100 / 0a03591019300106211a06
2021-01-30 19:10:57.921 [update info] received MS cmd: 1008b507020945 / 02cc01
2021-01-30 19:10:57.921 [update notice] received unknown MS cmd: 1008b507020945 / 02cc01
2021-01-30 19:10:58.160 [update info] received BC cmd: 10feb516080055101930010621
2021-01-30 19:10:58.160 [update notice] received unknown BC cmd: 10feb516080055101930010621
2021-01-30 19:10:58.451 [update info] received MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 19:10:58.451 [update notice] received unknown MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 19:10:58.700 [update info] received MS cmd: 1026b5230402000145 / 020164
2021-01-30 19:10:58.700 [update notice] received unknown MS cmd: 1026b5230402000145 / 020164
2021-01-30 19:10:59.061 [update info] received MS cmd: 1018b5110100 / 08890113001f100000
2021-01-30 19:10:59.061 [update notice] received unknown MS cmd: 1018b5110100 / 08890113001f100000
2021-01-30 19:10:59.324 [update info] received MS cmd: 1008b5110100 / 09490212320009000000
2021-01-30 19:10:59.324 [update notice] received unknown MS cmd: 1008b5110100 / 09490212320009000000
2021-01-30 19:10:59.546 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:10:59.546 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:10:59.617 [update info] received MS cmd: 1076b51303040d00 / 020d00
2021-01-30 19:10:59.618 [update notice] received unknown MS cmd: 1076b51303040d00 / 020d00
2021-01-30 19:10:59.836 [update info] received BC cmd: 10feb51603012706
2021-01-30 19:10:59.836 [update notice] received unknown BC cmd: 10feb51603012706
2021-01-30 19:11:00.568 [update info] received MS cmd: 1018b512020064 / 00
2021-01-30 19:11:00.572 [update notice] received unknown MS cmd: 1018b512020064 / 00
2021-01-30 19:11:00.798 [update info] received MS cmd: 1008b512020064 / 00
2021-01-30 19:11:00.798 [update notice] received unknown MS cmd: 1008b512020064 / 00
2021-01-30 19:11:01.126 [update info] received MS cmd: 1018b5120204ff / 0101
2021-01-30 19:11:01.126 [update notice] received unknown MS cmd: 1018b5120204ff / 0101
2021-01-30 19:11:01.357 [update info] received MS cmd: 1008b5120204ff / 00
2021-01-30 19:11:01.357 [update notice] received unknown MS cmd: 1008b5120204ff / 00
2021-01-30 19:11:01.674 [update info] received MS cmd: 1018b513020508 / 00
2021-01-30 19:11:01.674 [update notice] received unknown MS cmd: 1018b513020508 / 00
2021-01-30 19:11:01.909 [update info] received MS cmd: 1008b513020528 / 0101
2021-01-30 19:11:01.909 [update notice] received unknown MS cmd: 1008b513020528 / 0101
2021-01-30 19:11:02.122 [update info] received BC cmd: 10feb510020601
2021-01-30 19:11:02.122 [update notice] received unknown BC cmd: 10feb510020601
2021-01-30 19:11:02.336 [update info] received BC cmd: 10feb508020900
2021-01-30 19:11:02.336 [update notice] received unknown BC cmd: 10feb508020900
2021-01-30 19:11:02.591 [main error] scan config 08: ERR: element not found
2021-01-30 19:11:02.614 [update info] received MS cmd: 1026b5030c0700ffffffffffffffffffff / 0101
2021-01-30 19:11:02.614 [update notice] received unknown MS cmd: 1026b5030c0700ffffffffffffffffffff / 0101
2021-01-30 19:11:02.993 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:02.993 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:04.592 [main error] scan config 15: ERR: element not found
2021-01-30 19:11:04.787 [update info] received MS cmd: 1008b5110101 / 0949450080ffff0100ff
2021-01-30 19:11:04.787 [update notice] received unknown MS cmd: 1008b5110101 / 0949450080ffff0100ff
2021-01-30 19:11:05.057 [update info] received MS cmd: 7108b5120e1148022a021c029e021273040000 / 020232
2021-01-30 19:11:05.058 [update notice] received unknown MS cmd: 7108b5120e1148022a021c029e021273040000 / 020232
2021-01-30 19:11:05.120 [update info] received MS cmd: 1076b5110101 / 0949451a06ffff0000ff
2021-01-30 19:11:05.121 [update notice] received unknown MS cmd: 1076b5110101 / 0949451a06ffff0000ff
2021-01-30 19:11:06.121 [update info] received MS cmd: 1076b512030f0201 / 07008000480212ff
2021-01-30 19:11:06.121 [update notice] received unknown MS cmd: 1076b512030f0201 / 07008000480212ff
2021-01-30 19:11:06.454 [update info] received MS cmd: 1026b5230106 / 103d024e0100800080008000800080503d
2021-01-30 19:11:06.454 [update notice] received unknown MS cmd: 1026b5230106 / 103d024e0100800080008000800080503d
2021-01-30 19:11:06.511 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:06.511 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:06.592 [main error] scan config 18: ERR: element not found
2021-01-30 19:11:06.766 [update info] received MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 19:11:06.767 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 19:11:07.012 [bus notice] max. symbols per second: 116
2021-01-30 19:11:07.768 [update info] received MS cmd: 1008b51009000047ffffff060000 / 0101
2021-01-30 19:11:07.768 [update notice] received unknown MS cmd: 1008b51009000047ffffff060000 / 0101
2021-01-30 19:11:08.467 [update info] received MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 19:11:08.467 [update notice] received unknown MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 19:11:08.592 [main error] scan config 26: ERR: element not found
2021-01-30 19:11:09.452 [update info] received MS cmd: 1026b5230402000145 / 020164
2021-01-30 19:11:09.452 [update notice] received unknown MS cmd: 1026b5230402000145 / 020164
2021-01-30 19:11:09.875 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:09.875 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:10.593 [main error] scan config 76: ERR: element not found
2021-01-30 19:11:12.805 [update info] received MS cmd: 7108b5120e1147022a021c029f021274040000 / 020232
2021-01-30 19:11:12.805 [update notice] received unknown MS cmd: 7108b5120e1147022a021c029f021274040000 / 020232
2021-01-30 19:11:13.344 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:13.345 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:14.685 [update info] received MS cmd: 1008b5110101 / 0948450080ffff0100ff
2021-01-30 19:11:14.685 [update notice] received unknown MS cmd: 1008b5110101 / 0948450080ffff0100ff
2021-01-30 19:11:14.954 [update info] received MS cmd: 1076b5110101 / 0948452706ffff0000ff
2021-01-30 19:11:14.954 [update notice] received unknown MS cmd: 1076b5110101 / 0948452706ffff0000ff
2021-01-30 19:11:15.958 [update info] received MS cmd: 1076b512030f0201 / 07008000470212ff
2021-01-30 19:11:15.958 [update notice] received unknown MS cmd: 1076b512030f0201 / 07008000470212ff
2021-01-30 19:11:16.260 [update info] received MS cmd: 1026b5230106 / 103c024e0100800080008000800080503d
2021-01-30 19:11:16.260 [update notice] received unknown MS cmd: 1026b5230106 / 103c024e0100800080008000800080503d
2021-01-30 19:11:16.556 [update info] received MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 19:11:16.556 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2021-01-30 19:11:16.733 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:16.733 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:17.606 [update info] received MS cmd: 1008b51009000047ffffff060000 / 0101
2021-01-30 19:11:17.606 [update notice] received unknown MS cmd: 1008b51009000047ffffff060000 / 0101
2021-01-30 19:11:18.280 [update info] received MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 19:11:18.280 [update notice] received unknown MS cmd: 1026b5230f05ff0000140000ffff000000000000 / 0101
2021-01-30 19:11:19.265 [update info] received MS cmd: 1026b5230402000145 / 020164
2021-01-30 19:11:19.265 [update notice] received unknown MS cmd: 1026b5230402000145 / 020164
2021-01-30 19:11:20.178 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:20.179 [update notice] received unknown MS cmd: 7108b5110107 / 0a00510101083600000000
2021-01-30 19:11:20.988 [update info] received MS cmd: 7108b5120e1148022b021c02a1021273040000 / 020232
2021-01-30 19:11:20.988 [update notice] received unknown MS cmd: 7108b5120e1148022b021c02a1021273040000 / 020232
2021-01-30 19:11:22.201 [update info] received MS cmd: 7108b51a0304dc32 / 0edc07c0cfc07b3c00b01b20000000
2021-01-30 19:11:22.201 [update notice] received unknown MS cmd: 7108b51a0304dc32 / 0edc07c0cfc07b3c00b01b20000000
2021-01-30 19:11:22.564 [update info] received MS cmd: 7108b51a0304dd33 / 0edd00000082000000000000000000
2021-01-30 19:11:22.564 [update notice] received unknown MS cmd: 7108b51a0304dd33 / 0edd00000082000000000000000000
2021-01-30 19:11:22.997 [update info] received MS cmd: 7108b51a0304de34 / 0edecf2000c0022101001800061800
2021-01-30 19:11:22.997 [update notice] received unknown MS cmd: 7108b51a0304de34 / 0edecf2000c0022101001800061800
2021-01-30 19:11:23.041 [bus notice] max. symbols per second: 121
2021-01-30 19:11:23.404 [update info] received MS cmd: 7108b51a0304df35 / 0edf00000000000100b00000000000
2021-01-30 19:11:23.408 [update notice] received unknown MS cmd: 7108b51a0304df35 / 0edf00000000000100b00000000000
2021-01-30 19:11:23.767 [update info] received MS cmd: 7108b51a0304e036 / 0ee000000000000000000000000000
2021-01-30 19:11:23.767 [update notice] received unknown MS cmd: 7108b51a0304e036 / 0ee000000000000000000000000000
2021-01-30 19:11:24.262 [update info] received MS cmd: 7108b5110107 / 0a00510101083600000000


Bei 19:11:02 und 19:11:04 und 19:11:06 scheint er zu scannen, aber nichts zu finden!?

[Wolle02]

Ok, ich hab den Fehler gefunden. 
Ich bin einem Missverständnis aufgesessen und zwar habe ich den ebusd mit dem Schalter -r gestartet, weil ich dachte, dass das eine Sicherheitsoption wäre, damit nichts auf den Bus geschrieben werden kann. Scheinbar gilt das aber nicht für die Kommunikation mit dem Bus, sondern für den ganzen ebusd. Damit konnte er dann natürlich nichts schreiben.
Jetzt scheints erstmal zu laufen. Jetzt muss ich weiter probieren.

Vielen Dank erstmal.

[tlc]

sure I can!
The weird thing about the V32 coupler is that it only passed a very small number of message 1:1 (with address replacement) from one side to the other (b504 and b505 if I remember correctly).
But the really interesting stuff (all b5090d+b5090e) is just not working at all (as these address the coupler itself). Instead, the message definition has to be replaced by a completely different one and in addition to that, the timing is completely ruined.
I was really surprised to see that this device is working at all, as it is far away from being eBUS specification compliant.

@john30, thanks a lot for jumping in.
Presuming that you will ever have the time to fix this timing issue in order for ebusd to handle the messages translated by a VR32, will the issue be solvable at software level? Or the fixes will be done also at hardware level, which means a new HW version of the adapter will be necessary?

Cheers,
Cristian

[john30]

@john30, thanks a lot for jumping in.
Presuming that you will ever have the time to fix this timing issue in order for ebusd to handle the messages translated by a VR32, will the issue be solvable at software level? Or the fixes will be done also at hardware level, which means a new HW version of the adapter will be necessary?

it is only at software level, but it is so uncredibly ugly 
basically there is a simple translation of the original message to the one that has to be sent to the VR32, and thus is the message definition. but to solve this on an automatic level in ebusd code is a great hack and I'm lacking time to do it.