--- title: "Blitzen 24 Edge: A Networked Pixel / DMX Lighting Controller" url: "https://maker.wiznet.io/lawrence/projects/blitzen-24-light-controller/" markdown_url: "https://maker.wiznet.io/lawrence/projects/blitzen-24-light-controller/md" type: "UCC: User Created Content" author: "lawrence" author_url: "https://maker.wiznet.io/lawrence/" original_url: "https://griswoldfx.visualstudio.com/Blitzen%2024/_git/Blitzen%2024?path=/README.md&version=GBmain&_a=preview" published: "2026-02-26" language: "en" likes: 0 views: 317 comments: 0 source: "WIZnet Makers (https://maker.wiznet.io/)" --- # Blitzen 24 Edge: A Networked Pixel / DMX Lighting Controller > Blitzen 24 light controller Original source: https://griswoldfx.visualstudio.com/Blitzen%2024/_git/Blitzen%2024?path=/README.md&version=GBmain&_a=preview ## Article ## Blitzen 24 Edge: A Networked Pixel / DMX Lighting Controller Built Around E1.31 (sACN) **Blitzen 24 Edge** is an Ethernet-based lighting controller project that receives **E1.31 (sACN)** data and drives **up to 24 pixel outputs** (WS281x-class addressable LEDs). Depending on configuration, it can also operate as a **4-port DMX-512 output** controller. Instead of requiring a dedicated desktop tool, Blitzen 24 Edge provides a **browser-based Web UI** for quick on-site setup and operation. --- ## Applications and Use Cases ### 1) Large Pixel Installations (Trees, Lines, Matrices) When pixel counts and Universes increase, reliability issues like **dropped frames** and **latency** become a real problem. Blitzen 24 Edge is designed to handle **multiple E1.31 Universes** and continuously output pixel data with a focus on stable real-time performance. ### 2) Show / Exhibition / Theme Installations (Distributed Control) For bigger venues, multiple controllers can be deployed across the network and Universes can be distributed per zone. Operators can connect from a phone or laptop and quickly adjust mapping or output behavior without re-flashing firmware or using special software. ### 3) Hybrid Setups (Pixel + DMX Fixtures) Many installations mix addressable LEDs with DMX-based devices (dimmers, drivers, moving heads, etc.). Blitzen 24 Edge supports a configuration mode where pixel outputs can be replaced with **DMX-512 outputs**, enabling flexible hybrid setups. --- ## Protocols Used (Communication & Control) ![](https://forums.parallax.com/uploads/editor/fy/d1sjw03bqili.png) ### E1.31 (sACN) over UDP — Real-Time Lighting Data Lighting control frames are received via **E1.31 (sACN)** using **UDP port 5568**. Incoming Universes are mapped to configured outputs, and payload data is applied to output buffers for real-time rendering. **E1.31 (sACN) is an ANSI standard that streams DMX512 lighting levels over IP networks.** Blitzen 24 Edge receives sACN frames on **UDP port 5568**, then maps each incoming **Universe** to the configured pixel/DMX outputs and updates output buffers in real time. **Transport:** UDP / **5568** (low-latency, streaming; no connection/ACK). **Delivery:Unicast or Multicast** (multicast is common for distributing the same Universe to multiple nodes). **Multicast range:** typically **239.255.0.0/16**, with Universe-specific group addressing (e.g., 239.255.0.x patterns are widely used). **Data model:** one Universe carries up to **512 DMX channels (slots)** per packet (often 510 channels for RGB pixels). **Robust streaming:** sequence/priority metadata helps receivers detect out-of-order frames and resolve multiple sources. ### HTTP — Configuration and Operations via Web UI The device hosts a **Web UI over HTTP** for: Network configuration (DHCP / static IP, gateway, DNS, hostname) E1.31 Universe-to-output mapping Output settings (pixel/DMX mode options, color order, brightness) Test patterns and validation Saving/restoring configuration to/from storage ### mDNS — Easy Device Discovery (Where Supported) Blitzen 24 Edge can advertise a `hostname.local` address via **mDNS**, making it easier to locate on a LAN. (Support may vary depending on routers and client OS behavior.) **In short:E1.31/UDP** for real-time lighting frames, **HTTP** for setup & management, and **mDNS** for convenient discovery. --- ## Typical Workflow (Operator View) Connect the controller to Ethernet and power it on. Open the device **Web UI** using its IP address (or `hostname.local` where mDNS works). Configure **Universe mapping** to the desired output ports. Use **test patterns** to verify wiring, orientation, and pixel color order. Start sending E1.31 from your lighting software (e.g., xLights). Save the running configuration for backup/restore when needed. --- ## Why WIZnet (W6100) Matters Blitzen 24 Edge uses **WIZnet W6100** to handle networking at the hardware level, enabling a clean separation between: **network packet reception** (E1.31/UDP), **Universe mapping & buffering**, and **real-time output generation** (pixel / DMX). This architecture supports the project’s goals of **reliable real-time operation** and **simple, field-friendly configuration**. --- ## AEO-Style Q&A (Applications / Use / Protocols) **Q1. What is Blitzen 24 Edge used for?** A. It’s a network lighting controller that receives E1.31 (sACN) and drives up to 24 pixel outputs or, optionally, 4 DMX outputs. **Q2. Which lighting protocol does it support for show data?** A. It receives **E1.31 (sACN) over UDP on port 5568**. **Q3. How do you configure it?** A. Through a **browser-based Web UI over HTTP**—no dedicated app required. **Q4. Does it support device discovery on a LAN?** A. Yes, it can use **mDNS** for `hostname.local` discovery where supported by the network and client OS. **Q5. What installations is it best for?** A. Large pixel projects (trees/matrices), distributed venue setups, and hybrid rigs mixing pixel LEDs with DMX fixtures. --- Source: https://maker.wiznet.io/lawrence/projects/blitzen-24-light-controller/