New Life Games Tech Forums

**Reel Slots** Gaming Machines => IGT S2000 and Vision Games. => Topic started by: mwade109 on February 24, 2012, 02:41:38 PM



Title: Coin In Jam Error
Post by: mwade109 on February 24, 2012, 02:41:38 PM
Greetings.... I have my slots on timers to turn off and on and I am getting a coin in jam error on one of them, s2000, and when I open/close the door the error goes away and don't come back until the next morning,  any ideas?

-mike


Title: Re: Coin In Jam Error
Post by: cowboygames on February 24, 2012, 02:54:48 PM
Without a little more info on the machine I would first look at the voltage on the MPU coin battery. You might post as to what game theme you're running and what MPU version that machine is using.


Title: Re: Coin In Jam Error
Post by: stayouttadabunker on February 24, 2012, 03:26:09 PM
I've noticed a lot of posts on NLG of coin-in jam errors being the result of loose I/O cards -
either on the door panel or the one on the MPU wall (left of the hopper)

With the power turned "OFF" - I'd go about re-seating those I/O cards and connectors.
You don't ever want any power on when checking I/O cards ( or any other boards for that matter)
Power on while installing/removing a circuit board is never good.

Anyways, make sure the I/O cards and connecting Molex connectors
are inserted fully into the back of the receptor housings.
We've had instances where these errors happened as a result of
a machine being moved from one place to another.
Even though you're not moving the machine, opening and closing the doors a million times
could also cause the I/O circuit card/s on the door to wiggle loose as well.
Though I'm pretty sure it has nothing to do with the power being turned off or on.

I've never had a coin-in jam error and I might turn the power off/on about 30 times or more
in one evening as I'm tinkering around with an S2000.

In the Operator and Attendant Menus on page 2.5 I/O Tests (Option: [4]),
you can run some tests to see if there's anything out of whack.
Sometimes it will lead you to a component that's causing problems.

I attached that sheet below here...>>>