Omnia Audio Omnia.ONE User Manual
Page 169
150
primary input to analog will cause "GPI 2 Lxxxx" (where "x" is replaced by "h" or "l" depending on the previous
state of the GPI) to be issued to interested LWRP clients.
GPI 1 is used for the physical GPI port on the rear panel. Changes in its state are reported directly using LWRP.
Because the pin-based protocol was designed for use with physical contact closures, the result of each go-high or go-
low event may depend on the previous state of the pins and certain results cannot be achieved without going through
intermediate states. Thus, it is not recommended for use when control is being done directly by computer software
over a TCP connection. In this case, there is a stateless command-based protocol available.
The command-based protocol is also a part of LWRP, and accessed using a TCP connection to port 93. It is
implemented using the LWRP GPO
after CMD: ) to control the Omnia. Each GPO port maintains the same function as listed above for the pin-based
protocol, and will only accept CMD: arguments that relate to that function. The following arguments are supported,
listed by port:
GPO 2:
-- SEL
displayed by the front panel or remote. Note: A list of names may be obtained by issuing an http GET of /cgi-
bin/presetlist.cgi (from the webserver on the Omnia). This will give an http response containing a text/plain
document that contains preset names, one per line.
GPO 3:
-- PRI
AES (for AES/EBU), or LWR (for LiveWire).
-- SEC
-- FOV SET -- Force a failover to occur, putting the secondary input on-air and engaging the failback logic
-- FOV CLR -- Force a failback to occur, putting the primary input on-air and engaging the normal failover logic.
Note: if the failover function is defeated by setting the failover time to 0.0, this command will not cause it to become
activated.
The corresponding GPI ports issue reports using this same syntax. Whenever a preset is selected by any means, GPI
2 will issue a "SEL
and likewise for the secondary input with "SEC
failback occurs, it issues a "FOV CLR". These reports are sent to any client monitoring the GPI port using standard
LWRP procedures; see the LWRP documentation for more information. Note that these clients will also see reports
of the same changes issued in the pin-based protocol at the same time.