Failed to modify properties for axis <axistagname>.
A problem occurred when modifying the properties of the axis. The error message indicates one of the these conditions:
The number of Position loop axes configured has exceeded the limit of the parent module.
This table lists the restrictive limits for Position-loop axes:
Module | Position-loop axis limit |
1769-L18ERM | 2 max P-loop for CIP-Axis tag types |
1769-L27ERM | 4 max P-loop for CIP-Axis tag types |
1769-L30ERM | 4 max P-loop for CIP-Axis tag types |
1769-L33ERM | 8 max P-loop for CIP-Axis tag types |
1769-L36ERM | 16 max P-loop for CIP-Axis tag types |
1769-L37ERM | 16 max P-loop for CIP-Axis tag types |
1769-L37ERMS | 16 max P-loop for CIP-Axis tag types |
1769-L37ERMO | 16 max P-loop for CIP-Axis tag types |
1769-L37ERMOS | 16 max P-loop for CIP-Axis tag types |
1769-L38ERM | 16 max P-loop for CIP-Axis tag types |
1769-L38ERMS | 16 max P-loop for CIP-Axis tag types |
5560, 5570, and 5580 controllers | 8 max P-loop for CIP-Axes/Drives defined under EN2T-module |
unlimited P-loop for CIP-Axes/Drives defined under EN3T-module | |
5580 controllers | unlimited P-loop (max 256 axes-tags) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L306ERM | 2 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L3100ERM | 32 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L310ERM | 4 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L320ERM | 8 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L330ERM | 16 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L340ERM | 20 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L46ERMW | 150 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L350ERM | 24 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
5069-L380ERM | 28 max P-loop (CIP-Axis tag types) for CIP-Axes/Drives defined under Embedded EtherNet port |
A command encountered fatal problems and was not able to be submitted for execution.
The online command for axis (For example, tune) could not be executed.
Check for any axis faults for the axis tag, or motion group faults for the motion group, associated with the axis.
The specified axis is already associated with a motion group and is currently unavailable. An axis can not be associated with more than one group.
You attempted to associate an axis, already associated to a group, to another group. An axis cannot be assigned to multiple groups.
You must dissociate the axis from the current group before assigning it to another group. Determine the group to which you want to associate the axis, and reassign the axis to that group.
The axis is associated with a motion group.
You attempted to delete an axis associated with a group when online. This operation cannot be performed online.
Go offline and then retry the operation.
The required security permissions are not granted.
If
FactoryTalk Security
is enabled for the project, access must be granted to the FactoryTalk Security
policy, Motion: Modify Configuration, to allow users to modify axis, coordinate system, or motion group properties. For more information see: Use FactoryTalk Security
with the Logix Designer
Application.The requested module channel is currently in use by another axis.
You attempted to assign an axis to a channel that is already associated with another axis.
Check all axis assignments. Reassign the axis offline, and then download to the controller.
The request could not be processed because the axis is not associated with a motion group.
The operation you attempted is not valid for an axis that is not associated with a group.
Check all axis assignments. Reassign the axes to a group offline, and then download to the controller.
The channel is invalid for the specified motion module.
The channel specified for association to the axis is invalid.
Check all axis assignments. Reassign the axes to channels offline, and then download to the controller.
The specified motion module does not exist.
The module specified for association to the axis does not exist.
Create the module, and then make the association.
You cannot assign the same axis to both channels.
You attempted to associate two or more channels for the 1756-M02AE module to the same axis.
Check all axis assignments. Reassign the axes to channels offline, and then download to the controller.
The coarse rate is too small to process the number of scheduled axes.
Increase the size of the coarse rate to an appropriate size.
The coarse rate is a type of rate that selects the periodic rate (at which the motion task executes) to compute the servo commanded position, velocity, and accelerations to be sent to the output modules when executing motion instructions.
Tip: | If the coarse rate is too small, the AC processor may not have time to execute non-motion related ladder logic. As a general rule, one millisecond per axis is required by the motion task in order to allow the processor reasonable execution time. |
To calculate the coarse rate (or coarse update period) for the number of axes in your application, use the following formula:
2 *(Baseline task time + [Actions for axis 1 + Actions for axis 2 . . . + Actions for axis n]) = Coarse Update period |
You must then divide the result of this calculation by 1000 and round it to the nearest millisecond.
The coarse rate is too large to process the number of scheduled axes.
Decrease the size of the coarse rate to an appropriate size.
Tip: | If the coarse rate is too large, the AC processor may not have time to execute non-motion related ladder logic. As a general rule, one millisecond per axis is required by the motion task in order to allow the processor reasonable execution time. |
An invalid string was entered.
A character string was entered in a field where a numeric value was expected.
An invalid base was entered.
A real (decimal) value was entered in a field where an integer value was expected.
The Feedback Cycle Resolution must be a power of two and less than or equal to the fixed Effective Resolution.
When the Data Source mode is set to Nameplate DataSheet, correct the Cycle Resolution.
When setting the Data Source mode to Catalog Number, the error indicates the motor selected is incompatible with the module. The Cycle Resolution of the selected motor exceeds the resolution supported by the module. The workaround is to select another motor.
Provide Feedback