Appendix B - Controller Hardware Comparison - Revision history

ErnieHorning at 12:15, 18 July 2026

2026-07-18T12:15:28Z

ErnieHorning at 11:42, 18 July 2026

2026-07-18T11:42:09Z

ErnieHorning at 22:42, 17 July 2026

2026-07-17T22:42:52Z

ErnieHorning: Created page with "'''Appendix B – Controller Hardware Comparison''' '''Version:''' 0.5 (Draft) '''Written for:''' ESPPixelStick Version 4.x '''Last Updated:''' July 2026 '''Author:''' Ern..."

2026-07-17T22:34:12Z

Created page with "'''Appendix B – Controller Hardware Comparison''' '''Version:''' 0.5 (Draft) '''Written for:''' ESPPixelStick Version 4.x '''Last Updated:''' July 2026 '''Author:''' Ern..."

New page

'''Appendix B – Controller Hardware Comparison'''

'''Version:''' 0.5 (Draft)

'''Written for:''' ESPPixelStick Version 4.x

'''Last Updated:''' July 2026

'''Author:''' Ernest Horning

'''Research & Technical Editing:''' ChatGPT

'''Appendix Summary'''

'''Purpose'''

This appendix compares common microcontroller and controller-board categories that may be used with ESPPixelStick firmware.

It is intended to help readers select hardware appropriate for:

* Single-output pixel props
* Multi-output controllers
* Serial lighting interfaces
* Ethernet installations
* Stand-alone playback
* Experimental or custom hardware

This appendix does not replace the hardware-specific documentation for any controller.

'''Related Chapters'''

* Chapter 2 – ESPPixelStick Overview
* Chapter 3 – Supported Hardware
* Chapter 4 – Hardware Installation
* Chapter 5 – Firmware Installation
* Chapter 7 – Inputs, Outputs, and Interfaces
* Appendix A – GPIO Reference Tables

'''B.1 Introduction'''

ESPixelStick firmware can operate on more than one type of Espressif microcontroller.

The official project describes the firmware as supporting the ESP8266 and ESP32 platforms. However, those platform names include many individual modules and development boards. Two boards using the same processor may differ substantially in:

* Available GPIO pins
* Flash capacity
* USB interface
* Voltage regulation
* Ethernet support
* PSRAM
* SD-card support
* Connector arrangement
* Pins reserved by onboard hardware

For this reason, processor compatibility does not automatically guarantee complete board compatibility.

[[File:vertopal_635af067709144fabe2de355e6a715d4/media/image1.png|624x374px]]'''Figure B-1-1 – Hardware Selection Process'''

'''Engineering Note'''

Select hardware according to the required application rather than simply choosing the board with the largest processor or the greatest number of pins.

A simple prop may operate more reliably with a small, well-understood controller than with a more complex experimental board.

'''B.2 Hardware Categories'''

For the purposes of this appendix, hardware is divided into the following categories:

# ESPixelStick production hardware
# Generic ESP8266 boards
# Conventional ESP32 boards
# Specialized ESP32 controller boards
# Ethernet-capable hardware
# Newer or experimental ESP32-family devices
# Custom-designed controllers

'''B.3 ESPixelStick Production Hardware'''

The original ESPPixelStick hardware was designed specifically for pixel and serial-lighting applications.

A production ESPPixelStick board generally provides:

* ESP8266 processor
* Pixel data output
* RS-485 hardware for DMX or similar serial interfaces
* Power input suitable for common pixel voltages
* Compact inline construction
* Hardware designed around the firmware

The ESPixelStick V3 product documentation describes it as an ESP8266-based, single-output Wi-Fi pixel and DMX controller. It supports E1.31 and DDP and includes an RS-485 transceiver for differential serial output.

'''Advantages'''

* Purpose-built hardware
* Compact size
* Known electrical design
* Built-in output-conditioning circuitry
* Convenient for individual props
* Less custom wiring than a development board

'''Limitations'''

* Fewer available GPIO pins
* Primarily intended for one principal pixel or serial output
* Less suitable for large multi-output controllers
* Older ESP8266 processing platform
* Availability may vary

'''Best Suited For'''

