Open blakelyc opened 6 years ago
Dear Sir, I have got the same problem as you Sir. I don't know how to fix it, please help. Thank you
Have you guys found any solution for this issue?
The XM430-350R wasn't produced when I developed the driver. It's not on the supported motors list, so it doesn't currently work. If it has the same API as other motors, you should be able to add the model number to the list to make it work.
On Sat, Aug 24, 2019 at 1:52 PM ycho80 notifications@github.com wrote:
Have you guys found any solution for this issue?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/arebgun/dynamixel_motor/issues/86?email_source=notifications&email_token=AALPNU46P6KZUOGAZUSDKCLQGF7PTA5CNFSM4FUBYYJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CFSJQ#issuecomment-524572966, or mute the thread https://github.com/notifications/unsubscribe-auth/AALPNUZMPUWBDCLL6DBQBVTQGF7PTANCNFSM4FUBYYJA .
I have 8 XM430-350R motors connected through a U2D2 module. I am able to access each motor using the Dynamixel Workbench Single Manager. Verified that there are no baud or id conflicts.