A schedule specifies the simulation locations that a train stops at (or passes) whilst it is in the simulated area. It also specifies where and when the train enters the simulated area, unless the schedule is to be assigned to a train that is already in the simulated area, for example a train terminating at a major station and forming a new service. Certain train characteristics are defined within the schedule too.
A schedule location defines the times at which the train should arrive and depart, or pass, a simulation location, and the platform or line that it should use when doing so. It also defines the "path" and "line" codes, where appropriate, where there are multiple lines that can be used before or after the location.
Special rules apply to non-passenger trains (as defined in the schedule), which will not stop at a location even if planned to do so, unless any of the following conditions apply:
1. The train needs to reverse (change direction), or
2. The train has activities to carry out at that location, or
3. The "minimum dwell" value is set to a non-zero value.
Non-passenger trains will not wait until the planned departure time if they are ready to depart earlier. Note that a crew-change activity will have the effect of making the train wait until close to the planned departure time.
The planned stop position is shown in a schedule view whenever a value other than the default is used. This will either be:
N = "Near end", or
F = "Far end",
with the addition of "/XX", where a non-zero offset value is specified, where XX represents the distance in metres that the rear of the train will stop after passing a "near end" stop position or before reaching a "far end" stop position.
External locations allow the progress of a train to be (crudely) simulated before it enters the simulated area, and to show locations in the schedule that are outside (both before and after) the simulated area. Note that a limitation of the simulation is that it cannot generally account for the railway geography outside the simulated area, so may appear to produce some unrealistic situations in this respect. The exception is when the train in question has already entered another PCSig simulation area that is chained (directly or indirectly) to the simulation in use, in which case the actual progress of the train in that simulation area will be reported.
An activity (or association) defines a process that a train must carry out whilst at a location, for example detaching a portion. Note that reversing (changing direction) does not need to be specified as an activity, as this will happen automatically if necessary.
A location line-up shows all schedules planned to pass or call at the selected location in the near future, in a similar manner to a "TRUST line-up" that real signallers often use. Schedules will be added to the line-up when there is less than 2 hours to the planned departure time from their origin, which is an approximation for the process of schedules being manually or automatically "called" in reality..
By default, the main location associated with the signal box being operated will be selected - note that trains are not always timed at each signal box on relatively simple sections of railway, so the default location might actually be the nearest location at which trains are timed, or it might be necessary to select a different location (e.g. where a timing location is used in some timetable data but not others). It will not automatically refresh - click the 'refresh' button to manually refresh. Further location line-ups can be opened in new windows.
Double-click a schedule in the location line-up to view the full schedule data, or right-click and select 'edit schedule' to make changes to it "on the fly". Note that this will not change the base timetable data, only that for the single schedule that has already been "called". This can be useful to force signal boxes under computer control to make certain regulating decisions.