DMX Universe Channel Address Planner Tool

Plan actual contiguous DMX fixture footprints without crossing 512-channel universe boundaries, honoring start address/universe budget; not generic pixel-map capacity, reserved-address reconciliation, fixture personality inference or hardware patch write.

Description

DMX patch planning assigns contiguous fixture footprints within 512-channel universes.

DMX patch planning assigns contiguous fixture footprints within 512-channel universes. A fixture cannot span a universe boundary in this model.^[1]

Enter aligned nonempty unique fixture IDs/integer footprints 1–512, universes 1–63999 with maximum≥first and address 1–512. Preserve fixture order; return universe/start/end arrays and skipped tails before changes. Exceeding the universe budget fails.

When to use DMX Universe Channel Address Planner Tool

Use DMX Universe Channel Address Planner Tool when you need to evaluate the supplied records under the calculation and evidence rules below. No reserved addresses, personality inference or hardware patch is written.

Prepare the actual venue, production, inventory or financial records requested. Confirm units and supply applicable local limits or verified catalog values.

How to use DMX Universe Channel Address Planner Tool and understand its results

Prepare the actual venue, production, inventory or financial records requested. Confirm units and supply applicable local limits or verified catalog values.
Enter fixtureIds, fixtureFootprintsChannels, firstUniverse, firstAddress, callerMaximumUniverse using the field table and calculation rules, then run the tool.
Read assignedUniverses, assignedStartAddresses, assignedEndAddresses, unusedTailChannelsBeforeUniverseChanges. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
fixtureIds	Fixture ids	list of string	Required
fixtureFootprintsChannels	Fixture footprints channels	list of number	Required
firstUniverse	First universe	number	Required
firstAddress	First address	number	Required
callerMaximumUniverse	Caller maximum universe	number	Required

if start+footprint−1>512: nextUniverse, address1

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
assignedUniverses	Assigned universes	list of number
assignedStartAddresses	Assigned start addresses	list of number
assignedEndAddresses	Assigned end addresses	list of number
unusedTailChannelsBeforeUniverseChanges	Unused tail channels before universe changes	number

json

{
  "input": {
    "fixtureIds": [
      "a",
      "b",
      "c"
    ],
    "fixtureFootprintsChannels": [
      300,
      300,
      20
    ],
    "firstUniverse": 1,
    "firstAddress": 1,
    "callerMaximumUniverse": 2
  },
  "output": {
    "assignedUniverses": [
      1,
      2,
      2
    ],
    "assignedStartAddresses": [
      1,
      1,
      301
    ],
    "assignedEndAddresses": [
      300,
      300,
      320
    ],
    "unusedTailChannelsBeforeUniverseChanges": 212
  }
}

Limitations and assumptions

No reserved addresses, personality inference or hardware patch is written.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Kabuki Drop Solenoid Release Line Count Tool: Release-point inventories identify which points depend on each circuit. Recorded release evidence is separate from physical synchronization. For a complementary task, use Cue Light System Stations Wiring Loop Lookup: Cue-light station evidence can show known channel mismatches or missing observations. The two states need separate outputs.

References

DMX Universe Channel Address Planner Tool — tool.io

Similar or alternative tools

Kabuki Drop Solenoid Release Line Count Tool
Release-point inventories identify which points depend on each circuit. Recorded release evidence is separate from physical synchronization.
Cue Light System Stations Wiring Loop Lookup
Cue-light station evidence can show known channel mismatches or missing observations. The two states need separate outputs.