Difference between revisions of "Error Codes/zh-hans"
Line 802: | Line 802: | ||
== Interpreter (8000 through 8999, 22000 through 22999) == | == Interpreter (8000 through 8999, 22000 through 22999) == | ||
{{MC-Basic/ErrorCodeHeader| | {{MC-Basic/ErrorCodeHeader| | ||
− | {{MC-Basic/ErrorCode|8001|Division by zero| | + | {{MC-Basic/ErrorCode|8001|Division by zero|被零除|SYNC|错误|Idle Task}} |
− | {{MC-Basic/ErrorCode|8002|Internal error. Contact technical support.| | + | {{MC-Basic/ErrorCode|8002|Internal error. Contact technical support.|解释器堆栈下溢。可能的原因是内存损坏或解释器生成无效的代码。|SYNC|故障|解释器被阻止执行。}} |
− | {{MC-Basic/ErrorCode|8003|Stack overflow.| | + | {{MC-Basic/ErrorCode|8003|Stack overflow.|内存耗尽。|SYNC|故障|解释器被阻止执行。}} |
− | {{MC-Basic/ErrorCode|8004|Internal error. Contact technical support.| | + | {{MC-Basic/ErrorCode|8004|Internal error. Contact technical support.|解释器堆栈下溢。 可能的原因是内存损坏或解释器生成无效的代码。|SYNC|故障|解释器被阻止执行。}} |
− | {{MC-Basic/ErrorCode|8005|Functions stack overflow.| | + | {{MC-Basic/ErrorCode|8005|Functions stack overflow.|内存耗尽。|SYNC|故障|解释器被阻止执行。}} |
− | {{MC-Basic/ErrorCode|8006|Index underflow.| | + | {{MC-Basic/ErrorCode|8006|Index underflow.|无效的数组索引值。|SYNC|故障|}} |
− | {{MC-Basic/ErrorCode|8007|Index overflow.| | + | {{MC-Basic/ErrorCode|8007|Index overflow.|无效的数组索引值。|SYNC|故障|}} |
− | {{MC-Basic/ErrorCode|8008|Task not found.| | + | {{MC-Basic/ErrorCode|8008|Task not found.|任务操作失败。请求的任务不存在。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8009|Invalid breakpoint location.| | + | {{MC-Basic/ErrorCode|8009|Invalid breakpoint location.|将断点设置在无效的位置。例如: 在注释行或已存在的断点|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8010|Out of memory.| | + | {{MC-Basic/ErrorCode|8010|Out of memory.|内存耗尽。添加更多内存或卸载不必要的任务。|SYNC|故障|}} |
− | {{MC-Basic/ErrorCode|8011|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8011|Internal error. Contact technical support|在解释器函数的外部运行时错误。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8012|The task has not terminated.| | + | {{MC-Basic/ErrorCode|8012|The task has not terminated.|任务执行尚未终止。如果任务被锁定在某个最终功能中,如MOVE或STOP,则可能发生这种情况。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8013|The task is not stopped.| | + | {{MC-Basic/ErrorCode|8013|The task is not stopped.|任务不会停止(空闲)。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8014|The task is terminated.| | + | {{MC-Basic/ErrorCode|8014|The task is terminated.|任务被终止(结束)。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8015|Argument for EXP is out of range| | + | {{MC-Basic/ErrorCode|8015|Argument for EXP is out of range|EXP参数的取值范围是±7.09782712893383e + 02。 小于下限的值可以使用,但会返回0。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8016|llegal mathematical function call| | + | {{MC-Basic/ErrorCode|8016|llegal mathematical function call|数学函数的参数无效。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8017|Argument for LOG is out of range| | + | {{MC-Basic/ErrorCode|8017|Argument for LOG is out of range|LOG函数的参数必须大于零。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8018|Negative parameter in SQRT operator| | + | {{MC-Basic/ErrorCode|8018|Negative parameter in SQRT operator|SQRT函数的参数必须大于或等于零。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8019|Internal error. Contact technical support.| | + | {{MC-Basic/ErrorCode|8019|Internal error. Contact technical support.|Loader传递无效的上下文定义。|SYNC|致命错误|}} |
− | {{MC-Basic/ErrorCode|8020|Varible does not exist.| | + | {{MC-Basic/ErrorCode|8020|Varible does not exist.|监控的变量不存在。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8021|Incorrect number of dimensions.| | + | {{MC-Basic/ErrorCode|8021|Incorrect number of dimensions.|监控的维数错误。|SYNC|故障|}} |
− | {{MC-Basic/ErrorCode|8022|Task is not running.| | + | {{MC-Basic/ErrorCode|8022|Task is not running.|任务已停止(空闲)。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8023|Internal error. Contact technical support.| | + | {{MC-Basic/ErrorCode|8023|Internal error. Contact technical support.|元素不能从符号表中删除。|SYNC|故障|}} |
− | {{MC-Basic/ErrorCode|8024|Task must be killed first.| | + | {{MC-Basic/ErrorCode|8024|Task must be killed first.|任务仍在运行。 它可能被锁定在一些最终功能,如MOVE。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8025|Invalid task state for the `StartTask` command. Kill task first.| | + | {{MC-Basic/ErrorCode|8025|Invalid task state for the `StartTask` command. Kill task first.|任务不会被终止(结束)。它可能被锁定在一些最终功能,如MOVE。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8026|Bad memory address.| | + | {{MC-Basic/ErrorCode|8026|Bad memory address.|试图访问无效的内存地址。 错误可能是由于应用程序中的错误或内存损坏。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8027|Bad I/O address.| | + | {{MC-Basic/ErrorCode|8027|Bad I/O address.|试图访问无效的I / O地址。 错误可能是由于应用程序中的错误或内存损坏。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8028|Calculation overflow| | + | {{MC-Basic/ErrorCode|8028|Calculation overflow|计算溢出|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8029|Underflow| | + | {{MC-Basic/ErrorCode|8029|Underflow|计算下溢。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8030|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8030|Internal error. Contact technical support|无效的互斥ID。 该错误可能是由于内存损坏。|SYNC|致命错误|}} |
− | {{MC-Basic/ErrorCode|8031|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8031|Internal error. Contact technical support|无效的互斥ID。 该错误可能是由于内存损坏。|SYNC|Fatal Fault|}} |
− | {{MC-Basic/ErrorCode|8032|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8032|Internal error. Contact technical support|创建信号量时出错。 内存耗尽时发生错误。|SYNC|Fatal Fault|}} |
− | {{MC-Basic/ErrorCode|8033|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8033|Internal error. Contact technical support|代码段具有无效的校验和。原因是内存损坏。|SYNC|Fatal Fault|}} |
− | {{MC-Basic/ErrorCode|8034|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8034|Internal error. Contact technical support|无效令牌COP; 通常是由于内存损坏。|SYNC|Fatal Fault|}} |
− | {{MC-Basic/ErrorCode|8035|Task is interrupted by OnEvent or OnError| | + | {{MC-Basic/ErrorCode|8035|Task is interrupted by OnEvent or OnError|由于任务的中断状态,诸如STEP或STEPOVER等的任务调试命令被禁用。如果被ONERROR或者ONEVENT中断,任务将切换到这个状态。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8036|Entry Station output buffer overflow|Entry | + | {{MC-Basic/ErrorCode|8036|Entry Station output buffer overflow|Entry Station输出缓冲区溢出。错误是由不可操作的主机或用户任务发送太多的消息引起的。|SYNC|Note|}} |
− | {{MC-Basic/ErrorCode|8037|Error loading object file (see file oload.err for more details).| | + | {{MC-Basic/ErrorCode|8037|Error loading object file (see file oload.err for more details).|目标文件无效或包含未解析的符号|SYNC|Note|}} |
− | {{MC-Basic/ErrorCode|8038|The value is out of range| | + | {{MC-Basic/ErrorCode|8038|The value is out of range|传递给函数的值超出范围|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8039|Invalid file name| | + | {{MC-Basic/ErrorCode|8039|Invalid file name|无效的文件名|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8040|Invalid time or date| | + | {{MC-Basic/ErrorCode|8040|Invalid time or date|输入的时间或日期无效。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8041|Nothing to retry.| | + | {{MC-Basic/ErrorCode|8041|Nothing to retry.|运行时错误后,重试命令是适用的。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8042|Task is busy.| | + | {{MC-Basic/ErrorCode|8042|Task is busy.|任务繁忙;不允许调试。当任务在结束函数中时,会发生这种情况。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8043|Element could not be deleted while programs are in memory.| | + | {{MC-Basic/ErrorCode|8043|Element could not be deleted while programs are in memory.|程序在内存中时无法删除元素。|SYNC|故障|}} |
− | {{MC-Basic/ErrorCode|8045|Cannot stop unbreakable task.| | + | {{MC-Basic/ErrorCode|8045|Cannot stop unbreakable task.|无法停止或调试不可破解的任务|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8046|"User authorization code is not recognized. Contact technical support| | + | {{MC-Basic/ErrorCode|8046|"User authorization code is not recognized. Contact technical support|联系技术支持来验证您的卡的序列号和授权码|SYNC|错误|没有可用的轴}} |
− | {{MC-Basic/ErrorCode|8047|Invalid Authorization code! Contact technical support| | + | {{MC-Basic/ErrorCode|8047|Invalid Authorization code! Contact technical support|联系技术支持来验证您的授权码。|SYNC|错误|没有可用的轴}} |
− | {{MC-Basic/ErrorCode|8049|Invalid type of variable| | + | {{MC-Basic/ErrorCode|8049|Invalid type of variable|错误的变量类型|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8050|Argument for trigonometric function is out of range| | + | {{MC-Basic/ErrorCode|8050|Argument for trigonometric function is out of range|sin(x)或cos(x)的参数的最大值是9.223372036854699e + 18|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8051|The result of mathematical function overflows| | + | {{MC-Basic/ErrorCode|8051|The result of mathematical function overflows|结果大小大于Double类型的最大值。|SYNC|错误|}} |
− | {{MC-Basic/ErrorCode|8052|Internal error. Contact technical support| | + | {{MC-Basic/ErrorCode|8052|Internal error. Contact technical support|元素不能被添加到符号表中。 内部错误|SYNC|故障|}} |
{{MC-Basic/ErrorCode|8053|No permission: stop the motion first|Motion should be stopped before RESET.|SYNC|Fault|}} | {{MC-Basic/ErrorCode|8053|No permission: stop the motion first|Motion should be stopped before RESET.|SYNC|Fault|}} | ||
{{MC-Basic/ErrorCode|8054|Unrecognized Serial Number. Contact technical support|Contact technical support to validate both Serial Number of your card and Authorisation code|SYNC|Error|No axes available}} | {{MC-Basic/ErrorCode|8054|Unrecognized Serial Number. Contact technical support|Contact technical support to validate both Serial Number of your card and Authorisation code|SYNC|Error|No axes available}} |
Revision as of 03:38, 14 November 2017
语言: | [[::Error Codes|English]] • [[::Error Codes/zh-hans|中文(简体)]] |
---|
Contents
- 1 简介
- 2 错误处理程序 (1 through 999)
- 3 Built In Test (1000 through 1999)
- 4 Run Time Scheduler (2000 through 2999)
- 5 File System (4000 through 4999)
- 6 Entry Station (5000 through 5999)
- 7 Loader (6000 through 6999)
- 8 Translator (7000 through 7999)
- 9 Interpreter (8000 through 8999, 22000 through 22999)
- 10 Recorder (9000 through 9999)
- 11 Event Handler (10000 through 10999)
- 12 Backend Processor (11000 through 11999)
- 13 SERCOS (12000 through 12999)
- 14 ROBOT (13000 through 13999)
- 15 Root Process (16000 through 16999)
- 16 Motion bus (19000 through 19009)
- 17 User Error codes (20000 through 20999)
- 18 I/O Module (21000 through 21999)
简介
softMC通常通过串口向主机传送错误代码。 一些错误代码也会传输到状态显示器。 EEPROM中的错误历史记录(FLTHIST,ERR)中保存了相同的信息,因此断电时不会丢失任何信息。 不是所有的错误都反映了一个消息回到主机。 在这种情况下,没有消息的错误只传达到状态显示。
错误处理程序 (1 through 999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
1 | CPU Divide error | 如果除数为零或商数溢出结果寄存器,则由CPU产生。 | ASYNC | 致命错误 | Watchdog |
2 | CPU Debug | 如果设置了Trap标记,则在每条指令之后由CPU产生。 | ASYNC | 致命错误 | Watchdog |
3 | CPU NMI | 当输入到NMI引脚时,由CPU产生 | ASYNC | 致命错误 | Watchdog |
4 | CPU Breakpoint | 由一个字节的断点指令生成。 | ASYNC | 致命错误 | Watchdog |
5 | CPU Detected Overflow | 如果设置了溢出标志, 则由 CPU 生成。 | ASYNC | 致命错误 | Watchdog |
6 | CPU Bound range exceed | 当要测试的值小于指定的下限或大于指定的上限时,由BOUND指令生成。 | ASYNC | 致命错误 | Watchdog |
7 | Invalid opcode | 当CPU尝试执行无效操作时生成。 | ASYNC | 致命错误 | Watchdog |
8 | CPU extension not available | 如果遇到协处理器指令,并且未安装协处理器,则生成该错误。 | ASYNC | 致命错误 | Watchdog |
9 | CPU: double exception detected | 在一个CPU指令或异常处理程序中发生多个异常时生成。 | ASYNC | 致命错误 | Watchdog |
10 | CPU Coprocessor overrun | 如果协处理器试图访问片段边界之外的内存,则生成错误。 | ASYNC | 致命错误 | Watchdog |
11 | CPU Invalid Task State Segment | 如果任务门指定的新TSS无效,则在任务切换期间由CPU自动生成。 | ASYNC | 致命错误 | Watchdog |
12 | CPU segment not present | 如果段描述符指示段当前不在内存中,则在加载CPU的段寄存器时生成。 | ASYNC | 致命错误 | Watchdog |
13 | CPU Stack fault | 在堆栈溢出,下溢或层间转换或任务切换引用标记为"不存在"的堆栈段时生成。 | ASYNC | 致命错误 | Watchdog |
14 | CPU General protection fault | 当CPU检测到不适用于具有单独中断的另一类别的保护违规时生成。在80486保护模式浮点保护错误上产生此错误。 | ASYNC | 致命错误 | Watchdog |
15 | CPU Page fault | 在尝试访问一个 4 K 内存页, 该页面的页表项已清除 "当前" 位时生成该错误。 | ASYNC | 致命错误 | Watchdog |
16 | CPU Coprocessor fault | 如果处理器试图访问段边界外的内存, 则生成该错误。它可能在协处理器指令发出后的任意时间发生。 | ASYNC | 致命错误 | Watchdog |
17 | CPU Alignment error | 如果内存未对齐,则由CPU自动生成错误。 | ASYNC | 致命错误 | Watchdog |
18 | Invalid FPU operation | 程序错误(例如,三角函数的超范围参数,负操作数的SQRT,零或负操作数的对数)。 | ASYNC | 错误 | Idle Task |
19 | FPU: Unnormalized operand | 当一条指令试图对一个未规范化的操作数进行操作时产生。 由于丢失了低位,结果可能会显着性降低。 | ASYNC | 错误 | Idle task |
20 | FPU divide by zero | 当指令尝试除以零时生成该错误。 | ASYNC | 错误 | Idle Task |
21 | FPU overflow | 如果四舍五入结果的大小超过目标格式中最大有限数的大小,则发生该错误。 | ASYNC | 错误 | Idle Task |
22 | FPU Underflow | 两个相关的事件可能导致这个错误: 1) 创建一个非常小的操作数,以后可能会导致一些其他异常,2) 在除法时溢出产生不精确的结果。 | ASYNC | 错误 | Idle Task |
23 | FPU Precision lost | 在操作结果不能完全以目标格式表示时发生。 例如,1/3不能以二进制形式精确表示。 这种异常频繁发生,表明有一些(通常可接受的)异常已经丢失。 大多数应用程序掩盖此异常 | ASYNC | 错误 | Idle task |
24 | FPU Stack fault | 由于堆栈溢出或下溢,在FPU上生成错误。 | ASYNC | 错误 | Idle Task |
25 | Invalid FPU operation | 程序错误(例如,三角函数的超范围参数,负操作数的SQRT,零或负操作数的对数)。 系统上下文 | ASYNC | 致命错误 | Watchdog |
26 | FPU: Unnormalized operand | 当一个指令试图操作一个非标准化的操作数时,由于丢失了低位,结果可能会显着性降低。 大多数应用程序都会屏蔽这个异常,因为非标准化的操作数在加载到FPU时将被标准化为扩展实数格式。 系统上下文 | ASYNC | 致命错误 | Watchdog |
27 | FPU Zero divide | 当指令试图将有限的非零操作数除以零时生成。 系统上下文。 | ASYNC | 致命错误 | Watchdog |
28 | FPU Overflow | 如果四舍五入结果的大小超过目标格式中最大有限数的大小,则发生该错误。 | ASYNC | 致命错误 | Watchdog |
29 | FPU Underflow | 两个相关的事件导致了这个错误:1)创建一个非常小的操作数,以后可能会导致一些其他的异常,2)除以时溢出产生不精确的结果。 | ASYNC | 致命错误 | Watchdog |
30 | FPU Precision lost | 在操作结果不能完全以目标格式表示时发生。 例如,1/3不能以二进制形式精确表示。 这种异常频繁发生,表明有一些(通常可接受的)异常已经丢失。 大多数应用程序掩盖此异常 | ASYNC | 致命错误 | Watchdog |
31 | FPU Stack fault | 由于堆栈溢出或下溢,在FPU上生成错误。 | ASYNC | 致命错误 | Watchdog |
32 | Unknown module ID | 内部错误。 错误代码中遇到的未注册的模块代码。 | ASYNC | 致命错误 | Watchdog |
33 | Failed to create Logger message queue | 内部系统资源不能分配 | ROOT | 致命错误 | Watchdog |
34 | Failed to create logger task | 内部错误。 联系技术支持。 | ROOT | 致命错误 | Watchdog |
35 | Failed to write logger file | 写入日志文件时发生错误。 如果同时产生很多错误,就会发生这种情况。 | ASYNC | 错误 | None |
36 | Invalid logger message queue ID | 内部错误。联系技术支持。 | ASYNC | 致命错误 | Watchdog |
37 | Failed to create logger mutex | 内部错误。联系技术支持。 | ROOT | 致命错误 | Watchdog |
38 | Invalid logger mutex | 内部错误。联系技术支持。 | ASYNC | 致命错误 | Watchdog |
39 | Task does not exist | 在任务不存在时响应ERROR或ERRORNUM任务查询而生成错误。 | SYNC | Note | None |
40 | Invalid message queue | 无效的消息队列ID | SYNC/ ASYNC | 致命错误 | Watchdog |
41 | Failed to create Error Handler task | 内部错误。联系技术支持。 | ROOT | 致命错误 | Watchdog |
42 | Failed to create Error Handler message queue | 内部错误。联系技术支持。 | ROOT | 致命错误 | Watchdog |
43 | Error message queue overflow | 错误太多。 有些错误信息可能会丢失。 | ASYNC | 错误 | None |
44 | Logger message queue overflow | 错误消息流量太多。 有些错误信息可能会丢失。 | ASYNC | 错误 | None |
46 | Could not stop Interpreter | 用户进程不能被默认的系统错误处理程序停止。 | ASYNC | 致命错误 | Watchdog |
47 | Cannot proceed user error handler | 内部错误。联系技术支持。 | ASYNC | 致命错误 | Watchdog |
48 | Error code with invalid severity | 内部错误。联系技术支持。 | ASYNC | 致命错误 | Watchdog |
49 | Error code with invalid context info | 内部错误。联系技术支持。错误处理程序状态机识别的上下文值无效。 | ASYNC | 致命错误 | Watchdog |
50 | Cannot open logger file | 打开记录器文件时发生文件系统错误。 | ASYNC | 错误 | None |
51 | User error handler cannot be created. | 产生用户错误处理程序任务时发生错误。增加内存。 | SYNC | 错误 | None |
52 | User error handler message queue failed | 内部错误。联系技术支持。 | SYNC | 致命错误 | Watchdog |
53 | User error handler stack allocation failed. | 无法创建内部数据结构。增加内存或卸载不必要的任务。 | SYNC | 错误 | None |
54 | Recurring attempt to define user system error handler | 用户系统错误处理程序只有一个实例可能存在。 | SYNC | 错误 | Idle Task |
55 | Unsuccessful OnSystemError kill | 用户错误处理程序无法运行。 | ASYNC | 错误 | Idle Task |
56 | Bad exception handle | 异常句柄错误 | SYNC | 错误 | Idle Task |
57 | Bad exception number | 错误的异常号 | SYNC | 错误 | Idle Task |
58 | Exception number is already used | 已使用异常号 | SYNC | 错误 | Idle Task |
59 | No memory | 内存不足 | SYNC | 错误 | Idle Task |
60 | Too many user defined exceptions | 用户定义的例外太多 | SYNC | 错误 | Idle Task |
61 | Invalid error print level | 无效的错误打印级别 | SYNC | 错误 | Idle Task |
62 | Unknown error | 错误代码不能被错误处理程序识别。 | ASYNC | 致命错误 | Watchdog |
63 | On System Error queue is full | 系统错误队列已满 | SYNC | 错误 | Idle Task |
64 | Fault.log file was invalid see Fault.bak file | Fault.log文件无效,请参阅Fault.bak文件 | SYNC | 错误 | Idle Task |
65 | Error occurred in the attached motion element. | 如果系统中出现任何未注册的错误,则关联运动元素的所有任务都会因此错误而停止。 | ASYNC | 错误 | Idle Task |
66 | CPU overload. | 用户任务进入繁忙循环超过4秒钟。增加延迟 | ASYNC | 错误 | Idle Task |
Built In Test (1000 through 1999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
1001 | Internal error. Contact technical support. | 内部错误。联系技术支持。 | ROOT | 致命错误 | Watchdog |
1002 | Internal error. Contact technical support. | 内部错误。联系技术支持。 | ROOT | 致命错误 | Watchdog |
1003 | System memory exhausted: unload tasks or add memory. | 位任务验证至少200k字节的连续内存不可用。 卸载不必要的任务或添加内存。 | ASYNC | Note | |
1004 | Out of memory: add more memory or unload unnecessary tasks. | 内存不足。位不能为新的句柄分配所需的RAM量。 这可能会发生在响应WDINIT()函数。添加更多内存或卸载不必要的任务。 | SYNC | 错误 | Idle Task |
1005 | Invalid BIT handle. | 内部错误。位任务收到一个无效的句柄(指针)。该句柄是响应WdInit()函数而生成的,并且必须在WdCycle()函数中指定 | SYNC | 错误 | Idle Task |
1006 | Task stuck. | 应该报告给Bit的任务之一还未完成。一个任务告诉Bit,在执行WDINIT时会报告给INIT。此后,该任务必须定期执行WDCYCLE。 | ASYNC | 致命错误Watchdog | {{{6}}} |
1015 | Error reading to SERCON DPRAM. | 内部错误。硬件上电测试从SERCON芯片双端口RAM读取失败 | ASYNC | 错误 | |
1016 | Error writing to SERCON DPRAM. | 内部错误。硬件上电测试无法写入SERCON芯片的双端口RAM | ASYNC | 错误 | |
1020 | TaskUnlock() failure | 内部错误,由诊断代码返回。不适用于应用程序。 | ASYNC | 致命错误 | Watchdog |
1021 | TaskLock() failure. | 内部错误,由诊断代码返回。不适用于应用程序。 | ASYNC | 致命错误 | Watchdog |
1023 | WatchDog failure. | 内部错误,由诊断代码返回。不适用于应用程序。 | ASYNC | 致命错误 | Watchdog |
Run Time Scheduler (2000 through 2999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
2001 | Unknown error. Contact tech support. | 内部错误:无法识别的错误代码 | ASYNC | 致命错误 | |
2002 | Internal error. Contact tech support. | 内部错误:未能为MutEx信号量分配数据结构。 | ROOT | 致命错误 | |
2003 | Internal error. Contact tech support. | 内部错误:未能为同步信号分配数据结构 | ROOT | 致命错误 | |
2004 | Overlap error. | 没有足够的系统资源来运行所有强制性系统任务。 | ASYNC | 错误 | |
2005 | Internal error. Contact technical support. | 内部错误:无法对未注册的RTS元素执行调度操作。 | ASYNC | 致命错误 | |
2006 | Internal error. Contact technical support. | 内部错误:信号不能被采集。 | ASYNC | 致命错误 | |
2007 | Internal error. Contact technical support. | 内部错误:任务收到无效的操作请求。 | ASYNC | 致命错误 | |
2008 | Out of memory. | 内部错误:没有足够的内存来分配内部数据。 | ASYNC | 致命错误 | |
2009 | Internal error. Contact technical support. | 内部错误:产生Reatime Scheduler任务时失败 | ROOT | 致命错误 |
Motion (3000 through 3100)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
3001 | Maximum number of groups in the system exceeded | 系统中定义的组超过允许的组。系统最多支持32个组。当输入的元素多于允许的元素时,SYNCSTART命令也会发生错误。 | SYNC | 错误 | |
3002 | Non-existent axis | 内部错误。 给出一个未知的轴号。 这个错误只能通过解释器的无效输入引起。 | SYNC | 致命错误 | Watchdog |
3003 | Non-existent group | 内部错误。 给出了一个未知的组号。 输入了无效的组句柄。 此错误只能通过解释器中的无效组地址引起。 | SYNC | 致命错误 | Watchdog |
3004 | Too many axes in group | 组中定义的轴数太多。组中轴的数量限制为32。 | SYNC | 错误 | |
3005 | Non-existent group or axis | 内部错误。输入了无效的组或轴的句柄。句柄用于组和轴。如果不清楚轴或组是否被访问,并且句柄指向不存在的元素,则返回错误。 | SYNC | 致命错误 | Watchdog |
3006 | Element is already attached to a task | 元素已经关联到一个任务。 在ATTACH命令或任何需要关联权限的命令中出现错误。 | SYNC | 错误 | Idle Task |
3007 | Invalid mode | 内部错误。给定的模式无效。根据发出的命令(MOT_MODAL,MOT_NODAL,MOT_IMMEDIATE),模式只能有一定的数值。 | SYNC | 致命错误 | Watchdog |
3008 | Velocity out of range | 速度的值不在该系统变量(最大速度,巡航速度,最终速度...)的允许范围内。 例如,A1.VMAX=-1。 | SYNC | 错误 | Idle Task |
3009 | Time value out of range | 无效的持续时间值给出。 时间值(通常是时间间隔)不在允许的范围内。 | SYNC | 错误 | Idle Task |
3010 | Wrong parameter value. | 提供的命令值无效。 在所有运动命令中检查命令参数的适当值(STOPTYPE,PROCEEDTYPE,...) | SYNC | 错误 | |
3011 | Not available nodal package. | 内部错误。该变量目前不可用。可以查询节点变量,但用户命令集不支持该功能。节点包并不总是可用的。 | SYNC | 致命错误 | Watchdog |
3012 | Acceleration out of range | 加速度的值不在允许的加速度值的范围内。 例如,A1.ACC=-1 | SYNC | 错误 | |
3013 | Deceleration out of range | 减速度的值不在允许的减速度值的范围内。 例如,A1.DEC=-1 | SYNC | 错误 | |
3014 | Jerk out of range | 加加速度值不在允许的加加速度值的范围内。例如A1.JERK=-1 | SYNC | 错误 | |
3015 | Velocity override out of range | 速度覆盖的值超出了允许值的范围。例如 A1.VELOCITYOVERRIDE=-1 | SYNC | 错误 | |
3016 | Group envelope error | 该组的位置误差大于PEMAX指定的允许误差。 | ASYNC | 错误 | 运动停止 |
3017 | Axis following error: | 轴的位置误差大于由PEMAX指定的允许误差。 | ASYNC | 错误 | 运动停止 |
3018 | Wrong position value. | 给出的位置值无效。给定的位置超出了该轴定义的位置范围。 | SYNC | 错误 | |
3019 | Axis belongs to a group. | 内部错误。无法删除属于组的轴。 | SYNC | 致命错误 | Watch dog |
3020 | The element is moving | 尝试从监视器输入三个MOVE命令时会返回此错误。从监视器只能有两个MOVE命令缓存。当轴已经运动时尝试启用齿轮传动或凸轮运动时,也会返回错误。 | SYNC | 错误 | |
3021 | At axis. Input switch might have been dedicated to an other function | 当输入切换模式功能改变时,返回该注释 | SYNC | Note | None |
3022 | Homing maximum distance exceeded - aborting homing procedure | 在回原点时,超过最大回原点行程极限 | SYNC | 错误 | |
3023 | The action is not allowed in this CONMODE | N/A for MC | N/A | N/A | |
3024 | Unknown mechanical model | 无效的模型类型。 模型类型用于指定机械结构。 | SYNC | 错误 | |
3025 | Axis active in a group. | 组的轴不能独立于组关联或分离。 | SYNC | 错误 | |
3026 | Motion inhibited: Set Motion flag to ON | 运动指定的元素被MOTION属性禁止。 | SYNC | 错误 | |
3027 | Circle can be done in 2 or 3D | CIRCLE命令不能在少于2个轴或3个轴的组上执行。 | SYNC | 错误 | |
3028 | Not available at this state | N/A for MC | SYNC | 错误 | |
3029 | The group cannot be synchronized with its axes. | 组和它的轴不能同步。 | SYNC | 错误 | |
3030 | Attachment Error : Different motion types | 只有当它们的轴具有相同的运动类型时,才能关联或运动该组。 轴运动类型可以是LINEAR或ROTARY。 | SYNC | 错误 | |
3031 | This command is not allowed during AI | 某些命令(如CIRCLE,DELAY,WAITFORMOTION,...)在高级插补过程中不能使用。 | SYNC | 错误 | |
3032 | Axis specified more than once in group | 该组不能由一个轴的多个实例组成。 | SYNC | 错误 | |
3033 | SYNC flag not set. Set STARTTYPE to SYNC | SYNCSTART命令是在StartType没有被定义为SYNC的元素上运行的。 | SYNC | 错误 | |
3035 | Synchronized movement is pending. Clear sync using SYNCCLEAR command | 运动元素存在一个挂起的同步运动。 在发出SYNCSTART命令之前,运动元素无法运动,或者使用SYNCCLEAR清除同步。 | SYNC | 错误 | |
3036 | Automatic braking | 元素正在自动停止。当最终速度不为零并且没有挂起的运动命令时,可能会发生这种情况。 | ASYNC | 错误 | |
3037 | Not stopped. | 给一个没有停止的元素的proceed命令。 | SYNC | 错误 | |
3038 | The element is stopped from another task | 元素被其他任务停止时,无法定义齿轮或凸轮。在这种情况下,STOP命令也禁止运动。 | SYNC | 错误 | |
3039 | Only the task can Proceed | 该元素已被任务停止。PROCEED命令必须从任务发出,而不是从终端发出。 | SYNC | 错误 | |
3040 | Only the monitor can Proceed | 已经由终端的STOP命令停止的运动元素只能由终端的PROCEED命令启动,而不能从另一个任务启动。 | SYNC | 错误 | |
3041 | Nothing to proceed | PROCEED命令在一个尚未停止的元素上发出。 | SYNC | Note | |
3042 | Proceed in progress. | 对于PROCEED和STOP命令有一些限制。详情请参阅参考手册。 | SYNC | 错误 | |
3043 | Cannot execute move. Element is stopped by another task. | 当一个元素用STOP命令停止后,不能执行,直到执行STOP命令的同一个任务发出一个PROCEED命令。 | SYNC | 错误 | |
3044 | Jog is not allowed on group: specify axis name | 点动只能在一个轴上完成。 | SYNC | 错误 | |
3045 | Wrong speed override value. | 设置VELOCITYOVERRIDE功能的百分比是有限的。 请参阅参考手册了解允许的范围。 | SYNC | 错误 | |
3046 | Smooth factor out of range | 给定的平滑值不在范围内。请参阅参考手册了解允许的范围。 | SYNC | 错误 | |
3047 | Excessive Jerk/Acceleration ratio: decrease jerk or increase accel and decel | 加速度比率定义了达到最大加速度所需的时间。此时间不能少于5个运动采样周期。该比例受限于0.9 * PI /(5T),其中T是以毫秒为单位的周期时间。因此,当循环时间是2毫秒时限制是282.74,当循环时间是4毫秒时是141.37。使用从0到100的SMOOTHFACTOR来解决JERK的限制。 | SYNC | 错误 | |
3048 | Proceed command may be entered from monitor | 如果停止运动的任务在没有提供PROCEED命令的情况下被终止或终止,则允许从终端接收PROCEED命令。 | SYNC | Note | |
3049 | Group is stopped: at least one of its axes is disabled or in following mode | 由于其中的一个(或多个)轴已禁用或进入跟随模式,组停止。 | SYNC | Note | |
3050 | The movement has been recalculated | 运动状态有变化,在运动计算开始之前,但在此之前,运动可以执行。 | SYNC | Note | |
3051 | The current operation mode doesn't allow this action | N/A for MC | SYNC | 错误 | |
3052 | Circle plane out of range: must be 0, 1 or 2 | CIRCLE命令可以在XY平面,YZ平面或XZ平面中执行。在CIRCLE命令中,这些平面分别使用值0,1和2指定。 | SYNC | 错误 | |
3053 | Wrong master declaration. | 主类型的定义错误。 检查主源分配的递归。 | SYNC | 错误 | |
3054 | Invalid slave specification | 尝试将组指定为从轴时发生此错误,例如G1.MasterSource = A1.PCMD。一个组不能被声明为从属。当主/从规格超出范围时也会发生。 例如,A1.SLAVE = 3 | SYNC | 错误 | |
3055 | The element is already a slave | 当轴已经是从轴时,不能声明主轴或从轴类型(齿轮或凸轮)。 | SYNC | 错误 | |
3056 | One of the axes in the group is a slave: absolute motion not allowed | 如果组中的某一个轴被设置为从轴,则不允许在组上进行绝对位置运动。 | SYNC | 错误 | |
3057 | Absolute move not allowed on slave axis | 在尝试在从动轴上执行绝对运动命令时发生。 从轴上只允许增量移动。 | SYNC | 错误 | |
3058 | The drive is disabled or in the following mode; no motion allowed | 如果驱动器被禁用或轴处于跟随模式,则无法执行运动命令。 | SYNC | 错误 | |
3059 | Master axis unknown: specify master source | 主轴声明丢失时产生该错误。当一个轴被声明为一个从轴时,会检查主轴是否存在。 | SYNC | 错误 | |
3060 | Invalid cam index | 内部错误。出现凸轮查询并且不能识别凸轮时,会显示此错误。 | SYNC | 致命错误 | |
3061 | Can't declare more cam tables. | 凸轮表格不能被定义。 只能定义256个凸轮表。 | SYNC | 错误 | |
3062 | Wrong cam table size | 凸轮表尺寸必须为16模。使用LOADCAMDATA命令加载凸轮文件时会返回此错误。 | SYNC | 错误 | |
3063 | Problem reading cam data file: verify file size and existence. | 从文件读取数据时出现问题。 从文件中读取的数据项的数量与文件大小不匹配,或者文件不存在。 | SYNC | 错误 | |
3064 | No NEXT cam table: camming terminated and slave axis stopped | 凸轮表的末端已经到达,没有下一个凸轮表。轴停止并退出从轴模式。 | ASYNC | Note | |
3065 | No PREVIOUS cam table: camming terminated and slave axis stopped | 已经到达凸轮表的起始点,没有之前的凸轮表。轴停止并退出从轴模式。 | ASYNC | Note | |
3066 | Two identical master values inside cam table: change cam table | 当检查单调性时,在凸轮表内找到两个相同的主值。 | SYNC | 错误 | |
3067 | The cam table is not monotonic | 凸轮表必须是单调的(向上或向下)。当一个轴被声明为一个从轴或者当一个文件被加载到一个凸轮表中时,检查单调性。 | SYNC | 错误 | |
3068 | Cam offset not found in the cam table | 在凸轮表中找不到指定的CAMOFFSET。 必须将CAMOFFSET的值作为凸轮表中的主位置值之一。 | SYNC | 错误 | |
3069 | The cam table is already linked: unlink table before changing it | 链接后,文件无法加载到凸轮表中。 如果已链接,凸轮表不能被删除。 | SYNC | 错误 | |
3070 | Not calibrated. | 内部错误 | SYNC | 错误 | |
3071 | Already calibrated/configured | N/A for MC | N/A | N/A | |
3072 | Enabled. | 如果元素已使能,则不能发出configgroup命令,而在使能驱动器时,不能执行其他的操作。 | SYNC | 错误 | |
3073 | Time cannot be negative. | TIME必须为正值. | SYNC | 错误 | |
3074 | Cam table is empty. | 加载文件时或轴被声明为从轴(凸轮模式)时检查凸轮表 | SYNC | 错误 | |
3075 | Gear ratio out of range | 电子齿轮比超出范围。 参考参考手册中的GEARRATIO轴属性。 | SYNC | 错误 | |
3076 | Value could not be queried in a single cycle time. | 查询实时矢量变量时,需要从一个采样周期中获取所有的坐标值。 如果系统过载,这是不可能的。 | SYNC | 错误 | |
3077 | The Cam data array is in use | 当使用凸轮数据数组时,其操作受到限制: 1) 将文件加载到数据数组中, 2) 保存数组, 3) 重新创建数据数组 , 4) 将从轴或主轴值写入数组。当该数组是该轴的活动凸轮时,正在使用凸轮数据数组。 | SYNC | 错误 | |
3078 | Cam cycles out of range | 指定的凸轮循环数超出范围。 请参阅参考手册中的CYCLE凸轮属性说明。 | SYNC | 错误 | |
3079 | No active cam. | 没有为轴定义凸轮。在执行以下轴属性:ACTIVECAM,CAMCYCLE,CAMINDEX查询时,将返回此错误。 | SYNC | 错误 | |
3080 | Wrong file extension: must be .cam | 凸轮文件的扩展名必须是.CAM | SYNC | 错误 | |
3081 | Cam chain is not connected correctly. | 当轴移动到下一个或上一个表格时,将检查表格之间的连接。 如果连接不正确,则轴停止并退出从轴模式 | ASYNC | 错误 | |
3082 | Feedback velocity is out of limit | 实际速度受VELOCITYOVERSPEED属性的限制。 当实际速度超过VELOCITYOVERSPEED时,运动停止。 | ASYNC | 错误 | 运动停止 |
3083 | Feedback velocity is out of limit when motion is stopped: drive disabled | 实际速度受VELOCITYOVERSPEED属性的限制。 当实际速度超过VELOCITYOVERSPEED时,运动停止。 如果在运动已经停止时发生这种情况,则驱动器被禁用。 这可能表示驱动器调试问题或噪音问题。 | ASYNC | 错误 | 驱动器被禁用 |
3084 | SYNC | Error | |||
3085 | Incorrect parameter value | 当用户给定的参数不在允许的参数范围内时,返回一般错误。 | SYNC | 错误 | |
3086 | Incorrect number of point coordinates given to this movement | 在给定的组(不要与关节混淆)运动命令如:MOVE,MOVES,...目标点师必须有精确的坐标数(等于组中的轴数) | SYNC | 错误 | |
3087 | SYNC | Error | |||
3088 | Wrong factor value : specify a positive value | 有些值 (PFAC, AFAC, VFAC, ....)不能是负数 | SYNC | 错误 | |
3089 | Property value cannot be changed while drive is enabled | 某些属性(如转换系数)在驱动器使能时不能更改。有关指令执行的限制,请参阅参考手册。 | SYNC | 错误 | Idle Task |
3090 | Can not execute syncstart without any pending move command | SYNCStart中没有定义运动的错误 | SYNC | 错误 | |
3091 | Drive mode failure (unable to set drive-mode) | N/A for MC | N/A | N/A | |
3092 | Property can not be changed while cam is active : disable cam before changing it | 凸轮表处于活动状态时,某些凸轮属性不能更改。 | SYNC | 错误 | |
3093 | Invalid hard limit switch state | N/A for MC | N/A | N/A | |
3094 | Hard limit switch was detected | N/A for MC | N/A | N/A | |
3095 | The cruise velocity can not be reached | 串联期间(vifnal非零) | SYNC | Note | |
3096 | Minimum position limit must be less than the maximum limit | PMIN必须小于PMAX | SYNC | 错误 | |
3097 | Data structure is not defined. | 补偿或凸轮表未定义 | SYNC | 错误 | |
3098 | VelocityMax exceeds the max number of counts per motion sample. Reduce VelocityMax or change PositionFactor - VelocityFactor settings. | SYNC | Error | ||
3099 | Cannot execute InPosition | 当前一个运动的最终速度非零时,STARTTYPE的INPOSITION值是没有意义的。 | SYNC | Note | |
3100 | Configuration switch. | N/A for MC | N/A | N/A |
Motion (3101 through 3200)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
3101 | Time jog is meaningless | TimeJog不能为零. | SYNC | Note | |
3102 | The index is out of the table range. | 索引超出凸轮表范围。 尝试访问凸轮表中的值(索引大于表中的点数)时会返回此错误。 | SYNC | 错误 | |
3103 | Given value will cause cam table to be non-monotonic: value not accepted. | 凸轮表被链接,但数据未被使用。给定主轴的值将导致表非单调性,所以该值不被接受。 | SYNC | Note | |
3104 | The movement will be calculated until the position limit | SYNC | Note | ||
3105 | Blending is not provided with non-zero final velocity motions and jog movements | vfinal = ..和cp = … 不能同时使用 | SYNC | 错误 | |
3106 | Invalid Quaternion. | 内部错误,在SCARA&DELTA运动学中获得非零偏航和俯仰的方位时 | SYNC | 错误 | |
3107 | Initialized the velocity to its maximum | 如果 Vcruise > vmax ,将设置为vmax。 | ASYNC | Note | |
3109 | Wrist configuration at the target point differs from the wrist configuration of the start! | 在运动路径中通过手腕奇异点时,手腕改变其翻转值,因此目标位置可以不同于其预先计算的值,并且可以发出重新计算的通知 | ASYNC | Note | |
3110 | Wrong Phaser definition. | 相位器参数无效 | SYNC | 错误 | |
3111 | Wrist Singularity encountered. Motion has been stopped. Try with different movement type | 无法处理的手腕奇异点 | ASYNC | Note | |
3112 | Initialized the acceleration to its maximum | 如果acc > amax,acc将设置为amax | ASYNC | Note | |
3113 | Initialized the deceleration to its maximum | 如果dec > dmax,dec将设置为dmax | ASYNC | Note | |
3114 | Initialized the jerk to its maximum | 如果jerk> jmax,jerk将设置为jmax | ASYNC | Note | |
3115 | Element entered into following mode, all motions aborted | 运动由于元素禁用被中止 | SYNC | 错误 | |
3116 | The configuration flags can not be specified together with joint target position. | 不能同时给出关节目标坐标和配置标志 | SYNC | 错误 | |
3117 | Point too close. The target coordinates are too close to the robot's Cartesian space origin point. | 目标点位于Rmin球体内(仅在PUMA的情况下为XY圈) | SYNC | 错误 | |
3118 | MOVES can not interpolate these orientation angels. Try with different orientation interpolation or change the target to location. | 某些方向路径不能与平移部分一起按比例插补,因为平移所需的关节角度与给定定向分量冲突 | SYNC | 错误 | |
3119 | Point too far. Outside of the working envelope. The target coordinates are too far from the robot's Cartesian space origin point. | 目标点在Rmax球体之外 | SYNC | 错误 | |
3120 | Not a robot. | 某些属性仅适用于机器人模型,并不存在于常规组中 | SYNC | 错误 | |
3121 | The target point is not reachable. | 目标坐标超过[pmin,pmax]的范围 | SYNC | 错误 | |
3122 | Motion can not be executed due to the unsolvable configuration change. | 在直线运动期间,一些启动和目标配置标志不会有差异(ABOVE, BELOW) | SYNC | 错误 | |
3123 | Unreachable target orientation. | 内部检查四元数。 在一些机器人模型(SCARA,DELTA <...)中,方位表示的NDOF受到限制,因此目标方位的四元数将受到一定的限制。 通常用户不会产生这个错误。 | SYNC | 错误 | |
3124 | Crossing unreachable region. | 例如在SCARA中,不允许有穿过Rmin球体的直线运动 | SYNC | 错误 | |
3125 | Wrong point type. | 位置点类型不适合给定的命令/属性。 | SYNC | 错误 | |
3126 | Can not de-select orientation coordinates. Check the selectaxis property | N/A for MC | N/A | N/A | |
3127 | Both final velocities(rotary & translation) must be zero or non zero | vtranfinal和vrotfinal既可以是零也可以都是非零。 | SYNC | 错误 | |
3128 | Error in Closed-Chain Kinematics. Point is not reachable | 关节坐标不闭环闭链运动学(仅在某些模型中发生:SCISSOR,CSE,...) | ASYNC | 错误 | |
3129 | Task start failure. | 内部错误。无法启动任务。该错误从操作系统返回。 | SYNC | 致命错误 | |
3130 | Task end failure. | 内部错误。无法结束任务。该错误从操作系统返回。 | SYNC | 致命错误 | |
3131 | Invalid semaphore ID or time-out elapsed. | 内部错误。无效的信号ID。该错误从操作系统返回。 | SYNC | 致命错误 | |
3132 | Invalid message. | 内部错误。运动管理器收到无效的消息。运动管理器是一个消息驱动的任务。接收到无效的消息是致命的系统故障。 | SYNC | 致命错误 | |
3133 | Invalid element handle. | 内部错误。在实时执行期间遇到无效的元素句柄。该错误与MOT_ERR_IELEMENT相同,但是这次是内部源(而不是解释器) | ASYNC | 致命错误 | |
3134 | No memory. | 内部错误。系统中没有更多的空闲内存。系统的内存已经耗尽。运动的内存应始终可用。 | SYNC | 致命错误 | |
3135 | Invalid pointer. | 内部错误。在实时执行过程中遇到无效的指针。在RTK或MM任务中找到零指针。 | SYNC | 致命错误 | |
3136 | Corrupted task data. | 内部错误。无效的任务数据。每个关联任务都由一个数据块表示。如果这些数据已损坏,则会发生致命的系统错误。 | SYNC | 致命错误 | |
3137 | Task mismatch. | 内部错误。 一个任务试图添加一个轴到它没有创建的组。 组创建是一个几个步骤的过程,在这个过程中,只有开始创建组的任务才能结束。 | SYNC | 致命错误 | |
3138 | Bad dimension. | 内部错误。元素维数(轴数)无效。 每个运动包都包含组的大小(维度)。 如果封装了两个维数不同的包的副本,则会生成此致命错误。 | SYNC | 致命错误 | |
3139 | Corrupted data | 内部错误。在删除元素过程中,遇到了损坏的数据。当元素数据被解除分配时,进行一些检查。其中检查是验证所有分配的运动包都被删除。如果不是,则产生错误。 | SYNC | 致命错误 | |
3140 | RTS blocked. | 内部错误。RTS没有释放信号量, RTS周期性地释放这个信号量,但是如果信号量在两个时间周期之后没有被释放,这个错误被设置。 它表示RTS运行不正常或中断处理程序停止。 | ASYNC | 致命错误 | |
3141 | Bad profile data. | 内部错误。分析器错误。提供的配置文件计算的数据无效。 | SYNC | 致命错误 | |
3142 | RTS element add failed. | 内部错误。RTS未能添加元素。RTS拒绝在其表中添加新的元素。 | SYNC | 致命错误 | |
3144 | RTS clear motion failed. | 内部错误。 RTS无法清除运动启用标志。 RTK初始化期间或暂停 - 恢复转换期间可能发生错误。 | ASYNC | 致命错误 | |
3145 | RTS set motion failed. | 内部错误。 RTS未能设置运动启用标志。 RTK初始化期间或暂停 - 恢复转换期间可能发生错误。 | ASYNC | 致命错误 | |
3146 | RTS overrun clear failed. | 内部错误。 RTS未能清除溢出标志。 仅在运行时发生。 | SYNC | 致命错误 | |
3147 | RTS delete failed. | 内部错误。RTS未能删除元素。在删除任务结束时,系统无法删除RTS条目。恢复操作不需要,因为任务已经结束。 | SYNC | 致命错误 | |
3148 | Computing too late | 预计算较晚。对于即时移动或速度倍率等即时运动变化,假定预计算时间延迟。 通常,这个延迟应该足以完成计算。 这个错误通常表明系统负载过重。 | ASYNC | 错误 | |
3149 | Unable to create system resource. | 内部错误。操作系统无法创建资源(队列,信号量...)可能的原因:没有更多内存,操作系统关闭。 | SYNC | 致命错误 | |
3150 | Invalid profiler parameters. | 内部错误。无效的分析器参数。 | Sync | 致命错误 | |
3151 | Profiler in motion. | 内部错误。某些分析器设置只能在加速度为零时设置。 | SYNC | 致命错误 | |
3152 | Invalid profiler status. | 内部错误。分析器是驱动状态的。如果遇到无效状态,则会发生此错误。 | SYNC | 致命错误 | |
3153 | RTK continuously interrupting. | 内部错误。 RTK处于连续重复停止状态。 | ASYNC | 致命错误 | |
3154 | Maximum Position reached. | 达到最大轴限制。通常通过JOG命令。 | SYNC | 错误 | |
3155 | Minimum position reached | 轴达到的最小限制。通常通过JOG命令。 | SYNC | 错误 | |
3156 | No previous package. | 内部错误。在预先计算过程中,在m.p.环是需要的。 | SYNC | 致命错误 | |
3157 | Supper-immediate movements can be executed with the trapezoidal velocity profile only. | starttype = 5时smooth必须等于0 | SYNC | 错误 | |
3158 | Property value cannot be changed while drive is disabled | 如果驱动器被禁用,则某些属性(slave, ...)不能更改为某些值。 与某些命令相同proceed, move, ... | SYNC | 错误 | |
3159 | No memory for group/axis definition | 系统中没有更多的空闲内存。 系统的内存已经耗尽。 | SYNC | 错误 | |
3160 | Wrong PLS index. | 错误的PLS索引。 | SYNC | 错误 | |
3161 | Can't declare more PLS's | 最多可以声明65536个PLS。 | SYNC | 错误 | |
3162 | PLS property cannot be set while PLS is enabled | PLS启用时,某些PLS属性不能设置。首先,禁用PLS,然后更改属性值。 | SYNC | 错误 | |
3163 | PLS value cannot be accessed before the PLS data are created | 为了在PLS上操作,必须定义PLS (COMMON SHARED ... AS PLS),并且必须创建PLS数据(CREATEPLSDATA)。 | SYNC | 错误 | |
3164 | PLS position index out of range | 尝试访问不存在的PLS位置时会返回此错误。创建PLS数据结构(CREATEPLSDATA)时设置PLS位置的数量。 | SYNC | 错误 | |
3165 | PLS position data must be monotonic | PLS数据结构中的数据必须按升序排列。 当尝试启用PLS时,顺序会被验证。 | SYNC | 错误 | |
3166 | PLS output polarity must be binary (0 / 1) | PLS输出极性必须是二进制(0或1)。 | SYNC | 错误 | |
3167 | Wrong value for the repetition interval. | 重复间隔错误的值 | SYNC | 错误 | |
3168 | PLS Enable must be binary ( 0 or 1 ) | PLS启用必须是二进制(0或1) | SYNC | 错误 | |
3169 | Fatal Fault, the error number is not defined by the programmer | 内部错误 | SYNC | 致命错误 | Watch dog |
3170 | PLS Hysteresis must be positive | PLS指定的滞后值必须是正值 | SYNC | 错误 | |
3171 | PLS cannot be deleted while it is enabled | PLS启用时,不能被删除。 首先使用PLSENABLE属性关闭PLS。 | SYNC | 错误 | |
3172 | Wrong output index. | 错误的输出索引. | SYNC | 错误 | |
3173 | Cannot attach element. Element is stopped by another task: issue PROCEED command | STOP命令既用于停止运动又用于禁止进一步的运动。 如果从终端或任务发出STOP命令,则在发出PROCEED命令之前,运动元素不能被另一个任务关联。 | SYNC | 错误 | |
3174 | Current property cannot be changed for a Master axis | 轴被定义为主轴时当前的属性不能更改,应首先通过将从轴的从属属性设置为OFF来关闭主/从轴。 | SYNC | 错误 | |
3175 | Wrong index for location. | 查询位置变量的坐标,如here,setpoint, tool等等。给出了[1,NDOF]以外的索引。 | SYNC | 错误 | |
3176 | PLS value will is scaled to be at the range 0-100%. | N/A for MC | N/A | N/A | |
3177 | Cannot execute the move command while the axis is active in a group | 如果轴关联了组,则不能单独移动轴。 例如,如果G1有AX1,MOVE AX1 ...不允许。 | SYNC | 错误 | |
3178 | Cannot execute the stop command while the axis is active in a group | 轴不能独立于其组而停止。 | SYNC | 错误 | |
3179 | Cannot move immediate. Need to proceed motion | 被停止的元素不能执行即时运动(StartType=1),直到执行proceeded. | SYNC | 错误 | |
3181 | Index out of range | Link[]或 Axis[]错误的索引 | SYNC | 错误 | |
3182 | Disable time out expired: NETWORK SHUTDOWN | 禁用驱动器超时 | SYNC | 错误 | |
3183 | Settling time expired | 达到位置超时 | SYNC | 错误 | |
3184 | Maximum trial time to settle is less than settling time | 最大试验时间要少于稳定时间 | SYNC | 错误 | |
3185 | Ambiguous configuration flags. Can not determine the joint coordinates. | N/A for MC | N/A | N/A | |
3186 | Motion Buffer Full | 运动缓冲区中已经有两个运动挂起。 | SYNC | 错误 | |
3187 | Could not interpolate in Cartesian space with this target point. Try to re-write the target point or change the motion. | 给定目标关节值的直线运动没有达到给定的目标关节坐标,最有可能是方位角的问题。 | ASYNC | 错误 | |
3188 | Insufficient points during dynamic AI | 没有足够的点做高级插值 | SYNC | 错误 | |
3191 | Pipe Mode operation failed. | 在pipe模式下读取值时出错 | ASYNC | 错误 | |
3192 | Element is not attached | 尝试从任务更改属性或移动未关联到该任务的元素。 | SYNC | 错误 | |
3193 | The user limit can not exceed the max/min limits. | N/A for MC | N/A | N/A | |
3194 | The max/min limits can not be set within the user limits. | N/A for MC | N/A | N/A | |
3195 | Element Pipe Mode is declared or system Pipe Mode is disabled. | SYNC | 错误 | ||
3196 | Wrong factor value: specify a non zero value | 错误的因子值:指定一个非零值 | SYNC | 错误 | |
3197 | Displacement cannot be set if PLS enabled. | SYNC | 错误 | ||
3199 | Value can't be changed from terminal | slave=5 只能从程序中给出 | SYNC | 错误 | |
3200 | This motion interpolation type must have a non-zero translation part | 在CIRCLE运动中只有方位部分的是不允许的。 | SYNC | 错误 |
Motion (3201 through 3300)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
3201 | At circular movement first 2 axes must be linear. Check value of PositionRollOverEnable | 如果在XY表上发出循环(例如)必须禁用翻转 | SYNC | 错误 | |
3202 | The group is not coupled | N/A | N/A | ||
3203 | The coupled matrix has been changed or its inverse doesn't exist | N/A | N/A | ||
3204 | Inverse matrix can not be calculated | 当使用三点给定圆周运动或定义耦合矩阵时 | SYNC | 错误 | |
3205 | Memory allocation for matrix failed | 当使用三点给定圆周运动或定义耦合矩阵时 | SYNC | 错误 | |
3206 | Wrong matrix dimension | 当使用三点给定圆周运动或定义耦合矩阵时 | SYNC | 错误 | |
3207 | Property valid for Group only | 有些属性没有为轴定义 | SYNC | 错误 | |
3208 | Blending omitted due to stopped motion | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3209 | Blending omitted due to braking motion | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3210 | Blending omitted due to short path | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3211 | Blending omitted due to missing cruise phase | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3212 | Blending omitted due to different motion types | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3213 | Blending omitted due to extremely short motion duration | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3214 | Blending: acceleration decreased due to exceeding total acceleration | SYNC | Note, 只有在使用sys.motionassistance =1时激活 | ||
3215 | Blending: velocity decreased due to exceeding total velocity | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3216 | Blending: velocity decreased due to profiler following | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3217 | Blending: acceleration decreased due to profiler following | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3218 | Blending: jerk decreased due to profiler following | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3219 | Blending: acceleration decreased due to short braking distance | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3220 | Blending: jerk decreased due to short braking distance | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3221 | Blending: velocity & jerk decreased for adjusting to the profiler following | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3222 | Blending: Second velocity reduced | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3223 | Blending: First velocity reduced | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3224 | Blending: First marker set | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3225 | Blending: Second marker set | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3226 | Blending omitted due to inability to adjust velocity for the given blending distance and cruise velocity | SYNC | Note,只有在使用sys.motionassistance =1时激活 | ||
3227 | Wrong moving frame index | 解释器给出一个不存在的句柄,或者没有定义通用的运动坐标系 | SYNC | 错误 | |
3228 | There isn't any moving frame linked | 没有运动坐标系被链接到机器人。 | SYNC | 错误 | |
3229 | Can't declare more moving frames | 超过系统中最大运动坐标系数 | SYNC | 错误 | |
3230 | Invalid index or ndf. Moving frame NDOF range is 1 to element NDOF | SYNC | 错误 | ||
3231 | The element is already in tracking mode | N/A for MC | N/A | N/A | |
3232 | The moving frame is already linked to an element | 运动坐标系链接到机器人时,某些设置运动坐标系的属性操作不允许 | SYNC | 错误 | |
3233 | Robot type and moving frame type must be the same | 运动坐标系的类型和机器人类型相同是强制性的 | SYNC | 错误 | |
3234 | No more triggers can be inserted | 超过最大触发次数 | SYNC | 错误 | |
3235 | The moving frame must be linked to a Robot. | 如果运动坐标系未链接到机器人,则不允许执行某些操作 | SYNC | 错误 | |
3236 | Working window limits are too close - check upmaster & downmaster values | SYNC | 错误 | ||
3237 | No more triggers in the buffer. | 在传送缓冲区中没有任何内容时,应用NextItem 命令会导致此错误 | SYNC | 错误 | |
3238 | Item missed. The item has left the working-window area. | SYNC | 错误 | ||
3239 | Blending: CP of the first movement reduced due to the big velocity ratio | N/A | N/A | ||
3240 | Property valid for axis only | 某些运动元素属性仅对轴有效。例如PFAC,PEXT。 | SYNC | 错误 | |
3241 | Delay cannot be used with the StartType set to Immediate. | DELAY命令受到运动元素的STARTTYPE延迟的影响。但是,使用STARTTYPE立即与DELAY命令是不允许的。 在执行DELAY命令之前更改STARTTYPE。 | SYNC | 错误 | |
3242 | No possibility for blending of different profile types | 不允许使用梯形速度和正弦曲线的CP混合 | SYNC | 错误 | |
3243 | Stop in progress. | 在运动停止的时候,某些非常特殊的运动情况是不允许的。 | SYNC | 错误 | |
3244 | Cannot change following mode while homing is in progress | 模式只能在运动停止时设置 | SYNC | 错误 | |
3245 | Error in homing procedure | ASYNC | Error | ||
3246 | Axis position after homing is subjected to the axis displacement | N/A for MC | N/A | N/A | |
3247 | System Motion property can be set only from the terminal | 默认系统错误处理程序将系统运动标志设置为低。 一旦发生这种情况,MOTION属性只能在终端发出SYSTEM.MOTION=ON的情况下设置为高。 | SYNC | 错误 | |
3248 | This motion interpolation type is not allowed. | 给定的插值类型是不允许的。(传送带跟踪时的关节插补,某些机器人模型上的MOVESKD,jointEnable属性为false ... | SYNC | 错误 | |
3249 | System automatic braking | 速度不是零。 该元素由系统停止。 当从轴通过其位置限制时,可能会发生这种情况。 轴由系统停止。 | ASYNC | 致命错误 | |
3250 | Different motion type in group | 只有在轴的类型相同的情况下才能定义该组。错误发生在组定义或系统或用户尝试关联组时,运动类型是LINEAR或ROTARY。 | SYNC | 错误 | |
3251 | RTS set motion failed in initialization. | 内部错误。 RTS未能设置运动启用标志。 RTK初始化期间或挂起 - 恢复转换期间发生错误。 | ASYNC | 致命错误 | |
3252 | RTS clear motion failed in initialization. | 内部错误。 RTS无法清除运动启用标志。 RTK初始化期间或挂起 - 恢复转换期间发生错误。 | ASYNC | 致命错误 | |
3253 | Following error when motion is stopped: drive disabled. | 没有运动命令,但有位置误差。 最大位置误差(PEMax)可能设置得太低,或者轴可能被外力移动,或者驱动器可能没有正确调试。 | ASYNC | 错误 | |
3254 | Envelope error when motion is stopped: drives disabled. | 没有运动命令,但有封装错误。 最大位置误差(PEMAX)可能设置得太低,轴可能被外力移动,或者驱动器可能没有正确调试 | ASYNC | 错误 | |
3255 | Fatal experience | 不应该发生 | SYNC | 致命错误 | |
3256 | The acceleration/deceleration time is not achieved | tacc / tdec值没有达到 | SYNC | Note | |
3257 | Homing is not allowed on a slaved axis | SYNC | 错误 | ||
3258 | No home input assigned | SYNC | 错误 | ||
3259 | Drive parameters are zeroed | N/A for MC | N/A | N/A | |
3260 | Value assigned was rounded up to nearest integer | N/A | N/A | ||
3261 | Invalid moving frame parameters. | 零半径,零角度或相同的上下点 | SYNC | 错误 | |
3262 | Compensation table table is empty. | SYNC | 错误 | ||
3263 | Can't declare more compensation tables. | 超过补偿表的最大数量 | SYNC | 错误 | |
3264 | Invalid compensation table index | 无论是内部解释错误还是使用未定义的通用补偿表,从解释器收到的补偿处理无效 | SYNC | 错误 | |
3265 | Compensation table active value must be set to 0 or 1. | 在这里只允许0/1 | SYNC | 错误 | |
3266 | Compensation table can not be changed while in use: value not accepted. | SYNC | 错误 | ||
3267 | Load the compensation table data and set the axes(function compset) first. | SYNC | 错误 | ||
3268 | Number of axes does not match the mechanical model | 机器人模型只能用一定数量的轴来定义 | SYNC | 错误 | |
3269 | Position command might be lost by this action | N/A for MC | N/A | N/A | |
3270 | Velocity rate initialized to its limit | 仅允许[0.1,100]百分比范围内的比率值 | SYNC | Note | |
3271 | Acceleration rate initialized to its limit | 仅允许[0.1,100]百分比范围内的比率值 | SYNC | Note | |
3272 | Deceleration rate initialized to its limit | 仅允许[0.1,100]百分比范围内的比率值 | SYNC | Note | |
3273 | Jerk rate initialized to its limit | 仅允许[0.1,100]百分比范围内的比率值 | SYNC | Note | |
3274 | After digital torque command only supper immediate movement is allowed | N/A for MC | N/A | N/A | |
3275 | The property can not be queried if no tracking (slave <>0) has been established. | SYNC | 错误 | ||
3276 | Element is detached by the system in order to avoid endless error messaging. | 在某些情况下(由关节角引起的闭链运动误差),该组自动分离 | ASYNC | Note | detach |
3277 | Absolute motion not allowed | AbsEnable为0 | SYNC | 错误 | |
3278 | Wrong buffer size. | AI: 用一个大于AI缓冲区的数组传递命令 | SYNC | 错误 | |
3279 | The correct setting is: passbuffermin < passbuffermax < passbuffersize. | AI: 检查PassBufferMin, PassBufferMax, …. | SYNC | 错误 | |
3280 | Wrong stretch factor value. | 只允许百分比在[0.1,100]内 | SYNC | 错误 | |
3281 | Wrong size of stretch factor vector or user parameter vector. | AI:使用大于AI缓冲区的数组传递命令 | SYNC | 错误 | |
3282 | Wrong relationship between passfrom and passupto properties. | passfrom必须总是小于passupto | SYNC | 错误 | |
3283 | No more points to interpolate. | DOPASS在一个空的缓冲区上执行。 | SYNC | Note | |
3284 | Wrong blend method. | AI不允许使用CP或SP混合 | SYNC | 错误 | |
3285 | Advance interpolation/Conveyor tracking cannot be used with starttype immediate. | AI不允许使用CT | SYNC | 错误 | |
3286 | Advance interpolation - points have been lost. | 清除点缓冲区(停止,重置BlendingMethod属性)不可继续停止的运动 | Note | 错误 | |
3287 | Excessive master-slave deviation | SYNC | 错误 | stop | |
3288 | Number of axes does not match the given compensation table dimensions. | SYNC | 错误 | ||
3289 | Action not allowed while compensation table is active. | SYNC | 错误 | ||
3290 | Compensation table: Limit mismatch. | SYNC | 错误 | ||
3291 | This compensation table has been already set. | SYNC | 错误 | ||
3292 | No more space for compensation tables. | SYNC | 错误 | ||
3293 | Compensation table: Invalid row. | SYNC | 错误 | ||
3294 | Velocity Safety Limit exceeded! | 在一个采样中pcmd的剧烈增加(跳跃)超过了该轴的VelocitySafetyLimit。 VelocitySafetyLimit应至少设置为该轴的10 * Vmax。 请参阅:VelocitySafetyLimit | ASYNC | 致命错误 | |
3295 | Extremely low velocity. | 不允许JOG为0 | SYNC | 错误 | |
3296 | Additive torque value is over threshold limit | TorqueAddCommand > Tmax | ASYNC | 错误 | stop |
3297 | Additive torque value is over threshold limit when motion is stopped: drive disabled | TorqueAddCommand > Tmax | ASYNC | 错误 | disable |
3298 | The pls positions are too close to each other and/or the velocity is too high for output to toggle | ASYNC | 错误 | ||
3299 | Hardware Assistance is true but not available due to wrong CPU/FPGA/etc. | SYNC | 错误 | ||
3300 | Excessive master-slave deviation when the motion is stopped: drive disabled | ASYNC | 错误 | disable |
Motion (3301 through 3999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
3301 | This Kinematic model is not fully supported yet. | SYNC | 错误 | ||
3302 | Axis was disabled due to an error. | ASYNC | Note | disable | |
3303 | Axis was disabled due to a master-slave connection. | ASYNC | Note | disable | |
3304 | Axis was disabled due to a group connection. | ASYNC | Note | disable | |
3305 | Torque error - drive is disabled. | ASYNC | 错误 | disable | |
3306 | Torque error - motion is stopped | ASYNC | 错误 | stop | |
3307 | Velocity exceeds its maximum during blending. | ASYNC | Note | ||
3308 | Velocity exceeds its maximum during CT. | ASYNC | Note | ||
3309 | Velocity exceeds its maximum. | ASYNC | Note | ||
3310 | Acceleration exceeds its maximum during blending | ASYNC | Note | ||
3311 | Acceleration exceeds its maximum during CT. | ASYNC | Note | ||
3312 | Acceleration exceeds its maximum. | ASYNC | Note | ||
3313 | Velocity exceeds its maximum during AI. | ASYNC | Note | ||
3314 | Trapezoidal Acceleration does not support on-line VORD change. Vord change will be postponed until the start of next movement. | SYNC | Note | ||
3315 | Can't operate more PLS using WithPls command. | SYNC | 错误 | ||
3316 | PLS source from type PathTime relevant only to profiler based on time. | SYNC | 错误 | ||
3317 | Drive PCMD (AT/MT)is not supported. | SYNC | 错误 | ||
3318 | Kinodynamic movement is not supported by the given motion profile. | Kino动态运动只能用于梯形加速度曲线(Prftype = 2). | SYNC | 错误 | |
3319 | This motion profile does not support immediate starttype. | 某些插值类型(MOVESKD)不支持启动类型即时选项。 | ASYNC | Note | |
3320 | Acceleration exceeds its maximum during AI. | ASYNC | Note | ||
3321 | Trapezoidal Acceleration: only zero final & initial velocity allowed. | ASYNC | 错误 | ||
3322 | Trapezoidal Acceleration: excitation control looping! | SYNC | 错误 | ||
3323 | Marginal acceleration limit exceeded, element is stopped. | ASYNC | 错误 | ||
3324 | PLS - I/O error | SYNC | 错误 | ||
3325 | PLS propagation delay cannot be larger then position error delay. | SYNC | 错误 | ||
3326 | End of program without issuing detach command, motion was stopped and the element detached. | SYNC | Note | ||
3327 | Torque command valid to axis only. | SYNC | 错误 | ||
3328 | Command is executed not in the right operation mode. | SYNC | Note | ||
3329 | Kinodynamic movement is not supported by the CP blending. | SYNC | Note | ||
3330 | Movement can't be synchronized due its type or its velocity final. | SYNC | 错误 | ||
3331 | Movement can't be stopped with the defined StopType. | SYNC | 错误 | ||
3332 | PLS is not defined to this element. | SYNC | 错误 | ||
3333 | This property is not allowed in nodal assignment. | SYNC | 错误 | ||
3334 | Invalid Proceed Sequence. | SYNC | 错误 | ||
3335 | Limit switch is engaged. | ASYNC | 错误 | ||
3336 | Movement is crossing limit switch in wrong direction. Reverse movement direction. | ASYNC | 错误 | ||
3337 | Advance Interpolation BlendingMethod 3 not allowed from terminal context. | SYNC | 错误 |
File System (4000 through 4999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
4001 | Error opening file for Retrieve | 打开文件RETRIEVE时错误 | SYNC | 错误 | |
4002 | Error opening the file for Send | 打开文件SEND错误 | SYNC | 错误 | |
4003 | Internal error. Contact technical support. | 内部错误。创建上传消息通道。 | SYNC | 错误 | |
4004 | Internal error. Contact technical support. | 内部错误。创建下载消息通道。 | SYNC | 错误 | |
4005 | Internal error. Contact technical support. | 内部错误。删除上传消息通道。 | ASYNC | 错误 | |
4006 | Internal error. Contact technical support. | 内部错误。删除下载消息通道 | ASYNC | 错误 | |
4007 | Internal error. Contact technical support. | 内部错误。上传任务存在。 | SYNC | 错误 | |
4008 | Internal error. Contact technical support. | 内部错误。下载任务存在。 | SYNC | 错误 | |
4009 | Internal error. Contact technical support. | 内部错误。 创建上传任务。 | SYNC | 错误 | |
4010 | Creating download task | 内部错误 | SYNC | 错误 | |
4011 | Internal error. Contact technical support. | 内部错误。无法创建RAM驱动器设备。 | ROOT | 致命错误 | Watchdog |
4012 | Internal error. Contact technical support. | 内部错误。错误的初始化选项 | SYNC | 错误 | |
4013 | No memory for RAM drive volume | 没有足够的内存来创建RAM磁盘。添加更多内存或删除不需要的文件。 | SYNC | 错误 | |
4014 | Time-out during file transfer | 主机已经中断文件传输操作。 | ASYNC | Note | |
4015 | No disk space | 文件操作由于缺少磁盘空间而无法完成。 | SYNC | 错误 | |
4016 | File not found | 找不到该文件。 | SYNC | 错误 | |
4017 | Error opening file | 打开文件时出错。 | SYNC | 错误 | |
4018 | Error closing file | 关闭文件出错。 | SYNC | 错误 | |
4019 | Disk full | 文件设备上没有可用磁盘空间。 | SYNC | 错误 | |
4020 | Invalid device name | 为文件操作指定的设备名称无效。 | ROOT | 致命错误 | Watchdog |
4021 | Cannot delete file. | 没有权限删除该文件。 | SYNC | 错误 | |
4022 | Cannot delete directory. Use RMDIR. | 试图删除目录。 | SYNC | 错误 | |
4023 | Cannnot delete directory - it is not empty or in use. | 不能删除目录,因为它不是空的 | SYNC | 错误 | |
4024 | Error reading directory | 执行DIR时发生错误 | SYNC | 错误 | |
4025 | Cannot create directory - it already exists or access is denied. | 无法创建目录。 | SYNC | 错误 | |
4026 | Closing directory | 执行DIR命令期间发生错误 | SYNC | 错误 | |
4027 | Memory allocation error. | 不能分配内部数据结构。添加更多内存或卸载不需要的任务。 | SYNC | 错误 | |
4028 | Error writing into file | 写入文件时出错。 | SYNC | 错误 | |
4029 | Error reading from file | 从文件读取时出错。 | SYNC | 错误 | |
4030 | Bad access to the file | 指向文件句柄的指针无效。 | SYNC | 错误 | |
4031 | Unknown file extension. | 只有特定的文件扩展名被识别。 PRG用于程序,REC用于凸轮文件的记录文件CAM。 | SYNC | 错误 | |
4032 | Cannot access this type of file | 系统不允许访问这种类型的文件。 | SYNC | 错误 | |
4033 | File does not exist | 试图在(检索,删除,加载)闪存盘上不存在的文件上进行操作时,会显示此消息。 | SYNC | 错误 | |
4034 | Root directory is full | 根目录中的文件数已达到允许的最大文件数。 | SYNC | 错误 | |
4035 | Invalid semaphore ID | 无效的信号标识。 信号量守卫文件的链接列表。 | SYNC | 致命错误 | |
4036 | Password file is broken. | 无法启动密码列表 - 密码文件无效。 | ASYNC | 错误 | |
4037 | Invalid password. | 输入的密码无效。 | SYNC | 错误 | |
4038 | Password protected | 该文件不能被删除或检索,因为它受密码保护。 使用PROGRAMPASSWORD命令删除保护。 | SYNC | 错误 | |
4039 | Error setting the password | 无法写入系统密码的日志。 | SYNC | 错误 | |
4040 | File in use. Access denied. | 已经有一个同名的文件已被打开。 如果它是打开读取,你不能打开写入。 | SYNC | 错误 | |
4041 | No available file descriptors | 当前目录中没有可用的文件描述符。 | SYNC | 错误 | |
4042 | Illegal name | 从文件系统的角度来看,文件名是非法的。 | SYNC | 错误 | |
4043 | Cannot rename. Files are on different devices. | 文件重命名失败 - 扩展名分配给不同的设备(RAM驱动器或系统设备)。 | SYNC | 错误 | |
4044 | Cannot rename. Destination file already exists. | 文件重命名失败 - 存在重复的文件名。 | SYNC | 错误 | |
4045 | Cannot rename file. | 文件重命名失败 - 文件正在使用。 | SYNC | 错误 | |
4048 | Directory does not exist. | 内部错误: 目录不存在 | SYNC | 错误 | |
4049 | Cannot create sub-directory - only 17 levels are allowed. | 无法创建子目录 - 只允许17个级别。 | SYNC | 错误 | |
4050 | Volume unavailable. | 量不可用. | SYNC | 错误 | |
4051 | Internal file system error | 内部错误 | SYNC | 错误 | |
4052 | Error opening directory. | 访问目录时发生错误。 | SYNC | 错误 | |
4053 | Firmware upgrade failure - current firmware version is not the new one. | 升级失败 - 无法删除或无法重命名文件。 文件可能被写保护 | SYNC | 错误 | |
4054 | Firmware restoration failed - current firmware version is not the previous one. | 无法复制备份文件。可能没有足够的磁盘空间或文件被写保护。 | SYNC | 错误 | |
4055 | Error creating a contiguous boot file. | 闪存或硬盘上没有足够的空间用于连续的bootrom。 | SYNC | 错误 | |
4056 | Error creating TFFS block device. | 不曾用过 | N/A | N/A | |
4057 | Cannot install file system driver. | 不曾用过 | N/A | N/A | |
4058 | No memory to create disk cache. | 内存不足 | ROOT | 致命错误 | |
4059 | No memory to create file system device. | 内存不足 | ROOT | 致命错误 | |
4060 | NVRAM data checksum error. | NVRAM上的数据已损坏。执行NVRAMFORMAT来解决这个问题。 | SYNC | 错误 | |
4061 | Error creating semaphore. | 内部错误。 在NVRAM模块初始化期间未能创建信号量。 | ASYNC | 错误 | |
4062 | Variables indexes exceed the size of NVRAM. | 尝试定义大于NVRAM大小的NVRAM数组时,NVRAMFORMAT命令失败。 | SYNC | 错误 | |
4063 | Value is out of range. | 索引值超出范围。 | SYNC | 错误 | |
4064 | NVRAM does not exist. | 控制器没有NVRAM设备。 | SYNC | 错误 | |
4065 | Unknown error | 在文件系统运行时产生未知的错误代码。 | SYNC | 致命错误 |
Entry Station (5000 through 5999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
5001 | Internal error. Contact technical support. | 内部错误,联系技术支持 | ROOT | 致命错误 | Watchdog |
5002 | Failed to create output pipe: add more memory. | 创建通道失败,添加更多的内存。 | ROOT | 致命错误 | Watchdog |
5003 | Internal error. Contact technical support. | 内部错误,联系技术支持 | ROOT | 致命错误 | Watchdog |
5004 | Failed to create input task: add more memory. | 没有足够的内存来创建任务。 添加更多的内存 | ROOT | 致命错误 | Watchdog |
5005 | Failed to create output task: add more memory. | 没有足够的内存来创建任务。 添加更多的内存 | ROOT | 致命错误 | Watchdog |
5006 | Failed to create semaphore: add more memory. | 无法创建同步信号。 添加更多的内存。 | ROOT | 致命错误 | Watchdog |
5007 | Internal error. Contact technical support. | 内部错误,联系技术支持 | ROOT | 致命错误 | Watchdog |
5008 | Internal error. Contact technical support. | 内部错误,联系技术支持 | ROOT | 致命错误 | Watchdog |
5009 | Serial communication error; Bad BCC. Try again | 无法匹配消息中的控制块字符。 | ASYNC | 错误 | |
5010 | Serial communication error; Bad protocol data. Try again | 无法在消息中检测到新行。 | ASYNC | 错误 | |
5011 | Serial communication error; Bad protocol data format: try again | 无法格式化输出消息。 | ASYNC | 错误 | |
5012 | Failed to write translator input. | RAM驱动器上的内存耗尽。 添加内存或删除REC文件。 | Terminal | 错误 | |
5013 | Internal error. Contact technical support | 内部错误,联系技术支持 | Terminal | 错误 | |
5014 | Internal error. Contact technical support | 内部错误,联系技术支持 | Terminal | 错误 | |
5015 | Failed to create semaphore: add more memory | 无法为活动上下文创建互斥锁。 添加更多的内存。 | ROOT | 致命错误 | Watchdog |
5016 | Internal error. Contact technical support | 内部错误,联系技术支持 | Terminal | 错误 | |
5017 | Internal error. Contact technical support | 内部错误,联系技术支持 | Terminal | 错误 | |
5018 | Internal error. Contact technical support | 内部错误,联系技术支持 | Terminal | 错误 | |
5019 | Internal error. Contact technical support | 内部错误,联系技术支持 | Terminal | 错误 | |
5020 | Failed to create internal file: add more memory. | 无法创建后端输出文件。 添加更多的内存。 | ROOT | 致命错误 | Watchdog |
5021 | Internal error. Contact technical support | 无法创建存储设备。 | ROOT | 致命错误 | Watchdog |
5022 | Virtual input index out of range | 虚拟输入超出范围。参考手册中的SYS.VIN。 | SYNC/ ASYNC | 错误 | Idle Task |
5023 | Virtual output index out of range | 虚拟输出超出范围。 参考参考手册中的SYS.VOUT。 | SYNC/ ASYNC | 错误 | Idle Task |
5024 | Fast data available for axes 1 through 8 only | 快速数据只能在1至8轴上启用。 | SYNC | 错误 | Idle Task |
5025 | Fast data array index out of range. | 为快速数据指定的索引必须在该范围内。 请参考参考手册中的快速数据属性。 | SYNC | 错误 | Idle Task |
5026 | Incorrect fast data check sum. | 快速数据没有被初始化。 主机必须在softMC读取之前写入有效的数据。 | SYNC | 错误 | Idle Task |
5027 | Internal error. Contact technical support | 内部错误,联系技术支持 | SYNC/ ASYNC | 致命错误 | Watchdog |
5028 | Device is blocked for safety reasons. | N/A for MC | N/A | N/A | |
5029 | No such device. | N/A for MC | N/A | N/A | |
5030 | Unknown error | 内部错误,联系技术支持 | Terminal | 致命错误 | Watchdog |
5031 | Internal error. Contact technical support. | 无法创建TCP套接字 | SYNC | 错误 | Idle Task |
5032 | Could not Bind IP address to TCP socket | 无法将IP地址绑定到TCP套接字 | SYNC | 错误 | Idle Task |
5033 | Could not use TCP socket | 无法“侦听“TCP套接字 | SYNC | 错误 | Idle Task |
5034 | Could not accept connection from host | TCP“接收“失败 | SYNC | 错误 | Idle Task |
5035 | Connection lost | 失去连接 | SYNC | Note | None |
5036 | Incorrect parameter value | 不正确的参数值 | SYNC | 错误 | Idle Task |
5037 | Incorrect baud rate value | 不正确的波特率值 | SYNC | 错误 | Idle Task |
5038 | Cannot configure port - incorrect settings | 无法配置端口 - 不正确的设置 | SYNC | 错误 | Idle Task |
5039 | Cannot configure port - incorrect settings | 无法配置端口 - 不正确的设置 | SYNC | 错误 | Idle Task |
5040 | Device handle is already use | 设备句柄已经在使用 | SYNC | 错误 | Idle Task |
5041 | Device handle is not valid - use OPEN command | 设备句柄无效 - 使用OPEN命令 | SYNC | 错误 | Idle Task |
5042 | Device handle is not valid - use OPEN command | 设备句柄无效 - 使用OPEN命令 | SYNC | 错误 | Idle Task |
5043 | Port or file is already open | 端口或文件已经打开 | SYNC | 错误 | Idle Task |
5044 | Could not connect to server | 无法连接到服务器 | SYNC | 错误 | Idle Task |
5045 | Internal error. Contact technical support | 内存不足。 | SYNC | ERR_FAULT_FATAL | Watchdog |
5046 | Cannot execute a command while the Translator is busy | 解释器仍然忙于上一个命令 | SYNC | 错误 | Idle Task |
5047 | Cannot execute a command while the MODBUS is started | MODBUS启动时不能执行命令 | SYNC | 错误 | Idle Task |
5048 | Translation of command in Entry station took too long | 命令的解释需要花费太多的时间。通常会发生在从终端加载很多库。 | Sync | 错误 | |
5049 | Execution of command in Entry station took too long. | 命令的解释需要太多的时间。如果从终端调用的全局库中的函数/过程有无穷循环,通常会发生。使用 USER_SET_ES_LOCK_DETECT_TIMEOUT(timeout,0,0)用户函数来更改默认超时(3000毫秒) | Sync | 错误 | |
5050 | Disk full. | 磁盘已满 | SYNC | 错误 | Idle Task |
5052 | Other connections are still active. | "Reset all" 失败,因为其他电脑/设备连接到另一个入口站。 | SYNC | 错误 |
Loader (6000 through 6999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
6001 | Task already exists. | 加载用户任务或定义新事件时,可能已经存在具有相同名称的进程。来源: Load, OnEvent | SYNC | 错误 | |
6002 | Failed to open program file | 无法读取打开的程序文件,因为它: 1)不存在, 2) 打开的文件太多, 3)没有足够的内存。 如果上电时发生错误,请验证CONFIG.PRG文件是否存在有效数据。 | SYNC | 错误 | |
6003 | Bad element index. | 内部错误。 错误的任务索引作为参数传递。表示系统数据不再可靠。 数据问题来源:任务优先级更新,事件prolog,epilog | SYNC | 致命错误 | |
6004 | Array overflow | 定义太多的事件/任务(任务加载,事件创建)来源 : Load, OnEvent | SYNC | 错误 | |
6005 | Failed to open translator map file. | 内部错误。 无法创建MAP文件。来源: Loader | SYNC | 错误 | |
6006 | Cannot open translator error file. | 内部错误。 无法在根源中创建解释器错误文件: Loader | SYNC | 错误 | |
6007 | Task must be killed first | 如果任务不处于结束或就绪状态,则无法卸载该任务。 | SYNC | 错误 | |
6008 | Task does not exist | 卸载用户任务或事件时,具有指定名称的进程不存在。来源: Unload, EventDelete, Task priority get. | SYNC | 错误 | |
6009 | Failed to run interpreter. | 内部错误。无法调用解释器函数或产生解释器任务。资源问题来源: configuration (root),Load, OnEvent | SYNC/ ROOT | 错误 | |
6010 | Event task already exists | 具有给定名称的事件任务已经存在。 | SYNC | 错误 | |
6011 | Failed to create data segment. | 内部错误。加载任务时无法分配数据段。资源问题来源: Load | SYNC | 错误 | |
6012 | Failed to create code segment. | 内部错误。加载任务时无法分配代码段。资源问题来源: Load | SYNC | 错误 | |
6013 | Invalid semaphore ID. | 内部错误。没有采取ITCB互斥。 指针不良来源:试图更新ITCB数据的任何ITCB例程(Load, Unload, Priority等, OnEvent等.) | SYNC | 致命错误 | |
6014 | Failed to create data stack. | 内部错误。Load或OnEvent尝试时无法创建解释器数据堆栈,资源问题源:Load, OnEvent | SYNC | 错误 | |
6015 | Failed to create function stack. | 内部错误。Load或OnEvent时无法创建解释器函数堆栈。资源问题源:Load, OnEvent | SYNC | 错误 | |
6016 | Failed to create command line code segment. | 内部错误。 无法创建命令行代码段 | ROOT | 致命错误 | |
6017 | Failed allocate memory for event node. | 内部错误。无法为事件节点分配内存。资源问题源:Load, prolog, epilog | SYNC | 错误 | |
6018 | Specified priority does not exist. | 内部错误。 在事件列表中按优先级查找或事件itcb idx失败。问题可能在于数据可靠性,因为有些过程在事件列表中寻找元素。 如果元素不在列表中,任务被中止源: 事件列表管理,优先级修改. 注释:在正常运行时不能发生。 | SYNC/ ASYNC | 致命错误 | |
6019 | Invalid event node. | 内部错误。无效的事件ID。对当前/前一个活动事件的NULL引用。资源问题来源:事件管理,优先级修改。 | SYNC/ ASYNC | 致命错误 | |
6020 | Invalid parent task node. | 内部错误。无效的父任务ID。请求的ITCB idx与事件列表中的不一致。 违反数据完整性。来源: Load, 卸载注释: 在正常运行时不能发生。 | SYNC | 致命错误 | |
6021 | Invalid interpreter pointer. | 内部错误。空指针遇到内部解释器寄存器,来源: event管理器 注释:在正常运行期间不能发生.如果发生错误,则不能处理此任务:解释器的空指针,但ITCB索引仍然存在。 | SYNC/ ASYNC | 致命错误 | |
6022 | Invalid operation code | 内部错误。 加载器处理程序的操作代码无效 | SYNC | 错误 | |
6023 | Invalid event list mutex. | 不能采取事件列表互斥 - 它是无效的)。错误指针来源: event management (prolog, epilog), Load, Unload, OnEvent | SYNC/ ASYNC | 致命错误 | |
6024 | Failed to delete OnError handler | 内部错误。无法删除OnError处理程序(message queue, interpreter) 来源: OnError. | SYNC | 错误 | |
6025 | Invalid OnError message queue | 内部错误。 无效的OnError消息队列ID。错误指针,来源: 将错误消息发送给OnError任务。 | ASYNC | 致命错误 | |
6026 | Reserved task priority | 非法优先级0(为OnError保留)指定源:load,OnEvent,优先级修改。 | SYNC | 错误 | |
6027 | Invalid parent task semaphore | 内部错误。尝试同步执行父任务信号失败时发生。来源: Loader, OnEvent, OnError. | SYNC | 致命错误 | |
6028 | Invalid translator mutex | 内部错误。 当尝试解释互斥失败时会发生。来源: Loader, OnEvent, OnError | SYNC | 致命错误 | |
6029 | Zero file size detected. | 无法加载空文件。 | SYNC | 错误 | |
6030 | Failed to create user task error handler | 内部错误。无法创建默认任务错误处理程序(任务生成,消息队列)。来源: Load | ROOT | 致命错误 | |
6031 | Command given in invalid context. | 命令在无效的情况下给出。 | SYNC | Note | |
6032 | Invalid priority range. | 指定的优先级无效。 | SYNC | Note | |
6033 | Failed to create translator mutex | 内部错误。在启动时创建解释互斥失败时发生。来源: Loader, OnEvent, OnError | ROOT | 致命错误 | |
6034 | Failed to open translator output file. | 内部错误。无法创建永久解释器输出文件。来源: Root | ROOT | 错误 | |
6035 | Failed to open backend output file. | 内部错误。无法创建永久的后端输出。来源: Root | ROOT | 致命错误 | |
6036 | Cannot open translator string file. | 内部错误。无法在根中创建解释器字符串文件。来源: Root | ROOT | 致命错误 | |
6037 | Failed to create mutex. | 内部错误。 无法在ITCB初始化中创建加载程序互斥锁。来源: Root | ROOT | 致命错误 | |
6038 | Failed to create sync semaphore | 内部错误。 Root: 有一个共同的同步信号用于创建任务和事件。 | ROOT | 致命错误 | |
6039 | Failed to retrieve system settings | 内部错误。无法检索系统设置。 | SYNC/ ASYNC | 致命错误 | |
6040 | Failed to create command line files. | 内部错误。无法创建临时命令行文件 (ITCB init). 来源:Root | ROOT | 致命错误 | |
6041 | Cannot create tasks STDIN. | 内部错误。无法创建临时文件。 | ASYNC | 错误 | |
6042 | Cannot open tasks STDIN. | 内部错误。无法从临时任务文件读取。 | ASYNC | 错误 | |
6043 | Cannot delete task STDIN | 内部错误。无法删除任务的输入消息队列。 | SYNC | 错误 | |
6044 | Cannot write to tasks STDIN. | 内部错误。无法写入临时任务文件。 | ASYNC | 错误 | |
6045 | Cannot Reset. Stop the task(s) first. | 如果任务正在运行,则不允许RESET ALL | SYNC | 错误 | |
6046 | File cannot be loaded | 尝试加载config.prg,系统或其他保留文件时会发生此错误。 | SYNC | 错误 | |
6047 | Invalid Translator mutex | 内部错误。无效的互斥体,由于内存损坏或内存有限而导致的内部错误。 | SYNC | 致命错误 | |
6048 | Invalid operation code | 内部错误。无效的操作码。 | SYNC | 致命错误 | |
6049 | Cannot unload library. which is in use. | 由于被其他任务使用而无法卸载库,请首先卸载任务。 | SYNC | 错误 | |
6050 | Unknown error | 内部错误:未知的错误代码。 | SYNC | 致命错误 |
Translator (7000 through 7999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
7001 | Error writing to internal translator output file | 写入到解释器的输出文件时出错。解释器使用RAM磁盘上的临时输出文件。添加更多内存或删除不需要的REC文件。 此错误会中止解释过程。 | SYNC | 故障 | |
7002 | Error writing to internal translator temporary file | 写入解释器的临时文件时出错。解释器使用RAM磁盘上的临时输出文件。添加更多内存或删除不需要的REC文件。 此错误会中止解释过程。 | SYNC | 错误 | |
7003 | Error writing to translator error file | 写入解释器的错误文件时出错。 解释器错误文件存储在RAM磁盘上。添加更多内存或删除不需要的REC文件。此错误会中止解释过程。 | SYNC | 错误 | |
7005 | Errors found during translation | 在解释过程中发现错误。如果在任务中发现解释错误,则在LOAD命令之后将返回此常规消息。如果在CONFIG.PRG文件中发现解释错误,错误严重程度将是致命错误。 | SYNC | 错误 | |
7006 | Variable could not be added to internal symbol table | 内部错误。添加更多的内存。这个错误将中止解释过程。 | SYNC | 错误 | |
7007 | Variable already declared | 一个变量只能被声明一次。 | Translation | 错误 | |
7008 | Subroutine already exists | 子程序已被定义 | Translation | 错误 | |
7009 | Translator temp file could not be opened | 内部错误。解释器的临时文件无法打开。 | SYNC | 错误 | |
7010 | Value out of range | 值超出范围 | SYNC | 错误 | |
7013 | Undefined motion element in command | 您尝试使用的运动元素(轴或组)是未定义的 | Translation | 错误 | |
7014 | Group cannot be added to symbol table | 符号表是内部数据结构。如果信息无法写入,则内存不足,添加更多的内存。 | SYNC | 错误 | |
7015 | Group is already defined | 定义的组已经存在。为该组使用不同的名称。 | Translation | 错误 | |
7016 | Too many axes in Group definition | 组定义中有太多的轴 | SYNC | 错误 | |
7017 | Group cannot be deleted: unload all tasks first | 如果任务将组加载到内存中,则不能删除该组。 | Terminal | 错误 | |
7018 | Internal translation error | 内部错误 | SYNC | 错误 | |
7019 | Variable does not exist | 您正在尝试使用的变量不存在。确保它已被声明。 | Translation | 错误 | |
7020 | No default motion element: use the WITH instruction | 您正在尝试使用一个命令,而没有明确定义一个运动元素,并且一个默认的运动元素没有被WITH指令定义。 | Translation | 错误 | |
7021 | Property valid for Axis only | 该属性仅对轴有效 | Translation | 错误 | |
7022 | Could not change axis name | 内部错误,联系技术支持 | Translation | 错误 | |
7023 | Axis could not be created | 内部错误,联系技术支持 | ROOT | 错误 | |
7024 | Axes not created | 轴未被创建 | ROOT | 错误 | |
7025 | Too many values into vector | 向量中的值太多 | SYNC | 错误 | |
7026 | Too many variable names: simplify the expression | 表达式中允许的最大变量数是20个。 | Translation | 错误 | |
7027 | Instruction given in invalid context | 您尝试使用的命令不能在此上下文中使用。检查参考手册中允许的指令范围。 | Translation | 错误 | |
7028 | PROGRAM must be on the first line | PROGRAM关键字必须在第一行 | SYNC | 错误 | |
7029 | Program symbol table not created | 内部错误。内部数据结构无法创建。添加更多内存或删除不需要的文件。 | SYNC | 错误 | |
7032 | CALL references non-existent SUB | 您正尝试调用不存在的子程序。子程序必须定义。 | Translation | 错误 | |
7034 | Translator Initialization failure | 内部错误。解释器无法初始化。联系技术支持。 | ROOT | 致命错误 | |
7035 | Translator syntax error | 表达式的语法错误,在参考手册中检查正确的语法。 | Translation | 错误 | |
7036 | Program structure error | 该程序必须坚持一个明确的结构。 请参阅用户手册中的任务部分。 | Translation | 错误 | |
7037 | Not enough space for parser stacks | 解析器堆栈空间不足 | SYNC | 错误 | |
7038 | Parser stack overflow | 解析器堆栈溢出 | SYNC | 错误 | |
7039 | Syntax Error | 语法错误 | SYNC | 错误 | |
7040 | Translator out of memory | 解释器内存不足 | SYNC | 错误 | |
7041 | Invalid numbers of drives | 无效的驱动器数量(SERCOS) | SYNC | 错误 | |
7042 | Event definition not allowed in event action | 事件操作中不允许事件定义 | SYNC | 错误 | |
7043 | Event already defined in this program | 事件已经在这个程序中定义 | SYNC | 错误 | |
7044 | Could not create new event symbol. | 无法创建新的事件符号。内部错误 | SYNC | 错误 | |
7045 | Unmatched end of event definition block | 未匹配的事件定义块结束 | SYNC | 错误 | |
7046 | Parameter repetition not allowed | Parameter repetition not allowed | SYNC | 错误 | |
7047 | Undefined event | 未定义的事情 | SYNC | 错误 | |
7048 | Label repeated in the same block | Label在同一个块中重复 | SYNC | 错误 | |
7049 | GOTO references non-exisiting label | GOTO引用不存在的标签 | SYNC | 错误 | |
7050 | String too long ( limit = 80 char) | 字符串太长(80个字符) | SYNC | 错误 | |
7051 | Too many dimension in declaration - maximum is 10. | 声明中的维数过多(最大维数为10) | SYNC | 错误 | |
7052 | Number of dimension does not match declaration | 维数与声明不符 | SYNC | 错误 | |
7053 | Label repeated in the same block | Label在同一个块中重复 | SYNC | 错误 | |
7054 | If block mismatch | If块必须以End If语句结束 | SYNC | 错误 | |
7055 | While block mismatch | While块必须以End While语句结束。 | SYNC | 错误 | |
7056 | For block mismatch | For块必须以Next {variable_name}语句结束。 | SYNC | 错误 | |
7057 | Invalid array index | 无效的数组索引 | SYNC | 错误 | |
7058 | Name already declared as variable, axis, group, or function | 名称已经声明为变量,轴,组或函数 | SYNC | 错误 | |
7059 | Invalid number of coordinates | 在坐标数不匹配的两点之间执行操作时发生此错误。 | SYNC | 错误 | |
7060 | Name of group is invalid | 组名称无效 | SYNC | 错误 | |
7061 | Variable cannot be deleted from the symbol table | 变量不能从符号表中删除 | SYNC | 错误 | |
7063 | Error definition allowed only once in program | 程序中只允许一次错误定义 | SYNC | 错误 | |
7064 | Unmatched end of error definition block | 不相配的错误结束块定义 | SYNC | 错误 | |
7065 | Command not allowed into OnError block | 命令不允许进入OnError块 | SYNC | 错误 | |
7066 | Wrong index type. Index must be of long type | 数组索引的类型必须很长 | SYNC | 错误 | |
7067 | Wrong input type | 错误的输入类型。 | SYNC | 错误 | |
7068 | Index of array must be a constant value | 数组中元素的数量必须用一个常数值声明。 | SYNC | 错误 | |
7069 | Name is a reserved command name or contains invalid symbols | 变量,系统元素,子程序和函数的名称不能与保留的命令名称相同,也不能有包含字母,数字和下划线以外的符号的名称。 | SYNC | 错误 | |
7071 | With block mismatch | With 块必须以End With结束 | SYNC | 错误 | |
7072 | Case Select block mismatch | Select Case块必须以End Select语句结束。 | SYNC | 错误 | |
7073 | Invalid name of motion element | 运动元素的名称无效 | SYNC | 错误 | |
7074 | Property valid for group only | 属性仅适用于组 | SYNC | 错误 | |
7075 | Too many spaces | 命令中的连续空格太多(超过83个) | SYNC | 错误 | |
7076 | Motion element must be an axis | 运动元素必须是轴 | SYNC | 错误 | |
7077 | Motion element must be a group | 运动元素必须是组 | SYNC | 错误 | |
7078 | This property isn't a system property | 该属性不是系统属性 | SYNC | 错误 | |
7079 | Wrong given master type | 不正确的主轴类型(当前定义的3个主轴类型) | SYNC | 错误 | |
7084 | Wrong syntax for joints | 指令不能用于关节轴(J轴)。 | |||
7087 | Dimension mismatch | 尺维数不匹配。在声明期间尝试分配数组时使用。 | 错误 | ||
7089 | User function does not exist | 调用的用户函数不存在或未加载到内存中 | SYNC | 错误 | |
7090 | System camming element does not exist | 系统凸轮元素不存在 | 错误 | ||
7091 | Camming element can only be a system element | 凸轮元素只能是系统元素(不是程序或局部变量) | 错误 | ||
7092 | Wrong input type for the select statement. | 输入类型无效。 | 错误 | ||
7095 | The hex/decimal/bin keywords can only be used in a query command | 十六进制/十进制/ bin关键字只能用于查询命令 | SYNC | 错误 | |
7096 | OnError can be defined only once in a program | OnError只能在程序中定义一次 | SYNC | 错误 | |
7097 | Incorrect print format | 如果打印语句的格式不正确,则会发生此错误。 | SYNC | 错误 | |
7100 | This property is a nodal only property | 该属性是仅有节点的属性 | SYNC | 错误 | |
7102 | Try block mismatch | Try块必须以End Try语句结束。 | SYNC | 错误 | |
7103 | Cannot write a catch-case after the finally-case | 用户不能在finally语句之后编写另一个catch语句。 | SYNC | 错误 | |
7104 | This is a read-only property | 无法分配只读属性。 | SYNC | 错误 | |
7105 | Undefined PLS in command | 在命令中未定义PLS | SYNC | 错误 | |
7106 | PLS could not be added to symbol table | PLS不能被添加到符号表中。这是由于内存故障。 | SYNC | 错误 | |
7107 | PLS is already defined | PLS已经定义。 | SYNC | 错误 | |
7108 | Invalid PLS name | PLS的名称无效。 | SYNC | 错误 | |
7109 | The with block must be closed before entering this block | with块必须关闭。 | SYNC | 错误 | |
7110 | Cannot use locals in this context | 必须在事件条件和事件内部块中使用全局变量和程序变量。 | SYNC | 错误 | |
7111 | The maximal length of the expression must be less than 128 | 表达式的最大长度必须少于128个字符。 | SYNC | 错误 | |
7113 | Expression can only contain strings | 表达式只能包含字符串 | SYNC | 错误 | |
7114 | This function cannot be used as a condition | 此功能不能用作事件条件。 | SYNC | 错误 | |
7115 | The PLS cannot be declared into a program | PLS不能在程序上下文中声明。 | SYNC | 错误 | |
7117 | Missing end onevent statement | 最后一个声明丢失 | SYNC | 错误 | |
7118 | Then statement missing | IF语句中缺少THEN语句 | SYNC | 错误 | |
7119 | Library function is not loaded into memory | 没有加载包含这个函数/子程序的库文件。 | SYNC | 错误 | |
7120 | Cannot record this kind of expression | 不能记录这种表达。 | SYNC | 错误 | |
7121 | This is not a subroutine, but this is a function | 试图使用函数的子程序语法。 | SYNC | 错误 | |
7122 | This is not a function, but this is a subroutine | 试图使用函数语法的子程序。 | SYNC | 错误 | |
7123 | Multiple definition of Else statement | 在单个If块中多出一个Else语句。 | SYNC | 错误 | |
7124 | Multiple definitions of Next statement | 在一个For块中多一个Next语句。 | SYNC | 错误 | |
7125 | Cannot record a vector | 无法记录矢量(点)。 | SYNC | 错误 | |
7126 | Cannot use vector for condition | 在事件定义,流程控制语句等中不能使用矢量(point)作为条件 | SYNC | 错误 | |
7127 | The record file or number of recording points is missing | 记录文件或记录点数缺失。 | SYNC | 错误 | |
7128 | The recorder file is missing | 记录文件丢失 | SYNC | 错误 | |
7129 | Cannot use this operator for strings | 此运算符对字符串无效。例如,你不能乘以字符串。 | SYNC | 错误 | |
7130 | Cannot import library file. Library file must be loaded into memory | 库文件在导入之前必须加载到内存中。 | SYNC | 错误 | |
7131 | Cannot import file which isn’t a library file | 导入命令仅对库文件有效。 | SYNC | 错误 | |
7132 | Input can only contain one string input | 在提示命令中试图使用不是字符串的输入。 | SYNC | 错误 | |
7133 | Catch statement is missing or must be before the statement block | Catch语句丢失或者必须在语句块之前。 | SYNC | 错误 | |
7134 | A filename cannot have more than 8 characters | 文件名不能超过8个字符。 | SYNC | 错误 | |
7135 | Wrong input parameter for the Print command | 打印命令有错误的输入参数。 | SYNC | 错误 | |
7136 | Declaration type is missing | 变量声明语句中缺少变量类型。 | SYNC | Error | |
7137 | Parameter name is a reserved command name or contains invalid symbols | 参数的名称不能与保留的命令名称相同,也不能有包含字母,数字和下划线以外的符号的名称。 | SYNC | 错误 | |
7138 | Cannot use wildcards for this command | 不能对此命令使用通配符(*,?)。 | SYNC | 错误 | |
7139 | Variable passed by reference has another type as in subroutine/function declaration | 变量的类型与相应的子程序/函数参数的类型不匹配。 | SYNC | 错误 | |
7140 | Cannot pass a constant or a complex expression by reference to subroutine/function | 通过引用子例程或函数不能传递常量或复杂表达式(例如:Var1 + Var2)。 | SYNC | 错误 | |
7141 | Cannot use external device for this command | 此命令不能使用外部设备(转储终端) | SYNC | 错误 | |
7142 | Use only long type constants for array size definition | 只有long类型的十进制数和常量可以用于数组大小定义(在数组声明语句中) | SYNC | 错误 | |
7143 | Cannot import a global library | 无法在全局库上应用导入命令。 | SYNC | 错误 | |
7144 | Subroutine already exists in a global library | 子程序或函数的名称已经被赋予了函数的全局子程序 | SYNC | 错误 | |
7145 | The Nodal parameter is inappropriate for this type of motion command | Nodal参数不能用于此类型的运动命令(例如:VelocityFinalTrans不能用于Move命令) | SYNC | 错误 | |
7146 | Expression can only contain points | 表达式只能包含点(例如:指定点类型的组属性) | SYNC | 错误 | |
7147 | Wrong robot-type | 声明或保存命令期间给出了无效的机器人类型 | SYNC | 错误 | |
7148 | Robot-type mismatch | 点变量或点参数之间的机器人类型不匹配 | SYNC | 错误 | |
7149 | Statement cannot contain points | 语句不能包含点(例如:Select Case语句) | SYNC | 错误 | |
7150 | Too many coordinates in a vector | 矢量不能包含超过10个坐标。 | SYNC | 错误 | |
7151 | Cannot use this operator for points | 点不能使用此运算符(例如:逻辑运算符) | SYNC | 错误 | |
7152 | Cannot use vectorial multiplication for points | 点不可以乘以另一点。 | SYNC | 错误 | |
7153 | The variable parameter must be an array | 命令或系统函数的参数是一个数组。 | SYNC | 错误 | |
7154 | Incorrect pls type | 不正确的PLS类型 | SYNC | 错误 | |
7155 | Cannot access a member of a returned-value structure through function call | 无法通过函数调用访问返回值结构的成员,例如: ? StructFunc(…, …)->member1 | SYNC | 错误 | |
7156 | Too many structure members | 结构成员太多 | SYNC | 错误 | |
7157 | Name already given to another member of this structure-type | 名称已经被赋予了相同结构类型的另一个成员。 | SYNC | 错误 | |
7158 | Wrong type for a structure member | 结构成员的错误类型(例如:结构的嵌套)。 | SYNC | 错误 | |
7159 | Name already declared as a structure-type | 结构类型的名称已经被赋予另一个结构类型。 | SYNC | 错误 | |
7160 | Undefined structure-type | 变量声明命令中的未知结构类型或变量类型。 | SYNC | 错误 | |
7161 | Structure-type mismatch | 结构之间的结构类型不匹配。 | SYNC | 错误 | |
7162 | Cannot use this operator for structures | 结构体不能使用该运算符(例如: 所有算术运算符). | SYNC | 错误 | |
7163 | Expression can only contain structures | 在赋值语句中,赋值给结构的表达式也必须是一个结构。 | SYNC | 错误 | |
7164 | Statement cannot contain structures | 语句不能包含结构(例如:For循环索引)。 | SYNC | 错误 | |
7165 | Cannot pass a structure member by reference to a subroutine/function | 不能通过引用子例程/函数传递结构成员 | SYNC | 错误 | |
7166 | Undefined structure member | 结构体成员未在结构类型中定义。 | SYNC | 错误 | |
7167 | A semaphore can only be a system element | 信号量不能有本地或程序范围。 | SYNC | 错误 | |
7168 | Cannot pass an array by value to subroutine/function | 无法将数组按值传递给子程序/函数 | SYNC | 错误 | |
7169 | Use only long type decimal values as error numbers in catch statements | 在catch语句中只能使用Long类型的数字作为错误号。 | SYNC | 错误 | |
7170 | A moving frame can only be a system element | 运动坐标系不能有本地或程序范围。 | SYNC | 错误 | |
7171 | Moving frame element does not exist | 运动坐标系元素不存在 | SYNC | 错误 | |
7172 | A compensation table can only be a system element | 补偿表不能有本地或程序范围。 | SYNC | 错误 | |
7173 | Compensation table does not exist | 补偿表不存在 | SYNC | 错误 | |
7175 | This function has no return value | 无法通过表达式语句调用不返回值的C函数(例如:通过查询)。 | SYNC | 错误 | |
7176 | This function must be used as an expression | C函数返回一个值,因此必须通过表达式语句来调用(例如:通过查询)。 | SYNC | 错误 | |
7178 | Cannot pass an axis or a group by value to subroutine/function | 无法将值或组(“实数”或通用值)传递给子程序/函数 | SYNC | 错误 | |
7180 | Cannot use this command or operation for generic axes and groups | 不能对通用轴和组使用该命令或操作(例如:使用通用轴来声明实际组) | SYNC | 错误 |
Interpreter (8000 through 8999, 22000 through 22999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
8001 | Division by zero | 被零除 | SYNC | 错误 | Idle Task |
8002 | Internal error. Contact technical support. | 解释器堆栈下溢。可能的原因是内存损坏或解释器生成无效的代码。 | SYNC | 故障 | 解释器被阻止执行。 |
8003 | Stack overflow. | 内存耗尽。 | SYNC | 故障 | 解释器被阻止执行。 |
8004 | Internal error. Contact technical support. | 解释器堆栈下溢。 可能的原因是内存损坏或解释器生成无效的代码。 | SYNC | 故障 | 解释器被阻止执行。 |
8005 | Functions stack overflow. | 内存耗尽。 | SYNC | 故障 | 解释器被阻止执行。 |
8006 | Index underflow. | 无效的数组索引值。 | SYNC | 故障 | |
8007 | Index overflow. | 无效的数组索引值。 | SYNC | 故障 | |
8008 | Task not found. | 任务操作失败。请求的任务不存在。 | SYNC | 错误 | |
8009 | Invalid breakpoint location. | 将断点设置在无效的位置。例如: 在注释行或已存在的断点 | SYNC | 错误 | |
8010 | Out of memory. | 内存耗尽。添加更多内存或卸载不必要的任务。 | SYNC | 故障 | |
8011 | Internal error. Contact technical support | 在解释器函数的外部运行时错误。 | SYNC | 错误 | |
8012 | The task has not terminated. | 任务执行尚未终止。如果任务被锁定在某个最终功能中,如MOVE或STOP,则可能发生这种情况。 | SYNC | 错误 | |
8013 | The task is not stopped. | 任务不会停止(空闲)。 | SYNC | 错误 | |
8014 | The task is terminated. | 任务被终止(结束)。 | SYNC | 错误 | |
8015 | Argument for EXP is out of range | EXP参数的取值范围是±7.09782712893383e + 02。 小于下限的值可以使用,但会返回0。 | SYNC | 错误 | |
8016 | llegal mathematical function call | 数学函数的参数无效。 | SYNC | 错误 | |
8017 | Argument for LOG is out of range | LOG函数的参数必须大于零。 | SYNC | 错误 | |
8018 | Negative parameter in SQRT operator | SQRT函数的参数必须大于或等于零。 | SYNC | 错误 | |
8019 | Internal error. Contact technical support. | Loader传递无效的上下文定义。 | SYNC | 致命错误 | |
8020 | Varible does not exist. | 监控的变量不存在。 | SYNC | 错误 | |
8021 | Incorrect number of dimensions. | 监控的维数错误。 | SYNC | 故障 | |
8022 | Task is not running. | 任务已停止(空闲)。 | SYNC | 错误 | |
8023 | Internal error. Contact technical support. | 元素不能从符号表中删除。 | SYNC | 故障 | |
8024 | Task must be killed first. | 任务仍在运行。 它可能被锁定在一些最终功能,如MOVE。 | SYNC | 错误 | |
8025 | Invalid task state for the `StartTask` command. Kill task first. | 任务不会被终止(结束)。它可能被锁定在一些最终功能,如MOVE。 | SYNC | 错误 | |
8026 | Bad memory address. | 试图访问无效的内存地址。 错误可能是由于应用程序中的错误或内存损坏。 | SYNC | 错误 | |
8027 | Bad I/O address. | 试图访问无效的I / O地址。 错误可能是由于应用程序中的错误或内存损坏。 | SYNC | 错误 | |
8028 | Calculation overflow | 计算溢出 | SYNC | 错误 | |
8029 | Underflow | 计算下溢。 | SYNC | 错误 | |
8030 | Internal error. Contact technical support | 无效的互斥ID。 该错误可能是由于内存损坏。 | SYNC | 致命错误 | |
8031 | Internal error. Contact technical support | 无效的互斥ID。 该错误可能是由于内存损坏。 | SYNC | Fatal Fault | |
8032 | Internal error. Contact technical support | 创建信号量时出错。 内存耗尽时发生错误。 | SYNC | Fatal Fault | |
8033 | Internal error. Contact technical support | 代码段具有无效的校验和。原因是内存损坏。 | SYNC | Fatal Fault | |
8034 | Internal error. Contact technical support | 无效令牌COP; 通常是由于内存损坏。 | SYNC | Fatal Fault | |
8035 | Task is interrupted by OnEvent or OnError | 由于任务的中断状态,诸如STEP或STEPOVER等的任务调试命令被禁用。如果被ONERROR或者ONEVENT中断,任务将切换到这个状态。 | SYNC | 错误 | |
8036 | Entry Station output buffer overflow | Entry Station输出缓冲区溢出。错误是由不可操作的主机或用户任务发送太多的消息引起的。 | SYNC | Note | |
8037 | Error loading object file (see file oload.err for more details). | 目标文件无效或包含未解析的符号 | SYNC | Note | |
8038 | The value is out of range | 传递给函数的值超出范围 | SYNC | 错误 | |
8039 | Invalid file name | 无效的文件名 | SYNC | 错误 | |
8040 | Invalid time or date | 输入的时间或日期无效。 | SYNC | 错误 | |
8041 | Nothing to retry. | 运行时错误后,重试命令是适用的。 | SYNC | 错误 | |
8042 | Task is busy. | 任务繁忙;不允许调试。当任务在结束函数中时,会发生这种情况。 | SYNC | 错误 | |
8043 | Element could not be deleted while programs are in memory. | 程序在内存中时无法删除元素。 | SYNC | 故障 | |
8045 | Cannot stop unbreakable task. | 无法停止或调试不可破解的任务 | SYNC | 错误 | |
8046 | "User authorization code is not recognized. Contact technical support | 联系技术支持来验证您的卡的序列号和授权码 | SYNC | 错误 | 没有可用的轴 |
8047 | Invalid Authorization code! Contact technical support | 联系技术支持来验证您的授权码。 | SYNC | 错误 | 没有可用的轴 |
8049 | Invalid type of variable | 错误的变量类型 | SYNC | 错误 | |
8050 | Argument for trigonometric function is out of range | sin(x)或cos(x)的参数的最大值是9.223372036854699e + 18 | SYNC | 错误 | |
8051 | The result of mathematical function overflows | 结果大小大于Double类型的最大值。 | SYNC | 错误 | |
8052 | Internal error. Contact technical support | 元素不能被添加到符号表中。 内部错误 | SYNC | 故障 | |
8053 | No permission: stop the motion first | Motion should be stopped before RESET. | SYNC | Fault | |
8054 | Unrecognized Serial Number. Contact technical support | Contact technical support to validate both Serial Number of your card and Authorisation code | SYNC | Error | No axes available |
8055 | Event/OnError cannot kill a task in which defined. | Event/OnError cannot kill a task in which defined. | SYNC | Error | |
8056 | Wrong file type for this operation | Wrong file type for this operation | SYNC | Error | |
8057 | Invalid time | Invalid time | SYNC | Error | |
8058 | Invalid date | Invalid date | SYNC | Error | |
8059 | Cannot unload a global library while tasks are in memory | Cannot unload a global library while tasks are in memory | SYNC | Error | |
8060 | Global subroutine, function or library could not be deleted from symbol table. | Global subroutine, function or library could not be deleted from symbol table. | SYNC | Error | |
8061 | Subroutine/function contains a call to a non-existent global subroutine/function. | Subroutine/function contains a call to a non-existent global subroutine/function. | SYNC | Error | |
8062 | The file name is too long. A file name should contain no more than 8 characters. | The file name is too long. A file name should contain no more than 8 characters. | SYNC | Error | |
8063 | Error in OnSystemError task | SYNC | Error |
Recorder (9000 through 9999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
9001 | Recorder task cannot be created: add memory. | The recorder task cannot be created. This occurs if there is not enough memory. Add memory or unload tasks that are not necessary. | SYNC | Error | |
9002 | Internal error. Contact technical support. | Internal error. Cannot create recorder mutex. Contact Technical support. | ROOT | Fatal Fault | Watchdog |
9003 | Recorder task already exists. | Only one instance of the recorder is allowed. Issue RECORDCLOSE command and restart the recorder. | SYNC | Error | |
9004 | Invalid record gap value: must be a positive value. | The record gap must be a positive value. | SYNC | Error | |
9005 | Too many record variables. | Up to 6 variables may be specified for recording. | SYNC | Error | |
9006 | Number of points must be a positive value. | Invalid number of record points: number of points must be a positive value | SYNC | Error | |
9007 | Out of memory. | Not enough memory for record operation. Add memory, or unload tasks that are not necessary. This can happen if the RECORD command specifies more data than can be stored in the available free memory. | SYNC | Error | |
9008 | Insufficient disk space to store recorded data. | Record data are stored on the RAM disk when RECORDCLOSE is issued. There is not enough free space on the RAM disk to store the recorded data. Delete files from the RAM disk and then try executing the RECORDCLOSE command again. Adding memory would be the permanent solution for this problem. | SYNC | Error | |
9009 | Internal error. Contact technical support. | Internal error. Disk I/O operation fault. Contact technical support. | SYNC | Error | |
9010 | Failed to store recorded data. | Internal error. Contact technical support. | SYNC | Error | |
9011 | Synchronization error. Recorder did not manage to run within a single cycle. | This error occurs if you attempt to record data that cannot be available immediately to the recorder, and that therefore result in the recorder operation not completing before the end of the system cycle. This can happen, for example, if you try to record drive data that need to be accessed from the service channel. | ASYNC | Error | |
9012 | Internal error. Contact technical support. | Internal error. Creation of Data segment failed. Contact technical support. | SYNC | Error | |
9013 | Internal error. Contact technical support. | Internal error. Creation of System segment failed. Contact technical support. | SYNC | Error | |
9014 | Internal error. Contact technical support. | Internal error. Failed to run Interpreter's agent. Contact technical support. | ASYNC | Error | |
9015 | Internal error. Contact technical support. | Internal error. Invalid Mutex ID. Contact technical support. | SYNC | Fatal Fault | Watchdog |
9016 | Invalid record file extension: must be REC. | Invalid file extension specified for recorder file. Only the REC extension is allowed. | SYNC | Error | |
9017 | Recorder has not been initialized. | The RECORD command has to be successfully executed before the RECORDON, RECORDOFF or RECORDCLOSE commands can be executed. | SYNC | Error | |
9018 | Invalid index of recording variable. | Internal error. Contact technical support. | ASYNC | Error | |
9019 | Recording already has been completed. | The RECORDON and RECORDOFF commands cannot be executed if the recording process is complete. Execute the RECORDCLOSE command to save the recorded data on the RAM disk. | ASYNC | Note | |
9020 | Internal error. Contact technical support. | Internal error. Unknown Recorder state. Contact technical support. | ASYNC | Fatal Fault | Watchdog |
9021 | Unknown error. | Internal error. Unknown error code. Contact technical support. | SYNC | Fatal Fault | Watchdog |
Event Handler (10000 through 10999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
10001 | Event does not exist | Event does not exist | SYNC | Error | |
10002 | Too many events defined | To many events defined | SYNC | Error | |
10003 | Invalid event task ID. | Failed to create an event handling task. This may occur during start up. Contact technical support. | ROOT | Fatal Fault | |
10004 | Invalid mutex ID | Invalid mutex ID. Contact technical support. | SYNC | Fatal Fault | |
10005 | Invalid semaphore ID | Invalid semaphore ID. Contact technical support. | SYNC/ ASYNC | Fatal Fault | |
10006 | Invalid event message queue ID | Invalid message queue ID. Contact technical support. | SYNC/ ASYNC | Fatal Fault | |
10007 | Memory allocation failed | Memory allocation failed. Contact technical support. | SYNC | Error | |
10008 | Invalid operation code | Invalid operation code for operation with internal linked list. Contact technical support. | ASYNC | Fatal Fault | |
10009 | Invalid RTS element | Invalid RTS element otained. It could happen at start up. Contact technical support. | ROOT | Error | |
10010 | Event condition not specified | Event condition not specified. Condition pointer is NULL | SYNC | Fatal Fault | |
10011 | Error checking event condition. | Event condition function call failed | ASYNC | Error | |
10012 | Invalid event handle | Event invalid handle. Contact technical support. | SYNC | Fatal Fault | |
10013 | Invalid interpreter handle | Invalid pointer to interpreter internal registers is used. Contact technical support. | SYNC | Fatal Fault | |
10014 | Failed to delete event entry | Failed to delete event entry | SYNC | Error | |
10015 | Task does not exist | Invalid event task name specified | SYNC | Note | |
10016 | Event action task is active | Event task is active (running at the moment of event deletion) | SYNC | Error | |
10017 | Event action is not specified | Pointer to action code is NULL | SYNC | Fatal Fault | |
10018 | Failed to create event mutex ID | Error creating mutual exclusion semaphore for event handler. Contact technical support. | ROOT | Fatal Fault | |
10019 | Failed to create semaphore ID | Error creating synchronization semaphore for event handler. Contact technical support. | ROOT | Fatal Fault | |
10020 | Failed to create event message queue ID | Error creating message queue for event handler. Contact technical support. | ROOT | Fatal Fault | |
10021 | Invalid scan rate specified | Bad value of scan rate | SYNC | Error | |
10022 | Unknown Error | Unknown Error. Contact technical support. | SYNC | Fatal Fault |
Backend Processor (11000 through 11999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
11001 | COP does not match its number. | Internal error. Contact technical support. | Translation | Error | None |
11002 | Error at line of the table of mnemonics. Token name already exists. | Internal error. Contact technical support. | ROOT | Fatal Fault | Watchdog |
11003 | Symbol table of token mnemonics is full. | The symbol table allocated for token mnemonics is full. There is not enough memory available to create an internal data structure. Add more memory. | ROOT | Fatal Fault | Watchdog |
11004 | Unable to create symbol table for mnemonics. | There is not enough memory available to create an internal data structure. Add more memory. | ROOT | Fatal Fault | Watchdog |
11005 | Unable to create symbol table for user names(labels). | There is not enough memory available to create an internal data structure. Add more memory. | ROOT | Fatal Fault | Watchdog |
11006 | Unable to delete symbol table for mnemonics. | Internal error. Contact technical support. | ROOT | Fatal Fault | Watchdog |
11007 | Unable to delete symbol table for user names(labels). | Internal error. Contact technical support. | ROOT | Fatal Fault | Watchdog |
11008 | Name already defined. | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11009 | Symbol table of user names(labels) is full. | Not enough memory for translation. Add memory, or unload tasks that are not necessary. | SYNC | Error | Idle Task |
11010 | Token mnemonic is invalid (unknown). | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11011 | Number of parameters at line does not match the token | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11012 | This token data type is not supported yet. | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11013 | Symbol or label has not been defined. | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11014 | Calculated length of the token does not match its predefined value. | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11016 | Out of disk space. | Out of disk space while attempting to write temporary file to RAM drive. Add more memory or delete REC files. | SYNC | Error | Idle Task |
11017 | Cannot find library map | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11018 | Library Map file is invalid | Internal error. Contact technical support. | SYNC | Error | Idle Task |
11019 | Invalid Error code | Internal error. Contact technical support. | SYNC | Fatal Fault | Watchdog |
SERCOS (12000 through 12999)
SERCOS is not supported in EtherCAT system.
Contact Servotronix for SERCOS solutions.
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
12001 | Service Channel not open | Drive indicates it cannot open the service channel. Contact technical support. | SYNC | Error | |
12002 | MDT telegram processing overrun | Overlap between reference generation and transmission. Try using a higher baud rate, longer cycle time, and reducing the amount of cyclic data. | ASYNC | Error | |
12003 | Interrupt Service Routine Overlap: use longer cycle time. | ISR's duration is too long (more than one communication cycle). Try using a higher baud rate, longer cycle time, and reducing the amount of cyclic data. | SYNC | Error | |
12004 | Service channel timeout waiting for drive | Timeout during service channel transmission. Change the communication phase to 0 and try using longer cycle time. If error persists, call technical support. | SYNC | Error | |
12005 | Service channel timeout while drive is busy | Timeout during service channel transmission. Change the communication phase to 0, bring the ring up and try again. Another solution would be using longer cycle time. If error persists, call technical support | SYNC | Error | |
12006 | Undefined error number | Undefined error code. Internal error. Contact technical support. | SYNC | Fatal Fault | Watchdog |
12007 | Axis cannot be enabled: check C1D and Remote Enable | This error occurs if the softMC times out while trying to enable the drive. A drive cannot be enabled if the drive is reporting a C1D error or if the drive's hardware enable signal is Off. You can check this by querying IDN P15 in the CD drive. | SYNC | Error | |
12008 | Axis cannot be disabled | This error occurs if the softMC times out while trying to disable the drive. Refer to IDN207 in the drive or contact technical support. | SYNC | Error | Bring the ring down to CP0 |
12009 | Invalid access to closing the Service Channel | Internal error. Contact technical support. | SYNC | Error | |
12010 | Axis in group cannot be enabled: check C1D and Remote Enable | This error occurs if the softMC times out while trying to enable the drive. A drive cannot be enabled if the drive is reporting a C1D error or if the drive's hardware enable signal is Off. You can check this by querying IDN P15 in the CD drive. | SYNC | Error | |
12011 | Axis in group cannot be disabled | This error occurs if the softMC times out while trying to disable the drive. Refer to IDN207 in the drive or contact technical support. | SYNC | Error | Bring the ring down to CP0 |
12012 | Drive not ready for power up | A drive cannot be enabled if the drive is reporting a C1D error or if the drive's hardware enable signal is Off. | SYNC | Error | |
12013 | Drive reports fault in C1D: read IDN 95 to get the error | When a drive fault occurs, the drive decelerates to a stop and releases torque. The C1D status bit is set and the corresponding fault bits are set in IDN 11. Faults are reset using IDN 99. | SYNC/ASYNC | Error | Drive is disabled |
12014 | Telegram data corrupted | Telegram data received from the drive is invalid. Contact technical support. | ASYNC | Note | |
12015 | One of the programming error flags is active | One of the SERCOS programming times was incorrect. Contact technical support. | ASYNC | Error | |
12016 | Invalid drive address | There may be a conflict between the axis DriveAddress and Simulated properties. If an axis is simulated, the drive address must be set to 0. If the axis is real, the simulated property must be set to 0 (Off). Check if exists on ring drive in this address. | SYNC | Error | |
12017 | No IDN: IDN being accessed is not defined in the drive | The IDN number being used is not defined in the drive. Check the drive manual. | SYNC | Error | |
12022 | Bad handle-function index | Internal error. Contact technical support. | SYNC | Error | |
12023 | Service channel data not initialized | Internal error. Contact technical support | SYNC | Error | |
12024 | Wrong bus bus operation mode | The command requires EtherCAT/CAN bus to be in OP state or phase #4 in case of SERCOS bus. | SYNC | Error | |
12025 | Invalid access to the element 1 | Element 1 of the IDN holds the IDN number. Access to this element is read-only. | SYNC | Error | |
12026 | Wrong ring number | Internal error. Contact technical support. | SYNC | Fatal Fault | Watchdog |
12027 | Too many drives for this ring. | Internal error. Contact technical support. | SYNC | Error | |
12028 | Wrong AT number. | Internal error. Contact technical support. | SYNC | Error | |
12029 | Not enough memory. | Not enough memory to allocate internal data structures. Add memory or unload unnecessary tasks. | SYNC | Error | |
12030 | SERCOS ring is broken: check the SERCOS wiring | At the transition from Phase 0 to Phase 1, the softMC checks whether the ring is closed by transmitting data and then verifying that it receives this data. This error occurs if the ring is open. In some cases, an invalid baud rate setting causes this error. | SYNC | Error | |
12031 | No memory to maintain Service container | Try to use less drives on the ring or contact technical support. | SYNC | Error | |
12032 | Service transfer not ready | Internal error. Contact technical support. | SYNC | Error | |
12033 | No name | Element 2 of drive's IDN table should contain the name of the IDN. The IDN has not been assigned a name. | SYNC | Error | |
12034 | Name transmission too short | Drive expects more information for the IDN name. | SYNC | Error | |
12035 | Name transmission too long. | Drive expects less information for the IDN name. | SYNC | Error | |
12036 | Name cannot be changed | The name of the IDN may not be changed. | SYNC | Error | |
12037 | Name is write-protected at this time. | The name of the IDN cannot be changed in the current communication phase. | SYNC | Error | |
12038 | Service transfer data unavailable | Internal error. Contact technical support. | SYNC | Error | |
12039 | Initialization error | An error occurred during Initialization of the SERCOS module. | ROOT | Fatal Fault | Watchdog |
12040 | Service channel hand-shake time-out. | Service channel hand-shake time-out. Drive does not acknowledge service transmission. | SYNC | Error | |
12041 | Missing telegram(s): communication interrupted | Controller did not receive telegram from the drive(s) in communications phase 2. This error is generated when a drive stops functioning, or when there is a timing problem on the SERCOS bus. | SYNC | Error | Bring the ring down to CP0 |
12042 | DPRAM overflow. Two many drives for this ring | Not enough DPRAM space to allocate data structures. Try configure less cyclic data in telegrams (IDN’s 16 and 24) or use less drives. | SYNC | Error | |
12043 | Data element too long | This error occurs when drive cannot accept long data array for the particular IDN. | SYNC | Error | |
12044 | Error calculating T2: increase cycle time or baud rate | Error calculating MDT starting time. There is an expected time overlap between the AT's and the MDT. Either increase the cycle time, increase baud rate, simplify the telegrams, or decrease the number of drives. | SYNC | Error | |
12045 | Error calculating T3 | Error calculating command value valid time. The time calculated for T3 exceeds the SERCOS cycle time. This may be due to different drives being on the ring, with different processing requirements. | SYNC | Error | |
12046 | Error calculating T4 | Error calculating feedback acquisition capture point. The time calculated for T4 exceeds the SERCOS cycle time. This may be due to different drives being on the ring, with different processing requirements. | SYNC | Error | |
12047 | Error calculating TEND | Error calculating end of transmission time. The time calculated exceeds the SERCOS cycle time. Increase the cycle time, increase baud rate, simplify the telegrams, or decrease the number of drives. | SYNC | Error | |
12048 | No service data | Internal error. Contact technical support. | SYNC | Error | |
12050 | Attribute transmission too short | Internal error. Contact technical support. | SYNC | Error | |
12051 | Attribute transmission too long | Internal error. Contact technical support. | SYNC | Error | |
12052 | Attribute cannot be changed | Element 3 of the IDN is write protected. Attribute cannot be changed. | SYNC | Error | |
12053 | Attribute is write protected at this time | Cannot change the attribute in the current communication phase. | SYNC | Error | |
12054 | Service transfer not error-free | Internal error. Contact technical support | SYNC | Error | |
12055 | Missing telegram(s): communication interrupted | Controller did not receive telegram from the drive(s). This error is generated if a drive stops functioning, or if there is a timing problem on the SERCOS bus. Communication interrupted due to missing telegram(s) in communication phase 3 or communication phase 4. | ASYNC | Error | Bring the ring down to CP0 |
12056 | Wrong IDN number: the IDN must be defined | One of the IDN’s wasn’t defined or there are no free place for this IDN. If error persists, call technical support. | SYNC | Error | |
12057 | Wrong telegram type specified in IDN15 | Data telegram type number is out of range (0..7). | SYNC | Error | |
12058 | Wrong element number: must be in range 1..7 | An IDN has 7 elements, each storing a different attribute of the IDN. Element number 7 is used to store the value of the IDN, and it is the element most frequently used. The element range is 1 to 7. | SYNC | Error | |
12059 | Communication phase 3 transition check failed | Execution of CP2 to CP3 transition procedure (IDN127) failed. Check IDN 21 to obtain a list of invalid operation data. | SYNC | Error | |
12060 | Communication phase 4 transition check failed | Execution of CP3 to CP4 transition procedure IDN#00128 failed. Check IDN 22 to obtain a list of invalid operation data. | SYNC | Error | |
12061 | Error creating MutEx for the Service channel task | Internal error. Contact technical support | SYNC | Fatal Fault | Watchdog |
12062 | Cannot create MsgQ to provide service transmission | Internal error. Contact technical support | SYNC | Fatal Fault | Watchdog |
12063 | Error creating Service event semaphore | Internal error. Contact technical support. | SYNC | Fatal Fault | Watchdog |
12064 | Cannot pass communication phase 1: drive address(es) not declared. | Drive addresses must be declared explicitly (<axis>.DRIVEADDRESS) or implicitly (SERCOS.SCAN) for the ring to be scanned. The SERCOS.SCAN property can be used for automatic scanning. | SYNC/ ASYNC | Error | |
12065 | No units | Element 4 of drive's IDN table should contain the units of the IDN. The IDN has not been assigned units | SYNC | Error | |
12066 | Unit transmission too short. | Internal error. Contact technical support. | SYNC | Error | |
12067 | Unit transmission too long | Internal error. Contact technical support. | SYNC | Error | |
12068 | Unit cannot be changed | Element 4 of the IDN is write-protected. Units cannot be changed | SYNC | Error | |
12069 | Unit is write protected at this time | The units of the IDN cannot be changed in the current communication phase. | SYNC | Error | |
12070 | Incorrect value or value out of range | Invalid value assignment at this statement. See the entry in the reference manual for this command. | SYNC | Error | |
12071 | Cannot proceed to communication phase 1: check baud rate and drive addresses | This error occurs if the system cannot be advanced to communication phase 1. This can happen if the baud rates in the drives and controller are not matched. It can also happen if there is a conflict between the DRIVEADDRESS property and the SIMULATED property. If an axis is simulated, the drive address must be set to 0. If the axis is real, the simulated property must be set to 0 (Off). | SYNC/ASYNC | Error | |
12072 | The drive address has already been assigned to another axis | Each axis must be assigned a unique drive address. There cannot be multiple drives with the same address. | SYNC | Error | |
12073 | Not valid for simulated axis | Cannot perform this command for simulated axis | SYNC | Error | |
12074 | Invalid request for service channel transmission | Internal error. Contact technical support. | SYNC | Fatal Fault | Watchdog |
12075 | Invalid data pointer | Internal error. Contact technical support. | SYNC | Error | |
12076 | Unknown operation data type for this command | Internal error. Contact technical support. | SYNC | Error | |
12077 | Cannot redefine default IDN | Internal error. Contact technical support. | SYNC | Error | |
12078 | List of IDNs defined as cyclic data is too long | The length of the IDN list declared by an user is too long. Try use simpler telegrams or contact technical support. | SYNC | Error | |
12079 | Cannot enable axis: System Enable property is off | A drive cannot be enabled if the System.Enable property is OFF. Set this property to on to allow the drives to be enabled, and then enable the axis. | SYNC | Error | |
12081 | No minimum value | Element 4 of drive's IDN table should contain the units of the IDN. The IDN has not been assigned a minimum value. | SYNC | Error | |
12082 | Minimum value transmission too short. | Internal error. Contact technical support. | SYNC | Error | |
12083 | Minimum value transmission too long | Internal error. Contact technical support. | SYNC | Error | |
12084 | Minimum value cannot be changed. | Element 5 of the IDN is write-protected. Minimum value cannot be changed. | SYNC | Error | |
12085 | Minimum value is write protected at this time | The minimum value of the IDN cannot be changed in the current communication phase. | SYNC | Error | |
12086 | Error of synchronization with the drive | Synchronization between SERCOS driver and motion module lost | ASYNC | Note | |
12087 | Return back to CP0 due to a missed telegram | Telegram missed in CP1 or CP2 | SYNC | Error | |
12088 | An error occurred on the drive | Drive reports about Class 1 Diagnostic fault. Check IDN 95 to get the diagnostic message. | ASYNC | Error | Drive is disabled |
12089 | Drive does not respond | This message is generated in CP1 when the master scans drive addresses. Check correspondence <axis>.DRIVEADDRESS property with the actual drive addresses. | ASYNC | Note | |
12090 | Drive telegram error | Telegram received from the drive is not error-free. This message may be followed by the missing telegram error. | ASYNC | Note | |
12091 | The IDN being declared in cyclic data is not defined | Check in drive IDN documentation if this IDN exists in drive. | SYNC | Error | |
12092 | Wrong operation data length for IDN | Wrong operation data length was specified in definition of the IDN. | SYNC | Error | |
12093 | Receiving telegram over-run | One of the SERCOS programming times was incorrect. Contact technical support. | ASYNC | Error | |
12094 | Telegram processing cannot follow receiving rate | One of the SERCOS programming times was incorrect. Contact technical support. | ASYNC | Error | |
12097 | No maximum value. | Element 6 of drive's IDN table should contain the units of the IDN. The IDN has not been assigned a maximum value. | SYNC | Error | |
12098 | Maximum value transmission too short. | Internal error. Contact technical support. | SYNC | Error | |
12099 | Maximum value transmission too long | Internal error. Contact technical support. | SYNC | Error | |
12100 | Maximum value cannot be changed. | Element 6 of the IDN is write protected. Maximum value cannot be changed. | SYNC | Error | |
12101 | Maximum value is write protected at this time | The maximum value of the IDN cannot be changed in the current communication phase. | SYNC | Error | |
12114 | Operation data transmission too short. | Drive expects more information for the IDN data. Refer to the drive’s IDN manual. | SYNC | Error | |
12115 | Operation data transmission too long. | Drive expects less information for the IDN data. Refer to the drive’s IDN manual. | SYNC | Error | |
12116 | Operation data cannot be changed | The operation data of the IDN may not be changed. | SYNC | Error | |
12117 | Operation data is write protected at this time. | The operation data of the IDN cannot be changed in the current communication phase. Refer to the drive’s IDN manual. | SYNC | Error | |
12118 | Operation data are smaller than the minimum value. | Operation data of the IDN should be equal or greater than that defined in Element 5. | SYNC | Error | |
12119 | Operation data are greater than the maximum value. | Operation data of the IDN should be equal or less than that defined in Element 6. | SYNC | Error | |
12120 | Invalid data (e.g., invalid bit combination for this IDN). | The drive cannot accept the value written. Refer to description of the IDN entry in the Drive’s IDN manual. | SYNC | Error | |
12121 | Operation data are password write-protected | Operation data are password write-protected. Refer to drive’s manual to get more information on IDN password protection. | SYNC | Error | |
12122 | IDN is configured in the MDT or AT, therefore writing to it over the service channel not permitted | Operation data is write-protected at this time, since it is cyclically configured. | SYNC | Error | |
12123 | Invalid indirect addressing: (eg. data container, list handling) | Internal error. Contact technical support. | SYNC | Error | |
12124 | Operation data is write protected at this time, due to other adjustments (e.g. parameter, operating mode, drive release, drive etc.). | Refer to description of the IDN entry in the Drive’s IDN manual. | SYNC | Error | |
12128 | Procedure already activated | Check IDNstate of this procedure. Refer to description of the IDN procedure entry in the Drive’s IDN manual for check limitation of this procedure | SYNC | Error | |
12129 | Procedure not interruptible | This procedure can’t be interrupted. Refer to description of the IDN procedure entry in the Drive’s IDN manual for check limitation of this procedure | SYNC | Error | |
12130 | Procedure cannot be executed at this time (e.g. procedure in this phase cannot be activated) | Refer to description of the IDN procedure entry in the Drive’s IDN manual for check limitation of this procedure | SYNC | Error | |
12131 | Procedure cannot be executed (invalid or false parameters) | The parameter of this procedure is invalid. Refer to description of the IDN procedure entry in the Drive’s IDN manual. | SYNC | Error |
ROBOT (13000 through 13999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
13102 | Additive torque value is over threshold limit. | SYNC | Error | ||
13103 | Additive torque value is over threshold limit when motion is stopped: drive disabled. | ASYNC | Error | ||
13104 | X coordinate beyond XMAX limit. | SYNC/ASYNC | Error | ||
13105 | X coordinate beyond XMIN limit. | SYNC/ASYNC | Error | ||
13106 | Y coordinate beyond YMAX limit. | SYNC/ASYNC | Error | ||
13107 | Y coordinate beyond YMIN limit. | SYNC/ASYNC | Error | ||
13108 | Z coordinate beyond ZMAX limit. | SYNC/ASYNC | Error | ||
13109 | Z coordinate beyond ZMIN limit. | SYNC/ASYNC | Error | ||
13110 | Chair Side Engine Kinematics: alpha exceeds ALPHAMAX. | SYNC/ASYNC | Error | ||
13111 | Chair Side Engine Kinematics: carriages 1 & 2 collision. | SYNC/ASYNC | Error | ||
13112 | Chair Side Engine Kinematics: carriages 1 & 2 too far from each other. | SYNC/ASYNC | Error | ||
13113 | Chair Side Engine Kinematics: carriages 2 & 3 collision. | SYNC/ASYNC | Error | ||
13114 | Chair Side Engine Kinematics: Z coordinate contradicts mechanical model. | SYNC/ASYNC | Error | ||
13115 | Chair Side Engine Kinematics: B angle contradicts mechanical model. | SYNC/ASYNC | Error | ||
13116 | Direct Kinematics error on feedback position. | ASYNC | Error | ||
13117 | Robot too slow or Moving Frame too fast. | ASYNC | Error | ||
13118 | Unable to smooth out the given path [iterations], try to reduce velocity or change the path. | SYNC | Error | ||
13119 | Too many points for smoothing, either there are too many points or the velocity is too slow. | SYNC | Error | ||
13120 | In Smoothing: Wrong position of the slow-down/speed-up point. | SYNC | Error | ||
13121 | Unable to smooth out the given path [offset], try to reduce velocity or change the path. | SYNC | Error | ||
13123 | Invalid AxisType settings. AxisType of robot axes should comply to its kinematics model. | SYNC | Error | ||
13128 | Unable to smooth out the given path [shrinking], try to reduce velocity or change the path. | SYNC | Error | ||
13129 | Traverse Arm: Y Coordinate exceeds link's length. | SYNC | Error | ||
13130 | DELTA: Internal singularity. | SYNC/ASYNC | Error | ||
13131 | Parts of the given trajectory includes points not reachable by the robot. | SYNC | Error | ||
13132 | Singularity margin - no Cartesian interpolation allowed. | SYNC | Error | ||
13133 | ModelEnable flag automatic reset. | SYNC | Error | ||
13134 | ModelEnable flag is zero, no motion allowed. | SYNC | Error | ||
13142 | X coordinate beyond WORKPIECE.XMAX limit. | SYNC/ASYNC | Error | ||
13143 | X coordinate beyond WORKPIECE.XMIN limit. | SYNC/ASYNC | Error | ||
13144 | Y coordinate beyond WORKPIECE.YMAX limit. | SYNC/ASYNC | Error | ||
13145 | Y coordinate beyond WORKPIECE.YMIN limit. | SYNC/ASYNC | Error | ||
13146 | Z coordinate beyond WORKPIECE.ZMAX limit. | SYNC/ASYNC | Error | ||
13147 | Z coordinate beyond WORKPIECE.ZMIN limit. | SYNC/ASYNC | Error | ||
13148 | X coordinate beyond MACHINETABLE.XMAX limit. | SYNC/ASYNC | Error | ||
13149 | X coordinate beyond MACHINETABLE.XMIN limit. | SYNC/ASYNC | Error | ||
13150 | Y coordinate beyond MACHINETABLE.YMAX limit. | SYNC/ASYNC | Error | ||
13151 | Y coordinate beyond MACHINETABLE.YMIN limit. | SYNC/ASYNC | Error | ||
13152 | Z coordinate beyond MACHINETABLE.ZMAX limit. | SYNC/ASYNC | Error | ||
13153 | Z coordinate beyond MACHINETABLE.ZMIN limit. | SYNC/ASYNC | Error | ||
13154 | X coordinate beyond BASE.XMAX limit. | SYNC/ASYNC | Error | ||
13155 | X coordinate beyond BASE.XMIN limit. | SYNC/ASYNC | Error | ||
13156 | Y coordinate beyond BASE.YMAX limit. | SYNC/ASYNC | Error | ||
13157 | Y coordinate beyond BASE.YMIN limit. | SYNC/ASYNC | Error | ||
13158 | Z coordinate beyond BASE.ZMAX limit. | SYNC/ASYNC | Error | ||
13159 | Z coordinate beyond BASE.ZMIN limit. | SYNC/ASYNC | Error | ||
13160 | X coordinate beyond TOOL.XMAX limit. | SYNC/ASYNC | Error | ||
13161 | X coordinate beyond TOOL.XMIN limit. | SYNC/ASYNC | Error | ||
13162 | Y coordinate beyond TOOL.YMAX limit. | SYNC/ASYNC | Error | ||
13163 | Y coordinate beyond TOOL.YMIN limit. | SYNC/ASYNC | Error | ||
13164 | Z coordinate beyond TOOL.ZMAX limit. | SYNC/ASYNC | Error | ||
13165 | Z coordinate beyond TOOL.ZMIN limit. | SYNC/ASYNC | Error |
Root Process (16000 through 16999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
16001 | Root : softMC Hardware | softMC Hardware Error | ASYNC | Fatal Fault | Watchdog |
16002 | Root : Entry Station(s) | Entry Station(s) Error | ASYNC | Fatal Fault | |
16003 | Root : System Clock | System Clock Error | ASYNC | Fatal Fault | |
16004 | Root : Translator | Translator Error | ASYNC | Fatal Fault | |
16005 | Root : Back-End | Back-End Error | ASYNC | Fatal Fault | |
16006 | Root : RAM Drive | RAM Drive Error | ASYNC | Fatal Fault | |
16007 | Root : Flash File System | Flash File System Error | ASYNC | Fatal Fault | |
16008 | Root : FLASH and File system | FLASH and File system Error | ASYNC | Fatal Fault | |
16009 | Root : Error handler | Error handler Error | ASYNC | Fatal Fault | |
16010 | Root : Task Control Block | Task Control Block Error | ASYNC | Fatal Fault | |
16011 | Root : Real Time Scheduler | Real Time Scheduler Error | ASYNC | Fatal Fault | |
16011 | Root : Real Time Scheduler | Real Time Scheduler Error | ASYNC | Fatal Fault | |
16012 | Root : Built-in Diagnostic | Built-in Diagnostic Error | ASYNC | Fatal Fault | |
16013 | Root : SERCOS Communications | SERCOS Communications Error | ASYNC | Fatal Fault | |
16014 | Root : Motion Module | Motion Module Error | ASYNC | Fatal Fault | |
16015 | Root : System Configuration | System Configuration Error | ASYNC | Fatal Fault | |
16016 | Root : User configuration file | User configuration file Error | ASYNC | Fatal Fault | |
16017 | Root : ITCB Setup | ITCB Setup Error | ASYNC | Fatal Fault | |
16018 | Root : Event Handler | Event Handler Error | ASYNC | Fatal Fault | |
16019 | Root : Recorder | Recorder Error | ASYNC | Fatal Fault | |
16020 | Root : Fault Handler | Fault Handler Error | ASYNC | Fatal Fault | |
16022 | Root : I/O Module | I/O Module Error | ASYNC | Fatal Fault | |
16023 | Root : Serial Number Specification | Serial Number Specification Error | ASYNC | error | |
16024 | Root : User Authorization Code Specification File | User Authorization Code Specification File Error | ASYNC | Error | |
16025 | Root : Hardware power-up tests | Hardware power-up tests Error | ASYNC | Fatal Fault | Watchdog |
16026 | Config.prg failed | Config.prg failed. See error history and retrieve trn.err for more details. | ASYNC | Fatal Fault | Watchdog |
16032 | Autoexec.prg failed | Autoexec.prg failed. See error history and retrieve trn.err for more details. | ASYNC | Error | |
16036 | Root : Current running firmware version is the backup version not last updated version. | Current running firmware version is the backup version not last updated version. | ASYNC | Note | |
16037 | Root : DPRAM Test | DPRAM Test Error | ASYNC | Fatal Fault | |
16038 | Root : SERCON DPRAM Test | SERCON DPRAM Test Error | ASYNC | Fatal Fault | |
16039 | Root : Microchip PIC | Microchip PIC Error | ASYNC | Fatal Fault | |
16040 | Root : Unknown error code. | Unknown error code. | ASYNC | Error | Watchdog |
Motion bus (19000 through 19009)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
19001 | Drive cannot be enabled. | Drive cannot be enabled. Drive got fault or hardware enable or STO chain is open. | SYNC | Error | |
19002 | Drive cannot be disabled. | Drive cannot be disable. System could not disable drive. | SYNC | Error | |
19003 | Communication error. | Not used. | SYNC | Error | |
19004 | Drive reports error. | Drive got fault: SERCOS: look into C1D, EtherCAT/CAN: look into SDO 0x603F | SYNC | Error | |
19005 | Cannot enable axis: System Enable property is off. | Sys.Enable is 0 | SYNC | Error | |
19006 | Drive reports warning. | Drive has warning. | SYNC | Error | |
19007 | Bus fault. | Most probable that cable is disconnected. | SYNC | Error | |
19008 | Invalid value. | Provided value for parameter of flag is not valid. | SYNC | Error | |
19009 | Property value can not be changed while drive is enabled. | Cannot change while enabled. | SYNC | Error | |
19010 | Duplicated address. | Attempt to assign the same physical address to more than one axis. | SYNC | Error | |
19011 | Node is not a motor. | Attempt to assign a physical address of I/O module to axis.driveaddress property. | SYNC | Error | |
19012 | Cannot enable axis/group. | Cannot enable axis or group of axes. Usually occurs due to missing/inverted drive's hardware enable signal, or one of axis has wrong or zero drive address axis.dadd property. | SYNC | Error | |
19013 | Cannot clear fault on drive. | Fault on drive persists. | SYNC | Error |
User Error codes (20000 through 20999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
20xxx | Custom error code range | Defined in user application - programs or libraries. | SYNC | Error | Idle task |
I/O Module (21000 through 21999)
Number | Message | Description | Type | Severity | Action |
---|---|---|---|---|---|
21001 | Cannot create semaphore. | Internal error. No resources left to create a semaphore | SYNC | Error | |
21002 | Invalid memory address. | Incorrect memory address. | SYNC | Error | |
21003 | Invalid I/O address. | Incorrect I/O space address. | SYNC | Error | |
21004 | Invalid address. | Incorrect device address address. | SYNC | Error | |
21005 | Invalid bit number. | Incorrect bit number - no device registered for this bit number. | SYNC | Error | |
21006 | Invalid range. | Incorrect bit range - no device registered for this bit number or bit range. | SYNC | Error | |
21007 | Invalid port index. | Incorrect I/O space address. | SYNC | Error | |
21008 | Cannot delete semaphore. | Internal error. | SYNC | Error | |
21009 | Invalid value. | Error code is not in use. | SYNC | Error | |
21010 | PLS toggling time exceeded cycle time. | Internal error. | SYNC | Error | |
21011 | Too many PLS toggling requested or cycle source is not routed to PLS module. | Too many output transition per cycle time. | SYNC | Error | |
21012 | Invalid error code. | Error code is not in use. | SYNC | Error | |
21013 | Cannot create PLS task. | Internal error. No resources left to create a task | SYNC | Error | |
21014 | PDO Parameters Error: make sure Digital IOs PDO entries are mapped in the drive. | Cannot write PDO to the device - drive or IO module | SYNC | Error | |
21015 | Slave Address Error. | Incorrect device address | SYNC | Error |