How builder interacts with Cedrus Response box

Builder
1

OS (e.g. Win10): Win10
PsychoPy version (e.g. 1.84.x): 2020.1.0
Standard Standalone? (y/n) If not then what?: Y

I think this might be more reporting an issue than asking for a solution, but if anyone has any ideas please let me know :slight_smile:
I’m trying to use a Cedrus response box (RB-540) in my latest experiment. I initially got the error message mentioned in Trying to use v3.2 with Cedrus button box. Error: "Unable to find D2XX DLL. Please make sure ftd2xx.dll or ftd2xx64.dll is in the path.", but was able to fix that my adding the .dll files in the appropriate places.
To test out the response box i made a routine with only a text component and the response box component (named buttonBox as per default). When I tried to run just that I got the error “NameError: name ‘buttonBox’ is not defined”. I then generated the script and looked at the code, and it turns out the script uses the default name “cedrusBox_0” for the component, no matter what you name it. So when I then changed the name of my response box component to “cedrusBox_0” the script ran and behaved as it was intended.

Having done all that, I of course can only name the first cedrus component “cedrusBox_0”, so won’t be able to create any more. Besides that, i suppose i would run in to the problem described in https://groups.google.com/forum/#!topic/psychopy-users/FIltal9nDbw anyway?

So I suppose my questions are: Could the initial naming-problem be hotfixed? And what is the current best workaround for the problem of only being able to run the component in the first routine?

Regards
Örn

2

As an update to this; although one of the issues with using Cedrus response boxes was fixed in the 2020.1.1 release, I’m still running into an error when attempting to use the response box component through the builder interface.

Traceback (most recent call last):
  File "C:\Users\Örn\Exp\cedrusTest_lastrun.py", line 47, in <module>
    buttonBox.clock = core.Clock()
NameError: name 'buttonBox' is not defined

What seems to be happening is that after the cedrusBox_0 object is created at the start of the experiment, the buttonbox.clock = core.Clock() line is generated although buttonBox hasn’t been created yet.
The same line appears later, when initializing the buttonBox component, but only after buttonBox = cedrusBox_0

Would appreciate input from someone more knowledgeable about the best current workaround/solution.

All the best
Örn

3

@Oern
have you by any chance found a solution?

4

Unfortunately I can’t say that I have.
Ended up giving up on trying to find a fix because of time constraints and haven’t really bothered looking into it after that.
Please let me know if you figure something out!