Hello all, While I'm waiting for the motivation to get my hands dirty and start the woodwork on my other project, I felt a creative wave and started developing software utilizing the TSW API. This is something I’ve always wanted to create for my control desk. What is it? It is an MFD (Multi-Functional Display). What is an MFD? They are the screens (usually three) found in modern locomotives that display all sorts of information, such as the speedometer, traction values, Ebula, etc. Since I’m building a control desk, I want it to feel as realistic as possible. What do I have currently? Functions: API: I have a robust API polling solution that automatically looks for the API Key document and gathers all endpoints from a designated file for easy expansion. It creates subscriptions with different polling intervals and exposes all API responses for use anywhere in the app. Webserver: It creates a webserver so the displays are available via my local network. It can be easily accessible through a tablet, phone, or another computer on the same network. Components: I designed the system to be easily expandable, allowing for new pages, functions, and templates to be added in the future. Templates: Currently, I have two templates: a "traditional" screen with physical buttons around the edges and a touchscreen template for more modern units. Main Cluster: This is based on the speedometer screen from the Railpool Vectron, influenced by several other German electric locomotives. As you can see from the screenshot below, it features a functioning: Speedometer (including the AFB diamond, LZB triangle, and next speed limit display). LZB distance bar. PZD indicator bar with all required indicators for HUD-less driving. SIFA indicator. Tractive/Brake effort dial, with target effort triangles and percentage displays. List elements to display different messages based on various values. And of course, night mode Limitations: Because of how the TSW API is structured, many systems are unique to each locomotive (e.g., three different PZB systems and two LZB systems). This has mainly been set up for the Vectron, BR182/1116, and BR146. I still haven't found all the values to reach 100% functionality across all four locomotives. It is currently quite "broken" for EMUs and cab cars, and I haven't had the patience to hunt down those specific endpoints yet. I even set up a helper program, that maps all available endpoints, and was socked that there can be more than 200.000. It took countless hours to identify the ones I'm using right now. EBULA This is my own interpretation of how an Ebula works, as I have never seen one in real life. I sifted through the internet for references and documentation. I was able to find parts of some manuals, plus thankfully there are some data readily available for the TSW routes on Train Sim Community. During my search I have found the online-ebula page, but by this time I was so invested in creating my own I felt like cheating for using it in my project, so decided not to even check the demo out. In my version, the Ebula: Shows your current position on the track. Shows what is coming up (speed limits, tunnels, signals). Advances automatically as you pass waypoints. Displays route details (length, max train speed, next stop). Shows the train's timetable (if loaded beforehand). Records arrival/departure times and calculates delays. Logs data to a file (I am planning a statistics page). Includes a switchable GNT speed limit display, alternative route switching for double tracks. Limitations: All track info, direction data, and timetables must be created from scratch. Recording the location for each point is time-consuming, travelling up and down the line multiple times. Currently, I have only finished the Köln-Aachen main line and S-Bahn line in both direction, without the alternative route, as I was checking out the remaster when decided to start this. I plan to finish SKA, then move on to Frankfurt-Fulda and Dresden-Leipzig ans they are inviting routes where I spend very little time. Future Plans Expanding EBULA data: I want this to be usable across the TSW universe. More components: I want to create pages for electric motor status, overhead line voltage, brake pipe pressure, etc. UK-based components: I’d like to expand beyond the continent and include UK systems. Editors: I’m getting tired of editing code files manually, so I plan to build a dedicated editor for pages, Ebula data, and timetables. Disclaimer: I am not a software developer or a rail professional; I’m doing this purely out of interest. I have a basic background in coding and enjoy self-teaching, but my time is limited, so I’ve used AI to assist with parts of the solution. My knowledge of systems like LZB, PZB, and AFB comes strictly from simulators and the internet—so it is definitely not 100% accurate. Publishing: I don’t want to be the person who shares a project and then sits on it. We all love trains, and when the time is right, I want people who are interested to have an opporunity to try it. It isn’t ready yet, but if you have a bit of a coding background or technical knowledge of these train systems and want to help, feel free to reach out.
