Difference between revisions of "CanServo/ID2/en"
Jump to navigation
Jump to search
(Created page with "Register ID2 is a 4 byte value: registers 0x3E, 0x3C are called together. * 0x3C - High 2 byte * 0x3E - Low 2 byte In CAN 2.0A, 2.0B status, CAN ID of servo is designated, an...") |
|||
| Line 5: | Line 5: | ||
In CAN 2.0A, 2.0B status, CAN ID of servo is designated, and in UAVCAN status, [[CanServo/ID/Node/en]] is designated. | In CAN 2.0A, 2.0B status, CAN ID of servo is designated, and in UAVCAN status, [[CanServo/ID/Node/en]] is designated. | ||
* Refer to [[CanServo/Packet Accept Rule/en]] for the packet reception procedure in CAN 2.0A, 2.0B. | * Refer to [[CanServo/Packet Accept Rule/en]] for the packet reception procedure in CAN 2.0A, 2.0B. | ||
The setting values related to communication setting including this setting are applied at the time of servo reset. | |||
Therefore, after changing, SAVE and Servo Reset must be performed for actual application. | |||
Revision as of 17:25, 23 September 2021
Register ID2 is a 4 byte value: registers 0x3E, 0x3C are called together.
- 0x3C - High 2 byte
- 0x3E - Low 2 byte
In CAN 2.0A, 2.0B status, CAN ID of servo is designated, and in UAVCAN status, CanServo/ID/Node/en is designated.
- Refer to CanServo/Packet Accept Rule/en for the packet reception procedure in CAN 2.0A, 2.0B.
The setting values related to communication setting including this setting are applied at the time of servo reset.
Therefore, after changing, SAVE and Servo Reset must be performed for actual application.