01 — Protocol baseline
The protocol baseline
All LITEVISION stage luminaires are built on DMX512, and will accept control from any console, node or software that outputs a compliant DMX512 stream. There is no proprietary protocol lock-in: if the desk speaks DMX, it drives the fixture.
Physical connection is 3-pin or 5-pin XLR depending on the model, with 5-pin preferred on professional installs. Standard universes carry 512 channels; multi-head fixtures such as the Tornado range occupy a larger block and are documented per mode in the channel chart.
02 — Consoles we match
Consoles we already match
Fixture personalities are maintained for the desks our customers actually use. The table shows the console families, the file format we supply, and any caveat worth knowing before you buy.
| Console family | File we supply | Notes |
|---|---|---|
| Avolites Titan | .d4 personality (R20 also issued) | Covers Tiger Touch, Quartz, Arena and other Titan desks; loaded through the personality cache |
| grandMA2 | .xml personality, R20 compatible | Import through the fixture library folder; channel sets and gobo images included where applicable |
| grandMA3 | GDTF, or MA2 XML converted | Mode 3 accepts GDTF directly; older fixtures are mapped from the MA2 file |
| ChamSys MagicQ | GDTF or .d4 | Both routes work; GDTF is the cleaner path on current software |
| Hog, Onyx, ETC Eos | GDTF | GDTF is the cross-platform format these desks import natively |
| Any other DMX desk | Channel chart (PDF) | Manual patching from the chart; no library file needed |
03 — Art-Net and RDM
Art-Net and RDM
Most models support Art-Net over Ethernet, so a single network cable can carry multiple universes to a truss instead of a chain of DMX runs. Art-Net is the reason a 40-fixture rig can be addressed in minutes rather than hours of cable work.
RDM is supported on most models too, which means the desk can discover the fixture, change its DMX address and personality mode, and read back temperature and firmware version without anyone climbing a ladder. Where a specific model does not carry one of these options, the product page and channel chart state it — check before specifying, rather than assuming across the range.
04 — Fixture libraries
Fixture libraries we provide
The library files are what make a fixture usable on the first day. We supply them in the formats the main platforms read:
- Avolites — .d4 personality files for the Titan platform
- grandMA2 / MA3 — .xml personality in R20-compatible structure
- GDTF — the general device type format, with an MVR scene file for previsualisation in capture and pre-programming workflows
- Channel chart — a PDF for every model, listing channel functions, 16-bit pairs and value ranges per mode
Files are issued with the order and on request afterwards. Where a library has to be revised — new firmware, a changed channel order, a new mode — we reissue it rather than ask you to patch around the difference.
05 — Channel charts
Channel charts for every fixture
Every product we make has a published DMX channel chart: mode by mode, channel by channel, with the function, the 16-bit pairing and the value ranges for strobe, colour, gobo, prism, focus and zoom. Programmers use it to build a personality by hand when a library file is not at hand; rental houses use it to check that a substituted fixture will behave the same as the one on the plot.
06 — Firmware and updates
Firmware and updates
Firmware updates are delivered as a file and applied from a USB drive through the fixture menu, with the procedure documented for each model. We tell you which firmware a fixture shipped with, so a mixed fleet can be brought to one version before a tour rather than discovering the mismatch on site.
07 — Cabling and termination
Cabling and termination, briefly
Most “the console will not talk to the fixture” calls are cabling, not compatibility:
- Use 110 ohm shielded twisted-pair DMX cable, not microphone cable
- Terminate the last fixture in a DMX line with a 120 ohm terminator
- Keep runs under 32 fixtures per line, and use an optically isolated splitter beyond that
- For Art-Net, use CAT5e or CAT6 and a gigabit switch; keep the lighting network separate from any other traffic
- Check that the fixture’s personality mode is the one you patched, not merely the address
08 — Other desks
If your console is not on the list
Send us the console make, model and software version, and we will produce a matching personality or a patching sheet — usually inside two working days for a desk we have not built for before. In an emergency, the channel chart is enough to patch any compliant console manually.
09 — FAQ
Questions we are asked most
Will your fixtures work with my console?
Yes, if the console outputs DMX512. Library files exist for Avolites, grandMA2 and MA3, ChamSys, Hog, Onyx and ETC Eos; for anything else the channel chart allows manual patching.
Which file should I use for Avolites?
The .d4 personality. A Tiger Touch or any Titan desk loads it through the personality cache; an R20 file is also available if your workflow needs it.
Do you support Art-Net and RDM?
Most models do, both for network control and for remote addressing and setup. Because it is model-dependent, confirm the specific fixture before you specify a network-only rig.
Is a GDTF file available?
Yes, and with an MVR for previsualisation, which covers grandMA3, ChamSys, Eos and most capture workflows.
Can I get a channel chart before ordering?
Yes. Ask your sales contact for the chart of any model — it is the document we would want in your position before committing to a fleet.
What if my desk is unusual or the software is old?
Send the make, model and version. We will build a personality or a patching sheet, normally within two working days.
Next step
Get the library file for your console before you buy
Send the console make, model and software version, and the fixture you are considering. We will send the matching personality, or a patching sheet if the desk is unusual.
Ask for the library file →