Moin Tom,
the sensors are now ok. I see no error with the 8 Inputs and 8 Outputs now. Great!
Then basic input/output support is 
What do you think about a list of events of the node, in the setup procedure of the board? I.e. I click a signal/point/sensor, set the node and there is a button to read all events from node, than a click on the event in the list to choose it for the signal/point/sensor? Not yet, but for the future
I like it, that will make life easier for future users 
Somehow I can’t access your site from my home IP, using a VPN I can access it…strange. It is a really nice article (I’ve read it using Firefox translate, my German is not that good.)
In the cbus branch manual is already a WIP page about CBUS/VLCB in the appendix, see here.
The manual also has a Lua scripting reference section under appendix, the pages are partly auto generated based on the Traintastic source code. Feedback and improvements and practical examples are very welcome
CBUS/VLCB is the first hardware system that has a proper throttle acquire/release, Traintastic’s HAL isn’t currently aware of that, so I need to make some adjustments there. The CANCAB also has a Steal option, that should make it possible to take control even if Traintastic doesn’t release it properly.
Traintastic doesn’t allow to change direction if the train is moving, I can add a world setting for that to make it configurable. (The default value is debatable then 
)
My todo list:
- Implement acquire/release awareness.
- When interface goes online sync power/estop.
- Basic list of discovered nodes. (nice to have)
Greetings,
Reinder
p.s. once all the basics are working I’ll merge it into master.