how to fix wait................ in iRb/w series

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • teckat
    replied
    KOOL~~~~~~~~~~~~~~~~~~~:}

    Leave a comment:


  • davidj7
    replied
    guys thanks for all the inputs i am keeping a boot rom and a few ram modules . Hope that will solve my issues in future

    Leave a comment:


  • teckat
    replied
    Originally posted by stopbanks
    I also want to get the solutions, hope you will explore more your ideas...

    Hello Jerk ! u have been REPORTED / post your spam links elsewhere

    angry_man.jpg

    Leave a comment:


  • SCREWTAPE
    replied
    Originally posted by stopbanks
    I also want to get the solutions, hope you will explore more your ideas...
    SPAM

    Leave a comment:


  • SCREWTAPE
    replied
    Originally posted by waffu22
    How about the R-CON board? Have you tried to replaced?
    Of cousre he can try. I wouldn't focus on it. If there was a E733 then yea I would try replacing RCON.

    Leave a comment:


  • waffu22
    replied
    How about the R-CON board? Have you tried to replaced?

    Leave a comment:


  • stopbanks
    Guest replied
    Re:

    I also want to get the solutions, hope you will explore more your ideas...

    Leave a comment:


  • madu132
    replied
    just share my experience...

    several weeks ago I have problem "wait..." with ir7200...

    it was on sequence 2...
    after I change ethernet card, it was OK...

    I was also having problem on sequence 3... I found that scanner connection not connect properly....

    Leave a comment:


  • SCREWTAPE
    replied
    Any accessories attached, finisher.
    Check the reader cables.
    Where any e-code noted in the past 3 months?

    So it stops at the 2nd & 3rd interval which checks the configuration of the printer/reader.

    You have past the 1st interval which runs a self diagnostic program. The program checks image memory(ram) and the HDD. Once that's done the software is loaded to the memory, in this case it seems like memory or the HDD is not the problem. BUT, you never know.

    For the hell of it try the defrag 1&9.

    Leave a comment:


  • teckat
    replied
    [QUOTE=davidj7;176423]
    Originally posted by teckat
    Have u reseated the DIMMS and the Boot on the Main controller[/QUO

    yes i have .

    Just because u tried this HDD in another printer, does not mean the partitions are in agreement /

    I would format HDD- RE LOAD FIRMWARE

    Leave a comment:


  • davidj7
    replied
    [QUOTE=teckat;176387]Have u reseated the DIMMS and the Boot on the Main controller[/QUO

    yes i have .

    Leave a comment:


  • tinnyjay
    replied
    Originally posted by SCREWTAPE
    <Control Program Area>

    - Control Program 1 (interval 2)
    1) The machine checks and initializes the various hardware on the main controller PCB.
    2) If the previous shut-down sequence was not performed normally, the machine recovers the system files
    as needed. (In this case, the start-up time tends to be longer than usual.)
    3) The machine initializes the various program modules.

    - Control Program 2 (interval 3)
    1) The machine initializes the various software modules, and checks the configuration of the printer/
    reader.
    2) If the printer/reader is found to be normal, the machine ends the start-up sequence; otherwise, it will
    indicate E732/E733.

    Where does it stop?
    I think you must check fuser,dimms,power supply(Standard Rules).
    Check one by one these parts and find which is wrong.You cannot repair the copier without changing parts at least just for test.

    Leave a comment:


  • teckat
    replied
    Originally posted by davidj7
    screwtape : the progress bar reaches the end and then stops. like in the figure at the end of section 3.

    Have u reseated the DIMMS and the Boot on the Main controller

    Leave a comment:


  • davidj7
    replied
    screwtape : the progress bar reaches the end and then stops. like in the figure at the end of section 3.

    Leave a comment:


  • davidj7
    replied
    Originally posted by D_L_P
    In my experience if reseating the boot ROM doesn't fix it try replacing the RAM. That is the next most common cause, then I move on the $$$ main control PCB. I think in over 10 years I've replaced less than 5 main controllers and maybe about 10 RAM sticks.
    We ran into this mostly when we tried using non-OEM RAM to save a few $$$.
    thanks DLP i will buy and keep a few boot rom and couple of RAM's

    Leave a comment:

Working...