7 OPC UA ObjectTypes

Figure 5 shows the organization of the OPC UA for Powertrain - Functional Model ObjectTypes used to model Powertrain Objects. All Axis ObjectTypes are derived from the abstract PtDriveAxisType providing the functions common to all Axis ObjectTypes.

The PtDriveAxisType ObjectType is derived from the PtFunctionType ObjectType defining common properties shared by all Powertrain Objects.

Figure 5 - Powertrain Functional Model ObjectTypes organization

7.1 PtFunctionType definition

The PtFunctionType specifies the properties which are common for all OPC UA for Powertrain - Functional Model ObjectTypes.

Table 15 - PtFunctionType definition
AttributeValue
BrowseNamePtFunctionType
IsAbstractTrue
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasPropertyVariableApplicationTag0:String0:PropertyTypeO, RO
0:HasComponentMethodSetApplicationTagO
0:HasComponentObjectLock2:LockingServicesTypeO
0:HasComponentObjectFieldbusSignals0:FolderTypeO
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectMaintenance0:FolderTypeM
0:HasComponentObjectLogbookPtLogbookTypeO
0:GeneratesEventObjectTypePtLogbookEventType
0:HasComponentObjectLogObject0:LogObjectTypeO
0:GeneratesEventObjectTypePtLogObjectEventType
Conformance Units
Powertrain Actual and Command Values
Powertrain Logbook Readable
Powertrain Logbook Events
Powertrain Fieldbus
Powertrain Encoder Channel
Powertrain LogObject
Powertrain LogObject Events

General Properties in Semantic sub-aspect

The ApplicationTag Variable contains information given by the overall application. The purpose is to provide additional semantic information about the represented Powertrain Objects role or labelling in the context of the specific overall application context (machine, site or plant). Therefore, plant operators and/or application engineers are responsible to set the content of the ApplicationTag with information used for site management, asset management or other administrative purposes, e.g. "Production Line <m>/Machine <n>/x-Axis".

Furthermore, information out of identification objects offered by field bus protocols may be used as content of the ApplicationTag Variable (e.g. in case of PROFINET, the I&M-1 record "tag-function" or the I&M-3 "descriptor" could be used). However, as a default, vendors could also generate the ApplicationTag string out of the device or field bus configuration data as initial content of the Variable (e.g. in case of PROFINET, the NameOfStation and Module/Axis number could be used).

The Client can change the Value of this Variable by invoking the SetApplicationTag Method.

Before invoking a Method of the PtFunctionType Object, Clients must gain exclusive write access ("lock" the PtFunctionType Object) using the Lock Object.

The Lock Object ensures exclusive Method call for one Client. The Client locks the PtFunctionType Object by invoking the InitLock Method of the Lock Object. The Client invokes ExitLock to release the lock.

Some components of the PtFunctionType have additional subcomponents which are defined in Table 16.

Table 16 - PtFunctionType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
FieldbusSignals0:HasComponentVariable<SignalName>0:Number0:BaseDataVariableTypeOP, RO
Monitoring0:HasComponentVariableControlPriority0:UInt16PtControlPriorityVariableTypeO, RO
Monitoring0:HasComponentVariableShaftTurningDirection0:UInt16PtShaftTurningDirectionVariableTypeO, RO
Monitoring0:HasComponentVariableDeviceTemperature0:FloatPtTemperatureVariableTypeO, RO
Monitoring0:HasComponentObject<VibrationSensor_x>PtVibrationSensorTypeOP
Applied from 2:IOperationCounterType Interface:
Maintenance0:HasPropertyVariable2:PowerOnDuration0:Duration0:PropertyTypeO, RO
Maintenance0:HasPropertyVariable2:OperationDuration0:Duration0:PropertyTypeO, RO
Maintenance0:HasPropertyVariable2:OperationCycleCounter0:UInteger0:PropertyTypeO, RO
Maintenance0:HasComponentObject<Motor_x>0:BaseObjectTypeOP
Maintenance0:HasComponentObject<Converter>0:BaseObjectTypeOP
Maintenance0:HasComponentObject<Gear_x>0:BaseObjectTypeOP
Maintenance0:HasComponentObject<Encoder_x>0:BaseObjectTypeOP
Maintenance0:HasComponentObject<Brake_x>0:BaseObjectTypeOP
Applied from 2:IOperationCounterType Interface:
Maintenance
<Motor_x>

0:HasPropertyVariable2:PowerOnDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Motor_x>

0:HasPropertyVariable2:OperationDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Motor_x>

0:HasPropertyVariable2:OperationCycleCounter0:UInteger0:PropertyTypeO, RO
Maintenance
<Converter>

0:HasPropertyVariable2:PowerOnDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Converter>

0:HasPropertyVariable2:OperationDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Converter>

0:HasPropertyVariable2:OperationCycleCounter0:UInteger0:PropertyTypeO, RO
Maintenance
<Gear_x>

0:HasPropertyVariable2:PowerOnDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Gear_x>

0:HasPropertyVariable2:OperationDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Gear_x>

0:HasPropertyVariable2:OperationCycleCounter0:UInteger0:PropertyTypeO, RO
Maintenance
<Encoder_x>

0:HasPropertyVariable2:PowerOnDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Encoder_x>

0:HasPropertyVariable2:OperationDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Encoder_x>

0:HasPropertyVariable2:OperationCycleCounter0:UInteger0:PropertyTypeO, RO
Maintenance
<Brake_x>

0:HasPropertyVariable2:PowerOnDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Brake_x>

0:HasPropertyVariable2:OperationDuration0:Duration0:PropertyTypeO, RO
Maintenance
<Brake_x>

0:HasPropertyVariable2:OperationCycleCounter0:UInteger0:PropertyTypeO, RO
Maintenance
<Motor_x>

0:HasComponentVariableThermalCapacityUtilization0:UInteger0:BaseDataVariableTypeO, RO
Maintenance
<Motor_x>

0:HasComponentVariablePeakUtilization0:UInteger0:BaseDataVariableTypeO, RO
Maintenance
<Motor_x>

0:HasComponentVariableRemainingUsefulLifetime0:Integer0:BaseDataVariableTypeO, RO
Maintenance
<Gear_x>

0:HasPropertyVariableOilRemainingUsefulLifetime0:Duration0:PropertyTypeO, RO
Maintenance
<Gear_x>

0:HasComponentVariableMaintenanceStatus0:UInt16PtMaintenanceStatusVariableTypeO, RO
Maintenance0:HasComponentVariableThermalCapacityUtilization0:UInteger0:BaseDataVariableTypeO, RO
Maintenance0:HasComponentVariablePeakUtilization0:UInteger0:BaseDataVariableTypeO, RO
Maintenance0:HasComponentVariableRemainingUsefulLifetime0:Integer0:BaseAnalogTypeO, RO
Maintenance0:HasComponentVariableGearOilRemainingUsefulLifetime0:Integer0:BaseAnalogTypeO, RO
Maintenance0:HasComponentVariableGearMaintenanceStatus0:UInt16PtMaintenanceStatusVariableTypeO, RO

SetApplicationTag Method

This Method sets the Value of the ApplicationTag Variable. The security constraints defined in chapter 0 apply.

Signature

	SetApplicationTag (
		[in] 0:String	 ApplicationTag
		);
	
ArgumentDescription
ApplicationTagString containing the desired content of the ApplicationTag Variable.

The Method Result Codes (defined in Call Service) are defined in Table 17.

Table 17 - Possible Method Result Codes
Result CodeDescription
GoodThe Method execution was successful.
Bad_UserAccessDeniedThe user has not the authorization to execute the Method.
Bad_InvalidArgumentThe Server is not able to apply the name. The ApplicationTag string may be too long or may contain invalid characters. The Server may also reject duplicates.
Bad_LockedThe PtFunctionType Object is locked by a different Client's Session.
Bad_RequiresLockThe PtFunctionType Object is not locked. Clients must lock the PtFunctionType Object before invoking a Method.
Bad_UnexpectedErrorThe Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure.

Monitoring folder in Actual and Command Values sub-aspect

The Monitoring folder contains Variables common to all derived ObjectTypes. Derived ObjectTypes add additional type specific components to the Monitoring folder.

The specification of the Monitoring folder at the abstract root of the type hierarchy renders this folder mandatory for all derived ObjectTypes. The Variables specified by PtFunctionType are defined in Table 16 and are common for all derived ObjectTypes.

Maintenance folder in Maintenance sub-aspect

The Maintenance folder contains optional properties defined by the 2:IOperationCounterType Interface specified in [OPC 10000-100]. Figure 6 shows the motor related components of the Maintenance folder if the Drive has one motor. The PowerOnDuration, OperationDuration and OperationCycleCounter Properties are specified by the applied 2:IOperationCounterType Interface.

For a description of all Variables and Properties in the "Maintenance" folder see Table 54. The specification of the Maintenance folder at the abstract root of the type hierarchy renders this folder mandatory for all derived ObjectTypes. Derived ObjectTypes may add additional Variables to this folder.

If the Drive has more than one motor, and there are separate maintenance related variables for motors and converter, the 2:IOperationCounterType Interface shall be applied to the <Motor_x> or <Converter> placeholder Objects. The RemainingUsefulLifetime, ThermalCapacityUtilization and PeakUtilization Variables shall also be provided as components of the separate Objects representing the motors or converter in this case, as shown in Figure 7 for a dual motor scenario.

Figure 7 - IOperationCounterType Interface applied to placeholder Object

The same principle applies for the <Gear_x> placeholder objects. If the Drive has one gear, the gear-related Variables GearMaintenanceStatus and GearOilRemainingUsefulLifetime shall be provided as components of the Maintenance folder. If the Drive has more than one gear, the <Gear_x> placeholder Objects shall provide the MaintenanceStatus and OilRemainingUsefulLifetime Variables and the GearMaintenanceStatus and GearOilRemainingUsefulLifetime Variables shall be omitted.

If the Drive is equipped with more than one brake, the 2:IOperationCounterType Interface shall be applied to the individual <Brake_x> placeholder Objects. If the Drive is equipped with more than one encoder, this Interface shall be applied to the individual <Encoder_x> Objects.