* Individual yard props
* Small pixel strings
* DMX or Renard output
* Distributed Wi-Fi controllers
* Users who prefer ready-made hardware

'''B.4 Generic ESP8266 Boards'''

Generic ESP8266 boards include:

* ESP-01
* D1 Mini
* NodeMCU
* Other ESP8266 development boards

The ESP8266 is the original platform associated with ESPPixelStick and remains useful for small, distributed controllers.

'''Advantages'''

* Low cost
* Small size
* Widely available
* Low power consumption
* Sufficient performance for many single-output props
* Extensive community experience

'''Limitations'''

* Limited RAM
* Limited number of practical GPIO pins
* Usually Wi-Fi only
* Some pins affect boot behavior
* Most boards require external pixel-output circuitry
* Not ideal for large numbers of outputs

'''ESP-01'''

The ESP-01 is extremely compact but exposes very few GPIO pins.

It is best suited for:

* Single-output designs
* Existing ESPPixelStick-style hardware
* Very small custom controllers

Its limited pin count makes it poorly suited for multi-output or heavily expanded systems.

'''D1 Mini'''

The D1 Mini is a convenient general-purpose ESP8266 development board.

Typical advantages include:

* Integrated USB interface
* Onboard voltage regulation
* Small physical size
* More accessible GPIO than the ESP-01
* Inexpensive replacement boards

The D1 Mini is commonly used in custom pixel controllers, although external protection or level-shifting circuitry may be desirable.

'''NodeMCU'''

NodeMCU boards are physically larger than D1 Mini boards but provide similar ESP8266 functionality.

They may be useful for:

* Breadboard development
* Prototyping
* Applications where physical size is not critical

'''B.5 Conventional ESP32 Boards'''

The original ESP32 family provides more processing power, RAM, and GPIO capability than the ESP8266.

Common forms include:

* ESP32 DevKit
* ESP32-WROOM development boards
* LOLIN D32-series boards
* Other conventional dual-core ESP32 boards

The ESPPixelStick project includes ESP32 support, and project documentation distinguishes the ESP32 output mapping from the ESP8266 mapping.

'''Advantages'''

* More GPIO pins
* Greater processing capacity
* More RAM
* Better suited to multiple outputs
* More peripheral interfaces
* Greater potential for SD-card and Ethernet hardware
* Better suited to advanced controller designs

'''Limitations'''

* Pin assignments vary substantially by board
* Some GPIO pins are input-only
* Some pins are reserved for flash or onboard hardware
* Development-board layouts are not standardized
* Firmware images may be board-specific
* More features can create more configuration complexity

'''Best Suited For'''

* Multi-output controllers
* Higher pixel counts
* Controllers requiring several interfaces
* Stand-alone playback
* SD-card-equipped designs
* Advanced custom controller projects

'''B.6 ESP32 Development-Board Variations'''

Not every board labeled “ESP32” is electrically identical.

Differences may include:

* 30-pin versus 36-pin or 38-pin headers
* Different USB-to-serial chips
* Different voltage regulators
* External antenna connector
* PSRAM
* Different flash sizes
* Different onboard LED pins
* Different boot and reset circuits
* Missing or internally reserved GPIO pins

'''Engineering Note'''

Never select GPIO assignments solely from the processor datasheet.

Verify the schematic or pinout for the exact development board being used.

Appendix A should be consulted after identifying the exact board model.

'''B.7 Specialized ESP32 Pixel Controllers'''

Several third-party controller boards use ESP32 processors and provide circuitry intended specifically for pixel control.

Depending upon the design, these boards may include:

* Multiple fused outputs
* Logic-level shifting
* Power distribution
* Differential outputs
* Ethernet
* SD-card socket
* External antenna connector
* Output-status LEDs
* Temperature monitoring

A recent ESPPixelStick issue documents operation on a QuinLED ESP32-based controller using a Version 4 beta build, but it also illustrates why each output mapping must be verified for the exact board and firmware combination.

'''Advantages'''

* Less custom wiring
* Integrated output protection
* Multiple pixel outputs
* Convenient power distribution
* Mechanically organized connectors
* Better suited to permanent controller installations

'''Limitations'''

