Is there any ways to couple or link a scenario and the state of a signal ?
I did not find anything about this question in previous posts. If I'm wrong, don't be too rude with me ;-)
So, my question is to know whether there's a possibility to couple, to link an action in a scenario with the
state of a signal.
An example to be more clear (I hope): I want to change the state of signal at a specific time or date in order to
simulate a clearance or an authorisation for a train...
Hi Satnur !
I don't think that this can be done, signalling being limited to doing just certain basic functions linked to a switch/switches and track sections.
What you are thinking of, which is being done by a real dispatcher on real railways, would have to be programmed into the Timetable function and then set as required in a Standard scenario.
O t t o
Very soon a release just for you ;-)
This is the idea. For example, at Gare Saint Lazare, 2 minutes before the departure, a special light is flashing and the path is formed: the signal that protects the switch points, shows a light (green, yellow or double red) according to the status of the path (free, warn or danger...). In order to be more realistic, I was looking for a way to activate the signal according to the timetable.
Originally Posted by OTTODAD
Otto, when you're talking about "programmed into the Timetable function", you mean that it exists specific function that communicates with the signal through the lua script of the signal ?
The Timetable function in the Scenario Editor is limited to what it can be used for when creating Standard scenarios.
Originally Posted by satnur
Everything signals do is determined in their scripts and you can not code the same signal to do different things triggered by whatever and how and if it could be done would apply to this signal in all the routes it is being used in.
O t t o
While I don't suppose that this information will be useful for your situation, I include it for scenario writers that have similar desires.
Let's assume that ( in a simple problem,) you want your driver's train to wait behind a red signal for 2 minutes before starting its route. Place a "dummy train" in the signal block in front of your driver's train that will leave the block two minutes later than the start of the driver's train. The controlling signal for the driver will appear red, until the "dummy" train moves out of its block. The driver's signal will then go to amber. In the same fashion starting the dummy train one further block ahead will produce an initial amber for the driver's train. To make this function in the most simple manner set the priority of the dummy train to a higher status than the driver's train. For example, the dummy can be set to "Special" and the Driver's train set to "Stopping Passenger."
The above is not always necessary, and a good result can be obtained with long signal blocks by "timing" the trains. Reduce the programmed speed of the drivers train from 75% of posted limit to 25%, for example. The dispatcher function, running the signals, will assume that the driver's train will not come of the red, until the red has changed to amber. This "fooling" of the dispatcher function requires practice and patience.
These routines can be used anywhere in the scenario, but are easiest to demonstrate at the beginning of a scenario.