157
Intera 3.2
Pulse (output), edge (input): the information is contained in the change of the signal from
false to true (the rising edge of the signal.) How long the signal remains true doesn’t matter.
This represents the occurrence of an event. For example, when an action is started, a pulse
is sent.
•An edge input should remain true for a minimum of 0.5 seconds to
ensure it is reliably recognized.
•Pulse outputs are true for at least 0.5 seconds.
•Other notes
In advanced applications, there are some cases where it makes sense to
connect a pulse output to a level input, or a level output to an edge input. For
a contrived example, a user could connect a Done (output level) signal to a
Task Reset (input edge) and the task would reset when the Done signal
became true.
Task element: a task element is a piece of a task to which signals can be assigned. Elements
include: the overall task itself, a subtask, an action group, an individual action. Action Sequences
are also task elements, though signals cannot be attached directly to them.
Signal types: Intera has a predefined set of signal types. In order to define a signal, a type must be
selected, it must be named, and it must be associated with a particular input or output. Once
defined, a signal can only be connected to an input or output of a task element of the same type.
Signal Types
Intera has a predefined set of signal types. While a type implies a certain high-level meaning, the
details of how any signal operates are dependent upon the element to which the signal is attached.
The main types are described below.
INPUTS
Ready (edge and level): when true, indicates that the task element is okay to run. In many cases the
edge of the Ready signal is also used to reset the count or error state of the connected element.
Skip (level): when true, causes Intera to move on from the current element.
To Next Page