* Board-specific firmware configuration
* Output numbering may not match physical labeling
* Some features may not yet be supported by ESPPixelStick
* More expensive than a bare development board
* Manufacturer revisions may change pin assignments

'''Best Suited For'''

* Medium and large props
* Centralized multi-output controllers
* Matrixes
* Megatrees
* Users who want integrated power distribution

'''B.8 Wi-Fi Hardware'''

Most ESP8266 and ESP32 development boards include Wi-Fi.

Wi-Fi controllers are useful when:

* Running network cable is impractical
* Controllers are distributed throughout a display
* Pixel data rates remain within the network design limits
* Suitable access-point coverage is available

'''Advantages'''

* Minimal data cabling
* Easy placement near props
* Low-cost network architecture
* Convenient for temporary displays

'''Limitations'''

* Radio interference
* Dependence on access-point coverage
* Shared wireless bandwidth
* Performance affected by antenna placement
* Metal enclosures may reduce signal strength

'''Engineering Recommendation'''

Do not place a controller antenna directly against:

* Metal enclosure walls
* Power supplies
* Large wiring bundles
* Grounded metal mounting plates

Where practical, position the antenna near a nonmetallic portion of the enclosure.

'''B.9 Ethernet Hardware'''

Ethernet may provide:

* Predictable wired connectivity
* Reduced dependence on radio conditions
* Convenient use in dense controller installations
* Improved network isolation

However, Ethernet support depends on both the controller hardware and the firmware driver.

Support should never be assumed merely because an ESP32 board includes an Ethernet connector.

Project issues show continuing work and requests involving ESP32 Ethernet, W5500 SPI Ethernet, and additional Ethernet switching hardware. These items demonstrate that support varies by interface and firmware revision.

'''Common Ethernet Types'''

'''Internal ESP32 Ethernet MAC with External PHY'''

Some ESP32 boards use the processor’s built-in Ethernet MAC with an external physical-layer device.

Examples may use:

* LAN8720
* Other RMII PHY devices

'''SPI Ethernet'''

Some boards use an Ethernet controller connected through SPI.

A common example is:

* W5500

An open project enhancement request specifically addresses W5500 SPI Ethernet support, so it should not be treated as universally supported without checking the current firmware status.

'''Engineering Recommendation'''

Before purchasing an Ethernet controller, verify:

# Exact Ethernet controller or PHY
# Exact ESP32 variant
# Required firmware build
# GPIO assignments
# Whether the interface has been tested with ESPPixelStick
# Whether Wi-Fi and Ethernet can be enabled in the intended configuration

'''B.10 SD-Card Hardware'''

Some ESP32 boards include or support SD-card storage.

SD storage may be used for:

* Sequence files
* Stand-alone playback
* FPP remote operation
* Configuration or log storage

Not every SD-card interface is wired in the same manner.

Important differences include:

* SPI versus SDMMC interface
* Chip-select pin
* Shared SPI devices
* Card-detect switch
* Power-control circuitry

'''Engineering Note'''

An SD-card socket on the board does not guarantee ESPPixelStick support.

The firmware must support the board’s specific SD interface and pin mapping.

'''B.11 PSRAM'''

Some ESP32 modules include external pseudo-static RAM, commonly called PSRAM.

PSRAM may be useful for:

* Large frame buffers
* Large web resources
* Sequence playback
* Memory-intensive features

However, basic pixel output does not always require PSRAM.

'''Engineering Recommendation'''

Do not select a PSRAM-equipped board unless the intended firmware feature benefits from it.

Extra memory does not correct poor power distribution, network design, or signal wiring.

'''B.12 External Antennas'''

Some modules provide a U.FL or similar connector for an external antenna.

External antennas may improve:

* Range
* Enclosure placement
* Signal strength through walls
* Performance inside large installations

'''Caution'''

A board with an external antenna connector may require:

* A resistor or jumper change
* Selection between onboard and external antenna
* A compatible 2.4 GHz antenna
* Proper antenna mounting

Never operate a radio design in a configuration prohibited by its manufacturer.

'''B.13 USB Interfaces'''

Development boards may use:

* Micro-USB
* USB-C
* USB-to-UART bridge
* Native USB
* Separate programming and power ports

USB may provide:

