This documentation supports the latest PCIe host firmware, the latest OpenEphys.Onix1 package, and Bonsai 2.9+.

Table of Contents

Headstage64GpoTrigger

sink Operator

Trigger a headstage-64 stimulator using the port controller's general purpose output (GPO).

This data IO operator must be linked to an appropriate configuration, such as a ConfigureHeadstage64.Headstage64PortController, using a shared DeviceName. Each headstage port has a GPO interface for sending digital signals to the headstage with low latency. This operator uses a dedicated GPO line rather than a register write to trigger stimulation and therefore has lower latencies than Headstage64ElectricalStimulatorTrigger or Headstage64OpticalStimulatorTrigger. However, the trigger will be delivered to both of the stimulators so care must be taken to ensure only the appropriate stimulator is armed when the trigger is sent.

Headstage64GpoTrigger Workflow

Inputs & Outputs

Issue a stimulus trigger using the port controller's GPO.

A sequence of boolean values indicating if a stimulus trigger should be issued.

right-arrow
representation of a sink operator
right-arrow

A sequence that is identical to source.

Properties

Property Type Description
DeviceName string

Gets or sets a unique device name.

The device name provides a unique, human-readable identifier that is used to link software elements for configuration, control, and data streaming to hardware. For instance, it can be used to link configuration operators to data IO operators within a workflow. This value is usually not set manually, but is assigned in a MultiDeviceFactory to correspond to a fixed address with a piece of hardware such as a headstage. This address is used for software communication.