DMXKing Devices

Overview

DMXKing manufactures professional-grade USB-to-DMX and Ethernet-to-DMX interfaces. QLC+ provides comprehensive support for DMXKing devices through the DMX USB plugin, including advanced features like RDM and multi-port configurations.

DMXKing devices are supported through the DMX USB plugin. This page covers DMXKing-specific features and configuration.

Supported Devices

DMXKing ultraDMX Pro

ultraDMX Pro

High-performance USB-to-DMX interfaceFeatures:

2 DMX outputs (1024 channels total)
1 DMX input (512 channels)
RDM support on both outputs
Galvanic isolation
Individual port configuration
Art-Net/sACN forwarding capability

Type: UltraPro

Port configuration:

Port 1: DMX Output (512 channels)
Port 2: DMX Output (512 channels)  
Port 3: DMX Input (512 channels)

Technical specifications:

Chipset: FTDI FT232RL
DMX Refresh Rate: Up to 44Hz per port
Connector: USB Type-B, 5-pin XLR
Power: USB bus-powered or external 9-12V DC
Isolation: 2500V galvanic isolation

Other DMXKing Devices

DMXKing produces other interfaces that may work with QLC+:

ultraDMX Micro - Compact single-universe interface
eDMX1 Pro - Ethernet to DMX converter
eDMX2 Pro - Dual Ethernet to DMX converter
RDM Responder - Test device for RDM development

Ethernet-based DMXKing devices (eDMX series) work with QLC+ through the Art-Net or E1.31 plugins, not the DMX USB plugin.

Device Detection

DMXKing devices use FTDI USB chips and implement the ENTTEC Pro protocol with extensions:

DMXKing Detection Process

static bool detectDMXKingDevice(DMXInterface *iface,
                                QString &manufName, QString &deviceName,
                                int &ESTA_ID, int &DEV_ID,
                                QByteArray &portDirection);

Detection steps:

Query manufacturer - Send label 77 (Get Widget Parameters)
Check ESTA ID - DMXKing devices report ESTA ID
Read device name - Label 78 (Get Widget Name)
Get port configuration - Label 211 (Get Port Assignment)
Activate DMXKing mode - Enable DMXKing-specific features

ESTA Manufacturer ID

DMXKing devices report their ESTA manufacturer ID:

#define ULTRADMX_PRO_DEV_ID 0x02

int ESTA_ID;  // DMXKing ESTA ID
int DEV_ID;   // Device ID (e.g., 0x02 for ultraDMX Pro)

DMXKing Mode

Once detected, the plugin enables DMXKing-specific features:

void setDMXKingMode();
bool m_dmxKingMode;  // Flag for DMXKing-specific commands

Port Configuration

DMXKing devices have configurable ports with direction flags:

Port Flags

enum PortType
{
    Output              = 1 << 0,  // DMX output capability
    Input               = 1 << 1,  // DMX input capability  
    USB_DMX_Forward     = 1 << 2,  // Forward USB DMX to network
    ArtNet_sACN_Forward = 1 << 3,  // Forward network to USB DMX
    ArtNet_sACN_Select  = 1 << 4   // Select Art-Net vs sACN
};

Port Direction

Ports can be configured as input, output, or both:

static void parsePortFlags(const QByteArray &inArray, QByteArray &outArray);

Example port configuration:

Port 1: Output (0x01)
Port 2: Output (0x01)
Port 3: Input  (0x02)

Getting Port Configuration

Query current port settings with label 211:

// Send: Label 211 (Get Port Assignment)
// Receive: Port flags for each port

The plugin automatically reads port configuration during device detection.

ultraDMX Pro Features

Multi-Port Operation

The ultraDMX Pro supports simultaneous operation on multiple ports:

// Opening outputs
open(0, false);  // Open Port 1 (output)
open(1, false);  // Open Port 2 (output)

// Opening input  
open(0, true);   // Open Port 3 (input)

Port-Specific Labels

DMXKing extends the ENTTEC protocol with port-specific labels: Standard labels (Port 1):

Label 6: Send DMX Packet (Port 1)
Label 5: Receive DMX Packet (Port 1)

Extended labels (Port 2):

Label 202: Send DMX Packet (Port 2)
Label 212: Receive DMX Packet (Port 2)

// Plugin automatically uses correct label based on port
if (output == 0) {
    // Use label 6
} else if (output == 1) {
    // Use label 202
}

RDM on Multiple Ports

Both output ports support RDM independently:

bool sendRDMCommand(quint32 universe, quint32 line,
                    uchar command, QVariantList params);

RDM labels:

