Operational turntables in timetable mode

Registered by James Ross on 2019-10-05

Add fully automated operational turntables to timetable mode, to be used by both player and AI trains.

Discussion: ???
Roadmap: https://trello.com/c/ADrh94Ol/414-operational-turntables-in-timetable-mode

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
James Ross
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

The use of turntables in timetable mode is based on the pool concept.
In line with normal pools, an engine can be sent to the pool or extracted from it.
Also in line with normal posts, a separate path must be defined for each storage track contained within the pool, as well as for access tracks.
The definition of tracks does, however, differ from normal pools :
 - each storage track must be connected to the relevant turntable
 - each access track must also be connected to the relevant turntable.

Access tracks are not directly linked to storage tracks but all storage tracks share the same access track (or tracks).

All access to and from the storage tracks runs via the turntable. A special qualifier, available for both commands to send to or extract from a pool, can be set to define in which direction (forward or reverse) the engine must leave the turntable.

If the turntable is to be used by different engine types, a separate pool must be set up for each engine type. These pools can share the turntable and the access paths but they cannot share storage paths, these must be uniquely allocated to a single specific pool only.

The pool must be identified to OR in the way as set for activities, using a turntable.dat file.
The turntable is identified in the pool definition through reference to the information in this turntable.dat file.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.