Where This Can Be Used

Modern lighting systems rarely operate in isolation. A lighting console may control stage fixtures, while a separate NovaStar processor manages the LED wall. Although both devices are connected to the same Ethernet network, they often communicate using different protocols and cannot interact directly.

This project addresses that gap by acting as a dedicated protocol bridge. Instead of requiring an operator to manually trigger both systems, it monitors a predefined Art-Net DMX value and automatically sends the corresponding TCP command to a NovaStar controller.

Typical deployment scenarios include:

• Live concerts and stage productions
• Exhibition and museum installations
• Broadcast studios
• Theme parks and permanent attractions
• LED media façade control
• Automated blackout or screen enable systems

Because the bridge operates entirely over wired Ethernet, it integrates naturally into existing show-control networks without requiring Wi-Fi configuration or additional control software.

System Block Diagram

Lighting Console / Media Server
            |
      Art-Net DMX (UDP)
            |
            v
     WIZnet W5500 Ethernet
            |
            v
    Arduino-compatible MCU
            |
            v
   Art-Net Packet Processing
            |
            v
Universe / Channel Evaluation
            |
            v
 NovaStar TCP Command Generator
            |
            v
      NovaStar VX/V1000
            |
            v
         LED Display

Architecture Overview

The system has a single responsibility: observe incoming Art-Net traffic and convert one specific DMX condition into a NovaStar control command.

Rather than forwarding Art-Net packets, the firmware extracts only the information it needs. Once the configured universe and DMX value match the required condition, the MCU transmits a predefined binary TCP command to the NovaStar controller.

This event-driven architecture keeps processing simple while minimizing unnecessary network traffic.

What the Project Does

The firmware continuously listens for Art-Net packets on the standard UDP port used by Art-Net networks.

After receiving a packet, it performs three checks:

1. Is this an ArtDMX packet?
2. Does it belong to the configured universe?
3. Does the monitored DMX value cross the configured threshold?

Only when all three conditions are satisfied does the bridge transmit a TCP command to the NovaStar processor.

The uploaded source summarizes the intended behavior directly:

//takes artnet uni 5 addy 512 and will blackout or enable the novastar 1000 screen controller

The actual control logic is equally compact.

if (packet.raw[529] > 127) {
    if (screenOn == false){
        tcp.write(normal, sizeof(normal));
        screenOn = true;
    }
}
else {
    if (screenOn == true) {
        tcp.write(blackout, sizeof(blackout));
        screenOn = false;
    }
}

Instead of translating every DMX channel, the firmware treats one channel as a trigger. A value above the threshold enables the display, while a lower value issues a blackout command.

This makes the project easy to understand and demonstrates a practical protocol conversion rather than a generic Ethernet example.

Where WIZnet Fits

The WIZnet Ethernet interface is the network foundation of the bridge.

The uploaded project uses the W5x00 Ethernet stack through Ethernet_Generic, EthernetUDP, and EthernetClient, while the repository description specifically references a W5500 Ethernet hat.

Within the architecture, WIZnet performs three essential tasks:

• Connects the MCU to the wired Art-Net network
• Receives incoming UDP lighting packets
• Provides the TCP transport used to communicate with the NovaStar controller

Because the networking layer is handled through the W5x00 Ethernet library, the application logic remains focused on packet parsing and command generation rather than low-level Ethernet implementation.

Source Code Highlights

1. Separate UDP and TCP Communication

File: bridge.ino

EthernetUDP udp;
EthernetClient tcp;

The firmware creates separate network objects for receiving Art-Net packets and transmitting NovaStar commands.

This clean separation reflects the bridge architecture: UDP is dedicated to incoming lighting data, while TCP is reserved for device control.

2. Ethernet Initialization

File: bridge.ino

Ethernet.begin(mac[0], ip);
connect();
udp.begin(ART_NET_PORT);

The initialization sequence performs three actions:

• Starts the Ethernet interface
• Connects to the NovaStar controller
• Opens the Art-Net UDP listener

The order mirrors the runtime requirements of the bridge and keeps network setup straightforward.

3. Universe Filtering

File: bridge.ino

case ART_DMX: {
    if(packet.subUni == 5)
        handleArtnetDMXPacket();
    break;
}

Rather than processing every Art-Net packet on the network, the firmware filters traffic by universe before examining DMX data.

This reduces unnecessary processing and keeps the implementation focused on the intended control channel.

4. NovaStar TCP Connection

File: bridge.ino

if (tcp.connect("2.0.0.10", 5200)) {
    Serial.println("Connected to v1000");
}

The bridge establishes a persistent TCP connection to the NovaStar controller using a fixed IP address and port.

Using a dedicated TCP session simplifies command delivery because the controller is treated as a single known endpoint.

5. W5x00 Ethernet Stack

File: defines.h

#include "Ethernet_Generic.h"

#define SHIELD_TYPE "W5x00 using Ethernet_Generic Library"

This confirms that the networking layer is built around a W5x00-compatible Ethernet interface. Combined with the repository description identifying a W5500 hat, it provides strong evidence that the project targets the W5500 hardware family.

Software Flow

At runtime, the firmware follows a straightforward event-driven sequence.

Power On
    │
Initialize Ethernet
    │
Connect to NovaStar
    │
Listen for Art-Net
    │
Receive UDP Packet
    │
Verify ArtDMX
    │
Verify Universe
    │
Read DMX Trigger
    │
Threshold Check
    │
Send Normal or Blackout TCP Command

The design intentionally avoids unnecessary abstraction. Each received Art-Net packet is inspected once, evaluated against a single control condition, and translated into one predefined NovaStar command.

Related WIZnet Maker Projects

Links

• MoonLight ESP32 DMX Lighting Software
  https://maker.wiznet.io/sophia/projects/moonlight-esp32-dmx-led-lighting-software/
• Dual-Port Art-Net v4 / sACN to DMX512/RDM Node
  https://maker.wiznet.io/viktor/projects/how-to-build-a-dual-port-art-net-v4-sacn-to-dmx512-rdm-node-with-wiznet-w5500-on-esp32-s3/

FAQ

1. Why use a W5500 or W5x00 Ethernet interface for this project?

The bridge depends on a wired Ethernet connection for both Art-Net reception and NovaStar communication. A W5x00 Ethernet interface provides that connectivity while allowing the firmware to use the familiar Arduino Ethernet API.

2. How does the W5500 connect to the Arduino?

The W5500 communicates with the MCU over SPI. The project uses the Ethernet_Generic library together with EthernetUDP and EthernetClient, providing UDP and TCP communication without implementing a custom Ethernet driver.

3. What role does WIZnet play in this project?

WIZnet provides the Ethernet interface used by the bridge. It receives Art-Net packets from the lighting network and delivers TCP commands to the NovaStar controller.

4. Is this project suitable for beginners?

The overall architecture is easy to follow because the codebase is compact. However, understanding Art-Net addressing, IP networking, and NovaStar controller configuration will make implementation significantly easier.

5. Can the bridge be extended beyond blackout control?

Yes. The same architecture can trigger additional NovaStar commands, support multiple universes, monitor several DMX channels, or interface with other Ethernet-based control equipment without changing the overall design.

Source

Repository

novastar_Uno_Interface

Primary Source Files

bridge.ino

defines.h

README.md

LICENSE

License

GNU General Public License v3.0 (according to the uploaded project analysis).

Tags

W5500 • W5x00 • WIZnet • Arduino • Art-Net • DMX • NovaStar • EthernetUDP • EthernetClient • Show Control • LED Display • Protocol Bridge