-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
other #2
Comments
xwcwe |
|
|
|
|
w/ unicode
├
|
|
The CAN protocol used for Motion ControlThe CAN protocol used for Motion Control uses two classes of the iCub CAN protocol: the In here we describe the format of the messages used by the We start with explaining the generic structure of the iCub CAN frame and then we focus on the used messages. [TOC] Generic Structure of the iCub CAN frameThe structure of the generic iCub CAN frame is the following.
Figure. The CAN frame is formed by an The
|
Value of CLS |
Description | Third field of ID |
---|---|---|
0b000 | Motor Control Command | DST |
0b001 | Motor Control Streaming | TYP |
0b010 | Analog Sensors Command | DST |
0b100 | Skin Sensor Streaming | TYP |
0b101 | Inertial Sensor Streaming | TYP |
0b110 | For Future Use | TYP |
0b111 | Management / Bootloader | DST |
Table. The possible values for CLS
.
The values of ID.TYP depend on the class CLS. We shall show these values later.
The PAYLOAD
The PAYLOAD can have two formats depending if the class CLS
has a DST
or a TYP
.
PAYLOAD:
+---+---+---+---+---+---+---+---+---+---+---+ - - - - +---+
| CMD | ARG |
+---+---+---+---+---+---+---+---+---+---+---+ - - - - +---+
1 byte 0 / 7 bytes
Figure. Format of thePAYLOAD
for the case of ID w/ a DST
field. This is the case of a command message which has a command field CMD
plus possible arguments inside ARG
. There is a different CMD
for each class CLS
.
PAYLOAD:
+---+---+---+---+---+---+---+---+---+---+---+ - - - - +---+
| DATA |
+---+---+---+---+---+---+---+---+---+---+---+ - - - - +---+
1 / 8 bytes
Figure. Format of thePAYLOAD
for the case of ID w/ a TYP
field. This is the case of a streaming message which uses the full PAYLOAD
to carry DATA
of the type and formatting specified by the pair {ID.CLS
, ID.TYP
}.
Motor Control messages used for the amcbldc
board
They are a subset of the complete set of messages. Here they are.
Messages in the Motor Control Command class MCC
In this class the PAYLOAD.CMD
field reserves one bit to specify if the command is about motor 0 or motor 1. The other 7 bits specify up to 128 possible commands specified by an operational code.
PAYLOAD.CMD for Motor Control Command Class:
1 bit
|
+---+---+---+---+---+---+---+---+
| M | OPC |
+---+---+---+---+---+---+---+---+
|
7 bits
Figure. The PAYLOAD.CMD
byte contains CMD.M
which specifies to which motor to apply the operational code CMD.OPC
.
The bytes inside PAYLOAD.ARG
depend on the values of each operational code.
The Operational Code MCC::SET_CONTROL_MODE
.
The length of the PAYLOAD.ARG
= 1 (L
= 2).
PAYLOAD.ARG for MCC::SET_CONTROL_MODE:
+---+---+---+---+---+---+---+---+
| MODE |
+---+---+---+---+---+---+---+---+
1 byte
Figure. The PAYLOAD.ARG
of MCC::SET_CONTROL_MODE
contains only 1 byte with the desired control mode.
Value of MODE |
Tag | Description |
---|---|---|
0x00 | Idle | |
0x50 | OpenLoop | |
0x0A | SpeedVoltage | |
0x06 | Current |
Table. The possible values for MODE
.
this is just renamed. remove
.renamed.zip
and use it for the mc4plusmc4plus.hex.renamed.zip
The text was updated successfully, but these errors were encountered: