title: Extron XTP, DTP, FOX3, and NAV Pro — Signal Distribution description: Deep dive into Extron's signal distribution platforms: XTP (HDBaseT matrix routing), DTP (point-to-point HDBaseT), FOX3 (fiber optic extension), and NAV Pro (10GbE AV-over-IP), covering system design, cabling, and platform selection. tags: [control-systems, extron, xtp, dtp, fox3, nav-pro, hdbaset, fiber, av-over-ip, 10gbe, signal-distribution, video] created: 2026-05-04 status: current review_by: 2027-05-04

Extron XTP, DTP, FOX3, and NAV Pro — Signal Distribution

Extron offers four signal distribution platforms serving different scale and infrastructure requirements: XTP for large-scale HDBaseT matrix systems, DTP for point-to-point HDBaseT extension, FOX3 for fiber optic extension beyond copper distances, and NAV Pro for AV-over-IP at 10GbE. Understanding which platform fits a given project — and the specific technical requirements of each — is essential for accurate specification and reliable commissioning. All three platforms are Extron-proprietary to varying degrees: XTP is fully proprietary, DTP is proprietary but simpler, and NAV Pro uses standard IP networking infrastructure.

See control-systems/extron-basics for the Extron platform overview and control-systems/extron-sis-protocol for SIS commands used to manage these products.

XTP — CrossPoint Transport Protocol

What XTP Is

XTP is Extron's HDBaseT-based proprietary video distribution platform for large-scale matrix routing. An XTP system consists of:

• XTP transmitters — encode the source signal (HDMI, VGA, DisplayPort) for transport over Cat cable
• XTP CrossPoint chassis — the central matrix that routes XTP signals between any input and output
• XTP receivers — decode the transported signal back to HDMI at the display

All three components must be Extron XTP products — XTP does not interoperate with third-party HDBaseT equipment despite using the same physical cabling standard.

XTP Signal Payload

Each XTP cable carries the full AV system payload in a single Cat 6A run:

• Video — HDMI up to 4K60 (generation-dependent, see below)
• Audio — embedded HDMI audio passes through transparently
• Bidirectional RS-232 — control signal from IPCP Pro to display, or display feedback to control system
• Bidirectional IR — remote control pass-through
• Ethernet — 100 Mbps Ethernet channel alongside video (on XTP2 and XTP3)
• PoE — power for the XTP receiver at the display (eliminates local power supply)

This "all on one cable" characteristic is XTP's primary value proposition: a single Cat 6A run replaces HDMI, control cable, network drop, and power run to each display location.

XTP Generations

XTP3 backward compatibility: XTP3 transmitters and receivers are backward compatible with XTP2 chassis — they operate at XTP2 resolutions (4K60 4:2:0) when connected to an XTP2 chassis. For full 4K60 4:4:4, the entire chain (transmitter, chassis, receiver) must be XTP3.

XTP CrossPoint Chassis

Chassis are modular — I/O cards slot into the chassis backplane. Card types include XTP input/output, HDMI local I/O (for sources/displays at the rack), analog I/O (for legacy equipment), and FOX3 fiber I/O (for runs beyond 100m or requiring electrical isolation — see FOX3 section below). This modularity allows a single chassis to serve mixed-signal environments.

XTP Cabling Requirements

