Extron Velocity — Browser-Based AV Control Platform

Velocity is Extron's simplified, server-based AV control platform targeting education and small-to-medium corporate environments where speed of deployment, centralized management, and standardization across many rooms are priorities. Unlike Global Configurator (GCP) — which requires Windows software, device-by-device programming, and upload to each IPCP Pro — Velocity is managed entirely from a web browser and can deploy a room control program in minutes using pre-built room templates. Velocity does not replace GCP for complex custom installations, but for standardized room types (huddle space, medium conference room, lecture hall) it dramatically reduces deployment time per room.

See control-systems/extron-basics for the Extron platform overview and control-systems/extron-globalscripter for GCP programming used in more complex installations.

Velocity Architecture

Components

Velocity has three hardware/software components:

1. Velocity Hub The central server that hosts the Velocity software, stores all room configurations, and pushes programs to connected control processors. Available as:

• Velocity Hub 100 — dedicated hardware appliance (1U rack); the recommended production deployment
• Velocity Software on Windows PC — for evaluation, small deployments, or IT-managed server environments

The Hub must be on the same network (or routable to) all Velocity-controlled rooms. It communicates with control processors over standard TCP/IP.

2. Velocity-Compatible IPCP Pro Velocity runs on select IPCP Pro models with Velocity firmware support. Not all IPCP Pro models support Velocity — confirm model compatibility in the Extron spec sheet. Compatible processors receive their programming from the Velocity Hub over the network; no local program upload via Toolbelt is required after initial firmware setup.

3. Browser-Based Management Interface All configuration, programming, and monitoring happens through a web browser pointed at the Velocity Hub's IP address. No installed software required on the administrator's computer — works from any device with a modern browser (Chrome recommended).

Scalability

• One Velocity Hub 100 supports up to 100 rooms (100 connected IPCP Pro processors)
• Multi-Hub deployments using Velocity Enterprise scale to enterprise-wide installations
• All rooms share a common device library and room templates, ensuring consistency across a campus

Setting Up Velocity

Initial Hub Configuration

1. Rack-mount and power the Velocity Hub 100
2. Connect to the management network (separate from AV control network recommended)
3. Navigate to http://[HubIP] from any browser on the same network
4. Default credentials: admin / admin1 — change immediately on first login
5. Set Hub network settings (static IP recommended for production)
6. Configure the AV network subnet so the Hub can reach IPCP Pro processors

Adding Control Processors

1. In the Velocity browser interface, go to Processors → Add Processor
2. Enter the IPCP Pro's IP address
3. Velocity Hub contacts the processor — if firmware is Velocity-compatible, it appears as online
4. If the processor is running standard GlobalScripter firmware, update to Velocity firmware via Toolbelt first (one-time operation per processor)

Device Library

Velocity includes a cloud-synchronized device library with thousands of device drivers — the same scope as GCP's device module library. Drivers are updated from Extron's cloud automatically when the Hub has internet connectivity; offline updates are available for air-gapped networks.

Add devices to the Velocity library:

1. Devices → Add Device
2. Search by manufacturer + model
3. Select communication method and port assignment
4. Device appears in the library for use across all room templates

Room Templates

Room templates are the core productivity feature of Velocity. A template defines the complete room control program for a room type — devices, touchpanel layout, button logic, automation behaviors — as a reusable pattern.

Template Types

Velocity ships with pre-built templates for common room types:

Templates are fully customizable — they serve as starting points, not fixed configurations.

Customizing a Template

1. Select a template from the library
2. Assign the specific devices in this room to the template's device slots (e.g., assign "Sony VPL-PHZ10" to the "Projector" slot)
3. Customize the touchpanel page layout in the Visual Editor (see below)
4. Add or modify automation behaviors (e.g., auto-shutdown after 30 minutes idle)
5. Save the template as a room configuration

Deploying a Room Configuration

1. Rooms → Create Room
2. Select the room template
3. Assign a Velocity-compatible IPCP Pro processor to the room
4. Assign a touchpanel (TLP Pro) to the room
5. Click Deploy — Velocity pushes the complete program to the IPCP Pro over the network
6. Deployment takes 30–90 seconds; the room is live immediately after

This workflow replaces the GCP workflow of: opening GCP on Windows → building the program → saving → uploading via Toolbelt → waiting for processor restart. A Velocity room deployment is faster from first template to live room.

Visual Editor — Touchpanel Design

Velocity includes a browser-based Visual Editor for TouchLink Pro panel page design. It is less powerful than GCP's panel designer but sufficient for standard room control interfaces.

Visual Editor Capabilities

