62
10 Ember+ Interface
This shows all of the devices input channels down the left-hand side and all
the devices output channels along the top of the matrix, by clicking on a box
where an input channel and an output channel intersect, the audio from the
input channel is routed the output channel. This routing can be removed
by clicking on the same box. Right clicking on a routing or name allows
parameters to be viewed or changed.
GPIO Node
The GPIO node branch of the Ember+ provider tree interface allows
monitoring and control of the GPIO ports. Fig 10 10 shows the structure of
each GPIO child node.
Fig 10-10: Ember+ GPIO Branch Structure
Each GPIO node has a similar set of parameters and functions;
Type Parameter
This enumerated integer parameter is the current port type. This parameter
indicates whether the GPIO is disabled, or set to be an input or an output.
Input Function Parameter
This string parameter is the function that will be activated when the GPIO
port, when configured as an input, is asserted. The values that this parameter
can be set to are listed under the “Handlers” node see page 64.
Output Trigger Parameter
This string parameter is the function that triggers the GPIO port when it is
configured as an output. The values that this parameter can be set to are
listed under the “Triggers” node see page 64.
Invert Trigger Parameter
When this boolean parameter is set to true, the status of the GPIO when
it is configured as an output is the inverse of the configured trigger. When
this parameter is set to false, the output status matches the state of the
configured trigger.
Input Mode Parameter
When the GPIO is configured as an input, this enumerated parameter
configures whether the GPIO works in a latching or momentary mode.
Status Parameter
The status parameter shown in Fig 10 10 represents the current state of the
GPIO port regardless of whether the port is set as an input or an output.
A value of False indicates the port is inactive and True indicates the port
is active. When the GPIO is configured as an output, a connected Ember+
consumer can modify the value of this parameter.
Relay Node
The relay node of the Ember+ provider interface allows the relay to be
controlled by an Ember+ consumer. Fig 10-11 shows the structure of the
relay node.
Fig 10-11: Ember+ Relay Branch Structure
