8500fn1 and 30.01.40

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Samir
    Self-Taught
    • Oct 2023
    • 31

    8500fn1 and 30.01.40

    We have several of these machines and this 'new to us' machine after 9 months of working great seems to not be detecting the scanner even though there is no error message, it detects the scanner covers open properly, and the page detect LED is working correctly. It doesn't seem to be a hardware issue because I was able to get the adf to work once after I rebooted it in a way where it detected the panels open and had an error message on the display, but I can't seem to get it to do it again. In the error log, it's showing the following:
    49 10/9/2024 3:48:39 PM 3718 30.01.40 2308937_578486 General scanner communication failure 0
    48 10/9/2024 3:48:31 PM 0 99.04.20 2308937_578486 Firmware install error 0
    47 10/9/2024 1:30:58 PM 3718 30.01.40 2308937_578486 General scanner communication failure 0
    46 10/9/2024 1:30:50 PM 0 99.04.20 2308937_578486 Firmware install error 0
    45 10/9/2024 11:15:04 AM 3718 30.01.40 2308937_578486 General scanner communication failure 0
    44 10/9/2024 11:14:57 AM 0 99.04.20 2308937_578486 Firmware install error 0
    I'm going to try swapping the power supply with another working machine as either that or the interconnect PCA seems like it might be an issue. Other solution will be to swap this ADF to another unit where the ADF stopped working properly (garbage output from the ADF side) as that one's Interconnect seems to be working. Swapping the ADF seems to be less work than swapping the Interconnect.

    Just wanted to see if anyone else has dealt with these machines and if it sounds like I'm on the right track. Also would be curious what could cause something like this. Literally have two machines side by side plugged into the same outlet, and this one starting having this problem and the other one is still working fine.
  • Samir
    Self-Taught
    • Oct 2023
    • 31

    #2
    Just tried the power supply swap and same results--adf doesn't do normal self-test 'exercise' when powering up, but shows up as connected once the scanner is fully booted. No error messages in log for 30.01.40 or 99.04.20, but when trying to scan, it simply says 'scanning' and the adf isn't doing anything and then times-out. Sounds like the interconnect or the adf assembly went bad.

    Comment

    • Samir
      Self-Taught
      • Oct 2023
      • 31

      #3
      So this was weird. Plugged in the power supply and turn on the machine and the ADF was just feeding at full speed. I waited to let the machine boot up and it was still this way. Shut the machine down and it stopped. Powered it back up and it did the same as my initial problem. Shut it down again and pulled the power from the back of the machine and let it sit for about 10 minutes. Plugged it back in and powered it up and everything behaved normally and I was able to scan something via the adf. I'm rebooting the machine to see if this was a fluke, but so far the adf is 'exercising' the way it should upon boot. We'll see what happens when I try to use the flatbed as that's how this all started in the first place...
      Last edited by Samir; 10-13-2024, 05:47 PM.

      Comment

      • Samir
        Self-Taught
        • Oct 2023
        • 31

        #4
        Well, I'm not sure exactly what was wrong and what fixed it, but it's working 100% normally again.

        Comment

        Working...