Integration

Integration Header Image

Here are examples of how MADRIX hardware and software can be integrated into your project.

Different control equipment can simply be connected together nowadays, usually by using a computer network. Connections over USB, XLR, or serial cabling are often still be part of the overall setup. The schematics below show only some of the possibilities. These are not the only options.

You can see more detailed connectivity explanations in the technical manuals available at   help.madrix.com

If you require more information, please contact us at This email address is being protected from spambots. You need JavaScript enabled to view it.

[Ctrl & +/- or Ctrl & Mouse Wheel] = Zoom In/Out / [Ctrl & 0] = 100% / [Right Mouse Click > Open Image In New Tab]

 

How do I connect devices?

 

 

 

 

 

The Basics - Schematic Example 01

Network Basics

 

  • Ethernet is regularly used to connect lighting controllers and devices.
  • Mainly Art-Net / Streaming ACN (sACN / E1.31) is then sent over these computer networks.
  • More devices increase the number of LED fixtures that can be controlled.

 

  • Connect multiple units together by using a network switch.
  • Or you can use daisy-chaining for devices that support it.
  • You can also connect devices directly with each other. A network switch is not necessarily required.
    • You can use regular patch cables for such a direct connection (thanks to Auto MDI-X supported by MADRIX devices). Crossover cabling is not required.

 

  • AURA, LUNA, NEBULA, ORION, and STELLA are all network nodes that support Art-Net / sACN.
    • All of these devices can be connected to the same network in any combination.
    • Nearly all of them support daisy-chaining.

 

  • An outage of a preceding networking device will result in connection failure of all subsequent network devices.
    • This could be network switches, or daisy-chained devices for example, which then affect all following devices.

 

  • Each controller and device in the network needs its own unique IP address.
  • Network devices that should communicate with each other need to have the same subnet mask set in their network settings.

 

  • Network cabling is usually less expensive in comparison and allows you to cover long distances.
    • That means the distance from a controller to devices (such as MADRIX 5 or a lighting console to LUNA) is usually longer than the distance from LUNA to your lighting fixtures over DMX XLR, for example.

 

  • We recommend controlling a maximum of 1024 universes per network card (for a computer running the MADRIX 5 Software).
    • Note: More is theoretically possible.
    • Add more network cards if more universes are required.

 

 

MADRIX ORION Schematic Example 01

MADRIX ORION — Example 01

 

  • MADRIX ORION
    • receives signals and triggers
    • from a variety of equipment, such as
      • analog buttons,
      • optical triggers,
      • sensors,
      • and many more.
  • These triggers, in turn,
    • can be used to remotely control
      • MADRIX 5,
      • MADRIX AURA,
      • or any other compatible Art-Net/sACN controller with support for input.

 

 

MADRIX AURA Schematic Example 01

MADRIX AURA — Example 01

 

  • MADRIX AURA
    • packs the MADRIX effect engine into a small device
    • thanks to stand-alone playback of effects and scenes
    • that have been recorded onto the SD card beforehand.
  • Three MADRIX AURA units are shown here
    • working in Master-Slave Synchronization;
    • all connected together over Ethernet network
    • and each controlling a different part of an overall project:
      • AURA 32 working as master and controlling LUNA 16,
      • AURA 8 working as slave and controlling NEBULA,
      • AURA 2 working as slave and controlling STELLA.

 

 

MADRIX STELLA Schematic Example 01

MADRIX STELLA — Example 01

 

  • The MADRIX 5 Software
    • is controlled remotely
    • via a wall panel that sends (DMX512) data
    • to one MADRIX STELLA unit, which automatically works in input mode.
  • MADRIX 5, in turn, controls
    • a range of DMX LED fixtures
    • by sending output data over Ethernet network
    • to four STELLA units working in output mode.

 

 

MADRIX RADAR Schematic Example 01

MADRIX RADAR — Example 01

 

  • MADRIX RADAR provides
    • 24/7 reliability monitoring
    • of RDM lighting fixtures and hardware nodes
    • based on RDM and Art-Net (ArtRdm).
  • At the same time, MADRIX 5 is used
    • to control the lighting fixtures,
    • which are controlled via DMX512
    • over direct connections from MADRIX STELLA units.

 

 

MADRIX And Pharos Schematic Example 01

MADRIX And Pharos — Example 01

 

  • Pharos provides a native integration to trigger MADRIX AURA.
  • MADRIX AURA 32
    • is used for stand-alone playback,
    • controls four MADRIX NEBULA units, which in turn control an SPI LED tape installation,
    • has its remote-control functions used over Remote HTTP and is getting triggered by Pharos.
  • Pharos LPC
    • is the Pharos controller triggering MADRIX AURA,
    • can receive commands from the Pharos TPS 5 touch-panel interface.
  • Ethernet Network:
    • All systems are connected over an Ethernet network with each other.
  • Pharos can provide:
    • Show Control
    • System Integration
    • Lighting Control
    • Touch Stations
    • Pharos Cloud
  • MADRIX can provide:
    • LED-Lighting Control
    • Small-Scale To Large-Scale Pixel Mapping
    • Stand-Alone Playback
    • Remote Control