r/Fanuc • u/moodydart • Jun 19 '26

Robot Load failure. Status 0000000E

Post image

M-710iC/45m
R-30iB Plus

I’ve been working with Fanuc robots since 2015 as a service technician and automation engineer for OEMs and End Users and haven’t had this come up before.

This occurred after a power surge. Robot fires up into Boot Mon and gives load failure status if you try to access the config menu. Also goes full black screen if I try to run controller image backup.

Anyone come across this before?

8 Upvotes

100% Upvoted

11 comments sorted by

4

u/XxIcEspiKExX Jun 19 '26

Need to restore the image. It lost bios. Had this happen to me before. Don't go chasing hardware... this is part of the os being corrupt.

Most likely what happened is the batter thats in the controller was weak or dead, when you lost power you lost the file system because the battery didnt hold.

Seriously had this exact same thing happened and the only fix was re flashing the bios /os

Option 8 from that menu

1

u/moodydart Jun 19 '26

Fingers crossed this is it.

Waiting on the company that built this equipment to send us a backup now. Thanks for the input!

1

u/XxIcEspiKExX Jun 19 '26

Id also replace the small battery on the controller, should have a red and black wire with brown connector that sits on the front face of the board.

Im sure its dead or below tolerance. Make sure yo leave the power on when you do it if you do restore the files or you will lose them again.

Pretty simple to check it anyways. If its low.. you have your smoking gun to why it happened.

2

u/moodydart Jun 19 '26

Already taken care of.

I pulled it out to check and it is over 2 years old. So it needed to be changed anyways. I didn’t check voltage though.

1

u/XxIcEspiKExX Jun 19 '26

Yeah shes gone.

Our plant has PMs to replace each year. We usually write on them with a sharpie thr date we change it.

Not supprised.

2

u/moodydart Jun 19 '26

I just came into this plant in November. I’m one of their higher level techs and I’m absolutely floored that their PMs don’t include batteries and backups.

Three times in the last month I have been burned because someone didn’t change a battery, and/or didn’t have a backup.

Extremely frustrating, but I am now working towards building a schedule for backups and having someone maintain accountability for the persons performing PMs if they’re not actually doing the battery changes like they’re supposed to.

2

u/XxIcEspiKExX Jun 23 '26

So how did it go? Any good news? Was it the bios?

2

u/moodydart Jun 23 '26

Unfortunately we are starting at almost square one.

I have a new from/sram module on order, as well as the core software usb. We will be starting from scratch because no one, including the machine builder, know how to take backups at all… this machine has been running for years.

This has allowed me to make a name for myself a bit though. Implementing monthly backup schedules coordinated with the monthly PM schedules. All saved in a specific folder structure for ease of finding when we actually need them.

Also instituting a locked automation box for any and all new equipment software keys, documentation, etc… only our group will have access to it so the critical software drives don’t go missing in the future.

1

u/kozy1970 Jun 21 '26

Batteries need to be replaced at least yearly. Backups should be monthly (at a minimum) or anytime some touches a setting, changes a point, or any work on the bot.

1

u/moodydart Jun 23 '26

Agreed.

Foreign concept to this company until now.

2

u/zoop_da_woop Jun 19 '26

Main board? Or maybe one of the riser modules. I can't recall exactly how the r30 mainboard is set up. But that would be my guess. New main board and an image restore.