# Wiring Guide

## ※**Wiring WS2812/SK6812 Compatible (Neopixel) LEDs**

**Power Requirements**

* Neopixel LEDs need one digital IO pin and a power supply.
* They typically operate at **5V** but can also function with a **3V** source.
* Always verify the manufacturer's specifications for compatibility with your board.

**Pin Configuration**\
Each Neopixel has four pins:

* **VCC**: Power supply
* **GND**: Ground
* **Din**: Data input
* **Dout**: Data output

Neopixel strips generally come with three solder pads or a connector with three pins, marked with arrows to indicate data flow direction.\
**Note**: The Din pin is unidirectional and cannot be reversed.

**Wiring Instructions**

1. Connect the Din (D→) pin to an available digital IO pin on the MCU board.
2. Connect the VCC pin to a compatible voltage supply.
   * Neopixels typically draw **60mA** of current per LED at full brightness. If your printer board's power capabilities are limited, consider using a separate power source.
3. Run a GND wire from the Neopixel strip back to the MCU board, along with a GND connection to the power source for proper communication.

**Limitations**

* The number of Neopixels per IO pin is limited.
* You can connect two strips to the same data pin to display the same colors.
* Alternatively, configure multiple LED chains on different IO pins in the LED Effects settings.

***

## **Wiring APA102 Compatible (Dotstar) LEDs**

APA102 Dotstar LEDs are similar to Neopixel LEDs but utilize one-way **SPI** for communication. This requires the addition of a **clock signal** for the emitters, allowing multiple strips to share the same clock pin while each needing its own data line.


---

# 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.siboor.com/other-products/led-effect-notes/wiring-guide.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.