1. The three laws and the real ones

Isaac Asimov’s I, Robot made robotics famous through three laws that keep humans safe. A desktop in orbit needs different laws: do not break the attachment, do not collide with the visiting vehicle, and do not use more propellant than planned. The principles are the same: predictability before capability.

Entry 198 sketched the desktop’s software stack. This entry looks at the robotic hardware that the software controls.

2. The desktop arm

A desktop needs at least one robotic arm for attachment handling. It installs new payloads, removes old ones, connects cables and fluid lines, and positions tools for manufacturing or inspection. The arm does not need humanoid dexterity, but it needs reach, stiffness, and reliability.

A 2–3 meter arm with a force-torque sensor and interchangeable end effectors is a reasonable starting point. It can be augmented with a second smaller arm for fine manipulation.

3. End effectors and tools

The arm is only as useful as its end effectors. The desktop needs a tool library: grippers for standard attachment fixtures, connectors for power and data, cameras for inspection, drills and cutters for manufacturing, and simple probes for testing.

Tools should be stored on the desktop and swapped automatically or by a visiting vehicle.

4. The keeper tug

A keeper tug docked to or operating near the desktop extends the desktop’s reach. It can inspect and service other satellites, retrieve small objects, and move payloads between nodes. The tug is a robot that operates away from home base.

The desktop controls the tug through the same comms architecture used for ground links, with more autonomy because round-trip light delay is small in LEO.

5. Free-flying assistants

Smaller free-flying robots, like NASA’s Astrobee, can operate inside or near the desktop for inspection, inventory, and close-up work. They are less capable than the main arm but more flexible for tight spaces or tasks that require a different viewpoint.

6. Safety and collision avoidance

Robotics in orbit is unforgiving. A collision can damage the desktop, a payload, or a customer asset. Every robotic operation needs pre-planned trajectories, force limits, and abort conditions. Visual Servoing and force feedback help, but the final authority is usually a human operator approving the plan.

What this changes

  • The desktop’s robotics include a main arm, tool library, keeper tug, and possibly free-flying assistants.
  • The arm handles attachments and tools; the tug handles external operations.
  • Safety systems and human oversight are essential for all robotic operations.
  • The next entry marks two hundred ledger entries.