IGT S+ 65-0 Error

[Clawsino]

i have a machine here, it used to be a sierra silver but the belly glass is broken and i havent been able to find a replacement. therefore i have decided to switch it out with a triple triple diamond theme set i have. basically i swapped the entire door (other door was loosing some of its gold colored plating) then the top glass, the reels and the removable board (i may have just swapped the chips, cant remember :p). now when i power it up i get the 61 error then i hold the test button for a couple seconds and it goes to 61-1, i close the door and turn thereset key and i get 65-0. im reading the code is bad eeprom and i have to replace it? im curious which eeprom i should be replacing. i have a few spare board kicking around i could steal an eeprom out of. im also unable to use my clear chip, it keeps going to 65-0 as well. this i why im guessing it needs to be replaced.

[knagl]

The EEPROM is a tiny square chip that is soldered to the fixed motherboard inside your machine (not the removable MPU board, but the board that the MPU plugs into).

[Clawsino]

ok, is it replaceable? if i was to find the same chip online could i order it and replace my faulty one and it should work?

[Sunrise Side]

At 65-0, open the door and press the reset button, close the door. see if that clears it.

[Sunrise Side]

Here's a note from NLG member poppo


Ok, this was interesting. I was attempting to see if I could do an initial read as soon as the machine is powering up. I waited a few seconds after applying power, pressed my read button and got nothing. And the machine promptly gave me a 65-0 (bad EEPROM) error. I figured I just triggered what I was trying to avoid (both the MPU and me accessing the EEPROM at the same time). I was not able to clear the 65-0 by powering down/up. BTW, there is nothing wrong with the EEPROM and subsequent presses of my button were able to read it just fine. Apparently what happens is if there is a problem reading the EEPROM (which the machine does at power up to compare to the CMOS), a flag gets set somewhere in the CMOS saying it's bad, and you are dead in the water. The machine probably looks for a blank EEPROM before resetting the error flag. So I just pulled the CMOS to get it to lose it's memory (and any set flag). After that, it got me back to the normal 61 (61_1) and all is well again, except I lost my credits as expected. [/size]So apparently a 65_0 does not necessarily mean the EEPROM is bad, only that the MPU failed to read it. I suppose normally that would only happen if it is bad. But once that error flag is set, it stays set until either the EEPROM is replaced or the CMOS is pulled. Of course if the EEPROM really is bad, pulling the CMOS won't help, as the flag will just get set again.




[/color]

[Sunrise Side]

Here's more info. from old site


Good news![/size]After much tinkering and even trading EPROMS and CMOS chips with other machines, the fix was totally different than what I had figured.  In reading the door tag inside my machine, it reports an error 65_1 as BAD EPROM DATA.  The 65_3 error isn't even listed on the door tag.  I read this to mean that something was either wrong with the EPROM or the data burned onto it.  I understood this as something that needed to be fixed.As it turns out, reading the replies above from edski and Brianzz, nothing really needed to be physically fixed or eproms reprogrammed.  The 65_x errors were resettable with the white test button, not with the jackpot key in the way that a 61 is resettable.Once the 65's were cleared, I received a 67 (DATA EPROM CHANGED), which was also cleared.  From this point, the game functioned normally![/color]

[Sunrise Side]

S+ forum info on this site.    http://newlifegames.com/nlg/index.php?topic=3005.0








More info from old site


I had the exact same problem after I replaced the battery in my S+ (was getting a "12" error code, telling me bad battery).  Got stuck in the "61", "61 1", "65" loop.  Used a CLEAR chip and a SET chip and was able to get my problems to go away.  Chips themselves weren't bad, but couldn't get passed the problem without doing the CLEAR/SET thing.[/size][/color]