This ObjectType defines the structure of the Sercos Device Object. Figure 6 shows the SercosDeviceType. It is formally defined in Table 5.
Table 5 – SercosDeviceType Definition
|
Attribute |
Value |
|||
|
BrowseName |
SercosDeviceType |
|||
|
IsAbstract |
False |
|||
|
References |
NodeClass |
BrowseName |
TypeDefinition |
ModellingRule |
|
Inherit the Properties of the TopologyElementType defined in OPC UA for Devices companion specification. |
||||
|
Inherit the Properties of the DeviceType defined in OPC UA for Devices companion specification. |
||||
|
|
||||
|
HasComponent |
Object |
ParameterSet |
FunctionalGroupType |
Mandatory |
|
HasComponent |
Object |
ProfileSet |
FunctionalGroupType |
Mandatory |
|
HasComponent |
Object |
ClassSet |
FunctionalGroupType |
Mandatory |
|
HasComponent |
Object |
FunctionGroupSet |
FunctionalGroupType |
Mandatory |
The following Properties extend the OPC UA model according to the Sercos Information Model. They are mandatory for all SercosDeviceType instances.
Sercos devices have a device name. There are different Sercos Parameters to get a proper device name. The name of the Sercos device shall be the (operational) data from IDN S-0-1302.0.3 Application Type (e.g., main spindle drive, round axis, X axis, etc.). If this parameter is missing, the outdated data from IDN S-0-0142 (Application Type) may be taken (for compatibility issues). If both are missing, the Sercos device name shall be the data from IDN S-0-1300.0.4 (manufacturer specific device name). In absence of all of them the device name is the combination of the mandatory data of IDN S-0-1300.0.3 (Vendor Code) and IDN S-0-1300.0.5 (Vendor Device ID). The Vendor Code is a unique number assigned to each vendor. The Vendor Device ID is a unique device ID managed by the vendor, that indentifies the component number.
ParameterSet is inherited from TopologyElementType and mandatory for SercosDeviceType instances.
ProfileSet includes all Sercos Profile instances that are used within the Sercos device. Currently these are GDP, SCP and FSP. “ProfileSet” object is formally defined in Table 6.
Table 6 – ProfileSet Definition
|
Attribute |
Value |
|||
|
BrowseName |
ProfileSet |
|||
|
References |
NodeClass |
BrowseName |
TypeDefinition |
ModellingRule |
|
HasTypeDefinition |
ObjectType |
FunctionalGroupType |
|
|
|
HasComponent |
Object |
<SercosProfileIdentifier> |
SercosProfileType |
OptionalPlaceholder |
ClassSet includes all Sercos Class instances that are used within the Sercos device. “ClassSet” Object is formally defined in Table 7.
|
Attribute |
Value |
|||
|
BrowseName |
ClassSet |
|||
|
References |
NodeClass |
BrowseName |
TypeDefinition |
ModellingRule |
|
HasTypeDefinition |
ObjectType |
FunctionalGroupType |
|
|
|
HasComponent |
Object |
<SercosClassIdentifier> |
SercosClassType |
OptionalPlaceholder |
FuntionGroupSet includes all Sercos instances of SercosFunctionGroup. “FunctionGroupSet” is formally defined in Table 8.
Table 8 – FunctionGroupSet Definition
|
Attribute |
Value |
|||
|
BrowseName |
FunctionGroupSet |
|||
|
References |
NodeClass |
BrowseName |
TypeDefinition |
ModellingRule |
|
HasTypeDefinition |
ObjectType |
FunctionalGroupType |
|
|
|
HasComponent |
Object |
<SercosFunctionGroupIdentifier> |
SercosFunctionGroupType |
OptionalPlaceholder |