| T O P I C R E V I E W |
| petty |
Posted - Oct 14 2004 : 10:38:26 AM
In the 4T suite there are 2 experimental computers, and therefore 2 experimental joysticks/button boxes. Our task (ADVT) has a calibration function that calculates the range of motion of the joystick and applies it to our tracking paradigms. The computer on the left appears to be the lesser of 2 evils when it comes to this issue. The joystick in only "slightly" responsive, in that it may move the cursor 2inches to the left of right, and maybe 1 inch up or down. The computer on the right, will barely move the cursor at all and it is worthless for us to even try to use it. This poses questions and problems when it comes to our paradigms that contain 2 orders of tracking ... easy and difficult, it concerns me that we are only getting difficult and down right annoying instead. Is there anything that can be done about this? I've replaced rubber-bands within the joysticks before, but this only helps with the problems for about a day or so.
Also, we keep getting windows errors when the task attempts to write a logfile at the end of each run, causing the task to crash (after the run) ... "run-time error 9, subscript out of range". This error has yet to be replicated on any computer except the left experimental computer. Any ideas, suggestions? |
| 9 L A T E S T R E P L I E S (Newest First) |
| petty |
Posted - Jan 28 2005 : 3:18:52 PM
The Joystick with WHITE buttons is currently connected to the right experimental computer.
The Joystick with YELLOW buttons is connected to the left experimental computer (which is not set up to be triggered by the scanner).
I changed them because when calibrating through windows, the WHITE one was way more accurate and utilized the entire motion field, while the other one was stuck in the lower hemisphere of the setup window. |
| jim.voyvodic |
Posted - Nov 29 2004 : 5:45:21 PM
The second joystick has not yet been repaired (hopefully back next week) but the Tech can easily move the one that's connected to the XP computer to the Win98 computer if it's needed.
It's just a USB cable that comes out of one and plugs into the other.
Jim |
| sem |
Posted - Nov 29 2004 : 5:00:45 PM
Has a new/repaired joystick been connected to the Win98 machine on the 4T? If not, is there a timeframe?
Thanks!
Sara |
| jim.voyvodic |
Posted - Nov 08 2004 : 11:53:48 AM
Joystick update.
There seems to be a hardware problem with one of the joysticks at the
4T scanner (it does not respond to left-right motion). That joystick
will be sent back for repair.
The other joystick seems to work fine now. It was out of calibration
(and the stick was off-center) but we recalibrated and now it seems okay.
The working joystick is connected to the WindowsXP computer. There is
currently no response box connected to the Windows98 computer at the 4T.
Jim |
| ayse.belger |
Posted - Nov 04 2004 : 1:33:43 PM
The joystick on either response box does not work.
We have halted the PPG4 projects that require tracking until the joystick is fixed. 
Can you help us? |
| petty |
Posted - Oct 15 2004 : 09:26:38 AM
i actually did reboot the computer before starting yesterday. The VB task wrote out one logfile, but not the other (there are 2, one with tracking error and the other with event location).
Using XP isn't a problem for us. The only reason we aren't currently using it right now is that the joystick connected to the XP computer is virtually inresponsive. If we can switch the joysticks, then we can use the XP computer. |
| jim.voyvodic |
Posted - Oct 15 2004 : 09:21:51 AM
The left monitor in both scanner set-ups is generally
connected to the old Windows 98 computer. Those systems
are unlike any others at BIAC in 2 respects. First,
they are Windows 98, so it is possible that your Basic
program runs slightly differently on Win98 vs Win/NT or
Win/XP. That's possible.
The more likely problem is due to the fact that the Win98
computers have much lass memory than any other BIAC
computers. In addition, Win98 does not manage memory very
well, so after quitting some applications memory is sometimes
not completely released. This means that over time the
amount of memory, which was not large to begin with, dwindles
even more.
Your subscript out of bounds error may be because the
program was not able to allocate as much memory as it expected.
If that's the case the software should be fixed to make sure that
there is enough memory, and either make do with what's available
or tell you that there isn't enough to run.
If memory is the problem, you could try rebooting the computer
before you start to make sure it has a clean slate and all free memory is available.
The alternative is to run on Windows XP. We have been trying to
get everybody to run on XP so that we can retire the Win98 system
and replace it with something better. Why are you using Win98
for your experiments?
Jim |
| petty |
Posted - Oct 15 2004 : 08:13:15 AM
the tasks are made with visual basic |
| jim.voyvodic |
Posted - Oct 14 2004 : 10:31:57 PM
Chris,
What software are you using?
Jim |
