Skip to main content

Link, check and set up controllers from a Pixel Designer import

Updated Nov 15, 2026
9 Views

ELM (ENTTEC LED Mapper) 2026 version 26.11.15, released on 15 November 2026, carries a Pixel Designer import through to the hardware on site. It lists the controllers a show needs, lets you link each one to a unit on the network, and checks it against the design. This article explains that workflow in detail and then summarises the other changes since 26.10.16. It is written for installers, integrators and designers commissioning pixel shows.

What's new: from Pixel Designer to a working installation

Pixel Designer (pixeldesigner.enttec.com) is ENTTEC's free online tool for designing pixel installations. ELM already imported a design's layout and patch. From 26.11.15 the import also brings in the controllers.

1. Import the design and read the summary

When you import a Pixel Designer design, ELM lists every controller the show needs in Device manager › Project. Each one is shown as "waiting for its hardware". The example below is public design PXD-SQDFV, which adds 4 × OCTO MK3.

The import summary states what was created: the stage, the patch (pixels and universes), the controllers, and the Sentry alert rule.

ELM dialog showing a Pixel Designer import adding four OCTO MK3 controllers to Device manager.

Import summary for design PXD-SQDFV: 732 strings, 12,444 pixels on 106 universes, and 4 × OCTO MK3 added to Device manager › Project.

Open Device manager › Project to see the controller list. You can read it before you travel, so you know which controllers to set up and what each must do.

ELM Device manager Project tab with four OCTO MK3 controllers waiting for hardware.

Device manager › Project listing four OCTO MK3 controllers, c1 to c4, each marked "Waiting for hardware, Required by this project", with Link a unit and Show settings to enter buttons.

2. Link each controller to its unit

Each controller in the design has a name such as c1 or c2. In Device manager › Project, pick the physical unit on the network that is that controller. Repeat for every controller in the list.

Linking means you do not have to retype the patch by hand, which cuts down on typing errors during commissioning.

3. Set up the controller

What happens next depends on the controller model.

  • ELM configures it: DIN Ethergate and Storm nodes. ELM applies the settings itself.
  • ELM shows the settings, you enter them: OCTO and Pixelator. ELM cannot yet configure these. It shows the exact settings to enter on the controller's own web page.

The settings ELM shows for OCTO and Pixelator are:

  • Input protocol
  • IP address
  • For each output: pixel type
  • For each output: pixel count
  • For each output: universes
  • For each output: colour order
  • For each output: bit depth

To see them, use Show settings to enter beside the controller in Device manager › Project.

4. Check the controller against the design

ELM reads what each unit reports over Art-Net and compares it with the design. It also keeps the show's output pointed at each controller's address.

If a controller is "listening on the wrong universes", ELM flags it per output. For example: "Output 3: not listening to universe(s) 48–54". This catches the common fault where one section of a show displays the wrong content, before the client sees it.

Because the check uses what the unit itself reports, it works for any Art-Net controller, including models ELM cannot configure.

ELM Device manager showing one controller flagged for wrong universes while three others are Ready.

Simulated controllers: no hardware was connected when this screenshot was taken. The screens, wording and checks are the real app's. Three controllers are Ready and one is flagged, with Output 3 and Output 4 reported as not listening to universes 48–54 and 56–62, alongside the settings to enter.

Controller statuses

Each controller in Device manager › Project shows one of five statuses:

  • Ready
  • Needs setup
  • Mismatch
  • Offline
  • Waiting

What ELM configures and what it only checks

  • Configures and checks: DIN Ethergate and Storm.
  • Shows settings to enter, then checks: OCTO and Pixelator.
  • Checks only, using the unit's own Art-Net report: any other Art-Net controller.

5. Sentry offline alert

Sentry alerts you when a controller belonging to the show goes offline. The import adds the alert rule automatically. A controller that has not yet been linked to a unit never raises an alarm.

ELM Device manager and Sentry notification showing an OCTO MK3 controller offline.

Simulated controllers: no hardware was connected. All four OCTO MK3 controllers show Offline, with a Sentry notification that the gateway OCTO MK3 is not responding to Art-Net.

What's new: 3D designs import as a 3D stage

A 3D design from Pixel Designer now imports as a real 3D stage. A pixel Christmas tree arrives as a cone, so 3D effects play across its actual shape "instead of across a flat fan". Earlier versions unrolled it flat.

