Driver Details

New Community

TCP Toolkit

By: David Bowdler
Updated: June 14, 2026
Version: 1.11
Download Driver Purchase License
Rating: 0.0 (0 ratings)
Log in to rate this driver

TCP Toolkit

The TCP Toolkit turns an RTI XP processor into a two-way controller for any device that speaks over a raw TCP/IP socket - projectors, AV receivers, matrix switchers, DSPs and automation gateways that never got a dedicated RTI driver. Pre-define up to 50 commands your macros fire by name, and independently watch the incoming stream 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 entire protocol from the live device - no Integration Designer restart, no guesswork.

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 the incoming stream and writing live values to system variables.
  • Send & Capture web UI: a browser page on port 9031 to fire commands, watch the live traffic log, and author feedback patterns by clicking buttons on the real device.
  • Connect handshake + auto-reconnect: send a fixed hex byte string the moment the socket opens (e.g. Epson ESC/VP.net), and recover automatically if the link drops.
  • Flexible framing: split the incoming byte stream 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 Epson ESC/VP.net projector example ships in the driver's examples folder.
  • Events for everything: a SENT event per command, MATCHED and CHANGED events per feedback, plus Connected and Disconnected link-state events for reconnect logic.
  • Telnet debug console: an optional on-processor console for live diagnostics during commissioning.

Requirements

  • RTI XP processor (XP-8 or compatible) running Integration Designer 11.4+ (runtime 24+).
  • A target device reachable over TCP/IP on the same network, with a text or binary control protocol you can document or capture.
  • For the web authoring UI: any browser on the same LAN (default port 9031, configurable).

How It Works

Point the driver at your device's IP address and TCP 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; the driver continuously parses the device's replies against your feedback patterns and keeps the matching system variables current, so touch panels show real device state. When a protocol 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 Toolkit, switched to TCP/IP transport.

TCP Toolkit

Version 1.11

A general-purpose TCP/IP utility driver. Same architecture as the RS-232 Toolkit - just talks TCP instead of RS-232. Pre-define up to 50 TCP 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 the incoming TCP stream and write to sysvars. Browser test page on port 9031 for ad-hoc command entry, live capture, and per-feedback authoring.

Setup

In Driver Properties:

- Host: IP address or hostname of the device. Example: 192.168.1.50

- Port: TCP port. Common AV defaults: 23 (Telnet, most Epson/Sony projectors), 4999 (Lumagen Radiance Pro), 5000 (some matrix switchers), 8080.

- Auto-Reconnect: on by default. Driver retries the connection every 5 seconds if it drops.

- Receive Framing: how to split incoming bytes into messages.

- Enable Web Interface: on by default, port 9031.

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

TCP Toolkit can run alongside RS-232 Toolkit, UDP 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 TCP Toolkit key won't unlock the RS-232 Toolkit.

Support

Smart Home Programming

support@smarthomeprogramming.com.au

smarthomeprogramming.com.au

The TCP 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 $59 ex GST. One licence per processor; sites with multiple XP processors need one key each.