The map is useful. The drawing is the answer.
How to use the public robot-family map without treating it as a released configuration.
A model map is a starting line, not a release
The public map connects a robot family to one or more reference architectures. It contains 10 robot brands, 40 base model families and 84 reference configurations, each tagged with a series, diameter and process context.
That is enough to make the first conversation specific. It is not enough to release a bracket. The exact robot variant, controller, tool, tool-change cycle, cable bundle, fixture and service access can change the answer.
Use the map to ask: which series has appeared on this family, which process does the record reflect, and which drawing inputs are still missing? Then send the exact code and motion so an engineer can close those gaps.
The short version.
- Use the family to narrow the series.
- Check the exact variant and wrist.
- Measure the assembled bundle.
- Treat every result as reference-only.
Before this becomes a project.
Is the map a catalogue of released kits?
No. It is a public reference layer showing series, diameter and process combinations. A released drawing and BOM remain project-specific.
Why can two models with the same payload differ?
Wrist shape, J3/J4 fixing points, controller and tool can change the available route even when the payload figure looks similar.
Keep asking questions.
Bring the robot, the tool and the motion.
We will turn the note into the questions that actually block your drawing.