Two tender drawings show a controller connected to six masts. One uses a line that passes each mast in turn. The other brings every route back to the control room. Calling the first economical and the second reliable is tempting, but incomplete. The right answer depends on which cables the lines represent.
A lighting wiring topology describes connections, not just geometry on a page. Power distribution, a DALI bus, a DMX segment and an Ethernet backbone obey different constraints. They may share trenches while requiring different electrical arrangements, equipment and failure tests.
Should a Large Project Use Daisy Chain or Star?
Use a protocol-appropriate layout, then divide the installation into manageable fault and service areas. Conventional DMX segments use a daisy-chain arrangement; properly selected active distribution can create separate branches. DALI permits flexible wiring within its limits. Switched Ethernet commonly supports star-like distribution, but its design is not a substitute for either lighting bus.
The best lighting wiring topology may therefore be a hybrid: a backbone serving local controllers, followed by short protocol-compliant branches. Whether that is justified depends on distances, available routes, equipment access and the operational consequences of a fault.
| Connection type | Planning approach | Avoid assuming |
|---|---|---|
| DMX segment | Line arrangement with appropriate termination; active distribution for branches | A passive Y connection is equivalent to a splitter |
| DALI bus | Flexible arrangement within device, current and cable limits | Free topology means unlimited distances or devices |
| Ethernet backbone | Designed switched network with appropriate links and management | An RJ45 socket proves the signal is Ethernet |
| Power circuits | Electrical design based on loads, routes and protection | A data daisy chain means series-connected luminaires |
| Remote driver outputs | Driver-specific cable design | Control-bus limits also apply to LED output cables |
Draw the System in Separate Layers
Begin with a physical route plan showing ducts, pits, buildings, masts and service access. Then prepare separate views of power distribution and control connections. Add a logical map for groups, scenes and device addresses. Combining everything into one line diagram often hides important differences.
A control group may include fittings on several circuits. A circuit may power fittings assigned to different scenes. Maintenance staff need both maps. Otherwise an operator may think a software group identifies the equipment isolated by a physical switch, which is not a safe assumption.
For separated drivers, show the connection from each driver to its LED load independently from the control bus. Label cable types and approved routes without treating them as interchangeable. The driver’s output-cable requirements need confirmation for the selected equipment.
Ask every bidder to use a common drawing legend. A simple line labeled “control” is insufficient when different protocols or media appear in the same project. Clear labels make quotation differences visible before they become installation changes.
DMX: A Branch Needs the Right Distribution Equipment
ETC’s DMX guidance describes daisy chaining rather than passive Y-splitting, and termination at the end of a line. These are signal-integrity considerations, not simply preferences about cable tidiness.
Where the site calls for several outgoing routes, specify a suitable active splitter or distribution arrangement. Each resulting segment needs its own design. Confirm compatibility with RDM if the project requires that additional functionality.
Do not confuse an active branch with guaranteed redundancy. A common splitter or its power supply may still be a shared dependency. Its failure behavior should be part of the review, particularly where several masts depend on the same device.
In a lighting wiring topology comparison, draw the active equipment explicitly and include it in the bill of materials. A star-shaped diagram that omits the necessary distribution hardware can make an incomplete proposal appear cheaper than a properly designed one.
DALI: Flexible Routing Still Has Boundaries
The DALI Alliance permits flexible bus wiring. Its cable-length note gives a recommended maximum distance of 300 m between devices under stated conductor and bus-supply conditions. Treat that as a conditional design guideline, not a general permission for every outdoor cable route.
Count the actual control gear, not only the luminaire housings. A large fitting may contain more than one addressable driver. Confirm the proposed addressing and bus load with the selected components instead of estimating capacity from the number of poles.
Record the electrical route distance, including rises, cabinet entries and deviations around existing infrastructure. A straight-line distance on a site plan can understate the installed cable length. Leave the designer enough information to evaluate the real route.
Flexible wiring can make construction easier, but fault isolation still deserves thought. Provide accessible branch information and a documented test method. A tree-shaped bus with unlabelled junctions may be difficult to investigate even if its original operation was satisfactory.
Keep the Backbone and Lighting Bus Distinct
A large venue may use Ethernet between a control room and local gateways, then DALI or DMX from each gateway to luminaires. The backbone transports information between network devices; the local gateway provides the interface to the lighting segment.
ETC’s network-topology guidance discusses star arrangements for its entertainment control networks. That guidance should not be read as permission to wire a DMX electrical segment into a passive star.
Likewise, connector shape does not establish protocol. Identify what signal each port carries and use the equipment manufacturer’s cabling instructions. A connector that fits is not evidence of electrical or network compatibility.
Where long outdoor links or electrical separation are concerns, ask the network designer to assess suitable media, including fiber where appropriate. Fiber does not remove the need for power, environmental protection and maintenance of equipment at each end.
Compare the Consequences of a Fault
Reliability cannot be reduced to line versus star. A star may localize a branch cable fault but concentrate dependence on a central switch or controller. A line can reduce cable routes while creating different downstream dependencies. Actual behavior also depends on device design and where the fault occurs.
Use a hypothetical six-mast stadium to ask concrete questions. What happens if one branch cable is damaged? What if a local gateway loses power? What if the central controller restarts? Which normal scenes remain available, and what does the operator see?
The proposed lighting wiring topology should make those answers legible. Mark shared dependencies and identify any approved local fallback. Do not label a drawing resilient simply because it contains two lines; they may occupy the same vulnerable trench or rely on the same supply.
Separate normal-service resilience from emergency-lighting design. Maintaining a control path after a network fault is not the same as providing an independently designed emergency lighting function. Each requirement needs its own evidence.
Price Cable Routes, Equipment and Maintenance Together
Cable length is an important cost, but not the whole installed cost. Civil work, junctions, termination labor, active equipment, protected locations and commissioning all affect the comparison. A longer route through an existing duct may be less disruptive than a shorter route requiring new excavation.
Ask bidders to identify where their assumptions differ. One may include local cabinets while another assumes space and power already exist at each mast. Without a common scope, the price comparison is not measuring topology alone.
Think about maintenance visits as well as construction. A central service location may be convenient, but excessive concentration can complicate thermal design or create a large failure area. Distributed equipment can shorten local cable runs while adding more locations to inspect.
For expansion, reserve defined resources: routes, ports, addresses, power and enclosure capacity. Spare duct is useful but does not automatically create spare controller capacity. Record which future additions the installed design can accommodate and which require further engineering.
Make the Installed Route Traceable
Label both ends of cables and identify accessible junction points. Keep the labels consistent with the asset register and drawings. A fault investigation should not begin with guessing which of several identical cables serves the north mast.
Record changes made during construction. Moving a route to avoid a drain, adding an enclosure or changing a gateway location can affect distance and maintenance access. As-built documentation should describe the installation, not simply repeat the approved drawing issued before excavation.
For a lighting wiring topology handover, include termination locations, distribution equipment, port assignments and configuration references. Keep the electrical isolation information separate but cross-referenced. Only qualified personnel should perform electrical testing and intervention using approved procedures.
Do not use operating success as the sole cable test. A marginal connection can appear acceptable during a short demonstration. Specify the inspection and testing appropriate to each medium and protocol, and keep the results with the project record.
Coordinate FL09 Drivers With the Control Architecture
ZC’s FL09 documentation describes digital control configurations and driver installation options on brackets, poles and in cabinets. These options let the design team compare service access and equipment placement, but the approved arrangement still depends on the selected driver and project layout.
Request a schedule linking every FL09 fitting to its driver, control address, circuit and physical location. If several driver channels or addresses are involved, show them explicitly. Do not assume one housing corresponds to one control address or one software channel.
For remote driver installations, obtain written confirmation of the permitted output-cable arrangement. The distance rules for DALI, DMX or Ethernet do not establish how far a particular LED driver can be placed from its load.
Send ZC the route plan and the proposed controller details with the RFQ. Ask the integrator to identify any gateways, splitters, interface options or commissioning tools required. This prevents a luminaire supply scope from being mistaken for a complete control network.
For Retrofits, Survey the Existing Routes Before Promising Reuse
An existing duct can be valuable, but its presence on an old drawing is not proof that it is available. Confirm its route, access points, condition and usable capacity through an appropriate survey. Record where access is uncertain instead of pricing the project as though every route were clear.
Identify the installed cable and its original purpose. A cable that carried an older control system should not be assumed suitable for the new protocol. The responsible designer needs its construction, length, condition and termination details before approving reuse.
Plan the changeover around venue availability. A phased replacement may temporarily leave old and new controls operating in different areas. Define who controls each area, how staff distinguish the interfaces and what configuration is permitted during the transition.
Keep a rollback plan for the commissioning window where practical. If the new control path cannot be accepted that evening, the owner should know which operating options remain. This is an operational planning exercise, not permission to bypass protection or improvise temporary electrical connections.
For a hypothetical multi-pitch club, upgrading one pitch first may reveal route and handover issues before the remaining pitches are affected. However, the pilot route should be representative. Testing only the shortest and easiest branch says little about a distant mast with different infrastructure.
Attach the survey findings to the quotation comparison. Otherwise one bidder may price verified routes while another assumes complete reuse, creating an apparent saving that disappears during construction. Clear assumptions make the commercial comparison more honest and reduce disputes over additional work.
Test the Drawing Against Real Failure Scenarios
Use planned, safe tests to verify representative branches. Demonstrate normal scenes, a controlled communication interruption, restart behavior and recovery from a saved configuration. Record the actual outcome instead of assuming the design’s intended behavior was achieved.
Have the operator identify the affected area from the interface and the maintenance team locate it using the drawings. This checks the connection between the logical and physical maps. It also reveals whether faults create a clear alarm or only leave stale status information behind.
Approve a lighting wiring topology only when the routes, equipment and responsibilities form a coherent system. The answer may be a line, a star or a hybrid, but it should be supported by protocol rules and a service plan rather than a slogan about reliability.
Frequently Asked Questions
Can DMX use a star layout?
A system can distribute DMX into separate branches using suitable active equipment. That is different from passively joining several cables into a Y or star. Each segment must follow the relevant equipment and termination requirements.
Does DALI allow unlimited branch lengths?
No. Flexible wiring does not remove distance, electrical or device-capacity limits. Evaluate the actual cable routes, conductor details, bus supply and connected equipment against the applicable guidance and manufacturer instructions.
Is a daisy chain the same as series-connected power?
No. The term may describe the control-data route rather than the luminaire power arrangement. Draw and label power distribution separately, and have the electrical design reviewed by qualified personnel.
What should an FL09 wiring enquiry include?
Provide mast locations, realistic routes, driver positions, proposed controllers, operating groups and required failure behavior. Request a configuration-specific wiring proposal, including the approved driver-to-LED cable arrangement and all necessary control interfaces.