Table 154defines the namespace metadata for this specification. The Objec namespace metadata is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See OPC 10000-5 for more details.
The information is provided as Object of the type NamespaceMetadataType. This Object is a component of the Namespace Object that is part of the Server Object . The NamespaceMetadataType ObjectType and its Propertiesare defined in OPC 10000-5.
The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in OPC 10000-6.
Table 154– NamespaceMetadata Object for this Specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
0:HasProperty |
NamespaceUri |
0:String |
||
|
0:HasProperty |
NamespaceVersion |
0:String |
1.0 |
|
|
0:HasProperty |
NamespacePublicationDate |
0:DateTime |
2020-05-01 |
|
|
0:HasProperty |
IsNamespaceSubset |
Bool |
False |
|
|
0:HasProperty |
StaticNodeIdTypes |
IdType[] |
|
|
|
0:HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
|
|
|
0:HasProperty |
Static0:StringNodeIdPattern |
0:String |
|
|
This section defines the corresponding Profilesand Conformance Unitsfor the OPC UA Information Model for Weighing Technology. Profilesare named groupings of Conformance Units. Facetsare Profilesthat will be combined with other Profiles to define the complete functionality of an OPC UA Server or Client.
The following tables specify the Facets available for servers that implement the Weighing Technology Companion Specification.
Table 155defines a Facet for servers that implement a simple scale device.
Table 155– Scales_Base_Scale Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
ScaleDeviceType |
Supports the handling of the ScaleDeviceType and the mandatory components of the type |
M |
|
Profile/Facets |
|
|
|
ComplexType Server Facet (defined in OPC 10000-7) |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 156defines a Facet for servers that implement a multi scale device with a ScaleSystemType. Figure 70shows an example of a scale system with two scales as subdevices: a catchweigher and a checkweigher.
Table 156– Scales_Scale_System Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
ScaleSystemType |
Supports the handling of the ScaleSystemType and the mandatrory components of the type |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale Facet |
M |
|
|
ComplexType Server Facet (defined in OPC 10000-7) |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Figure 70– Example of a Scale System
Table 157defines a Facet for servers that implement feeder subdevices.
Table 157– Scales_Feeder_Module Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
FeederModule |
Supports the handling of the FeederModuleType and the mandatrory components of the types |
M |
|
Profile/Facets |
|
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 158defines a Facet for servers that implement printer subdevices.
Table 158– Scales_Printer_Module Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
PrinterModule |
Supports the handling of the PrinterModuleType and the mandatrory components of the types |
M |
|
Profile/Facets |
|
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 159– Scales_Minimal_Production_Preset Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
ProductType |
Supports the handling of the ProductType. |
M |
|
StaticProductAddressSpace |
The product folder contains at least one product Object , but the objects are static in the address space (it is not possible to add or remove obejct from the product folder). To change product-related information, a product Object must be overwritten. |
M |
|
SelectProduct |
Supports the handling of the methods SelectProduct/deselectProduct |
O |
|
Profile/Facets |
|
|
|
Standard DataChange Subscription 2017 Server Facet |
O |
|
Table 160defines a Facet for servers that implement a full production solution. This solution requires a dynamic address space. For each product a product Object will be created with the method AddProduct.
Table 160– Scales_Full_Production_Preset Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
ProductType |
Supports the handling of the ProductType. |
M |
|
DynamicProductAddressSpace |
Supports ProductionPreset handling with dynamic address space (the server dynamically deletes and adds ProductType objects). |
M |
|
SelectProduct |
Supports the handling of the methods SelectProduct/deselectProduct |
M |
|
ManageProduct |
Supports the handling of the methods AddProduct/RemoveProduct |
M |
|
Profile/Facets |
|
|
|
Standard DataChange Subscription 2017 Server Facet |
O |
|
Table 161defines a Facet for servers that use only SI units or units derived from SI units.
Table 161– Scales_International_System_of_Units Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Display SI units |
Properties with the DataType 0:EUInformation only contains SI units or units derived from SI units |
M |
|
InputArgument_SI_units |
The OPC UA server only accepted SI units or units derived from SI units as InputArgument |
M |
|
Profile/Facets |
|
|
Table 162defines a Facet for servers that implement an AutomaticFillingScale.
Table 162– Scales_AutomaticFillingScale Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
AutomaticFillingScale |
Supports the handling of the AutomaticFillingScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 163defines a Facet for servers that implement a catchweigher.
Table 163– Scales_Catchweigher Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Catchweigher |
Supports the handling of the CatchweigherTyüe |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 164defines a Facet for servers that implement an automatic weight-price labeler.
Table 164– Scales_AutomaticWeightPriceLabeler_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
AutomaticFillingScale |
Supports the handling of the AutomaticWeightPriceLabelerType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 165defines a Facet for servers that implement a checkweigher.
Table 165– Scales_Checkweigher_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Checkweigher |
Supports the handling of the CheckweigherType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 166defines a Facet for servers that implement a continuous scale
Table 166– Scales_Continuous_Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
ContinuousScale |
Supports the handling of the ContinuousScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 167defines a Facet for servers that implement a loss in weight scale
Table 167– Scales_LossInWeight Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Loss In Weight Scale |
Supports the handling of the LossInWeightScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 168defines a Facet for servers that implement a piece counting scale.
Table 168– Scales_PieceCountingScale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
PieceCountingScale |
Supports the handling of the PieceCountingScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 169defines a Facet for servers that implement a recipe scale.
Table 169– Scales_RecipeScale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
RecipeScale |
Supports the handling of the RecipeScaleType |
M |
|
RecipeManagment |
Supports the handling of the RecipeManagmentType |
O |
|
DynamicRecipeManagment |
Supports the possiblity to add Recipe via OPC UA methods |
O |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 170defines a Facet for servers that implement a totalizing hopper scale.
Table 170– Scales_Totalizing_Hopper Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
TotalizingHopperScale |
Supports the handling of the TotalizingHopperScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 171defines a Facet for servers that implement a simple scale.
Table 171– Scales_Simple Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
SimpleScale |
Supports the handling of the SimpleScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 172defines a Facet for servers that implement a laboratory scale.
Table 172– Scales_Laboratory_Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
LaboratoryScale |
Supports the handling of the LaboratoryScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 173defines a Facet for servers that implement a hopper scale.
Table 173– Scales_Hopper_Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
HopperScale |
Supports the handling of the HopperScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 174defines a Facet for servers that implement a weighing bridge.
Table 174– Scales_Weighing Bridge_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
WeighingBridge |
Supports the handling of the WeighingModuleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Table 174defines a Facet for servers that implement a vehicle scale.
Table 175– Scales_Vehicle_Scale_Facets
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
VehicleScale |
Supports the handling of the VehicleScaleType |
M |
|
Profile/Facets |
|
|
|
Scales_Base_Scale_Facet |
M |
|
Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeIdand BrowseNameare identifiers. A Nodein the UA AddressSpaceis unambiguously identified using a NodeId. Unlike NodeIds, the BrowseNamecannot be used to unambiguously identify a Node. Different Nodesmay have the same BrowseName. They are used to build a browse path between two Nodesor to define a standard Property.
Serversmay often choose to use the same namespace for the NodeIdand the BrowseName. However, if they want to provide a standard Property, its BrowseNameshall have the namespace of the standard body although the namespace of the NodeIdreflects something else, for example the EngineeringUnits Property. All NodeIdsof Nodesnot defined in this specification shall not use the standard namespaces.
Table 176provides a list of mandatory and optional namespaces used in a weighing technology OPC UA server.
Table 176– Namespaces used in a Weighing Technology Server
|
NamespaceURI |
Description |
Use |
|
Namespace for NodeIdsand BrowseNamesdefined in the OPC UA specification. This namespace shall have namespace index 0. |
Mandatory |
|
|
Local Server URI |
Namespace for nodes defined in the local server. This may include types and instances used in an AutoID Device represented by the server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIdsand BrowseNamesdefined in OPC 10000-100. The namespace index is server specific. |
Mandatory |
|
|
Namespace for NodeIdsand BrowseNamesdefined in this specification. The namespace index is server specific. |
Mandatory |
|
|
Vendor-specific types and instances |
A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific namespace. |
Optional |
Table 177provides a list of namespaces and their index used for BrowseNamesin this specification. The default namespace of this specification is not listed since all BrowseNameswithout prefix use this default namespace.
Table 177– Namespaces used in this specification
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
2 |
2:DeviceRevision |