The example is public design PXD-0BS5V: 64 strings, 976 pixels, 16 universes and 1 × OCTO MK3. The import summary reads "64 strings at the designed positions (3D)".

ELM import summary for a 3D Christmas tree design: 64 strings, 976 pixels, 16 universes and one OCTO MK3. ELM 3D stages view of a Christmas tree design shown as a cone of cyan and magenta pixel strings.

The tree as a 3D cone. The effect is projected across the cone from the front. It follows the true 3D shape but does not wrap around the tree.

What's new: schedules that end at a set time

Under Ends, choose Until to run a schedule from one time to another instead of working out a duration. Examples: 18:00 until 23:30, or Sunset until Sunrise. ELM calculates the duration and handles a show that runs past midnight. This suits permanent installations such as façades, hospitality, retail and landmarks.

The Schedule tab also shows the current time, today's sunrise and sunset, and when the schedule next starts, for example "Starts at 5:31 PM (in 5 h 54 min)". You no longer need to open Settings for this.

ELM schedule settings set to run from sunset until sunrise, with today's sunrise, sunset and next start time.

What's new: other additions

  • Graphics card choice on laptops. On a laptop with two graphics cards, ELM now requests the fast card from Windows, so it no longer runs on the slower built-in graphics. This takes effect the next time ELM opens. Under Settings › Benchmark › Graphics card you can choose High performance (recommended), Power saving or Let Windows decide. The section also shows which card ELM is actually using.
  • Automatic unicast for Art-Net. Each universe is sent only to the nodes that use it, which reduces network traffic on large rigs and shared networks. It is on by default in new projects. Existing projects can enable it in the Art-Net settings.
  • Beat detection: Detection speed. Fast follows a change of tempo within a few seconds. Steady, the default, holds the tempo through breaks.

Improvements and fixes

Benchmark

Settings › Benchmark now rates the computer and the project on one six-level scale: Basic, Small, Medium, Large, Very large, Extreme. It shows:

  • where this computer sits on the scale, and where the project sits;
  • what runs out first (for example the processor or the network card), with advice on what would help;
  • how each network card you tick keeps up.

The test plays reference shows with everything running at once. A level only counts if it runs smoothly: no more than 2 frames in 100 late, and no freeze longer than 0.25 seconds.

The show pauses while a benchmark test runs, so the test has the computer to itself. ELM asks first if a show is playing. Benchmark results no longer vary widely between runs when testing with Loopback.

ELM Benchmark settings showing the six-level scale and the graphics card choice.

Benchmark scale, network card list and Graphics card option. The result shown comes from one development PC and is not a specification.

Output

  • 16-bit fixtures now use the full 16-bit range, for smoother fades and low dim levels.

Fixes

  • Universes assigned to other network cards output again in Single mode. They had been leaving via the main card.
  • Universes on other network cards keep their card after RDM, the nodes view or network recovery.
  • Schedules restored after a restart end on time, with no full or late replay. An overnight schedule continues into an unticked day after a restart.
  • Slide, zoom, rotate and flip transitions in sequences play in the chosen direction.
  • Sentry checks every device before it calls a poll finished.
  • The ELM Server Benchmark now reports what the server can really run. It previously reported far less.
  • Layout: table column headings are always readable, "Test patterns" on the 2D Testing tab is no longer cut off, and the "Sequences" and "Columns" labels in Edit sequences no longer overlap.

Upgrade notes

  • Version number: the release is 26.11.15. The app and the update feed show it as 26.1115.1.
  • ELM desktop: offered as an automatic in-app update.
  • New installs: use the ELM installer from ENTTEC's download page.
  • ELM Server: uses a separate installer and does not update automatically.
  • China: available from the ENTTEC China download mirror on the same day, 15 November 2026.
  • Graphics card setting: the change takes effect the next time ELM opens.
  • Automatic unicast: on by default in new projects. Existing projects must enable it in the Art-Net settings.
  • Controller setup: ELM cannot yet configure OCTO or Pixelator. It configures DIN Ethergate and Storm only. For OCTO and Pixelator, enter the settings ELM shows on the controller's web page.
  • Testing: nearly all of these changes were available in ELM Preview from 4 November 2026.

Download

ELM desktop users: open ELM and accept the update when it is offered. New installs: download the ELM installer from ENTTEC's download page. To design an installation to import, use Pixel Designer.

Was this article helpful?

Let us know if this article helped answer your question.

You can only submit feedback once per article.

Thank you for your feedback!

Your input helps us improve our knowledge base.