Inquisit 5 and Cedrus Response Pad RB-530:


Author
Message
Natalia
Natalia
Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)
Group: Forum Members
Posts: 5, Visits: 34
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 105K
Natalia - Tuesday, November 28, 2017
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia

Hi Natalia

> At the same time, when I change the valid response to "anyresponse" [...] Inquisit does react to the buttons pressed.

When you run the script with /validresponse = (anyresponse), what are the values logged in the resulting data file's "response" column?

Thanks,
-David

Natalia
Natalia
Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)
Group: Forum Members
Posts: 5, Visits: 34
Dave - Tuesday, November 28, 2017
Natalia - Tuesday, November 28, 2017
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia

Hi Natalia

> At the same time, when I change the valid response to "anyresponse" [...] Inquisit does react to the buttons pressed.

When you run the script with /validresponse = (anyresponse), what are the values logged in the resulting data file's "response" column?

Thanks,
-David

Hi David,
The values are '112' and '176' (for buttons 3 and 5 correspondingly). When I add them to the script (see below) and run it, I have the same problem again.

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ responsetrial = (112, correctmessage)
/ responsetrial = (176, errormessage)
/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
<trial>

Thanks,
Natalia
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 105K
Natalia - Wednesday, November 29, 2017
Dave - Tuesday, November 28, 2017
Natalia - Tuesday, November 28, 2017
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia

Hi Natalia

> At the same time, when I change the valid response to "anyresponse" [...] Inquisit does react to the buttons pressed.

When you run the script with /validresponse = (anyresponse), what are the values logged in the resulting data file's "response" column?

Thanks,
-David

Hi David,
The values are '112' and '176' (for buttons 3 and 5 correspondingly). When I add them to the script (see below) and run it, I have the same problem again.

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ responsetrial = (112, correctmessage)
/ responsetrial = (176, errormessage)
/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
<trial>

Thanks,
Natalia

Hi Natalia,

Thanks -- the values you should enter in /validresponse should definitely be the numerical values 112 and 176 then. That's what Inquisit "sees" as the responses coming from the box (not the button number). Could you check if the box works with xid test script ( https://www.millisecond.com/download/library/v5/cedrus/xidresponsetest.iqx ) and post the resulting data file here? To attach a file to a post click +Insert -> Add File.

Also, does your script's behavior change in any way when specifying

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ beginresponsetime = 251
/ branch = [if (trial.test1.response==112) trial.correctmessage]
/ branch = [if (trial.test1.response==176) trial.errormessage]
/ branch = [if (trial.test1.response==0) trial.timeoutmessage]
/ pretrialpause = 250
<trial>
Natalia
Natalia
Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)
Group: Forum Members
Posts: 5, Visits: 34
Dave - Wednesday, November 29, 2017
Natalia - Wednesday, November 29, 2017
Dave - Tuesday, November 28, 2017
Natalia - Tuesday, November 28, 2017
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia

Hi Natalia

> At the same time, when I change the valid response to "anyresponse" [...] Inquisit does react to the buttons pressed.

When you run the script with /validresponse = (anyresponse), what are the values logged in the resulting data file's "response" column?

Thanks,
-David

Hi David,
The values are '112' and '176' (for buttons 3 and 5 correspondingly). When I add them to the script (see below) and run it, I have the same problem again.

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ responsetrial = (112, correctmessage)
/ responsetrial = (176, errormessage)
/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
<trial>

Thanks,
Natalia

Hi Natalia,

Thanks -- the values you should enter in /validresponse should definitely be the numerical values 112 and 176 then. That's what Inquisit "sees" as the responses coming from the box (not the button number). Could you check if the box works with xid test script ( https://www.millisecond.com/download/library/v5/cedrus/xidresponsetest.iqx ) and post the resulting data file here? To attach a file to a post click +Insert -> Add File.

Also, does your script's behavior change in any way when specifying

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ beginresponsetime = 251
/ branch = [if (trial.test1.response==112) trial.correctmessage]
/ branch = [if (trial.test1.response==176) trial.errormessage]
/ branch = [if (trial.test1.response==0) trial.timeoutmessage]
/ pretrialpause = 250
<trial>

Hi David,

Thank you very much for trying to help!

Yes, the response box does work with the xid test script well, and this is where I took "112" and "176" values from. Unfortunately, I can't attach the output file right now, but I will do it in a bit.
As for the "branch" thing, the script's behavior didn't change, "no reaction" to pressing the buttons. 
Natalia
Natalia
Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)
Group: Forum Members
Posts: 5, Visits: 34
Dave - Wednesday, November 29, 2017
Natalia - Wednesday, November 29, 2017
Dave - Tuesday, November 28, 2017
Natalia - Tuesday, November 28, 2017
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia

