Gpio - Revision history

Camille at 08:10, 5 September 2024

2024-09-05T08:10:47Z

Camille at 10:54, 14 February 2024

2024-02-14T10:54:04Z

Marcel: /* Logical Inputs */

2021-02-23T11:16:36Z

Logical Inputs

Marcel: /* Logical Inputs */

2021-02-23T10:06:15Z

Logical Inputs

Marcel at 18:08, 22 February 2021

2021-02-22T18:08:45Z

Marcel at 18:08, 22 February 2021

2021-02-22T18:08:25Z

Marcel: Created page with "=== Livewire GPIO config under Remote (snake mode) === How to configure a LW GPO port on SOUND4 products ? (snake mode) Same config as Axia GPIO : /
2020-10-23T13:23:45Z

Created page with "=== Livewire GPIO config under Remote (snake mode) === How to configure a LW GPO port on SOUND4 products ? (snake mode) Same config as Axia GPIO : <IP address>/<GPIO port #..."

New page
=== Livewire GPIO config under Remote (snake mode) ===
How to configure a LW GPO port on SOUND4 products ? (snake mode)

Same config as Axia GPIO :

<IP address>/<GPIO port #>

* IP address of remote GPI to duplicate
* One port is 5 pins on Axia devices, 8 on SOUND4.
* Port # is 1 for most Devices, up to 2 for Impact, up to 8 for Axia GPIO node

[[Category:Livewire]]
[[Category:GPIO]]
[[Category:Remote software]]

@@ Line 53: / Line 53: @@
 As the drawings above show, unlike most Livewire device, these ports are not connected to physical GPIO but to logical GPIO machinery :
-* Livewire GPO (driven from Internet) is connected to a Logical GPI, which in turn may trig an event or drive a hardware GPO
+*Livewire GPO (driven from Internet) is connected to a Logical GPI, which in turn may trig an event or drive a hardware GPO
-* Livewire GPI (exposed to Internet) gets its level from a Logical GPO, which may come from a hardware GPI or an internal state
+*Livewire GPI (exposed to Internet) gets its level from a Logical GPO, which may come from a hardware GPI or an internal state
 ====Configuring Livewire Snake Mode under Remote Control (aka GPIO Routing)====
@@ Line 65: / Line 65: @@
 The Livewire GPO will then mirror the 5 pins of the Livewire GPI port of the remote device. This then feeds Logical GPI in the SOUND4 product.
-==== Configuring Livewire Console Mode under Remote Control ====
+====Configuring Livewire Console Mode under Remote Control====
 You have to fill the Axia GPO  : under "Livewire GPO Port ''n''", "Config" = <Livewire Channel #>
@@ Line 73: / Line 73: @@
 [[Category:Livewire]]
 [[Category:GPIO]]

@@ Line 7: / Line 7: @@
 ''Hardware Electrical Level is either "Low" (0V) or "High". Active level is LOW level''.
-[[File:GPI.png|thumb|705x705px]]
+[[File:GPI.png|thumb|494x494px]]
 <br />
@@ Line 21: / Line 21: @@
 Every logical GPI may also be routed to a logical GPO.
 ===Logical Outputs===
@@ Line 27: / Line 33: @@
 Each logical GPO gets its level amongst one of many sources  :
-*"patched" to any GPI
+*"patched" from any GPI
 *"patched" forced ON or OFF or Heartbeat
-*"Software Routing", triggered from a state variable condition, for example which Preset is On Air, or Digital Input Level less than xxdBfs, etc
+*"Software Routing", triggered from a state variable condition, for example which Preset is On Air, or Digital Output Level less than xxdBfs, failing input, etc
-The logical GPO level is then available on one one   :
+The logical GPO level is then available on one  :
 *Hardware : the logical GPO drives a physical electrical level on the Output Pins of the GPIO connector. This is "Hardware GPO[1 to ''n'']". Active level is Closed Contact.
@@ Line 41: / Line 47: @@
 ==Livewire GPIO==
-. Either Snake (mirroring) from another device, or controlled from a console.
+Either Snake (mirroring) from another device, or controlled from a console.
-===Livewire GPIO config under Remote (snake mode)===
+As a Livewire device, the SOUND4 device exposes 2 Livewire GPI ports and 2 Livewire GPO ports, each having 5 "pins".
-Same config as Axia GPIO :
+As the drawings above show, unlike most Livewire device, these ports are not connected to physical GPIO but to logical GPIO machinery :
-<IP address>/<GPIO port #>
+* Livewire GPO (driven from Internet) is connected to a Logical GPI, which in turn may trig an event or drive a hardware GPO
 *IP address of remote GPI to duplicate
-*One port is 5 pins on Axia devices, 8 on SOUND4.
+*One port is 5 pins on Axia devices
 *Port # is 1 for most Devices, up to 2 for Impact, up to 8 for Axia GPIO node
 [[Category:Livewire]]
 [[Category:GPIO]]
 [[Category:Remote software]]

@@ Line 7: / Line 7: @@
 ''Hardware Electrical Level is either "Low" (0V) or "High". Active level is LOW level''.
 ===Logical Inputs===
