NOTE: Email support_preciseflex@brooksautomation.com for help resolving error codes.
| Code | Text | Description |
|---|---|---|
|
-200 |
No memory available |
There is not sufficient memory to perform the requested operation. Large amounts of memory may be used by the following: loaded GPL procedures, arrays, strings, and the Data Logger. Check if any of these items are unusually large. |
|
-201 |
System internal consistency error |
This error indicates that a condition has been detected that should not be possible if the controller and its system software are operating properly. Most likely, this indicates that a software bug has been encountered. Please report this message along with the process necessary to generate this problem to Precise. |
|
-202 |
Invalid argument |
The value of an argument used in a GPL instruction, built-in method, or console command is not allowed. |
|
-203 |
FIFO overflowed |
An overflow has occurred in a system data structure. Most likely, this indicates that a software bug has been encountered. Please report this message along with the process necessary to generate this problem to Precise. |
|
-204 |
Not implemented |
You have attempted to use a feature of GPL or the Precise Controller that is planned but not implemented. |
|
-205 |
Missing argument |
A required argument for a GPL instruction, built-in method, or console command was not supplied. |
|
-206 |
Invalid auto execute mode |
The "Auto execution mode" specifies the major motion control function that the controller should perform. For example, the execution of the DIOMotion Blocks and GPL projects are examples of two "Auto execution modes". This error indicates that an invalid mode has been specified. Most likely, the value of "Automatic execution mode" (DataID 200) has been set incorrectly. |
|
-207 |
Too many |
The current operation has attempted to create more items of an internal data structure than is allowed. Most likely, this indicates that a software bug has been encountered. Please report this message along with the process necessary to generate this problem to Precise. |
|
-208 |
Protection error |
You have attempted to read a hidden
value, access a secured data area without proper authorization,
or use the Data Logger on data that cannot be logged. |
|
-209 |
Read only |
This error message indicates that you have attempted to alter a value that can only be read. For example, this error is generated if you attempt to change the value of an analog input. |
|
-210 |
Operating system error code |
This error message indicates that the underlying real-time operating system (the RTOS) or one of its communications drivers has signaled an error that does not correspond to a standard GPL error. The numeric code contains the RTOS error number. |
|
-211 |
Option not enabled |
This error is generated if you attempt
to execute or enable a software or hardware option that is either
not available in your system or has not been enabled. Typically,
this indicates that your system software does not support the
desired feature or a parameter has not be properly set. This
is different from missing a required license bit, which is indicated
by the "License not installed" error message. Normally,
this error includes one of the following codes that further defines
the problem. |
|
-212 |
License not installed |
A required software license is not
installed on your controller. The name of the missing
license is shown after this error message. The license names include: |
|
-213 |
Invalid password |
An invalid password was entered for a protected operation or facility. Please re-enter the correct password or ask your system administrator for the correct password. |
|
-214 |
Cancelled |
An operation was initiated that was subsequently cancelled. No further action is required. |
|
-215 |
No system clock interrupts |
Many of the major subsystems of the controller (e.g. the servo code, the trajectory generator, the GPL projects) are serviced by different threads of software that execute independently. This thread execution is governed in part by the ticking of a master system clock. When the system restarts, it automatically tests the system clock to ensure that it is ticking at the correct rate. These errors signify that the system clock is not operating properly. Most likely, this indicates a hardware problem with the main processor board, the MIDS. |
|
-216 |
System clock interrupts too slow |
|
|
-217 |
System clock interrupts too fast |
|
|
-218 |
Invalid task configuration |
An invalid parameter has been entered associated with one of the major tasks of the system. For example, the update period of the trajectory generator must be specified as a number that is a power of two. |
|
-219 |
Incompatible FPGA version |
The firmware in the FPGA is not compatible with the hardware or software configuration options in this controller. The FPGA ("Field Programmable Gate Array") controls the robot power sequencing, encoder interfaces, motor current loop and a host of other critical functions. There are multiple versions of FPGA firmware that support various motors, encoders, and other options. Please obtain a compatible version of the FPGA firmware data or modify your configuration parameters. FPGA firmware may be loaded by following the instructions in the FAQ section of the PreciseFlex™ PreciseFlex Library. |
|
-220 |
Not configured |
You have attempted to access some aspect of the system that has not been configured. For example, you have attempted to set a parameter for an axis that was not defined in the configuration database. |
|
-221 |
Invalid robot type |
A kinematic robot module does not exist for the specified robot type. This typically indicates that a value specified in the "Robot types" (DataID 116) is incorrect. Please review this list of values and look at the information on the available robot kinematic modules. |
|
-222 |
Remote software incompatible |
In a Servo Network system, the indicated slave controller contains software that is not compatible with the master controller. Update the slave controller's software to a compatible version. Normally the master and all slaves should run the identical GPL software version. |
|
-223 |
Incompatible system |
|
|
-224 |
FPGA load failed |
|