RE: ser up port signal

Back

ser up port signal

Author	Message
marjalena	marjalena posted 9 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 4, Visits: 43	Hi all, I have a problem by setting up the port for the cyberball task. When I try to run the script, the following error always occurs: "Unable to obtain the address for parallel port 1". I checked the port number in the system device manager (it is named LPT1 there) and tried also some portnumbers at the parallel port monitor tool where the error occured too although a trigger is sent. So what could be the reason for that error? I also used another task with Presentation and with the same port number and it works well with that. Or is the port set up not working with the free version? For better understanding, here are the port and appropriated trial definitions: (trial "wait" is the added "wait for connection" text before the ball tossing game begins) **********TRIALS & BLOCKS************************ <trial wait> / validresponse = (0) / trialduration = round(5000) / stimulustimes = [0=blankscreen; 500=wait, onsetsignal_connect; 1500=endsignal_connect; 4500=blankscreen] </trial> <block wait> / trials = [1=wait] </block> ********************************************************************************************************** Trigger ************************************************************************************************************ <port onsetsignal_connect> / port = LPT1 / subport = data / items = ("00000010") </port> <port endsignal_connect> / port = LPT1 / subport = data / items = ("00000000") </port> Thank you very much for your help. marjalena
	Reply Like 40
Dave	Dave posted 9 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	The <port> definitions look okay. Also, there aren't any restrictions re. port functionality in an unregistered / trial Inquisit Lab installation. The fact that you signals get sent despite an error via the Parallel Port Monitor is weird, but -- on the other hand -- confirms that your <port> elements are fine and that your hardware is working. Given the above, I frankly have no clear idea where the error originates. Two guesses: - It may be a driver issue. Double-check if the driver for your LPT port is up to date (latest drivers may be included in the chipset drivers for your system's mainboard). - More likely: A permissions issue or the like. Windows can be a bit weird in terms of how it grants users and applications access to parallel ports. Try executing Inquisit with administrative privileges (right-click on the Inquisit icon -> Run as administrator...) and let me know if that makes the error go away. While written for dealing with LPT issues related to printers, some useful things to check can be found at http://smallbusiness.chron.com/win32-port-lpt1-could-not-opened-access-denied-47050.html Let me know what you find.
	Reply Like 47
marjalena	marjalena posted 9 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 4, Visits: 43	Dear Dave Thank you for your help and support and sorry for my delayed response. I just tried it out with "run as admin" but the error occurs anyway. In the parallel port monitoring tool, when I use port number:1 port address: 378 and pin 3 "send", the trigger is sent to windaq on the other pc. I think there must be something wrong in the script because in that toolboy the port works. Can I or do I have to define the port address in the skript somewhere because it always tells me that it couldn't obtain the address of port 1. Or do you have any other ideas? Thank you... marja
	Reply Like 58
Dave	Dave posted 9 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 104K	Hi Marja, Assuming that the code snippets in your initial post still apply, port address appears to be specified properly via / port = LPT1 / subport = data Now, it may be possible that there's something peculiar about how the parallel port is configured / set up on the operating side of things (a non-standard, modified based address; a particular mode; cf. http://computer.howstuffworks.com/parallel-port2.htm ) which somehow prevents Inquisit from retrieving the address. What are the exact technical parameters of the port on your system? (Screenshots of the Windows device manager details and the parallel port monitor's settings may be helpful here.)
	Reply Like 45