Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Cedrus RB-830

NoaNoa
edited April 2017 in OpenSesame

Hi,

I am using the Cedrus RB-830 in Open Sesame using the SR-box plugin.

I do see that Open Sesame get the Cedrus responses, but I cannot figure out the numbers for the different keys.
I write to the logfile the "response" variable and in different runs when I press in the same key I do get different numbers for the "response".
I have 8 buttons on my box as shown here:

http://www.net-eng.it/prodotti/response-pad/RB-830.html

Did anybody use the Cedrus RB-830 and can suggest on the keys numbers ?
I also understand that there is an option that keys are stores when presseing or when releasing. How do I control that using the plugin?

Thanks!
Noa

Comments

  • I haven't used this myself, but as far as I know you need the open source python libs for xid.
    You can get them here --> https://github.com/cedrus-opensource/pyxid

  • I do have them already (otherwise I would expect the responses would not have been recorded at all)

    I am just looking for the documentation about the numbers the buttons are supposed to send...

  • I attach as example: I have a loop where I record the SRbox response. I tried it 8 times. All the times I pressed on the upper left button, and I got different "response numbers":

    count_new_srbox response response_new_srbox
    0 1 1
    1 2 2
    2 2 2
    3 1 1
    4 1 1
    5 1 1
    6 1 1
    7 1 1

    How is this possible?

  • Hello,


    Has this ever been resolved? I was thinking of using a Cedrus RB box and came across this problem which looks a bit odd.

  • So, I tested our RB-730 with Opensesame 3.3 today and am getting exactly the same problem as Noa above. They key labels logged seem completely random (times are rather accurate). How can this be solved?

  • Hi Art,

    I don't know anything about the Cedrus, and unfortunately don't have one available, so I also can't help in terms of testing, but given that it is a commercial product that you access in Opensesame via a Python api provided on Github, I wonder whether it would make more sense to file an issue on that Github repository, or ask contact the Cedrus support, rather than here on the forum? At least, I can't see where Opensesame is relevant for this specific issue. Not sure how responsive they are, but they are certainly more experienced with the device.

    Sorry,

    Eduard

    Buy Me A Coffee

  • Hey Eduard,


    Thanks for the tip. I was actually wondering if any other user has resolved this in the meantime as most of the forum threads on this are rather inconclusive. Weird given how popular Cedrus devices seem in psychology crowd.


    Anyway, since I don't Python I asked a colleague of mine to help. Will try to post on here whenever he finds away to get this to work.

  • Sounds like a plan! Good luck

    Buy Me A Coffee

Sign In or Register to comment.