Hi Natalia

> At the same time, when I change the valid response to "anyresponse" [...] Inquisit does react to the buttons pressed.

When you run the script with /validresponse = (anyresponse), what are the values logged in the resulting data file's "response" column?

Thanks,
-David

Hi David,
The values are '112' and '176' (for buttons 3 and 5 correspondingly). When I add them to the script (see below) and run it, I have the same problem again.

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ responsetrial = (112, correctmessage)
/ responsetrial = (176, errormessage)
/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
<trial>

Thanks,
Natalia

Hi Natalia,

Thanks -- the values you should enter in /validresponse should definitely be the numerical values 112 and 176 then. That's what Inquisit "sees" as the responses coming from the box (not the button number). Could you check if the box works with xid test script ( https://www.millisecond.com/download/library/v5/cedrus/xidresponsetest.iqx ) and post the resulting data file here? To attach a file to a post click +Insert -> Add File.

Also, does your script's behavior change in any way when specifying

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ beginresponsetime = 251
/ branch = [if (trial.test1.response==112) trial.correctmessage]
/ branch = [if (trial.test1.response==176) trial.errormessage]
/ branch = [if (trial.test1.response==0) trial.timeoutmessage]
/ pretrialpause = 250
<trial>

Hi Dave,
You may find the output file in the attachement.
Thanks!

Best,
Natalia
Attachments
xidtest_raw.iqdat (244 views, 198 bytes)
Natalia
Natalia
Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)Partner Member (526 reputation)
Group: Forum Members
Posts: 5, Visits: 34
Dave - Wednesday, November 29, 2017
Natalia - Wednesday, November 29, 2017
Dave - Tuesday, November 28, 2017
Natalia - Tuesday, November 28, 2017
Hello everyone,
While working with Inquisit, I have faced some difficulties with making the Cedrus Response Pad RB-530 work with the file I created for my experiment.
I would like to use both a keyboard and the response pad for running a study, where the keyboard is used by default for instructions (i.e. <page instructions>) and the response pad is used for responding to experimental trials. 
I followed the guidelines available on the millisecond.com. Thus, I installed the appropriate driver, checked the correspondence between buttons and responses, specified them for valid response, correct response, etc., and inserted  "/ imputdevice = XID" in each trial code.
When I run the experiment, the Inquisit seems to not react to the buttons I have pressed, thus I keep receiving timeout messages instead of correct/incorrect feedback.The scripts itself worked well when I run this file customed for the keyboard responses only (without XID).
 My trials look like that:

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (3, 5) #Here, I was trying to set it to the response meanings, like (112, 176)

/ timeout = 1800
/ responsetrial = (3, correctmessage)
/ responsetrial = (5, errormessage)

/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
</trial>

At the same time, when I change the valid response to "anyresponse", the Inquisit does react to the buttons pressed, and I receive correct message feedback since any response is considered to be correct. 

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (anyresponse)
...

Has anyone had similar problems with setting the validresponse buttons? Or maybe anyone knows what is wrong here? I would really appreciate any help.

Cheers,
Natalia

Hi Natalia

> At the same time, when I change the valid response to "anyresponse" [...] Inquisit does react to the buttons pressed.

When you run the script with /validresponse = (anyresponse), what are the values logged in the resulting data file's "response" column?

Thanks,
-David

Hi David,
The values are '112' and '176' (for buttons 3 and 5 correspondingly). When I add them to the script (see below) and run it, I have the same problem again.

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ responsetrial = (112, correctmessage)
/ responsetrial = (176, errormessage)
/ responsetrial = (noresponse, timeoutmessage)
/ pretrialpause = 250
<trial>

Thanks,
Natalia

Hi Natalia,

Thanks -- the values you should enter in /validresponse should definitely be the numerical values 112 and 176 then. That's what Inquisit "sees" as the responses coming from the box (not the button number). Could you check if the box works with xid test script ( https://www.millisecond.com/download/library/v5/cedrus/xidresponsetest.iqx ) and post the resulting data file here? To attach a file to a post click +Insert -> Add File.

Also, does your script's behavior change in any way when specifying

<trial test1>
/ stimulustimes = [1 = test1; 251 = postmask]
/ inputdevice = XID
/ validresponse = (112, 176

/ timeout = 1800
/ beginresponsetime = 251
/ branch = [if (trial.test1.response==112) trial.correctmessage]
/ branch = [if (trial.test1.response==176) trial.errormessage]
/ branch = [if (trial.test1.response==0) trial.timeoutmessage]
/ pretrialpause = 250
<trial>

Hi Dave,

We have found an alternative solution for the problem. 
The script works well with Inquisit 4, not the Inquisit 5. Thus, I will stick to the Inquisit 4 instead :-) 

Best,
Natalia
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search