* Firmware installation
* Serial diagnostics
* Power during bench testing

'''Common USB Problems'''

* Charge-only cable
* Insufficient cable quality
* Missing driver
* USB connector used only for power
* Incorrect boot mode
* Native-USB firmware mismatch

'''B.14 Logic-Level Output Circuitry'''

Most ESP8266 and ESP32 GPIO signals operate at approximately 3.3 V logic.

Many pixels accept these signals directly under favorable conditions, but not every installation has sufficient signal margin.

Controller hardware may include:

* Logic-level shifter
* Series resistor
* Output buffer
* Differential transmitter
* Electrostatic-discharge protection

'''Bare Development Board'''

A bare development board usually does not provide robust pixel-output conditioning.

It may function successfully during bench testing but become unreliable with:

* Longer data cables
* Lower pixel supply voltage margin
* Electrical noise
* Outdoor wiring
* Multiple connectors

'''Purpose-Built Controller'''

A purpose-built controller usually provides a more predictable output interface.

This is particularly useful for:

* Long-term outdoor installations
* Long data leads
* Large props
* Equipment repeatedly connected and disconnected

'''B.15 Hardware Comparison Table'''

{|
!width="16%"| '''Hardware Category'''
!width="12%"| '''Typical Processor'''
!width="13%"| '''Wi-Fi'''
!width="13%"| '''Ethernet'''
!width="14%"| '''Practical Output Capacity'''
!width="14%"| '''Integrated Pixel Interface'''
!width="15%"| '''Relative Complexity'''
|-
| ESPixelStick production board
| ESP8266
| Yes
| No
| Single principal output
| Yes
| Low
|-
| ESP-01 custom board
| ESP8266
| Yes
| No
| Very limited
| Usually external
| Medium
|-
| D1 Mini
| ESP8266
| Yes
| No
| Single or small number
| Usually external
| Low to medium
|-
| NodeMCU
| ESP8266
| Yes
| No
| Single or small number
| Usually external
| Low to medium
|-
| Generic ESP32 DevKit
| ESP32
| Yes
| Board dependent
| Multiple outputs
| Usually external
| Medium
|-
| Specialized ESP32 pixel board
| ESP32
| Usually
| Board dependent
| Multiple outputs
| Usually yes
| Medium
|-
| ESP32 Ethernet board
| ESP32
| Often
| Yes
| Multiple outputs
| Board dependent
| Medium to high
|-
| Newer ESP32-family board
| Varies
| Usually
| Varies
| Firmware dependent
| Usually external
| Experimental
|-
| Custom controller PCB
| ESP8266 or ESP32
| Design dependent
| Design dependent
| Design dependent
| Design dependent
| High
|}

'''Table Note'''

“Practical Output Capacity” is intentionally descriptive rather than numerical.

The actual number of usable outputs depends on:

* Firmware limits
* Processor timing resources
* Pixel protocol
* Frame rate
* Pixel count
* GPIO availability
* Other enabled interfaces

'''B.16 Feature Comparison Table'''

{|
!width="28%"| '''Feature'''
!width="19%"| '''ESP8266'''
!width="23%"| '''Conventional ESP32'''
!width="28%"| '''Specialized ESP32 Board'''
|-
| Low purchase cost
| Excellent
| Good
| Moderate
|-
| Small physical size
| Excellent
| Good
| Varies
|-
| Single-output prop control
| Excellent
| Excellent
| Excellent
|-
| Multi-output control
| Limited
| Good
| Excellent
|-
| Available GPIO
| Limited
| Good
| Board dependent
|-
| Integrated USB
| Board dependent
| Common
| Common
|-
| Ethernet potential
| Limited
| Good
| Board dependent
|-
| SD-card potential
| Limited
| Good
| Board dependent
|-
| PSRAM availability
| No
| Some modules
| Board dependent
|-
| Built-in pixel protection
| Rare
| Rare
| Common
|-
| Ease of custom wiring
| Good
| Moderate
| Excellent
|-
| Firmware certainty
| Mature platform
| Build dependent
| Board dependent
|}

'''B.17 Selecting Hardware by Application'''

'''Small Individual Prop'''

Recommended characteristics:

