Bitfocus AS
logo
logo
Bitfocus AS
logo
logo
Sign upSign in

Loading...

Bitfocus

Subscribe to our newsletter

The latest news, articles, and resources, sent to your inbox.

FacebookInstagramGitHubYouTubeLinkedIn

Products

  • Buttons
  • Companion

Integrations

  • Supported Devices
  • Developer Community
  • Connection Development

Support

  • Support Overview
  • Documentation
  • Video Tutorials
  • Community Forum

Sales

  • Resellers & Integrators
  • Buttons Pricing

Updates

  • Case Studies
  • Events & Trade Shows
  • Press Releases
  • Product Updates
  • Webinars

Legal

  • Legal Overview
  • Privacy Policy
  • Buttons EULA
  • Terms & Cookie Policy

Company

  • About us
  • Press kit
  • Careers

© 2026 Bitfocus AS. All rights reserved.

Utah Scientific BPS
Docs for
Overview
Getting started
What is Bitfocus Buttons?
Install Buttons and get started
Manage your Buttons license
Activate Buttons offline
Find your way around Buttons
Create your first backup
Add an ATEM connection
Choose a control method
Choose an installation path
Install Buttons on Debian or Ubuntu
Understand HA clustering
Kubernetes HA
Update or remove Buttons
Positions
Understand positions
Create a position
Add controls and sections to a position
Create your first button
Use a connection's presets
Build more capable button actions
Add more feedback to a button
Organize controls in a section
Shift Section
Organize controls with a Folder Section
Add a Popover Section
Build and reuse a Shared Section
Build a Router Section
Understand Custom Routers
Custom Router panel
Surfaces
Surface compatibility
Add and attach a surface
Device orientation
Connections
Update a connection's module safely
Monitor and troubleshoot a connection
Router integrations
VideoHub and AJA KUMO
Utah Scientific BPS
Generic SW-P-08
Nevion VideoIPath
Arkona BLADE//runner
Routing
Physical routing
Configure ports and labels
Take a physical route
Understand route status
Topology graph
Routing Presets
Get started with virtual routing
Configure Nested Shapes
Reverse routing
Tielines
Routing Projects
Routing settings
Troubleshoot a route
Tally
Understand the Tally system
Send ATEM tally and labels to a UMD
Interpret Active Tally state
TSL/UMD connections
Diagnose tally problems
NMOS
Understand NMOS in Buttons
Connect Buttons to an NMOS Registry
Built-in Registry Server
Configure NMOS connections
Discover and adopt
Browse the NMOS inventory
Manage NMOS multicast addresses
Diagnose NMOS problems
Understand Cuelists
Build a Cuelist
Read and advance a running Cuelist
Control a Cuelist from a Position
Workflows
Understand workflows
Build your first workflow
Reuse a group of workflow nodes safely
Troubleshoot a workflow
Recipes
Sequence a timed automation
Call an HTTP endpoint from a workflow
REST endpoint
Use variables
Understand variable scope
Understand nested variables
Update expressions for v1.8
Plan and use Tags
Access
Create and manage users
Create roles and assign permissions
Grant access to specific resources
Show different controls by role
Sessions
Set up PIN and NFC sign-in
SSO
Get started with SSO
Connect a generic OIDC provider
Connect LDAP or Active Directory
Map identity claims to roles
Secure a Buttons deployment
Integrations
External control
Connect to Bitfocus Listener
USB Relay
Install USB Relay on Windows
Install USB Relay on macOS
Install USB Relay on Linux
Install USB Relay on a Raspberry Pi
Get started with the Control API
Secure and monitor the Control API
Control API reference
API reference
Administration
Enable and manage installable features
Services and health
Configure and monitor scheduled backups
Restore a backup and verify it
Export or import Buttons configuration
Store and rotate connection secrets
Replace the HTTPS certificate
HA backup and recovery
Settings
Collect support information
Reference
Glossary
Button Inspector reference
Network ports reference
Expressions
Internal actions reference
Routing Presets panel reference
Startup configuration reference
Workflow nodes
Connection workflow nodes
Workflow workflow nodes
Internal workflow nodes
Position workflow nodes
API workflow nodes
Utility workflow nodes

Loading...

Previous
← VideoHub and AJA KUMO
Next
Generic SW-P-08 →
Contact support →
You are viewing documentation for Buttons 1.8.See the docs for Buttons 1.6
Buttons/Connections/Router integrations/Utah Scientific BPS

Utah Scientific BPS

A Utah Scientific BPS panel connection can expose more than one independently-routable Level (typically video and one or more audio channels), so Buttons can help you send a different source to a destination's audio than its video, the same way you would break away one part of any multi-level bundle. This page covers setting up those Levels and what to expect from destination locking.

Before you begin#

  • A Utah Scientific BPS panel connection already added and connected.
  • Know how many Levels your panel is actually configured for (video-only, or video plus one or more audio channels).

Configure Levels to match your panel#

Open the connection's configuration and use the Levels field to add one entry per independently-routable layer of the signal: for example Video, then Left Audio and Right Audio. Each entry needs a label and a role (Video, Audio, or Data); the role is what the Routing view's Ports filter matches against.
If you leave Levels at its default, Buttons builds one automatically from the panel's own configured Level count: a single combined Video+Audio Level if the panel reports one Level, or a Video Level plus one Audio Level per remaining Level if it reports more. Set Levels explicitly if you want your own labels instead of the generated ones, or if the automatic count doesn't match your panel.
Once more than one Level exists, you can route them independently: see Route only one part of a bundle for how to select and take a route for a single Level.

Lock and unlock destinations#

This module supports destination locking, so lock and unlock controls appear wherever locking is enabled: see Manage locking and Understand route status.
Two things behave differently here than on a single-level router:
  • Locking a destination locks every configured Level of it together. You can't lock only its audio Level while leaving video unlocked: the lock action always applies to the whole physical destination.
  • The panel doesn't distinguish a lock placed through Buttons from one placed any other way: both Locked and Protected report back as the same state. A destination you just locked from Buttons shows as a hard/device lock, not a user lock.

If you get stuck#

What you see
What to try
You locked a destination from Buttons, but it shows a hard lock instead of a user lock.
That's expected for this panel: it reports every lock the same way regardless of where it was set.
Locking one Level of a destination locked the others too.
Expected: this module locks the whole destination across all its Levels at once.

Where to go next#

  • Check what a router integration supports, for how this compares with other router modules.
  • Take a physical route.
  • Add a Router Section to a position, for lock and unlock controls on a surface.

Was this helpful?

Was this helpful?

0 of 0 users found this page helpful