> For the complete documentation index, see [llms.txt](https://dahl-design.gitbook.io/ddc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dahl-design.gitbook.io/ddc/1.-project-planning/digital-outputs.md).
# Digital outputs
DDC supports setting up pins as digital output pins. "Digital" in this sense means they are either on or off (being connected to VCC or ground). Typically, output pins can only supply a low amount of current (up to 50 mA), and can only power tiny devices. The most relevant application would be analog LEDs, but in that regard you can also use PWM control. Here are some differences:
There are pros and cons of each method, and they have different applications. PWM requires only a single pin, but more external hardware like transistors and capacitors. A PWM controlled circuit is possible to dim up and down, and you can use any voltage you want. You can also power things like fans or a lightbulb, that require a fair bit of current. Using digital outputs however will give you controll over individual devices (such as LEDs), and you can use SimHub to make an LED profile and control them with telemetry.
If you need static backlight for a button box, use PWM. If you want to make revlights for a wheel or dashboard using analog LEDs, use digital outputs.
Lets say you have 20 LEDs in your project. That requires 20 output pins. You'll have no pins left for your switches at this point. You can add a [port expander ](/ddc/1.-project-planning/switch-inputs/port-expander.md)to your project, and use this either as an output device, or use it for your switches. Each port expander gives you 16 more pins for your project!
The [CB1 board](/ddc/cb1/code/settings.md) has its own settings for setting up outputs.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://dahl-design.gitbook.io/ddc/1.-project-planning/digital-outputs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.