You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/moonbase/module/editor.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,13 @@ Ultimately the nodes will be displayed in a graphical interface where nodes are
11
11
12
12
Typically a node will define a layout (🚥), or an effect (🔥), or a modifier (💎) or a supporting process (☸️) but can also combine these tasks (experimental at the moment). To avoid duplication it's in most cases recommended to keep them seperated so an effect can run on multiple layouts and a modifier can modify any effect.
13
13
14
-
***Layout** 🚥: a layout defines what lights are connected to MoonLight. Currently only one layout node is supported defining all the lights (But might change in the future). It defines the coordinates of all lights (addLight) and assigns lights to the GPIO pins of the ESP32 (addPin) and how many channels each light has (normal LEDs 3: Red, Green and Blue).
14
+
***Layout** 🚥: a layout defines what lights are connected to MoonLight. It defines the coordinates of all lights (addLight) and assigns lights to the GPIO pins of the ESP32 (addPin) and how many channels each light has (normal LEDs 3: Red, Green and Blue).
15
15
* The **coordinates** of each light are defined in a 3D coordinate space where each coordinate range between 1 and 255. Currently a strip until 255 leds is supported, a panel until 128x96 LEDS and a cube max 20x20x20.
16
16
* Coordinates needs to be specified in the order the lights are wired so MoonLight knows which light is first, which is second etc.
17
17
* If a 1D strip is longer, you can address more leds by pretending it is a 2D fixture, e.g. 32x32 to address a strip of 1024 LEDs.
18
18
* In the future we might look at redefining Coord3D where width is 12 bytes, height is 7 bytes and depth is 5 bytes allowing for max 4096 x 128 x 32 ...
19
19
* Currently **pins** are by default driven by FastLED.show. FastLED needs all LEDs specifications be defined at compile time, e.g. LED type, color order, etc. Normally also the pin(s) need to be defined beforehand but all pins are predefined in the code to avoid this (at a cost of larger firmware). As we want to be able to define all LED specs in the UI instead of during compile, we need to see how / if this can be done.
20
+
* 🆕 **Multiple layout nodes** can be defined which will execute one after the other
20
21
* In the future, instead of pins, also **IP addresses and universes** can be specified to support sending lights data to ArtNet devices - e.g. [Pknight Artnet DMX 512](https://s.click.aliexpress.com/e/_ExQK8Dc) to control DMX lights or [ArtNet LED controller](https://s.click.aliexpress.com/e/_Ex9uaOk) to control LED strips or panels over local network. Currently this is handled by [Module ArtNet](https://moonmodules.org/MoonLight/moonbase/module/artnet/).
21
22
* Alternatively Moonlight supports 2 other drivers: [Physical Driver](https://github.com/hpwit/I2SClocklessLedDriver) and [Virtual Driver](https://github.com/ewowi/I2SClocklessVirtualLedDriver). Firmware ending with PD or VD will have this enabled. Code has been included but not tested yet (tested in StarLight), this is planned for June/July.
22
23
* The physical driver is an alternative to the FastLED driver and does not need LED specifications defined at compile time, all can be controlled via UI.
***Safe Mode**: MoonBase will jump into safe mode after a crash, see [System Status](https://moonmodules.org/MoonLight/system/status/). In safe mode, MoonLight will disable the following features:
6
+
* Add more then 1024 lights
7
+
* Execute a live script
8
+
9
+
This list is dynamic and will change over time if crash reasons change.
Copy file name to clipboardExpand all lines: docs/system/status.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,16 @@
4
4
5
5
## Functional
6
6
7
-
* <imgwidth="30"src="https://github.com/user-attachments/assets/b0e8af99-ed76-422a-8bd1-bfbd9e0f4c44"/> Performance: loops per second: nr of times main loop is executed
7
+
* 🌙 **Performance**: loops per second: nr of times main loop is executed
8
+
* 🌙 **Safe Mode** 🆕: After a crash, the device will start in Safe Mode disabling possible causes of crashes. See also [MoonLight](https://moonmodules.org/MoonLight/moonlight/general/). In case of safe mode, the statusbar will show a shield: 🛡️. Try to find the reason of the crash and correct and restart the device. If no crash, it will go out of safe mode.
8
9
9
-
* Sleep: Device is set in low power mode.
10
-
* Restart: The device will restart
11
-
* Factory reset: all settings will be removed.
10
+
***Sleep**: Device is set in low power mode.
11
+
***Restart**: The device will restart
12
+
***Factory reset**: all settings will be removed.
12
13
13
14
## Technical
14
15
15
-
*<imgwidth="30"src="https://github.com/user-attachments/assets/b0e8af99-ed76-422a-8bd1-bfbd9e0f4c44"/> Reordered info from dynamic to static
0 commit comments