Srbox e prime number pad serial#
Srbox e prime number pad driver#
Srbox e prime number pad code#
Srbox e prime number pad trial#

You might first want to figure out whether your serial port communication actually works the SRbox isn't all that sophisticated. If not, then depending on the number of devices installed, you could try disabling a few, see if that helps. In short, however, 1) check in device manager whether the SRbox is in fact on a port between 1 and 4. A long bit of the Cedrus response box installation help went into getting it to work in such a way that the IRQ is valid for E-Prime. There was something, if memory serves, in the issue that E-Prime only uses the first 4 IRQ ports or some such. I've found, often enough, that the specific IRQ port of the serial port can be a problem. If you turn the SR-box off and on (all lights should then be on), and run e-prime, is the thing detected or does it immediately come up with the error? Is it there? You could try reinstalling E-Prime. Some better coding on PST's part should have integrated it a bit better in Windows, but you can't expect too much for a couple of hundreds of dollars and many years of development, I suppose.

Srbox e prime number pad driver#

check in device manager whether the uncertified 'unknown' sr-box driver is actually there. I am, however, somewhat in awe that it ran on a 64-bit win7 pc! Anyway, two thoughts: I do not think it is anything to do with Dell, as such - my ancient (I think, about 7/8 years old by now) latitude has never got into problems with e-prime, despite nowadays running win7 (a mistake on my part, it's really far too old for that).

Srbox e prime number pad trial#

I only want the trial to terminate after 'target' picture is shown, but want to know if the button is released / pressed earlier than that.Generally, you probably want to check with PST - they should be able to help out. Response_logging = log_active is in the header. But when I set 'all-responses = true' for a trial, it terminates upon a release, even if it is before a target.

Going back to your earlier point about monitoring releases (May 17th) - You're right, it would be good to know if subjects have released and pressed the key before the target has appeared. # or response_active = true if not a target or not using targets You will want to do that.Р”Р„n example of a trial where this approach would work: To prevent this, set the 'response_logging' header parameter to 'log_active'. If you have multiple active stimuli appearing around the same time, this won't work because codes from the first press will be matched to both stimuli even though there was only 1 response.Р”Р„lthough the response will be ignored for matching, trial duration, and response statistics purposes, they will still appear in the logfile. If you use the response matching features, once the stimulus is matched, Presentation will ignore the repeated codes sent by the box, assuming they stop coming before the next active stimulus occurs. (See 'Presentation Help : Help Guide : Stimulus Presentation : Button Responses : Response Matching). If you set the 'all_responses' trial parameter to 'false', Presentation will ignore responses that occur when no stimuli are active. You can tell Presentation to ignore certain responses.

Srbox e prime number pad code#

I figure that maybe something could be added between trials to flush the button box after the first code is sent? Do you know how this could be done or have any alternative suggestions? You mentioned before that things can possibly be arranged to overcome this problem. So far so good, but as you suggested, the button box continually sends codes after a button press which means that one press races through dozens of trials. Output_port_manager.get_port( 1 ).send_code( 224 ) Р”Вoes work placed at the beginning of my PCL file, but seemingly only once the box has been initialised with 'test'. This then allowed me to test the buttons in the input devices tab (which have the codes 1,2,4,8,16 running left to right). I thought you might be interested to know that I've had something of a breakthrough - It seems that the SR box can be initialised if, after I've added a serial port in the port settings tab, I click on 'test', and then add 224 to 'send code'.