--- title: "The Z/IP ONE and Livewire GPIO explained" slug: "the-zip-one-and-livewire-gpio-explained" updated: 2024-12-19T07:43:48Z published: 2024-12-19T07:43:48Z canonical: "docs.telosalliance.com/the-zip-one-and-livewire-gpio-explained" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt > Use this file to discover all available pages before exploring further. # The Z/IP ONE and Livewire GPIO explained ## Scope This document covers Livewire GPIO in the [Telos Z/IP ONE Broadcast IP Codec](https://www.telosalliance.com/site-to-site-connectivity/codecs-transceivers/telos-zip-one). Z/IP ONE also has physical GPIO via a parallel port on the back of the unit. Only Livewire GPIO is discussed in this article. ## Description The Telos Z/IP ONE Broadcast IP Codec (we'll just call it a Z/IP from here on) is a Livewire device. In addition to Livewire audio in and out, it also includes Livewire GPIO for interfacing with the Z/IP's built-in GPIO capabilities. The Z/IP's GPIO is configured on the GPIO page of the Web UI shown here. ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/880105b0-74b7-48d0-b2d3-c48705bcb91c-image.png) The functions of each of the eight "Bits" are controlled by the pull-down options and are explained in the Z/IP manual. ## Axia GPIO The Z/IP has two Axia GPIO ports that mirror the configuration set on the configuration page, with one exception. While the Z/IP has only EIGHT bits, each Livewire GPIO port has 5 pins (or 10 total). Only the first FOUR pins on each GPIO port get used. The 5th Pin is not used. - GPIO Port 1, Pin 1 - Z/IP Bit 1 - GPIO Port 1, Pin 2 - Z/IP Bit 2 - GPIO Port 1, Pin 3 - Z/IP Bit 3 - GPIO Port 1, Pin 4 - Z/IP Bit 4 - GPIO Port 1, Pin 5 - Not used - GPIO Port 2, Pin 1 - Z/IP Bit 5 - GPIO Port 2, Pin 2 - Z/IP Bit 6 - GPIO Port 2, Pin 3 - Z/IP Bit 7 - GPIO Port 2, Pin 4 - Z/IP Bit 8 - GPIO Port 2, Pin 5 - Not used > [!WARNING] > The "Not used" ports can not be assigned to other functions. They are not available to the Z/IP. For those that understand the Livewire GPIO vernacular a bit better, the GPIO can be restated like this. ```plaintext ***** GPI are "receive from remote" or defined OUTPUT function ***** GPI 1 hhhhh      1234      ^^^^^      ||||\_ Unused      |||\__ Z/IP Bit 4      ||\___ Z/IP Bit 3      |\____ Z/IP Bit 2      \_____ Z/IP Bit 1 GPI 2 hhhhh      5678      ^^^^^      ||||\_ Unused      |||\__ Z/IP Bit 8      ||\___ Z/IP Bit 7      |\____ Z/IP Bit 6      \_____ Z/IP Bit 5 **** GPO are "send to remote" or defined INPUT function ***** GPO 1 hhhhh      1234      ^^^^^      ||||\_ Unused      |||\__ Z/IP Bit 4      ||\___ Z/IP Bit 3      |\____ Z/IP Bit 2      \_____ Z/IP Bit 1 GPO 2 hhhhh      5678      ^^^^^      ||||\_ Unused      |||\__ Z/IP Bit 8      ||\___ Z/IP Bit 7      |\____ Z/IP Bit 6      \_____ Z/IP Bit 5 ``` ## Remember The **Outputs** you configure in the Z/IP, shown here, will arrive as a Livewire GPI. ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/5d1d674f-5ea6-4db2-a382-d94f2623da08-image.png) **Inputs** you configure in the Z/IP, shown here, will arrive as Livewire GPO. ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/75470563-326a-4aae-b345-2f42bfa97805-image.png) ## Let us know how we can help If you have further questions on this topic or have ideas about improving this document, please [contact us](https://www.telosalliance.com/support-request).