## MLB Error Information

An MLB error is generated by an MLB command that cannot be processed. It can occur when a part program is running, when a part is being measured, or when a part program is being edited within QuickTeach or MaxLite. MLB errors do not include errors detected by Visual Basic. Refer to the VB help for assistance with VB errors.

Some examples of MLB errors are:

1. A resource is not available, such as MLB-090 for 'DCC not available', or RCU-050 for 'RCU not available'.

2. Command syntax is invalid, such as MLB-020 for 'improper parameter', or MLB-010 for 'unidentified function command string'.

3. CMM cannot complete the motion, such as MLB-168 for 'unexpected touch', or MLB-169 for 'unexpected end-of-travel'.

4. Data cannot be processed, such as MLB-038 for 'cannot intersect line parallel with cylinder axis ', or MLB-070 for 'reference not saved'.

MLB errors are displayed at the PC, typically in a dialog box.

The MLB error codes are listed in this table:

MLB-001 | MLB-026 | MLB-062 | MLB-114 | MLB-168
MLB-003 | MLB-027 | MLB-063 | MLB-115 | MLB-169
MLB-004 | MLB-028 | MLB-064 | MLB-116 | MLB-170
MLB-005 | MLB-029 | MLB-070 | MLB-120 | MLB-173
MLB-006 | MLB-030 | MLB-071 | MLB-130 | MLB-190
MLB-007 | MLB-031 | MLB-072 | MLB-131 | MLB-191
MLB-010 | MLB-032 | MLB-080 | MLB-132 | MLB-505
MLB-011 | MLB-033 | MLB-088 | MLB-140 |
MLB-012 | MLB-034 | MLB-089 | MLB-150 |
MLB-013 | MLB-035 | MLB-090 | MLB-151 |
MLB-014 | MLB-036 | MLB-091 | MLB-152 |
MLB-015 | MLB-037 | MLB-092 | MLB-153 |
MLB-016 | MLB-038 | MLB-093 | MLB-154 |
MLB-017 | MLB-040 | MLB-094 | MLB-155 |
MLB-018 | MLB-041 | MLB-095 | MLB-156 |
MLB-019 | MLB-042 | MLB-096 | MLB-157 |
MLB-020 | MLB-043 | MLB-100 | MLB-158 |
MLB-021 | MLB-044 | MLB-101 | MLB-160 |
MLB-022 | MLB-045 | MLB-110 | MLB-161 |
MLB-023 | MLB-050 | MLB-111 | MLB-162 |
MLB-024 | MLB-060 | MLB-112 | MLB-164 |
MLB-025 | MLB-061 | MLB-113 | MLB-166 |