• Drag-and-drop button placement on a pixel canvas
• Pre-built button styles (on/off, source select, volume, mute)
• Background image upload (room photo, company logo, floor plan)
• Dynamic label binding (show current input name, room name, time)
• Multi-page navigation (home page → source selection page → settings page)
• Button color and active/inactive state styling

Visual Editor Limitations vs. GCP

• No custom scripting within the panel designer
• No conditional visibility (showing/hiding elements based on device state) — available only through template automation logic
• Limited font and typography control
• Cannot create complex animation or transition effects

For rooms requiring advanced panel features, GCP/GCPro remains the tool of choice.

Automation and Scheduling

Built-in Automation Behaviors

Velocity templates include configurable automation behaviors:

• Auto-shutdown: System powers off all devices after N minutes of inactivity (no button press, no signal detected)
• Warm-up / cool-down: Projector warm-up delay before enabling full room control; cool-down period before power-off confirmation
• Occupancy-based control: Integration with occupancy sensor inputs — room activates on occupancy, shuts down on vacancy
• Scheduled events: Power on/off at specific times (morning startup, end-of-day shutdown)
• AV mute: Blank all displays and mute audio without powering down (privacy mode)

Calendar and Room Booking Integration

Velocity supports integration with room booking systems via API:

• Microsoft Exchange / Office 365: Velocity can query Exchange calendars to display meeting titles and end times on the room touchpanel
• Google Calendar: Similar integration via Google Calendar API
• Custom REST API: Velocity can poll any REST endpoint for room status data

Calendar integration is configured in the Velocity Hub settings under Integrations → Calendar. The Hub polls the calendar API at a configured interval and pushes meeting data to room processors.

Velocity vs. Global Configurator — Decision Guide

The typical enterprise campus deployment: Velocity for the 80 standard conference rooms, GCP for the 3–5 executive boardrooms and auditoriums with custom requirements.

Monitoring and Management

The Velocity Hub provides a centralized monitoring dashboard:

• Room status: Online/offline for all connected processors
• Active sessions: Which rooms are currently in use
• Alert history: Device offline events, connection failures, program errors
• Remote control: Send commands to any room from the Hub browser interface (useful for IT helpdesk)
• Bulk operations: Push a template update to 50 rooms simultaneously — one change propagates everywhere instantly

This centralized management is Velocity's key advantage for IT departments managing large room counts. A firmware update to a display or a button label change can be deployed to all 80 rooms in one operation from the Hub.

Common Pitfalls

• Velocity firmware ≠ standard IPCP Pro firmware. Velocity-capable IPCP Pro processors must run Velocity firmware — different from the standard GlobalScripter firmware used with GCP. A processor running standard firmware will not connect to the Velocity Hub. The one-time firmware conversion is done via Toolbelt; after conversion, the processor is managed exclusively by Velocity and cannot run standalone GCP programs. Do not convert IPCP Pros in complex custom rooms to Velocity firmware.

• Room template customization not saved before deployment. Velocity's browser interface doesn't auto-save template edits. Closing the browser tab or navigating away loses unsaved changes. The deployed room runs the last saved template version, not the current editing state. Save explicitly before deploying, and confirm the deployed program version matches the intended template revision.

• Velocity Hub on wrong network segment. The Velocity Hub must be able to reach all IPCP Pro processors via TCP/IP. If the Hub is on the IT management VLAN and IPCP Pros are on an isolated AV VLAN with no inter-VLAN routing, the Hub cannot discover or push programs to processors. Plan the network with Layer 3 routing between the Hub's VLAN and the AV control VLAN, or place the Hub on the AV VLAN.

• Device library not updated on air-gapped network. Velocity's device library updates automatically from Extron's cloud. In government, healthcare, and education networks with no internet access from the AV control infrastructure, the library freezes at its last update. New device drivers must be downloaded manually from Extron's website on an internet-connected PC and imported into the Hub. Plan for this in secured environments.

• Template changes push to all rooms simultaneously. Velocity's bulk deployment is powerful but dangerous without testing. Pushing a template update with a bug to 80 rooms simultaneously renders all 80 inoperable at once. Always test template changes on a single room first, verify functionality, then propagate. Use Velocity's room group feature to deploy to a subset before the full fleet.

• Transitioning a Velocity room to GCP for custom requirements. If a room's requirements grow beyond Velocity's capabilities (complex state machines, custom device protocols), the IPCP Pro must be converted back to standard firmware via Toolbelt. This wipes the Velocity-pushed program. The room then requires full GCP programming from scratch — there is no export of Velocity configuration to GCP format. Plan room complexity requirements before committing to Velocity.