Introduction: ILDA sends X, Y and color data as differential voltages over one cable per projector, while network control delivers show data to addressed nodes and rewires the rig.
Put eight RGB moving head lasers across a wide stage and the visual question quickly turns into a wiring question. Someone has to get scan data to every one of those fixtures, and there are two very different ways to do it: the classic analog ILDA chain, and network control, where each projector becomes an addressed node on an Ethernet show network. The two routes differ in a way that has nothing to do with brand or build quality. They differ in topology — where the scan data is created, how it travels, and how each projector knows which part of the show belongs to it. That difference shapes the cable schedule, the way fixtures are identified, and how easily a rig can be rebuilt in a new venue.
The ILDA standard interface is a 25-pin connection built around a simple idea: the controller computes the scan, and the projector obeys. Its pin assignments carry X and Y deflection commands for the two galvanometer mirrors, red, green and blue intensity levels, plus shutter, blanking and interlock lines, each with its own dedicated conductor pair. Deflection arrives as an analog voltage, and on a fixture like the A17 that voltage sits inside a ±5V window that maps onto mirror movement across a scan angle of up to ±30°. Color works the same way: one analog voltage per laser channel sets how hard each diode fires, which is why an ILDA feed produces continuous fades instead of stepped color changes. What makes that analog chain survive a real stage is differential signaling. Every signal travels as a matched pair, one conductor carrying the positive version and the other an inverted copy, and the receiver reads only the difference between them. Noise picked up along the cable — from dimmers, motors and power runs — tends to appear on both conductors equally, so it cancels out at the input. Mirror position and color levels therefore stay faithful to what the controller intended, even when the cable snakes past a lot of electrical activity. The trade-off is that an ILDA link is point-to-point. One port drives one projector, and the entire show is generated upstream by the show computer and its digital-to-analog converter. Ten fixtures need ten ports, or a splitter and amplifier stage to fan the same signal out. The A17 lists both a 25DB ILDA port and an easy ILDA port, so the analog route stays available alongside its other connections — useful when an operator wants a direct signal chain, or when an existing control setup already speaks that language.
Network control moves the point where data becomes motion. Instead of a controller producing analog voltages for a single projector, show data travels over Ethernet to a node inside or attached to each fixture, and that node generates the scan and color signals locally. The wiring logic flips as a result: rather than one long run per projector back to the control position, a single data feed reaches a switch on or near the stage, and every fixture takes a short network connection from there. Adding another unit becomes a matter of a free port and an address, not another 25-pin cable pulled across the venue. Addressing is where the topology really changes shape. In an ILDA chain, a projector's identity is physical — the cable plugged into port three belongs to the fixture hanging at the end of that cable, and moving the fixture means re-patching at the controller. On a network, identity is logical. Each node has an address, and the show engine sends the correct data to the correct address, so a projector can be re-hung on another truss position and still perform exactly as before. For touring rigs rebuilt in a different layout every few days, that is the difference between a quick address check and an evening of cable routing. Media serving relocates too. A network layout can stream every frame from a central server, or it can let each node hold its own content and fire cues on command. Many network-ready fixtures ship with built-in pattern and animation libraries for exactly that reason: the A17 carries 140 patterns and 20 animation cues, along with an Art-net port and an optional built-in Pangolin FB4 board, so one fixture can play stored content on its own or follow a networked media server. On a large array both habits are useful, and the fixture count stops dictating how many long cables have to reach the control position.
The two approaches look almost identical from the truss, but they behave differently in the cable schedule, because one carries analog levels that must stay accurate while the other carries data that can be rebuilt at every hop. Four details change most.
None of this makes one route automatically better. A rig with two projectors close to the control position is simple on ILDA; a rig with fixtures on four trusses and a layout that changes every week is usually tidier on a network. Real behavior still depends on fixture firmware, switch configuration, cable quality and the way the show network is laid out, which is why a short test of the actual signal chain before a big date is worth the time.
The real question is not which interface is newer but where scan data is created and how many long cables the rig can tolerate. ILDA gives a direct analog path with one timing source and a signal chain that is easy to trace, which suits smaller or fixed setups. Network control spreads the work across addressed nodes, which suits arrays that grow, move and get re-patched. Both topologies can live on the same fixture: the A17 provides 25DB ILDA, easy ILDA, Art-net and an optional built-in Pangolin FB4, so the way a rig is wired can follow the show instead of the other way around. Comparing a fixture's interface list against the cable plan is a practical first step.
A：ILDA delivers X, Y and color as analog differential voltages from a controller to one projector per port, so the whole scan is computed upstream. Network control sends show data over Ethernet to an addressed node inside each fixture, and that node builds the scan and color signals locally. One is a point-to-point analog chain; the other is a distributed data network.
A：It usually wins when fixtures are spread across several trusses or sit far from the control position, and when the rig is rebuilt often. One data feed to a stage switch, a short cable per fixture and addresses that survive re-hanging keep the patch simple. On a two-projector rig close to the controller, an ILDA chain is often the easier plan.
A：For the fixtures that have it, yes. A projector with a built-in Pangolin FB4 board receives show data over the network and drives its own scanners, so it no longer depends on a 25-pin analog feed. Mixed arrays are common, with some units on ILDA and networked units working from their own addresses.
hardware: ILDA connector — Pangolin Complete Help Docs
FB4 interface — Pangolin Complete Help Docs
ESTA Technical Standards Program — Published Documents
