Artistic Licence Art-Net Parameter Controllable Device

Artistic Licence Art-Net Parameter Controllable Device

Minimum hi Version: v2.7.6

Overview

hi broadcasts ArtPoll to discover Art-Net^™ Nodes. It creates a Port for every Port that the Node reports, including input-only Ports, and only output Ports act on ArtDmx. Each hi system can have one Art-Net Node. Initialization fails if no Art-Net Node replies within 10 seconds. It exposes output channels as Parameters. When a channel changes, hi sends the complete 512-channel ArtDmx frame for that Port's universe.

Network Requirements

• Connection Model: hi sends discovery and DMX output datagrams and receives discovery replies on UDP 6454.

• Multicast / Unicast: IPv4 broadcast.

• VLAN / IGMP: Place hi and the Art-Net Nodes in a subnet that carries broadcast traffic.

• Bandwidth: DMX control traffic only.

• IP Version: IPv4.

• Firewall: Permit bidirectional UDP 6454 between hi and the commissioned Art-Net subnet.

Standards Conformance

Operator Workflow

• UI Surface in hi: Control Panel, Parameter Control, Rule Engine, and Inventory

• Resources Controlled: Discovered output Ports, universes, and DMX channels

• Parameter Semantics: Each output Port shows 512 channel Parameters, Channel: 1 to Channel: 512, that accept whole numbers from 0 to 255.

• Device Administration: Configure Nodes, fixture patching, and cue content in the lighting system's own tooling.

• Scope Boundary: hi sends ArtDmx output values. It does not author fixtures or cues and does not consume DMX input values.

Connection Details

Required Configuration

UDP Port 6454 is fixed on both hi and the Art-Net Nodes; it is not an editable setting in the hi device editor. Confirm that the commissioned hi network interface can send and receive Art-Net traffic on the selected subnet.

Device-Side Setup

Follow Artistic Licence Art-Net Parameter Controllable Device Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Potentially Compatible (Not Yet Verified)

• Other Art-Net nodes that receive ArtDmx universes and answer ArtPoll discovery.

Known Limitations

• hi listens on UDP 6454 on all server interfaces and sends to the broadcast address that it calculates from the configured subnet.

• A hi system has one Art-Net Node. All discovered Art-Net Nodes and their output Ports appear on that Node.

• hi names each Port DMX Output <number> - <name>, where <name> is the short name of the Art-Net Node. All Ports of one Node show the same name. hi reads up to four Ports from a discovery reply that describes all Ports of a Node.

• hi creates a DMX Output Port for every Port that the Node reports, including input-only Ports. Writes to an input-only Port have no effect.

• If no Art-Net Node replies within 10 seconds of connecting, the connection fails.

• hi repeats discovery every 10 seconds after connecting. The Art-Net 4 specification requires controllers to send ArtPoll every 2.5 to 3 seconds. hi does not answer ArtPoll with its own ArtPollReply.

• hi sends ArtDmx frames to the directed broadcast address of the configured subnet. It does not unicast each universe to its subscribed Nodes as the Art-Net 4 specification requires, so every Node in the subnet receives every universe that hi sends.

• hi addresses each output with the universe value that the Node reports in its discovery reply and does not apply the Node's Net or Sub-Net values. Verify output on Nodes that use a non-zero Net or Sub-Net.

• hi sends ArtDmx frames with sequence checking disabled and does not send ArtSync, so Nodes output each frame when they receive it.

• hi sends an ArtDmx frame only when a channel value changes and does not repeat frames. The Art-Net 4 specification defines a failsafe state for Nodes that lose network data: hold last state, all outputs to zero, all outputs to full, or play a failsafe scene. Check the failsafe state of each Node.

• When another controller sends ArtDmx to the same universe, the Art-Net Node merges the two sources as the Art-Net 4 specification describes.

• If Nodes are not discovered, verify that the selected server interface and the Art-Net Nodes share a subnet that carries IPv4 broadcast traffic.

What's Not Supported

• DMX input, merge behavior, fixture profiles, patch authoring, cue authoring, and Art-Net Node configuration.

• RDM device discovery and control (ArtTodRequest, ArtTodData, and ArtRdm).

• ArtTrigger and ArtNzs (non-zero start code) packets.

Trademarks