Diagnosis sub-aspect

The Logbook Object provides access to the PtDriveAxisType Object's diagnosis system.

The Server might provide the Client with information about new incidents by sending PtLogbookEventType Events.

The 0:LogObject Object (defined in OPC 10000-26) can be provided to make the content of the diagnosis system represented by the Logbook Object available for all Clients which prefer to utilize the LogObject. The mapping from the LogEntryDataType structures provided by the Logbook Object to the LogObject's 0:LogRecord structures is specified in Table 94.

The Server might provide the Client with information about new entries in the LogObject by sending PtLogObjectType Events.

The Logbook Object essentially provides the Client with the means to obtain information about the diagnosis state of a PtFunctionType Object. The Logbook also makes the history of diagnosis relevant events available for Clients by recording timestamps for the event when the event first appears, when it is acknowledged and when it disappears. Since the capacity of the diagnosis buffer the Logbook represents is limited, acknowledged events may be deleted by the Server.

The 0:LogObject provides a standard way to collect diagnostic information and to make it available for Clients. This allows a standard Client unaware of the Logbook Object defined in this specification to access the diagnosis information of a Powertrain Object. It also offers more flexibility regarding the required local memory, since the 0:LogObject may send the diagnosis records to a remote Server allowing the local 0:LogObject to have only a small buffer of records. The 0:LogObject also allows the collection of diagnosis information in a system using OpenTelemetry (see OPC 10000-26 Annex C).

Figure 8 shows the structure of the "Diagnosis" sub-aspect in conjunction with the associated EventTypes. The PtLogbookEventType Events related to entries into the Logbook are generated by the parent PtFunctionType Object. The insertion of 0:LogRecords by the LogObject causes PtLogObjectEventType Events to be generated by the parent PtFunctionType Object as well. The parent PtFunctionType Object is the SourceNode of the Events.

Figure 8 - Relationship of diagnosis Objects and diagnosis Events

7.1.1 PtDriveAxisType definition

The PtDriveAxisType ObjectType specifies the properties which are common for OPC UA for Powertrain - Functional Model Axis Type Drive Object ObjectTypes. The general characteristic for the PtDriveAxisType is that it contains an actuator.

The PtDriveAxisType is an abstract ObjectType representing Powertrain Drive Axis Objects.

Table 18 - PtDriveAxisType definition
AttributeValue
BrowseNamePtDriveAxisType
IsAbstractTrue
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtFunctionType.
0:HasComponentVariableAxisType0:UInt160:MultiStateValueDiscreteTypeM, RO
0:HasComponentObjectLimitSupervision0:FolderTypeO
0:HasComponentObjectCharacteristicsConverterPtCharacteristicsConverterTypeO
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectLogbookPtLogbookTypeM
0:HasComponentObjectSafetyPtSafetyTypeO
0:HasComponentObjectVelocityProfile0:FolderTypeO
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectMaintenance0:FolderTypeM
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties
Powertrain Logbook Readable
Powertrain Safety

Some components of the PtDriveAxisType have additional subcomponents which are defined in Table 19. For detailed descriptions of these Variables see Table 54.

Table 19 - PtDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableAxisState0:UInt160:MultiStateValueDiscreteTypeM, RO
Monitoring0:HasComponentVariableControlPriority0:UInt16PtControlPriorityVariableTypeM, RO
Monitoring0:HasComponentVariableControlMode0:UInt160:MultiStateValueDiscreteTypeO, RO
Monitoring0:HasComponentVariableFrequencySetpoint0:Float0:AnalogUnitTypeO, RO
Applied from IMonitoringElectric Interface (for electric drives only):
Monitoring0:HasComponentVariableBleederTemperature0:FloatPtTemperatureVariableTypeO, RO
Monitoring0:HasComponentVariableConverterOutputFrequency0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputVoltage0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputVoltageMagnetization0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputVoltageTorque0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputCosPhi0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputCurrent0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputCurrentMagnetization0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputCurrentTorque0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterOutputPower0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableConverterTemperature0:FloatPtTemperatureVariableTypeO, RO
Monitoring0:HasComponentVariableDcBusVoltage0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableLineInputPower0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring

0:HasComponent

VariableMotorTemperature0:FloatPtTemperatureVariableTypeO, RO
Monitoring0:HasComponentVariableBrakeState0:UInt16PtBrakeStateVariableTypeO, RO
Monitoring0:HasComponentVariableAxisTorqueForce0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAxisOutputVelocity0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearInputVelocity0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearInputTorque0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearOutputVelocity0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearOutputTorque0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
Monitoring0:HasComponentVariableGearTemperature0:FloatPtTemperatureVariableTypeO, RO
Monitoring0:HasComponentVariableGearState0:UInt16PtGearStateVariableTypeO, RO
Monitoring0:HasComponentVariableGearOutputShaftTurningDirection0:UInt16PtShaftTurningDirectionVariableTypeO, RO
Monitoring0:HasComponentVariableGearInputShaftTurningDirection0:UInt16PtShaftTurningDirectionVariableTypeO, RO
Maintenance0:HasComponentVariableGearBacklash0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorPowerRated0:Float0:AnalogUnitTypeM, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorSpeedRated0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorTorqueRated0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorForceRated0:Float0:AnalogUnitTypeO, RO
Applied from ICharacteristicsMotorAndControlElectric Interface (for electric drives only):
CharacteristicsMotorAndControl0:HasComponentVariableMotorMaxCurrent0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasPropertyVariableMotorUfRatio0:Float0:PropertyTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorRunUpVoltage0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorDcBrakingCurrent0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableDcBrakingTime0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorThermalLoadLimitConfigured0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorPeakCurrentConfigured0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodCurrentControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableFeedbackMode0:UInt160:MultiStateValueDiscreteTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableSpeedMaxConfigured0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTorqueMaxConfigured0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableMotorType0:UInt160:MultiStateValueDiscreteTypeM, RO
CharacteristicsMotorAndControl0:HasComponentVariablePositionFollowingErrorLimit0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableVelocityFollowingErrorLimit0:Float0:AnalogUnitTypeO, RO
Applied from ILimitSupervisionElectric Interface (for electric drives only):
LimitSupervision0:HasComponentVariableMotorCurrentLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableMotorCurrentLimitHigh0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableJogSpeed10:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableJogSpeed20:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableNominalSpeed0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableVelocityRampDownTime0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableQuickStopVelocityRampDownTime0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableVelocityRampDeceleration0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableQuickStopVelocityRampDeceleration0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableMinimumVelocity0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableMaximumVelocity0:Float0:AnalogUnitTypeO, RO

The child Nodes of the PtDriveAxisType have additional Attribute values defined in Table 20.

Table 20 - PtDriveAxisType Attribute values for child Nodes
BrowsePathValue Attribute
AxisType
0:EnumValues

[

{ "Value":0,

"DisplayName": "LINEAR",

"Description": "Axis with linear movement"

},

{ "Value":1,

"DisplayName": "ROTATORY",

"Description": "Axis with rotatory movement"

},

{ "Value":2,

"DisplayName": "ROTATORY_MODULO",

"Description": "Single turn rotatory axis with modulo correction"

},

{ "Value":3,

"DisplayName": "SPINDLE",

"Description": "Axis with spindle properties"

},

{ "Value":4,

"DisplayName": "VIRTUAL_AXIS_LINEAR",

"Description": "Virtual axis with linear movement"

},

{ "Value":5,

"DisplayName": "VIRTUAL_AXIS_ROTARY",

"Description": "Virtual axis with rotatory movement"

}

]

Monitoring
AxisState
0:EnumValues

[

{ "Value":0,

"DisplayName": "SWITCHING_ON_INHIBITED",

"Description": "Switching on inhibited"

},

{ "Value":1,

"DisplayName": "READY_FOR_SWITCHING_ON",

"Description": "Ready for switching on"

},

{ "Value":2,

"DisplayName": "SWITCHED_ON",

"Description": "Switched on"

},

{ "Value":3,

"DisplayName": "OPERATION",

"Description": "In operation"

},

{ "Value":4,

"DisplayName": "RAMP_STOP",

"Description": "Controlled stop by ramp function"

},

{ "Value":5,

"DisplayName": "QUICK_STOP",

"Description": "Controlled stop with maximum deceleration"

},

{ "Value":6,

"DisplayName": "POS_BASIC_STATE",

"Description": "Positioning mode basic state"

},

{ "Value":7,

"DisplayName": "POS_JOGGING",

"Description": "Positioning mode jogging"

},

{ "Value":8,

"DisplayName": "POS_BRAKING_WITH_RAMP",

"Description": "Positioning mode braking with ramp function"

},

{ "Value":9,

"DisplayName": "POS_HOMING_PROCEDURE",

"Description": "Positioning mode homing"

},

{ "Value":10,

"DisplayName": "POS_TRAVERSING_TASK_ACTIVE",

"Description": "Positioning mode traversing task active"

},

{ "Value":11,

"DisplayName": "POS_INTERMEDIATE_STOP_STOPPED",

"Description": "Positioning mode stopped in intermediate stop"

},

{ "Value":12,

"DisplayName": "POS_INTERMEDIATE_STOP_BRAKING",

"Description": "Positioning mode breaking in intermediate stop"

},

{ "Value":13,

"DisplayName": "PARKED",

"Description": "Parked"

},

{ "Value":14,

"DisplayName": "SPINDLE_STOPPED",

"Description": "Spindle stopped"

},

{ "Value":15,

"DisplayName": "SPINDLE_ACCELERATING",

"Description": "Spindle is accelerating"

},

{ "Value":16,

"DisplayName": "SPINDLE_DECELERATING",

"Description": "Spindle is decelerating"

},

{ "Value":17,

"DisplayName": "SPINDLE_IN_TARGET_AREA",

"Description": "Spindle is in target area"

}

]

Monitoring
ControlMode
0:EnumValues

