Plan Arduino wiring before choosing the layout
This Arduino and ESP32 pin planner assigns signal pins to a set of supported parts and checks selected board rules. Use it before laying out a small robotics project, connecting a classroom sensor demo, or moving an existing Arduino plan to the modeled ESP32 board. It starts with an LED, a push button, a potentiometer, and a servo so you can inspect a complete example immediately.
Choose among the modeled Arduino Uno, Arduino Nano, and ESP32 DevKit WROOM-32. Those names matter: another board with a similar product name may have different pins, peripherals, or electrical requirements. The planner does not discover connected hardware, upload firmware, or verify a physical circuit. Its output is a proposed signal assignment and starter code, supported by checks against its built-in board and part definitions.
How the assignment rule works
Pin assignment is a constrained matching problem rather than a voltage equation. Each part contributes jobs such as analog input, PWM output, digital input, or a bus connection. A candidate pin must support the requested job and be available. Manual selections are kept as overrides, then the remaining jobs are assigned around them.
The automatic allocator reserves active bus pins and places scarce jobs before more flexible ones. It prefers ordinary pins over choices with modeled side effects. This is a practical allocation rule, not a proof that every possible arrangement has been searched. If there is no suitable free pin, the plan reports a problem rather than inventing an extra connection.
The checker then reviews the resulting plan for incompatible capabilities, duplicate assignments, bus conflicts, and selected warnings. Errors and warnings have different meanings: a plan can have no errors while still containing a warning you need to read. Neither a clean status nor successful code generation proves that the complete circuit is electrically correct.
Worked example from the loaded plan
Running the loaded parts through the site's pin library with Arduino Uno selected produces this assignment:
| Part | Signal job | Assigned pin |
|---|---|---|
| LED | PWM-capable LED output | D3 |
| Push button | Input with pull-up | D2 |
| Potentiometer | Analog wiper input | A0 |
| Servo | Servo signal | D5 |
The library reports no issues for this assignment. Sketch setup declares the corresponding pin constants and configures the LED as OUTPUT and the button as INPUT_PULLUP. It leaves the main loop empty. The servo receives a named signal constant, but the generated sketch does not attach a Servo object, read the potentiometer, or implement motion behavior.
For a deliberate conflict, manually assign both the LED and push button to D3. The checker reports that D3 is used twice. Changing a menu does not silently discard the other manual choice; review the warning beside the pin, then select a distinct compatible input or reset to automatic pins. This makes the conflict visible while you are planning instead of hiding it behind an automatic reassignment.
Move the same project to ESP32
Switching boards keeps the parts and clears manual overrides. With Wi-Fi enabled, the same library-generated example assigns the LED to GPIO13, button to GPIO16, potentiometer to GPIO32, and servo signal to GPIO14. These are example assignments for the modeled board, not mandatory wiring choices for every ESP32 project.
The Wi-Fi option affects analog allocation because the model excludes ADC2 analog inputs while Wi-Fi is active. It also distinguishes input-only pins, pins without internal pull-ups, flash connections, serial connections, and boot-strapping warnings. Selecting a pin manually can expose these constraints in the table. The board definitions do not cover every ESP32 family or alternate module pinout.
The modeled Uno and Nano use 5 V logic, while the modeled ESP32 uses 3.3 V logic. A part's supply voltage does not by itself establish that its signal output is compatible. Read the part tips and any level-shifting warning, then confirm the actual module documentation. Do not use a pin assignment table as a substitute for a power-distribution plan.
Shared buses and library side effects
I²C devices share the modeled board's SDA and SCL connections, so adding another I²C part does not consume another private signal pair. The checker reminds you that devices need different addresses. It does not inspect or assign those addresses. SPI parts share clock and data lines while each receives a separate chip-select assignment.
On the modeled AVR boards, the checks also account for selected timer interactions from servo and buzzer use. That matters when an LED or motor driver needs PWM while another library owns a timer. The planner cannot infer the libraries or timer settings in an arbitrary sketch; it checks the behaviors associated with the parts you selected. Review additional firmware dependencies yourself.
Read the generated code before copying
Sketch setup contains pin constants, applicable pinMode calls, and bus startup when a selected part needs it. It is a starting structure, not a complete driver implementation. You still need the appropriate device libraries, initialization calls, control logic, and any required board-core setup. Copying code does not clear reported wiring problems, so resolve the plan before carrying its constants into your project.
Part tips cover connections that are not represented as table rows, such as a shared ground or an external servo supply. The table focuses on signal jobs and does not draw every power wire. Likewise, current checks use the library's modeled part loads; they do not measure module consumption or establish a complete electrical budget.
Check the circuit before soldering
A common mistake is choosing pins only by their physical position, then discovering that the selected signal needs an analog input or PWM capability. Another is treating an automatically allocated pin as approval for every attached module. Review each job, module voltage, power connection, and firmware requirement together.
Use the LED resistor calculator to size the LED's separate series resistor, and the voltage divider calculator for a separate divider calculation. Move the completed connection plan into the perfboard simulator, following how to plan a perfboard layout. Keep the pin table and your actual module pin labels consistent as you turn the plan into wiring.