• Cable type: Cat 6A (minimum) — Cat 5e is not supported for 4K distances; Cat 7 is acceptable
• Maximum distance: 100 meters (328 feet) on Cat 6A for all XTP generations
• Termination: T568B standard RJ45 — consistent termination throughout; mixing T568A and T568B on the same run causes failures
• Cable routing: Avoid running XTP cable parallel to AC power runs (maintain 6" minimum separation, or use shielded Cat 6A in electrically noisy environments)
• Solid-core vs. stranded: Solid-core preferred for in-wall runs; stranded for patch cables only. Stranded cable has higher attenuation and reduces effective distance.
• No passive patch panels on XTP runs: Every passive punch-down or keystone connector adds impedance discontinuity. XTP runs from transmitter to chassis should be home-run where possible. If patch panels are required, use Extron HDMI/XTP-compatible panels.

XTP System Design Workflow

1. Inventory sources and displays: Count HDMI inputs (laptops, cameras, PCs) and outputs (displays, projectors)
2. Select chassis size: Choose XTP CrossPoint chassis with 20–30% spare I/O capacity
3. Match transmitter/receiver to source: XTP DTP transmitters for wall plates; XTP matrix I/O cards for rack-mounted sources
4. Select XTP generation: XTP3 for new projects requiring 4K60 4:4:4; XTP2 acceptable for 4K60 4:2:0
5. Plan cabling: Home-run Cat 6A from each source location to the rack; home-run to each display
6. Control integration: IPCP Pro connects to XTP CrossPoint via RS-232 or SIS over IP; GCP device module handles routing commands

XTP Audio

XTP passes embedded HDMI audio transparently — sources with HDMI audio (PCs, Blu-ray, media players) deliver audio to displays through the XTP chain without modification. For separate audio routing (independent audio matrix, amplified zones), the HDMI audio is typically extracted at the CrossPoint chassis via an audio de-embedder card or external de-embedder, then routed to a separate DMP or third-party DSP.

DTP — Differential Transport Protocol

What DTP Is

DTP is Extron's point-to-point HDBaseT extension system. Unlike XTP (which routes through a central matrix), DTP connects a single source directly to a single display over Cat cable. DTP is the correct choice when:

• Only one source needs to reach one display
• Budget doesn't justify XTP infrastructure
• Distances are up to 100m but no matrix routing is needed

DTP Product Lines

DTP2 HD 4K 330 is the current recommended product for new DTP deployments — it achieves 4K60 4:4:4 at 100m on Cat 6A, matching XTP3 performance for point-to-point runs.

DTP Distribution Amplifiers

For one-to-many distribution (same source to multiple displays) without full matrix routing:

• DTP2 HDMI DA4K 4 — 1 DTP2 input, 4 DTP2 outputs. Distribute one source to 4 displays over Cat 6A.
• DTP HDMI 4K 230 DA4 — Budget option for 4:2:0 distribution

Distribution amplifiers are common in digital signage, wayfinding, and multi-display installations where a single content source feeds multiple screens in a zone.

DTP Wall Plates

DTP transmitters are available as wall plate form factors for clean BYOD connections at conference tables and lecterns:

• DTP2 T HWP 4K 331 — HDMI + USB-C wall plate transmitter; single-gang; PoE powered from receiver
• DTP2 T HWP 4K 232 — HDMI wall plate; compact design
• MediaPort 200 — HDMI + USB-C + audio combination connectivity panel; integrates with Extron control

Wall plates eliminate visible cable management at the table surface — the only visible hardware is the wall plate itself; the Cat 6A run is concealed in the table or wall.

DTP vs. XTP Selection Guide

NAV Pro — AV-over-IP at 10GbE

What NAV Pro Is

NAV Pro is Extron's AV-over-IP platform for large-scale video distribution over standard IP networking infrastructure. Instead of proprietary HDBaseT cabling, NAV Pro uses 10GbE Ethernet — the same network infrastructure used for IT data. Encoders convert HDMI sources to IP multicast streams; decoders receive those streams and output to displays. Routing (which encoder feeds which decoder) is managed by the NAV Pro SW software.

NAV Pro is the correct platform when:

• The installation exceeds XTP chassis capacity (64×64)
• Flexible any-to-any routing is needed beyond a fixed matrix size
• The facility already has 10GbE networking infrastructure
• Future expansion is planned and adding I/O cards to a chassis is not practical

NAV Pro Video Quality

NAV Pro uses visually lossless compression — not uncompressed transport like SDVoE. The compression ratio is low enough that artifacts are imperceptible in practice, and the video quality is indistinguishable from direct HDMI to the human eye at normal viewing distances. This is a key differentiator from compressed AV-over-IP (H.264/H.265 based) platforms that trade quality for bandwidth efficiency.

NAV Pro Product Family

The NAV Pro SW software provides a virtual matrix interface — operators can route any encoder to any decoder (or multiple decoders) through a graphical routing grid, equivalent to a software CrossPoint.

10GbE Network Architecture for NAV Pro

NAV Pro has strict network requirements. Non-compliance is the primary cause of field failures — dropped frames, no video, or intermittent signal loss.

Switch Requirements

• 10GbE switching throughout: All ports connecting NAV Pro encoders, decoders, and inter-switch uplinks must be 10GbE. 1GbE ports cannot carry 4K NAV Pro streams.
• IGMP snooping: Must be enabled on all switches in the NAV Pro VLAN. NAV Pro uses IP multicast for one-to-many distribution — without IGMP snooping, multicast floods all ports, saturating all 10GbE links.
• IGMP querier: Exactly one switch in the VLAN must act as the IGMP querier. If no querier is present, IGMP group memberships time out and streams stop. If multiple queriers exist, IGMP elections create instability. Designate one switch as querier — typically the core/distribution switch.
• MTU 9000 (Jumbo Frames): Must be enabled on all switch ports in the NAV Pro VLAN. NAV Pro uses large packet sizes for efficiency; standard 1500-byte MTU causes fragmentation and severe performance degradation.
• QoS / DSCP marking: Mark NAV Pro traffic with DSCP EF (Expedited Forwarding, DSCP 46) or a dedicated queue to ensure video traffic is prioritized over background data on shared infrastructure.

Recommended Switches for NAV Pro

Avoid: Unmanaged 10GbE switches (no IGMP snooping), entry-level managed switches with incomplete IGMP querier support, consumer-grade 10GbE NICs in encoding/decoding hardware.

VLAN Design for NAV Pro

Isolate NAV Pro traffic on a dedicated VLAN:

VLAN 10 — NAV Pro Video (10GbE ports: all encoders, decoders, uplinks)
VLAN 20 — AV Control (IPCP Pro, NAV Pro SW server, management)
VLAN 30 — General IT / Corporate

Inter-VLAN routing between VLAN 10 and VLAN 20 must be enabled so the NAV Pro SW software (on VLAN 20) can communicate with encoders and decoders (on VLAN 10). The NAV Pro SW server needs Layer 3 access to both VLANs — either dual NIC or a managed router/firewall allowing specific traffic between VLANs.

NAV Pro Bandwidth Planning

A 10GbE switch port can carry approximately 1 × 4K60 stream or 4–5 × 1080p60 streams. For large deployments with many simultaneous streams, uplink capacity between switches must be planned — consider 40GbE or 100GbE uplinks between access and distribution switches.

NAV Pro SW Routing Software

NAV Pro SW is a Windows-based software application that serves as the routing controller for the NAV Pro platform. It:

• Discovers all NAV Pro encoders and decoders on the network automatically via multicast discovery
• Presents a routing matrix (encoders as rows, decoders as columns) for manual and automated routing
• Accepts routing commands via REST API — enabling GCP automation or third-party control
• Manages stream multicast addresses automatically — no manual multicast group assignment needed
• Provides system status: encoder/decoder online/offline, stream active/inactive, network health

NAV Pro SW REST API: Third-party control systems can send HTTP POST requests to NAV Pro SW to change routing:

POST /api/route
Body: { "encoder": "Encoder1", "decoder": "Decoder3" }

This allows GCP scripts or external room booking systems to route NAV Pro streams as part of room automation.

NAV vs. NAV Pro Comparison

Existing NAV installations remain in service and are supported. New projects should specify NAV Pro exclusively.

FOX3 — Fiber Optic Extension

What FOX3 Is

FOX3 is Extron's fiber optic signal extension platform for HDMI video distribution over multi-mode or single-mode fiber. Where XTP and DTP use Cat 6A copper cable limited to 100 meters, FOX3 uses fiber to achieve distances up to 400 meters on multi-mode fiber and up to 10 kilometers on single-mode fiber. FOX3 is the correct platform when:

• Runs exceed 100 meters (copper HDBaseT maximum)
• Electrical isolation is required between source and display (ground loop elimination, lightning protection, medical/laboratory environments)
• The signal path crosses buildings where direct copper burial is impractical or code-prohibited
• EMI/RFI immunity is needed (broadcast studios, RF-dense environments, manufacturing floors)

FOX3 Product Family

FOX3 transmitters and receivers ship as matched pairs. TX connects at the source end; RX connects at the display end. Both are powered — either from local power supplies or, on supported models, PoE from the RX side.

FOX3 Signal Payload

Like XTP and DTP, FOX3 carries the full AV payload on a single fiber run:

• Video — HDMI up to 4K60 4:4:4 (FOX3 330 series)
• Audio — embedded HDMI audio passes through transparently
• Bidirectional RS-232 — control pass-through (display control from IPCP Pro or GCP)
• Bidirectional IR — remote control pass-through
• USB (select models) — USB 2.0 extension for peripherals

RS-232 pass-through over fiber is particularly valuable in installations where the display is far from the control system — the IPCP Pro can still send power/input commands to the remote display without a separate control cable.

FOX3 Integration with XTP Chassis

FOX3 is not a standalone product only — fiber I/O cards for XTP CrossPoint chassis allow long-distance fiber runs to be terminated directly into the matrix:

• FOX3 XTP fiber I/O cards — Slot into XTP CrossPoint chassis backplane. Provide SFP ports for fiber connections from remote FOX3 transmitters or receivers.
• This allows a source 2 km away (via single-mode fiber) to appear as an XTP input on the CrossPoint matrix — routable to any display in the system.
• Commonly used in multi-building campuses: the central equipment room houses the XTP CrossPoint; fiber runs connect to FOX3 transmitters in remote buildings.

Fiber Types and Cabling

Multi-mode fiber (OM3 / OM4)

• Orange (OM3) or aqua (OM4) jacket
• LC connectors (standard for FOX3)
• Maximum distance: 400 m on OM4; 300 m on OM3
• Lower cost than single-mode; easier to terminate on-site
• Best for within-building long runs: auditoriums, gymnasiums, data center–to–display, AV closet–to–room on upper floors

Single-mode fiber (OS2)

• Yellow jacket
• LC connectors
• Maximum distance: 10 km
• Higher cost; requires precision cleaving and polishing for field termination (prefer pre-terminated assemblies)
• Best for building-to-building: campus networks, outdoor conduit runs, between floors in very tall buildings

Fiber cabling best practices:

• Use pre-terminated fiber assemblies (factory-made) rather than field-terminated where possible — consistent end-face quality, guaranteed insertion loss
• Indoor/outdoor-rated fiber for runs that pass through building envelope — standard indoor fiber is not rated for outdoor UV exposure or temperature swings
• Bend radius: minimum 10× cable diameter for multi-mode; 15× for single-mode; avoid sharp bends at conduit entry points
• Label both ends of every fiber with source/destination and fiber count
• Test with an OTDR (Optical Time Domain Reflectometer) or optical power meter after installation; insertion loss budget for FOX3 MM is typically < 3 dB

Electrical Isolation — Why Fiber Matters

Fiber is non-conductive. This makes FOX3 the correct solution in several scenarios where copper fails:

Ground loops — Two pieces of equipment connected by copper cable in different parts of a building, or on different electrical circuits, develop a ground potential difference. This manifests as video noise, hum bars, color shifts, or complete signal loss. Fiber carries no ground reference — the signal transmits optically across complete electrical isolation. FOX3 eliminates ground loop failures by design.

Lightning protection — Building-to-building copper cable runs are a lightning strike path. A strike on one building travels through the copper to equipment in the other building, destroying both endpoints. Fiber in a conduit between buildings carries no electrical current — a strike on one building cannot damage equipment in the other via the fiber run. (The conduit itself should still be bonded per NEC.)

Medical and laboratory environments — Patient care areas and certain lab environments have strict isolation requirements for electrical equipment. Fiber signal paths between equipment satisfy isolation requirements that copper cannot.

High EMI environments — Broadcast studios near RF transmitters, manufacturing floors near motors and welding equipment, and server rooms with dense switching generate EMI that induces noise on copper signal cables. Fiber is immune to electromagnetic interference.

FOX3 vs. DTP vs. XTP — Distance and Use Case Summary

Platform Comparison and Selection Guide

Common Pitfalls

• XTP transmitter/receiver mixed with non-Extron HDBaseT equipment. XTP is proprietary — XTP transmitters must connect to XTP CrossPoint chassis inputs, and XTP chassis outputs must connect to XTP receivers. Plugging an XTP transmitter into a third-party HDBaseT receiver produces no signal. This surprises installers who expect all HDBaseT equipment to interoperate. If interoperability with non-Extron equipment is needed, use DTP (which is also proprietary) only for point-to-point Extron-to-Extron runs, or specify standard HDMI with separate HDBaseT extenders.

• NAV Pro on 1GbE infrastructure. The single most common NAV Pro deployment failure. 1GbE switch ports cannot carry 4K60 NAV Pro streams — the bandwidth overflows immediately. Symptoms: dropped frames, no video, or extremely degraded image quality. Confirm every port in the path (encoder NIC, switch port, inter-switch uplink, decoder NIC) is 10GbE before deployment. Budget for 10GbE infrastructure upgrades — they often cost more than the NAV Pro equipment itself.

• MTU 9000 not enabled on NAV Pro VLAN. Jumbo frames are mandatory for NAV Pro. Default switch MTU is 1500 bytes. NAV Pro encoders send large packets that exceed 1500 bytes; the switch fragments them, causing severe stream degradation. Enable MTU 9000 on every switch port in the NAV Pro VLAN — access ports, trunk ports, and uplinks. Verify with ping -s 8972 [NAV Pro device IP] — packets at this size should pass without fragmentation.

• No IGMP querier configured. IGMP group memberships have a timeout — if no querier sends IGMP general queries, memberships expire and multicast stops flowing to decoders. Symptoms appear minutes after system startup as streams drop one by one. Designate exactly one switch as IGMP querier per VLAN. On Cisco switches: ip igmp snooping querier on the SVI for the NAV Pro VLAN. On NETGEAR M4250: enable querier in the IGMP snooping settings.

• DTP cable length exceeded with Cat 5e. DTP2 HD 4K 330 achieves 100m only on Cat 6A. Using Cat 5e limits reliable distance to 40–70m depending on cable quality and environment. Longer runs with Cat 5e produce intermittent signal loss, HDCP failures, and resolution fallback. Always specify Cat 6A for DTP and XTP runs, and verify installed cable category before commissioning.

• XTP straight-through vs. crossover cable confusion. XTP uses a straight-through (T568B to T568B) Cat cable — the same as standard Ethernet patch cable. Some older HDBaseT equipment requires crossover wiring; do not apply that assumption to XTP. Inconsistent termination standards (mixing T568A and T568B across a run through patch panels) causes signal loss at higher frequencies.

• FOX3 fiber type mismatch. Multi-mode FOX3 TX/RX pairs will not work with single-mode fiber, and vice versa. The transceivers are physically incompatible — multi-mode uses an LED light source (850 nm), single-mode uses a laser (1310 nm). Specifying FOX3 MM transmitters with OS2 single-mode fiber installed in conduit produces no signal. Confirm fiber type in conduit (check cable jacket color and documentation) before specifying FOX3 models. When in doubt, pull a single-mode cable — it works at shorter distances too, and SM fiber costs only marginally more than MM for the cable itself.

• Fiber insertion loss budget exceeded. A poorly-terminated or damaged fiber connector adds 0.5–1.5 dB of insertion loss per connector, compared to 0.1–0.3 dB for a good factory termination. FOX3 has a maximum allowable optical loss budget (typically 3 dB for MM, 6 dB for SM). Multiple bad field terminations, patch panel connections, or a damaged fiber section can exceed this budget, causing intermittent signal loss or no signal. Test with an optical power meter before connecting FOX3 equipment — verify insertion loss is within spec.