[

{ "Value":0,

"DisplayName": "TORQUE_CONTROL",

"Description": "Torque control"

},

{ "Value":1,

"DisplayName": "TORQUE_CONTROL_SENSORLESS",

"Description": "Torque control sensorless"

},

{ "Value":2,

"DisplayName": "FORCE_CONTROL",

"Description": "Force control"

},

{ "Value":3,

"DisplayName": "FORCE_CONTROL_SENSORLESS",

"Description": "Force control sensorless"

},

{ "Value":4,

"DisplayName": "SPEED_CONTROL",

"Description": "Speed control"

},

{ "Value":5,

"DisplayName": "SPEED_CONTROL_SENSORLESS",

"Description": "Speed control sensorless"

},

{ "Value":6,

"DisplayName": "SPEED_CONTROL_DSC",

"Description": "Speed control with dynamic stiffness control"

},

{ "Value":7,

"DisplayName": "POSITION_CONTROL",

"Description": "Position control"

},

{ "Value":8,

"DisplayName": "POSITION_CONTROL_SENSORLESS",

"Description": "Position control sensorless"

},

{ "Value":9,

"DisplayName": "POSITIONING_CONTROL",

"Description": "Positioning control"

},

{ "Value":10,

"DisplayName": "UF_CONTROL",

"Description": "U/F control"

},

{ "Value":11,

"DisplayName": "VECTOR_CONTROL",

"Description": "Vector control"

},

{ "Value":12,

"DisplayName": "VECTOR_CONTROL_SENSORLESS",

"Description": "Vector control sensorless"

}

]

CharacteristicsMotorAndControl
FeedbackMode
0:EnumValues

[

{ "Value":0,

"DisplayName": "FEEDBACK_MOTOR",

"Description": "Feedback with motor encoder"

},

{ "Value":1,

"DisplayName": "FEEDBACK_DIRECT",

"Description": "Feedback with direct encoder"

},

{ "Value":2,

"DisplayName": "FEEDBACK_MOTOR_AND_DIRECT",

"Description": "Feedback with motor and direct encoder"

},

{ "Value":3,

"DisplayName": "FEEDBACK_SENSOR_1",

"Description": "Feedback with sensor 1"

},

{ "Value":4,

"DisplayName": "FEEDBACK_SENSOR_2",

"Description": "Feedback with sensor 2"

},

{ "Value":5,

"DisplayName": "FEEDBACK_SENSOR_3",

"Description": "Feedback with sensor 3"

},

{ "Value":6,

"DisplayName": "SENSORLESS",

"Description": "Feedback without sensor"

}

]

CharacteristicsMotorAndControl
MotorType
0:EnumValues

[

{ "Value":0,

"DisplayName": "ASYNCHRONOUS",

"Description": "Induction motor"

},

{ "Value":1,

"DisplayName": "PM_AC_SYNCHRONOUS",

"Description": "Synchronous motor"

},

{ "Value":2,

"DisplayName": "PM_AC_SYNCHRONOUS_IRONLESS",

"Description": "Synchronous ironless motor"

},

{ "Value":3,

"DisplayName": "DC_BRUSHLESS",

"Description": "Brushless DC motor"

},

{ "Value":4,

"DisplayName": "DC_BRUSHED",

"Description": "DC motor"

},

{ "Value":5,

"DisplayName": "PM_STEPPER",

"Description": "Stepper motor"

},

{ "Value":6,

"DisplayName": "HYBRID_STEPPER",

"Description": "Hybrid stepper motor"

},

{ "Value":7,

"DisplayName": "SYNC_RELUCTANCE",

"Description": "Synchronous reluctance motor"

}

]

Some values represented as enumerations in the Monitoring and CharacteristicsMotorAndControl folders are modelled as 0:MultiStateValueDiscreteType Variables. The content of the EnumValues lookup table Property is defined in Table 20 for all these 0:MultiStateValueDiscreteType Variables. The "Locale" field of the 0:LocalizedText structures is Server specific.

The AxisType Variable contains the mechanical drive type of the represented Powertrain Axis Object modelled as 0:MultiStateValueDiscreteType.

Monitoring folder in Actual and Command Values sub-aspect

The Monitoring folder inherited from PtFunctionType contains Monitoring Variables describing measurements of the Powertrain Axis Objects which are of interest for monitoring encoded as numeric data type. The PtDriveAxisType ObjectType adds Variables and Properties common for all the derived concrete ObjectTypes. Each derived ObjectType may add the Variables and Properties specific for the respective ObjectType.

Instances of the Monitoring folder shall reference the IMonitoringElectric Interface using the HasInterface ReferenceType.

For a description of all Variables and Properties in the "Monitoring" folder see Table 54.

LimitSupervision folder in Process Supervision sub-aspect

The LimitSupervision folder contains Variables with Values describing limit values for motor current, torque, and the like. These limit Variables differ between concrete derived Axis ObjectTypes and are specified separately for each derived Axis ObjectType.

Instances of the LimitSupervision folder shall reference the ILimitSupervisionElectric Interface using the HasInterface ReferenceType.

For a description of the Variables in the "LimitSupervision" folder see Table 54.

Axis Properties sub-aspect

The CharacteristicsConverter Object contains Variables with Values describing key data of the CDM's converter. This ObjectType represents the electric converter properties of electric drives and shall be always provided for electric drives. However, future versions of this specification might support additional drive types such as hydraulic or pneumatic drives. For these drive types dedicated Objects might be specified and referenced with additional optional HasComponent References.

The CharacteristicsMotorAndControl folder contains Variables with Values describing key data of the CDM's motor and its key control features.

Instances of the CharacteristicsMotorAndControl folder shall reference the ICharacteristicsMotorAndControlElectric Interface using the HasInterface ReferenceType.

The VelocityProfile folder contains Variables describing key properties of brake ramps. In addition, this folder also contains Variables describing the properties of a ramp function generator often available with VSD drives. The folder contains the properties mandatory for each derived Powertrain Axis Object type.

The Variables VelocityRampUpTime and VelocityRampDownTime are always related to the Value of the NominalSpeed Variable. The Variable VelocityRampDeceleration describes the same ramp function as VelocityRampDownTime and shall therefore always be provided together with this Variable. The same is true for the Variables VelocityRampUpTime and VelocityRampAcceleration provided by derived axis types.

For a description of the Variables in the CharacteristicsMotorAndControl folder and the VelocityProfile folder see Table 54.

7.1.1.1 PtFrequencyDriveAxisType

A PtFrequencyDriveAxisType is a PtDriveAxisType representing the functionality of a VSD with a frequency command interface. Figure 9 shows a block diagram demonstrating the basic organization and control flow for this axis type.

Figure 9 - PtFrequencyDriveAxisType Block Diagram

The formal definition of the PtFrequencyDriveAxisType ObjectType can be found in Table 21.

Table 21 - PtFrequencyDriveAxisType Definition
AttributeValue
BrowseNamePtFrequencyDriveAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtDriveAxisType.
0:GeneratesEventObjectTypePtMotorCurrentLimitEventType
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:HasComponentObjectVelocityProfile0:FolderTypeM
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectLimitSupervision0:FolderTypeO
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties

The components of the PtFrequencyDriveAxisType have additional subcomponents which are defined in Table 22.

Table 22 - PtFrequencyDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableFrequencyCommandValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableFrequencySetpoint0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableConverterOutputFrequency0:Float0:AnalogUnitTypeM, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodVelocityControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
LimitSupervision0:HasComponentVariableMotorCurrentLimitHigh0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableTorqueLimit0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitHigh0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableVelocityRampUpTime0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableVelocityRampAcceleration0:Float0:AnalogUnitTypeO, RO

For a description of the Variables see Table 54.

7.1.1.2 PtVelocityDriveAxisType

The PtVelocityDriveAxisType is an PtDriveAxisType representing the functionality of a VSD with a speed command interface. Figure 10 shows a block diagram demonstrating the basic organization and control flow for this axis type.

Figure 10 - PtVelocityDriveAxisType Block Diagram

The formal definition of the PtVelocityDriveAxisType ObjectType can be found in Table 23.

Table 23 - PtVelocityDriveAxisType Definition
AttributeValue
BrowseNamePtVelocityDriveAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtDriveAxisType.
0:HasComponentObjectVelocityProfile0:FolderTypeM
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:GeneratesEventObjectTypePtTorqueForceLimitEventType
0:GeneratesEventObjectTypePtMotorCurrentLimitEventType
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectLimitSupervision0:FolderTypeO
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties
Powertrain Limit Events

The components of the PtVelocityDriveAxisType have additional subcomponents which are defined in Table 24.

Table 24 - PtVelocityDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableVelocitySetpoint0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityCommandValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableAccelerationSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariablePositionActualValue0:Double0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariable<EncoderxTemperature>0:FloatPtTemperatureVariableTypeOP, RO
Monitoring0:HasComponentVariableVelocityFollowingError0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodVelocityControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodTorqueControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimit0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitHigh0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableVelocityRampUpTime0:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableVelocityRampAcceleration0:Float0:AnalogUnitTypeO, RO

For a description of the Variables see Table 54.

7.1.1.3 PtPositioningDriveAxisType

A PtPositioningDriveAxisType is an PtDriveAxisType representing the functionality of a servo drive or stepper drive with a motion trajectory command interface. Figure 11 shows a block diagram demonstrating the basic organization and control flow for this axis type.

Figure 11 - PtPositioningDriveAxisType Block Diagram

The formal definition of the PtPositioningDriveAxisType ObjectType can be found in Table 25.

Table 25 - PtPositioningDriveAxisType Definition
AttributeValue
BrowseNamePtPositioningDriveAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtDriveAxisType.
0:HasComponentObjectHoming0:FolderTypeM
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:HasComponentObjectVelocityProfile0:FolderTypeM
0:HasComponentObjectLimitSupervision0:FolderTypeM
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectMotionProgram0:FileTypeO
0:GeneratesEventObjectTypePtTorqueForceLimitEventType
0:GeneratesEventObjectTypePtMotorCurrentLimitEventType
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties
Powertrain Limit Events

Some components of the PtPositioningDriveAxisType have additional subcomponents which are defined in Table 26.

