Hi DTG team, since a few month I’m the proud owner of my own crafted mini Br101 cabdesk. To link it to TSW I use an Arduino nano and an Open source project called Trenino (link to github). It works really well for most locos and EMUs (at least for the german ones, as I’m now mostly driving DB trains). However, I noticed a few missing APIs for some trains. Here is a list of the missing things that I Stumbled uppon: Br 642: turning the door manager via the API does nothing (doors don’t open) Br 442 (DRA, did not test the other versions): the highbeam does not work (there is nothing in the directory shown by trenino) Br 111 (all versions): you need to push the brake lever to the « Fahren » position in order to fully release brakes and that position is not accesible via the API. Br 147: all the PZB knobs (wachsam, frei, Befehl) are not trigerrable via the API (like for the 442 headlight, nothing showing in the directory) Br 147: no reverser axis so the button needs to be triggered ÖBB 1116: the reverser does not activate the cab when triggered by the api, it has to be activated with the keyboard. I would really like to get these few adjustments as it would add quite a lot of immersion to the gaming experience. If something is not clear, feel free to DM me or respond in the thread. As a little help to how trenino actually works, there is this great tutorial on youtube. Thanks for the answers
I'll try and take a look at some of these and see what can be done, or find them for you - in theory everything should be available, it's literally just taking the config and blasting it out to the API, there's no specific per-train setup for this beyond how the train is built in the game already. For the BR147 btw - it doesnt have an axis, so you will only get the buttons for that. Same for any other similar trains, the inputs on the API match with what's on the train. If you need a simplified unified interface, use the VirtualRailDriver part of the API where everything behaves more uniformly. Matt.
