Yesterday, in manuals, drivers, and firmware: support that converts, we mapped the downloads hub and unbox habits. Today the lens shifts: a shared vocabulary so technicians and buyers speak the same language before the first cue. Fewer “someone said I need two universes” moments without knowing what a universe is; fewer buzzword purchases.
This post is a practical glossary hub for DMX, Art-Net, USB, and Modbus terms used across the series. It is not a rewrite of day 20, not the Modbus deep-dive alone from day 12, not a stand-in for the USB–DMX intro on day 1 , and not a replacement for the TH-2U guide on day 8. Each entry adds why it matters and a path to go deeper. Indexes: shop · blog · Downloads.
How to use this glossary (buyer vs tech)
You do not need to read it cover to cover. Treat it as a map:
- If you are buying: jump to the “term and decision” cheat-sheet and the rows on universe, USB–DMX vs Art-Net, terminator, and Modbus TCP. Cross-link day 18 (budget and scale) and day 19 (use cases).
- If you are cabling or commissioning: prioritize DMX512, terminator, 120 Ω, optical isolation, node, universe mapping, and IP/subnet. Cross-link day 16, day 15, day 10 and day 9.
- If setup “does not detect”: check driver vs lighting software, USB–DMX interface, and common mistakes — day 20 · day 6 · day 4.
When a definition is not enough: info@electrotas.com · +54 (011) 3221-4474. State model, symptom, and which glossary term matches what you see.
DMX family: terms that define the bus
| Term | Practical definition | Why it matters | Go deeper |
| DMX512 | Lighting-control protocol on a balanced cable at 250 kbps; a daisy-chained serial “bus.” | Shared language between console/interface and fixtures. A dirty DMX bus beats expensive software every time — in the wrong direction. | Blog series · cable 80 Ω vs 120 Ω |
| Universe | A block of up to 512 DMX channels. One universe = one “street” of 512 addresses. | Decides whether a TZ-Mini/TZ-1U is enough or you need 2U / multi-universe Art-Net. | Day 2 · shop TZ-Mini · TZ-1U · TZ-2U |
| Channel | One address inside the universe (1–512), usually mapped to a parameter (dimmer, pan, color…). | Soft patch and fixture address must match. “No response” is often a bad patch, not dead hardware. | Day 4 software |
| DMX terminator | A ~120 Ω load at the end of the line to absorb reflections. | Without termination you get flicker, “crazy” fixtures, or intermittent faults that look like software bugs. | Day 16 · TDMX |
| 120 Ω DMX cable | Data cable with ~120 Ω impedance designed for DMX (not audio mic cable). | Audio cable at ~80 Ω is a classic that degrades the bus, especially on long runs. | Cable post |
| XLR 3 / XLR 5 | Common DMX connectors. Many pro interfaces use Neutrik XLR3; some ecosystems use XLR5. | Keep adapters and cabling consistent with your inventory. Do not mix “audio XLR” with “DMX XLR” without checking cable and pinout docs. | CNAB · Accessories |
| 120 Ω (impedance) | Reference value for the DMX bus and the terminator. | Aligned cable + terminator means fewer reflections. Electrical hygiene, not marketing. | Days 15–16 · MTDMX |
| Optical isolation (opto) | Galvanic barrier (optocouplers) between the control stage and DMX outputs. | Protects PC/interface from spikes and ground issues on stage or in fixed installs. | Day 3 · TZ-1U / TZ-2U |
| USB–DMX | An interface that outputs DMX from a USB host (PC/Mac) onto the lighting bus. | Typical path for studios, SMBs, and small tours: notebook software + interface. Different scale than Ethernet/Art-Net. | Day 1 · Day 7 |
| DMX mini tester | A quick diagnostic tool for cabling/signal on the bus. | Separates “bad cable / no termination” from “misconfigured software” in minutes. | Day 15 · MTDMX |
Short rule: universe + 120 Ω cable + terminator + correct patch is the floor. Software and drivers come next — see day 20.
Art-Net and network: Ethernet-path terms
| Term | Practical definition | Why it matters | Go deeper |
| Art-Net | A protocol that carries DMX universes over IP Ethernet. | Enables distance, switches, and multiple nodes without a single USB cable to FOH. Not the same as “any network cable” with no plan. | What is Art-Net · Day 7 |
| Art-Net node | A device that receives Art-Net and delivers DMX (among other roles). Line example: TH-2U (2 universes). | The bridge between the network and the stage/room DMX cable. | Day 8 TH-2U · shop TH-2U |
| Universe mapping | Assigning which Art-Net/soft universe exits which DMX port on the node. | Wrong mapping means silent fixtures even when the network “pings.” | Day 10 |
| Fixed IP / subnet | Coherent address and mask across console, nodes, and the control switch. | Art-Net does not forgive guest Wi-Fi or random IPs. Same hygiene as an orderly industrial LAN. | Day 10 · Day 9 topologies |
| Network topology | How switch, backbone, and nodes are cabled (star, and so on). | Defines robustness for touring vs fixed install; avoids a “magic hub” without a plan. | Day 9 · Day 17 rack |
| Ethernet path vs USB path | USB–DMX: local host. Art-Net: network + DMX node(s). | The buy decision is not “which is abstractly better,” but scale, distance, and universe count. | Day 7 · Day 18 |
If you come from show lighting and also run plant automation, Art-Net and Modbus can share a backbone only with documented IPs and a decent switch — see days 9, 10, and 12.
USB and host: PC-side terms
| Term | Practical definition | Why it matters | Go deeper |
| Driver | OS layer that surfaces USB hardware. | Without the right driver, QLC+ “does not see” the interface even if an LED is on. | Day 20 · Downloads |
| Lighting software | Creative app (QLC+, FreeStyler, and others) that builds cues and patch. | Does not replace the driver. Real compatibility is not “any marketplace soft.” | Day 4 |
| USB–DMX interface | Hardware between the host and the DMX bus (TZ line: Mini / 1U / 2U). | Choose by universes, opto, and use case (studio vs demanding stage). | Day 1 · TZ shop pages |
| 1U vs 2U | One or two universes in the same opto USB–DMX interface family. | “I ran out of channels” is a scale problem (2U / Art-Net), not a reason to abuse a single universe. | Day 2 |
| USB ownership | Only one app should open the interface at a time. | Two softs fighting one port means ghost detection and crossed blame. | Day 6 |
| Firmware (buyer habit) | Device-internal software; touch it only with an official package. | Not a synonym for driver. Do not flash on show night. | Day 20 |
Modbus, I/O, and relays: automation terms
| Term | Practical definition | Why it matters | Go deeper |
| Modbus TCP | Industrial dialect over Ethernet: a client (SCADA/PLC/HMI) talks to a server (I/O board). | When the plant already requires Modbus tags, a browser-only panel is not the production contract. | Day 12 |
| Digital / analog I/O | Field inputs/outputs: contacts, pushbuttons, and sometimes analogs depending on model. | Decides whether you need relays only, or also status/sensors into the supervisor. | Day 11 Ethernet I/O |
| DMX-to-relay | Turning DMX channels into switched loads (extractors, motors, effects). | The lighting console can also automate power — within confirmed ratings. | Day 13 · D21R · D28R |
| USB-to-relay | Switching relays from the USB host without riding the DMX bus. | Handy on the bench and for local automation; a different contract than DMX or Modbus. | Day 14 · U24R |
| Modbus client / server | Client starts; server (board) answers with coils/registers per the official map. | Do not invent register maps in a blog post: use ElectroTAS product documentation. | Day 12 · hub Downloads |
| DMX-RGB / color | Color/RGB control from DMX (AIO line in the shop). | Bridges the lighting patch and RGB strips/modules without mode mystery. | Day 14 · DMX-RGB-AIO |
Useful shop categories: DMX Relay · USB Relay · Accessories.
Workflow: from term confusion to a working cue
- Step 1 — Name the symptom with precise vocabulary
- Is it “USB not detected,” “wrong universe mapping,” “no termination,” or “I need Modbus, not only a web panel”? Write it down. Glossary above + day 20.
- Step 2 — Separate layers: host / network / DMX bus / load
- Host = driver + soft. Network = IP + Art-Net node. Bus = 120 Ω cable + terminator. Load = relay/fixture. Do not mix layers while diagnosing (days 6, 7, 10, 16).
- Step 3 — Pick the right control path
- Step 4 — Open the official pack and one soft only
- Hub Downloads or the product Downloads section. One soft at a time. Manual in view (day 20 · day 4 · day 6).
- Step 5 — First cue with bus hygiene
Buyer cheat-sheet: term and the decision it unlocks
| If you hear… | Decision it unlocks | Anchor product / post |
| “I need more than 512 channels” | Add a universe (2U) or move to multi-node Art-Net | TZ-2U · TH-2U · days 2 and 7 |
| “It is just a notebook in rehearsal” | USB–DMX often enough; do not overbuy network without a reason | TZ-Mini · days 1 and 18 |
| “Spikes / weird grounds on stage” | Prioritize an optically isolated interface | TZ-1U / TZ-2U · day 3 |
| “FOH is far / several DMX drops” | Art-Net + node(s), fixed IPs, clear topology | TH-2U · days 8–10 |
| “It flickers at the end of the line” | Terminator + 120 Ω cable + tester before blaming software | TDMX · MTDMX · days 15–16 |
| “The console must start an extractor” | DMX-to-relay within rating (or pilot a contactor) | D21R / D28R · day 13 |
| “On the bench I want four contacts from the PC” | USB-to-relay — do not force Modbus “because it sounds industrial” | U24R · day 14 |
| “SCADA/PLC must own the tags” | Modbus TCP (or a clear industrial contract), not web panel alone | Day 12 · day 11 |
| “USB not detected” | Official driver + one soft + Downloads pack — not random forums | Day 20 · day 6 · Downloads hub |
| “Touring vs fixed room” | Different rack checklist; same terms, different logistics | Day 17 |
Frequently asked questions
1. Does this glossary replace product posts?
No. It is the vocabulary map. Deep guides stay on days 1, 3, 8, 11–14 and the day-20 support hub.
2. Are “universe” and “Art-Net” the same thing?
No. A universe is the 512-channel DMX block. Art-Net is one way to carry those universes over Ethernet. You can have universes on USB–DMX with no Art-Net at all.
3. When is USB–DMX enough, and when is Art-Net the better path?
USB–DMX: local host, few universes, compact setup. Art-Net: distance, multiple nodes, network scale. Detail in day 7 and day 18.
4. Is the terminator optional “if the run is short”?
Best practice is to terminate the bus. Short runs sometimes “work”; long runs or picky fixtures punish missing termination. See day 16 and TDMX.
5. Are driver and lighting software the same?
No. Driver = OS sees the hardware. Soft = creative control. Day 20 · day 4.
6. Does Modbus TCP replace Art-Net?
No. Art-Net moves lighting universes; Modbus TCP moves industrial automation points. They can coexist on an orderly plant network (days 9–12).
7. Where do I download manuals after I understand the term?
Hub Downloads (Spanish twin: /descargas) and each product’s Downloads section. Full flow in day 20.
8. Does this post invent prices, pinouts, or register maps?
No. Only operational definitions and confirmed shop, hub, and published-post links. Specs and official maps live in ElectroTAS product sheets and packs.
Lock the vocabulary, then look at day 22
If today’s question is sharing one language between purchasing and operation, bookmark this glossary next to the Downloadshub. Anchor series: support · use cases · choose an interface · USB vs Art-Net · TH-2U · universes/IPs · Modbus · terminator · USB mistakes. Shop: shop · TZ · TH-2U · relays · blog.
Day 22 teaser: What an SMD pick-and-place line is, and how it fits a small/medium manufacturer (no post URL yet). Until then, do not buy on buzzwords: name the term, see the decision it unlocks, then open the product page.
ElectroTAS publishes this series so tech and buyer share vocabulary: fewer loops, fewer wrong kits, a shorter path to the first stable cue.