All Activity
- Past hour
-
Can’t see what error you have, but it’s known for the hopper driver boards to burn out. just like with solenoids, and battery leaks the payout constantly fires/spins. I would say concentrate on switch issue first as may be related to that, and needs to be fixed regardless
- Today
-
Just the one hopper Jim
-
Quick question, what make/ model are the hoppers / hopper?
-
Thanks for the input Jim, well it's good to get an understanding of how it works, let's hope it's not an issue on the card! Hope Bob can advise on the chip readings I posted earlier.
-
I think you are right on both counts. I have just had a look on one of mine and although it has not got a hopper it has got the extended game card and that square chip near the aux 3 connector on the game card is a 68681 DUART which makes sense, so power from pl10 and information from aux3 on the game card. So that is a dead end as none of the tracks that directly go to the hopper are anywhere near the battery area. As Bob says a screwed up switch matrix can make them do funny things and something else i would look at which realy can do strange things is the RAM, although it looks quite clean in the photo it is in the battery area.
-
Ok so had a look at what I thought was a hopper driver board but thinking it’s some kind of power board? It looks like the hopper might be driven by the game card? Or the blue pl10 connector it’s hard to tell! the white triac connctor is fully populated so must be doing another job! thanks Ronnie
-
Never had anything to do with one with a hopper on it (bit modern for me lol) but i would think it is still related to the battery damage. Which port on the mpu does the hopper plug into, maybe have a look at the tracks to that socket and see where they go in relation to the damaged area. Jim
-
Thanks for this jimxxx, that makes sense, and maybe confirms a switch matrix issue in that the hopper is getting switched on. Or could it be the hopper driver board, it looks to be over engineered to me. Thanks Ronnie
-
After typing the above i did a quick search and found this on github/mame, seems to point in that direction although F knows what it means apart from it appears to be hopper related.
-
As a complete guess (but logical) and i may be completely wrong but heres my two peneth worth. Since you have mentioned that about the hopper is the alarm maybe Unexpected Pay Out.🤔
-
ee88lep joined the community
-
JuigREele joined the community
-
SyuyREele joined the community
- Yesterday
-
ALerjREele joined the community
-
Might be a smoking gun? As machine boots up and just before the error comes up I can hear the hopper motor pulse for just a second and that triggers the error message, I see a hopper driver board under the mpu if I unplug the hopper I get error 4.0 hopper jam the error with it plugged in id 4.0 unexpected PO thanks Ronnie
-
So IC22 pin 3 is pulse pin 6 is high pin 8 is low and pin 11 is pulse checked IC33 pins 16 and 13 are floating, only other pin pulsing is pin 2, the rest are either high or low Thanks Ronnie
- Last week
-
Claudianef joined the community
-
Thanks bob will double check those pins but everything else was pulsing other than 4 5 and 6
-
You should see pulsing outputs on pins 7-15. The ones we're interested in go to IC22 so make sure the outputs on 3,6,8 and 11 are good. Depending on what switches are operated you should then see good outputs on IC33 & 34. These two are in the firing line for the battery vapours and can do funny things. I think I've mentioned this already.
-
I’m on holiday at the moment, so not with a machine.. BUT hopefully this helps. with the route plug in place, it’s either top two left side, or top left, and bottom left. 90% sure it’s the former, you can link these without a plug if you wish, but a plug would be cleaner unless you have some link tabs there
-
Just got round to checking IC23, not sure what I should be seeing? The enables 4 and 5 are low 6 is hi, inputs and outputs are all pulsing? Thanks Ronnie
-
SiiyREele joined the community
-
Power, Power, Power. We have all done it and will no doubt continue to do so, start off and get side tracked, cant see the the wood for the trees scenario. Well done Bob, another interesting read. Didnt realise Caroline was still going, just had a look on their home page and the solar power meter for the Orford Transmitter made me chuckle.
-
Yet another board nearly drove me to insanity. Maybe I'm lossing my touch with age, who knows. Usual battery rot symptoms so all the usual suspects whipped out and renewed. A bit of track patching out needed for the alpha and triac driver links but other than that pretty clean. So on power up (with diags) the triacs all test OK then the tester alpha comes up with MPU4 ALPHATEST OK so all looking good. Thinking I'm in for an early day and just waiting for the lamp tests to start it comes up with an alarm and a bit of garbage on the alpha although I can see it's trying to say 'alarm' but no idea what. The RAM solder joints were looking a bit crusty so I thought that better come out, just in case, which was good as it failed on my tester. I've had similar issues before, like the previous fault above, so it's always a good idea to check out IC16 and put it in a socket which then gives you the option to isolate the CS feeds to all the support chips. Isolating IC5 the alarm was still apparent but the alpha then stopped on a readable 6840 error. Of course changing the chip made no difference. Just a little teaser here, I'd checked the 5v previously and it was a bit low at 4.77v but we all know TTL min rating is 4.5v and it boots OK so I thought I'd come back to that later. Big mistake!! Anyway back at the ranch getting nowhere and contemplating taking out all the support chips and putting in sockets which I did. After each replacement no change to the fault so 2 days later I'm losing the will to live. By now I've made sure all the Address and Data lines are intact plus every other line from the cart to the board. I'm thinking there must be a corroded via somewhere that I've missed. Rapidly running out of ideas and it's now day 3. There's only two options left, the first one is to jump in the Thames but maybe option two first. Thought I'd go back to the low voltage supply and see what's going on there. After stripping down the regulator I thought I'd run a test on the LM323 with my bench PSU and lo and behold it stuck solidly at 5v?? Hmm, what am I missing here? Tried a spare regulator chassis and blow me the board booted and ran fine. After all that wasted work but hey ho it works so put away the swimming trunks. So what was going on with the original regulator? Putting it back with the little board again it's measuring 5v off load but if I put a 12R resistor across the output it drops to 4.77v. It was then I noticed something on the radio. I listen to Caroline on 648Khz and putting the resistor on the output more or less blocked out the radio signal! Suspicion then pointed towards the tant cap that decouples the input to the LM323. When a new one was fitted the voltage remained stable under load at 5v. As the wires to the board power socket weren't attached they probably acted like an aerial otherwise I would have noticed this before. I'm sure someone up there doesn't like me.
-
JiogREele joined the community
-
Ok so it’s pins 2 and 4 for 10p enable, so all Issues now sorted apart from one! The 50p is going to 10p tube even though I have it jumped to go left, tried changing sorter but no joy thanks everyone for your input
-
hi there can anyone help me out am needing the flash file for tornado reflex gaming scorp 6 100 jackpot non data many thanks pete
-
Thanks for that, would that 13 and 14 as it uses a 14 way plug but the mech has 18 pins
-
Two pins on route plug for mars mech need to be linked to accept 10ps (two end ones)
-
Ok having spoke to Tim apparently it needs a routing plug pinned to enable 10p! Watch this space
-
Thanks for that, could point me to the issue on big shot I will have a good look
-
Hi, i assume you mean you are getting the error screen, if so at the bottom of any page where it says theme, click on it and change it to new(default).
