Closed snozawa closed 10 years ago
This probably won't work for everyone as idVendor and manufacturer strings are hardcoded in this script. Although this might be good as an example of how it's done. It would probably also help to have a script that that extracts that information from the USB subsystem.
This probably won't work for everyone as idVendor and manufacturer strings are hardcoded in this script.
I misunderstood that a device which I use is manufactured by Robotis, so I hardcoded idVender and manufacturer. However, that device seems to be not a product from Robotis.
extracts that information from the USB subsystem. Although I think it would be better too, it will be complicated to distinguish dynamixel device from other devices. If I can write patch for this, I'll send pull request again.
I'll close this request. Thank you.
Hi, Arebgun,
I created new scripts to configure udev files. By using these scripts, we can generate /dev/dynamixel_motors instead of /dev/ttyUSB?. We just need to run rosrun dynamixel_motor create_udev_rules command.
Could you merge this change?