As part of the system setup, a slot ID must be assigned to each control surface module. This determines the functionality of the module according to the matching slot ID/address defined in the configuration.

For a Console Compact license, there are two valid slot IDs (to support either a Fader or Main module):

  • ID 01 = Fader module: faders 1 to 8.
  • ID 03 = Main module: faders 9 to 14 + central controls.

Please note: in crystal, there are no even numbered slot IDs.

The image below shows how these should be assigned to an 8-fader, 6-fader and 14-fader surface. You can see the ON-AIR Designer 'Frame → Surface' configuration (at the top) and the console frames (below). 

Important: each module's address must be unique. It is not permitted to assign the same slot ID to more than one module. If more than one module has the same slot ID, then you may see some odd behaviours once the console is operational.

If Power Core is running a Console MAX license, then up to four Access Groups are supported (to share the resources of a single Power Core device).

In this instance, the active slot ID defines the functionality of the module; which fader numbers are controlled; and which access group the frame belongs to. 

  • ID 01 = Access Group 1, Fader module: faders 1 to 8.
  • ID 03 = Access Group 1, Main module: faders 9 to 14 + central controls.
  • ID 05 = Access Group 2, Fader module: faders 17 to 24.
  • ID 07 = Access Group 2, Main module: faders 25 to 30 + central controls.
  • ID 09 = Access Group 3, Fader module: faders 33 to 40.
  • ID 11 = Access Group 3, Main module: faders 41 to 46 + central controls.
  • ID 13 = Access Group 4, Main module: faders 49 to 54 + central controls.

In the example below, three surfaces are configured. The slot IDs are highlighted in different colors to show the different access groups. In this example, the third access group is unused (so that another 14-fader surface can be added later).


When configuring Power Core Max...

Please note that the real-time input measurement for the channel in ACCESS is supported by Access Group 1 only, and not Access Groups 2 to 4. This affects the dynamic signal level visualizations on the GUI such as the bouncing balls in the Dynamics 'Source Parameter' dialog box. So, in the example above, these visualizations are available for Studio 1 only, and not Studios 2 to 4.

For this reason, it is recommended to use Access Group 1 for the most important surface / the surface with a Virtual Extension.

For more information about the 'Frame → Surface' configuration, please refer to ON-AIR Designer User Manual. Here we deal with the assignment of the slot IDs to the surface modules.

How to Check and Assign the Slot ID(s)

The active slot IDs are shown on the surface displays during boot-up, and are configured using the "Surface → Modules" tab in the Web UI.

To check the settings:

  1. Open a Web UI connection to the crystal frame.
  2. Log in as either Supervisor or Administrator. The default passwords are orion for Supervisor and hydra for Administrator.
  3. Select the "Surface Modules" tab and look at the Act. Slot values - these show the active slot ID for each module. 

The active slot ID can be changed either, permanently, by editing the Dflt (default) value or, temporarily, by loading one of the alternate mappings (Map 1 to 4). 

Editing the Default Slot IDs

During the initial setup, you should use the Dflt value to assign the correct slot ID to each physical module (e.g. for a 6-fader surface, assign 03 to the Main module).

This is done as follows.

  1. Type the required slot ID into the Dflt field - the edited value and Set Slot button highlight in yellow.
  2. Press Set Slot to make the assignment.
  3. Wait for the Act. Slot field to update and check its value.
  4. Repeat these steps for each module.

The screenshot below shows how the Web UI looks when a default value is changed but not yet saved.

Using the Alternate Mappings

The alternate mappings (Map 1 to 4) can be used, during operation, to provide access to different sets of faders and/or central controls. In this instance, the mapping data is stored globally and recalled using the Slot Map Selection option (at the bottom of the page) or via Ember+ (for more convenient control).

  1. Start by entering the required slot IDs into the Map # fields - the edited values and Set Slot Map Data button highlight in magenta.
  2. To save all of the changed values, press the Set Slot Map Data button. (Or to cancel all changes, press Cancel Slot Map Changes).
  3. To load a mapping, click on Slot Map Selection and choose an option from the drop-down menu. You can choose any of the four alternate mappings (Map 1 to 4) or revert to the Default slot IDs (defined in the Dflt fields).
  4. Wait for the Act. Slot fields to update and check their values. Note that all zero (0) values are ignored.

The screenshot below show how the Web UI looks when one of the mapping values is changed but not yet saved.

The screenshot below shows the options in the Slot Map Selection menu. Once an option is selected, the active slot IDs update to match. So, in this example, the Act. Slot and Dflt values should be the same.