Table 26 - PtPositioningDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariablePositionActualValue0:Double0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariablePositionCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariablePositionSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocitySetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariable<EncoderxTemperature>0:FloatPtTemperatureVariableTypeOP, RO
Monitoring0:HasComponentVariablePositionFollowingError0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocityFollowingError0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentObjectTraversingTaskPtTraversingTaskTypeM
Monitoring0:HasComponentVariableOverride0:Float0:BaseDataVariableTypeO, RO
Monitoring0:HasComponentVariableHomingState0:UInt16PtHomingStateVariableTypeM, RO
LimitSupervision0:HasComponentVariableMotorCurrentLimitHigh0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableTorqueLimit0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitHigh0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitLow0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitHigh0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableTorqueLimiting0:Boolean0:BaseDataVariableTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodVelocityControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodTrajectoryInterpolation0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodPositionControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodTorqueControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTrajectoryInterpolationMode0:Byte0:MultiStateValueDiscreteTypeO, RO
Homing0:HasComponentVariableHomingDirection0:UInt16PtHomingDirectionVariableTypeO, RO
Homing0:HasComponentVariableHomingSpeedToCam0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingSpeedToMark0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingPointOffset0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingMode0:UInt16PtHomingModeVariableTypeM, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableSpindlePitch0:Float0:BaseDataVariableTypeO, RO
VelocityProfile0:HasComponentVariableJogPosInc10:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableJogPosInc20:Float0:AnalogUnitTypeO, RO

The SpindlePitch Variable shall be provided if a spindle is present in the Powertrain Axis Object.

The child Nodes of the PtPositioningDriveAxisType have additional Attribute values defined in Table 27.

Table 27 - PtPositioningDriveAxisType Attribute values for child Nodes
BrowsePathValue Attribute
CharacteristicsMotorAndControl
TrajectoryInterpolationMode
0:EnumValues

[

{ "Value":0,

"DisplayName": "LINEAR",

"Description": "Linear trajectory interpolation"

},

{ "Value":1,

"DisplayName": "VENDOR_SPECIFIC",

"Description": "Vendor specific trajectory interpolation"

}

]

For a description of the Variables see Table 54.

7.1.1.4 PtVelocityServoDriveAxisType

A PtVelocityServoDriveAxisType is an PtDriveAxisType representing the functionality of a servo drive with a velocity command interface. Figure 12 shows a block diagram demonstrating the basic organization and control flow for this axis type.

Figure 12 - PtVelocityServoDriveAxisType Block Diagram

The formal definition of the PtVelocityServoDriveAxisType ObjectType can be found in Table 28.

Table 28 - PtVelocityServoDriveAxisType Definition
AttributeValue
BrowseNamePtVelocityServoDriveAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtDriveAxisType.
0:HasComponentObjectEncoderChannelMotorPtEncoderChannelTypeM
0:HasComponentObjectEncoderChannelMechanicPtEncoderChannelTypeO
0:HasComponentObject<EncoderChannelAuxiliary>PtEncoderChannelTypeOP
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:HasComponentObjectHoming0:FolderTypeO
0:HasComponentObjectVelocityProfile0:FolderTypeM
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectLimitSupervision0:FolderTypeO
0:GeneratesEventObjectTypePtAxisSwOvertravelEventType
0:GeneratesEventObjectTypePtAxisHwOvertravelEventType
0:GeneratesEventObjectTypePtTorqueForceLimitEventType
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties
Powertrain Limit Events
Powertrain Encoder Channel

Some components of the PtVelocityServoDriveAxisType have additional subcomponents which are defined in Table 29.

Table 29 - PtVelocityServoDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableVelocitySetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocityCommandValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariablePositionActualValue0:Double0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableCurrentTorqueCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariable<EncoderxTemperature>0:FloatPtTemperatureVariableTypeOP, RO
Monitoring0:HasComponentVariableVelocityFollowingError0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableHomingState0:UInt16PtHomingStateVariableTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodVelocityControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodTorqueControl0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingMode0:UInt16PtHomingModeVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableSpindlePitch0:Float0:BaseDataVariableTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimit0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitLow0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableTorqueLimitHigh0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitHigh0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimiting0:Boolean0:BaseDataVariableTypeO, RO

The SpindlePitch Variable shall be provided if a spindle is present in the Powertrain Axis Object.

For a description of the Variables see Table 54.

7.1.1.5 PtPositionServoDriveAxisType

A PtPositionServoDriveAxisType is an PtDriveAxisType representing the functionality of a servo drive with a position command interface. Figure 13 shows a block diagram demonstrating the basic organization and control flow for this axis type.

Figure 13 - PtPositionServoDriveAxisType Block Diagram

The formal definition of the PtPositionServoDriveAxisType ObjectType can be found in Table 30.

Table 30 - PtPositionServoDriveAxisType Definition
AttributeValue
BrowseNamePtPositionServoDriveAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtDriveAxisType.
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:HasComponentObjectEncoderChannelMotorPtEncoderChannelTypeM
0:HasComponentObjectEncoderChannelMechanicPtEncoderChannelTypeO
0:HasComponentObject<EncoderChannelAuxiliary>PtEncoderChannelTypeOP
0:HasComponentObjectHoming0:FolderTypeM
0:HasComponentObjectVelocityProfile0:FolderTypeM
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectLimitSupervision0:FolderTypeO
0:GeneratesEventObjectTypePtAxisSwOvertravelEventType
0:GeneratesEventObjectTypePtAxisHwOvertravelEventType
0:GeneratesEventObjectTypePtTorqueForceLimitEventType
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties
Powertrain Limit Events
Powertrain Encoder Channel

Some components of the PtPositionServoDriveAxisType have additional subcomponents which are defined in Table 31.

Table 31 - PtPositionServoDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariablePositionCommandValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocitySetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariablePositionActualValue0:Double0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableVelocityCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableCurrentTorqueCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariablePositionSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariable<EncoderxTemperature>0:FloatPtTemperatureVariableTypeOP, RO
Monitoring0:HasComponentVariablePositionFollowingError0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableVelocityFollowingError0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableHomingState0:UInt16PtHomingStateVariableTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimit0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableTorqueLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitHigh0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitLow0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitHigh0:Float0:AnalogUnitTypeM, RO
LimitSupervision0:HasComponentVariableTorqueLimiting0:Boolean0:BaseDataVariableTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodVelocityControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodPositionControl0:Float0:AnalogUnitTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodTorqueControl0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingDirection0:UInt16PtHomingDirectionVariableTypeO, RO
Homing0:HasComponentVariableHomingSpeedToCam0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingSpeedToMark0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingPointOffset0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingMode0:UInt16PtHomingModeVariableTypeM, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableSpindlePitch0:Float0:BaseDataVariableTypeO, RO
VelocityProfile0:HasComponentVariableJogPosInc10:Float0:AnalogUnitTypeO, RO
VelocityProfile0:HasComponentVariableJogPosInc20:Float0:AnalogUnitTypeO, RO

The SpindlePitch Variable shall be provided if a spindle is present in the Powertrain Axis Object.

For a description of the Variables see Table 54.

7.1.1.6 PtTorqueServoDriveAxisType

A PtTorqueServoDriveAxisType is an PtDriveAxisType representing the functionality of a servo drive with a torque command interface. Figure 14 shows a block diagram demonstrating the basic organization and control flow for this axis type.

Figure 14 - PtTorqueServoDriveAxisType Block Diagram

The formal definition of the PtTorqueServoDriveAxisType ObjectType can be found in Table 32.

Table 32 - PtTorqueServoDriveAxisType Definition
AttributeValue
BrowseNamePtTorqueServoDriveAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtDriveAxisType.
0:HasComponentObjectEncoderChannelMotorPtEncoderChannelTypeM
0:HasComponentObjectEncoderChannelMechanicPtEncoderChannelTypeO
0:HasComponentObject<EncoderChannelAuxiliary>PtEncoderChannelTypeOP
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:HasComponentObjectHoming0:FolderTypeO
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectCharacteristicsMotorAndControl0:FolderTypeM
0:HasComponentObjectLimitSupervision0:FolderTypeO
0:GeneratesEventObjectTypePtTorqueForceLimitEventType
Conformance Units
Powertrain Actual and Command Values
Powertrain Axis Properties
Powertrain Limit Events
Powertrain Encoder Channel

Some components of the PtTorqueServoDriveAxisType have additional subcomponents which are defined in Table 33.

Table 33 - PtTorqueServoDriveAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariablePositionActualValue0:Double0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableAccelerationSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAccelerationActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceSetpoint0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableCurrentTorqueCommandValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableTorqueForceCommandAdditiveValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariable<EncoderxTemperature>0:FloatPtTemperatureVariableTypeOP, RO
Monitoring0:HasComponentVariableHomingState0:UInt16PtHomingStateVariableTypeO, RO
CharacteristicsMotorAndControl0:HasComponentVariableTimePeriodTorqueControl0:Float0:AnalogUnitTypeO, RO
Homing0:HasComponentVariableHomingMode0:UInt16PtHomingModeVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableSpindlePitch0:Float0:BaseDataVariableTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimit0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimitHigh0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitLow0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableSoftwarePosLimitHigh0:Float0:AnalogUnitTypeO, RO
LimitSupervision0:HasComponentVariableTorqueLimiting0:Boolean0:BaseDataVariableTypeO, RO

The SpindlePitch Variable shall be provided if a spindle is present in the Powertrain Axis Object.

One of the TorqueForceCommandValue and CurrentTorqueCommandValue Variables shall be provided.

For a description of the Variables see Table 54.

7.1.2 PtEncoderAxisType definition

The PtEncoderAxisType ObjectType specifies the properties of encoder Objects.

Table 34 - PtEncoderAxisType definition
AttributeValue
BrowseNamePtEncoderAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the PtFunctionType.
0:HasComponentObjectEncoderChannelPtEncoderChannelTypeM
0:HasComponentObjectMonitoring0:FolderTypeM
Conformance Units
Powertrain Actual and Command Values
Powertrain Encoder Channel

