RE: Inquisit breaking Cedrus Lumina LSC-400B respond pad

Back

Home
»
Millisecond Forums
»
Inquisit 4
»
RE: Inquisit breaking Cedrus Lumina LSC-400B respond pad

Inquisit breaking Cedrus Lumina LSC-400B respond pad

Author	Message
xiller09	xiller09 posted 11 Years Ago HOT Topic Details Share Topic
Group: Forum Members Posts: 21, Visits: 10	Hi guys, I'm having an issue using the Cedrus Lumina LSC-400B response pads with Inquisit and have now "broken" three of them. These devices run as Lumina products under the <xid> element. After using these products in Lumina mode controlled by Inquisit (http://cedrus.com/support/lumina/tn1202_lsc400_controller.htm) they no longer work in any of the other modes (i.e., with any other software), but continue to operate perfectly with Inquisit. Is there anything under the hood that could be causing these issues? It's not an individual unit, has occurred with both response pads receiving signals from fMRI scanners and TTL pulse generators, and with no shared computer hardware; so a this point I'm inclined to believe it's an Inquisit issue. Cheers.
	Reply Like 24
Dave	Dave posted 11 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 108K	You can find some information about the settings Inquisit applies to those pads in http://www.millisecond.com/forums/Topic13677.aspx Have you tried checking / changing the pad's settings prior to interfacing it with other devices / software (e.g. via Cedrus' xidon utility also linked from the above thread)?
	Reply Like 23
seandr	seandr posted 11 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 1.3K, Visits: 5.9K	Inquisit simply communicates with the device through it's published APIs, so it shouldn't be possible for Inquisit to literally break the device. I'll get with Hisham and see if we can figure out what's going on. -Sean Edited 11 Years Ago by seandr
	Reply Like 22
*Erik*	*Erik* posted 11 Years Ago ANSWER Post Details Share Post
Group: Moderators Posts: 13, Visits: 199	What other software are you trying to use to communicate with the Lumina? Is it possible for you to post the contents of the <xid> elements in question? Define "broken", (i.e. when the user hits a button no event is generated? or are the i/o pins not behaving as your setup expects? We set the device to use the XID protocol if we're configured to use it as an inputdevice or via an <xid> element. If a response box is used as a stimulus via the <xid> element we do set the lines to General Purpose (a10), the direction to output (a4), and optionally set the pulse duration (ap). All of which should be resettable via the Cedrus xidon tool. Thanks and Enjoy, Erik Developer at Millisecond Software, LLC.
	Reply Like 23
seandr	seandr posted 11 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 1.3K, Visits: 5.9K	Ok, spoke with Hisham at Cedrus. Inquisit switches these devices into XID mode (just as SuperLab does). It seems the other equipment is expecting the devices to be in a different mode. You should be able to change the modes using the utility Dave mentioned or via "a button press or two" according to Hisham. Lumina docs should have more details. -Sean
	Reply Like 23
xiller09	xiller09 posted 11 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 21, Visits: 10	Excellent, thanks Sean. I'll try out the utility Dave linked and let you know if I'm still having issues.
	Reply Like 19