Robotron P1 Start stuck on

Grbgemen

Active member
Joined
Mar 12, 2008
Messages
1,167
Reaction score
8
Location
Lincoln, Nebraska
I posted about this before but never got the issue fixed.

Problem is, player 1 start is always stuck on even with the switch completely unhooked.

First suggestion was to unplug the widget board with the game on and in the input test screen. When i did this, all other switches activated and the player 1 start deactivated...

So i thought it was okay to rule out the widget board being the problem. I ended up picking up a working CPU from Saltbreez on here and finally got around to testing it today.

Same problem still exists. Not sure where i should go from here.
 
Still sounds like the widget board to me. I had a similar problem on joust and it was a bad chip on the board. The bird would run left even when I unhooked the joystick completely. Changing the chip fixed it. The only problem is figuring which chip is the problem. I think there are 3-4 chips that could be the bad one.
 
If you are interested, I do repair the I/O boards. I charge $15 + shipping (usually about $5 in Priority Mail small boxes). If you were closer I'd just swap yours for a known good one.

ken
 
I posted about this before but never got the issue fixed.

Problem is, player 1 start is always stuck on even with the switch completely unhooked.

First suggestion was to unplug the widget board with the game on and in the input test screen. When i did this, all other switches activated and the player 1 start deactivated...

So i thought it was okay to rule out the widget board being the problem. I ended up picking up a working CPU from Saltbreez on here and finally got around to testing it today.

Same problem still exists. Not sure where i should go from here.


Pay postage and I will swap your Widget for a know working one.

Saltbreez
 
I just quickly went through the schematics and it looks like data line 2 is stuck on somewhere. I would check the RAM in 1M, 2M and 3M. In the good old days we just put a finger on the top of each of the RAMs and which ever one burned the fingerprint off was the bad one. (I am a little wiser now... just a little.) It looks as though they are socketed so you might just try swapping them around. hope that helps!
 
I just quickly went through the schematics and it looks like data line 2 is stuck on somewhere. I would check the RAM in 1M, 2M and 3M. In the good old days we just put a finger on the top of each of the RAMs and which ever one burned the fingerprint off was the bad one. (I am a little wiser now... just a little.) It looks as though they are socketed so you might just try swapping them around. hope that helps!

The MPU he is using has tested good with another widget board. This is the second MPU he has reported the issue with. Not likely this problem is on the MPU.

Saltbreez
 
saltbreez,

That would be very generous of you.

Will try and get it in the mail today. still have your address from before.

Thanks.
 
Back
Top Bottom