Difference between revisions of "CanServo/ID2/en"

From HITEC_HELP
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...")
 
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Register ID2 is a 4 byte value: registers 0x3E, 0x3C are called together.
ID2 is a 4 byte value: registers 0x3E, 0x3C are called together.
* 0x3C - High 2 byte
* 0x3C - High 2 byte
* 0x3E - Low 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.
According to the [[CanServo/MODE/CAN/en]] setting, specify the CAN ID or Node ID ( [[CanServo/ID/Node/en]] ) of the servo.
* 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 [[CanServo/MODE/CAN/en]] = CAN 2.0A, 2.0B.
 
 
Communication settings including this setting are applied at the time of servo reset.
When changing, SAVE and Servo Reset are required.

Latest revision as of 00:57, 24 September 2021

ID2 is a 4 byte value: registers 0x3E, 0x3C are called together.

  • 0x3C - High 2 byte
  • 0x3E - Low 2 byte

According to the CanServo/MODE/CAN/en setting, specify the CAN ID or Node ID ( CanServo/ID/Node/en ) of the servo.


Communication settings including this setting are applied at the time of servo reset. When changing, SAVE and Servo Reset are required.