Millisecond Forums

We are facing massive problems with operating our Cedrus RB-830 response pads reliably under Inquisit. Without any indication of reproducibility, our lab computers frequently fail to detect a Cedrus response pad. Our scripts invoke the response pad like this:

<defaults>
/ inputdevice = XID_cedrus
</defaults>

<xid XID_cedrus>
/ product = responsepad
</xid>

All of our lab computers at least once every few days will fail to detect the response pad. The error message is

No XID devices detected. Besure the device is plugged in, turned on (if necessary), and the appropriate driver installed.

There are no preconditions which reliably lead up to the error. It will occur no matter if the computer was just booted up, woken up from hibernation, or had Inquisit successfully detect the response pad once, never, or multiple times before. Sometimes, only restarting the computer solves the problem, at other times trying to run Inquisit again and again until it finally detects the pad will suffice.

On all our computers, the XID device is either assigned to COM5 or to COM7. We have set a baud rate of 115200 and configured all response pads identically. The error occurs on different hardware (Core Duo, Core i5, Core i7), under multiple OS'es (Win7 64bit, Win 8.1 64bit) and with multiple versions of Inquisit 4. With Inquisit 3, we never had any such issues, hence we would assume Inquisit 4 to be the culprit.

How can we help to track down the bug?

Best wishes
 Malte