Changes for page Basic design
Last modified by nfl on 2025/01/30 12:05
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. krat1 +XWiki.sna - Content
-
... ... @@ -34,7 +34,7 @@ 34 34 35 35 == Train controller == 36 36 37 -Each train controller is set in a separate region with a referenced state. This state has the following interface :37 +Each train controller is set in a separate region with a referenced state. This state has the following interface 38 38 39 39 40 40 \\\\\\\\ ... ... @@ -41,13 +41,13 @@ 41 41 42 42 {{{ input int *_perm; # All permission variables (Tracks) input bool *_perm # KH permission variables input int trainNum; input bool cleanup; input bool debug; output bool *_req[]; # All request variables}}} 43 43 44 -The train controller is composed of several //Station-2-Station// controllers. These are combined to form a complete schedule. Additionally ,the cleanup signal has to be watched to abort the schedule and return back to the initial position.44 +The train controller is composed of several //Station-2-Station// controllers. These are combined to form a complete schedule. Additionally the cleanup signal has to be watched to abort the schedule and return back to the initial position. 45 45 46 46 == Station-2-Station controller == 47 47 48 -Each Station-2-Station controller realizes the movement from one of the stations (IC,OC,KH) to anotherstation. All controllers using IC or OC parts have to respect the traveling directions. For the Kicking Horse Pass two separate controllers, forwards and backwards, are used.48 +Each station-2-station controller realizes the movement from one of the stations (IC,OC,KH) to a second station. All controllers using IC or OC parts have to respect the traveling directions. For the Kicking Horse Pass two separate controllers, forwards and backwards, are used. 49 49 50 -The controllers starting from Kicking Horse Pass Station make an assumption of the direction of the train. These are dependent o nthe directions of the inner or outer circle, e.g. the KHIC controller starts backwards because this is the only valid direction to travel this path. To drive a train from the Kicking Horse Station (facing forward) to the Inner Circle we have to combine the KHOC and OCIC controllers.50 +The controllers starting from Kicking Horse Pass Station make an assumption of the direction of the train. These are dependent of the directions of the inner or outer circle, e.g. the KHIC controller starts backwards because this is the only valid direction to travel this path. To drive a train from the Kicking Horse Station (facing forward) to the Inner Circle we have to combine the KHOC and OCIC controllers. 51 51 52 52 [[image:attach:ICIC.png]] 53 53 ... ... @@ -501,7 +501,7 @@ 501 501 502 502 {{{ final state reallyDone;}}} 503 503 )))|=((( 504 -~/~/ All permissions variables 504 +~/~/ All permissiions variables 505 505 506 506 ~/~/ All request variables 507 507 ... ... @@ -511,7 +511,7 @@ 511 511 512 512 ~/~/ Destination track number 513 513 514 -~/~/ Cleanup flag for selecting the destination track514 +~/~/ Cleanup flag for selecting the track of destination 515 515 516 516 ~/~/ Debug flag for additional output 517 517 ... ... @@ -527,7 +527,7 @@ 527 527 528 528 529 529 530 -~/~/ State, which set srequests for needed tracks530 +~/~/ State, which set requests for needed tracks 531 531 532 532 533 533 ... ... @@ -535,9 +535,9 @@ 535 535 536 536 537 537 538 -~/~/ Transition istaken,ifall permissionsare received538 +~/~/ Transition for received **all** needed permissions 539 539 540 -~/~/ Transition istaken,ifsome(notall)permissionsare received540 +~/~/ Tranisition for received **some** needed permissions 541 541 542 542 543 543 ... ... @@ -555,7 +555,7 @@ 555 555 556 556 557 557 558 -~/~/ Transition to r epeat requestingpermissions procedure558 +~/~/ Transition to trying the requesting again 559 559 560 560 561 561 ... ... @@ -584,7 +584,7 @@ 584 584 585 585 586 586 587 -~/~/ Transition to next track segment, if contact is triggered587 +~/~/ Transition to next track segment, if contact is readed 588 588 589 589 590 590 ... ... @@ -680,7 +680,7 @@ 680 680 681 681 ~/~/ Transitional state 682 682 683 -~/~/ Transition to next track segment, if contact is triggered683 +~/~/ Transition to next track segment, if contact is readed 684 684 685 685 686 686 ... ... @@ -748,6 +748,8 @@ 748 748 749 749 750 750 751 + 752 + 751 751 ~/~/ Setting the arrival track (output) 752 752 753 753 ... ... @@ -794,10 +794,6 @@ 794 794 795 795 796 796 797 - 798 - 799 - 800 - 801 801 ~/~/ Transitions for permitted tracks don't match wished tracks 802 802 803 803 ... ... @@ -808,8 +808,6 @@ 808 808 809 809 810 810 811 - 812 - 813 813 ~/~/ State for waiting an additional tick 814 814 815 815 ... ... @@ -838,7 +838,7 @@ 838 838 839 839 840 840 841 -~/~/ State for releasing not used track requests 837 +~/~/ State for releasing not used track requests and 842 842 843 843 844 844
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -94716 601 +9471652 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/94716 60/Basic design1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471652/Basic design