Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
UDP Toolkit
By: David Bowdler
Updated: June 14, 2026
Version: 1.05
UDP Toolkit
Plenty of AV and automation gear is controlled over UDP rather than a connection-based socket - broadcast scene triggers, Wake-on-LAN, discovery beacons and a long tail of projectors, matrix switchers and gateways that simply listen for datagrams. The UDP Toolkit turns an RTI XP processor into a two-way controller for any of them. Pre-define up to 50 commands your macros fire by name, and independently watch incoming datagrams with up to 80 feedback patterns that drop live values straight into RTI system variables. A built-in browser page lets you author and capture the protocol from the live device - no Integration Designer restart.
Key Features
- 50 command slots: each fires from any macro as SendSlot1 through SendSlot50, with its own name, ASCII or hex payload and terminator.
- 80 feedback slots: 20 each of Boolean, Integer, String and Enum, matching incoming datagrams and writing live values to system variables.
- Both UDP styles: fire-and-forget (Wake-on-LAN, broadcast scene/zone triggers - no reply expected) and two-way (the device replies on a known port).
- Send & Capture web UI: a browser page on port 9032 to fire commands, watch the live traffic log, and author feedback patterns by clicking buttons on the real device.
- Local Port control: set the exact port the driver listens on for replies, so two-way UDP protocols (SSDP, mDNS, and most commercial AV UDP control) deliver feedback reliably.
- Flexible framing: split incoming datagrams on CR, LF, CR+LF, a custom hex delimiter, or take raw bytes for binary protocols.
- Import/export .driverconfig: save an authored command-and-feedback surface and reuse it across projects. A ready-made generic two-way UDP device example ships in the driver's examples folder, validated against a bundled test server.
- Events for everything: a SENT event per command, plus MATCHED and CHANGED events per feedback.
Requirements
- RTI XP processor (XP-8 or compatible) running Integration Designer 11.4+ (runtime 24+).
- A target device reachable over UDP/IP on the same network. For two-way control, know the port the device replies on (its "Local Port").
- For the web authoring UI: any browser on the same LAN (default port 9032, configurable).
How It Works
Point the driver at your device's IP (or a broadcast address) and UDP port, then build your control surface either in Integration Designer Driver Properties or in the browser UI - both edit the same storage. Commands transmit on demand from macros. For two-way devices, set the Local Port to the port the device sends its replies to; the driver parses each incoming datagram against your feedback patterns and keeps the matching system variables current, so touch panels show real device state. When a response varies by model or firmware, the web UI's Send & Capture button re-authors the pattern from the live device in seconds. It is the same proven engine as our RS-232 and TCP Toolkits, switched to UDP/IP transport.
UDP Toolkit
Version 1.05
A general-purpose UDP/IP utility driver. Same architecture as the RS-232 and TCP Toolkit - just talks UDP datagrams instead. Pre-define up to 50 UDP commands your macros can fire as "Send Slot N", and independently pre-define up to 80 feedback patterns (20 Boolean + 20 Integer + 20 String + 20 Enum) that watch incoming UDP traffic and write to sysvars. Browser test page on port 9032 for ad-hoc command entry, live capture, and per-feedback authoring.
Setup
In Driver Properties:
- Host: target IP address or hostname (where to send datagrams). Example: 192.168.1.50 or 255.255.255.255 for broadcast.
- Port: target UDP port. Common AV defaults: 53 (DNS-style), 161 (SNMP-style), 9 (Wake-on-LAN), 5353 (mDNS).
- Local Port: where to bind locally to receive replies. Leave 0 to use the same port as the target.
- Receive Framing: how to split incoming bytes into messages.
- Enable Web Interface: on by default, port 9032.
UDP is connectionless. The driver shows "Connected" once the local socket is bound; there is nothing to reconnect if a device goes offline (no link to drop).
Important: how UDP replies are routed. Each outgoing datagram from this driver uses a fresh ephemeral source port (this is the RTI platform's UDP behaviour). The driver receives replies on the Local Port set above, NOT on the ephemeral source port. This works perfectly for protocols where the device replies to a well-known port (SSDP=1900, mDNS=5353, most commercial AV UDP protocols) and for fire-and-forget sends (Wake-on-LAN, broadcast triggers). It does NOT work for protocols where the device echoes back to the sender's source port. Check the device's UDP reply behaviour and set Local Port to match where it sends replies.
Commands (TX)
Set "Number of Commands" (0-50). Each command exposes its own settings category: Display Name, Data Format (ASCII or Hex), Command Data, Terminator.
Macros call commands by export name "SendSlot1" through "SendSlot50". Each fires a "SLOTN_SENT" event when used.
Feedbacks (RX)
Four feedback types, 20 of each. Match incoming RX patterns, write to sysvars. Boolean (ON + OFF), Integer (prefix extracts first int), String (prefix captures full RX), Enum (pattern-to-label list, first match wins).
Author via IDesign Driver Properties OR the web UI's per-tile gear icon. Web UI Send + Capture authors patterns from live device replies.
Multiple Toolkit drivers on one processor
UDP Toolkit can run alongside RS-232 Toolkit, TCP Toolkit, and HTTP Toolkit on the same RTI processor. Each driver:
- Has its own unique driver GUID
- Defaults to a different Web Interface port (9030 = RS-232, 9031 = TCP, 9032 = UDP, 9033 = HTTP)
- Uses its own licence seed (separate keys per driver)
- Has its own sysvars, events, and macro picks in IDesign
Licence
15-minute trial on every driver load. After 15 minutes, send operations refuse until a valid licence key is entered.
To obtain a licence key:
1. Install the driver. The MAC For Key sysvar (or the web UI banner) shows your processor's MAC address.
2. Email that MAC to support@smarthomeprogramming.com.au.
3. Paste the 32-character key into the "Licence Key" field.
Licence keys are per-processor AND per-driver. A UDP Toolkit key won't unlock the TCP Toolkit.
Support
Smart Home Programming
support@smarthomeprogramming.com.au
smarthomeprogramming.com.au
The UDP Toolkit runs as a fully functional 15-minute trial every time it loads - long enough to prove it controls your device before you buy. A licence key removes the trial limit.
Licensing is per RTI processor: each key is bound to that processor's MAC address. Find your MAC in the driver's MAC For Key system variable (or the banner across the top of the built-in web UI), purchase a key at the link below, and paste the 32-character key into the Licence Key field in Integration Designer Driver Properties. The key arrives by email within seconds of purchase.
Price: AUD $49 ex GST. One licence per processor; sites with multiple XP processors need one key each.