Skip to content

Dobot Setup ​

SUMMARY

This guide walks through connecting a physical Dobot controller to your network and controlling it with Synapse over the Dobot V4 TCP/IP interface.

For supported models and specifications, see All Supported Manipulators.

Hardware Setup ​

Connect Ethernet cable from your PC to the Dobot controller ​

Configure your PC network on the same subnet as the controller ​

Read the robot's IP from Dobot's control software, then set a static IP on your PC in the same subnet, e.g. robot 192.168.5.1 → PC 192.168.5.2, subnet mask 255.255.255.0.

Verify connectivity with ping ​

bash
ping 192.168.5.1   # replace with your robot's IP

Put the controller in TCP/IP control mode ​

Synapse commands the robot over the Dobot V4 TCP/IP interface: the Dashboard port (29999) for commands and the real-time feedback port (30004) for state. Make sure the controller is in TCP/IP control mode in DobotStudio Pro, and close any other client that holds those two ports, such as DobotStudio Pro itself or a previous session. If connect fails, Synapse reports these as the first things to check.

Stuck on setup?
Ask on the Telekinesis Discord and we'll help you get connected.
Join Discord →

Control a Dobot with Synapse ​

python
from telekinesis.synapse.robots.manipulators import dobot

robot = dobot.DobotCR5(name="cr5")
robot.connect(ip="192.168.5.1")  # replace with your robot's IP

Synapse downloads the robot description from the Telekinesis asset server when the robot is created, like every other manipulator. No local preparation is needed.

Connecting powers the arm on

connect(ip=...) requests TCP control mode, powers on and enables the arm, and starts streaming state from the feedback port. Clear the workspace and keep an E-Stop within reach before you connect. On disconnect, Synapse restores the tool that was selected on the controller and disables the arm if this session enabled it.

What is supported ​

  • Moves: joint and Cartesian moves, with joint or pose targets, block until the controller reports completion. Pass asynchronous=True to return immediately.
  • Stopping and pausing: stop_joint_motion, stop_cartesian_motion, pause_motion and continue_motion.
  • Power and status: motor_on, motor_off, reset_controller (clears controller errors), is_emergency_stopped and get_status.
  • Live state: robot.state is fed from the controller's 8 ms feedback stream.
  • TCPs: the tool selected on the controller appears as the inactive controller_interface_tcp. Synapse's active TCP is written to a reserved, session-only controller tool slot, robot.tcp_tool_index (default 9). A TCP with a zero offset selects the flange (tool 0) instead.

Limitations ​

TopicBehavior
AccelerationThe Dobot V4 interface only accepts acceleration as a percentage of the controller's maximum, so Synapse's absolute acceleration argument is not used on hardware. Set robot.motion_acceleration_ratio (integer, 1 to 100, default 20) instead. See Robot Properties.
Joint-speed movesmax_joint_velocities is verified for the CR3, CR5, CR7, CR10, CR12, CR16, CR20, CR6AL, CR5AF, CR10AF and CR20AF. For the CR3AF, CR30H, ME6 and Nova models there is no verified specification, so joint-speed moves on their hardware raise NotImplementedError.
Safety cuboidThe controller cannot apply a cuboid over TCP/IP. Connecting to hardware with a safety cuboid configured raises RuntimeError. Configure safety walls or work zones in DobotStudio Pro instead.