Common Use Cases
Create dynamic stores and logic outputs based on inputs from digital I/O bits or a software button. Use this gizmo to store I/O inputs with values defined by user or another gizmo and create fixed-duration, toggled, or edge logic outputs based.
Gizmo Help Slides
The User Input reads digital inputs from the hardware directly or accepts user button presses and outputs logic signals. The output Strobes can only be true when the Enable input is true. Typically the Enable input is connected to the #Enable signal on your RZ or RX, which remains high for the duration of the recording.
The Runtime Interface
At runtime, the standard Synapse data plot is available to display any stored data. The User Input can store its logic signals as onset/offset epoch events.
User Input Tab
Software buttons appear in the user interface at run time. Other bit inputs are labeled with their port name and a state indicator. For inputs with an associated data store, the last value saved is shown on the interface.
|User Input Runtime UI|
User Input Configuration Options
See The Options Area and Templates for more information on the gizmo name, source, global options, and displaying the block diagram.
The Name is how the input is shown on the user interface.
Button Mode sets the input. It can be directly fed from a digital input on the hardware, or set as a software button the user presses.
If Mode is a digital input, Debounce lets you set a duration of time for an input to settle before being detected (good for lever presses or hardware button presses).
Strobe controls how the button output behaves. An example input signal and the three Strobe options are shown below. Epoc events can be stored on the Onset of the Strobe output or on the onset and offset (Full).
If all of the buttons are set to Edge mode, the Exclusive option is available. When this option is selected, an additional gizmo output is available that contains the value of the button that was pressed (1, 2, 3, 4).