Some components of the PtEncoderAxisType have additional subcomponents which are defined in Table 35.

Table 35 - PtEncoderAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableControlPriority0:UInt16PtControlPriorityVariableTypeM, RO
Monitoring0:HasComponentVariableVelocityActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariablePositionActualValue0:Double0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableAccelerationActualValue0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableEncoderTemperature0:FloatPtTemperatureVariableTypeO, RO

7.1.3 PtGearAxisType definition

The PtGearAxisType ObjectType specifies the properties of Objects representing gears.

Table 36 - PtGearAxisType definition
AttributeValue
BrowseNamePtGearAxisType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
0:HasComponentObjectCharacteristicsMechanics0:FolderTypeO
0:HasComponentObjectMonitoring0:FolderTypeM
0:HasComponentObjectMaintenance0:FolderTypeM
Subtype of the PtFunctionType.
Conformance Units
Powertrain Actual and Command Values

Some components of the PtGearAxisType have additional subcomponents which are defined in Table 37.

Table 37 - PtGearAxisType additional Subcomponents
BrowsePathReferencesNodeClassBrowseNameDataTypeTypeDefinitionOthers
Monitoring0:HasComponentVariableBrakeState0:UInt16PtBrakeStateVariableTypeO, RO
Monitoring0:HasComponentVariableAxisTorqueForce0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableAxisOutputVelocity0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearInputVelocity0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearInputTorque0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearOutputVelocity0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearOutputTorque0:Float0:AnalogUnitTypeO, RO
Monitoring0:HasComponentVariableGearTemperature0:FloatPtTemperatureVariableTypeO, RO
Monitoring0:HasComponentVariableGearRatio0:Float0:AnalogUnitTypeM, RO
Monitoring0:HasComponentVariableGearState0:UInt16PtGearStateVariableTypeO, RO
Monitoring0:HasComponentVariableGearOutputShaftTurningDirection0:UInt16PtShaftTurningDirectionVariableTypeO, RO
Monitoring0:HasComponentVariableGearInputShaftTurningDirection0:UInt16PtShaftTurningDirectionVariableTypeO, RO
Maintenance0:HasComponentVariableGearBacklash0:Float0:AnalogUnitTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearFactorPrecisePtGearFactorDataType0:BaseDataVariableTypeO, RO
CharacteristicsMechanics0:HasComponentVariableGearRatio0:Float0:BaseDataVariableTypeO, RO

7.2 PtLogbookType definition

The PtLogbookType provides access to diagnosis information provided by ObjectTypes derived from the PtFunctionType.

Table 38 - PtLogbookType Definition
AttributeValue
BrowseNamePtLogbookType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableLogEntriesPtLogEntryDataType[]0:BaseDataVariableTypeM, RO
0:HasPropertyVariableLogbookSize0:UInt160:PropertyTypeM, RO
0:HasComponentMethodClearLogbookEntriesO
0:HasComponentMethodGetFilteredLogbookEntriesO
0:HasComponentMethodGetCurrentDiagnosisO
0:HasComponentMethodGetActiveDiagnosisO
0:HasComponentMethodGetHistoricDiagnosisO
Conformance Units
Powertrain Logbook Readable
Powertrain Logbook Events

The LogEntries array Variable consists of PtLogEntryDataType structure elements. The array is limited to the maximum size specified by the LogbookSize Property. The array contains PtLogEntryDataType elements for events and starts with the most recent event (the element with the most recent EventComing timestamp). If the Server maintains different fault situations in its diagnosis system, faults (events) which are still present after an acknowledge generate a new entry in the actual fault situation causing more than one entry with the same EventNumber for one event.

The LogbookSize Property contains the maximum length of the LogEntries array. The actual length of the array may be smaller.

Clients must lock the parent PtFunctionType Object before invoking a Method of the PtLogbookType Object.

7.2.1 ClearLogbookEntries Method

The ClearLogbookEntries Method clears the LogEntries array and resets the diagnosis system of the functional Object. The security constraints defined in chapter 6.2 apply.

Signature

	ClearLogbookEntries (
	);
	

The Method Result Codes (defined in Call Service) are defined in Table 39.

Table 39 - Possible Method Result Codes
Result CodeDescription
GoodThe Method execution was successful.
Bad_UserAccessDeniedThe user has not the right to execute the Method.
Bad_UnexpectedErrorThe Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure.

7.2.2 GetFilteredLogbookEntries Method

The GetFilteredLogbookEntries Method returns a LogEntries array matching the filter criteria. Method invocation shall be possible for all users (read-only).

Signature

	GetFilteredLogbookEntries (
		[in] 0:Byte				LogbookFilterOptions,
		[in] 0:Byte				FaultSituationNumber
		[in] PtEventTypeEnumeration 	EventType,
		[in] PtEventClassEnumeration	EventClass,
	[in] 0:Int32			VendorEventCode
		[in] 0:Duration			EventAppearanceInterval,
	[out] PtLogEntryDataType[] 	FilteredLogEntries
	);
ArgumentDescription
LogbookFilterOptions

Parameter restricting the returned logbook entries to those having valid EventGoing and/or EventAcknowledged timestamps.

If set to 1 ("GOING" filter), only logbook entries with valid EventGoing timestamp are returned.

If set to 2 ("ACKNOWLEDGED" filter), only entries with valid EventAcknowledged timestamp are returned.

If set to 3, the logic applied is "AND": only logbook entries meeting both filter criteria are returned.

Set to 0 if no filtering shall be applied.

If a value greater than 3 is passed, the Method Result Code shall be set to Bad_InvalidArgument.

FaultSituationNumberRestricts the returned logbook entries to those with the FaultSituationNumber field equal to this parameter. Passing 255 means "don't care".
EventTypeRestricts the returned logbook entries to those with the EventType field equal to this parameter. It is encoded as PtEventTypeEnumeration. Passing "UNSPECIFIED" means "don't care".
EventClassRestricts the returned logbook entries to those with the EventClass field equal to this parameter. It is encoded as PtEventClassEnumeration. Passing "UNSPECIFIED" means "don't care".
VendorEventCodeRestricts the returned logbook entries to those with the VendorEventCode field equal to this parameter. Passing -1 means "don't care" and does not restrict to entries with the VendorEventCode field set to -1.
EventAppearanceIntervalTime interval encoded as 0:Duration defined in [OPC 10000-3]. Restricts the returned logbook entries to those appearing within a timespan from the past up to now. The EventComing field of the logbook entries is used for checking this filter. Passing 0 means "don't care".
FilteredLogEntriesArray containing the logbook entries matching all filter criteria passed with the first 5 parameters. An empty array is returned if no logbook entry matches the filter criteria.

The Method Result Codes (defined in Call Service) are defined in Table 40.

Table 40 - Possible Method Result Codes
Result CodeDescription
GoodThe Method execution was successful.
Bad_InvalidArgumentThe Server is unable to execute the Method due to invalid arguments. For instance, the EventClass passed may be unknown.
Bad_UnexpectedErrorThe Server cannot execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure.

7.2.3 GetCurrentDiagnosis Method

The GetCurrentDiagnosis Method returns all log entries which occurred since the last acknowledge as LogEntries array. Starting with the most recent one, all log entries without valid EventAcknowledged timestamp are returned. Method invocation shall be possible for all users (read-only).

Signature

	GetCurrentDiagnosis (
		[out] PtLogEntryDataType[] 	CurrentLogEntries
	);
	
ArgumentDescription
CurrentLogEntriesArray containing the log entries occurred since the last acknowledge. An empty array is returned if no logbook entry matches the filter criteria.

The Method Result Codes (defined in Call Service) are defined in Table 41.

Table 41 - Possible Method Result Codes
Result CodeDescription
GoodThe Method execution was successful.
Bad_UnexpectedErrorThe Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure.

7.2.4 GetHistoricDiagnosis Method

The GetHistoricDiagnosis Method returns a LogEntries array with valid EventGoing field. Method invocation shall be possible for all users (read-only).

Signature

	GetHistoricDiagnosis (
		[in]  0:Byte					FaultSituationNumber,	
		[out] PtLogEntryDataType[]		HistoricLogEntries
	);
	
ArgumentDescription
FaultSituationNumberFault situation number the faults belong to. 0 identifies the current situation, 1 the historic situation preceding the current situation, and so on (see explanation below).
HistoricLogEntriesArray containing the log entries with valid EventGoing field entry. An empty array is returned if no logbook entry matches the filter criteria.

The Method Result Codes (defined in Call Service) are defined in Table 42.

Table 42 - Possible Method Result Codes
Result CodeDescription
GoodThe Method execution was successful.
Bad_InvalidArgumentThe fault situation specified by FaultSituationNumber does not exist.
Bad_UnexpectedErrorThe Server cannot execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure.

7.2.5 GetActiveDiagnosis Method

The GetActiveDiagnosis Method returns a LogEntries array containing log entries belonging to the current fault situation (log entries with FaultSituationNumber equal to 0) with valid EventComing timestamp, but with missing EventGoing timestamp. The method returns a subset of the entries returned by the GetCurrentDiagnosis Method. Method invocation shall be possible for all users (read-only).

Signature

	GetActiveDiagnosis (
		[out] PtLogEntryDataType[] 	ActiveDiagnosis
	);
	
ArgumentDescription
ActiveDiagnosisArray containing the log entries with missing EventGoing field entry. An empty array is returned if no logbook entry matches the filter criteria.

The Method Result Codes (defined in Call Service) are defined in Table 43.

Table 43 - Possible Method Result Codes
Result CodeDescription
GoodThe Method execution was successful.
Bad_UnexpectedErrorThe Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure.

7.3 PtEncoderChannelType

The PtEncoderChannelType is the representation of the Encoder sensor and sensor related auxiliary functionality. Clients gain access to the Encoder Object's data, properties, error log and configuration settings using an PtEncoderChannelType Object.

