Updated E1.31 & UDP Realtime Control (markdown)

This commit is contained in:
Aircoookie 2018-11-01 16:20:27 +01:00
parent 02fec9c35f
commit 035cd57308
1 changed files with 9 additions and 8 deletions

View File

@ -3,19 +3,20 @@
WLED supports the E1.31 (sACN) realtime light protocol.
I highly recommend the [LedFx](https://github.com/ahodges9/LedFx) project!
170 LEDs (510 DMX channels) are supported per universe.
You can use up to 5 adjacent universes which is a total of 850 LEDs.
LedFx users: If you want to use more than 170 LEDs, you need to go to additional settings and set "Universe Size" to 510!
### Hyperion
You can now use WLED with the popular Ambilight software Hyperion.
Just configure Hyperion to use an UDP device with protocol 0 on port 19446!
The maximum number of LEDs supported in this mode is 480. (WLED 0.8.0 and lower: 341)
The maximum number of LEDs supported in this mode is 490. (WLED 0.8.0 and lower: 341)
### UDP Realtime
Additionally, WLED offers a way to directly drive the connected LEDs via UDP. The protocol is referred to as WLED [Audio-Reactive-Led-Strip](https://github.com/scottlawsonbc/audio-reactive-led-strip) (WARLS), since the support of that project was its primary goal. However, it can also be used for other realtime applications like an ambilight.
The maximum number of LEDs supported in these modes is 480. (WLED 0.8.0 and lower: 341)
WARLS uses the same UDP port the notifier uses (default 21324, can be changed in settings).
At the moment, the web UI will be disabled while active, the HTTP API, Alexa and button control remains functional.
@ -23,13 +24,13 @@ It uses the current brightness and gamma correction settings.
Byte 0 of the UDP packet tells the server which realtime protocol to use.
Value | Description
Value | Description | Max. LEDs
--- | ---
1 | WARLS
2 | DRGB
3 | DRGBW
4 | DNRGB
0 | WLED Notifier
1 | WARLS | 255
2 | DRGB | 490
3 | DRGBW | 367
4 | DNRGB | 489/packet
0 | WLED Notifier | -
In every protocol, Byte 1 tells the server how many seconds to wait after the last received packet before returning to normal mode, in practice you should use 1-2 (seconds) here in most cases so that the module returns to normal mode quickly after the end of transmission.