Specifications
leaflet-xnd-4-d0-len-v01-07-1.pdf
Lighting and control
Swisson XND-4
A four-port node for sending Art-Net or sACN to DMX lines. Identify the exact variant and port before changing network settings.
Model and connections
| Model and connections | Swisson XND-4 |
|---|---|
| Family | XND-4: four ports; not XND-8 |
| Variants | B: box; R: rack. Suffixes 3/5/8: 3-pin XLR / 5-pin XLR / RJ45 |
| Other variant | XND-4D: DIN rail, RJ45 and terminals, external power supply |
| Revision | Manual V01-08; verify each unit’s firmware and hardware |
Show scenario
The controller discovers the node, but one fixture line does not respond. We propose tracing source → universe → port → cable → fixture, changing one variable at a time.
Patch and termination: tracing a nonresponsive line
Proposed example: three fixtures, each set to a 16-channel personality, on one universe. Addresses 1, 17 and 33 occupy 1–16, 17–32 and 33–48. This is an address calculation, not a claimed manufacturer profile; recalculate the footprint if the personality changes.
The universe identifies the stream; the start address identifies each fixture’s position in that stream. Mapping two node outputs to the same universe duplicates its data onto two branches; it does not add capacity or independent addresses. A splitter distributes a line; a node converts network data.
- Record each port’s direction, protocol, universe, physical destination and each fixture’s personality/address. Check that start address + channel count − 1 does not exceed 512.
- For the test, use one intended source and one Output port. Connect one fixture with a DMX cable known to be working and correct termination. Test intensity and any shutter prerequisites specified in the fixture manual.
- Reconnect fixtures in order. Daisy-chain the line rather than splitting it with a passive Y cable; assess an appropriate DMX splitter when separate branches are needed.
- Terminate each branch at its end: ETC specifies 120 Ω between data + and −. Check whether the last fixture’s termination is already enabled and use the exact model’s connector/pinout; do not add terminators at every fixture.
- If adding a segment introduces the fault, record the cable, receiver and termination that changed the result. Repair or replace the identified component instead of changing the entire network blindly.
We can assess the node, splitter, cables and terminators, prepare a patch and branch labels, or provide configuration and an operator. Start with date, venue and an approximate fixture count; a survey defines equipment and rehearsal needs.
Prepare the system
- Record the label, hardware, firmware, IP, netmask and port settings.
- Confirm Ethernet link and an agreed network with unique addresses; do not apply example addresses to someone else’s network.
- For network-to-fixture operation, set the intended port to Output with the correct protocol and universe; verify Apply or save.
- Test a DMX cable known to be working and one fixture with the correct address and personality, then reconnect the remaining line.
Questions and solutions
Does discovering the node prove it is sending DMX?
No. Discovery and lighting data are separate checks. Read port status and confirm that the controller is actually sending the assigned universe and protocol.
What if the port is set to Input or Off?
Network-to-DMX operation needs Output. Avoid changing all ports together: some may intentionally be inputs. Input support depends on hardware and firmware and cannot be assumed on older units.
What do No Update and No DMX mean?
The manual defines No Update as no updates on that universe for ten seconds, and No DMX as no DMX reception or transmission. Record status, port direction and source before concluding there is a physical fault.
Why can’t I open the web interface?
The manual specifies firmware 1.03 onward and units produced after 2017, hardware revision 1.0-b. Check IP and network; use the applicable local controls if the hardware does not meet that condition.
What happens when controller data stops?
Configurable behavior includes Off and Hold Last Look. Agree on and rehearse the show’s response. Holding a look is not a safety system and does not correct an unintended data source.
Should I select Relaxed for a flickering fixture?
The manual offers Relaxed, approximately 30 Hz, to help with older fixtures versus approximately 44 Hz for Max. Frame Rate. Compare outside the performance after checking cable, termination and profile; it is not a universal repair.
Can I use a Y cable to create two DMX lines?
ETC advises against passive Y splitting. Use a daisy chain and assess a suitable DMX splitter for separate branches. Each branch needs appropriate termination and cabling; confirm RDM and isolation requirements for the selected equipment.
Can two fixtures share the same start address?
Yes, to receive the same channels in the same universe when that behavior is intended. For independent control, reserve each personality’s footprint: in the 16-channel example, 1, 17 and 33 do not overlap. A shared address does not guarantee the same effect with different models or profiles.
Precautions
- Do not treat a DMX RJ45 output as Ethernet: check labeling and the variant’s pinout.
- Follow the rating label and manual for power, grounding and mounting. XND-4D uses an external supply, unlike mains-powered variants.
Manuals and documents for this equipment
Choose the document for the model, revision and language shown. Read it here or download the original PDF.
Sources and documentation
- Swisson XND — models and connectors
- XND-4 User Manual V01-08 — 2020-10-28
- ETC — DMX topology, cabling and termination
Consulted October 23, 2026. Manual V01-08 dated October 28, 2020; features depend on hardware and firmware. Line test proposed.
Missing sACN: separate sender, switch and node
For a MagicQ → GigaCore → XND-4 chain, record actual models and firmware before testing. A working web interface is insufficient: management may use a different group or interface. Locate the segment losing data before changing a documented setting.
In an isolated test, sACN unicast addressed to the node can provide a comparison with multicast. It is not an automatic IGMP fix or validation of the whole network. Record both destinations and restore approved configuration after testing.
- In MagicQ, check selected interface, universe, sACN output type, enabled state and any previous unicast destination. On XND-4, check protocol, universe and output port direction against its manual.
- If multicast fails, inspect the GigaCore Group/VLAN across links, querier and receiver IGMP registrations. A capture on another computer without subscription or mirroring may miss the traffic; an empty capture does not prove no transmission.
- Compare an authorized minimum path with the full path, adding switches separately. Record source, destination, time, test values and result. If data reaches the node, continue through its DMX port, cable and fixture.
Start with your date, venue and approximate needs. We can assess equipment, configuration and operation within an agreed scope.
Should I disable IGMP on every switch?
Avoid global changes. Identify generation, group, querier and subscription. Working under flooded traffic does not validate the intended design.
Why does unicast work while multicast fails?
It directs attention toward multicast transport, without excluding destination or configuration differences. We can assess segment testing, a network map and a rehearsed alternative path before the event.
Help us improve this guide
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.