SECTION 3 |
20
USING GPIO & DATA WITH ZEPHYR IPORT PLUS
3
Using GPIO & Data with
Zephyr iPort PLUS
As multiple audio signals are encoded in Zephyr iPort PLUS and distributed over a WAN or other network, their
associated GPIO information needs to travel with them. Zephyr iPort PLUS makes this happen by embedding
GPIO events in the coded audio stream.
Zephyr iPort PLUS has a GPIO capacity of 20 contact closures per codec channel, and per transmit direction. GPIO
events always travel from the encoder to the decoder. To establish a two-way exchange of GPIO events, a duplex
codec link is required.
The GPIO functionality of Zephyr iPort PLUS represents a significant upgrade over that of the original iPort. It is
not possible to describe every drop down menu and permutation that is available. Instead, we will describe the four
operation modes for GPIO. And, with a bit of experimentation, you should be able to develop a solution that works
for you. If you’re still having difficulties, remember that Telos Alliance 24/7 tech support is just a phone call away.
Audio and control functions aren’t the only things running around the data stream. There are “associated data
channels,” too. We’ll cover these options near the end of this chapter.
GPIO Operation Modes
Zephyr iPort PLUS supports four operation modes, which are selected individually on the dropdown menus, per
GPIO ports and transmission direction.
On the Livewire interface side, the Virtual Endpoint and Transit Point modes are TCP/unicast-centric. Zephyr
iPort PLUS provides individual point-to-point event transportation channels, which repeat the configuration
model and behavior of the “GPIO snake” as implemented in Axia GPIO devices.
In the “emulation” modes, Zephyr iPort PLUS communicates with other devices over the GPIO multicast channel
and repeats the behavior of the controller (e.g. Axia console) or I/O device (GPIO xNode) respectively. It allows
you to create a “virtual presence” for devices physically located on separate networks.
