When downloading a curve to the RMC via the variable table, the Curve Status register in the curve data will contain an error code if the Curve Add (82) command could not successfully add the curve data to the curve store. For more details on the Curve Status, see the Curve Data Formats topic.
The following error code values are defined:
10: Invalid curve data address.
Indicates that the Curve Data command parameter was not a valid curve data address. Only addresses in the Variable Tables current or initial values are acceptable.
11: Curve data is not in the correct format.
The Curve Data did not follow one of the supported Curve Data Formats. Examples of problems that will give this error include:
Invalid Format value.
Curve Data runs off the end of the variable table.
In a partial curve, the Part Offset is beyond the Total Curve Data Length.
In a partial curve, the Part Offset is negative.
In a partial curve, the Total Curve Data Length is negative or zero.
In a partial curve, the Part Length is negative or zero.
In a multiple curve format, the number of registers per curve is less than six (6).
In a multiple curve format, the number of curves is negative or zero.
In a multiple curve format, an individual Curve Data does not fit in the registers reserved for it.
The Interpolation Options field is not a valid value.
12: Too many pending Curve Adds.
This error indicates that a Curve Add command could not be accepted because the curve processing queue was full. That is, there are already sixteen Curve Add or Delete requests in the queue. The Curve Add command will also signal a command error for this error.
13: No room for the curve in the curve storage area.
Unable to allocate memory from the Curve Store for the curve. There are three times that a curve may require a block of memory from the Curve Store. First, if a partial curve format is used, a temporary buffer must be allocated to hold the entire download. Second, if the curve interpolation method requires significant pre-processing then a temporary block of memory must be allocated. Third, the processed curve itself will be allocated from the Curve Store. This error code will be used if the Curve Store does not have enough space free for any of these allocations. See Curve Storage Capacity for details on memory requirements.
14: Non-increasing X value found in curve data.
The X values for each successive point must be increasing. This error will be generated for the Variable-Spaced or Advanced curve data formats if the X values are not increasing, or in the Evenly-Spaced format if the X Interval is less than or equal to zero.
15: Invalid floating point value found in curve data.
This indicates that one or more point X, Y, or V values are invalid floating point values. For the Evenly-Spaced format, this also includes the X0 and X Interval values.
16: Point type found in curve data that is not valid.
In the Advanced curve data formats, the Point Type field must be 0, 1, or 2.
17: The curve has fewer than the required number of data points.
The Curve has fewer than the required number of points. All curves must have at least 2 points.
18: Interpolation Options are selected that are not supported by the selected interpolation method.
The Interpolation Options register had an invalid value for the selection interpolation method. For example, the Constant and Linear interpolation methods do not support any Interpolation Options, so this field must be zero. Refer to the Curve Interpolation Methods and Options topic for acceptable values for each interpolation method.
19: Point type found that is not supported by the selected interpolation method.
This error can occur if the Advanced curve data format is used with the Constant or Linear interpolation methods if the point type is inconsistent with the interpolation method. For example, the Constant interpolation method can only have point types of Standard, and the Linear interpolation method can only have point types of Standard or Constant-Velocity Segment.
20: Cyclic curve with not equal first and last points.
This error will occur if the curve with cubic interpolation uses the Cyclic interpolation option, but the first and last points in the curve do not have the same Y value. Firmware versions 3.39.0 and newer allow unequal first and last y values, so this error will not occur.
21: Curve calculations overflowed.
This error can occur for curves with cubic interpolation if processing the curve caused a numeric overflow. This will occur only for curves with extreme point definitions, such as extremely small changes in X, extremely large changes in Y, or extremely large velocities.
22: Curve Part had fields that mismatched previous part(s).
This error can occur when downloading a curve in multiple parts if certain values do not match between subsequent parts of the same curve. Specifically the following items must match across all parts in a curve:
Format field
Total Curve Data Length field
Curve ID command parameter
Interpolation Method command parameter
Life Cycle command parameter
23: Curve Part was received out of order.
This error can occur when downloading a curve in multiple parts if the Part Offset field does not match the next expected offset. The next part to be downloaded must have its Part Offset set to the previous Part Offset plus the previous Part Length. A part offset of zero (0) is always accepted as a new curve download, and will cause any in-progress partial download to be discarded.
24: Maximum number of curves reached.
This error will occur if there are already 128 curves in the curve store. You must delete one or more curves before adding more curves.
See Also
Curves Overview | Curve Add (82) | Curve Data Formats
Copyright © 2025 Delta Computer Systems, Inc. dba Delta Motion