Rename Physical Driver to Parallel LED Driver + migration

Docs
====
-  Multiple updates

Author: ewowi

docs/develop/development.md

@@ -14,7 +14,7 @@
 
 * Want to make changes: fork the repo (see installation)and submit pull requests, see [creating-a-pull-request-from-a-fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork):
 
-    * Press Branches, press New Branch, give it a name e.g. background-script and press Create new Branch, click on background-script
+    * Only branch from the main branch! Press Branches, press New Branch, give it a name e.g. background-script and press Create new Branch, click on background-script
 
       <img width="90" src="https://github.com/user-attachments/assets/588d0854-bac1-4b70-8931-ba6db4c94248" />
 

docs/develop/drivers.md

@@ -38,7 +38,7 @@ The development environment consists of
 
     <img width="320" src="https://github.com/user-attachments/assets/74928dac-d59b-4489-b97b-759c6d792b77" />
 
-    * The main branch will be checked out per default. To run / test latest developments, switch to the dev branch
+    * The main branch will be checked out per default. Latest development will be done in branches from main, merged back into main when done.
 
 ## Install and setup VSCode
 

docs/develop/installation.md

@@ -65,19 +65,19 @@ A node implements the following (overloaded) functions:
 
 ### Initless drivers
 
-Initless means there is no addLeds (like in FastLed) or initLed (like in physical and virtual driver): 
+Initless means there is no addLeds (like in FastLed) or initLed (like in Parallel LED Driver): 
 
 * a Context (see below) will be set
 * Driver.show (see below) will use this context to set the right data to the right output.
 * The context can dynamically change without needing to reboot or recompile! e.g. changes in pin allocations, leds per pin, RGB or RGBW, or DMX lights like moving heads.
 
-The Art-Net driver is currently working like this, to be added to physical and virtual driver and parallel IO (P4).
+The Art-Net driver is currently working like this, to be added to Parallel LED Driver and parallel IO (P4).
 
 The advantages of dynamic context change are:
 
 * No need to recompile any changed configs (e.g. colorOrder is fully flexible, not a setting in platformio.ini)
 * No need to restart while setting up a specific installation. Just change layouts until it works as intended.
-* Allows for a flexible mix of different outputs e.g. send the first 1024 leds to physical driver, next to virtual driver, next to spi, next to one Art-Net device, next to another Art-Net device. 
+* Allows for a flexible mix of different outputs e.g. send the first 1024 leds to Parallel LED Driver, next to SPI, next to one Art-Net device, next to another Art-Net device. 
 
 #### Context
 

docs/develop/nodes.md

@@ -7,7 +7,7 @@
 * Part of submitting a change via a pull request is updated documentation. Functionality and documentation should be in one Pull Request 
 * Make minimal changes in upstream (Sveltekit) code, as we need to stay in sync as easy as possible. Add // 🌙 to show a change has been made.
 * The main branch is the source to branch and merge to, no direct code commits to the main branch. As the main branch docs folder is the source for the website, doc changes can be made directly to main. 
-* The dev branch is used for latest updates between releases. Optionally branch from dev if latest updates are needed for a change.
+* Branches from main are made for latest updates and merged back to main when done.
 * The src folder is for all MoonBase and MoonLight Nodes and Modules development. No need for UI changes as that is generated for Nodes and Modules. The lib folder is for upstream (Sveltekit). The interface folder is for UI, mainly Sveltekit and Modules and Nodes generic functions.
 * A pull request should contain compilable code and tested to not crash the system at minimal and support also boards without PSRAM, e.g. ESP32-D0. Code may be work in progress.
 

docs/develop/standardsguidelines.md

@@ -139,11 +139,11 @@ Keep this page visible until installation complete.
 !!! tip "Choose driver"
     FastLED driver is best to start with if you have a normal (ws2812) LED strip or panel. 
 
-    Choose the Physical driver if you have more then 4 LED strips or panels or non standard LEDS (e.g. RGBW lights, curtains...). Other drivers (Virtual, Hub,) not supported yet.
+    Choose the Parallel LED Driver if you have more then 4 LED strips or panels or non standard LEDS (e.g. RGBW lights, curtains...). Other drivers (Virtual, Hub,) not supported yet.
 
     In some cases restart the device to make layout changes effective is needed.
 
