Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • components.png
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Documentation

Author

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

Content

...	...	@@ -8,6 +8,8 @@
8	8
9	9	[[image:attach:components.png]]
10	10
	11	+
	12	+
11	11	== SCCharts Contoroller ==
12	12
13	13	{{noformat}}
...	...	@@ -38,6 +38,12 @@
38	38	controller.h defaults.h controller.c
39	39	{{/noformat}}
40	40
	43	+The core controller component sets up a connection to the railway, maintains an environment for the synchronous tick-function and invokes the tick-function in a loop.
	44	+
	45	+Additionally some time tracking is performed to determine time consumption of the tick function and its environment.
	46	+
	47	+To increase the robustness of the system the controller checks internal permissions of the SCChart-Controller against detected trains on the railway.
	48	+
41	41	== State Monitor ==
42	42
43	43	{{noformat}}
...	...	@@ -44,6 +44,10 @@
44	44	statemonitor.h statemonitor.c
45	45	{{/noformat}}
46	46
	55	+The state monitor component allows a thread-safe communication between connected GUIs and the running controller. This communication is also tick-safe meaning that changes are only applied at tick-borders. In addition to that the communication is mutual excluded without blocking the controller thread and thus the controller remains a reactive system.
	56	+
	57	+Furthermore it allows the generation of the current state of the controller in JSON format.
	58	+
47	47	== GUI Server ==
48	48
49	49	{{noformat}}
...	...	@@ -50,6 +50,12 @@
50	50	guiserver.h guiserver.c
51	51	{{/noformat}}
52	52
	65	+The GUI server allows multiple GUI clients concurrently connecting to the controller. The number of available slots is defined in the guiserver header.
	66	+
	67	+The communication is established via TCP and the message format is JSON. Each client can request the current status of the controller and interact with some commands changing most of the important properties of each train, especially the schedule. The detailed communication format and capabilities are documented in the [[doc:TCP Communication]] section.
	68	+
	69	+Most controls are performed delayed and thread-safe with the state monitor, some are directly performed via the hostcode component. Changes of the same property from different clients is processed with first-come-first-serve-principle which may cause lost update writes but will not affect the integrity of the controller.
	70	+
53	53	= Interaction =
54	54
55	55	== GUI ==

components.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.XWikiGuest

Size

...	...	@@ -1,0 +1,1 @@
	1	+124.5 KB

Content

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-9471717
	1	+9471698

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471717/C Controller
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471698/C Controller