* ESP8266 or small ESP32
* One pixel output
* Wi-Fi
* Compact enclosure
* Simple power input

Typical choices:

* ESPPixelStick production board
* D1 Mini with output buffer
* Small dedicated controller

'''Large Individual Prop'''

Recommended characteristics:

* ESP32
* Several GPIO outputs
* Suitable level shifting
* Adequate power distribution
* Strong strain relief

Typical choices:

* Generic ESP32 with custom interface board
* Specialized multi-output ESP32 controller

'''Matrix'''

Recommended characteristics:

* ESP32
* Multiple outputs
* Good memory capacity
* High network throughput
* Well-organized power distribution
* Optional SD-card capability

'''DMX or Renard Device'''

Recommended characteristics:

* Supported serial output
* RS-485 transceiver where required
* Correct connector pinout
* Proper line termination where applicable

A production ESPPixelStick includes RS-485 hardware intended for serial lighting interfaces.

'''Distributed Yard Display'''

Recommended characteristics:

* Compact Wi-Fi controllers
* One controller near each prop
* Minimal long pixel-data cables
* Weather-resistant enclosure
* Replaceable low-cost hardware

'''Centralized Controller'''

Recommended characteristics:

* Multiple outputs
* Ethernet where supported
* Fused power distribution
* Larger enclosure
* Organized cable entry
* Adequate ventilation

'''B.18 Newer ESP32-Family Processors'''

The ESP32 family now includes several processor variants.

Examples include:

* ESP32-S2
* ESP32-S3
* ESP32-C2
* ESP32-C3
* ESP32-C6
* Other later variants

These processors are not automatically interchangeable with the original ESP32.

Differences may include:

* Processor architecture
* Number of cores
* USB support
* GPIO matrix
* Peripheral availability
* Radio capabilities
* Memory arrangement
* Arduino core support

A February 2026 project issue requests consideration of an ESP32-S3-based platform, indicating that support for newer variants should still be verified rather than assumed.

'''Engineering Recommendation'''

For Version 0.1 of this manual, newer ESP32-family processors should be identified as:

'''Board- and firmware-build dependent. Verify current support before purchasing hardware.'''

'''B.19 Unsupported and Experimental Hardware'''

A board may be considered experimental when:

* It requires a custom firmware build.
* It is not present in the standard installer.
* GPIO mappings have not been documented.
* Ethernet or SD support is incomplete.
* It appears only in an unresolved issue or discussion.
* Only one user has reported successful operation.
* Required libraries differ from the normal project build.

'''Warning'''

Do not describe hardware as officially supported solely because:

* The firmware compiled once.
* A similar processor is supported.
* WLED supports the board.
* Arduino recognizes the board.
* The board boots to a web interface.
* One output happened to operate.

Complete support requires testing of the functions actually needed by the application.

'''B.20 Hardware Evaluation Checklist'''

Before selecting a controller, record the following:

{|
!width="34%"| '''Item'''
!width="65%"| '''Information Required'''
|-
| Manufacturer
| Exact manufacturer or seller
|-
| Board model
| Full model and revision
|-
| Processor
| Exact ESP8266 or ESP32 variant
|-
| Module
| Exact module designation
|-
| Flash
| Capacity and mode
|-
| PSRAM
| Present or absent
|-
| USB
| Connector and interface type
|-
| Wi-Fi antenna
| Internal or external
|-
| Ethernet
| PHY or controller type
|-
| SD card
| Interface and pin assignment
|-
| Available GPIO
| Verified from board schematic
|-
| Output buffering
| Present or absent
|-
| Power input
| Voltage range
|-
| Firmware build
| Exact compatible image
|-
| Test status
| Verified functions
|-
| Documentation
| Link or saved schematic
|}

[[File:vertopal_635af067709144fabe2de355e6a715d4/media/image3.png|624x374px]]'''Figure B-20-1 – Board Evaluation Checklist'''

'''B.21 Recommended Selection Strategy'''

A practical selection process is:

# Define the required number of outputs.
# Determine whether Wi-Fi or Ethernet is required.
# Determine whether SD storage is required.
# Identify voltage and power-distribution requirements.
# Select a processor family.
# Select the exact board.
# Verify the required firmware build.
# Verify GPIO assignments.
# Test one controller before purchasing multiples.
# Document the final configuration.