-    For ESP32-P4-Nano, choose Physical driver, using the Parallel IO driver by @Troyhacks. Easy quick start: choose Pin 37 and connect a LED strip or panel as follows (Note: the pins on the board the jst connector is plugged in are in order +, Ground, Data !!! - Ignore the wire colors!):
+    For ESP32-P4-Nano, choose Parallel LED Driver, using the Parallel IO driver by @Troyhacks. Easy quick start: choose Pin 37 and connect a LED strip or panel as follows (Note: the pins on the board the jst connector is plugged in are in order +, Ground, Data !!! - Ignore the wire colors!):
 
     <img width="200" src="../../media/moonlight/esp32-p4-nano-quickstart.jpeg"/>
 

docs/gettingstarted/installation.md

@@ -3,14 +3,48 @@
 <img width="320" height="441" alt="io11" src="https://github.com/user-attachments/assets/b5452d8e-400c-4a72-a195-d5b7a7764407" />
 <img width="320" height="77" alt="io22" src="https://github.com/user-attachments/assets/99fd135c-8d36-463b-ae3a-f06119cb8ccb" />
 
-Shows info about input / output devices, e.g. GPIO pins.
+Defines hardware specifics per ESP32 device 🆕
+Currently the following boards are defined. Not all are supported yet 🚧
+
+<Image>
+
+For each board the following presets are defined:
+
+* Modded: if any change to the default preset is made.
+* Max Power: adjust the brightness to approach this max power, depending on the number of LEDs used.
+* Pins: This module is the central place to assign functionality to gpio pins. Other modules and nodes use the pin assignments made here.
 
 * Per pin:
     * GPIO = gpio_num;
-    * PinInfo : pin assignments: currently only static 🚧
+    * Usage: Can be updated, see below
     * Summary
        * Valid (✅)
        * Output (💡)
        * RTC (⏰);
     * Level (HIGH, LOW, N/A)
     * DriveCap (WEAK, STRONGER, MEDIUM, STRONGEST, N/A)
+
+<image>
+
+## Pin usage
+
+  * Supported
+    * LEDs DIO 01 to 20
+    * Voltage
+    * Current
+    * Infrared
+    * Button On/Off
+  * Planned soon
+    * Battery
+    * Relais brightness
+    * DMX (in)
+  * Planned later
+    * I2S for microphone and line in
+    * I2C
+
+## Naming convention
+
+- MCU: The ESP32 chip
+- MCU-Board: MCU on a PCB
+- Carrier Board: MCU-board + connectors...
+- Device: All of the above in a box

docs/moonbase/inputoutput.md

