Aristocrat LUCKY STRIKE video gaming machine vintage 1993

[rickoshay]

This is my first post, am new to this and sorry if i'm in the wrong area, anyway....I am in Australia and I was given an Aristocrat LUCKY STRIKE video gaming machine vintage 1993, the screen/game play is frozen showing "memory card disabled". I have had a look and see that a U2 memory chip is missing. Of course I am wanting to replace this chip, can anyone offer any help or advice please?

[palindrome]

Is this a Mark 4 or 2.5 machine ?

More pictures would help.

[edtruman]

looks like a 2.5 to me, and my  Caribbean Gold memory board is the same and does not use U2

[rickoshay]

Thanx for prompt reply, don't know version no. - what other pics would you like?

[proten]

Post a picture of the machine and MPU.

[palindrome]

I'd start by checking the  ribbon cable ( near r28 ) and pins underneath on both ends. If its been forced in then its likely some could be bent.

[rickoshay]

Thanx to all viewing and helping out, here are a couple more pics 

[proten]

Is that a broken DIP switch at W3-W4?
(Right lower corner of the top board)

[palindrome]

Looks that way but I don't know if that's causing his problem.

Perhaps you could try and reproduce it ?

[rickoshay]

Well I win the "stupid" award  , I checked out the cable for continuity and bent pins, all seems good BUT I did it with the power on and shorted some pins from the underside of the memory board on the hopper handle  , now the screen states ***MAIN DOOR OPEN*** when the door is closed, checked the white push button - continuity when open, open circuit when pushed in. I see there is another type of "security" in the form of what looks a little like a clear LED in a housing on the door, that when the door is closed goes over the top of maybe a sensor underneath the white button on the body. Would like to know how to bypass this. Does the "main door open" warning override the "memory board disconnected" warning? Am hoping by disconnecting?reconnecting the cable on the memory board it fixed that problem

[proten]

sounds more like you shorted out something.
It's not a good idea to do testing with the
power on unless you have to.

[rickoshay]

I won't do that again, a case of live and learn, do you know the sensor I am talking about?

[proten]

You mean the "Door Optics"?

[rickoshay]

Yes, do you know how I can test it? I may have damaged it and would like to bypass it

[palindrome]

The real problem here is that if it shorted at the board then there is a good chance you baked something.

I suggest you to try and get into the robot test and test all push buttons including the audit and jackpot keys.

When you test an input, a message should be displayed on the screen confirming that it is working.

To get into robot test.

1. Open the main door.
2. Switch the machine off.
3. Hold in Robot Test button on the main board while turning the machine on.

You should now be in the Robot test mode.

Test all inputs including all push buttons on the main board, you could then also trouble shoot the main door.

Most of the I/O for the buttons and switches connect to various ports on a peripheral interface adapter ( U3 which is a programmable gate array on the mark 4 ) , if that is fried then you probably won't be able to get into robot test mode to begin with or most inputs won't be working.

[rickoshay]

Thanx for reply, which button is the robot test button?
How do I tell what version machine this is? Behind the hopper in the back it says 1993, would love a manual for this, want it up and running soooooo much
Cheers

[palindrome]

You have a Mark 2.5 machine. Unfortunately a manual for this machine is proving difficult to find.

Robot test button is the first red button from the left.

[rickoshay]

Thanks for prompt reply, keen to get it fixed, will do the test you suggested.

[rickoshay]

Tried several times turning on the machine whilst holding down the first of six red buttons from the left.........and nothing.........what have I done? must persist!
When I turn it on an assembly under the coin mech activates then releases, that's it

[proten]

Will the error clear now?
You have a main door open tilt now.
If you close the door will it play or go
back to the first error?

[rickoshay]

thanks again, the pic above is how the screen is door open or closed, its frozen. 

[proten]

I would power down the slot then pull the main board and verify the
Robot test button is working with a DVOM.
If it tests good then I would look for someone to repair your board.

[rickoshay]

DVOM? digital V? O? meter, am I checking that when the button is pushed, there is continuity?
When you say get the board repaired, which board? and do you know of anyone who would repair whatever it is that I need repaired?
Cheers

[palindrome]

So far if you performed the trouble shooting correctly then you have.

* Established that the main door switch itself on the chassis is functioning correctly.
* That you are not able to get into the Robot Test mode using the correct steps.

If the main door is closed the switch is tied to active low, otherwise it is active high. If the software is not picking an active low signal with the door closed ( assuming the switch is working ) then I am inclined to agree with proten's post that the hardware is stuffed since the push button A and main door switch/optics communicate through the same PIA device but on different ports.

When we first started writing the Aristocrat 540 driver in MAME we did not have the PIA mapped initially, the game software complained about the main door also, which leads me to believe that the software in your machine is not able to communicate with the hardware.

[rickoshay]

First Issue-screen frozen with "memory board disconnected"
The ***main door open*** freeze wasn't an issue until I checked the ribbon cable on the memory board, as it was showing "memory board disconnected", I stupidly did this with the power on and shorted the memory board onto the hopper handle.
As it thinks the door is open when it is closed I thought it might be the optic switch, do you know of any tests I can perform to isolate what may be the problem?
It may well have been an easy fix before I fucked up, but I did, I can't go back.
Cheers