7.2.1 Environment and Communication Check
1. Check the Board Environment
Open the UNO Q Debian terminal and run:
uname -r
python3 --version
python3 -m pip --version
python3 -c "import importlib.metadata as m; print(m.version('pymycobot'))"
Confirm that the system returns kernel, Python, pip, and pymycobot versions. New boards may not have pip installed. If No module named pip is reported, install it first:
sudo apt update
sudo apt install -y python3-pip
python3 -m pip --version
The delivered system normally includes the UNO Q-compatible pymycobot version. If it is missing, obtain a package that matches the current system and project; do not overwrite it with an unrelated version.
2. Initialization
from pymycobot import MyCobot280
mc = MyCobot280(unoq_bridge=True)
- unoq_bridge=True is required.
- Do not provide serial device or baudrate parameters.
- The Bridge uses 1000000 internally; ordinary users do not need to change it.
3. Read-Only Communication Test
Run this before any motion command:
python3 -c "from pymycobot import MyCobot280; mc = MyCobot280(unoq_bridge=True); print('version:', mc.get_system_version()); print('angles:', mc.get_angles())"
A normal response includes the robot system version and six joint angles. For timeout or partial frames, stop other control programs, check robot power and D0/D1 wiring, then see Troubleshooting.
4. Run a Script
python3 your_demo.py
For a project-deployed example:
cd ~/mycobot/example
python3 control_rgb_demo.py
The actual path depends on the deployment location.