python/examples).config.h and test_joint_control.py).When updating the sdk to your codebase, please first remove the entire build folder and run the building process again.
sudo requirement for building the library (all dependencies are managed under conda environment, thanks to Cheng Chi)python/arx5_interface.pyi)We set up a conda environment for all the cmake dependencies, so no system package is required. If you want to run cmake and make after modifying the C++ source files, please make sure you are under the created conda environment (arx-py310 etc.).
We recommend mamba for creating conda environments, which takes only about 1min. You can also use conda, but it takes significantly longer (~10min).
mamba env create -f conda_environments/py310_environment.yaml
# if you do not have mamba, you can also use conda, which takes significantly longer
# Currently available python versions: 3.8, 3.9, 3.10, 3.11
conda activate arx-py310
mkdir build && cd build
cmake ..
make -j
# At this point, you should be able to run test scripts below.# To install the C++ package your system, run:
make installUse a USB cable to power the EtherCAT-CAN adapter and an ethernet cable to connect it to your computer. After running ip a in your terminal, you should find the interface name, usually eth. (existing ethernet port) or en.......... (additional USB-Ethernet adapters).
Then you should enable the ethernet access of your Python interpreter (usually in your bin folder). Note that which python usually gives you a symbolic link (say ~/miniforge3/envs/arx-py310/bin/python) and doesn't work in this case. You need to find out the actual file (usually python3.x).
mamba activate arx-py310
ls -l $(which python)
sudo setcap "cap_net_admin,cap_net_raw=eip" your/path/to/conda/envs/arx-py310/bin/python3.10To run C++, you need to enable the executable every time after compiling. You also need to update the C++ scripts with the correct interface.
sudo setcap "cap_net_admin,cap_net_raw=eip" build/test_cartesian_controller
sudo setcap "cap_net_admin,cap_net_raw=eip" build/test_joint_controllerYou can skip this step if you have already set up the EtherCAT-CAN adapter.
sudo apt install can-utils
sudo apt install net-toolsThere are 2 popular firmware types of usb-can adapter, SLCAN and candleLight. After plugging the adapter, you can find out the correct firmware type by the following rules:
ls /dev/ttyACM*. If there is a new /dev/ttyACM* device (where * is a number), this adapter is using SLCAN firmwareip a. If there is a new can* interface (where * is a number), this adapter is using candleLight firmware.Get serial number by:
udevadm info -a -n /dev/ttyACM* | grep serial
# Replace the * by the actual number if there are multiple ttyACM devices connected to your computer.You will get something like:
ATTRS{serial}=="209738924D4D"
ATTRS{serial}=="0000:00:14.0"Then edit CAN rules file:
sudo vim /etc/udev/rules.d/arx_can.rulesCopy and paste the following, and replace the serial number with yours. If you are registering multiple adapters, you can use other SYMLINK names (e.g. arxcan1) and make sure the following commands are updated accordingly.
SUBSYSTEM=="tty", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="117e", ATTRS{serial}=="209738924D4D", SYMLINK+="arxcan0"Finally, activate CAN connection by: (the second line should be run every time after connection)
sudo udevadm control --reload-rules && sudo udevadm trigger
sudo slcand -o -f -s8 /dev/arxcan0 can0 && sudo ifconfig can0 upAfter plugging the adapter and running ip a, you should immediately find a can interface (usually can0). If you only have one arm, simply run
sudo ip link set up can0 type can bitrate 1000000and you are good to go. You should run it every time after connecting a usb-can adapter. If you have multiple arms and you want to fix the CAN interface name mapping for each arm, you need to register the adapter to the CAN rules:
sudo dmesg # Find the idVendor, idProduct and serial number of your adapter
sudo vim /etc/udev/rules.d/arx_can.rulesand then append the following line to your arx_can.rules. Make sure you've replaced the serial number of your adapter and your desired CAN name.
SUBSYSTEM=="net", ATTRS{idVendor}=="1d50", ATTRS{idProduct}=="606f", ATTRS{serial}=="0040001E3730511620323746", NAME="can0"Run the following line to update the changes
sudo udevadm control --reload-rules && sudo systemctl restart systemd-udevd && sudo udevadm triggerFinally, reconnect your adapter and run (This line should be run every time after plugging the usb-can adapter)
sudo ip link set up can0 type can bitrate 1000000All the configurations are tested using 3Dconnexion spacemouse. You can skip this step and use keyboard to test Cartesian control.
sudo apt install libspnav-dev spacenavd
sudo systemctl enable spacenavd.service
sudo systemctl start spacenavd.serviceArguments for test_joint_control.py, keyboard_teleop.py, spacemouse_teleop.py and teach_replay.py:
X5 (silver and black) or L5 (all black metal with blue or red LED light). Choosing the wrong model may lead to dangerous movements!can0, enx6c1ff70ac436 etc. (run ip a to check your interface name)-u: by default ../models/arx5.urdfcd python
python examples/test_joint_control.py X5 can0 # replace X5 with L5 for the other model
python examples/test_bimanual.py # For two X5 arms using can0 and can1, each arm will act the same as test_joint_control.py
python examples/keyboard_teleop.py X5 can0
python examples/spacemouse_teleop.py X5 can0
python examples/teach_replay.py X5 can0To use python sdk from other directories, please make sure ./python is in $PYTHONPATH and ./lib/x86_64 or ./lib/aarch64 (depend on your computer system) is in $LD_LIBRARY_PATH.
export PYTHONPATH=$PYTHONPATH:/path/to/your/arx5-sdk/python
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/path/to/your/arx5-sdk/lib/your_archAfter compiling the arx5_interface pybind dynamic library (usually python/arx5_interface.cpython-version-arch-linux-gnu.so), you can run it under other python environments (need to be the same python version as the one you built).