Sending responses via TTL (case 5907)

[AaronNewman]

Hi Blair

Thanks for creating that feature! I downloaded and installed the new version and it works great. In the interim I had figured out another way of doing it, using jumping to different trials depending on which response was made, and sending codes (followed by presenting a "space" character for 0 msec) from the jump trials. But, the TTLecho method is far more flexible and saves one from coding a lot of jump trials if there are many response options.

It would be great if this could be integrated into the Styles file in a future release, rather than being dependent on an extra file.

thanks again, DirectRT rocks!

Aaron

[whiteej]

Blair & Aaron
I am working on programming a task with very similar demand I have created the ttlEcho.txt file and still have had no success in getting a response locked ttl signal. Is there any differences in how v2008.1 handles this situation? I know this thread is old, hopefully this topic is still relevant.

Evan

[AaronNewman]

Hi Evan

We use 2008 now and as far as I know, sending TTL codes works the same way. However we haven't been using the TTLecho feature so I can't comment on that specifically. Are you able to successfully send TTL codes using the standard approach of including a stim/loc/time triple with your ttl code, port address, and a short value for time (e.g., 10)?

Aaron

[whiteej]

Hi Aaron,
The ttl signal feature is working. It is just the ttlEcho feature that is not working. We just need a way to get a ttl signal that generates for responses.

Thanks for all the help!
Evan