Expand the possibilities of your digital matrix system

More computers

When cascaded into three levels, the ControlCenter-Compact system increases the number of connectable computers. The master device takes over all controlling tasks. The listed possibilities guarantee the full access of all consoles to all computers over all cascade levels.

Cascading allows for an additional transmission distance of 140 m per ControlCenter-Compact. When fully cascaded, the distance from computer through to the cascaded central modules up to the user module can be up to 560 m.

Example for cascading:

When configuring the ControlCenter-Compact with

• 2 console ports and 30 computer ports (stand-alone)
• you can operate 450 computers via 2 simultaneous consoles in the first cascade. This requires 16 ControlCenter-Compact.

The first ControlCenter-Compact provides no ports for connecting computers. Its 30 computer ports transmit 15 × 2 = 30 console accesses to the 15 ControlCenter-Compact of the first cascade level.

UC computer modules

Use UC modules instead of the usual computer modules to increase the number of consoles or to establish a redundant system.

Using a second RJ-45 socket, the UC module doubles the keyboard, video, mouse, and audio interfaces to the central module. Thus, a computer can be connected to two clusters. Combining the clusters with the corresponding central and user modules increases the number of consoles.

This requires:

• 1 x UC computer module per computer
• + number of user modules according to the number of additional consoles
• + central module according to the number in cluster 1

Details about the UC modules are given under computer modules.

More range through DVI-FiberLink and CAT-Repeater

I/O-Card-Trunk4

In addition to dedicated connection options, the I/O-Card-Trunk4 is also ethernet-capable, thus allowing you to use existing network structures. You can even set up KVM matrix installations with the ControlCenter-Digital across locations and large distances if suitable connections are available.

DVI-FiberLink

The DVI-FiberLink increases the system range within a cluster to up to 10,000 m. The system consists of two identical modules (transceivers) and is available in two variants:

• DVI-FiberLink(M)
  
  • Transmission via 2 multi-mode fiber optics (50/125µm)
  • Range up to 550 m
• DVI-FiberLink(S)
  
  • Transmission via 2 single-mode fiber optics (9/125µm)
  • Range up to 10,000 m

The pair of DVI-FiberLink devices can be placed between any module. One pair of DVI-FiberLink devices extends one access (console).

CAT-Repeater

Employing the expansion module CAT-Repeater lets you extend the transmission range between two CAT components of a digital matrix switch of the DVICenter or ControlCenter-Digital series.

The use of an expansion module adds 140 metres to the overall transmission distance. You can use up to five expansion modules on one line.

Installation

We provide 19" rack mount solutions for easily installing the devices into a server rack. The solutions are listed under mounting solutions.

Bidirectional communication through the KVM-Matrix Grid

Function: combining multiple matrix systems
Operation: via OSD and Web-Interface
Operating requirement: activation within each matrix switch connected
Efficiency: system

By default, G&D digital matrix systems can be expanded by means of a top-down cascade.

Moreover, the KVM-Matrix Grid establishes a bidirectional communication between individual matrix switches. Now systems can be interconnected even more directly to facilitate larger installations. Thus, users are able to operate the system bidirectionally at multiple locations.

For transmission between two matrix systems, the devices are directly connected via I/O ports. Each simultaneous KVM connection going beyond a matrix requires a connection to the grid. To establish communication between the matrices, they are connected to a network that provides access to a shared database.

At all expansion stages, digital matrix systems from G&D can be integrated into the KVM-Matrix Grid. This includes the entire DVICenter and ControlCenter-Digital series. Up to 24 matrices can be part of one grid. Within this framework, any topologies are possible (e.g. strand, tree, ring, star, meshed network).

The systems included in a grid are virtually combined to form one large matrix for the users. Thus, all connected user consoles are able to access all connected computers within a grid. The system automatically takes over the routing of KVM signals by selecting the ideal path through the grid.

MatrixGuard for maximum security

To offer you more security and flexibility for failure scenarios, we have developed the MatrixGuard.

Example of topology: simple lane

Thanks to the bidirectional connection, the G&D matrix grid allows access across locations. When connected via optical fibres, the location can even be several kilometres apart from each other - and in addition to the classic cascade users of all interconnected locations are able to access all systems connected.

Example of topology: networked circle

Ring topologies, for example, support redundancy concepts even better: even if a connecting line or a node fails, the system finds an alternate path for switching KVM signals. Therefore, users benefit from always available installations.

Example of topology: meshed network

The fully meshed network provides the maximum of accesses between individual matrices. In a later step the system automatically takes over the routing of KVM signals by selecting the ideal path through the grid.

Switching by network

Function: ControlCenter-Compact / ControlCenter-Digital remote control over IP
Operation via: customer-programmed user interface
Operating requirement: activation within master + programming of user interface
Efficiency: system (several clusters)

With the IP-Control-API function, you can send switching commands to the central module. The commands are sent via network.

The system is operated independently from user modules. Independent from any location, each computer can access the desired projection media and/or operator screens.

We provide you with the programming interface (Windows DLL or Linux SO), you program the user interface.

With IP-Switching, you can also:

• Receive information about current switching conditions
• Cancel all switching conditions (Disconnect)
• Receive information about the computer statuses
• Execute the Push-Get function via network (but no OSD integration)

Scenario switching

Example for day and night scenarios: With single command, all computers required for day or night shifts at the console can be switched at once.

Function: ControlCenter-Compact / ControlCenter-Digital Additional feature over IP-Control-API
Operation via: OSD
Operating requirement: activation within master + programming of user interface
Efficiency: system (several clusters)

Global scenarios for adapting the entire system to changing user behaviour

Global scenarios are best applied when all consoles within a system need to be used for other tasks. By using these scenarios, users are able to change the switching conditions of the entire matrix installation. One single command allows a user to switch the computers of all consoles within a control room from day to night shift. When used in OB vans, the parameters of the entire setup of one location can be switched to another location. This way, the intended use of an installation can be changed within seconds.

Local scenarios for fast reactions to changing tasks

Whether as emergency scenario at workplaces in control rooms or for a simple, less critical change of applications: Local scenarios are used when computers at individual workplaces are rearranged. Scenario switching is useful to apply whenever switching conditions need to be changed at a certain time. Especially when it comes to multi-monitor consoles that access multiple computers at the same time, the manual and therefore sequential selection of computers for every single monitor does not only prove to be complicated, but takes extremely long, too. Here again, scenario switching allows users to store switching states for local consoles which are then available for future applications

Of course, any login or access rights of KVM matrix systems remain the same when using scenarios.