eeros_architecture:control_system:blocks
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
eeros_architecture:control_system:blocks [2017/03/17 17:13] – [Making Connections] graf | eeros_architecture:control_system:blocks [2022/04/19 12:36] (current) – [Predefined Blocks] ursgraf | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Inputs and Outputs ===== | ===== Inputs and Outputs ===== | ||
- | Every output carries a signal. An input can be connected to an output and simply refers to the signal of this connected output. | + | Every output carries a [[eeros_architecture: |
[{{ block.png? | [{{ block.png? | ||
This makes sure that each input is connected to a single output. On the other hand, an output can carry its signal to many inputs. | This makes sure that each input is connected to a single output. On the other hand, an output can carry its signal to many inputs. | ||
Line 17: | Line 17: | ||
sum.getIn(0).connect(step.getOut()); | sum.getIn(0).connect(step.getOut()); | ||
- | Gain<> | + | Gain<Vector2> posController(174.5); |
posController.setName(" | posController.setName(" | ||
</ | </ | ||
Line 25: | Line 25: | ||
Output signals are created together with the blocks. On the other side, there is no need to generate and name input signals. | Output signals are created together with the blocks. On the other side, there is no need to generate and name input signals. | ||
+ | For most blocks you have to specify the signal types on its inputs or outputs with template parameters, see [[tools: | ||
eeros_architecture/control_system/blocks.1489767196.txt.gz · Last modified: 2017/03/17 17:13 by graf