Now Shipping! – The EyeLink 3; combined head and eye tracking at up to 1000 Hz.

FAQ: How do the Button trigger IDs map to EyeLink game controllers?
#1
Experiment Builder supports a wide range of button boxes and response devices. The correct setup depends on whether the device connects to the Host PC or the Display PC.

The most common way to accept participant responses would be via keyboard or response pads directly attached to your Display PC. Alternatively, you can use a limited range of response devices connected to the EyeLink host PC.
  • Devices Connected to Display PC
    Any USB-based button box that registers responses as standard keypresses should be connected to the Display PC. These devices are accessed using a KEYBOARD trigger node.

    Examples of compatible, high-precision devices include the LabHackers Millikey or Black box Toolkit USB Response pad.

    Cedrus button boxes also connect to the Display PC, but they are a special case. These devices require their own dedicated CEDRUS trigger node in Experiment Builder.

  • Devices Connected to the Host PC
    Button boxes that connect directly to the EyeLink Host PC must be used with the EYELINK BUTTON trigger node in your project. A list of supported devices can be found in the following FAQ: Can I use any button box / response device with my Host PC?.

    Configuration Steps
    To ensure Experiment Builder uses the correct button mappings, you must specify which device you're using:
    • Open the Structure panel and click the Devices tab.
         
    • Select BUTTONBOX from the list of devices.
    • In the Type property, select the appropriate input device from the dropdown menu.
    • The default key mappings for these devices can be found in the Experiment Builder manual by navigating to Help > Contents > Experiment Graph and Components > Components > Triggers > "EyeLink Button Trigger".