eeros_architecture:control_system:available_blocks:cansend
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
eeros_architecture:control_system:available_blocks:cansend [2024/05/27 16:31] – created ursgraf | eeros_architecture:control_system:available_blocks:cansend [2024/05/27 17:03] (current) – ursgraf | ||
---|---|---|---|
Line 7: | Line 7: | ||
The control system must incorporate a block for sending and another one for receiving CAN messages. | The control system must incorporate a block for sending and another one for receiving CAN messages. | ||
- | [{{ : | + | [{{ : |
- | The block for sending will periodically | + | The block for sending will periodically send a CAN message |
- | Each time the block is run by its time domain, | + | The position input expects |
<code cpp> | <code cpp> | ||
- | setCtrl(Matrix<nofNodes,1,uint16_t>); | + | void setScale(Matrix<N,1,double>& scale); |
</ | </ | ||
- | the velocity is taken from its input '' | + | This blocks uses the [[https://gitlab.ost.ch/ |
- | The velocity input expects a signal in SI units, e.g. rad/s. To account for encoder resolution of the actual drive together with a gearbox, it is possible to set a scaling factor with | + | |
- | <code cpp> | + | |
- | setVelScale(Matrix< | + | |
- | </ | + | |
- | This blocks uses the [[http://github.com/ntb-ch/ | + |
eeros_architecture/control_system/available_blocks/cansend.1716820272.txt.gz · Last modified: 2024/05/27 16:31 by ursgraf