Hier Auf Deutsch!
I provide a Windows program that displays the real-time arrival and departure schedules for long distance trains of the Deutsche Bahn AG using data from DB Vertrieb GmbH
The program allows you to search for any station, and once you select a station, it will show upcoming arrivals and departures according to the schedule. (Delays and other changes are not yet reflected.)
The program will also display this data on a RemoteSign - providing a realistic looking arrival and departure sign for your favorite station! (Yes! the sign is animated and makes the clicking noise as it updates!)
Here is a sample screen:
Requirements- Windows operating system (Windows XP or newer)
- Internet access
ScopeThe data supplied by DB Vertrieb GmbH is at present limited to scheduled long distance trains (Fernverkehr). It does not yet reflect delays and cancellations. The data is from the schedule.
Neither I nor DB Vertrieb GmbH are responsible for errors or omissions,
How to install and run DB:
- Run the installer found at https://s3-us-west-1.amazonaws.com/remotesign/setupDB.exe
(If Windows does not want to let the program run, override that and force it to run. See here for more information)
- Run the program that it installs, called DB
- Search for a station, for example enter 'Berlin' and press Enter or click the search button ->
- DB will present a list of possible matching stations, and select the first one for you too.
- You can click on any of the stations in the result list.
The DB installer installs a copy of RemoteSign also so that you can run it on the same machine.
Using one machineBy default, DB will use the copy of RemoteSign that came with it. To launch it simply click the button 'Launch local'.
DB will attempt to connect to the RemoteSign computer every 10 seconds, so just wait a short while after launching RemoteSign and it should connect.
If you have previously changed the configuration, here is how to get the 'Launch local' button to appear again:
1) In the RemoteSign configuration enter 127.1.1.1 as the IP address of the RemoteSign.
2) Click OK.
Using two machinesIf you want to run RemoteSign on a separate computer, and you do not yet have RemoteSign installed, get that in place first, see Installing RemoteSign
To get the train schedules to display on a RemoteSign you need to point the DB program to a copy of RemoteSign. Here is how to do that...
Assuming you have DB running on one machine and RemoteSign running on another, and both are connected to your network, here is how to proceed:
You need to know either name or the IP address of the RemoteSign machine.
On the RemoteSign machine (B), press the 'C' on the main screen on RemoteSign. This will bring up the Connection screen which will tell you the IP address - see the red ellipse in this example:
Make a note of that IP address and also ensure that the 'Wait for remote connection' option is selected as shown.
You can now close that screen.
On the DB machine, click the "Configure" button in the RemoteSign section.
Enter the IP address of the RemoteSign machine into the IP address field:
This will save the information for future runs automatically.
DB should then connect to the RemoteSign machine and send the train arrivals and departures information to it.
It will automatically update the screen every minute.
The next time you run DB it will also try to reconnect to the RemoteSign machine. If the RemoteSign cannot be found, or does not accept a connection, it will retry every 10 seconds.
You can also use the Windows name of the machine instead of the IP address (which may change from time to time).
Adjusting the layout of the RemoteSignYou can influence how the RemoteSign screen looks by adjusting the number of rows used and the size of the analog clock.
25 screen rows produces a good starting value. Increasing the rows on the screen makes the rows smaller and slower, so select a number of rows that produces legible text and also provides enough rows for the amount of schedule traffic you wish to see. An odd number of rows works better than an even number since there is an odd number of lines used for other purposes.
If you adjust the clock settings, you can elect to display an analog station clock, and then set how many rows the clock uses on the RemoteSign screen. Small stations with little traffic need fewer screen lines. If your RemoteSign computer is very slow, having too many rows may take too long for the screen to update when trains need to shift up a line.
Adjusting the appearance of the clockThe RemoteSign Configure button also provides a method to customize the appearance of the clock. Digital or analog mode can be selected. Digital mode allows a 12 or 24 hour clock and analog allows the size and colors of the clock face to be configured. Changes to the clock are reflected in the DB program as well as on a connected RemoteSign
Advanced configurationIt is possible to have RemoteSign running on another network, for example, at your friends house, and you can drive it from your house. This does however require the internet router where RemoteSign is running to allow traffic through to the machine running RemoteSign. All routers have the ability to do this, but the screens to do this are all different so you will need to consult your router help to make the changes, but here are the generic steps to do this:
- It is best to assign a static IP address to the machine that will be running RemoteSign. See your Windows help and control panel to do this.
- Install RemoteSign
- In the router administration direct internet traffic on port 50601 to the static IP address of the RemoteSign machine. Look for 'Port forwarding' or 'Port triggering'.
- Determine the external IP address of your router that is assigned to your router by your service provider.
- On the computer running DB, enter the IP address determined at step (4) above as the IP address of the RemoteSign machine.
If you wish to use a port other than 50601, you can edit the port that RemoteSign uses in the RemoteSign.ini file.
Select the same port number in the DB configuration screen too.
Version history1.05 Initial release
1.1 Switched to HTTPS in response to DB Vertrieb GmbH switching to HTTPS
220.127.116.11 added an error trap for an error that the DB Vertrieb GmbH server is returning instead of the data requested. DB AG have said the problem will be fixed with the next release of the API.