Port 1: Label 7 (RDM), Label 11 (RDM Discovery)
Port 2: Label 207 (RDM), Label 211 (RDM Discovery)

The plugin automatically selects the correct label based on the port.

Network Forwarding

The ultraDMX Pro can forward between USB and network protocols: USB to Network:

PortType::USB_DMX_Forward  // Forward USB DMX to Art-Net/sACN

Network to USB:

PortType::ArtNet_sACN_Forward  // Forward Art-Net/sACN to USB DMX

Protocol selection:

PortType::ArtNet_sACN_Select  // 0 = Art-Net, 1 = sACN

Network forwarding is configured through DMXKing’s configuration software, not QLC+. QLC+ reads the configuration but doesn’t modify it.

Reading Device Information

Device Name

Label 78 retrieves the device name:

static bool writeLabelRequest(DMXInterface *iface, int label);
static bool readResponse(DMXInterface *iface, char label, QByteArray &payload);

// Request: Label 78 (Get Widget Name)  
// Response: Device name string (e.g., "DMXking ultraDMX Pro")

The device name is displayed in QLC+:

virtual QString realName() const;  // Returns device name from label 78

Label 77 returns device capabilities:

// Request: Label 77 (Get Widget Parameters)
// Response: 
//   - Firmware version
//   - DMX break/MAB times
//   - DMX refresh rate

Serial Number

DMXKing devices have unique serial numbers:

static bool extractSerial();
QString m_proSerial;

Format: Serial number embedded in device string

Driver Configuration

Windows

D2XX Driver (Recommended):

Download FTDI D2XX drivers

Available from FTDI website or DMXKing website

Install drivers

Run installer and follow prompts

Remove VCP drivers

D2XX and VCP conflict - uninstall VCP if present

Connect device

Windows should detect as “USB Serial Converter”

Verify in QLC+

Device should appear in DMX USB plugin outputs

Linux

libFTDI (Recommended):

# Install libFTDI
sudo apt-get install libftdi1-dev

# Create udev rule for DMXKing devices
sudo nano /etc/udev/rules.d/50-dmxking.rules

Udev rule:

# DMXKing ultraDMX Pro
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="0666"

# Apply rule
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="dialout"

Reload udev:

sudo udevadm control --reload-rules
sudo udevadm trigger

Add user to dialout group:

sudo usermod -a -G dialout $USER
# Logout and login for changes to take effect

macOS

D2XX Driver: Drivers are typically included with QLC+ or installed automatically. Manual installation:

Download FTDI D2XX drivers for macOS
Run installer package
Restart if prompted
Connect DMXKing device

macOS may require security approval in System Preferences > Security & Privacy after driver installation.

RDM Features

DMXKing devices have excellent RDM support:

RDM Discovery

Find all RDM devices on the DMX line:

// Send discovery command
sendRDMCommand(universe, line, RDM_DISCOVERY, QVariantList());

// Plugin uses:
// - Label 11 for Port 1
// - Label 211 for Port 2

Discovery process:

Send discovery request (mute all devices)
Devices respond with their UIDs
Plugin builds list of discovered devices
Unmute all devices

RDM Get/Set Commands

Read or modify device parameters:

QVariantList params;
params << deviceUID << parameterID << value;
sendRDMCommand(universe, line, RDM_GET, params);

Common RDM parameters:

0x0010 - Device Info
0x0020 - Product Detail
0x00F0 - DMX Start Address
0x0080 - Device Label
0x0096 - Lamp State

RDM Best Practices

Use quality DMX cables

RDM requires good signal quality - use DMX-rated cables, not mic cables

Proper termination

Install 120Ω terminator on last device in chain

Short cable runs

Keep total cable length under 300m (1000ft)

Test one device at a time

Isolate issues by testing devices individually

Update firmware

Keep both interface and fixtures updated

Troubleshooting

Device Not Detected

Verify USB connection

Try different USB port (prefer USB 2.0)
Use high-quality USB cable
Avoid USB hubs if possible

Check drivers

Windows: Device Manager should show “USB Serial Converter”Linux: Check with lsusb | grep 0403:6001macOS: System Information > USB should show device

Verify permissions (Linux)

# Check udev rules
ls -l /dev/bus/usb/

# Verify user in dialout group
groups $USER

Test with DMXKing software

Download DMXKing’s test utility to verify hardware

Port 2 Not Working

Verify port configuration - Check port is configured as output
Check QLC+ patching - Ensure universe is patched to second output line
Test Port 1 first - Confirm Port 1 works before troubleshooting Port 2
Swap ports - Test DMX cable on Port 1 to isolate cable/fixture issues

