# Imagine LRC

> How an Imagine Communications router controlled over LRC exposes its levels and destination locks in Buttons.

An Imagine LRC connection controls an Imagine Communications router over the LRC protocol. Buttons builds one Level for each router level the module reports, and it can lock and unlock destinations.

## Before you begin

- An Imagine LRC connection already added and connected, running module version 2.2, 2.3 or 3.0. See [Update a connection's module safely](/docs/buttons/v1.8/connections/module-compatibility) if you need to check or change the installed module version.
- Access to **Connect → Connection** to check configuration, and to **Routing** to take and verify routes.

## Levels come from the router

There's no Levels field to fill in. Buttons reads the sources, destinations and levels that the Imagine LRC module reports, and gives each source and destination one port per level, named after the level. If the module reports no levels, each source and destination has a single port.

Source and destination names come from the router. Buttons leaves out a leading number in the name, so a destination called `12 Studio A PGM` shows as **Studio A PGM** next to **Out 12**.

A level only routes to the same level on the destination. To route one level of a bundle without the others, see [Route only one part of a bundle](/docs/buttons/v1.8/routing/take-a-route#route-only-one-part-of-a-bundle).

All of an Imagine router's ports have the same role in Buttons, so the **Ports** view's Role filter doesn't separate video from audio levels. Use the level names instead.

## Lock and unlock destinations

Lock and unlock controls appear on Imagine LRC destinations wherever locking is enabled: see [Manage locking](/docs/buttons/v1.8/positions/router-sections#manage-locking) and [Understand route status](/docs/buttons/v1.8/routing/understand-route-status#interpret-lock-indicators).

- A lock covers the whole destination: locking it locks every level of that destination together.
- The router doesn't report where a lock came from, so every lock shows as a hard lock, including one you just set from Buttons. You can still unlock it from Buttons.

Buttons doesn't route over a locked destination unless the operator overrides the 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: the router reports every lock the same way. |
| Locking one level of a destination locked the others too. | Expected: the lock always covers the whole destination. |
| The Role filter in the **Ports** view shows no difference between video and audio. | Expected for this router. Use the level names to tell the ports apart. |

## Where to go next

- [Check what a router integration supports](/docs/buttons/v1.8/connections/router-integrations), for how this compares with other router modules.
- [Take a physical route](/docs/buttons/v1.8/routing/take-a-route), including routing only one part of a bundle.
- [Add a Router Section to a position](/docs/buttons/v1.8/positions/router-sections), for lock and unlock controls on a surface.
