Change OpenCR device and permissions to group dialout

[LucidOne]

Given modern security issues, it seems like making /dev/ttyACM0 world writable might not be the best choice, perhaps assigning it to group dialout would be better.

In addition to the updated udev rule, this does require that the user is added to the group

$ sudo usermod -a -G dialout $USER

Unfortunately this does not update the current shell so the user needs to log out and back in or run the following command.

exec sg dialout newgrp `id -gn`

Given that many robots have several serial ports, symlinking /dev/ttyACM0 to /dev/opencr0 for matching USB VID/PID seems helpful.

We are happy to help update the documentation if this can be merged.

[OpusK]

Hi, @LucidOne

With regard to dialout, we want to check compatibility issues.
And, since it uses ST VID / PID now, there is a problem.

In this regard, I will discuss the matter further internally and decide whether to merge PR.

[LucidOne]

'On Debian and derivatives including Ubuntu this is "dialout"; on Gentoo/Fedora/openSuse it is "uucp".'

Please let me know if you have any questions as I am currently working on some OEM integration tools for OpenCR and would really like to see something like this merged. Particularly symlinking /dev/ttyACM0 to /dev/opencr0 or something like /dev/dmxl0 to make it easier to figure out which serial port on a robot is connected to the dynamixels.

Is Robotis moving to it's own VID/PID?
Is the DFU VID/PID going to stay the same?

[OpusK]

Is Robotis moving to it's own VID/PID?

It seems to be difficult due to driver support issue under WIN7. (There is also a problem with the boot loader change.)

Is the DFU VID/PID going to stay the same?

DFU remains the same.

[LucidOne]

@OpusK did you have a chance to look at https://git.sr.ht/~lucidone/dmxl
Thanks!