Table 44 - PtEncoderChannelType Definition
AttributeValue
BrowseNamePtEncoderChannelType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableEncoderChannelState0:UInt16PtEncoderChannelStateVariableTypeO, RO
0:HasComponentObjectSensorPtEncoderSensorTypeM
0:HasComponentObject<Probe_x>PtEncoderProbeTypeOP
0:HasComponentVariablePositionSensorFeedbackValue0:Number0:BaseDataVariableTypeO, RO
0:HasComponentVariableResolution0:Double0:BaseAnalogTypeO, RO
0:HasPropertyVariableAbsolutePositionRange0:Range0:PropertyTypeO, RO
0:HasComponentVariableSignalType0:UInt16PtEncoderChannelSignalTypeVariableTypeO, RO
Conformance Units
Powertrain Encoder Channel

The EncoderChannelState Variable contains the state of the encoder channel encoded as PtEncoderChannelStateVariableType.

The Sensor PtEncoderSensorType Object offers sensor related data. See section 7.3.1 for details.

The <Probe_x> PtEncoderProbeType Objects represent the probes provided by the Encoder. There shall be as many PtEncoderProbeType Objects as are needed to represent all probes provided. The BrowseNames shall be provided as defined by the template string <Probe_x>, where x is the probe number.

The PositionSensorSignalValue Variable contains the Encoder's position Signal encoded as numeric data type. Dependent on Encoder resolution, the data type may be 0:UInt32 or 0:UInt64. This is the raw signal value delivered by the encoder sensor.

The Resolution Variable contains the resolution of the Encoder's Position Variable Value.

The AbsolutePositionRange Variable contains the possible range of absolute position values represented as 0:Range Value.

The SignalType Variable contains the type of the position sensor's signal value encoded as PtEncoderChannelSignalTypeVariableType.

7.3.1 PtEncoderSensorType

Table 45 - PtEncoderSensorType Definition
AttributeValue
BrowseNamePtEncoderSensorType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariablePositionOffset0:Number0:BaseDataVariableTypeO, RO
0:HasComponentVariableLatchStatus0:UInt16PtLatchStatusVariableTypeO, RO
0:HasComponentVariableLatchValue0:Number0:BaseDataVariableTypeO, RO
Conformance Units
Powertrain Encoder Channel

The PositionOffset Variable contains the calculated offset belonging to the current preset value of the Encoder.

The LatchStatus Variable contains the current state of the reference pulse latch encoded as PtLatchStatusVariableType.

The LatchValue Variable contains the last latched value of the reference pulse latch.

7.3.2 PtEncoderProbeType

The PtEncoderProbeType represents the Encoder's probe functionality.

Table 46 - PtEncoderProbeType Definition
AttributeValue
BrowseNamePtEncoderProbeType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableLatchStatus0:UInt16PtLatchStatusVariableTypeO, RO
0:HasComponentVariableLastLatchedPos0:Number0:BaseDataVariableTypeM, RO
0:HasComponentVariableProbeInputSignal0:Boolean0:BaseDataVariableTypeO
Conformance Units
Powertrain Encoder Channel

The LatchStatus Variable contains the current state of the probe latch encoded as PtLatchStatusVariableType.

The LastLatchedPos Variable contains the last latched position of the probe.

The ProbeInputSignal Variable contains the status of the probe sensor at the clamp.

7.4 PtVibrationSensorType

The PtVibrationSensorType represents a vibration sensor and provides measurement values for velocity, vibration displacement and acceleration. The -X, -Y and -Z suffixes identify values provided individually for the x-, y- and z-direction.

Table 47 - PtVibrationSensorType Definition
AttributeValue
BrowseNamePtVibrationSensorType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableRMSAcceleration0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSAccelerationX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSAccelerationY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSAccelerationZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSVelocity0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSVelocityX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSVelocityY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSVelocityZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSDisplacement0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSDisplacementX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSDisplacementY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableRMSDisplacementZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakAcceleration0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakAccelerationX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakAccelerationY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakAccelerationZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakVelocity0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakVelocityX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakVelocityY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakVelocityZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakDisplacement0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakDisplacementX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakDisplacementY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariablePeakToPeakDisplacementZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakAcceleration0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakAccelerationX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakAccelerationY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakAccelerationZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakVelocity0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakVelocityX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakVelocityY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakVelocityZ0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakDisplacement0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakDisplacementX0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakDisplacementY0:FloatPtVibrationMeasurementVariableTypeO, RO
0:HasComponentVariableZeroToPeakDisplacementZ0:FloatPtVibrationMeasurementVariableTypeO, RO
Conformance Units
Powertrain Actual and Command Values

The RMSAcceleration, RMSAccelerationX, RMSAccelerationY and RMSAccelerationZ Variables contain the vibration acceleration KPI calculated via Root-Mean-Square based on DIN ISO 20816 series of standards.

The RMSVelocity, RMSVelocityX, RMSVelocityY and RMSVelocityZ Variables contain the standard vibration velocity KPI as defined in DIN ISO 20816-1, …-3 (Annex A) and …-9.

The RMSDisplacement, RMSDisplacementX, RMSDisplacementY and RMSDisplacementZ Variables contain the vibration displacement KPI calculated via Root-Mean-Square.

The PeakToPeakAcceleration, PeakToPeakAccelerationX, PeakToPeakAccelerationY and PeakToPeakAccelerationZ Variables contain the difference between maximum and minimum acceleration in the last interval based on DIN ISO 20816 series of standards.

The PeakToPeakVelocity, PeakToPeakVelocityX, PeakToPeakVelocityY and PeakToPeakVelocityZ Variables contain the difference between maximum and minimum velocity in the last interval.

The PeakToPeakDisplacement, PeakToPeakDisplacementX, PeakToPeakDisplacementY, PeakToPeakDisplacementZ Variables contain the standard vibration displacement KPI as defined in DIN ISO 20816-1, …-3 (Annex A) and …-9.

The ZeroToPeakAcceleration, ZeroToPeakAccelerationX, ZeroToPeakAccelerationY, ZeroToPeakAccelerationZ Variables contain the standard acceleration KPI as defined in DIN ISO 20816-1, …-3 (Annex A) and …-9.

The ZeroToPeakVelocity, ZeroToPeakVelocityX, ZeroToPeakVelocityY and ZeroToPeakVelocityZ Variables contain the difference between maximum and minimum velocity in the last interval.

The ZeroToPeakDisplacement, ZeroToPeakDisplacementX, ZeroToPeakDisplacementY and ZeroToPeakDisplacementZ Variables contain the difference between maximum and minimum displacement in the last interval.

7.5 PtCharacteristicsConverterType

The PtCharacteristicsConverterType represents the properties of the electric converter unit belonging to an electric drive.

Table 48 - PtCharacteristicsConverterType
AttributeValue
BrowseNamePtCharacteristicsConverterType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableBleederExcessCurrentLimit0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariableConverterExcessCurrentConfigured0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariableConverterThermalLoadLimitConfigured0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariableDcBusVoltageConfigured0:UInt160:AnalogUnitTypeO, RO
0:HasComponentVariableInputConverterAcInputVoltage0:UInt160:AnalogUnitTypeO, RO
0:HasComponentVariableOutputConverterPulseFrequency0:Float0:AnalogUnitTypeM, RO

The BleederExcessCurrentLimit Variable contains the excess current limit of the brake resistor in ampere.

The ConverterExcessCurrentConfigured Variable contains the excess current of the converter determined by configuration data.

The ConverterThermalLoadLimitConfigured Variable contains the thermal load limit of the converter determined by configuration data.

The DcBusVoltageConfigured Variable contains the voltage of the intermediate circuit determined by configuration data.

The InputConverterAcInputVoltage Variable contains the input alternating voltage.

The OutputConverterPulseFrequency Variable contains the pulse frequency of the converter.

7.6 PtTraversingTaskType

The PtTraversingTaskType represents a traversing task.

Table 49 - PtTraversingTaskType Definition
AttributeValue
BrowseNamePtTraversingTaskType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableTraversingTaskNumber0:Int320:BaseDataVariableTypeM, RO
0:HasComponentVariableTargetPosition0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariableVelocity0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariableAcceleration0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariableDeceleration0:Float0:AnalogUnitTypeO, RO
0:HasComponentVariablePositioningModuloMode0:UInt160:MultiStateValueDiscreteTypeM, RO
0:HasComponentVariablePositioningTaskChangeMode0:UInt160:MultiStateValueDiscreteTypeO, RO
Conformance Units
Powertrain Actual and Command Values

The TraversingTaskNumber Variable contains the number of the traversing task currently executed. Interpretation of TraversingTaskNumber:

TraversingTaskNumber ValueTraversing task executed
-5Jogging positive (S42)
-4Jogging negative (S42)
-3Homing procedure (S44)
-2MDI sub-mode active
-1No traversing task is executed: stand still (S41)
>=0Number of traversing task (0 - 1023)

If no traversing task is executed (TraversingTaskNumber == -1), the Value of all other Variables shall be 0. If a traversing task is executed (TraversingTaskNumber >=0), the AxisState Variable contains one of the values belonging to the S45 sub state machine (see [PDP], Figure 35 also).

The TargetPosition Variable contains the target position for the traversing task generator.

The Velocity Variable contains the desired speed for the traversing task generator.

The Acceleration Variable contains the desired acceleration for the traversing task generator.

The PositioningModuloMode Variable contains the information if the TargetPosition Variable must be interpreted as absolute or relative position encoded as 0:MultiStateValueDiscreteType defined in [OPC 10000-8]. The PositioningTaskChangeMode Variable corresponds to Bit 5 in DS402 control word " also encoded as 0:MultiStateValueDiscreteType. The content of their EnumStrings lookup table Properties is defined in Table 50.

Table 50 - PtTraversingTaskType Attribute values for child Nodes
BrowsePathValue Attribute
PositioningModuloMode
0:EnumValues

