Name:	Pro-Bel Matrix Switcher
Version:	6.7.2
Available for:	Manager V7 and Manager V6 (Lite & Pro), Showmaster (Mini, ST, Pro, LE, XS & iPro)
Limitation In:
Device Brand:	Pro-Bel
Positrack Compatible:	No
Resources type:	Serial

Overview

The PROBEL MxM provides an easy way to control one or several ProBel matrix switchers, from your PC’s RS 232 Com port. A regular RS 232 cable can be used (DB9 female on PC to DB9 Male on the matrix).

MxM Installation

No special installation required.

Device Setup

• COM Port: choose the PC communication that will control the ProBel matrix
• Matrix ID: choose the internal matrix ID to control
• Level Number: choose the number of level to control, this value depends on the matrix hardware configuration (for example to control a matrix with 2 analog video levels and 2 audio levels, you will have to choose 4 as the level number in the device setup box)
• Destination Number: choose the number of destinations (outputs) to control
• Source Number: choose the number of sources (inputs) to control
• Memories Backup File Name: select a file name that will be used to store and recall several matrix configs.

Device Commands

Crosspoint Connect

Send a commutation command to the matrix, the specified source is connected to the specified destination in the specified level

• Level: [Integer] level index value, from 1 to 8, 0 means all levels
• Source: [Integer] source value, from 1 to 128
• Destination: [Integer] destination value, from 1 to 128

Usage: this crosspoint connection is automatically saved in the default memory

Get Crosspoint

Call this function to retrieve the currently connected source on the specified desination, in the specified level

• Level: [Integer] level index value, from 1 to 8
• Source: [Integer][out] source value, from 1 to 128
• Destination: [Integer] destination value, from 1 to 128

Usage: this function retrieves the crosspoint connections from the “default” memory, no request is asked to the matrix. Thus the return value for source might not represent the actual value from the matrix. You should call the QueryMatrixConfig to retrieve (and automatically save to the default memory) the entire actual matrix crosspoint configuration. After that operation, it will be safe to call the GetCrosspoint function, the source value will contain the actual source connected to the given destination.

Store Memory

Stores in the given memory name the current matrix configuration

• Name: [String] memory name

Usage: this function stores the current “default” matrix config in the specified memory name. In order to store in a memory the actual matrix configuration, first call QueryMatrixConfig and then call StoreMemory with a memory name. This memory will contain the exact matrix configuration just before the QueryMatrixConfig command was called. This prevent storing wrong crosspoint connections in a memory, due to external crosspoint connections generated by a ProBel control panel for example. If the memory allready does exist in the MemoryList variable, it is replaced by the new one.

Load Memory

Load a given memory configuration into the matrix

• Name: [String] memory name

Usage: this function downloads to the matrix an entire configuration that was previously saved with StoreMemory. The MatrixStatus goes to the “Busy” state during the download process, and returns to “Idle” when it is finished.

Delete Memory

Delete a given memory

• Name: [String] memory name

Usage: this function delete a specified memory from the MemoryList variable. If the memory name does not match any memory in the MemoryList variable, the function does nothing.

Query Matrix Config

Start an upload process to retrieve the entire and actual matrix configuration

Usage: this function does make the MatrixStatus variable to change form “Idle” to “Busy”, the variable returns to “Idle” when upload process does finish. The entire uploaded configuration is automatically saved in the “default” memory, but you are free to save it in another memory by calling StoreMemory.

Destination Label Control

Allows to assign a text label to a destination

• Level: [Integer] level index value, from 1 to 8, 0 means all levels
• Command: [Enum] type of command to execute, “SetLabel”or “GetLabel”
• Destination: [Integer] destination value, from 1 to 128
• Label: [String][in or out] string that contains the label

Usage: if the command parameter is set to “SetLabel”,the specified string in the label parameter will be used for the specified destination label.

If the command parameter is set to “GetLabel”, the specified string in the label parameter will contain the previously configured label from the specified destination.

The destination label assignment is very usefull to give more explicit name to the destinations, like “Plasma screen”, “Monitor 1”, etc.

Source Label Control

Allows to assign a text label to a source

• Level: [Integer] level index value, from 1 to 8, 0 means all levels
• Command: [Enum] type of command to execute, “SetLabel” or “GetLabel”
• Source: [Integer] sourcevalue, from 1 to 128
• Label: [String][in or out] string that contains the label

Usage: if the command parameter is set to “SetLabel”,the specified string in the label parameter will be used for the specified source label.

If the command parameter is set to “GetLabel”, the specified string in the label parameter will contain the previously configured label from the specified source.

The source label assignment is very usefull to give more explicit name to the sources, like “VHS”, “Live”, etc.

Device Variables

MatrixStatus

[Enum] Current status of the matrix

• “Idle”: no communication between the PC and the matrix, this is the default state
• “Busy”: there is communication between the PC and the matrix, due uploading or downloading processes (by calling LoadMemory, or QueryMatrixConfig)

MemoryList

[String] List variable that contains all memories saved by calling StoreMemory

Usage: you can create a Manager list object to monitor that variable in order for the user to choose and recall a memory very easily

CurrentMemory

[String] Contains the current loaded memory

Usage: the crosspoint connection commands sent are only stored in the “default” memory, not in the CurrentMemory. To do so,you just have to call StoreMemory and pass the CurrentMemory as argument to the function.

ConfigUpdateEvent

[Integer] Values from 0 to 1. This variable changes when a crosspoint connection is issued

Usage: this variable works as an event. It set to 1 by the mxm when a crosspoint connection is issued either by the Crosspoint Connect command of the mxm or by an external ProBel control panel.

This varible is set back to 0 when calling the Get Crosspoint command. For example you can create a task automatically started when the ConfigUpdateEvent is set to 1. This task that will call the QueryMatrixConfig command in order to retrieve the new matrix configuration, issued by and external ProBel control panel.

Revisions

V 1.0.1

• Added: Support for Showmaster.

V 1.0.2

• Fixed: Showmaster Editor project user data folder was not selected by default.

V 1.0.3

• Modified: serial port is now opened when the device activity is enabled (i.e. when the project switches to Debug or Run mode).
• Fixed: under Showmaster memory file is not read if $CURRENTPROJECT_USERDATA macro is used
• Fixed: crash when the size of a memory name exceed 1K
• Fixed: crash when the size of the list of memory names exceed 4K

V 1.0.4

• Added: Support for Showmaster Pro.

V 6.0.0

• Modified: Support of Manager V6/Showmaster V2.

V 6.0.1

• Fixed: Setup dialog doesn’t open on the correct screen on a multi-screen configuration.

V 6.0.2

• Fixed: Device variables are not reset after a project load (Requires Manager 6.0.3+).

V 6.1.0

• Added: Support for Showmaster LE & Showmaster XS platforms.

V 6.1.1

• Fixed: The Setup dialog box is not always fully visible at the device creation time.

V 6.7.0

• Improved: Support for High DPI displays (require Manager 6.7.0+ or Showmaster Editor 2.7.0+)
• Changed: Compatibility for Manager 6.7.0 and Showmaster Editor 2.7.0