Module Class Attributes

The following collection of Module Class Attributes are stored in the controller and used to configure Motion Device Axis Object Class attributes associated with the CIP Motion device. These attributes generally apply to the CIP Motion connection behavior. If these Module Class attributes are included in the CIP Motion Control Axis Object implementation, the attribute values are the same for all axis instances associated with the module. In such an implementation, the controller need only apply the Module Class attribute value for one of the axis instances to configure the corresponding Motion Device Axis Object Class attribute of the device.
Controller Update Delay High Limit
Usage
Access
T
Data Type
Default
Min
Max
Semantics of Values
Optional
Set
SINT
4
1
10
# of Controller Update Periods
Represents the high limit delay threshold for a Controller to Device (C-to-D) Connection update. This delay is specified in units of Controller Update Periods. Exceeding this limit results in a Control Connection Update Fault.
Controller Update Delay Low Limit
Usage
Access
T
Data Type
Default
Min
Max
Semantics of Values
Optional
Set
SINT
2
1
10
# of Controller Update Periods
Represents the low limit delay threshold allowed for a Controller to Device (C-to-D) Connection update. This delay is specified in units of Controller Update Periods. Exceeding this limit results in a Control Connection Update Alarm.
Sync Threshold
Usage
Access
T
Data Type
Default
Min
Max
Semantics of Values
Optional
Set
DINT
10000
1
10
9
Nanoseconds
Default: device dependent minimum value
Determines the threshold for the Observed Variance of System Time below which the Motion Device Axis Object is considered synchronized. The Group_Sync service uses this as a criterion for a successful response.
Max Events per Update
Usage
Access
T
Data Type
Default
Min
Max
Semantics of Values
Optional
Set
SINT
2
1
4
# of Event Notifications per Update per Axis
Determines the maximum number of Event Notifications that can be passed to the controller per update per axis instance via the Device-to-Controller connection.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.