Nashville, TN 37207
(615) 904-5640
kenny@kg3.io
Power & Data Plan · beabadoobee 2026
Data & power flow: how to read these diagrams
Data and power both originate at the pylon. Every run's PXL-CTRL is the single source of data for that run and the first source of power. Data leaves the controller once and travels through the rope itself, segment to segment on the 3-core lead, passing every drop untouched. That is the yellow line.
Every PWR-NJCT is power only. It takes powerCON TRUE1 up to the box and feeds the rope it hangs over through our own drop. Nothing else lands on it. The winch is rigging only, nothing electrical rides the winch line: on DS/US the power drop comes down at the winch pickup; on the audience APs (chain motors, static) it is a fixed cable on the black pickup cable. No data enters it, no data leaves it. That is the red drop.
Where the power actually lands: the drop comes down the pickup to the rope, then a Wye feeds it into the LED. Red arrows on each diagram show which way each feed runs. A mid-rope injector feeds both directions, landing on the end of the segment arriving at it and the beginning of the segment leaving it. An injector at the last pickup has nowhere forward to go, so it feeds back one direction only. Beginning and end are defined by data flow, not by stage geography: the end of a segment is the end the data leaves by.
On screen the flows animate: a pulse travels the yellow data line from the controller out through the rope. The PDF shows the same paths held still.
| Box | Position | Data in | Data out | Power in | Power out |
|---|---|---|---|---|---|
| PXL-CTRL | Pylon rack (deck at the pylon base) | Cat5 / etherCON, sACN or Art-Net from the LX network | Yes, origin, into rope segment 1 | powerCON TRUE1, AC mains, auto-switching 100–240V | Feeds the rope near end (our cabling) |
| PWR-NJCT | Flown at each pickup (winch on DS/US, chain motor on the audience APs) | None | None | powerCON TRUE1, up to the box | Down our drop into the rope, run to run through our Y-3 and Y-2 Wyes, feeding each run in both directions |
KG3 cable plan: rack to LED, every cable with a length
CTRL A → DS1 · DS2 · DS3 · AUD1
CTRL B → AUD2 · US4 · US5 · US6
CTRL C → USR1-1 · 1-2 · 1-3
CTRL D → USR2-1 · 2-2 · 2-3
5× Pixel Data + Power Cable (NL8)
+ 4× NL4 = 14 circuits
Decision of record (Aug 31): the feeders leave the pylon control rack on our Pixel Data + Power Cables (NL8) plus one NL4 single per stage group. Each Pixel Data + Power Cable carries two circuits (V+ / GND / Data each, built on 16/6 wire); an NL8 barrel at the top couples the cable to an NL8-to-2x-NL4 splitter that lands the two runs it serves. The first run of each stage group rides its own NL4. Audience takes one NL8 only. That is 5x NL8 + 4x NL4 = 14 circuits, matching the 14 controller outputs above.
Pixel Data + Power Cable lengths marked ? are estimates from pylon geometry (arms at ~18'2" / 23'7" / 28'7", 10 ft ground run + 5 ft slack) and are not cut lengths. The Wye chains at the injection columns (Y-3 at each upper run, Y-2 at the bottom run) are drawn at the confirmed 5'2" to 5'6" between runs. Run spacing CONFIRMED by production (Josh Slade SWR schedule, Sep 1 2026): 5'2" to 5'6" run to run, with the top run 3'1" to 3'5" below the pickup. The Wye tails are 20" with the NL4 on, so two tails do not span a 5'2" to 5'6" gap on their own: a 20" stock jumper between Wyes covers every DS and US run with 0 to 3" of slack, and only the two audience jumpers are cut long.
Power requirements by point: international mains options
Every KG3 box runs an auto-switching 100–240V supply, so 110/120, 208, 220 and 230V legs all work unchanged, no voltage restriction at any point. Figures below are max draw at full white with 25% headroom already included.
| Point | Feed | LED load | AC watts (w/ headroom) | A @ 120V (US) | A @ 208V | A @ 230V (UK) |
|---|---|---|---|---|---|---|
| Pylon PXL CTRL rack | TRUE1 + etherCON data | 1,483 W | 2,181 W | 18.2 | 10.5 | 9.5 |
| PWR-NJCT 1 · MS WIRE ROPE Winch 1 (DSP), LX truss | TRUE1 | 637 W | 937 W | 7.8 | 4.5 | 4.1 |
| PWR-NJCT 2 · MS WIRE ROPE Winch 2 (DS end), backdrop truss | TRUE1 | 321 W | 472 W | 3.9 | 2.3 | 2.1 |
| PWR-NJCT 3 · US WIRE ROPE Winch 1 (USP), scenic truss | TRUE1 | 528 W | 776 W | 6.5 | 3.7 | 3.4 |
| PWR-NJCT 4 · US WIRE ROPE Winch 2 (US end), scenic truss | TRUE1 | 230 W | 338 W | 2.8 | 1.6 | 1.5 |
| PWR-NJCT 5 · DS ROPE 1 Winch 1 (AP1), chain motor | TRUE1 | 422 W | 620 W | 5.2 | 3.0 | 2.7 |
| PWR-NJCT 6 · DS ROPE 1 Winch 2 (AP2), chain motor | TRUE1 | 470 W | 691 W | 5.8 | 3.3 | 3.0 |
| PWR-NJCT 7 · DS ROPE 1 Winch 3 (AP3), chain motor | TRUE1 | 235 W | 346 W | 2.9 | 1.7 | 1.5 |
| Rig total (8 separately fed points) | 4,326 W | 6,361 W | 53.1 | 30.6 | 27.7 |
The total row is the sum across all eight points, not a single service: each point takes its own TRUE1 feed. Only the pylon rack takes data.
Controller allocation: 600 W / 4 outputs per box
Four boxes cover the rig: the audience runs ride the spare fourth outputs of the DS and US boxes, and every box stays inside its 600 W supply with margin. USR1 and USR2 keep their own boxes because those cables are single-end fed, so each box carries its group’s entire load.
Data origins & power injection by group
| Group | Runs | Data origin (pylon) | Data drops | Power injection, power only | Flown injectors |
|---|---|---|---|---|---|
| MS WIRE ROPE | 3 | CTRL A · out 1/2/3 | 0 | Winch 1 (DSP) · LX truss, + Winch 2 (DS end) backdrop truss | 2 |
| US WIRE ROPE | 3 | CTRL B · out 2/3/4 | 0 | Winch 1 (USP) · scenic truss, + Winch 2 (US end) scenic truss | 2 |
| US 1 | 3 | CTRL C · out 1/2/3 | 0 | none, single-end fed, ~5 m each | 0 |
| US 2 | 3 | CTRL D · out 1/2/3 | 0 | none, single-end fed, ~5 m each | 0 |
| DS ROPE 1 | 2 | CTRL A out 4 + CTRL B out 1 (cable bridge feed) | 0 | Winch 1 / 2 / 3 (AP1 / AP2 / AP3) | 3 |
| Rig total | 14 | 4 controllers in the rack + 1 road spare · every run starts at the pylon | 0 | at pickup points only (4 winch + 3 chain motor) | 7 |
One flown injector per pickup serves every rope in its group, so the 7 boxes below match the 7 pickups above. Data drops are zero everywhere by design: no run takes data from anywhere but its pylon controller.