This has been a recurring issue for several months now, and i would like to see if anyone else has had this issue.
When it began, it occurred on one robot. It would be operating normally, and then typically at the start or end of a weld, we would receive a SYST-302 (Please Power Off) and a OS-147 (Assert MAIN %d %d %s) Alarm, requiring us to cycle power. Then the robot would be fine for a while. At first, it would go 4 to 6 weeks between occurrences, then it slowly increased in frequency until it was occurring daily.
All of the help i have been able to find regarding this fault say to contact Fanuc, which we did, but the variable place holders have never been filled in with the two numbers and the string that they should display in place of %d %d %s. Fanuc suggested it may be a memory card issue. We took an image backup, reloaded it, and it went away. For a while. After a couple of months, it started occurring again. This time, Fanuc suggested that since we were on version 8.30p/11, we should do an AutoUpdate to 8.30p/36 (latest at that time).
I took an image, and an AOA backup, reloaded the image to verify it had worked, then attempted the AutoUpdate. The AutoUpdate went through the first sections fine, taking its own backups of the different drives, but after the first power cycle, it update the BOOT monitor version, and stopped. The AutoUpdate screen displayed a failure message, but otherwise no indicator was given that anything had gone wrong.
We have sent the AOA and Image backups, as well as the backups taken by the AutoUpdate to Fanuc, but we have not heard back yet.
1. Has anyone else had an issue with Assert MAIN, specifically with it not filling in the placeholder variables for debugging?
2. Has anyone performed an AutoUpdate across such a large version gap, and was there any indicator after the first power cycle that the update was still ongoing?
Robot in question is an R-30iB A Cabinet, with an ArcMate 120iC 12L robot, and it is from Fanuc Europe.