add_angle_mate
Fix an angular offset between two planar or axis entities. Use for hinge angles, lever positions, and rotated subassembly configurations.
Instructions
Mate de ángulo — fuerza un ángulo fijo entre dos entidades.
Uso típico autopartes: articulaciones de eslabón (cadena, bisagra), posiciones angulares de palancas y brazos, configuraciones rotadas de subconjuntos. Las dos entidades deben ser PLANARES (caras planas o planos de referencia) o EJES — no se puede aplicar un mate de ángulo entre dos caras cilíndricas concéntricas. [en: Add an angle mate (fixed angular offset) between two entities. Typical use: chain-link articulation, hinge angles, lever/arm rotational positions, rotated subassembly configs. Both entities must be PLANAR (planar faces or reference planes) or AXES — angle mates cannot be applied between two concentric cylindrical faces.]
Args: angle_deg: The fixed angle to enforce, in degrees. Positive rotates per SW's right-hand-rule about the inferred axis. Other args: same as add_concentric_mate.
Returns the created mate's metadata (including angle_deg).
Gotcha: if both selected entities are coplanar, SW's solver may reject the mate (over-defined). Choose entities that share a rotation axis but aren't already parallel at angle 0°.
Related: add_mate_by_face_position (no-entity-name convenience for coincident/distance only — angle mates still need entity strings).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"component1_name": "<component1_name>",
"entity1_id": "<entity1_id>",
"component2_name": "<component2_name>",
"entity2_id": "<entity2_id>",
"angle_deg": "<angle_deg>"
},
"name": "add_angle_mate"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| align | No | ALIGNED | |
| angle_deg | Yes | ||
| entity1_id | Yes | ||
| entity2_id | Yes | ||
| component1_name | Yes | ||
| component2_name | Yes |