Skip to content

no response from motor rs03 #1

@aslamahrahman

Description

@aslamahrahman

first i ran with with MotorStudio from here v1.0.1
can id of motor set to 10, extended can frame format chosen, baud rate chosen to 1mbps

i recorded what the payload the MotorStudio is sending and receiving from the motor
TxHex: "41542007e8540800000000000000000d0a"
rxHex: "4154100057ec08a6d4808c7fff01400d0a"

but if i try to decode this payload as per your documentation here

then i am seeing that

The extended CAN ID used in the captured frames is 0x07E854 (i.e. bytes 07 E8 54).
When decoded according to the manual layout:
Bits 7–0 = 0x54 → Motor ID = 84
Bits 15–8 = 0xE8 → Host ID = 232
Bits 28–24 = 0x07 → Communication Type = 7

BUT per manual, Communication Type for “enable” should be 3, and for “disable” should be 4. Instead, GUI is sending 7

is the documentation wrong? why is the MotorStudio sending something different?

because of this i am not able to communicate with the motor outside of the MotorStudio

i have tried out this example also from your github, and motor is not responding to even a stop command

https://github.com/RobStride/robstride_ros_sample

i am talking to the motor from the linux machine using the usb-can adapter you provide, and then using slcand to setup an can0 interface

the commands send is showing up with candump can0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions