# Change a line in the grid

- **MCP resource:** rdmbench://help/line-grid
- **Version:** 0.12.0
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Needs:** An Enttec DMX USB Pro with its DMX/RDM firmware (major version 2), or, on a rig, an Art-Net 4 node with RDM on at its ports
- **Price:** Free

> For macOS only.

How the app sets a whole line's addresses and modes as one plan. What
a plan is, and the same thing from the command line, are in
[Readdress a line in one plan](/help/line-plan/).

To see a whole line set step by step, on the built-in simulator, from
scanning it to putting the units back, watch
[How to re-address a line of fixtures, step by step](https://youtu.be/rzwMhTBWe3M)

Choose **Fixture → Change Addresses and Modes on Line…**, or click
**Change Addresses and Modes…** under **Patch** in the line's report.
The bench reads every chosen unit's list of modes, then shows one row
per unit: where it is now, its address and its mode. Units you have
left alone are not in the grid and are not read. The plan is not
checked against them either, so the header says how many there are.

The grid opens in a window of its own, so the line's report and each
unit's stay open beside it while you work. One plan is open at a time.
Choosing the command again brings its window to the front. Closing the
window cancels the plan, unless it is being sent: then the units go on
being changed, and the command shows the window again. Disconnecting
closes it.

Above the grid is the universe twice, laid out as a console shows a patch:
16 rows of 32 channels. **Current** is on the left and **Proposed**
on the right. Each unit is a run of cells in its own color, with its
grid row number in the first cell. Units that move or change mode are
outlined, and the rest are dimmed. Red cells are channels two units
would both listen on. Point at a unit in either map, or at its row,
to pick it out in both maps and the grid. **Changes only** hides the
rows you have not changed.

Nothing is sent while you edit. Every change is checked against the
rest of the line as you make it:

- an address that would run the unit's channels past 512, for the mode
  it is going to;
- a mode the unit does not list, or one it would not say the channel
  count of;
- two units that would end up on some of the same channels.

A row with a problem gets a red mark. Point at the mark to read the
problem. The same sentences are listed under the grid.

A stack is allowed: units of the same model, in the same mode, on
exactly the same channels, so the console drives them as one. Its cells
are striped rather than red, and the stack is listed under the grid and
on the confirmation so you can check it is meant. A stack of different
models, or of one model in different modes, is refused like any other
overlap. To see it on the built-in simulator, watch [Run several fixtures as one? Stack them on one address.](https://youtu.be/E13GmKh4qeY)

A mode with fewer or more channels leaves a gap after the unit, or
runs it into the next one. Turn on **Move the units after a mode
change** and picking a mode moves every unit placed after that unit by
the difference. A unit going from 25 channels to 14 brings the rest 11
nearer, and the gaps between them stay as they were. Units before it,
or on the same address, do not move. The option is off each time the
grid opens, and ⌘Z puts the whole change back. To see it on the
built-in simulator, watch [Change every fixture's mode without breaking the patch](https://youtu.be/Rq5DZwnCAJA)

## Moving a block on the map

You can also set an address on the **Proposed** map. Drag a block,
picking it up by any of its cells, and let go where you want it. The
address is the channel its first cell lands on. A block that runs off
the end of a row carries on at the start of the next, because an
address is a channel number. The address field changes as you drag,
and each step is checked as if you had typed it, so red cells and
problems show while the block is still moving. A block dropped where
it does not fit stays there, with the problem marked, until you move
it again. Dragging changes the address only. Change the mode in the
grid. To see it on the built-in simulator, with the keyboard's route
below, watch [How to lay out a DMX patch by dragging fixtures](https://youtu.be/55tNnZRh3Bk)

A stack moves as one. Pick up a striped block and every unit in the
stack comes with it, so you can readdress all of them at once. Hold ⌥
as you drag or click to take one unit out of the stack instead. Typing
in one row's address field moves that unit only.

From the keyboard, click a block, or press Tab until the map is
selected. Then press Tab to go from block to block; a stack is one
stop. The one you are on gets a ring in both maps and on its grid row,
or on every row of its stack.

- ← and → move it one channel.
- ↑ and ↓ move it one row of 32.
- ⇧← and ⇧→ move it flush against the next block that way, or
  against the start or end of the universe.
- Return or Esc lets go of it.

With VoiceOver, each block on the map is one item, and a stack is one
block, read as "rows 2 to 9, a stack of 8". Press VO‑⌘‑Space on a block
to open its actions menu, which moves it a channel or a row either way,
or flush against the unit before or after it. VO‑↑ and VO‑↓ do not move
a block. A block you click or Tab to brings VoiceOver's cursor with it,
and the arrow keys above work as well. Each move is read out with the
grid row, the name, the new channels and any channels it now shares,
such as "row 12, AURA-18, 166 to 179, overlaps row 13 on 175 to 179".
VoiceOver's cursor stays drawn on the cells the block has left until you
next move the cursor, so go by what is read out.

⌘Z undoes a drag. All the moves you make with
the keys before letting go undo together. Nothing is sent from the
map. As with typing, nothing goes to the line until **Continue…** and
the confirmation.

## Applying it

**Continue…** lists every change as from → to, with both maps above.
Nothing is sent until you click **Change**. The bench then goes through
the units one at a time. For each unit it reads the unit again, sets
the mode and then the address, and reads each one back. The progress
bar says which unit it is on, and **Stop** sends nothing after that
unit.

The plan stops at the first unit that does not take its change: a
locked unit, one that refuses it, one that reads back something else,
or one that does not answer. It was checked on the assumption that
every unit moves, and a unit left where it was may now be where a later
one was going. The units already changed stay changed, and the bench
says the line is half changed. A unit changed at its own menu since the
grid was opened is not sent anything, and the plan stops there too. To
see it on the built-in simulator, watch [Re-address stopped halfway? See which fixtures moved.](https://youtu.be/k6raXeslu1w)

Afterwards the right-hand map shows what the line **reads back**, so a
unit that did not take its change shows where it really is. Every unit
the plan changed is read again, and the line's findings are run again.

## Putting them back

**Put Them Back…** puts every unit a plan has changed back where it
was before the first plan. It is in the results and under **Patch**
until you disconnect. It goes through the same check and confirmation
as any plan, with one difference. If units shared channels before the
first plan (units all on address 1, say), putting them back puts them on the same channels again. The confirmation lists
those overlaps, and they do not stop it.

The action is unavailable while levels are held with Send DMX, during
a load test, a channel walk, a mode sweep or monitoring. Each of those
is placed by the units' addresses. With the grid open, you can still
start one of them from the main window, but the plan is not sent until
it has finished: the confirmation says what is in the way. While a
plan is being sent, the main window waits for it.

If you change a unit's address or mode from its own report while the
grid is open, the grid reads the line again and checks what you have
typed against where the units are now.