-There are 2 GPI flavors :
+A "Logical GPI" is an input stimulus which may come from one of these sources :
-*Hardware : physical electrical level present on the Input Pins of the GPIO connector. This is "Hardware GPI[1 to ''n'']". Active level is LOW level (grounded signal).
+*Hardware : the logical GPI gets its level from physical electrical level present on the Input Pins of the GPIO connector. This is "Hardware GPI[1 to ''n'']". Active level is LOW level (grounded signal).
-*Remote : logical level received from another device transported on IP. This is "ULA GPI[1 to ''m'']". Two protocols are recognized:
+*Remote : the logical GPI level is received from another device transported on IP. This is "ULA GPI[1 to ''m'']". Two protocols are recognized:
 **Livewire : status retrieved from another Livewire Device. See below.
-**SOUND4IP : one of the local DECODERs receives the GPI status from a SOUND4IP ENCODER on another device.
+**SOUND4IP : one of the local SOUND4IP DECODERs receives the GPI status from a SOUND4IP ENCODER on another device.
-For each GPI, an action may be triggered when ACTIVE or INACTIVE level is reached, for example change a config or launch a script.
+For each logical GPI, an action may be triggered when ACTIVE or INACTIVE level is reached, for example change a config or launch a script.
-Every GPI may also be routed to a GPO.
+Every logical GPI may also be routed to a logical GPO.
 ===Logical Outputs===
-There are also 2 GPO flavors :
+A "Logical GPO" is an internal state which is exposed to external world.
-*Hardware : physical electrical level forced on the Output Pins of the GPIO connector. This is "Hardware GPO[1 to ''n'']". Active level is Closed Contact.
+Each logical GPO gets its level amongst one of many sources  :
 *"patched" to any GPI
 *"patched" forced ON or OFF or Heartbeat
 *"Software Routing", triggered from a state variable condition, for example which Preset is On Air, or Digital Input Level less than xxdBfs, etc
 <br />

@@ Line 1: / Line 1: @@
 ''GPIO means "General Purpose Input Output"''
@@ Line 5: / Line 8: @@
 ''Hardware Electrical Level is either "Low" (0V) or "High". Active level is LOW level''.
-== GPIO Concept ==
+===Logical Inputs===
 There are 2 GPI flavors :
-* Hardware : physical electrical level present on the Input Pins of the GPIO connector. This is "Hardware GPI[1 to ''n'']". Active level is LOW level (grounded signal).
+*Hardware : physical electrical level present on the Input Pins of the GPIO connector. This is "Hardware GPI[1 to ''n'']". Active level is LOW level (grounded signal).
-* Remote : logical level received from another device transported on IP. This is "ULA GPI[1 to ''m'']". Two protocols are recognized:
+*Remote : logical level received from another device transported on IP. This is "ULA GPI[1 to ''m'']". Two protocols are recognized:
-** Livewire : status retrieved from another Livewire Device. See below.
+**Livewire : status retrieved from another Livewire Device. See below.
-** SOUND4IP : one of the local DECODERs receives the GPI status from a SOUND4IP ENCODER on another device.
+**SOUND4IP : one of the local DECODERs receives the GPI status from a SOUND4IP ENCODER on another device.
 For each GPI, an action may be triggered when ACTIVE or INACTIVE level is reached, for example change a config or launch a script.
@@ Line 20: / Line 20: @@
 Every GPI may also be routed to a GPO.
-=== Logical Outputs ===
+===Logical Outputs===
 There are also 2 GPO flavors :
-* Hardware : physical electrical level forced on the Output Pins of the GPIO connector. This is "Hardware GPO[1 to ''n'']". Active level is Closed Contact.
+*Hardware : physical electrical level forced on the Output Pins of the GPIO connector. This is "Hardware GPO[1 to ''n'']". Active level is Closed Contact.
-* Remote : logical level sent to another device transported on IP. This is "ULA GPO[1 to ''m'']". Two protocols are recognized:
+*Remote : logical level sent to another device transported on IP. This is "ULA GPO[1 to ''m'']". Two protocols are recognized:
-** Livewire : status sent to another Livewire Device. See below.
+**Livewire : status sent to another Livewire Device. See below.
-** SOUND4IP : one of the local ENCODERs sends the GPO level to one or many SOUND4IP DECODER(s) on other device(s).
+**SOUND4IP : one of the local ENCODERs sends the GPO level to one or many SOUND4IP DECODER(s) on other device(s).
 Each GPO gets its level amongst one of many sources  :
-* "patched" to any GPI
+*"patched" to any GPI
-* "patched" forced ON or OFF or Heartbeat
+*"patched" forced ON or OFF or Heartbeat
-* "Software Routing", triggered from a state variable condition, for example which Preset is On Air, or Digital Input Level less than xxdBfs, etc
+*"Software Routing", triggered from a state variable condition, for example which Preset is On Air, or Digital Input Level less than xxdBfs, etc
 <br />
-== Livewire GPIO ==
+==Livewire GPIO==
 . Either Snake (mirroring) from another device, or controlled from a console.