The topology view looks wrong
The Device Topology draws each DMX line of an Art-Net node as a chain of fixtures in cable order. KLSTR.ctrl only knows that order thanks to the KLSTR.nano modules on the line: during discovery, it asks every nano which fixture sits behind it and which nano comes next. Where that information is missing, KLSTR.ctrl still lists the fixture, but can't place it on the cable. It then draws it in a group box, or at the start of the line. This page explains the usual reasons and what to do about them.
Fixtures are in a group box instead of a chain
What you see. Several fixtures sit together in a box, joined to the line by a grey link. The box has a small arrow button in its corner (Collapse group or Expand group), and shows how many fixtures it holds when collapsed.
Why. A group means: these fixtures are on this line, but KLSTR.ctrl doesn't know their order. That is normal for RDM fixtures without a KLSTR.nano inside (they have a dotted border): nothing on the line can tell where they are. KLSTR.ctrl puts them together in front of the fixtures it can place.
When fixtures with a KLSTR.nano end up in a group, the topology discovery on that line didn't get through. Check these, in this order:
- Perform topology discovery is on in User settings › RDM. Switched off, KLSTR.ctrl runs a standard RDM discovery only and can't order the line. See Settings: RDM.
- The node accepts RDM from your computer. Some Art-Net nodes accept RDM only from one
controller IP address, set in their DMX or RDM settings (for example the RDM controller
IP of a LumiNode process engine). If that address is not your computer's, the node drops
the commands KLSTR.ctrl uses to map the line, while the node itself still shows up fine. Set
it to
0.0.0.0(any controller) or to your computer's IP address, in the node's own web interface. - The DMX line is healthy. A long line, a missing terminator or a splitter that doesn't pass RDM can lose the replies. Fix the line, then discover again.
Then run RDM discovery on that port again: click the discovery icon in the port's box in the Device Topology. See Discover devices.
Fixtures are in the wrong order
| What you see | Likely cause | What to do |
|---|---|---|
| A fixture without a KLSTR.nano is drawn at the start of the line, although it hangs further down the cable | KLSTR.ctrl can't know where a fixture without a nano sits, so it draws it in front | Nothing to fix. The order of the nano fixtures is still right |
| You recabled the line, and the old order is still shown | The drawing is from the last discovery | Run RDM discovery on that port again |
Fixtures you removed are still there
When a fixture stops answering, KLSTR.ctrl doesn't remove it: it marks it offline (red border) and keeps it in its last place, so you notice what went missing. After you recable or swap fixtures, those offline fixtures stay in the view next to the new ones.
To start from a clean picture, choose View › Reload (press CmdR on macOS, Ctrl R on Windows). KLSTR.ctrl forgets every discovered device and finds them again. If you ticked Remember interface, it reconnects to your interfaces by itself; otherwise select them again. KLSTR.one fixtures then come back by themselves. Run RDM discovery again for the fixtures behind Art-Net nodes.
Nodes overlap or the layout is a mess
| What you see | Likely cause | What to do |
|---|---|---|
| Nodes overlap after a large discovery | Devices were added one by one while the view was being laid out | Press d or click Auto distribute to lay out the view again. In the Network Topology, clear the selection first (press Esc), otherwise only the selected nodes are distributed |
| After rediscovery, nodes jump back to their automatic place | Their position wasn't saved to the device, or the device can't store one (Art-Net node, switch, RDM fixture without a KLSTR.nano) | Arrange them again and click Save positions |
| The view keeps refitting while devices are found | Auto-fit view on new device discovery is on | Switch it off on the VIEW tab of User settings |
| Some nodes look faded | They don't match the search or filter in the sidebar | Clear the filter. See Find devices with the sidebar |
| An Art-Net node without fixtures is missing | The node is hidden: it was disabled and Hide disabled nodes is on | See Disable and hide Art-Net nodes |
Related
Written for KLSTR.ctrl 1.2.0 (a0df909) · Checked 1 Oct 2026
macOS blocks local network access
Recognise and fix the macOS Local Network permission problem that makes KLSTR.one fixtures show offline although they are reachable.
RDM data or sensors are missing
What to do when RDM fixtures show no sensor readings, no DMX mode list or no device information after discovery.