> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/manufacturing/cam/cnc-program-numbers.md).

# CNC program numbers

{% hint style="info" %}
Copied from the [RAIDParts guide](https://docs.raidrobotics.org/raidparts/reference/cnc-program-numbers) and kept in sync automatically. Edit it in the RaidParts repo (`docs/`), not here.
{% endhint %}

Our CNC router only accepts program names up to 8 characters, so a CAM program is named from a short form of the part number. Set it at the **CAM** step, before the program goes to the **CNC Router**.

{% hint style="danger" %}
A program name longer than 8 characters can't be loaded on the router, and the part can't be cut.
{% endhint %}

## How a program number is built

`##A@@-SR`

| Characters | Example | Meaning                                                                                                                            |
| ---------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| 1–5        | `01101` | The [part number](https://docs.raidrobotics.org/raidparts/reference/part-numbers) without the year and dash (`26-01101` → `01101`) |
| 6          | `-`     | Always a dash                                                                                                                      |
| 7          | `1`     | Setup number: 1 for the first face or fixturing, 2 for the next                                                                    |
| 8          | `A`     | Revision of this program: `A` first, then `B`, `C`                                                                                 |

Most parts need one setup. A tube can need up to four if more than one side is machined.

## Examples

| Part                                 | Part number | Programs               | Why                                                       |
| ------------------------------------ | ----------- | ---------------------- | --------------------------------------------------------- |
| Belly pan, flat sheet                | `26-01102`  | `01102-1A`             | One setup, first revision                                 |
| Elevator tube, machined on two faces | `26-05203`  | `05203-1C`, `05203-2A` | Setup 1 is on its third revision; setup 2 is on its first |

When you change a program, move to the next letter. Don't reuse an old letter.

## Set the number in Fusion

Fusion exports the program under the name set on the setup, so set it once and every export is named correctly.

**New setup**

1. While creating the setup, open the **Post Process** tab.
2. Enter the program number in **Program Name/Number**.

![The Post Process tab with Program Name/Number set to 01101-1A](https://1562593674-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDzjyXcQsEe3JO5qxyNOA%2Fuploads%2Fgit-blob-3c7d4ed3767434d1746159178f7d84483791149c%2Ffusion-post-process-tab.png?alt=media)

**Existing setup**

1. Right-click the setup to open its Setup dialog.
2. Open the **Post Process** tab and change **Program Name/Number**.

The setup then shows the program number in the browser tree.

![A setup named 01101-1A under Setups in the CAM browser](https://1562593674-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDzjyXcQsEe3JO5qxyNOA%2Fuploads%2Fgit-blob-051d170e0d1e9992c48e06d630f476ff525a1033%2Ffusion-setup-program-number.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/manufacturing/cam/cnc-program-numbers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
