Try any driver free for 30 days
Sign in Cart (0)
Fixxy Driver

Docs · Driver manuals

WolfPack FIX 16x16 Matrix driver

Two-way IP/serial driver for the HDTV Supply WolfPack FIX 16x16 HDMI matrix, model HDTVFIX1600E

Driver name in Composer: WolfPack FIX 16x16 Matrix (TM). Model: HDTVFIX1600E. Manufacturer: HDTV Supply. File: WolfPackFIX16x16_TM.c4z. Current driver version: 1.2.3. Store slug: wolfpack-fix-16x16.

Overview

A Control4 driver for the HDTV Supply WolfPack FIX 16x16 HDMI matrix. It was built to replace a driver that dropped routes when many TVs switched at once and had no feedback.

What it does:

  • Routes any of 16 HDMI inputs to any of 16 outputs from normal Control4 Watch selections.
  • Network control on TCP port 5000 with automatic reconnect, and RS-232 as a fallback.
  • Batches bursts: switches that arrive together (for example Room On or a multi-display scene firing all 16 TVs) are combined into one chained command, or a single "input to all outputs" command.
  • Latest route wins per output, and a paced send queue keeps the matrix from being overrun.
  • Commands sent while offline are held and sent when the connection comes back.
  • Two-way feedback: polls the matrix's built-in web page for the live route map. Changes made from the matrix's web UI, front panel, app or scenes show up in Control4, and routes sync on first connect.
  • Route verification: about 1 second after sending, the driver checks the matrix and re-sends any route it dropped (up to 2 retries).
  • Scene save and recall, route commands for programming, Matrix Online/Offline events.

Who it is for: dealers with a WolfPack FIX 16x16 who need every route to land, including large multi-TV scenes.

Requirements

  • HDTV Supply WolfPack FIX 16x16 (HDTVFIX1600E).
  • Control4 OS 3.0.0 or newer.
  • Network: the matrix on the controller's LAN, reachable on TCP port 5000 for control and on its web server (HTTP port 80) for feedback.
  • Serial (optional): RS-232 at 9600 8N1 with a straight-through cable, not null-modem.
  • Give the matrix a static IP or DHCP reservation.

Installing and first setup

  1. Add WolfPack FIX 16x16 Matrix (TM) to the project.
  2. Network (recommended): Connections > Network, enter the matrix IP on the Network (TCP 5000) connection.
  3. Serial (optional, as backup or instead of network): bind Serial RS-232 to a controller serial port. 9600 8N1, straight-through cable.
  4. Bind HDMI Input 1 to 16 to the sources and HDMI Output 1 to 16 to the TVs or displays.
  5. Refresh Navigators.
  6. Run Send Test Route (In 1 to Out 1) and check Last Command Sent and the TV.
  7. Check the Feedback property reads Live (HTTP). If the matrix's web server is at a different IP than the control connection, set Matrix IP (HTTP).

On first good poll the driver pushes the matrix's current routes into Control4.

Properties

  • Driver Version: read only.
  • Status: read only. Online or Offline.
  • Active Transport: read only. Network (TCP 5000), Serial, or None.
  • Last Command Sent: read only. Last command string sent to the matrix.
  • Last Data Received: read only. Last data the matrix sent back.
  • Preferred Transport: Auto (Network, then Serial) (default), Network Only, or Serial Only. Auto uses the network when online, otherwise serial.
  • Command Terminator: None (default), CR or CRLF. Leave None unless the matrix ignores serial commands; then try CR.
  • Batch Window (ms): 0 to 1000, default 75. Switches arriving within this window are combined into one command. 0 sends each switch right away.
  • Command Spacing (ms): 50 to 2000, default 200. Gap between separate commands.
  • Feedback: read only. Live (HTTP) when polling works, Off when polling is off, or the poll error.
  • Poll Interval (s): 0 to 60, default 3. How often the driver reads the matrix route map. 0 turns feedback polling off.
  • Matrix IP (HTTP): leave blank to use the Network connection IP. Set it only if feedback should poll a different address.
  • Max Routes Per Command: 1 to 16, default 16. Caps how many routes are chained in one command. Lower it if the matrix misses routes in big scenes.
  • Debug Mode: Off (default) or On. Prints sends, receives and sync decisions to the Lua tab.

Actions

  • Sync From Matrix: reads the matrix route map now and pushes it into Control4.
  • Resend All Routes: re-sends every route the driver is tracking.
  • Send Test Route (In 1 to Out 1): routes input 1 to output 1.

Programming

Commands (Device Actions):

  • Route (Input, Output): route one input to one output.
  • Route Input to All Outputs (Input): one input to all 16 outputs.
  • Recall Scene (Scene): recall a scene saved on the matrix.
  • Save Scene (Scene): save the current routing to a matrix scene.
  • Resend All Routes: re-send all tracked routes.

Events:

  • Matrix Online: the network connection came up.
  • Matrix Offline: the network connection dropped.

No variables or conditionals.

Normal Watch selections need no programming. Control4 sends the switch through the matrix proxy and the driver handles it.

Connections and bindings

  • Network (TCP 5000): the matrix control connection. Set its IP in Connections > Network.
  • Serial RS-232: optional controller serial port.
  • HDMI Input 1 to 16: video inputs from sources.
  • HDMI Output 1 to 16: video outputs to displays.
  • The matrix is video-only in Control4 (no separate audio connections).

Best practices

  • Use the network connection as the main transport and bind serial as a backup.
  • Leave Batch Window at 75 ms so Room On and multi-TV scenes go out as one command.
  • If a big scene misses outputs, lower Max Routes Per Command (for example to 4 or 8) and raise Command Spacing.
  • Keep Poll Interval at 3 seconds for feedback and route checking.
  • Keep the matrix on the local network only. Do not expose its web page to the internet.
  • Use a straight-through serial cable.

Troubleshooting

  • Status Offline, Active Transport None: no network connection and no serial binding. Check the matrix IP in Connections > Network and that TCP port 5000 answers, or bind serial.
  • Routes go out over serial when network is expected: the network connection is down; Auto fell back. Check the IP and cabling.
  • Serial commands ignored: check the cable is straight-through, 9600 8N1. Try Command Terminator CR.
  • Feedback shows HTTP poll failed (code): the controller cannot load the matrix's web page. Check the IP, or set Matrix IP (HTTP) to the address the web page answers on.
  • Feedback shows Unrecognized status response: the web page did not return the route map. Check it is the WolfPack FIX 16x16 web server at that address.
  • Feedback Off: Poll Interval is 0. Set it to 3.
  • Some outputs miss a route in large scenes: the driver retries up to 2 times. If it still happens, lower Max Routes Per Command and raise Command Spacing.
  • Control4 shows the wrong source after someone used the front panel: run Sync From Matrix, and confirm Feedback is Live (HTTP).
  • After a matrix power cut the routes are wrong: run Resend All Routes.

Limitations

  • Supports the 16x16 model only.
  • The matrix has no output off command, so disconnecting an output in Control4 sends nothing.
  • No documented status query on the control port; feedback comes from polling the matrix's web page.
  • No audio routing in Control4.
  • Scene numbers are whatever the matrix supports; the driver passes them through.

Version history highlights

  • 1.2.3: driver code encrypted. No functional changes.
  • 1.2.2: field-verified on a customer site.
  • 1.2: two-way feedback by polling the matrix web page, route verification with automatic re-send.
  • 1.0 to 1.1: TCP 5000 control with reconnect, serial fallback, batch window, latest-route-wins, paced queue, offline hold.

Still stuck? Ask Fixxy (bottom right) or open a ticket.