Commissioning guide

From empty bench to controlled haze.

A practical commissioning sequence for the HazeVane software baseline. Do not call a controller field-ready until its actual board, wiring, fixtures, network, and failure behavior pass acceptance.

TargetESP32-S3R8 + W5500
SensorGill WindSonic M
ControlE1.31 sACN
AccessTrusted wired LAN
01

Plan the control boundary

Reserve dedicated output universes, a command-input universe if used, static addressing strategy, fixture locations, and a single coverage polygon.

02

Bench the complete signal path

Commission WindSonic E2 / 9600 8N1 / continuous 4 Hz / M16 / m/s / CRLF. Confirm checksummed valid samples before field installation.

03

Bring up wired networking

Connect PoE Ethernet and browse to hazevane.local or the DHCP lease. Keep Wi-Fi and Bluetooth out of the deployment.

04

Map the canvas

Choose feet or metres, size the site, place and orient stage and FOH references, draw the coverage polygon, then position and rotate every hazer.

05

Patch scenes and sACN

Set safe, standby, and active DMX values; universe/address; output mode; priority; CID; and any unicast destinations.

06

Tune automatic selection

Choose All qualified, Best N, Minimum set, or Weighted rotation; then tune thresholds, travel horizon, plume spread, hysteresis, and fixture timing.

07

Watch autosave, then test

Non-network edits validate and apply after a short debounce. Confirm “All changes saved,” pulse each fixture while disarmed, and verify every safe-output path.

08

Run field acceptance

Observe real wind shifts, capture sACN, interrupt sensor/network/power, verify recovery, and document the approved show configuration.

First power-up

01

Keep output disconnected

First boot with hazer receivers isolated or in a controlled test environment. Confirm the configured safe scene independently before enabling show output.

02

Verify wind health

The fixed-width header should progress from Starting to Valid. Degrees and compass text describe where wind comes from; the arrow and Flow toward label point downwind.

03

Export a baseline

Export JSON before editing. Most changes autosave transparently; hostname and IPv4 fields remain isolated until Save & apply network settings is selected.

Map what matters.

  1. Choose Imperial or Metric display; durable coordinates stay SI internally.
  2. Resize the site from any corner around its fixed origin.
  3. Place stage and FOH, mark their front edges, then use live distance and soft alignment guides.
  4. Draw one non-self-intersecting coverage polygon with 3–64 vertices.
  5. Place and rotate up to ten hazers, then verify downwind plume motion against the real site.
  6. Use right-click near an object or empty site area for contextual edit, insert, test, remove, place, and fit actions.
HazeVane FOH geometry inspector over the infinite site canvas

Define safe before active.

  1. Patch 1–32 consecutive slots per hazer.
  2. Set a safe scene for disarm, blackout, faults, and startup.
  3. Set standby values for armed but unselected fixtures.
  4. Set active values only after bench verification against the fixture manual.
  5. Pulse-test each hazer while automatic control is disarmed.

Patch thirteen bounded controls.

Use a dedicated universe and start address. Slot 1 enables remote takeover; 2 maintains arm; 3 controls blackout; 4–13 trigger bounded tests for hazers 1–10. Values 128–255 are active.

Start with remote input disabled. Import the supplied GDTF or native grandMA3 profile, patch it, verify source priority/CID behavior, then test stream loss and reconnect.

Prove failure behavior before show day.

Normal operation is only half the test plan.

Commission deliberately. Operate confidently.

Start commissioning Open manual