[

{ "Value":0,

"DisplayName": "NO_MODULO_FUNCTION",

"Description": "No traversing task is active"

},

{ "Value":1,

"DisplayName": "RELATIVE_POSITIONING",

"Description": "Relative Positioning"

},

{ "Value":2,

"DisplayName": "ABSOLUTE_SHORTEST_PATH_MODULO_DIRECTION _POSITIONING",

"Description": "The absolute position shall be reached by the shortest path"

},

{ "Value":3,

"DisplayName": "ABSOLUTE_POSITIVE_MODULO_DIRECTION _POSITIONING",

"Description": "The absolute position shall be reached by a motion in positive direction"

},

{ "Value":4,

"DisplayName": "ABSOLUTE_NEGATIVE_ MODULO_DIRECTION _POSITIONING",

"Description": "The absolute position shall be reached by a motion in negative direction"

}

]

PositioningTaskChangeMode
0:EnumValues

[

{ "Value":0,

"DisplayName": "CHANGE_TARGET_REACHED",

"Description": "Change traversing task after target position reached"

},

{ "Value":1,

"DisplayName": "CHANGE_IMMEDIATE",

"Description": "Change traversing task immediate"

}

]

The following table contains descriptions of the semantic for all possible Values of the PositioningModuloMode Variable.

7.7 PtSafetyType

The PtSafetyType contains PtSafetyFunctionType Variables describing basic settings for safety functions.

Table 51 - PtSafetyType Definition
AttributeValue
BrowseNamePtSafetyType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentObjectSTOPtSafetyFunctionTypeM
0:HasComponentObjectSS1PtSafetyFunctionTypeO
0:HasComponentObjectSS2PtSafetyFunctionTypeO
0:HasComponentObjectSOSPtSafetyFunctionTypeO
0:HasComponentObjectSLSPtSafetyFunctionTypeO
0:HasComponentObjectSDIPtSafetyFunctionTypeO
0:HasComponentObjectSLAPtSafetyFunctionTypeO
0:HasComponentObjectSLPPtSafetyFunctionTypeO
Conformance Units
Powertrain Safety

The STO Object represents the status of the "Safe torque off" safety function.

The SS1 Object represents the status of the "Safe stop 1" safety function.

The SS2 Object represents the status of the "Safe stop 2" safety function.

The SOS Object represents the status of the "Safe operating stop" safety function.

The SLS Object represents the status of the "Safely limited speed" safety function.

The SDI Object represents the status of the "Safe direction" safety function.

The SLA Object represents the status of the "Safely limited acceleration" safety function.

The SLP Object represents the status of the "Safely limited position" safety function.

If a specific safety function is supported by the Axis/DO, the representing PtSafetyFunctionType Object shall be provided.

7.8 PtSafetyFunctionType

The PtSafetyFunctionType represents the status of one safety function.

Table 52 - PtSafetyFunctionType Definition
AttributeValue
BrowseNamePtSafetyFunctionType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionOther
Subtype of the 0:BaseObjectType defined in OPC 10000-5.
0:HasComponentVariableSelectionState0:UInt160:MultiStateValueDiscreteTypeM, RO
0:HasComponentVariableActivationState0:UInt160:MultiStateValueDiscreteTypeM, RO
0:HasPropertyVariableLimit0:Float0:PropertyTypeO, RO
Conformance Units
Powertrain Safety

The SelectionState Variable represents the selection status of the represented safety function.

The ActivationState Variable represents the activation status of the represented safety function.

The Limit Variable represents the speed limit if representing the SLS safety function or the acceleration limit if representing the SLA safety function. Shall only be provided for these two safety functions.

Table 53 - PtSafetyFunctionType Attribute values for child Nodes
BrowsePathValue Attribute
SelectionState
0:EnumValues

[

{ "Value":0,

"DisplayName": "NONE",

"Description": "No safety function is selected"

},

{ "Value":1,

"DisplayName": "SELECTED",

"Description": "Safety function is selected"

},

{ "Value":2,

"DisplayName": "SELECTED_INTERN",

"Description": "Safety function is selected by internal client"

},

{ "Value":3,

"DisplayName": "SELECTED_EXTERN",

"Description": "Safety function is selected by external client"

},

{ "Value":4,

"DisplayName": "SELECTED_LIMIT_1",

"Description": "Safety function is selected with limit 1"

},

{ "Value":5,

"DisplayName": "SELECTED_LIMIT_2",

"Description": "Safety function is selected with limit 2"

},

{ "Value":6,

"DisplayName": "SELECTED_LIMIT_3",

"Description": "Safety function is selected with limit 3"

},

{ "Value":7,

"DisplayName": "SELECTED_LIMIT_4",

"Description": "Safety function is selected with limit 4"

},

{ "Value":8,

"DisplayName": "SELECTED_POS",

"Description": "Safety function positive direction selected"

},

{ "Value":9,

"DisplayName": "SELECTED_NEG",

"Description": "Safety function negative direction selected"

}

]

ActivationState
0:EnumValues

[

{ "Value":0,

"DisplayName": "NONE",

"Description": "No safety function is active"

},

{ "Value":1,

"DisplayName": "POWER_REMOVED",

"Description": "STO safety function is active"

},

{ "Value":2,

"DisplayName": "SS1_ACTIVE",

"Description": "SS1 safety function is active"

},

{ "Value":3,

"DisplayName": "SS1_ACTIVE_FAULTED",

"Description": "SS1 safety function is faulted"

},

{ "Value":4,

"DisplayName": "SS2_ACTIVE",

"Description": "SS2 safety function is active"

},

{ "Value":5,

"DisplayName": "SS2_ACTIVE_FAULTED",

"Description": "SS2 safety function is faulted"

},

{ "Value":6,

"DisplayName": "SOS_ACTIVE",

"Description": "SOS safety function is active"

},

{ "Value":7,

"DisplayName": "SOS_ACTIVE_FAULTED",

"Description": "SOS safety function is faulted"

},

{ "Value":8,

"DisplayName": "SLS_ACTIVE",

"Description": "SLS safety function is active"

},

{ "Value":9,

"DisplayName": "SLS_ACTIVE_FAULTED",

"Description": "SLS safety function is faulted"

},

{ "Value":10,

"DisplayName": "SDI_POS_ACTIVE",

"Description": "SDI positive safety function is active"

},

{ "Value":11,

"DisplayName": "SDI_NEG_ACTIVE",

"Description": "SDI negative safety function is active"

},

{ "Value":12,

"DisplayName": "SLA_ACTIVE",

"Description": "SLA safety function is active"

},

{ "Value":13,

"DisplayName": "SLA_ACTIVE_FAULTED",

"Description": "SLA safety function is faulted"

},

{ "Value":14,

"DisplayName": "SLP_ACTIVE",

"Description": "SLP safety function is active"

},

{ "Value":15,

"DisplayName": "SLP_ACTIVE_FAULTED",

"Description": "SLP safety function is faulted"

},

{ "Value":16,

"DisplayName": "SLP_INOPERABLE",

"Description": "SLP safety function is inoperable"

}

]

7.9 OPC UA Variable Mapping to PtFunctionType Properties

Table 54 lists the OPC UA Variables and the drive properties represented by Variables which are components of ObjectTypes specified above.

The Variables listed are components of a parent folder which belongs to the Object. The parent folder is specified in the row preceding the rows specifying the Variables which belong to this very folder.

The "Modelling Rule" columns have an entry for each ObjectType supporting the Variable listed in the respective row. If an ObjectType does not support the Variable, the respective column is empty. The modelling rules "optional" and "optional placeholder" are not distinguished.

