Reading Parallel Port as Response Device

Back

Home
»
Millisecond Forums
»
Inquisit 4
»
Reading Parallel Port as Response Device

Reading Parallel Port as Response Device

Author	Message
DrLand	DrLand posted 10 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 14, Visits: 38	Great! CRTL+B does exactly what I was trying to do. Thanks again!
	Reply Like 78
Dave	Dave posted 10 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	A given <trial> element can only have one type of /inputdevice, so that's not really possible. If your aim is merely to terminate a given <block> for testing purposes, you can use the built-in CTRL+B key combo. Otherwise, you'd have to set up a separate <trial> element with /inputdevice=keyboard after one (or several) of your regular <trial>'s and then use that <trial>'s response to /stop the <block>.
	Reply Like 67
DrLand	DrLand posted 10 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 14, Visits: 38	Hi Dave, Thanks for your quick response. Your reply cued me in to the problem. I have it working now. It works with both the /responsemessage and /correctresponse. Basically what was happening was...at the start of the trial, one pin I had set to go high, and another set to go low. At the end of the trial, the pins would switch in preparation for the next trial. Even though I was switching both pins at the "same" time, one pin was switching first and thus throwing a different value for a split second. So my data output file wasn't showing the correct value. I was able to fix this on the device side of things. One final quick question: My trials are based on input from the parallel port, but it would be nice if I could /stop a block early with input from a keyboard. I believe I read in the documentation that you couldn't mix parallel port inputs with a keyboard input. I wasn't sure if there was any work around for this.
	Reply Like 70
Dave	Dave posted 10 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	What happens when you use /responsemessage instead of /correctmessage? / responsemessage = (241, lowtone, 1000) Also, what do the 'response' and 'correct' columns in the data file actually indicate for the given trial? Are the values recorded there '241' and '1', respectively?
	Reply Like 59
DrLand	DrLand posted 10 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 14, Visits: 38	Ok, to follow up on the previous script, I have run into another problem when reading inputs from the parallel port. I am wanting a sound stimulus to be played when a correctresponse occurs from the parallel port. Here is the code: <trial lowtones> / stimulusframes = [1=lowtrials] / inputdevice = lptdata3 / validresponse = (241, 244) /correctresponse = (241) /correctmessage = true(lowtone, 1000) / branch = [trial.trialendcheck] </trial> <trial trialendcheck> / inputdevice = lptdata3 / validresponse = (244) </trial> The trial starts and stops fine, but no tone is played. However, if for instance I don't use the parallel port for the input, but base it on a keyboard command...the tone plays when the correct response is given. It's only when I'm using the parallel port input that I'm not getting the sound feedback.
	Reply Like 61
Dave	Dave posted 10 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	Great! And thank you for the kind words, too!
	Reply Like 77
DrLand	DrLand posted 10 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 14, Visits: 38	Bingo! That's it! The level of support on this site is unmatched. Thanks for all the help.
	Reply Like 84
Dave	Dave posted 10 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	Here's an idea. Simply have another <trial> check for the 'low' state instead of using /posttrialsignal. I.e., do <trial checkportsignal> / stimulusframes = [1=button] / inputdevice = lptdata3 / validresponse = (241) / branch = [trial.checkportstatuschange] </trial> <trial checkportstatuschange> / inputdevice = lptdata3 / validresponse = (242) </trial> That should do the trick (provided I'm not missing anything).
	Reply Like 57
DrLand	DrLand posted 10 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 14, Visits: 38	This isn't something that I can control. I am tracking the trajectory of a ball toss. When the ball crosses a start line, my motion analysis system will turn pin 2 to high. When the ball rolls past the finish line, the system turns pin 2 back to low.
	Reply Like 70
Dave	Dave posted 10 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	For how long does your device keep the pins high? Can you configure that duration?
	Reply Like 61