E-prime does not recognise fMRI scanner trigger pulse

[andreou.christina at gmail.com]

Right, I didn't need to try everything after all.. Luckily we just upgraded 
our response device system, and now the TTL pulse arrives to the stimulus 
PC through the device (as you, David, suggested). E-Prime automatically 
recognized everything, and I can insert the trigger pulse as a keyboard 
response where applicable. By the way, this is exactly how EEfMRI is 
supposed to work (which somehow had escaped our attention, although pstnet 
states it quite clearly under the requirements for using the extension). 
So, other than providing a very clear and "linear" logging file (I have an 
experiment with multiple responses and it would have been difficult, if not 
impossible, to track all events and their synchronization in the .dataaid 
file), I guess that one can do without EEfMRI in most cases.

The downside is that we didn't ever try to find out what was the problem 
with using the parallel port as input. E-Prime Support did not provide any 
solution for that either. 


Thank you for your help,
Christina

On Wednesday, May 14, 2014 11:17:43 AM UTC+2, andreou.... at gmail.com wrote:
>
> Thank you both for your advice! I'm going to try everything out and post 
> the results.
>
> Best,
> Christina
>

-- 
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To unsubscribe from this group and stop receiving emails from it, send an email to e-prime+unsubscribe at googlegroups.com.
To post to this group, send email to e-prime at googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/e-prime/d5211f02-d965-4bf1-aaea-4591e61c6684%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/eprime/attachments/20140531/bd9c1c9e/attachment.htm>