@@ -8,7 +8,7 @@ The Drivers module defines layers and drivers.
 
 * Layout 🚥: A layout (🚥) defines the positions of the lights to control. See [Layouts](https://moonmodules.org/MoonLight/moonlight/layouts/)
 * Driver ☸️: A driver is a link between MoonLight to hardware or the network. Drivers can both input data or output data. Examples:
-    * LED drivers (FastLED, Physical and Virtual drivers, hub75 panels)
+    * LED drivers (FastLED, Parallel LED Drivers, hub75 panels)
     * Light driver (Art-Net / DMX)
     * Audio driver
     * Sensor drivers (microphone, gyro, MIDI controller)
@@ -30,17 +30,20 @@ Want to add a Driver to MoonLight, see [develop](https://moonmodules.org/MoonLig
 
 | Name | Preview | Controls | Remarks
 | ---- | ----- | ---- | ---- |
-| Physical LED Driver | <img width="100" src="https://github.com/user-attachments/assets/9cbe487e-f330-40a5-8b40-6663c83e5d90"/> | <img width="320" alt="Physical" src="https://github.com/user-attachments/assets/0c6f1543-623a-45bf-98d7-f5ddd072a1c6" /> | Drive multiple LED types, all devices including ESP32-P4(-nano) supported<br>Max Power and Light preset: See below<br>DMA buffer: set higher when LEDs flicker |
+| Parallel LED Driver | <img width="100" src="https://github.com/user-attachments/assets/9cbe487e-f330-40a5-8b40-6663c83e5d90"/> | <img width="320" alt="Parallel" src="https://github.com/user-attachments/assets/0c6f1543-623a-45bf-98d7-f5ddd072a1c6" /> | Drive multiple LED types, all devices including ESP32-P4(-nano) supported<br>Max Power and Light preset: See below<br>DMA buffer: set higher when LEDs flicker<br>Virtual LED Driver will be part of the Parallel LED driver.|
 | FastLED Driver | <img width="100" src="https://avatars.githubusercontent.com/u/5899270?s=48&v=4"/> | <img width="320" alt="FastLed" src="https://github.com/user-attachments/assets/d5ea1510-9766-4687-895a-b68c82575b8f" /> | Most used LED driver. Drive most common LEDs (WS2812).<br>Max Power: See below |
 | Art-Net | <img width="100" src="https://github.com/user-attachments/assets/9c65921c-64e9-4558-b6ef-aed2a163fd88"> | <img width="320" alt="Art-Net" src="https://github.com/user-attachments/assets/1428e990-daf7-43ba-9e50-667d51b456eb" /> | Drive LEDS and DMX lights over the network. See below |
 | AudioSync | <img width="100" src="https://github.com/user-attachments/assets/bfedf80b-6596-41e7-a563-ba7dd58cc476"/> | No controls | Listens to audio sent over the local network by WLED-AC or WLED-MM and allows audio reactive effects (♪ & ♫) to use audio data (volume and bands (FFT)) |
-| Virtual LED Driver | <img width="100" src="https://github.com/user-attachments/assets/98fb5010-7192-44db-a5c9-09602681ee15"/> | <img width="100" src="https://github.com/user-attachments/assets/c81d2f56-00d1-4424-a716-8e3c30e76636"/> | Driving max 120! outputs. E.g. 48 panels of 256 LEDs each run at 50-100 FPS using shift registers<br>Not implemented yet |
 | HUB75 Driver | <img width="100" src="https://github.com/user-attachments/assets/620f7c41-8078-4024-b2a0-39a7424f9678"/> | <img width="100" src="https://github.com/user-attachments/assets/4d386045-9526-4a5a-aa31-638058b31f32"/> | Drive HUB75 panels<br>Not implemented yet |
 | IR Driver 🆕🚧 | <img width="100" src="../../media/moonlight/IRDriver.jpeg"/> |  | Receive IR commands and [Lights Control](https://moonmodules.org/MoonLight/moonlight/lightscontrol/) |
 
+
+Virtual LED Driver: Driving max 120! outputs. E.g. 48 panels of 256 LEDs each run at 50-100 FPS using shift registers. Not implemented yet
+<img width="100" src="https://github.com/user-attachments/assets/98fb5010-7192-44db-a5c9-09602681ee15"/><img width="100" src="https://github.com/user-attachments/assets/c81d2f56-00d1-4424-a716-8e3c30e76636"/>
+
 ### Max Power and Light Preset
 
-* **Max Power**: max amount of power in watts to send to LEDs. Default 10: 5V * 2A = 10W (so it runs fine on USB)
+* **Max Power**: max amount of power in watts to send to LEDs. Default 10: 5V * 2A = 10W (so it runs fine on USB). 🆕: Moved to board presets in [Module IO](https://moonmodules.org/MoonLight/moonbase/inputoutput/).
 
 * **Light preset**: Defines the channels per light and color order
 

docs/moonlight/drivers.md

@@ -10,7 +10,7 @@ build_flags =
   ; -D ARDUINO_USB_MSC_ON_BOOT=0 ;Mass Storage Class, disable
   ; -D ARDUINO_USB_DFU_ON_BOOT=0 ;download firmware update, disable
   ; -D ML_LIVE_MAPPING
-  ; Do not use the following FastLED settings! As we use the better version of this in Physical driver
+  ; Do not use the following FastLED settings! As we use the better version of this in Parallel LED Driverer
   ; -D FASTLED_USES_ESP32S3_I2S ; S3 boards use the I2S driver (RMT is not supporting more then 4 outputs)
   ; -DCOLOR_ORDER_RGB=1 ; not working yet, see also https://github.com/FastLED/FastLED/issues/1966, should use ML_COLOR_ORDER / FastLED.addLeds(RGB_ORDER), workaround change #define COLOR_ORDER_RBG in driver.h
 lib_deps =