CAIBI project benchmark: OpenMANIPULATOR-X
Prompt version 1.0

Help me build OpenMANIPULATOR-X using the existing creator project at https://github.com/ROBOTIS-GIT/open_manipulator. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- A current open four-axis robot arm and gripper platform built from DYNAMIXEL servos, modular frames and printable parts, with supported ROS 2, MoveIt 2 and OpenCR routes.
- Build context: Five XM430-W350-T DYNAMIXEL actuators, including the gripper actuator; ROBOTIS link frames, rail brackets, gripper parts, rods, bushes and servo frames; DYNAMIXEL daisy-chain cables and the published screw, nut, spacer, idler and bearing hardware; Suitable 12 V power supply; U2D2 plus power hub or OpenCR communication/control route for supported operation; Rigid base plate or equivalent secure mounting solution; Computer running a supported ROS 2 environment for the ROS route; Optional printable parts and custom end effectors from the open hardware ecosystem.
- Where AI helps: ROS 2 and MoveIt setup help, Package and launch-file troubleshooting, Kinematics and motion-planning code, Python and automation integration, CAD and end-effector modification guidance.
- Physical work: Configure each DYNAMIXEL correctly, Assemble and align the joints, Route and secure cables, Mount the arm rigidly, Set safe starting poses, Test real motion and payloads carefully.
- Main limitation: The current kit is expensive for a hobby arm and it is not complete by headline price alone. A base plate is not included, and ROS operation needs a suitable communication/control route and power supply. Servo IDs, horn alignment, cable routing and joint pose all matter before software can safely take over.

Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so.

Provide one practical build package:
1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications.
2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed.
3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability.
4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting.
5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions.
6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations.

Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why.

Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.