Moin Tom,
Thanks for the input, this also makes it possible to check Traintastic produced/consumend events against node configuration. I didn’t check the docs yet, but can we also determine if the node produces or consumes a specific event?
A Events tab could be added to CBUS/VLCB interdace dialog, something like:
| Node | Event | Node P/C | Traintastic P/C | Status | Description |
|---|---|---|---|---|---|
| 258 | 4 | Produced | Consumed |  Ok |
Turnout 5 mid |
| 258 | 5 | Consumed |  Missing in node |
Turnout 5 end |
This can help identifying mismatch between nodes and Traintastic. Synchronization should be manually I think, doing it at startup will put a massive load on the bus.
The turnout/signal output tab will need some adjustment as the Event number is just a small spinbox, that won’t fit long descriptions. Placing them vertical instead horizontal will fix that.
Something like this was also mentioned in MERG CBUS/VLCB hardware support - #183 by MZwa, back then I was unsure about the added value…but I’m starting to see it 
Maybe we can discuss it a bit more here what the options are pros/cons etc.
I didn’t do any CBUS/VLCB configuration myself yet, but I think in general it is a bit harder for the user than DCC/S88/LocoNet address stuff, so some extra help to find misconfiguration quickly is nice
Greetings,
Reinder