| Author |
 Topic  |
|
|
Jeff_Browndyke
Junior Member
35 Posts |
 Posted - Jul 24 2007 : 1:07:44 PM
|
We're setting up a simple ePrime task for the 3T, which should require the uni-manual 4-button/joystick box. Are the four keys for this box already mapped to the task computer keyboard? If so, what keyboard keys correspond with buttons 1-4 (left to right)?
If there is direct button-to-keyboard mapping for this response box, is it necessary to designate SRBOX in ePrime?
Thanks,
Jeff |
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - Jul 24 2007 : 1:29:55 PM
|
The ePrime SRbox is not set up as a keyboard device on our scanners. The 4 keys send in code values 1,2,4, & 8 and the scanner trigger pulse sends a code value of 16. These are binary values and can be combined by addition (e.g. pressing buttons 2 and 4 together will send a 10).
I'm not an ePrime expert but I suspect you do need to specify that you are using the SRBox device in the software. It is connected to serial port COM1, which is probably the default setting.
Jim |
 |
|
|
Jeff_Browndyke
Junior Member
35 Posts |
Posted - Jul 24 2007 : 4:00:19 PM
|
Thanks, Jim.
Designating SRBOX in ePrime as one of the input devices is very easy. I just wasn't certain if the 4-button box on the 3T was already set to map out a keyboard numerical response (i.e., 1, 2, 3, ...). I already have Keyboard set as one of the input devices for our task, so now I'll just add SRBOX to the list.
Appreciate your help.
Cheers,
Jeff |
|
|
|
Jeff_Browndyke
Junior Member
35 Posts |
Posted - Aug 06 2008 : 12:28:39 AM
|
Jim,
Is the NeuroScan 4-button box still set-up on COM1 at the 3T? Our e-Prime code, which used to work with this preferred box, now only works with the paired bi-manual response box. And, even though it appears to work, for some reason we get consistent intrusion of "5" responses, when only the "1" and "2" buttons are depressed during the task.
Thanks,
Jeff |
|
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - Aug 06 2008 : 09:47:46 AM
|
The NeuroScan box is still connected. There is an inventory of all hardware connected at each scanner at:
http://fourier.biac.duke.edu/wiki/doku.php/biac:experimentalcontrol:inventory
The 4 buttons send data codes 1,2,4,8 which ePrime recognizes as buttons 1-4.
The scanner trigger pulse is (and I believe always has been) connected as button 5 and
sends a 16 code every time the scanner pulses (1/TR). I believe that is the standard
ePrime arrangement. You can set your input parameters to expect button 5 as a trigger
start signal, and then only pay attention to buttons 1-4 for user responses.
There has been some ePrime confusion this past week with the installation of version 2.
If your program is behaving differently it may be because the parameters you have been
using were either changed in transition or are somehow interpreted differently.
Either way I'm pretty sure you will be able to adjust your settings to only accept
button 5 as a trigger signal. Let us know if you can't.
Jim
|
|
|
|
Jeff_Browndyke
Junior Member
35 Posts |
Posted - Aug 07 2008 : 2:30:57 PM
|
Thanks, Jim. I appreciate your time and input. I now know what the problem is, but not how to implement the change.
Does anyone lurking here have experience in getting proper *.edat output using the Neuroscan 4-button box and ignoring the scanner trigger pulse? Where would I specify in the *.es code to ignore "5" signals throughout the run?
Jeff |
|
|
|
smoski
New Member
16 Posts |
Posted - Aug 07 2008 : 2:43:20 PM
|
Assuming you're using the eStudio GUI to make the changes, open the properties for the object linked to response collection. On the Duration/Input tab, list your allowable responses (e.g., 1234). By listing allowables and omitting 5 as allowable, it should ignore the 5 response. You will need to change this for all objects collecting responses, but not for the object that collects the trigger response.
HTH!
|
|
|
|
Jeff_Browndyke
Junior Member
35 Posts |
Posted - Aug 07 2008 : 2:59:22 PM
|
I was wandering around the code just now and saw the same thing. Thanks! I had that field previously set as {ANY}, which allowed the scanner trigger to intrude. I don't have an object set up to collect the trigger. What would be the advantage of doing this other than avoiding having the tech to simultaneously press keys to start the scanner and task?
To add...if I were to set our task pause screen to accept the "5" scanner trigger start, then this would necessitate that the *.ebs file only be started/prepped after the localizer, right (i.e., the localizer would start the task if you prepped the task file too early)?
And, lastly, are TTL pulses ("5" signals) sent out during the disdaq period??? This would be very helpful to know as I make the modifications to our task.
Jeff |
Edited by - Jeff_Browndyke on Aug 07 2008 3:49:15 PM |
|
|
|
smoski
New Member
16 Posts |
Posted - Aug 07 2008 : 4:09:27 PM
|
| I'd say the advantage of having the scanner trigger is one of precision -- an automatic trigger is going to be more exact timing-wise than a person hitting both buttons at once by hand. And yes, you would have to start the task after the localizer. I'm pretty sure the TTL pulses are sent any time the scanner is active, including during disdaq periods. Others please correct me if I'm wrong! |
|
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - Aug 07 2008 : 4:54:04 PM
|
Correct -- Scanner trigger TTL pulses are sent at each TR including Disdaqs. They are also sent during prescans. So you want to Prep the scanner, then set your paradigm to start waiting AND make sure your paradigm knows to include the Disdaq period, if any, before actually starting the task.
Jim |
|
|
| |
Topic |
|
Small 4-button box on 3T
