dobot
Introduction
Project-wide robot control interface and MG400 implementation
Responsibilities
Local and remote control
Manufacturer manuals
Software architecture
Common Control Interface and MG400 Implementation Contract
Operation semantics and limitations
Cartesian and joint representations
Remote invocation
MG400 Hardware, Connectivity, and Pre-operation Checks
Manufacturer references
Network connection
Safety before motion
Axes and coordinate conventions
Alarms and maintenance
Next steps
MG400 Commissioning and Operational Checks
Networking
Safety and enabling
Commissioning sequence
MG400 connectivity and safety prerequisites
Network
Before operation
Coordinates
Tutorials
Quick start
Local control
FastAPI server
Synchronous client
Asynchronous client
DeviceProxy
Operational workflow: from local control to HTTP clients
1. Before connecting
2. Local control
3. FastAPI server
4. Synchronous client
5. Asynchronous client
6. Motion completion semantics
7. Configuration
8. Further reading
Control behavior
Common Control Interface: Implementation Boundaries
Public and implementation layers
Motion parameters and actual support
Two meanings of synchronous and asynchronous
Relationship to manufacturer documentation
Commissioning checklist
Motion control
Source-verified details
Coordinates and axis count
Status, errors, and I/O
Working with the common control interface
Local status inspection
Motor control versus arm ownership
Expose the same interface through FastAPI
Server and client implementation
Control paths
Starting the server
Synchronous and asynchronous clients
Scope of verification
Configuration
Implementation scope and limitations
API reference
DobotCtrl public API inventory
Public control API: method signatures
Lifecycle
Motion
Control
Configuration
I/O
Errors
Other public methods
Public API return and failure semantics: quick reference
Distinct completion boundaries
Control API coverage and operational cautions
Public methods versus hardware support
Public method signatures extracted from source
CHANGELOG
v0.1.2 - 2026-09-09
Fixed
Refactored
Compatibility
v0.1.1 - 2026-09-09
Changes
Design policy
v0.1.0 - 2026-09-08
Common interface and implementation layers
Official DOBOT API and extended API
Basic control
Work / User coordinate systems
Motion control
Final correction of blocking / non-blocking behavior
Hardware verification as of v0.1.0
v0.0.0
2026-09-08 - Initial record
Separation of the common interface and MG400 implementation
Changed architecture to avoid direct modifications to vendor dobot_api.py
Implemented the three MG400 port connections
Standardized logging through a logger
Mapped motor ON/OFF to the MG400 API
Standardized common coordinates to six components
Implemented MG400 conversion in move()
Separated motion_mode from path_blend
Implemented motion-completion detection
Implemented current position and joint-angle retrieval
Implemented forward and inverse kinematics
Implemented Work coordinates using User coordinates
Implemented Tool coordinate-system selection
Implemented I/O
Implemented error retrieval and description display
Reorganized the FastAPI layer
Split test scripts by interface
Explicitly documented unimplemented interfaces
Main currently identified unimplemented or partially implemented features
Hardware verification on 2026-09-08
Python API
Python API Reference
dobot
dobot package
Subpackages
Submodules
dobot.config module
dobot.dobot_api module
dobot.dobot_api_ext module
dobot.dobot_ctrl module
dobot.dobot_error module
dobot.dobot_tcp module
dobot.robot_var_manager module
dobot.server module
dobot
Python API Reference
View page source
Python API Reference
dobot
dobot package