The Data ID code and the specified index values do not form a valid data reference. Check that the appropriate index values are specified with this Data ID.

The Data ID code specified is not known by GPL. Check that the Data ID is valid. Some Data ID codes only become known if certain software options are enabled or configurations are selected. For example, you cannot specify absolute encoder parameters if you do not have any absolute encoders configured. Check that you are not specifying codes for a component that is not configured.

For networked servo systems, the definitions for a Data ID must be the same for the master and all slave nodes. This error indicates some differences were detected. Verify that compatible software is loaded on the master node and all slave nodes.

The parameter database was not initialized properly at system startup. This error indicates an internal system error and should never been seen.

For networked servo systems, some data and operations are only allowed on the master node. An attempt has been made to access such data or operations directly from a slave node.

The data index value specified in a Data ID reference is invalid. Probably an array index has been specified that is greater than the actual array size.

An internal error has occurred during a database reference. The parameter specified along with the Data ID may not be valid. This error should never be seen.

An internal error has occurred during a database reference. The parameter specified along with the Data ID may not be valid. This error should never be seen.

An internal error has occurred during a database reference. This error should never be seen.

A parameter index value specified in a Data ID reference is invalid. Probably the robot number or other index value is too large.

Some or all of the data in a configuration ".pac" file could not be read because it did not have the expected format. Either the file has become corrupted or an attempt to manually edit the file has introduced some errors.

The total number of axes or motors specified for a robot violates the number permitted. For example, this can occur if you specify 5 axes for the XYZTheta robot module. More subtly, if you configure the maximum number of motors supported by the system and then attempt to turn on split-axis control for one or axes, this requires that more motors be added.

A specified analog or digital signal number is not within the allowed range of values for the signal type expected. Change the signal number to a valid value.

A specified analog or digital signal is not currently installed in the controller. Remote signals may dynamically change between installed and uninstalled status depending on the state of the remote device. Verify that all remote devices are connected and active.

An input signal has been specified when an output signal is required. Change the signal number to an appropriate value.

During initialization, one or more of the parameter database files (*.pac files) could not be found on the controller’s flash drive in the folder /flash/config. Restore the files and reboot your controller.

A parameter database file (*.pac file) was found in the controller’s flash drive folder /flash/config but the file format is not valid. Restore the file and reboot your controller.

An attempt has been made to alter a Parameter Database value when motor power is enabled. However, the parameter can only be modified if motor power is disabled. This is a safety precaution to ensure that the robot does not move erratically when the value is modified. To avoid this error condition, disable motor power and retry modifying the Parameter Database value.

Two coupled robot axes, for example two axes that are coupled in Split-axis control, have been defined to be driven by amplifiers that are contained on two different physical controllers that are connected on a Servo Network. This is not permitted. The two axes must be driven by amplifiers on the same physical controller.

A special command has been issued that inhibits any modified Parameter Database values that are in memory from being written to the flash disk. This command is typically issued by system programs that temporarily modify PDB values, which if written to the flash, would corrupt the valid data that is already contained on the flash. If you wish to modify PDB values and permanently save the changes, reboot the controller to clear this special mode.

A data log specification refers to a Data ID that cannot be logged. Some values require too much computation to permit real-time logging.

An attempt has been made to perform an operation that is not valid while the datalogger is active. Disable the datalogger and try again.

An attempt has been made to start the datalogger before it has been initialized. Normally this error is not seen if the web interface is used for logging. It may be seen if database parameter "Data logger enable" (DataID 753) is set before parameter "Data logger load command" (DataID 752) is set.

An attempt has been made to start the datalogger before defining any items to log.

A datalogger trigger specification refers to a Data ID that is not specified as a logged item. Triggers can only specify Data ID values that are also being logged.

In a networked servo system, a datalogger trigger specification attempted to compare two Data IDs whose values exist on different network nodes. A trigger can only compare items that are on the same node.

Some Data ID values cannot be used as trigger values. For example Cartesian positions or velocities are computed from logged data after logging is complete, so these values cannot be tested at logging time.

In a servo network or GSB-based system, items collected by the datalogger from slave nodes are streamed from the slave to the master in real time. The amount of data that can be streamed depends on the trajectory period, the datalogger sampling interval, and the size and number of data items being logged from the slave. This error indicates that you have requested more data to be logged than can be streamed. Reduce the number of data items requested from the slave or increase the datalogger sampling interval.

An attempt was made to start the CPU Monitor utility or read data from it when it was active. Wait until the current monitor interval is complete, or cancel the current monitor and try again.