'''Why This Matters'''

Low-cost development boards frequently change without notice.

A seller may substitute:

* Different USB chip
* Different flash device
* Different regulator
* Different module revision
* Different board layout

Testing one sample before a large purchase can prevent an expensive incompatibility.

'''B.22 Engineering Recommendations'''

✔ Prefer documented hardware over unknown hardware.

✔ Identify the exact board, not only the processor family.

✔ Verify the firmware build before purchasing multiple boards.

✔ Check all GPIO assignments against the exact schematic.

✔ Do not assume Ethernet support from the presence of an Ethernet connector.

✔ Use purpose-built output circuitry for permanent installations.

✔ Select ESP8266 for simple, economical single-output controllers.

✔ Select ESP32 when additional outputs, memory, or interfaces are required.

✔ Treat newer ESP32 variants as board- and build-dependent until verified.

✔ Test every required interface before deploying the controller.

'''B.23 Open Research Items'''

{|
!width="12%"| '''Status'''
!width="87%"| '''Item'''
|-
| 🟨
| Exact Version 4.x board list for the web installer
|-
| 🟨
| Current support status for ESP32-S2
|-
| 🟨
| Current support status for ESP32-S3
|-
| 🟨
| Current support status for ESP32-C3
|-
| 🟨
| Current support status for ESP32-C6
|-
| 🟨
| W5500 SPI Ethernet support status
|-
| 🟨
| Supported RMII Ethernet PHY devices
|-
| 🟨
| SD-card interface compatibility by board
|-
| 🟨
| PSRAM usage by individual firmware features
|-
| 🟨
| Verified QuinLED board and output mappings
|-
| 🟨
| Maximum tested outputs by processor and protocol
|-
| 🟨
| Standardized hardware-validation procedure
|}

'''References'''

This appendix is based upon:

* ESPPixelStick GitHub repository
* ESPPixelStick Supported Inputs and Outputs documentation
* ESPPixelStick product documentation
* ESPPixelStick GitHub issue and discussion records
* Espressif processor and module documentation
* Controller-manufacturer schematics

The project repository identifies ESP8266 and ESP32 as the principal platforms, while current issue records show that support for particular Ethernet devices, specialized boards, and newer ESP32-family variants continues to evolve.

'''Revision History'''

{|
!width="8%"| '''Version'''
!width="8%"| '''Date'''
!width="83%"| '''Description'''
|-
| 0.1
| July 2026
| Initial hardware-comparison appendix
|-
| 0.5
| July 2026
| Expanded platform categories, comparison tables, selection guidance, evaluation checklist, research items, and current support cautions
|}

@@ Line 3: / Line 3: @@
 '''Version:''' 0.1 (Draft)
-'''Written for:''' ESPPixelStick Version 4.x
+'''Written for:''' ESPixelStick Version 4.x
 '''Last Updated:''' July 2026
@@ Line 15: / Line 15: @@
 '''Purpose'''
-This appendix compares common microcontroller and controller-board categories that may be used with ESPPixelStick firmware.
+This appendix compares common microcontroller and controller-board categories that may be used with ESPixelStick firmware.
 It is intended to help readers select hardware appropriate for:
@@ Line 30: / Line 30: @@
 '''Related Chapters'''
-* Chapter 2 – ESPPixelStick Overview
+* Chapter 2 – ESPixelStick Overview
 * Chapter 3 – Supported Hardware
 * Chapter 4 – Hardware Installation
@@ Line 77: / Line 77: @@
 '''B.3 ESPixelStick Production Hardware'''
-The original ESPPixelStick hardware was designed specifically for pixel and serial-lighting applications.
+The original ESPixelStick hardware was designed specifically for pixel and serial-lighting applications.
-A production ESPPixelStick board generally provides:
+A production ESPixelStick board generally provides:
 * ESP8266 processor
@@ Line 124: / Line 124: @@
 * Other ESP8266 development boards
-The ESP8266 is the original platform associated with ESPPixelStick and remains useful for small, distributed controllers.
+The ESP8266 is the original platform associated with ESPixelStick and remains useful for small, distributed controllers.
 '''Advantages'''
