Skip to content
You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
You are viewing the article in preview mode. It is not live at the moment.

⚠️  JADConfig will reach End of Support on January 1, 2027. View the official notice!   ⚠️

Download Advanced Matrix Programmer (AMP) (2G Legacy Mode, Omega, Ultra, and MaxColor Series)

Overview

Advanced Matrix Programmer (AMP) configures Just Add Power Encoders and Decoders into an HDMI matrix switching system. It supports Omega Series, Ultra Series, and MaxColor Series systems through Standardized Configuration and Alternate Configuration. Supported 2G Series systems use Standardized Configuration through AMP 2G Legacy Mode.

AMP 2.0.1 resolves TP-Link configuration file rejection and Luxul SW-505 configuration and service failures reported in AMP 2.0.0. This release also improves device discovery, switch communication, gateway detection, and device-to-port matching.

Latest AMP Version: v2.0.1

Release Date: October 27, 2026

Recommended Setup: Standardized Configuration

All new systems must use AMP. JADConfig is intended only for established systems and reaches End of Support on January 1, 2027. Review the JADConfig End of Support notice and migration requirements when planning service or conversion.

System Configuration Options

Standardized Configuration (Recommended)

AMP configures supported managed switches and Just Add Power Encoders and Decoders together. Standardized Configuration uses VLAN Switching and can also accommodate standard network devices on extra switch ports.

  • Supports Omega Series, Ultra Series, and MaxColor Series systems.
  • Supports 2G Series systems through AMP 2G Legacy Mode.
  • Requires switches from the Standardized Configuration supported switch list.
  • Select Build & Expand to begin configuration.
  • Supports up to 63 switches, 101 Encoders, and 3023 Decoders.

2G Legacy Mode: Requires Standardized Configuration. AMP applies L Series firmware to 2G Series devices and compatible Omega Series and Ultra Series devices during configuration. Review 2G Legacy Mode hardware compatibility and capability limitations before planning the system.

Ruckus Switch Restriction: Ruckus switches are not supported in AMP 2G Legacy Mode. For systems that include 2G Series devices, select a supported switch from another manufacturer.

Alternate Configuration

AMP configures the Encoders and Decoders only. The installer or network administrator configures the switches and network for Multicast Switching.

  • Supports Omega Series, Ultra Series, and MaxColor Series systems.
  • Does not support AMP 2G Legacy Mode.
  • Requires a network that meets the Multicast Switching minimum requirements.
  • Select Alternate Configuration from the bottom-left corner of AMP to begin.
  • Supports up to 9,999 Encoders and an unlimited number of Decoders, depending on network design.

For strengths, tradeoffs, and use cases, see Choosing between Standardized and Alternate Configurations.

Before You Begin

Confirm device compatibility, switch support, network capacity, and control-system requirements before configuration.

If you are converting an established JADConfig system to AMP, complete the preparation steps for your system before changing its configuration:

Download AMP

Download AMP and access training materials below. Review the Known Issues before configuring or servicing a TP-Link system.

Version Information

This section lists device firmware information and release notes for the current version of AMP. For previous versions, see AMP Release History.

Device Firmware

  • Omega Series and Ultra Series: B3.2.0 for normal series operation.
  • MaxColor Series: MAX v4.5.0.
  • AMP 2G Legacy Mode: L1.1.9.0 for 2G Series devices and compatible Omega Series and Ultra Series devices.

v2.0.1 — October 27, 2026

Added

  • Organized TP-Link Omada and JetStream switch models with clearer dropdown labels, including SG3428 and SG3452 variants.
  • Tools to map expected device IP addresses to switch ports and identify connected switch and port information.
  • A loading indicator during gateway reachability checks.
  • Tracking for legacy-mode preferences.

Changed

  • Device discovery now verifies network reachability and firmware compatibility before retrieving device identifiers.
  • Patching checks now prioritize the expected switch port when a device's MAC address appears on multiple ports.
  • Gateway reachability checks now test multiple network ports instead of relying only on port 80.
  • Improved Luxul Telnet communication with controlled timeouts and consistent credential handling.
  • Improved network ID calculations to handle invalid network data safely.
  • Removed outdated IGMP setup disclaimers.

Fixed

  • Resolved TP-Link configuration file rejection caused by an incorrect TL- model prefix in AMP 2.0.0.
  • Resolved the firmware validation issue that prevented Build & Expand and Service functions from working with Luxul SW-505 Series switches in AMP 2.0.0.
  • Corrected discovery skipping unexpected devices when expected devices timed out or were unreachable.
  • Resolved duplicate device rows, duplicate MAC entries, and inaccurate device counts during discovery.
  • Corrected device IP-to-switch-port matching and expected-port validation.
  • Corrected gateway reachability checks failing when port 80 is closed.
  • Resolved Telnet timeout leaks when managing multiple switches concurrently.
  • Video playback now resumes automatically after leaving device discovery or reopening AMP.
  • Corrected styling and prevented unintended clicks on disabled buttons, switch controls, and menu items.

Known Issues

TP-Link Switching and AMP Services

Certain newer TP-Link switch firmware versions prevent matrix switching and AMP service functions from working correctly in Standardized Configuration systems.

This issue remains present in AMP 2.0.1. A fix is expected in AMP 2.1.0.

Workaround: Return the switch to supported firmware using the maximum firmware table and TP-Link rollback instructions. Re-uploading the switch configuration file is not required.