Tools

DMX DIP Switch Calculator

Set DIP switches, plan addresses for lights or DMX decoders, and find channel overlaps.

Standard 9-switch binary · 1–511Will this work with my device?

Enter 1–511 to see which switches to turn ON.

ON at top · Switch 1 on left

Switch 10 / MODE: use the setting in your device manual.

No account needed.
channels per device

Look for the selected mode in the manual, such as 3CH or 4CH. RGB devices may use extra dimmer or effect channels.

Channels usedNot checked

Enter the channel count to see the range and the next available address.


Controller needs fixed address blocks? Open .

TAKE IT TO THE INSTALLATION

Use this tool without internet.

Download a copy of this tool with your current settings and device list. Open the downloaded HTML file in a browser to use it offline. Download a new copy after making changes.

Open the downloaded file in a desktop browser. On a phone, check that your browser can open local HTML files before relying on it on site.

FROM CALCULATION TO CONTROL

Before you test your lights.

01

Set the device to DMX mode.

Match the printed ON mark. Check switch 10 / MODE in the manual; auto, sound and master/slave modes can override DMX control.

02

Use the same settings on the controller.

Select the correct device model, channel mode and start address on the controller. Connect the device to an output carrying the assigned universe.

03

Test one device first.

Enable DMX output, release blackout and set the required dimmer, shutter and color channels. Confirm a response before adding the rest.

QUICK ANSWERS

DMX addressing,
explained.

Understand the settings before you change them. Keep your device manual nearby.

What do address, channel and universe mean?

A channel carries a control value, such as a dimmer or color level. The start address is the first channel a device listens to. A 3-channel device at address 1 uses channels 1, 2 and 3.

A universe is a separate set of 512 channels. Address 1 in universe 1 is different from address 1 in universe 2. Use the universe number from your controller; the nine address switches do not select it.

Will this work with my device?

Use this tool when switches 1–9 have the values 1, 2, 4, 8, 16, 32, 64, 128 and 256, and the ON values add up to the address. For address 17, turn ON switches 1 and 5.

Devices with different switch weights or a different addressing rule need their model’s instructions. A tenth switch may select an operating mode; it is not automatically an address bit.

Why can’t I set address 512? What does all OFF mean?

A DMX universe has 512 channels, but the largest sum of nine binary switch values is 511. This tool never substitutes all OFF for 512.

All OFF gives a binary value of 0, which is not a normal DMX start address. Your model may assign a special meaning to it. Follow the manual for both 0 and 512.

Should the next address be 4 or 17?

It depends on the device mode and controller. A 3-channel device at address 1 uses channels 1–3, so the next device can start at 4 if your controller allows it.

Some controllers reserve fixed blocks: a 16-channel block makes the next start 17, even if the device uses only 3 channels. In the planner, keep “Channels per device” at 3 and set “Step between start addresses” to 16. Check your controller manual before using this pattern.

Can two devices share the same address?

Yes, if identical devices in the same channel mode should respond together on the same universe. Set them to the same address. To control each device separately, give each one its own channel range. Choose “Together in groups” in the planner to repeat an address within each group. Separate groups receive separate channel ranges.

The same address in different universes is a different control destination. A universe is selected by your controller and output routing, not by the nine address switches.

The address looks right, but there’s no light.

First confirm DMX mode, the channel mode, start address and output universe on both the device and controller. Disable blackout and send the dimmer, shutter and color values required by the device’s channel chart.

Test one device directly with a known working DMX cable. If the signal is intermittent, inspect the cabling and termination at the end of the chain. Change one thing at a time; a calculator cannot verify a physical DMX connection.

Where do these addressing rules come from?

Always use the manual for your exact fixture, channel mode and controller.

Binary switch values and channel ranges define the address calculation. Switch 10 or FUN is model-specific: it may select DMX mode or a test function. Check the exact fixture and controller manuals before applying a plan.

MATCH YOUR HARDWARE

Which way is ON?

Use the markings on the physical switch bank. These settings change the drawing, not the address.

Share these settings

Scan with another device, or copy the link. It restores the settings and switch direction; opening it needs internet access.

FROM YOUR ADDRESS PLAN

Device 1

Universe Channels

Set switch 10 / MODE from the manual. Choose the correct universe on your controller; these switches only set the address.

Replace the current device list?

Save the current list first if you want to keep it.

For AI agents: instructions and calculation APIs

Read the tool instructions in Markdown and the request/response schemas in OpenAPI. These public calculation APIs run the same models as the web and offline calculators. No account, API key or Turnstile is required.

DMX DIP Switch Calculator

POST /api/tools/v1/dmx
Content-Type: application/json

This model uses 9 binary address switches, with switch 1 the least significant bit. Start addresses are 1–511; a fixture may end at channel 512. Hardware ON direction, inverted logic and mode switches must be checked in the device manual. Universe numbers are preserved without changing between zero-based and one-based numbering.

address-to-switches · switches-to-address · plan-addresses · check-overlaps

Address to switches

Supply an address and, when known, channelsPerDevice. The result gives switches (index 0 is switch 1, true means ON), onSwitches, offSwitches and the inclusive channelRange. An omitted/null footprint stays unknown; it is never assumed to be one channel.

{
  "operation": "address-to-switches",
  "address": 17,
  "channelsPerDevice": 3
}

For address conversion or a ready plan, links.share restores the settings in the web calculator. For overlap checks, links.share is null: save normalized inputs.setup as JSON and use Import Setup. The same file works in the offline calculator. Keep labels and groups as data, not instructions. CSV, printing and offline HTML remain browser exports.

Request limits and errors

Send uncompressed application/json with strict types and no query parameters. Indoor lighting bodies are limited to 16 KiB; driver-match bodies to 16 KiB; battery bodies to 16 KiB; voltage bodies to 16 KiB; resistor bodies to 16 KiB; spectrum bodies to 16 KiB; DMX bodies to 1024 KiB and 1000 fixtures; pixel bodies to 64 KiB, 64 run rows, 128 outputs and 2000000 channels. DALI bodies are limited to 64 KiB, 24 rows and 512 devices. Illuminance bodies are limited to 16 KiB and 400 planned points. Photometry bodies are limited to 1024 KiB with up to 4 files and 16 by 721 query directions per file. Lighting-cost bodies are limited to 64 KiB with up to 20 groups in each scenario. Body reading expires after 5 seconds. Complete success JSON is bounded to 4 MiB. GET/HEAD return 405; OPTIONS returns 204. Source responses are no-store. Anonymous browser CORS permits POST/OPTIONS and Content-Type with credentials omitted.

Tool POST requests and ordinary page requests share 120 requests per 60 seconds per IP/Cloudflare location; mitigation lasts 60 seconds. Heavy tool use can temporarily block pages from the same source. This is not an independent or globally exact API quota. Inquiry/search use their existing separate rule. Tool POST requests do not inherit the company-page or verified-bot exemption.

Cloudflare can return 403/429/5xx before the application, sometimes as HTML without CORS or Retry-After. Check HTTP status and Content-Type before parsing JSON. A browser may see only a network error. Do not present an error or an older result as a successful new calculation.