Symetrix

This driver is for the Symetrix lineup of DSP processors. It was developed and tested using a Radius 12x8 with firmware 3.001 (build 9.01), a Jupiter 4 with firmware 2.68, and a Solus 8 with firmware 2.65. Version 1.1 was tested with a Radius 12x8 EX with a 2 Line VoIP Interface card and running firmware version 4.100 (build 10.20).

Revision History

1.0 Initial driver release
1.01 Fixed ability to set negative integers in Set Fader Level command.

1.02 Adjusted code for response changes when querying status of controller numbers.

1.03 Adjusted code for differences between model responses upon driver initialization.

1.1 Added TCP network connectivity for Edge/Radius series controllers.

Added VoIP and ATI telephony capabilities for Edge/Radius series controllers.

Added RTI Sample Simple VOIP symetrix file to download.

Added RTI Sample Simple VOIP driver configuration to download.

Added Symetrix Simple VOIP sample file

1.11 Delayed Initialization for speed dial consistency.

Network (UDP) Connection

The network connection on the Symetrix processor switch should be connected to the Network. It is recommended the Symetrix processor be set to a static IP.

The driver uses port 48631 as a default for UDP communications. Symetrix systems use either port 48630 or 48631, please reffer to the Symetrix documentation for what the port setting should be.

Note - UDP connectivity is not supported when the telephony mode is enabled.

Network (TCP) Connection - Edge/Radius Only

The network connection on the Symetrix processor switch should be connected to the Network. It is recommended the Symetrix processor be set to a static IP.

The driver uses port 48631 as a default for TCP communications. Symetrix systems use either port 48630 or 48631, please reffer to the Symetrix documentation for what the port setting should be.

Note - TCP connectivity is required when the telephony mode is enabled and IP control is preferred.

RS-232 Connection

The Symetrix processor defaults to a baud rate of 57600 but can be set to RTI supported baud rates between 1200 and 115200.

Telephony Configuration

Telephony - Enable telephony for use with the Symetrix 2 Line VoIP Interface card or the Symetrix 2 Line Analog Telephone Interface Card. This feature is only available for the Edge and Radius AEC/12x8 EX controllers only.

Telephony Unit Identifier - Unit ID of the device.

Telephony Card Slot - which option card slot the VOIP/ATI card is installed in. The default is set to D for Radius 12x8EX and Radius AEC.

Line 1/2 Appearnce 1/2 Call/End Button Assignment - Controller Number assigned to Line 1/2 - Appearance 1/2 Call/End Button.

Controller Configuration

Fader Count - Enter the number of dB faders configured for control and feedback. Up to 256 faders are supported. Faders objects in the driver are intended for use with modules that use a dB value. Fader objects can be configured with a custom name in the driver configuration along with a min/max level (dB) for each object.

Meter Count - Enter the number of meters configured for feedback. Up to 256 meters are supported. Meter objects can be configured with a custom name in the driver configuration along with a min/max level (dB) for each object.

Meter Threshold - Global - Select the meter threshold for Meter Level variable updating. Meter threshold adjustments can be set to 1dB, 1.5dB, and 3dB. A higher the threshold setting lessens the amount of information being sent to the driver and will help minimize processor usage. Meters should only be configured where absolutely needed as continuous meter feedback in quantity may decrease system performance.

Button Count - Enter the number of buttons configured for control and feedback. Up to 256 buttons are supported. Button objects are intended for use with modules like mute, solo, combine objects, etc. Button objects can be configured with a custom name in the driver configuration.

LED Count - Enter the number of LEDs configured for feedback. Up to 256 LEDs are supported. LED objects can be configured with a custom name in the driver configuration.

Input Selector Count - Enter the number of input selectors configured for control and feedback. Up to 128 input selectors are supported. Input selector objects can also be used for matrix routing modules. An 8x8 matrix router would use 8 input selector objects with 8 inputs configured for each input selector object. Input selector objects can be configured with a custom name in the driver configuration along with an input count for each object.

Output Selector Count - Enter the number of output selectors configured for control and feedback. Up to 128 output selectors are supported. Output selector objects can be configured with a custom name in the driver configuration along with an output count for each object.

General Level Control Count - Enter the number of general level controls (0-65535 values) configured for control and feedback. Up to 128 general level controls are supported. General level control objects are intended for modules that do not abide to the dB values that faders use. The general level control object only provides values between 0 and 65535 and does not convert the object value to the value that the module may display in the SymNet Composer Software. Calculations for these modules was not provided in the Symetrix protocol at the time of driver development therefore general values of the protocol were used to provide access to modules who's values may not be easily understood by end users. General level control objects can be configured with a custom name in the driver configuration, along with a min/max level for each object.

Driver Notes

- All modules configured for feedback must have push messaging enabled in the SymNet Composer software.

- Loading of presets 1-1000 is supported. Due to the way preset loading can be performed in the Symetrix system, the only variable available for presets is "Last Preset Loaded".

- Larger Symetrix configurations may not allow proper exposure of driver "Fly Out" menus in Integration Designer on 32bit operating systems due to the raw number of variables and events the driver is capable of. This is due to the way Windows 32bit operating systems manage memory for such menus. 64bit operating systems do not appear to suffer from this limitation.

- A sample file along with a driver configuration file (driverconfig) and a SymNet Composer file (symx) are included with the driver download. Please refer to these files for examples on how to configure the driver with the corresponding Symetrix system.

- The Telephony Keyboard - VOIP Dialing/Speed Dial Presets commands are intended for use only with dialing a VOIP number or changing preset names and numbers. The separate dial pad in the Symetrix software must be configured for external control and the control numbers must be mapped in the button mapping of the driver. See the Simple VOIP files included in the download for examples.

- Using the clear button in the respective dialer does not always provide feedback for the Line 1/2 Dialed Number variables. The Clear Dialed Text command must be used if the field does not clear automatically.

- The Direct Dial - Key Input command automatically attempts to dial the information in the Input Text Variable of the user interface it was executed from.

- The Direct Dial - Number or URI command is intended for dialing hard coded numbers. This is useful for numbers that will not need be changed through the Speed Dial Preset structure of the unit.

- Store Speed Dial Name and Store Speed Dial Number/URI commands will attempt to store the information that is current in the Input Text Variable to the respective location.