C264 Task Manager

You may find the following links helpful in addressing this issue:

If you unable to resolve the issue, log in to http://myUR.universal-robots.com and create a new case.

C264A0 Critical error

A critical error occurred in the task manager

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance

C264A7 Start of Cycle pulse was required but did not occur after {unsigned}ms.

A Start of Cycle pulse did not happen within the required time. The issue may be due to a damaged internal communication cable to the node or a bad internal connection.

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance

C264A8 Systick timer and Start of Cycle pulse was misaligned by {float}us.

The internal systick timer and the Start of Cycle pulse was not aligned as expected. The issue may be due to a damaged internal communication cable to the node or a bad internal connection.

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance

C264A9 {signed} unexpected (+) or missing (-) Start of Cycle pulses was detected within a 1 second period.

The number of Start of Cycle pulses within a 1 second period was different than expected. The issue may be due to a damaged internal communication cable to the node or a bad internal connection.

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance

C264A10 {unsigned} invalid Start of Cycle pulses was detected within a 1 second period.

Too many misaligned Start of Cycle pulses was detected within a 1 second period. The issue may be due to a damaged internal communication cable to the node or a bad internal connection.

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance

C264A11 {unsigned} Start of Cycle pulses was lost in a row

Too many Start of Cycle pulses was lost in a row. The issue may be due to a damaged internal communication cable to the node or a bad internal connection.

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance