> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/physics-constraints/power-nets.md).

# Power Nets

Explanation of Quilter’s Power Net constraint, including automatic detection criteria, recommended naming conventions, default current values, and IPC-based validation methods.

This constraint aims to establish the minimum trace widths needed to prevent excessive resistive heating on traces carrying high currents, and to allow the user to specify which nets should have power pours.

### Automatic Detection

Nets with certain attributes will be automatically classified as high current nets. This will include:

* Any net that matches our various patterns for being a voltage or power net.
* Any net in a "Power" netclass.

### Recommended Patterns

You can force Quilter to detect a power net by placing it in a "Power" net class. This is particularly helpful for nets that do not have a voltage-pattern name (like 3V3) but do need to carry a significant amount of current, such as a net that powers a motor.

### Defaults

We assign conservative default values to every automatically detected net, assuming they are unlikely to carry high current. If a net is expected to encounter a substantial amount of current, you should specify the maximum in the interface.

Nets with detected voltages under 3V are assigned a 200mA maximum current by default, and nets over 3V receive a maximum of 500mA.

### Constraint details

<figure><img src="https://1761213452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL9R6Vsa5jGn27oTws0tG%2Fuploads%2FszPe4EjJAzrQK8raglDe%2Fimage.png?alt=media&amp;token=9653c9d1-6710-4d14-a06f-daefd2b031fd" alt=""><figcaption></figcaption></figure>

Power nets can be set up in the "Power Nets" section of Circuit Comprehension. You can add them one by one, match them with regex, or use a netclass.&#x20;

To define a power net constraint, you'll need to fill in the following fields:

1. Net name
2. Maximum current (mA)
3. Optionally choose if you want that net to be a power pour

{% hint style="info" %}
**Attempt Power Pour** is off by default. Turn it on only for nets that need a pour; pours can increase run time.
{% endhint %}

Quilter automatically completes IPC calculations that consider the specified copper weight and layer thickness for each stack-up to determine the ideal trace width for the net to prevent overheating.

### Physics Rule Checks

The PRCs that validate this constraint after compilation are:

**Overheated Length** determines the approximate analytic temperature rise of trace segments on a specified high current nets. A net segment is considered “overheated” if its approximated temperature rise exceeds 20C.

### Voltage drop simulation (Beta)

Requires power pours. Optionally set a source component and pin for each net. Leave both blank and Quilter calculates resistance using the worst pin pair and picks the worst-case scenario for voltage drop.&#x20;

<figure><img src="https://1761213452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL9R6Vsa5jGn27oTws0tG%2Fuploads%2F8FAfaOkcZxQAOZ3fT5OG%2Fimage.png?alt=media&amp;token=f8ba8ba5-1183-4ef1-8bed-04279c14bc3b" alt=""><figcaption></figcaption></figure>


---

# 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.quilter.ai/physics-constraints/power-nets.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.
