# Fault Error C264A0: Task Manager: Critical Error **URL:** \ **Category:** Technical Questions\ **Created:** [October 15, 2024, 1:06pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523 "2024-10-15T13:06:11Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![philip.l](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@philip.l](https://forum.universal-robots.com/u/philip.l)\ **Post date:** [October 15, 2024, 1:06pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/1 "2024-10-15T13:06:11Z")
Hi, We have 8 UR5e bots performing a suction picking application. One of them recently went into a C264A0 fault. The suggestion given to resolve was to upgrade the software. The robot was running 5.12.5 and I incrementally upgraded to 5.12.6, 5.13.0 and then 5.13.1. Each time, the robot would fully power on and then within a minute or 2 revert to the same fault. Any suggestions would be appreciated. ---
**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\ **Post date:** [October 16, 2024, 5:54am UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/2 "2024-10-16T05:54:06Z")
First off, you don’t have to update e-series incrementally. You can go straight to the latest 5.18 (5.13.1 is not the latest). 🙂 I’m afraid the only solution I’ve seen to this issue so far has been to replace Wrist 3. Do you have any other errors in the log history? ---
**Author:** ![philip.l](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@philip.l](https://forum.universal-robots.com/u/philip.l)\ **Post date:** [October 16, 2024, 12:32pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/3 "2024-10-16T12:32:20Z")
Thanks for the info. No other errors. Will investigate purchasing a new wrist 3. ---
**Author:** ![dpeva](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@dpeva](https://forum.universal-robots.com/u/dpeva)\ **Post date:** [October 16, 2024, 1:08pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/4 "2024-10-16T13:08:28Z")
We were getting that error and C264A11 when trying to start the robot. At one point we clicked on the Active Payload option on the Initialize screen, changed the number, and it would finally let us start the arm. I reset the payload using the standard procedure - If I remember correctly, the payload changed from around 1.5 to the current 1.22. We’re thinking that since this robot doesn’t get much use (can go a few weeks between uses), is mounted to the wall and has a fairly heavy OnRobot RG6 gripper (this is a UR5e), that maybe wrist3 develops a “set” or something of that sort. Once we got it moving, we exercised it a bit, and reset the home position a bit. Haven’t used it much since then, so I don’t know whether it will act up again. Total usage on this unit has been pretty low, so it shouldn’t be worn out - though we do use force control (12 N) to place parts into position. ---
**Author:** ![philip.l](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@philip.l](https://forum.universal-robots.com/u/philip.l)\ **Post date:** [October 16, 2024, 1:36pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/5 "2024-10-16T13:36:09Z")
Interesting. I’ll give it a shot. ---
**Author:** ![dpeva](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@dpeva](https://forum.universal-robots.com/u/dpeva)\ **Post date:** [October 16, 2024, 3:04pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/6 "2024-10-16T15:04:43Z")
I should also mention that when UR reviewed my log file, they mentioned that: _ **“We’re also seeing tens of thousands of overlapping blend errors which should be addressed. These are caused by too large of a blend radius with too close of waypoints.”** _ Not sure if this has any bearing on the issue. This unit has to go through some gyrations between picking up and placing parts, so there are several intermediate waypoints, where we had put large blend radii to try to smooth the motion. ---
**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\ **Post date:** [October 17, 2024, 5:30am UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/7 "2024-10-17T05:30:45Z")
You should also consult your local distributor for their advise before buying a new joint. 🙂 Maybe they or UR can see something else or identify some other fault from the error log or something. ---
**Author:** ![philip.l](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@philip.l](https://forum.universal-robots.com/u/philip.l)\ **Post date:** [October 17, 2024, 12:32pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/8 "2024-10-17T12:32:33Z")
Thanks. Have submitted log files and waiting to hear back. ---
**Author:** ![philip.l](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@philip.l](https://forum.universal-robots.com/u/philip.l)\ **Post date:** [October 29, 2024, 5:54pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/9 "2024-10-29T17:54:35Z")
Hi, I was told to try updating to version 5.18.0 in an attempt to resolve my task manager fault. After beginning the update process, the pendant restarted and I attempted to power on the robot, an “Updating Firmware” flag appeared (see pic). Assumed this was normal but after a couple of hours the screen has not changed. Assume its not safe to press the off button or restart the pendant. Checked and it seems to have updated to the correct version though. Any suggestions? ![Updating_Firmware](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/e/ecfe776058e5362f394369a50373efa5fb0ab8f9.jpeg) ---
**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\ **Post date:** [October 30, 2024, 6:11am UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/10 "2024-10-30T06:11:51Z")
That’s not a good sign. I have only seen that happen, when I once updated from \< 5.5 to \> 5.7 a long time ago. I had to send the whole robot to UR so they could update the firmware manually … You should try to revert back to your old software version. You will need the image file corresponding to your old software version. You can find the image here under Robot Image Legacy: [Universal Robots - LEGACY DOWNLOAD CENTER](https://www.universal-robots.com/articles/ur/documentation/legacy-download-center/) There’s also a link to a guide on how to use an image. ---
**Author:** ![philip.l](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@philip.l](https://forum.universal-robots.com/u/philip.l)\ **Post date:** [November 1, 2024, 3:55pm UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/11 "2024-11-01T15:55:23Z")
efn, Thanks again for your help. You were right, it wasn’t good. Universal suspects that the update somehow got corrupted. To save me the trouble of the image file, they are sending me a new SD card with preinstalled software. They also think the task manager fault is likely due to the FT sensor in the tool flange, so they’re sending me one of those as well. ---
**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\ **Post date:** [November 4, 2024, 6:01am UTC](https://forum.universal-robots.com/t/fault-error-c264a0-task-manager-critical-error/36523/12 "2024-11-04T06:01:52Z")
Let’s hope the new SD card will solve the issue with the update. I am slightly afraid that the firmware update has corrupted the firmware in the joints. This can only be solved by UR themselves. And glad to hear they are sending you a new tool flange, too. I hope that solves the main issue on your robot, and wrist 3 is not actually at fault.