RDM Discovery Fails

Verify RDM-capable fixtures

Not all DMX fixtures support RDM - check specifications

Test one fixture

Connect single RDM fixture to isolate issues

Check termination

RDM requires proper 120Ω termination

Inspect cables

Verify pin 4 and 5 are wired (some cheap cables omit these)

Reduce cable length

Long cable runs can cause RDM issues

Performance Issues

Symptoms:

Flickering lights
Delayed response
Dropped frames

Solutions:

Use direct USB connection - Avoid hubs
Check USB bandwidth - Multiple USB devices can saturate bus
Update drivers - Ensure latest FTDI drivers
Verify output frequency - Should be 44Hz (default)
Check computer performance - Ensure QLC+ has adequate CPU

Advanced Features

Custom Output Frequency

Adjust DMX refresh rate:

virtual void setOutputFrequency(int frequency);

DMXKing supports:

25Hz - Very slow (theatrical)
30Hz - Slow
40Hz - Standard
44Hz - DMX specification (default)

Multiple ultraDMX Pro Devices

Run multiple interfaces simultaneously:

Connect devices one at a time
Note serial numbers for identification
Patch QLC+ universes:
- Universe 1: Device 1, Port 1
- Universe 2: Device 1, Port 2
- Universe 3: Device 2, Port 1
- Universe 4: Device 2, Port 2

Total capacity: 2048 channels (4 universes × 512 channels)

External Power

The ultraDMX Pro can use external power: Benefits of external power:

More stable operation
Better isolation
Doesn’t load USB bus

Power specifications:

Voltage: 9-12V DC
Current: 200mA
Connector: 2.1mm barrel jack (center positive)

External power is optional - the device works fine on USB bus power for most applications.

Comparison with ENTTEC

Feature	DMXKing ultraDMX Pro	ENTTEC Pro Mk2
DMX Outputs	2	2
DMX Inputs	1	1
MIDI I/O	No	Yes
RDM	Yes (both ports)	Yes (both ports)
Isolation	2500V	Unknown
Network Forward	Yes	No
External Power	Yes	No
Price	$$	$$$

Choose DMXKing ultraDMX Pro if:

Need network forwarding
Want external power option
Don’t need MIDI
Budget-conscious

Choose ENTTEC Pro Mk2 if:

Need MIDI I/O
Established ENTTEC ecosystem
Prefer XLR-5 connectors throughout

DMX USB Plugin

Main DMX USB plugin documentation

ENTTEC Devices

ENTTEC hardware support

Plugin Overview

Learn about the plugin architecture

Supported Protocols

Hardware Support

​Overview

​Supported Devices

​DMXKing ultraDMX Pro

ultraDMX Pro

​Other DMXKing Devices

​Device Detection

​DMXKing Detection Process

​ESTA Manufacturer ID

​DMXKing Mode

​Port Configuration

​Port Flags

​Port Direction

​Getting Port Configuration

​ultraDMX Pro Features

​Multi-Port Operation

​Port-Specific Labels

​RDM on Multiple Ports

​Network Forwarding

​Reading Device Information

​Device Name

​Widget Parameters

​Serial Number

​Driver Configuration

​Windows

​Linux

​macOS

​RDM Features

​RDM Discovery

​RDM Get/Set Commands

​RDM Best Practices

​Troubleshooting

​Device Not Detected

​Port 2 Not Working

​RDM Discovery Fails

​Performance Issues

​Advanced Features

​Custom Output Frequency

​Multiple ultraDMX Pro Devices

​External Power

​Comparison with ENTTEC

​Related Pages

DMX USB Plugin

ENTTEC Devices

Plugin Overview

Build docs developers (and LLMs) love

Overview

Supported Devices

DMXKing ultraDMX Pro

Other DMXKing Devices

Device Detection

DMXKing Detection Process

ESTA Manufacturer ID

DMXKing Mode

Port Configuration

Port Flags

Port Direction

Getting Port Configuration

ultraDMX Pro Features

Multi-Port Operation

Port-Specific Labels

RDM on Multiple Ports

Network Forwarding

Reading Device Information

Device Name

Widget Parameters

Serial Number

Driver Configuration

Windows

Linux

macOS

RDM Features

RDM Discovery

RDM Get/Set Commands

RDM Best Practices

Troubleshooting

Device Not Detected

Port 2 Not Working

RDM Discovery Fails

Performance Issues

Advanced Features

Custom Output Frequency

Multiple ultraDMX Pro Devices

External Power

Comparison with ENTTEC

Related Pages