User Tools

Site Tools


eeros_architecture:control_system:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
eeros_architecture:control_system:start [2017/03/15 15:16] grafeeros_architecture:control_system:start [2017/12/16 09:03] (current) graf
Line 1: Line 1:
 ====== Control System ====== ====== Control System ======
  
-The control system is constructed using three main parts: blocks, signals, and time domains. Blocks represent something that will alter a signal, or produce a new signal based on the input it receives. Signals are the raw information that flow withing the system, passing between blocks through the hierarchical flow. This flow is predetermined by the connections between blocks constructed beforehand. +The control system is constructed using three main parts: blocks, signals, and time domains. Blocks represent something that will alter a signal, or produce a new signal based on the input it receives. Signals are the raw information that flow within the system, passing between blocks through the hierarchical flow. This flow is predetermined by the connections between blocks constructed beforehand. 
-{{:eeros_architecture:control_system:controlloopwithtwotimedomains.png?200|ewee}}+[{{ :eeros_architecture:control_system:controlloopwithtwotimedomains.png?500 //Blocks, signals and time domains are the building blocks of the control system// }}]
  
 The robot controller, defined in EEROS as the control system, is the real-time core of the application. In order to guarantee the modular and exchangeable nature of the software system, it is built from predefined blocks, which can alter the signals flowing through the blocks. Nesting and ordering of these blocks creates very clear hierarchical structures. Blocks can be assigned to real- or non-real-time domains. Additionally, all signals in EEROS have a standard set of information, which increases the semantics of this information. The robot controller, defined in EEROS as the control system, is the real-time core of the application. In order to guarantee the modular and exchangeable nature of the software system, it is built from predefined blocks, which can alter the signals flowing through the blocks. Nesting and ordering of these blocks creates very clear hierarchical structures. Blocks can be assigned to real- or non-real-time domains. Additionally, all signals in EEROS have a standard set of information, which increases the semantics of this information.
Line 8: Line 8:
 For more information about individual parts of the control system, check out these pages: For more information about individual parts of the control system, check out these pages:
  
-  * [[.:blocks|Blocks]] +  * [[.:blocks]] 
-  * [[.:signals|Signals]] +  * [[.:subsystem]] 
-  * [[.:time_domains|Time Domains]] +  * [[.:signals]] 
-  * [[.:executor|Executor]]   +  * [[.:time_domains]] 
-  * [[.:available_blocks|Available Blocks]]+  * [[.:executor]]   
 +  * [[.:available_blocks]] 
 +  * [[.:custom_blocks]]
eeros_architecture/control_system/start.1489587408.txt.gz · Last modified: 2017/03/15 15:16 by graf