Migrating rosbridge Clients
MoveIt Pro does not provide a rosbridge JSON endpoint. Port 3201 serves the
Foxglove WebSocket protocol used by the MoveIt Pro web UI; pointing a rosbridge
client at that port can appear to connect while subscriptions and service calls
fail because the wire protocols are different.
Choose the replacement that matches where your client runs:
| Existing client | Supported replacement |
|---|---|
| Python or C++ process on the robot network | Use the native ROS 2 client library API with rclpy or rclcpp. |
| JavaScript inside a MoveIt Pro Custom View Pane | Use IframeROSClient, which routes through the parent UI. |
| Standalone JavaScript application | Use the Foxglove WebSocket protocol with a Foxglove-compatible client, or place a native ROS 2 service on the robot network behind your application API. |
roslibpy, rossharp, roslibrust, or jrosbridge application | Migrate the application to a native ROS 2 library where available, or add an application-owned gateway outside MoveIt Pro. |
For Objective actions, services, and parameter overrides, start with the
Programmatic SDKs Overview. The ROS action, service,
topic, and parameter definitions remain available in
moveit_studio_sdk_msgs.