Attero Tech CommandHub Manuel de l'utilisateur - Page 9
Parcourez en ligne ou téléchargez le pdf Manuel de l'utilisateur pour {nom_de_la_catégorie} Attero Tech CommandHub. Attero Tech CommandHub 20 pages. Unify proxy device for control and routing
4 – Message Format Specification
The CommandHub can be used for two types of control. It can be used to send device-specific control commands to
Attero Tech unIFY devices on the Dante network. It can also be used to send network routing and more general control
and monitoring commands.
4.1 – Device Control
Control of unIFY devices is achieved by sending UDP messages to the UDP listen port (by default, port 3000) of the
CommandHub on the control network side. These commands are converted and then passed on to the device via the
CommandHub's Dante interface using a Dante proprietary protocol. Any responses from the device are delivered back
to the CommandHub which in turn, sends them to the UDP Response port at the source IP address of the original command
message.
*Note: Any unIFY device being used with a Command Hub **MUST** be setup to use the Dante proprietary interface. For
new devices to be used with a CommandHub, the order number should include a "–C" suffix. For existing devices, they
must be product version V1.x or be identified using unIFY Control Panel of having Direct UDP set to "No".
Each device uses the same message structure but has a unique command set based on the devices own features. The
commands a particular device supports can be found in the unIFY 3
area of the registered users section of the website (use the "Log-in" button on the Attero Tech website).
As these commands are being processed by the CommandHub, the CommandHub will need to know which device the
command is intended for. As a result, messages send to the CommandHub for device control must have the devices
name and a space prefixed to the actual control command. For example, a message to the CommandHub for an unD3IO
would look like this:
unD3IO-000000 IG 1 0.0dB<CR>
This command sets the input 1 to line level for device unD3IO-00000.
*NOTE: The devices name is case sensitive and must match exactly the device name as shown in Dante Controller. Any
inaccuracies in the case for characters contained within the name will give indeterminate results.
4.2 – Routing and Monitoring
The following 3rd party Dante routing and monitoring commands are available for the CommandHub.
© Attero Tech LLC 2015
Description
Get Dante Device List
Get Dante Device's TX Channels
Get Dante Device's RX Channels
Get Assigned Dante Channels
Get Network State
Set Dante Route
Get Version
Network State Changed
Get Clock Status
Configure Network State Status
Page 8
CommandHub
rd
party software API, available from the documents
Command
GDDL
GDTX
GDRX
GADC
GNST
SDRT
GVER
NSTC
GCLK
CSTS
User Manual
614-00019-01