SuperLab version 6.3 introduces significant behind-the-scenes changes to how TTL signals are generated. The most impactful one is the switch from synchronous to asynchronous TTL output.

Sync vs. Async

With synchronous output, sending a 5ms TTL signal meant that SuperLab would raise the output line, pause the experiment for 5ms, and then lower the output line. Pausing for 5ms does not sound like a lot but it is a long time for certain kinds of experiments.

With asynchronous output, there is no pausing: SuperLab sends a command to the output device to produce a 5ms pulse and continues with the stimulus presentation.

Who is Affected?

If you are making a new experiment and have compatible hardware, we have no doubt that you will love the changes. 

Here are a few situations that would affect users switching to SuperLab 6.3 or later:

• If you have an experiment that was built with a version prior to 6.3, it is important that you review the it carefully. Experiments are all different and only you can know if the switch from sync to async matters.
• SuperLab 6.3 drops support for older devices because they are unable to produce signals asynchronously. This includes:
• The RB-530, RB-730, RB-830, and RB-834 response pads
  You can continue using them as input devices, but they can no longer be used with events of type Digital Output.
• SV-1 voice key
  You can continue using it as a voice key but it can no longer be used with events of type Digital Output.
• Lumina LSC-400 controller
  You can continue using it as input but it can no longer be used with events of type Digital Output.
• The original StimTracker ST-100 model
• Measurement Computing I/O devices
  You can continue using them as input in the Windows version of SuperLab for now, but support for Measurement Computing I/O devices will be dropped completely in a future version of SuperLab.
• National Instruments I/O devices
• When using a compatible device (StimTracker Duo or Quad, RB-x40 or Riponda response pad, c-pod, or Lumina 3G controller), firmware version 2.2.5 or later is required.

Why Go Async?

In two words: new features.

SuperLab 6.3 can now auto-generate event markers, e.g. when a stimulus is presented or a participant’s response is correct. This required async output. Click on Experiment menu and choose Event Markers… to see this feature in action.

There are other planned features for SuperLab that can be implemented only with async output.

 

Back to SuperLab Support main page
Last Revision: June 7, 2022