| Author |
 Topic  |
|
|
Seniha
BIAC Alum
6 Posts |
 Posted - Mar 21 2003 : 2:22:30 PM
|
Dear all,
The '4 button-response box' at 4T has a problem with the second button. It does not always send a response signal. There were blocks of missing responses in the CIGAL output file. We first thought that the subject is missing/sleeping  Then we did a device test with CIGAL and saw that it is the button problem. Could anybody fix it?
thanks
seniha |
|
|
melissa.slavin
BIAC Alum
Australia
44 Posts |
Posted - Apr 03 2003 : 4:42:34 PM
|
| We also have had problems with the button box at the 4T. The second button does not work, and the third button has just started having problems. Apparently the fourth button does work, however we cannot test it before each scan as it is not linked to the testing function in Cigal (not sure why), so we are a little nervous about using it without testing it each time. This is quite urgent as it has affected some people's behavioural results. We need to use TWO buttons, in case you're going to tell me just to use the first. |
 |
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - Apr 11 2003 : 09:40:54 AM
|
I tested the button box on the 4T and all the buttons worked fine for me. I know that's not a very satisfying answer but it does make fixing things more difficult. There was a loose cable, which I screwed down tight at the beginning so that might explain the difference. I am ordering a spare joystick button box, and will also build another simple button box in the meantime so that we have backup options. The new IO-test function in CIGAL now shows all 8 input lines so that you can test all 5 buttons on the joystick box.
Jim |
|
|
|
mack
BIAC Alum
USA
19 Posts |
Posted - Apr 11 2003 : 5:04:01 PM
|
Scott and I just tested out the button box at the 4T and saw that all the buttons were working properly using the I/O test function of CIGAL. I think using I/O test before any experiment that uses the button box is good practice, since that is a high-traffic device.
There is a quirk with I/O test that does not affect ShowTime paradigms where if one presses a button extremely rapidly, I/O test can miss the release of the button and it appears to be "stuck". Pressing the button again fixes this. When running ShowTime files, CIGAL only logs the button press, not the release. I just wanted to make everyone aware of this so if you notice this issue in I/O test there will be no concern about the integrity of the output files from experimental runs. |
Edited by - mack on Apr 11 2003 5:04:44 PM |
|
|
| |
Topic |
|
Joystick/button-box at 4T
