we most recently purchased a Cedrus Response Box of the RB-830 variant (2012 model).
The box installs fine and shows up in the Windows device manager as a "USB Serial Port (COM11)", like described on the Cedrus homepage.
I can access and monitor the box with HTerm without any problem. All keys send signals of 48bit length when pressed or released.
To test the box with Inquisit 184.108.40.206 (build Mar 23, 2011) I used the script Sean posted here: http://www.millisecond.com/community/forums/t/1013.aspx
The script defaults to COM3 in XID mode by specifying "/inputdevice = XID3", which I changed to XID11 to match the COM port settings of the Cedrus box on my system.
After starting the script Inquisit immediately issues the error:
System error 2: .Line 71, File .\ComPort.cpp
When clicking OK on this dialog, Inquisit pops up another error message stating
Inquisit can not access port COM11. Verify that this is a valid port on this machine.
It IS a valid port, as HTerm most convincingly proves. What's going on?
Addendum: I just installed the current stable version 220.127.116.11 (build Feb 28, 2012). Same result: same bug.
Another addition: I switched the RB-830 to COM mode by setting DIP switches 1 and 2 to high and changing the Inquisit script to "/ inputdevice = COM11".
Again, HTerm reads out the box correctly on COM11. All eight buttons are registered with the expected bit patterns.
Inquisit also exhibits the same behavior as before with identical error messages.
Any ideas anyone?
Try manually assigning a COM # between 1-9. This can be done via Windows Device Manager:
Properties of your device -> Port Settings tab -> Advanced... -> COM Port Number dropdown.
"To understand recursion, you must first understand recursion." - Unknown Zen Master
I did indeed try that workaround before posting. Assigning a 1-digit COM port actually makes Inquisit work perfectly well with the Cedrus box.
Unfortunately, on about half of our lab computers (~ a dozen), all COM ports below COM10 are in use.
That's why we would very much love Inquisit to be able to address COM ports above 10.
Maybe Sean can fix this in a future update.
Best wishes, Malte