# 1. Double Sided PCB Workflow

For the Punk Console tutorial, we will be creating a double sided PCB using the V-One Drill attachment.

For a high-level overview of the generic process, see the [Double Sided PCB Workflow](/docs/v-one/learn-v-one/drill-attachment/double-sided-pcb-workflow.md).

<figure><img src="/files/gKULGjd3i9LI7A7I5wZH" alt=""><figcaption></figcaption></figure>

There are a couple of ways of creating a double sided board, today we'll follow this sequence:

#### 1. Drill the holes.

To start, a blank board will be mounted on the heated bed with the sacrificial layer. Then we will drill two types of holes: small holes for vias, and large ones for through hole components.

#### 2. Print the top layer

After drilling, the top layer will be printed. This procedure is the same as creating a single layer board, however the board will contain drill holes.

In this step, it is important to carefully clean all of the drilling debris off of the board.

#### 3. Print the bottom layer

Once the top side finishes baking, it is time to print the bottom side by doing an aligned print. Here, we'll use two of the holes we drilled to align the circuit and get the layers to line up.

#### 4. Add rivets

Now that both layers are printed, we will connect the top and bottom layers using rivets.

#### 5. Dispense solder paste

Next we will dispense solder paste onto our board to make soldering surface mount components a breeze.

#### 6. Assemble the board

Finally, we need to populate and reflow all of the surface mount components and hand solder the through-hole components to the board.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.voltera.io/docs/v-one/learn-v-one/v-one-projects/punk-console-project/1.-double-sided-pcb-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.