Content
Summary
This document provides information about the ETL RCM protocol implementation for VSM.
Status of Driver | |
---|
Component for Driver | |
---|
Release (Build) of Component | vsmGadgetserver 5.6.0.xyz |
---|
Revision of Implementation | 1.0.0.0 |
---|
Name/Type of 3rd Party API | ETL RCM |
---|
Version of 3rd Party API |
|
---|
Additional 3rd Party information | Supported devices: ETL Hurricane and ETL Nigma |
---|
Connection
Connection Type | TCP/ IP |
---|
Default Port | 4000 (default) |
---|
Supported Features
The protocol only supports the Hurricane and NiGMa devices.
Access to basic parameters describing the health of the device.
Ability to perform any switching operations as well as adjustment of new connections via VSM panel.
Possibility to rename the optical sources and targets.
Control over the poll interval of messages.
Control over logging.
Supported Commands
Status (?) | Gets the current crosspoints from the device as well as the health info about the PSU(s), inter matrix communication and the matrix status itself. |
---|
Quick Status (Q) | Gets the health info about the PSU(s), inter matrix communication and the matrix status itself. |
---|
Switch (s) | Performs a crosspoint switch operation (On Hurricane device also returns the switch status containing possible errors) |
---|
Aliases (T?) | Gets all source/target aliases(labels) from the device. |
---|
Set Source Alias (TS) | Sets the alias(label) of a specific source. |
---|
Set Target Alias (TS) | Sets the alias(label) of a specific target. |
---|
Configuration Details
It is required to choose the right device model (Hurricane or NiGMa)
It is required to set the matrix/protocol addresses.
The default matrix address is 'A', change it only if you are sure that it's different.
The protocol address is our (VSM) address. It should be something that is not used by the rest of the system (default 'V').
The user should configure the Polling Interval (min:500ms , max: 60000ms). The lower the number the faster the matrix will poll the current configuration from the device (default: 5000ms)
Known Issues
There are currently no known issues.
Related Articles