@@ Line 151: / Line 151: @@
 * Single-output designs
-* Existing ESPPixelStick-style hardware
+* Existing ESPixelStick-style hardware
 * Very small custom controllers
@@ Line 191: / Line 191: @@
 * Other conventional dual-core ESP32 boards
-The ESPPixelStick project includes ESP32 support, and project documentation distinguishes the ESP32 output mapping from the ESP8266 mapping.
+The ESPixelStick project includes ESP32 support, and project documentation distinguishes the ESP32 output mapping from the ESP8266 mapping.
 '''Advantages'''
@@ Line 261: / Line 261: @@
 * Temperature monitoring
-A recent ESPPixelStick issue documents operation on a QuinLED ESP32-based controller using a Version 4 beta build, but it also illustrates why each output mapping must be verified for the exact board and firmware combination.
+A recent ESPixelStick issue documents operation on a QuinLED ESP32-based controller using a Version 4 beta build, but it also illustrates why each output mapping must be verified for the exact board and firmware combination.
 '''Advantages'''
@@ Line 276: / Line 276: @@
 * Board-specific firmware configuration
 * Output numbering may not match physical labeling
-* Some features may not yet be supported by ESPPixelStick
+* Some features may not yet be supported by ESPixelStick
 * More expensive than a bare development board
 * Manufacturer revisions may change pin assignments
@@ Line 369: / Line 369: @@
 # Required firmware build
 # GPIO assignments
-# Whether the interface has been tested with ESPPixelStick
+# Whether the interface has been tested with ESPixelStick
 # Whether Wi-Fi and Ethernet can be enabled in the intended configuration
@@ Line 395: / Line 395: @@
 '''Engineering Note'''
-An SD-card socket on the board does not guarantee ESPPixelStick support.
+An SD-card socket on the board does not guarantee ESPixelStick support.
 The firmware must support the board’s specific SD interface and pin mapping.
@@ Line 683: / Line 683: @@
 Typical choices:
-* ESPPixelStick production board
+* ESPixelStick production board
 * D1 Mini with output buffer
 * Small dedicated controller
@@ Line 722: / Line 722: @@
 * Proper line termination where applicable
-A production ESPPixelStick includes RS-485 hardware intended for serial lighting interfaces.
+A production ESPixelStick includes RS-485 hardware intended for serial lighting interfaces.
 '''Distributed Yard Display'''
@@ Line 961: / Line 961: @@
 This appendix is based upon:
-* ESPPixelStick GitHub repository
+* ESPixelStick GitHub repository
-* ESPPixelStick Supported Inputs and Outputs documentation
+* ESPixelStick Supported Inputs and Outputs documentation
-* ESPPixelStick product documentation
+* ESPixelStick product documentation
-* ESPPixelStick GitHub issue and discussion records
+* ESPixelStick GitHub issue and discussion records
 * Espressif processor and module documentation
 * Controller-manufacturer schematics

@@ Line 55: / Line 55: @@
 For this reason, processor compatibility does not automatically guarantee complete board compatibility.
-[[File:vertopal_635af067709144fabe2de355e6a715d4/media/image1.png|624x374px]]'''Figure B-1-1 – Hardware Selection Process'''
+[[File:Figure_B-01-01_Hardware_Selection.png|thumb|none|600px|'''Figure B-1-1 – Hardware Selection Process''']]
 '''Engineering Note'''
@@ Line 861: / Line 861: @@
 |}
-[[File:vertopal_635af067709144fabe2de355e6a715d4/media/image3.png|624x374px]]'''Figure B-20-1 – Board Evaluation Checklist'''
+[[File:Figure_B-20-01_Board_Checklist.png|thumb|none|600px|'''Figure B-20-1 – Board Evaluation Checklist''']]
 '''B.21 Recommended Selection Strategy'''
@@ Line 981: / Line 981: @@
 | Initial hardware-comparison appendix
 |-
 |}

@@ Line 1: / Line 1: @@
 '''Appendix B – Controller Hardware Comparison'''
-'''Version:''' 0.5 (Draft)
+'''Version:''' 0.1 (Draft)
 '''Written for:''' ESPPixelStick Version 4.x