Summary

• Page properties (2 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.als
	1	+XWiki.krat

Content

...	...	@@ -117,6 +117,8 @@
117	117
118	118	At the end of every Station-to-Station-Controller the trains should stand in one station, because every controller starts with the train in standstill.
119	119
	120	+Contact reading in triggers should only used when it is clearly determined which train will fire the contact.
	121	+
120	120	=== TrainController ===
121	121
122	122	Train-Schedules should be modelled by putting together the Station-to-Station-Controllers for every train in individual regions.
...	...	@@ -137,6 +137,14 @@
137	137	bool <track>_req[<trainAmount>] contains the requests for each track and train. Before the availability of arrays, we used bool <train>_<track>_req.
138	138	int <track>_perm contains the trainnumber of the train, who is allowed to drive on <track>.
139	139
	142	+== Deadlock Prevention ==
	143	+
	144	+An example controller for deadlock prevention is located in// rail-repo: docs/deadlocks/resolve_deadlock.sct//
	145	+
	146	+Sidings should only be used in one direction.
	147	+
	148	+Trains trying to leave a station in order to use KIO_LN_0 or KIO_LN_1 should, if they do not receive the locks for all segments, release them for two ticks.
	149	+
140	140	= C Controller =
141	141
142	142	The C controller wraps the basic railway interface and creates an correct environment to run the generated controller.

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-9471001
	1	+9471043

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471001/Documentation
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471043/Documentation