Additional verification: implementation and manufacturer documentation

This review is based on the supplied dobot_ctrl(3).py and dobot_tcp(2).py files and the Japanese manufacturer manuals. No physical robot tests have been performed. DobotStudio Pro controls are not the Python API.

Reassessment of six reported signature differences

Item	DobotCtrl line	DobotTcp line	Assessment
coord_type	168	935	Property setter, not an ordinary method; earlier method comparison was misleading
get_digital_input	496	1751	Parameter name only; forwarded positionally
get_version	39	1851	Backend optional, wrapper required
set_extaccel	372	1109	Parameter name only; forwarded positionally
set_extdecel	382	1115	Parameter name only; forwarded positionally
wait_for_complete	90	653	Wrapper has no arguments; backend timeout/interval are not applied to Sync()

Operational and safety boundaries

• halt() and stop() are unsupported backend operations and raise NotImplementedError; they are not emergency-stop functions (dobot_tcp(2).py, lines 493–509).

• wait_for_complete() invokes Sync(). Backend timeout and interval are not used, and the public DobotCtrl wrapper does not expose them (dobot_tcp(2).py, lines 653–678). Do not describe this as a timeout-controlled wait.

• The DobotStudio Pro User Manual (revision 2023-06-25, software 2.7.1), printed pp. 9–10, gives default LAN1 and LAN2 IP addresses 192.168.1.6 and 192.168.2.6; these are configurable.

• The same manual, printed pp. 16–17, explains the enable state and warns about incorrect payload configuration.

• The MG400 Maintenance Manual V1.2 (2026-04-23), printed pp. 2–4, requires safety-function checks and risk assessment and prohibits connecting safety devices to ordinary I/O.

• The maintenance manual, printed pp. 6–8, lists periodic inspections that this Python package does not replace.

Note: Manufacturer page numbers refer to printed manual pages, excluding front matter. Source line numbers refer to the supplied Python files.