Table 54 - Powertrain - Functional Model Properties represented by OPC UA Variables
PtFrequencyDriveAxisTypePtVelocityDriveAxisTypePtPositioningDriveAxisTypePtVelocityServoDriveAxisTypePtPositionServoDriveAxisTypePtTorqueServoDriveAxisTypePtEncoderAxisTypePtGearAxisType
BrowseNameModelling RuleDescription
Monitoring
AccelerationActualValueOOOOOOCurrent acceleration of motor or axis.
AccelerationCommandAdditiveValueOOOOAdditional additive value for AccelerationSetpoint (e.g. precontrol value from motion controller).
AccelerationSetpointOOOOOAcceleration setpoint as input for motor/axis control algorithm.
AxisTorqueForceOOOOOOOActual force or torque that is provided at the end of the full drive train. Differentiation via unit e.g. Nm or N. Shall be provided only if it differs from TorqueForceActualValue (e.g. a gear following the motor and the drive control command value refers to the motor and not to the powertrain output).
AxisOutputVelocityOOOOOOOActual velocity that is provided at the end of the full drive train. Can be interpreted as rotational velocity or linear velocity. Differentiation via unit e.g. rpm or m/s. Shall be provided only if it differs from VelocityActualValue (e.g. a gear following the motor and the velocity or drive control command value refers to the motor and not to the powertrain output).
AxisStateMMMMMMActual state of the Powertrain Axis Object' internal state machine, e.g. S2, encoded as 0:MultiStateValueDiscreteType. The content of the EnumStrings lookup table Property is defined in Table 20.
BrakeStateOOOOOOOActual brake status encoded as PtBrakeStateVariableType. The Variable shall not be provided if the Drive Axis has no brake.
ControlModeOOOOOOActive control function in the overall control cascade, e.g. SPEED_CONTROL_MODE, encoded as 0:MultiStateValueDiscreteType. The content of the EnumStrings lookup table Property is defined in Table 20.
ControlPriorityMMMMMMMOLeading control context, e.g. Fieldbus or Local, of the Powertrain Axis Object encoded as PtControlPriorityVariableType.
DeviceTemperatureOOOOOOOOActual device temperature. May be used if no separate motor and converter temperature is available.
<EncoderxTemperature>OOOOOOActual temperature of encoder feedback sensor.
FrequencyCommandValueMCommanded frequency value, transmitted from the controller to the drive by Fieldbus communication or analogue input clamp.
FrequencySetpointMOOOOOFrequency setpoint as input for motor/axis control algorithm.
GearInputShaftTurningDirectionOOOOOOOTurning direction of gear input shaft, encoded as PtShaftTurningDirectionVariableType.
GearInputTorqueOOOOOOOActual torque that is provided/measured to/at the gearbox input shaft.
GearInputVelocityOOOOOOOActual velocity that is provided/measured to/at the gearbox. Most commonly a rotational velocity.
GearOutputShaftTurningDirectionOOOOOOOTurning direction of gear output shaft, encoded as PtShaftTurningDirectionVariableType.
GearOutputTorqueOOOOOOOActual torque that is provided/measured at the end of the gearbox (classical rotational output)
GearOutputVelocityOOOOOOOActual rotational velocity that is provided/measured at the output shaft of the gearbox.
GearRatioOOOOOOMIf gear ratio is adjustable, active ratio should be shown here. Gear factor represented as ratio of input turns / output turns.
GearStateOOOOOOOIf there are multiple gear stages that can be switched the current "state" should be presented here. It is encoded as PtGearStateVariableType.
GearTemperatureOOOOOOOActual temperature for monitoring the gearbox. E.g. oil sump.
HomingStateMOOOHoming state (NOT_REFERENCED, REFERENCED).
MotorTemperatureOOOOOOActual motor temperature.
OverrideOActive override factor on programmed velocity in percent (100% == programmed velocity).
PositionActualValueOMOMMMCurrent position of motor or axis.
PositionCommandValueOMCommanded position of the controller.
PositionFollowingErrorOOActual difference between PositionSetpoint and PositionActualValue.
PositionSetpointOOSetpoint as input for motor/axis control algorithm.
ShaftTurningDirectionOOOOOOOOTurning direction of the shaft, encoded as PtShaftTurningDirectionVariableType.
TorqueForceActualValueOOOOOOActual axis torque. Means torque for a rotatory axis and force for a linear axis.
TorqueForceCommandAdditiveValueOOOOOAdditional value for commanded torque/force of the controller, transmitted by associated signal, or fixed offset value e.g. for compensation of weight or constant process forces.
TorqueForceCommandValueOOOCommanded torque/force value, transmitted from the controller to the drive by Fieldbus communication or analogue input clamp.
CurrentTorqueCommandValueOOOCommanded torque related current of the controller, transmitted by the associated Telegram Signal.
TorqueForceSetpointOOOOOTorque/Force setpoint as input for motor/axis control unit.
TraversingTaskMCurrent active/executed traversing task. May be commanded via fieldbus by PLC or is commanded by drive internal program execution. Details are visible at referenced PtTraversingTaskType Object.
VelocityActualValueOMMMMOOCurrent velocity of axis. Corresponds to VelocityCommandValue.
VelocityCommandAdditiveValueOOOAdditional additive value for Velocity Setpoint (e.g. precontrol value from motion controller).
VelocityCommandValueMMOCommanded velocity value, transmitted from the controller to the drive by Fieldbus communication or analogue input clamp.
VelocityFollowingErrorOOOOActual difference between VelocitySetpoint and VelocityActualValue.
VelocitySetpointMOOMVelocity setpoint as input for motor/axis control algorithm.
<VibrationSensor_x>OOOOOOOOPtVibrationSensorType Object representing an attached vibration sensor.
Maintenance
GearBacklashOOOOOOOMeasured value of wear.
GearMaintenanceStatusOOOOOOOOStatus indicator with the values "Green", "Yellow", "Red", encoded as PtMaintenanceStatusVariableType. Provided if no Gear x Object present.
GearOilRemainingUsefulLifetimeOOOOOOOORemaining hours until scheduled maintenance, in hours or percentage. Provided if no Gear x Object present.
<Gear_x>
MaintenanceStatus
OOOOOOOOStatus indicator with the values "Green", "Yellow", "Red", encoded as PtMaintenanceStatusVariableType.
<Gear_x>
OilRemainingUsefulLifetime
OOOOOOOORemaining hours until scheduled maintenance, in hours or percentage.
<Motor_x>, <Converter>, <Encoder_x> ,<Brake_x>, <Gear_x>
PowerOnDuration
OOOOOOOOActual duration of the power-on-state of motor x in milliseconds.
<Motor_x> , <Converter>, <Encoder_x> ,<Brake_x>, <Gear_x>
OperationDuration
OOOOOOOOActual duration of performing effective operation of motor x in milliseconds.
<Motor_x> , <Converter>, <Encoder_x> ,<Brake_x>, <Gear_x>
OperationCycleCounter
OOOOOOOONumber of switches of motor x between power-on and operation.
<Motor_x>PeakUtilizationOOOOOOOOUtilization of motor (converter) capacity, in % of converter load limit (0% - 100%), applies for motor x. Provide if global PeakUtilization Variable is not provided or not adequate.
<Motor_x>
RemainingUsefulLifetime
OOOOOOOORemaining hours until scheduled maintenance, in hours or percentage, applies for motor x. Provide if global RemainingUsefulLifetime Variable is not provided or not adequate.
<Motor_x>
ThermalCapacityUtilization
OOOOOOOOUtilization of motor thermal capacity, in % of motor load limit (0% - 100%), applies for motor x. Provide if global ThermalCapacityUtilization Variable is not provided or not adequate.
OperationCycleCounterOOOOOOOONumber of switches between power-on and operation.
OperationDurationOOOOOOOOActual duration of performing effective operation of the Powertrain Axis Object (e.g. the Drive's motor "works") in milliseconds.
PeakUtilizationOOOOOOOOUtilization of motor (converter) capacity, in % of converter load limit (0% - 100%).
PowerOnDurationOOOOOOOOActual duration of the power-on-state in milliseconds of the Powertrain Axis Object.
RemainingUsefulLifetimeOOOOOOOORemaining hours until scheduled maintenance, in hours or percentage.
ThermalCapacityUtilizationOOOOOOOOUtilization of motor (converter) thermal capacity, in % of converter load limit (0% - 100%).
CharacteristicsMotorAndControl
FeedbackModeOOOOOOSensing device used by closed loop control of the Powertrain Axis Object, e.g. FEEDBACK_SENSOR_1, encoded as 0:MultiStateValueDiscreteType. The content of the EnumStrings lookup table Property is defined in Table 20.
MotorForceRatedOOOOOORated force of a linear moving axis.
MotorPowerRatedMMMMMMRated power of the motor.
MotorSpeedRatedOOOOOORated speed of rotatory motor. If the motor of the axis does not work rotatory, the Variable shall not be provided.
MotorTorqueRatedOOOOOORated torque of the motor.
MotorTypeMMMMMMKind of motor, e.g. STEPPER, INDUCTION_ROTATORY, etc. encoded as 0:MultiStateValueDiscreteType. The content of the EnumStrings lookup table Property is defined in Table 20.
PositionFollowingErrorLimitOOOOOOMaximum allowed position deviation in the position closed loop control. Exceeding this limit causes position following error.
SpeedMaxConfiguredOOOOOOMaximum speed determined by configuration data.
TimePeriodPositionControlOOTime period for calculation of position control.
TimePeriodTorqueControlOOOOOTime period for calculation of torque control.
TimePeriodTrajectoryInterpolationOTime period for delivering of new trajectory setpoint.
TimePeriodVelocityControlOOOOOTime period for calculation of velocity control
TorqueMaxConfiguredOOOOOOMaximum torque determined by configuration data.
TrajectoryInterpolationModeOInterpolation mode of trajectory interpolator
VelocityFollowingErrorLimitOOOOOOMaximum allowed velocity deviation in the velocity closed loop control. Exceeding this limit causes velocity following error.
LimitSupervisionOOMOOO
SoftwarePosLimitHighMOMOSoftware upper position limit.
SoftwarePosLimitLowMOMOSoftware lower position limit.
TorqueLimitOOOOMOTorque limit of the motor.
TorqueLimitHighOOOMOOUpper torque limit of the motor.
TorqueLimitingOOOOIndicates if torque limiting is active.
TorqueLimitLowOOOMOOLower torque limit of the motor.
VelocityProfileMMMMM
JogPosInc1OOJogging position increment 1.
JogPosInc2OOJogging position increment 2.
JogSpeed1OOOOOOJogging setpoint 1 value (see [PDP], chapter 6.3.3.3.4).
JogSpeed2OOOOOOJogging setpoint 2 value (see [PDP], chapter 6.3.3.3.4).
MaximumVelocityOOOOOOHighest speed of the ramp-function.
MinimumVelocityOOOOOOLowest speed of the ramp-function.
NominalSpeedMMMMMOReference value for ramp up (down) used to calculate ramp acceleration (deceleration)
QuickStopVelocityRampDecelerationMMMMMOQuick stop ramp deceleration.
QuickStopVelocityRampDownTimeMMMMMOQuick stop ramp down time, in seconds.
VelocityRampAccelerationMMActual ramp acceleration.
VelocityRampDecelerationMMMMMOActual ramp deceleration.
VelocityRampDownTimeMMMMMOActual ramp down time of the RFG (see RfgRampUpTime above), in seconds
VelocityRampUpTimeMMActual ramp up time of the Ramp Function Generator (RFG), see [PDP], chapter 6.3.3, in seconds
CharacteristicsMechanicsOOOO
GearFactorPreciseOOOOOOOMay be used if GearRatio is not precise enough. Structure representing the Gear factor as ratio of input turns / output turns. Mechanical movement at the input to mechanical movement at the output (transmission factor).
GearRatioOOOOOOORotation to rotation transmission factor. Mechanical movement at the input to mechanical movement at the output (transmission factor). Shall be provided if a gear is present in the Powertrain Axis Object.
SpindlePitchOOOORotation to linear transmission factor. Mechanical movement at the input to mechanical movement at the output (transmission factor).
HomingMMMM
HomingDirectionOOHoming direction (POSITIVE or NEGATIVE)
HomingModeMOMOActive homing mode (ABSOLUTE, REF_MARK, DIST_CODE, FLY).
HomingPointOffsetOOHome position shift for adjustment of axis mechanical zero.
HomingSpeedToCamOOSpeed when moving to cam.
HomingSpeedToMarkOOSpeed when moving to mark.
Diagnosis
LogbookMMMMMMOOPtLogbookType mapping the content of the Powertrain Axis Object diagnosis system.
LogObjectOOOOOOOO0:LogObjectType (specified in OPC 10000-26) mapping the content of the Powertrain Axis Object diagnosis system.