Wiki source code of Hardwarecontrol
Last modified by stu115775 on 2025/01/30 12:17
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | The Hardwarecontrol should give an abstraction for controllng the Hardware wich also makes sure some of the base rules apply. | ||
| 2 | |||
| 3 | Tasks/Rules the Hardwarecontrol should manage: | ||
| 4 | |||
| 5 | * train tracking | ||
| 6 | * block locking/crash avoidance | ||
| 7 | * speed control: slow down(/speed up?)/parking in a segment | ||
| 8 | * same speed policy (same speed on all tracks beneath a train) | ||
| 9 | * automatic signal management | ||
| 10 | * automatic point branching | ||
| 11 | |||
| 12 | We split up the track into smaller interacting parts to achive this: | ||
| 13 | |||
| 14 | * Segment (1 Track, 2 Contacts, 1 Signal) | ||
| 15 | * Segment_bid (bi-directional) (1 Track, 2 Contacts, 2 Signals) | ||
| 16 | * Track (1 Track) | ||
| 17 | * Track_bid (1 Track) | ||
| 18 | * Point_in (1 Point with 2 incoming and 1 outgoing tracks) | ||
| 19 | * Point_out (1 Point with 1 incoming and 2 outgoing tracks) | ||
| 20 | * Point_bid (1 Point, 2 to 1 bi-directional point) | ||
| 21 | * Cross_in (1 Track, 2 Points, has 2 incoming, 1 outgoing and 1 bi-directional track where incoming trains get on the main track and outgoing come from the side track) | ||
| 22 | * Cross_out (1 Track, 2 Points, has 1 incoming, 2 outgoing and 1 bi-directional track where outgoing trains come from the main track and incoming go to the side track) | ||
| 23 | |||
| 24 | The differenciation of bi-directional and uni-directional Elements is done to have simpler Parts for the unidirectional parts. | ||
| 25 | |||
| 26 | With these we can model the railway system by connecting these parts in terms of mapping input and output values according to the connections. To fullfill the tasks/rules every connection (uni-directional) has the following variables, where in and out descibes if it's an input/output of the previous part in travel direction: | ||
| 27 | |||
| 28 | 1. out int requestLockFor: >0: id of the track to request the lock for, -1: get next lock (not supported if nondeterministic) | ||
| 29 | 1. out int requestLockTrain: when requestLockFor!=0 the id of the incoming train | ||
| 30 | 1. in bool Locked: the next part is locked and expects an incoming train, lock is releaded when train reaches the next track | ||
| 31 | 1. in bool Branched: the connection to the next "part"(save track) is branched (to set the signal) | ||
| 32 | 1. in bool PullSpeed: the speed to synchronize to have one speed for all used tracks. | ||
| 33 | |||
| 34 | To stay dependency cycle free there has to be a part in each cycle wich writes each of these in order and first read afterwards. |