From download
to verified output.

Account and license

Get your portal account.

1. Purchase a license or receive a demo account from BroadcastPilot.
2. Sign in at the customer portal with the email and password supplied during registration.
3. Open Subscriptions and select the eye icon beside the protected product key.
4. Copy the complete product key. Confirm that your station’s FCC call sign appears under Licensed stations.

The call sign entered in the application must match a call sign covered by the license.

Install

Install the correct version.

Windows 64-bit

1. Download the Windows `.exe` from the home page.
2. Run the installer and approve the Windows security prompt.
3. Open BroadcastPilot from the Start menu.

Ubuntu Linux 64-bit

1. Download the Ubuntu `.deb` from the home page.
2. Open a terminal in the download folder.
3. Run sudo apt install ./BroadcastPilot-Linux-vVERSION-buildNUMBER-amd64.deb.
4. Open BroadcastPilot from the application menu.

Product access

Activate the computer.

1. Connect the BroadcastPilot computer to the internet.
2. Open Settings → Product Access.
3. Enter the organization and licensed station call sign.
4. Paste the product key and select Activate online.
5. Confirm the page reports an active license and the expected expiration date.

One computer is included. Contact BroadcastPilot before replacing the licensed computer so its previous activation can be released.

Station outputs

Configure each station route.

1. Open Station Outputs and add an output for each station you operate.
2. Select the station profile and the imported Guide schedule to send.
3. Enter the exact call sign, virtual major and minor channel, program number, source ID, and TSID using the station’s approved engineering values.
4. Choose the PSIP ownership profile agreed with the multiplexer configuration.
5. Enter that station’s destination IP address, port, and network interface.
6. Confirm the selected schedule shows imported events, then save and export a configuration backup.

Important: Each output is independent. Confirm its station and schedule selections before transmission. BroadcastPilot and the multiplexer must never generate the same PSIP tables at the same time.

Program guide

Import and assign each schedule.

1. Open Schedule → Import schedule.
2. Choose Excel weekly grid, CSV, JSON, or XMLTV.
3. Select the correct station channel and schedule date range.
4. Import and validate the schedule, then repeat for each additional station.
5. Review warnings, gaps, overlapping events, program titles, descriptions, and start times.
6. Return to Station Outputs and select the correct guide schedule for every route.

BroadcastPilot displays the number of matching events beside each route’s schedule selection. A route cannot start when its selected schedule contains no imported events.

Live operation

Start the selected station output.

1. Open Live Output & Testing.
2. Select the validated station route.
3. Confirm the station, guide event count, destination, port, network interface, bitrate, and PSIP profile.
4. Confirm the destination acknowledgment.
5. Select the prominent Start output control.
6. Confirm the application displays a green ACTIVE status and that packet and byte counters increase.

Only the station and guide schedule assigned to the selected route are transmitted. A healthy local sender does not by itself prove receipt downstream.

Commissioning

Verify the completed signal.

1. In the guided station setup, open Test and run the built-in PSIP Analyzer.
2. Review its EIT/ETT sections, PIDs, schedule coverage, event durations, descriptions, gaps, overlaps, packet structure, and CRC result.
3. After the local analyzer passes, inspect the live stream at the receiving equipment or another transport analyzer.
4. Confirm STT, MGT, TVCT, EIT, and ETT are present according to the selected profile.
5. Check for continuity and TEI errors through the completed signal path.
6. Verify the final result from an off-air receiver when the equipment supports the guide tables.

A BroadcastPilot analyzer pass proves that the locally generated data is structurally valid. It does not prove that downstream equipment passes the tables or that the off-air signal is clean.

If guide tables are duplicated, stop output and recheck PSIP ownership in both BroadcastPilot and the receiving equipment.