Fail to cold start

(Irb 6400): S/N= 64-13958

3.1 OS

I have got a problem with this bot. I was on vacation last week so I’m just coming into this mess.

They was in the process of a setup, Weld mods, and reg counts, then had a system fail. I told them to restart

Then they got the disk changed / reread-cancel window after the start up. They did a reread and the was no TCP data.

I told them that we will have to do a cold start on it. They tried and had problems, for some reason the disk 1 was gone from the flash drive. I loaded the dick 1 back on the flash drive , did a cold start, loaded the key disk, then loaded disk 1 then got this error. (error. 03:07003 unexpected interrupt on MC: ) Now every time it boots up is goes to this point and gives me the same error.

I have changed the main computer and memory boards .

I have been in touch with ABB Tech and recommend to try a robot computer board.

We are kinda at a stand still on this. I'm going to check the pin on all the boards and back plain next and try again. We will have to order a robot computer board so I will have to wait for it to come in. 


  • graemepaulin
    graemepaulin New Zealand ✭✭✭
    Have checked the internal support case database for this error:
    -disconnect batteries for at least 10 minutes to ensure the memory is empty ->though you have changed memory board so it should have been empty.
    -Memory board failure -> you have changed already, is it a know good spare?
    -Must have correct hardware for the version of RW/OS -> as it was running should not be an issue, but any changed boards must be of the same type.
    -If some one by mistake used a RW/OS 3.2 boot disk then the robot computer board must be replaced.
  • graemepaulin  If the memory or main computer board had a different OS could it cause this problem? The part # was the same as the old boards, also the boards was used, and as far as I know they was working.
  • graemepaulin
    graemepaulin New Zealand ✭✭✭
    According to one of the cases if the main computer has ever had OS 3.2 loaded it will cause an issue with the Robot Computer.
    But for the memory board the case only said to leave the batteries disconnected for at least 10 minutes which will erase all the contents as it is volatile memory (like RAM in your PC).
  • Ok thanks. We do have another bot that has 3.2 OS I Wasn't here when they first tried to load the key disk.  
  • graemepaulin
    graemepaulin New Zealand ✭✭✭
    Depending on the hardware in this system you may be able to upgrade to OS 3.2 - would that be all your controllers on OS 3.2 or would there still be a mixture?

    I will see if I can find the document that details the different combinations that work together.
  • we have also have one that runs on 3.0 OS. and we also have a 1400 with a 3.0 OS.
    we are going to have to update soon because parts are becoming hard to find. So hopefully it will be in the next year or two.  
  • Up date on the board, it should be here 3/17/21
  • We got the board today and I have installed it. It started up like it should, I did find out that the flash drive I was using was bad, when I went to load disk 1, it went to the start up screen with the counter. I got a flash drive that i new was good and every thing went fine.
    Thanks for the help.
  • Also I did reinstall the original memory and main computer boards
  • graemepaulin
    graemepaulin New Zealand ✭✭✭
    Thanks for the update, and good to hear it is all up and running now.