Jump to content

Leaderboard

    [[Template core/front/popular/memberRow is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] [[Template core/front/popular/memberRow is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] [[Template core/front/popular/memberRow is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Popular Content

Showing content with the highest reputation on 06/29/24 in all areas

  1. There is another video on Youtube of a guy who bought a faulty one from a friend. He also posts pictures of the manual towards the end of the video.
    1 point
  2. Thanks so much for your help with this. This has given me renewed hope. I couldn't find the ROM online anywhere, so if mine is good, we now have it for preservation and it means I can look else where for the fault. The fact that mine is completely dead, apart from the reel sensor LEDS and the MPU4 LED seems to point to the same issue Andrew had. As you said John, it's not progressing with the initialisation because some part of the machine (switch or sensor) isn't returning the right condition for the boot sequence. I need to go through the wiring and all the switches to see if there are any issues. Also this machine doesn't have the standard MPU4 reel backboard, so I'll have a look at the reel sensors as well. I just need to keep at it. Paul
    1 point
  3. It's not dead, it's firing reel #3, and 4 of the 7 segment display blocks (firing all 7 segs plus dot lit). I see 2x 7seg display blocks on the youtube video, perhaps there's 2 more inside the machine or something. It is starting the code, and boot looping (very quickly). The reel 3 'jiggle' leads me to suspect this machine uses a custom reel controller MCU that is not implemented in MFME, and so the program is resetting repeatedly as it's not getting the signal back it's expecting from the reel after the 'jiggle' so it's tripping the code. That's not guaranteed, but as a quick look I suspect that is what's going on! Oh this machine doesn't use a Chr chip, at least it's not reading/writing that address range during the small amount of code it does run before the reset.
    1 point
×
×
  • Create New...