OPC UA Companion-Specification

OPC 40200

 

OPC UA for Weighing Technology

 

 

Release V1.00

2020-06

 

 

 

 

 

 

OPC 40200 (Edition 1.0, 2020-06) is identical with VDMA 40200:2020-06

 


 

VDMA Specification

June 2020

 

VDMA 40200

LDDG2W

 

ICS 17.100; 35.240.50

 

 

OPC UA Companion Specification for Weighing Technology

OPC UA Companion Specification für Wägetechnik

VDMA 40200:2020-06 (Version 1.0) is identical with OPC 40200 (Edition 1.0)

 

 

 

Document comprises 136 pages

VDMA

 

 

 

 

 

 

©  All rights reserved to VDMA e.V., Frankfurt/Main – Modification, amendment, editing, translation, copying and/or circulation
only with permission in writing from VDMA e.V.

 

VDMA 40200:2020-06


Contents

Page

Foreword. 11

1              Introduction. 12

1.1          General 12

1.2          Associations. 12

2              Scope. 12

3              Normative references. 13

4              Terms, definitions and conventions. 14

4.1          Overview.. 14

4.2          OPC UA for Weighing Technology terms. 14

4.3          Abbreviations and symbols. 16

4.4          Conventions used in this document 17

5              General Information on Weighing Technology and OPC UA. 20

5.1          Introduction to Weighing Technology Companion Specification. 20

5.2          Introduction to OPC Unified Architecture. 24

6              Use cases. 30

6.1          General 30

6.2          Accessing Data of measurement result and statisics. 30

6.3          Reserved for a further version. 31

6.4          Production Preset 31

7              Weighing Technology Information Model overview.. 31

7.1          General 31

7.2          Overview of generic Scales. 31

7.3          Modular scale devices. 32

7.4          Subtypes of the ScaleDeviceType. 33

8              OPC UA ObjectTypes. 34

8.1          FeederModuleType Definition. 34

8.2          PrinterModuleType Definition. 36

8.3          ScaleSystemType Definition. 37

8.4          ScaleDeviceType Definition. 40

8.5          WeighingRangeElementType Definition. 44

8.6          StatisticType Definition. 45

8.7          ProductionPresetType Definition. 47

8.8          ProductType Definition. 50

8.9          AutomaticFillingScaleType Definition. 52

8.10        AutomaticFillingProductType Definition. 53

8.11        CatchweigherType Definition. 55

8.12        CatchweigherProductType Definition. 56

8.13        WeighingItemType Definition. 59

8.14        AutomaticWeightPriceLabelerType Definition. 61

8.15        AutomaticWeightPriceLabelerProductType Definition. 61

8.16        PriceItemType Definition. 62

8.17        CheckweigherType Definition. 63

8.18        CheckweigherProductType Definition. 64

8.19        CheckweigherStatisticType Definition. 65

8.20        StatisticCounterType Definition. 67

8.21        AcceptedStatisticCounterType Definition. 69

8.22        RejectedStatisticCounterType Definition. 69

8.23        ZoneType Definition. 70

8.24        ContinuousScaleType Definition. 71

8.25        ContinuousProductType Definition. 72

8.26        LossInWeightScaleType Definition. 73

8.27        PieceCountingScaleType Definition. 75

8.28        PieceCountingProductType Definition. 77

8.29        RecipeScaleType Definition. 81

8.30        RecipeProductType Definition. 84

8.31        RecipeType Definition. 85

8.32        RecipeManagementType Definition. 87

8.33        RecipeElementType Definition. 89

8.34        ActivationType Definition. 89

8.35        ConditionSleepType Definition. 90

8.36        AnalogConditionSleepType Definition. 91

8.37        EdgeTriggeredSleepType Definition. 92

8.38        TimerType Definition. 93

8.39        UserInstructionType Definition. 94

8.40        WeighingType Definition. 95

8.41        MaterialAutomaticType Definition. 96

8.42        TotalizingHopperScaleType Definition. 97

8.43        TotalizingHopperProductType Definition. 97

8.44        SimpleScaleType Definition. 98

8.45        SimpleProductType Definition. 99

8.46        LaboratoryScaleType Definition. 99

8.47        HopperScaleType Definition. 103

8.48        VehicleScaleType Definition. 104

8.49        VehicleProductType Definition. 107

8.50        WeighingModuleType Definition. 111

8.51        MaterialType Definition. 111

8.52        FloatingStatisticType Definition. 112

8.53        TotalizerType Definition. 113

9              OPC UA EventTypes. 113

9.1          ScaleEventType Definition. 114

9.2          ScaleAlarmType Definition. 115

10           OPC UA VariableTypes. 116

10.1        TargetItemType. 116

10.2        MeasuredItemType. 117

10.3        WeightItemType. 117

11           OPC UA DataTypes. 119

11.1        AbstractWeightType. 119

11.2        PrintableWeightType. 120

11.3        WeightType. 120

11.4        RecipeReportElementType. 120

11.5        RecipeTargetValueType. 121

11.6        EqualityAndRelationalOperator 121

11.7        EdgeOperator 122

11.8        DraftShieldType. 122

11.9        TareMode. 122

11.10     ToleranceState. 122

12           ReferenceType. 123

12.1        NextRecipeElementType. 123

13           Profiles and Namespaces. 123

13.1        Namespace Metadata. 123

13.2        Conformance Units and Profiles. 124

13.3        Server Facets. 124

13.4        Handling of OPC UA Namespaces. 128

Annex A       (normative)  Weighing Technology Namespace and mappings. 130

Annex B       (normative)  Recipe and Recipe Management 132

Annex C       (normative)  Event and Alarm Categories. 134

Annex D       (informative)  Example. 136

 

 

 

 

Figures

Figure 1 – Schematic view of a scale system.. 21

Figure 2 – Scale Types Classification. 22

Figure 3 – Schematic Overview of a Loss In Weight scale. 23

Figure 4 – Overview of a Product handle. 24

Figure 5 – The Scope of OPC UA within an Enterprise. 25

Figure 6 – A Basic Object in an OPC UA Address Space. 26

Figure 7 – The Relationship between Type Definitions and Instances. 27

Figure 8 – Examples of References between Objects. 28

Figure 9 – The OPC UA Information Model Notation. 28

Figure 10 – Notation Overview of the OPC UA Weighing Technology information model 32

Figure 11 – Modular scale devices and scale systems. 33

Figure 12 – Overview of the scale types in the information model 34

Figure 13 – Overview FeederModuleType. 35

Figure 14 – Overview PrinterModuleType. 36

Figure 15 – Overview ScaleSystemType. 38

Figure 16 – Overview ScaleDeviceType. 41

Figure 17 – Overview WeighingRangeElementType. 44

Figure 18 – Overview StatisticType. 46

Figure 19 – Overview ProductionPresetType. 47

Figure 20 – Overview ProductType. 51

Figure 21 – Overview AutomaticFillingScaleType. 53

Figure 22 – Overview AutomaticFillingProductType. 54

Figure 23 – Overview CatchweigherType. 56

Figure 24 – Overview CatchweigherProductType. 57

Figure 25 – Orientation of an Object 58

Figure 26 – Overview WeighingItemType. 60

Figure 27 – Overview AutomaticWeightPriceLabelerType. 61

Figure 28 – Overview AutomaticWeightPriceLabelerProductType. 62

Figure 29 – Overview PriceItemType. 63

Figure 30 – Overview CheckweigherType. 63

Figure 31 – Overview CheckweigherProductType. 64

Figure 32 – Overview CheckweigherStatisticType. 65

Figure 33 – Overview StatisticCounterType. 68

Figure 34 – Overview ZoneType. 70

Figure 35 – Overview ContinuousScaleType. 71

Figure 36 – Overview ContinuousProductType. 73

Figure 37 – Overview LossInWeightScaleType. 74

Figure 38 – Overview PieceCountingScaleType. 75

Figure 39 – Overview PieceCountingProductType. 78

Figure 40 – Overview RecipeScaleType. 81

Figure 41 – Overview RecipeProductType. 84

Figure 42 – Overview RecipeType. 85

Figure 43 – Overview RecipeManagementType. 87

Figure 44 – Overview RecipeElementType. 89

Figure 45 – Overview ActivationType. 90

Figure 46 – Overview ConditionSleepType. 91

Figure 47 – Overview AnalogConditionSleepType. 92

Figure 48 – Overview EdgeTriggeredSleepType. 93

Figure 49 – Overview TimerType. 94

Figure 50 – Overview UserInstructionType. 94

Figure 51 – Overview WeighingType. 95

Figure 52 – Overview MaterialAutomaticType. 96

Figure 53 – Overview TotalizingHopperScaleType. 97

Figure 54 – Overview TotalizingHopperProductType. 97

Figure 55 – Overview SimpleScaleType. 98

Figure 56 – Overview SimpleProductType. 99

Figure 57 – Overview LaboratoryScaleType. 100

Figure 58 – Overview HopperScaleType. 103

Figure 59 – Overview VehicleScaleType. 105

Figure 60 – Overview VehicleProductType. 108

Figure 61 – Overview WeighingModuleType. 111

Figure 62 – Overview MaterialType. 111

Figure 63 – Overview FloatingStatisticType. 112

Figure 64 – Overview TotalizerType. 113

Figure 65 – Overview ScaleEventType. 114

Figure 66 – Overview ScaleAlarmType. 115

Figure 67 – Overview TargetItemType. 116

Figure 68 – Overview MeasuredItemType. 117

Figure 69 – Overview WeightItemType. 118

Figure 70 – Example of a Scale System.. 124

Figure B.1 – Sequential part of a recipe with two recipe steps. 132

Figure B.2 – Forking part of a recipe with two simultaneous steps. 132

Figure B.3 – Joining part of a recipe waiting on two other steps. 133

Figure D.1 − Overview of a Server with a SimpleScale. 136

 

Tables

Table 1 – Normative references. 13

Table 2 – General Terms. 15

Table 3 – Examples of DataTypes. 17

Table 4 – Type Definition Table. 18

Table 5 – Common Node Attributes. 19

Table 6 – Common Object Attributes. 19

Table 7 – Common Variable Attributes. 20

Table 8 – Common VariableType Attributes. 20

Table 9 – Common VariableType Attributes. 20

Table 10 – Overview of scale types. 22

Table 11 – RelativePath. 30

Table 12 – FeederModuleType Definition. 35

Table 13 – SetFeederSpeed Method Arguments. 36

Table 14 – SetFeederSpeed Method AddressSpace definition. 36

Table 15 – PrinterModuleType Definition. 37

Table 16 – ScaleSystemType Definition. 39

Table 17 – ScaleSystemType Additional Subcomponents. 39

Table 18 – ScaleDeviceType Definition. 42

Table 19 – ScaleDeviceType Additional Subcomponents. 43

Table 20 – SetPresetTare Method Arguments. 43

Table 21 – SetPresetTare Method AddressSpace definition. 43

Table 22 – WeighingRangeElementType Definition. 45

Table 23 – WeighingRangeElementType Additional Subcomponents. 45

Table 24 – StatisticType Definition. 46

Table 25 – ProductionPresetType Definition. 48

Table 26 – AddProduct Method Arguments. 48

Table 27 – AddProduct Method AddressSpace definition. 49

Table 28 – SelectProduct Method Arguments. 49

Table 29 – SelectProduct Method AddressSpace definition. 49

Table 30 – DeselectProduct Method Arguments. 49

Table 31 – DeselectProduct Method AddressSpace definition. 49

Table 32 – RemoveProduct Method Arguments. 50

Table 33 – RemoveProduct Method AddressSpace definition. 50

Table 34 – SwitchProduct Method Arguments. 50

Table 35 – SwitchProduct Method AddressSpace definition. 50

Table 36 – ProductType Definition. 52

Table 37 – AutomaticFillingScaleType Definition. 53

Table 38 – AutomaticFillingProductType Definition. 55

Table 39 – CatchweigherType Definition. 56

Table 40 – CatchweigherProductType Definition. 57

Table 41 – AddZone Method Arguments. 58

Table 42 – AddZone Method AddressSpace definition. 59

Table 43 – RemoveZone Method Arguments. 59

Table 44 – RemoveZone Method AddressSpace definition. 59

Table 45 – WeighingItemType Definition. 60

Table 46 – AutomaticWeighPriceLabelerType Definition. 61

Table 47 – AutomaticWeightPriceLabelerProductType Definition. 62

Table 48 – AutomaticWeightPriceLabelerProductType Additional Subcomponents. 62

Table 49 – PriceItemType Definition. 63

Table 50 – PriceItemType Additional Subcomponents. 63

Table 51 – CheckweigherType Definition. 64

Table 52 – CheckweigherProductType Definition. 64

Table 53 – CheckweigherStatisticType Definition. 66

Table 54 – StatisticCounterType Definition. 68

Table 55 – AcceptedStatisticCounterType Definition. 69

Table 56 – RejectedStatisticCounterType Definition. 70

Table 57 – ZoneType Definition. 70

Table 58 – ContinuousScaleType Defintion. 72

Table 59 – ContinuousProductType Definition. 73

Table 60 – LossInWeightScaleType Definition. 74

Table 61 – PieceCountingScaleType. 76

Table 62 – SetReferencePieceWeight Method Arguments. 76

Table 63 – SetReferencePieceWeight Method AddressSpace definition. 76

Table 64 – StartReference Method Arguments. 77

Table 65 – StartReference Method AddressSpace definition. 77

Table 66 – SetNumberOfReferencePieces Method Arguments. 77

Table 67 – SetNumberOfReferencePieces Method AddressSpace definition. 77

Table 68 – PieceCountingProductType Definition. 79

Table 69 – SetTargetItemCount Method Arguments. 80

Table 70 – SetTargetItemCount Method AddressSpace definition. 80

Table 71 – SetTargetPieceCount Method Arguments. 80

Table 72 – SetTargetPieceCount Method AddressSpace definition. 81

Table 73 – RecipeScaleType Definition. 82

Table 74 – StartRecipe Method Arguments. 82

Table 75 – StartRecipe Method AddressSpace definition. 82

Table 76 – StopRecipe Method Arguments. 83

Table 77 – StopRecipe Method AddressSpace definition. 83

Table 78 – ContinueRecipe Method Arguments. 83

Table 79 – ContinueRecipe Method AddressSpace definition. 83

Table 80 – SkipCurrentRecipeElement Method Arguments. 83

Table 81 – SkipCurrentRecipeElement Method AddressSpace definition. 84

Table 82 – AbortRecipe Method Arguments. 84

Table 83 – AbortRecipe Method AddressSpace definition. 84

Table 84 – RecipeProductType Definition. 85

Table 85 – RecipeType Definition. 86

Table 86 – AddRecipeElement Method Arguments. 86

Table 87 – AddRecipeElement Method AddressSpace definition. 86

Table 88 – RemoveRecipeElement Method Arguments. 87

Table 89 – RemoveRecipeElement Method AddressSpace definition. 87

Table 90 – RecipeManagementType Definition. 88

Table 91 – AddRecipe Method Arguments. 88

Table 92 – AddRecipe Method AddressSpace definition. 88

Table 93 – RemoveRecipe Method Arguments. 89

Table 94 – RemoveRecipe Method AddressSpace definition. 89

Table 95 – RecipeElementType Definition. 89

Table 96 – ActivationType Definition. 90

Table 97 – ConditionSleepType Definition. 91

Table 98 – Possible Conditions for AnalogConditionSleepType. 92

Table 99 – AnalogConditionSleepType Definition. 92

Table 100 – Possible Conditions for EdgeTriggeredSleepType. 93

Table 101 – EdgeTriggeredSleepType Definition. 93

Table 102 – TimerType Definition. 94

Table 103 – UserInstructionType Definition. 95

Table 104 – WeighingType Definition. 96

Table 105 – MaterialAutomaticType Definition. 96

Table 106 – TotalizingHopperScaleType Definition. 97

Table 107 – TotalizingHopperProductType Definition. 98

Table 108 – SimpleScaleType Definition. 98

Table 109 – SimpleProductType Definition. 99

Table 110 – SimpleProductType Additional Subcomponents. 99

Table 111 – LaboratoryScaleType Definition. 101

Table 112 – CloseDraftShields Method Arguments. 102

Table 113 – CloseDraftShields Method AddressSpace definition. 102

Table 114 – OpenDraftShields Method Arguments. 102

Table 115 – OpenDraftShields Method AddressSpace definition. 102

Table 116 – HopperScaleType Definition. 104

Table 117 – HopperScaleType Additional Subcomponents. 104

Table 118 – Proccess of vehicle weighing. 105

Table 119 – VehicleScaleType Definition. 105

Table 120 – InboundWeighing Method Arguments. 106

Table 121 – InboundWeighing Method AddressSpace definition. 106

Table 122 – OutboundWeighing Method Arguments. 106

Table 123 – OutboundWeighing Method AddressSpace definition. 106

Table 124 – OnePassWeighing Method Arguments. 107

Table 125 – OnePassWeighing Method AddressSpace definition. 107

Table 126 – VehicleProductType Definition. 109

Table 127 – VehicleProductType Additional Subcomponents. 110

Table 128 – GetVehicleInformation Method Arguments. 110

Table 129 – GetVehicleInformation Method AddressSpace definition. 110

Table 130 – WeighingModuleType Definition. 111

Table 131 – MaterialType Definition. 112

Table 132 – FloatingStatisticType Definition. 112

Table 133 – TotalizerType Definition. 113

Table 134 – ScaleEventType Definition. 114

Table 135 – ScaleAlarmType Definition. 115

Table 136 – TargetItemType Definition. 116

Table 137 – MeasuredItemType Definition. 117

Table 138 – WeightItemType Definition. 119

Table 139 – AbstractWeightType Definition. 120

Table 140 – PrintableWeightType Definition. 120

Table 141 – PrintableWeightType Structure. 120

Table 142 – WeightType Definition. 120

Table 143 – WeightType Structure. 120

Table 144 – RecipeReportElementType Definition. 121

Table 145 – RecipeReportElementType Structure. 121

Table 146 – RecipeTargetValueType Definition. 121

Table 147 – RecipeTargetValueType Structure. 121

Table 148 – EqualityAndRelationalOperator Definition. 122

Table 149 – EdgeOperator Definition. 122

Table 150 – DraftShieldType Definition. 122

Table 151 – TareMode Definition. 122

Table 152 – ToleranceState Definition. 123

Table 153 – NextRecipeElementType Definition. 123

Table 154 – NamespaceMetadata Object for this Specification. 123

Table 155 Scales_Base_Scale Facet 124

Table 156 Scales_Scale_System Facet 124

Table 157 Scales_Feeder_Module Facet 125

Table 158 Scales_Printer_Module Facet 125

Table 159 Scales_Minimal_Production_Preset Facet 125

Table 160 Scales_Full_Production_Preset Facet 125

Table 161 Scales_International_System_of_Units Facets. 126

Table 162 Scales_AutomaticFillingScale Facets. 126

Table 163 Scales_Catchweigher Facets. 126

Table 164 Scales_AutomaticWeightPriceLabeler_Facets. 126

Table 165 Scales_Checkweigher_Facets. 126

Table 166 – Scales_Continuous_Scale_Facets. 126

Table 167 – Scales_LossInWeight Scale_Facets. 127

Table 168 – Scales_PieceCountingScale_Facets. 127

Table 169 – Scales_RecipeScale_Facets. 127

Table 170 – Scales_Totalizing_Hopper Scale_Facets. 127

Table 171 – Scales_Simple Scale_Facets. 127

Table 172 – Scales_Laboratory_Scale_Facets. 127

Table 173 – Scales_Hopper_Scale_Facets. 128

Table 174 – Scales_Weighing Bridge_Facets. 128

Table 175 – Scales_Vehicle_Scale_Facets. 128

Table 176 – Namespaces used in a Weighing Technology Server 128

Table 177 – Namespaces used in this specification. 129

Table C.1 – Defined NotificationCategories. 134

Table C.2 – Defined NotificationIds. 134

 


 

OPC FOUNDATION, VDMA

AGREEMENT OF USE

 

COPYRIGHT RESTRICTIONS

 

·          This document is provided "as is" by the OPC Foundation and the VDMA

·          Right of use for this specification is restricted to this specification and does not grant rights of use for referred documents.

·          Right of use for this specification will be granted without cost.

·          This document may be distributed through computer systems, printed or copied as long as the content remains unchanged and the document is not modified.

·          OPC Foundation and VDMA do not guarantee usability for any purpose and shall not be made liable for any case  using the content of this document.

·          The user of the document agrees to indemnify OPC Foundation and VDMA and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.

·          The document shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

·          The intellectual property and copyright is solely owned by the OPC Foundation and the VDMA.

 

PATENTS

 

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or VDMA specifications may require use of an invention covered by patent rights. OPC Foundation or VDMA shall not be re sponsible for identifying patents for which a license may be required by any OPC or VDMA specification, or for conducting legal inquiries into the legal validi ty  or scope of those patents that are brought to its attention. OPC or VDMA specifications are pr ospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

 

WARRANTY AND LIABILITY DISCLAIMERS

 

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CON TAIN ERRORS OR MISPRINTS. THE OPC FOUDATION NOR VDMA MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION NOR VDMA BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING  LOSS  OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

 

The entire risk as to the quality and performance of software developed using this specification is borne by the user of this specification.

 

RESTRICTED RIGHTS LEGEND

 

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227 -7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260 -1830

 

TRADEMARKS

 

Most computer and software brand names have trademarks or registered trademarks. The  individual  trademarks have not been listed here.

 

GENERAL PROVISIONS

 

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

 

This Agreement shall be governed by and construed under the laws of Germany.

 

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification

Foreword

This project was initiated by twelve leading scale manufacturers in conjunction with the VDMA to develop a standardized open and manufacturer-independent interface for weighing instruments in OPC UA format. The initiative was officially registered with the OPC Foundation, the umbrella organization for the development of interoperability standards for industrial automation, as an international Joint Working Group.

The standardization enables a broad and international application of the open communication interface. Therefore, the initiating manufacturer group has already started a close exchange of information with CECIP, the European Association of Weighing Instruments Manufacturers, at an early stage. Further international partner associations and companies have been invited to cooperate on the new standard.

The twelve members of the initiating group of manufacturers are:

·         Bizerba SE & Co.KG

·         Espera-Werke GmbH

·         Hottinger Baldwin Messtechnik GmbH

·         Kern & Sohn GmbH

·         Mettler Toledo International Inc

·         Minebea Intec GmbH

·         RHEWA Waagenfabrik August Freudewald GmbH & Co.KG

·         Sartorius Lab Instruments GmbH & Co.KG

·         Schenck Process Europe GmbH

·         Siemens AG

·         SysTec Systemtechnik und Industrieautomation GmbH

·         Wipotec GmbH

 


 

1       Introduction

1.1       General

This document presents the OPC UA Companion Specification for Weighing Technology and covers different scale systems. The document is the result of the “VDMA OPC UA Weighing Technology Inititative” Working Group initially founded by the VDMA, Frankfurt a. M., Germany and including members of international leading manufacturers of weighing technology devices and metrology institutions.

1.2       Associations

1.2.1      VDMA Measuring and Testing Technology

The Mechanical Engineering Industry Association (VDMA) represents more than 3,200 member companies in the SME-dominated mechanical and systems engineering industry in Germany and Europe. VDMA Measuring and Testing Technology and its more than 180 manufacturers have joined forces in a collaborative platform representing the interests of the Measuring and Testing Technology industry vis-à-vis national and international authorities as well as in other business circles.

The Weighing Technology Department brings together around 60 manufacturers of industrial scales, fine and precision scales, shop scales as well as household and personal scales.

1.2.2      OPC Foundation

OPC is the interoperability standard for the secure and reliable exchange of data and information in the industrial automation space and in other industries. It is platform independent and ensures the seamless flow of information among devices from multiple vendors. The OPC Foundation is responsible for the development and maintenance of this standard.

OPC UA is a platform independent service-oriented architecture that integrates all the functionality of the individual OPC Classic specifications into one extensible framework. This multi-layered approach accomplishes the original design specification goals of:

      Platform independence: from an embedded microcontroller to cloud-based infrastructure

      Secure: encryption, authentication, authorization and auditing

      Extensible: ability to add new features including transports without affecting existing applications

      Comprehensive information modelling capabilities: for defining any model from simple to complex

2       Scope

The joint VDMA and OPC Foundation Working Group “VDMA OPC UA Weighing Technology Initiative” developed an OPC UA information model for communication of scale systems. Scale systems are defined as devices within a value chain that measure the weight or mass flow of a product or Object containing serveral additional parameters (e.g. price, tare of packaging, etc.). Scale systems stand for a complete weight measuring device that includes one or multiple scales. The scales may fulfill different use cases within one scale system (e.g. filling and price labeling). Each scale consists of one or multiple load cells which capture the weight. It is the smallest unit regarding the components of a scale system within this Companion Specification.

The OPC UA Weighing Technology Companion Specification covers the following scale system types directly: Automatic Filling Scales, catchweigher (Automatic Price Labeling Scales, Automatic Weight Labeling Scales, checkweigher), Continuously Scales, Hopper Scales, Laboratory Scales, Piece Counting Scales, Simple Scales, Totalizing Scales and Vehicle Scales.

Other scale systems including weighing bridges may be modeled based on this Companion Specification, but probably need to be extended by certain parameters.

NOTE: The scale systemclass “Retail Scales” is excluded by this information model. At this time there is no relevance for an OPC UA interface and therefore there is no information modelled for representing these devices.

 

3       Normative references

The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

Table 1 – Normative references

Document

Version

OPC 10000-1, OPC Unified Architecture - Part 1: Overview and Concepts

http://www.opcfoundation.org/UA/Part1/

 

OPC 10001-1, OPC Unified Architecture - Amendment 1: AnalogItem Types

http://www.opcfoundation.org/UA/Amendment1/

 

OPC 10000-3, OPC Unified Architecture - Part 3: Address Space Model

http://www.opcfoundation.org/UA/Part3/

 

OPC 10000-4, OPC Unified Architecture - Part 4: Services

http://www.opcfoundation.org/UA/Part4/

 

OPC 10000-5, OPC Unified Architecture - Part 5: Information Model

http://www.opcfoundation.org/UA/Part5/

 

OPC 10000-7, OPC Unified Architecture - Part 7: Profiles

http://www.opcfoundation.org/UA/Part7/

 

OPC 10000-8, OPC Unified Architecture - Part 8: Data Access

http://www.opcfoundation.org/UA/Part8/

 

OPC 10000-9, OPC Unified Architecture - Part 9: Alarms and Conditions

http://www.opcfoundation.org/UA/Part9/

 

OPC 10000-10, OPC Unified Architecture - Part 10: Programs

http://www.opcfoundation.org/UA/Part10/

 

OPC 10000-11, OPC Unified Architecture - Part 11: Historical Access

http://www.opcfoundation.org/UA/Part11/

 

OPC 10000-100, OPC Unified Architecture - Part 100: Devices

http://www.opcfoundation.org/UA/Part100/

 

OPC 10001-1, OPC Unified Architecture - Amendment 1: AnalogItem Types

http://www.opcfoundation.org/UA/Amendment1/

 

OPC 10001-10, OPC Unified Architecture - Amendment 10: Currency

http://www.opcfoundation.org/UA/Amendment10/

 

 

 

https://opcfoundation.org/developer-tools/specifications-opc-ua-information-models/opc-ua-packml-companion-specification/

 

 

 

The International Vocabulary of Basic and General Terms in Metrology (VIM)

2.9

International Vocabulary of Legal Metrology (VIML)

V1 - 2013

OIML D 11 General requirements for measuring instruments - Environmental conditions

2011

OIML D 31 General requirements for software controlled measuring instruments

2008

OIML R 50 - Continuous totalizing automatic weighing instruments (belt weighers)

2014

OIML R 51 - Automatic catchweighing instruments

2006

OIML R 61 - Automatic gravimetric filling instruments

2017

OIML R 76 - Non-automatic weighing instruments

2006

OIML R 107 - Discontinuous totalizing automatic weighing instruments (totalizing hopper weighers)

2007

WELMEC 6.4 - Guide for packers and importers of e-marked prepacked products

June 2005

 

4       Terms, definitions and conventions

4.1       Overview

For this specification it is assumed that basic concepts of OPC UA information modelling are understood. This specification will use these concepts to describe the OPC UA for the Weighing Technology Companion Specification Information Model. For the purpose of this document, the terms and definitions given in OPC 10000- 1, OPC 10000-3, OPC 10000- 4, OPC 10000- 5, OPC 10000- 7, OPC 10000- 100, OPC UA for PackML as well as in the following apply.

NOTE: OPC UA terms and terms defined in this specification are italicized in the specification.

4.2       OPC UA for Weighing Technology terms

The terminology used in this specification conforms to

·                     The International Vocabulary of Legal Metrology (VIML)

·                     Basic and General Terms in Metrology (VIM)

·                     D 11 General requirements for measuring instruments - Environmental conditions

·                     R 76 Non-automatic weighing instruments,

·                     D 31 General requirements for software controlled measuring instruments.

In addition the following definitions apply.

4.2.1      General Terms

Table 2 – General Terms

Term

Definition

Actual scale interval,d

Value expressed in units of mass of:

the difference between the values corresponding to two consecutive scale marks, for analog indication; or

the difference between two consecutive indicated values, for digital indication.

(OIML R51)

Automatic scale

An instrument that weighs without the intervention of an operator and follows a predetermined program of automatic processes, which are characteristic of the instrument.

Current weight

Defines the current value that is measured at the sensor at the concurrent timestamp. Might be a highly fluctuating value.

Division

Value of the smallest increment. See also (atual scale interval, verification scale interval)

Feeder

Devices for conveying the product to or from the weighing module

Flow rate

The flow rate is a measured value passes per unit of time. The flow rate can be defined as mass flow rate (flow of mass m through a surface per unit time t)

or as volumetric flow rate (flow of volume of fluid V through a surface per unit time t)

Gross value

Indication of the weight value of a load on an instrument, with no tare or preset tare device in operation. (see OIML R 76)

Weight of an objective or sample (net weight) including its container or packaging (tare weight)

Height

In direction of global gravity.

Item

A physical product in scales that process a set of physical products like catchweigher. In case a “productType” represented a set of physical products the single physical product is called item.

Length

In direction of travel.

Load

Amount of product that is currently introducing the force on the load receptor. (OIML R61)

A general term for any Object when it is intended to convey the meaning that this Object is exerting a weight force

Measurement result

Set of quantity values being attributed to a measurand together with any other available relevant information (see VIM 2.9)

Net value

Indication of the weight value of a load placed on an instrument after operation of a tare device. (see OIML R 76)

The weight of a material or sample after deducting the weight of its packaging or of the transport instrument (tare weight)

PackML

“PackML stands for Packaging Machine Language and is an interface standard originally used inbatch manufacturing in the packaging industry but which is now used in multiple different types of production and assembly lines.” (see OPC UA for PackML)

Preset tare value

Numerical value, representing a weight value, that is introduced into the instrument. It is a predetermined tare value that is used for one or several weighings. (see OIML R 76)

Product

For the purposes of this Companion Specification, a product is a physical good that is processed by a weighing system. Depending on the type of scale and type of good, the result may be a single weighing and/or a statistical evaluation of many weighing operations. Additional process steps (e.g. metal detection) can also be performed. A OPC UA Object of type "productType" represented a physical product or a set of physical products and contain additional (meta-)informations like a target value or some identifier.


 

Proportional tare

Tare value that is determined by the scale automatically and that is proportional to the gross weight.

Recipe

See Annex B

RegisteredWeight

Defines the last valid measurement that was recorded and will be used for further processing..

Scale

Synonym: weighing instrument

Measuring instrument that serves to determine the mass of an amount of material by using the action of gravity on this material.

 

NOTE: In this Recommendation “mass” (or “weight value”) is preferably used in the sense of “conventional mass” or “conventional value of the result of weighing in air” according to OIML R 111 and OIML D 28, whereas “weight” is preferably used for an embodiment (= material measure) of mass that is regulated in regard to its physical and metrological characteristics.

The instrument may also be used to determine other quantities, magnitudes, parameters or characteristics related to mass. According to its method of operation, a weighing instrument is classified as automatic or non-automatic. (See OIML R 76)

Scale division

See division

Scale system

A scale system is the combination of several scales that are addressed by a common interface. A scale system can have additional functions, such as a state machine or a production preset.

Setpoint

Time at which an action is triggered

Standard deviation

A quantity expressing by how much the members of a group differ from the mean value for the group.

Tare value,T

Weight value of a load, determined by a tare weighing device. (see OIML R 76)

The mass of packaging or transport container of the material that ist beeing weighed

Target value

Requested value of a variable size at a given time and under specified conditions. (see IEC 60050)

Tolerable Negative Error (TU1) for prepackages

Only a small number of prepackages may have a content below the nominal quantity minus the maximum permissible error (TU1-limit) (not more than 2.5%). These prepackages are known and referred to as ‘defectives’ (see Welmec 6.4)

TU2-limit

No prepackage with a quantity of product less than the nominal quantity minus twice  the  tolerable negative error (TU2-limit) may be ℮-marked. (see Welmec 6.4)

Verification scale interval, e

Value, expressed in units of mass, used for the classification and verification of an instrument. (OIML R51)

Weighing

Process of determining the mass of a load using the effect of gravity on that load (OIML R61)

Weighing bridge

Mechanical component of the scale that carry the load. One or more load cells are integrated into the WeighingBridge as an element of mass determination.

Weighing good id

Defines the identifier of an Object that is to be weighed (load)

Weighing instrument

Synonym: scale

Weighing module

Part of the weighing instrument that comprises all mechanical and electronic devices (i.e. load receptor, load-transmitting device, load cell, and analog data processing device or digital data processing device) but not having the means to display the weighing result. It may optionally have devices for further processing (digital) data and operating the instrument. (OIML R76)

Weighing range

The range of a scale can measure a mass. A scale can have several weighing ranges with different scale divisions

Width

In third possible orthogonal direction to height and length

4.2.2      State machine terms

The terms for state machine defined in OPC UA for PackML[1].

4.3       Abbreviations and symbols

value

 

mean value

AC

Alarm and Condition

DCS

Distributed Control Systems

G

Gross

HMI

Human Machine Interface

HTTP

Hypertext Transfer Protocol

IP

Internet Protocol

L

Load

N

Net

OIML

International Organization of Legal Metrology

PT

Preset tare

T

Tare

TCP

Transmission Control Protocol

TU1

lower tolerance limit

 

count

 

standard deviation

4.4       Conventions used in this document

4.4.1      Conventions for Node descriptions

Node definitions are specified using tables (see Table 4).

Attributes are defined by providing the Attribute name and a value, or a description of the value.

References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass.

      If the TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table.

      The DataType is only specified for Variables; “[<number>]” indicates a single-dimensional array, for multi-dimensional arrays the expression is repeated for each dimension (e.g. [2][3] for a two-dimensional array). For all arrays the ArrayDimensions is set as identified by <number> values. If no <number> is set, the corresponding dimension is set to 0, indicating an unknown size. If no number is provided at all the ArrayDimensions can be omitted. If no brackets are provided, it identifies a scalar DataType and the ValueRank is set to the corresponding value (see OPC 10000-3). In addition, ArrayDimensions is set to null or is omitted. If it can be Any or ScalarOrOneDimension, the value is put into “{<value>}”, so either “{Any}” or “{ScalarOrOneDimension}” and the ValueRank is set to the corresponding value (see OPC 10000-3) and the ArrayDimensions is set to null or is omitted. Examples are given in Table 3.

Table 3 – Examples of DataTypes

Notation

Data­Type

Value­Rank

Array­Dimensions

Description

Int32

Int32

-1

omitted or null

A scalar Int32.

Int32[]

Int32

1

omitted or {0}

Single-dimensional array of Int32 with an unknown size.

Int32[][]

Int32

2

omitted or {0,0}

Two-dimensional array of Int32 with unknown sizes for both dimensions.

Int32[3][]

Int32

2

{3,0}

Two-dimensional array of Int32 with a size of 3 for the first dimension and an unknown size for the second dimension.

Int32[5][3]

Int32

2

{5,3}

Two-dimensional array of Int32 with a size of 5 for the first dimension and a size of 3 for the second dimension.

Int32{Any}

Int32

-2

omitted or null

An Int32 where it is unknown if it is scalar or array with any number of dimensions.

Int32{ScalarOrOneDimension}

Int32

-3

omitted or null

An Int32 where it is either a single-dimensional array or a scalar.

 

      The TypeDefinition is specified for Objects and Variables.

      The TypeDefinition column specifies a symbolic name for a NodeId, i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node.

      The ModellingRule of the referenced component is provided by specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace, the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object .

If the NodeId of a DataType is provided, the symbolic name of the Node representing the DataType shall be used.

Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType, their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition.

Table 4 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point to the Node definition.

Table 4 – Type Definition Table

Attribute

Value

Attribute name

Attribute value. If it is an optional Attribute that is not set “--“ will be used.

 

 

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

ReferenceType name

NodeClass of the TargetNode.

BrowseName of the target Node. If the Reference is to be instantiated by the server, then the value of the target Node’s BrowseName is “--“.

DataType of the referenced Node, only applicable for Variables.

TypeDefinition of the referenced Node, only applicable for Variables and Objects.

Referenced ModellingRule of the referenced Object .

NOTE: Notices referencing footnotes of the table content.

 

Components of Nodes can be complex that is containing components by themselves. The TypeDefinition, NodeClass, DataType and ModellingRule can be derived from the type definitions, and the symbolic name can be created as defined in 4.4.3.1. Therefore, those containing components are not explicitly specified; they are implicitly specified by the type definitions.

4.4.2      NodeIds and BrowseNames

4.4.2.1      NodeIds

The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.

The symbolic name of each Node defined in this specification is its BrowseName, or, when it is part of another Node, the BrowseName of the other Node, a “.”, and the BrowseName of itself. In this case “part of” means that the whole has a 0:HasProperty or 0:HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique name in this specification, the symbolic name is unique.

The namespace for all NodeIds defined in this specification is defined in Annex A The namespace for this NamespaceIndex is Server-specific and depends on the position of the namespace URI in the server namespace table.

NOTE: This specification not only defines concrete Nodes, but also requires that some Nodes shall be generated, for example one for each Session running on the Server. The NodeIds of those Nodes are Server-specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this specification, because they are not defined by this specification but generated by the Server.

4.4.2.2      BrowseNames

The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes. The NamespaceIndex for all BrowseNames defined in this specification is defined in Annex A.

If the BrowseName is not defined by this specification, a namespace index prefix like ‘0:EngineeringUnits’ or ‘2:DeviceRevision’ is added to the BrowseName. This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this specification. Table 18 provides a list of namespaces and their indexes as used in this specification.

4.4.3      Common Attributes

4.4.3.1      General

The Attributes of Nodes, their DataTypes and descriptions are defined in OPC 10000-3. Attributes not marked as optional are mandatory and shall be provided by a Server. The following tables define if the Attribute value is defined by this specification or if it is server-specific.

For all Nodes specified in this specification, the Attributes named in Table 3 shall be set as specified in the table.

Table 5 – Common Node Attributes

Attribute

Value

DisplayName

The DisplayName is a 0:LocalizedText. Each server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId “en”. Whether the server provides translated names for other LocaleIds is server-specific.

Description

Optionally a server-specific description is provided.

NodeClass

Shall reflect the NodeClass of the Node.

NodeId

The NodeId is described by BrowseNames as defined in 4.4.2.1.

WriteMask

Optionally the WriteMask Attribute can be provided. If the WriteMask Attribute is provided, it shall set all non-server-specific Attributes to not writable. For example, the Description Attribute may be set to writable since a Server may provide a server-specific description for the Node. The NodeId shall not be writable, because it is defined for each Node in this specification.

UserWriteMask

Optionally the UserWriteMask Attribute can be provided. The same rules as for the WriteMask Attribute apply.

RolePermissions

Optionally server-specific role permissions can be provided.

UserRolePermissions

Optionally the role permissions of the current Session can be provided. The value is server-specifc and depend on the RolePermissions Attribute (if provided) and the current Session.

AccessRestrictions

Optionally server-specific access restrictions can be provided.

 

4.4.3.2      Objects

For all Objects specified in this specification, the Attributes named in Table 4 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

Table 6 – Common Object Attributes

Attribute

Value

EventNotifier

Whether the Node can be used to subscribe to Events or not is server-specific.

 

4.4.3.3      Variables

For all Variables specified in this specification, the Attributes named in Table 5 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

 

Table 7 – Common Variable Attributes

Attribute

Value

MinimumSamplingInterval

Optionally, a server-specific minimum sampling interval is provided.

AccessLevel

The access level for Variables used for type definitions is server-specific, for all other Variables defined in this specification, the access level shall allow reading; other settings are server-specific.

UserAccessLevel

The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least one user.

Value

For Variables used as InstanceDeclarations, the value is server-specific; otherwise it shall represent the value described in the text.

ArrayDimensions

If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific.

If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the Variable.

Historizing

The value for the Historizing Attribute is server-specific.

AccessLevelEx

If the AccessLevelEx Attribute is provided, it shall have the bits 8, 9, and 10 set to 0, meaning that read and write operations on an individual Variable are atomic, and arrays can be partly written.

 

4.4.3.4      VariableTypes

For all VariableTypes specified in this specification, the Attributes named in Table 6 shall be set as specified in the table. The definitions for the Attributes can be found in

Table 8 – Common VariableType Attributes

Attributes

Value

Value

Optionally a server-specific default value can be provided.

ArrayDimensions

If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific.

If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType.

4.4.3.5      Methods

For all Methods specified in this specification, the Attributes named in Table 7 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

Table 9 – Common VariableType Attributes

Attributes

Value

Executable

All Methods defined in this specification shall be executable (Executable Attribute set to “True”), unless it is defined differently in the Method definition.

UserExecutable

The value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user.

 

5       General Information on Weighing Technology and OPC UA

5.1       Introduction to Weighing Technology Companion Specification

Scales are used in a wide range of applications. Therefore, this section describes the schematic structure of a scale and includes a simple classification of scale types.

5.1.1      Schematic Structure of a Scale system

In addition to the definition of a scale of OIML R76 the following definition applies:

A scale is a computer system, device or measuring instrument used to determine the mass or mass flow of a quantity of material and consisting of one or more weighing modules (including load receptor, load-transmitting device, load cell and data processing device) and additional modules or peripheral devices (see Figure 1). Each weighing module determines a mass. The weighing result of the scale may be the result of one weighing module or the addition of several weighing modules. Not all partial results need to be included in the result.

In addition, a scale can also have subdevices such as printers or feeder systems. Each scale needs a data processing device and at least one interface like a display or field bus. Thus, an interaction other than OPC UA is always possible.

Figure 1 – Schematic view of a scale system

Each scale provides a specific set of functions. These functions can be divided into three categories. The basic set of functions is available for all scales and behaves the same way for all scales. The scale type functions depend on the scale types (see Section 5.1.2) and behave the same within this type. An example is the administration of zones at the checkweigher or the administration of recipes at the recipe scale. In addition, further functions or applications can be specifically defined by a vendor.

A scale system is the combination of several scales that are addressed by a common interface and can have additional functions, such as a state machine or a production preset. However, a scale must be included in any case.

The schematic described here is a significant simplification of scales and focuses on the external representation of entire scale systems. It does not include any metrological details. In addition, real systems can deviate significantly from this schematic.

5.1.2      Introduction into scale classification

This classification of the scales is based on the aspect of communication via OPC UA. If possible, existing classifications (e.g. from OIML) were used. However, further conflicting classifications may exist. Since the boundaries are partly fluid, some devices can be assigned to several scale types. The resulting classification is shown in Figure 2.

Figure 2 – Scale Types Classification

The definitions of the individual types can be found in Table 10.

Table 10 – Overview of scale types

Term

Definition

Automatic Filling Scale

Instrument which fills containers with predetermined and virtually constant mass of product from bulk by automatic weighing, and which comprises essentially automatic feeding device(s) associated with weighing unit(s) and the appropriate control and discharge devices. (Definition is based on OIML R61)

Catchweighing Scale (catchweigher)

Automatic weighing instrument that weighs pre-assembled discrete loads or single loads of loose material. (Definition is based on OIML OIML R51)

Automatic Weight Labeling Scale

catchweigher that labels individual pre-assembled discrete loads (e.g. prepackages) with the weight value. (Definition is based on OIML OIML R51)

Automatic Price Labeling Scale

catchweigher that calculates the price to pay on the basis of the indicated mass and the unit price and labels individual pre-assembled discrete loads (e.g. prepackages with the weight value, unit price and price to pay). (Definition is based on OIML OIML R51)

checkweigher

catchweigher that sub-divides prepackages of different mass into two or more sub-groups according to the value of the difference between their mass and the nominal set point. (Definition is based on OIML OIML R51)

Continuous Scale

An automatic weighing instrument for continuously weighing a bulk product on a conveyor belt, without systematic subdivision of the mass and without interrupting the movement of the conveyor belt. (Definition is based on OIML OIML R50)

Loss In Weight Scale

A special type of continuous scale is the loss in weight scale. It works according to the principle of controlled material increase or removal. The weight of the material is weighed by load cells and the change in weight per time unit is determined. The change in weight corresponds to the actual feed rate of the feeder when filling or emptying is stopped.

A schematic overview is shown in Figure 3.


 

Piece Counting Scale

A scale that can determine the number of parts in the load. A reference weight must first be determined or stored.

Recipe Weighing Scale

Scale with the capacity to manage and process recipes. Single recipe steps in a recipe can be the weighing of ingredients, the display of user instructions, the monitoring of switching values or the activation of aggregates.

Simple Scale

Simple scales do not have any major functional extensions and provide only basic weighing functionality, i.e. acting as a sensor.

Hopper Scale

A scale for weighing a bulk product with a tank, box or hopper mounted on one or more weighing bridges. The primary use case is tank level monitoring.

 

Laboratory Scale

The laboratory scales have a particularly high resolution and represent highly sensitive measuring insturments. For this reason, additional processes and measures are necessary in order to carry out an accurate measurement. For this purpose, e.g. the shielding of the environment with additional signs may be necessary.

Totalizing Hopper Scale

 

An automatic weighing instrument that weighs a bulk product by dividing it into discrete loads, determining the mass of each discrete load in sequence, summing the weighing results and delivering the discrete loads to bulk. (Definition is based on OIML OIML R107)

Vehicle Scale

Automatic or non-automatic scale having one or more weight bridges that determines the mass of a vehicle. The vehicle is typically a truck with or without a trailer or a rail wagon.

A special variant is the automatic rail-weighbridge (see OIML R106), which has one or more load receptors, including rails for the transport of rail vehicles, which determine the mass of the wagons and/or of the entire train by weighing during travel.

 

 

 

Figure 3 – Schematic Overview of a Loss In Weight scale

5.1.3      Product HandleHandling of product-related information

In addition to measuring, scales may also perform other tasks such as managing product data (production presetting and statistics/production output). To ensure that product-related information does not become inconsistent during the weighing process, it must be protected accordingly. For this purpose, a corresponding product information handle model shown in Figure 4is described in this Companion Specification. It defines two different modes (ProductHandleMode/AccessRestrictionMode).

Figure 4 – Overview of a Product handle

The ProductHandleMode indicates if a product can currently be processed by the scale or not. It is possible that the product-related information can be writeable or read only in both modes. The transition between the two states of the mode can be triggered internally in the scale or via the OPC UA methods selectProduct, DeselectProduct, SwitchProduct (see sections 8.7 - 8.8). In some cases it is possible that several products are in the "Processing" mode. For example, a catchweigher can process different products in parallel, while a continuous scale can only process one product at a time.

The AccessRestritionMode can be used to define the access restriction of the product. A client can make a set of changes (e.g. multiple write operations and method calls) only when the mode is in "WritableMode". This mode applies to the entire product Object , including all components such as zones. The access level of all child nodes of the product Object should at least have written access and the method should be executable. The AccessRestritionMode is used via the LockingService descripted in OPC 10000-100.

NOTE 1: When a physical product is to be processed but is not in the correct mode or has no OPC UA representation, the behaviour of the scale is application-specific and must be specified separately.

NOTE 2: The combination of the "Processing" mode and the "Writeable" mode should be used with caution, as the writeable element may be in an inconsistent state.

5.2       Introduction to OPC Unified Architecture

5.2.1      What is OPC UA?

OPC UA is an open and royalty free set of standards designed as a universal communication protocol. While there are numerous communication solutions available, OPC UA has key advantages:

      A state of art security model (see OPC 10000-2).

      A fault tolerant communication protocol.

      An information modelling framework that allows application developers to represent their data in a way that makes sense to them.

OPC UA has a broad scope which delivers for economies of scale for application developers. This means that a larger number of high quality applications at a reasonable cost are available. When combined with semantic models such as Weighing Technology Companion Specification, OPC UA makes it easier for end users to access data via generic commercial applications.

The OPC UA model is scalable from small devices to ERP systems. OPC UA Servers process information locally and then provide that data in a consistent format to any application requesting data - ERP, MES, PMS, Maintenance Systems, HMI, Smartphone or a standard Browser, for examples. For a more complete overview see OPC 10000- 1.

5.2.2      Basics of OPC UA

As an open standard, OPC UA is based on standard internet technologies, like TCP/IP, HTTP, Web Sockets.

As an extensible standard, OPC UA provides a set of Services (see OPC 10000- 4) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information in a standard way. More importantly all OPC UA Clients are expected to be able to discover and use vendor-defined information. This means OPC UA users can benefit from the economies of scale that come with generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users.

OPC UA Clients can be any consumer of data from another device on the network to browser based thin clients and ERP systems. The full scope of OPC UA applications is shown in Figure 5.

Figure 5 – The Scope of OPC UA within an Enterprise

OPC UA provides a robust and reliable communication infrastructure having mechanisms for handling lost messages, failover, heartbeat, etc. With its binary encoded data, it offers a high-performing data exchange solution. Security is built into OPC UA as security requirements become more and more important especially since environments are connected to the office network or the internet and attackers are starting to focus on automation systems.

5.2.3      Information modelling in OPC UA

5.2.3.1      Concepts

OPC UA provides a framework that can be used to represent complex information as Objects in an AddressSpace which can be accessed with standard services. These Objects consist of Nodes connected by References. Different classes of Nodes convey different semantics. For example, a Variable Node represents a value that can be read or written. The Variable Node has an associated DataType that can define the actual value, such as a 0:String, float, structure etc. It can also describe the Variable value as a variant. A Method Node represents a function that can be called. Every Node has a number of Attributes including a unique identifier called a NodeId and non-localized name called as BrowseName. An Object representing a ‘Reservation’ is shown in Figure 6.

Figure 6 – A Basic Object in an OPC UA Address Space

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 7 illustrates the relationship between an instance and its TypeDefinition.

The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 7 the PersonType ObjectType defines two children: First Name and Last Name. All instances of PersonType are expected to have the same children with the same BrowseNames. Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed to search for children based on the BrowseNames from the type instead of NodeIds. This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers implement.

OPC UA also supports the concept of sub-typing. This allows a modeller to take an existing type and extend it. There are rules regarding sub-typing defined in OPC 10000-3, but in general they allow the extension of a given type or the restriction of a DataType. For example, the modeller may decide that the existing ObjectType in some cases needs an additional Variable. The modeller can create a subtype of the ObjectType and add the Variable. A Client that is expecting the parent type can treat the new type as if it was of the parent type. Regarding DataTypes, subtypes can only restrict. If a Variable is defined to have a numeric value, a sub type could restrict it to a float.

Figure 7 – The Relationship between Type Definitions and Instances

References allow Nodes to be connected in ways that describe their relationships. All References have a ReferenceType that specifies the semantics of the relationship. References can be hierarchical or non-hierarchical. Hierarchical references are used to create the structure of Objects and Variables. Non-hierarchical are used to create arbitrary associations. Applications can define their own ReferenceType by creating subtypes of an existing ReferenceType. Subtypes inherit the semantics of the parent but may add additional restrictions. Figure 8 depicts several References, connecting different Objects.

Figure 8 – Examples of References between Objects

The figures above use a notation that was developed for the OPC UA specification. The notation is summarized in Figure 9. UML representations can also be used; however, the OPC UA notation is less ambiguous because there is a direct mapping from the elements in the figures to Nodes in the AddressSpace of an OPC UA Server.

Figure 9 – The OPC UA Information Model Notation

A complete description of the different types of Nodes and References can be found in OPC 10000-3 and the base structure is described in OPC 10000- 5.

OPC UA specification defines a very wide range of functionality in its basic information model. It is not expected that all Clients or Servers support all functionality in the OPC UA specifications. OPC UA includes the concept of Profiles, which segment the functionality into testable certifiable units. This allows the definition of functional subsets (that are expected to be implemented) within a Companion Specification. The Profiles do not restrict functionality, but generate requirements for a minimum set of functionality (see OPC 10000- 7)

5.2.3.2      Namespaces

OPC UA allows information from many different sources to be combined into a single coherent AddressSpace. Namespaces are used to make this possible by eliminating naming and id conflicts between information from different sources. Namespaces in OPC UA have a globally unique 0:String called a NamespaceUri and a locally unique integer called a NamespaceIndex. The NamespaceIndex is only unique within the context of a Session between an OPC UA Client and an OPC UA Server. The Services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values.

There are two types of values in OPC UA that are qualified with Namespaces: NodeIds and QualifiedNames. NodeIds are globally unique identifiers for Nodes. This means the same Node with the same NodeId can appear in many Servers. This, in turn, means Clients can have built in knowledge of some Nodes. OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model.

QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames; however, instances do not have that restriction.

5.2.3.3      Companion Specifications

An OPC UA Companion Specification for an industry specific vertical market describes an Information Model by defining ObjectTypes, VariableTypes, DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects as entry points into the AddressSpace.

5.2.4      RelativePath

A RelativePath is a structure that describes a sequence of References and Nodes to follow. Annex A of OPC Part 4 Services describes a text format for a RelativePath that can be used in documentation or in files used to store configuration information.

The components of a RelativePath text format are specified in Table 11.

Table 11 – RelativePath

Symbol

Meaning

/

The forward slash character indicates that the Server is to follow any subtype of HierarchicalReferences.

.

The period (dot) character indicates that the Server is to follow any subtype of a Aggregates ReferenceType.

<[#!ns:]ReferenceType>

A 0:String delimited by the ‘<’ and ‘>’ symbols specifies the BrowseName of a ReferenceType to follow. By default, any References of the subtypes the ReferenceType are followed as well. A ‘#’ placed in front of the BrowseName indicates that subtypes should not be followed.

A ‘!’ in front of the BrowseName is used to indicate that the inverse Reference should be followed.

The BrowseName may be qualified with a namespace index (indicated by a numeric prefix followed by a colon). This namespace index is used specify the namespace component of the BrowseName for the ReferenceType. If the namespace prefix is omitted then namespace index 0 is used.

[ns:]BrowseName

A 0:String that follows a ‘/’, ‘.’ or ‘>’ symbol specifies the BrowseName of a target Node to return or follow. This BrowseName may be prefixed by its namespace index. If the namespace prefix is omitted then namespace index 0 is used.

Omitting the final BrowseName from a path is equivalent to a wildcard operation that matches all Nodes which are the target of the Reference specified by the path.

&

The & sign character is the escape character. It is used to specify reserved characters that appear within a BrowseName. A reserved character is escaped by inserting the ‘&’ in front of it. Examples of BrowseNames with escaped characters are:

Received browse path name Resolves to

“&/Name_1” “/Name_1”

“&.Name_2” “.Name_2”

“&:Name_3” “:Name_3”

“&&Name_4” “&Name_4”

 

6       Use cases

6.1       General

This Weighing Technology Companion Specification describes how a scale system is addressed via OPC UA. For this purpose, the following primary use cases for the different scale types from section 5.1.2 were considered. Other use cases can also be covered or specified in other standards (vendor or Companion Specification).

In all defined use cases the scale system usually has the role of an OPC UA server. Therefore, this specification describes and defines the way an OPC UA client can read or write data and control the scale system via OPC UA. A scale system may also have a different interface (e.g. an HMI) that can control the scale as well. Some peripheral devices (e.g. printer, feeder) are also described in this specification but the communication between the peripheral devices and the scale is not part of the description.

NOTE: The OPC UA Companion Specification for Weighing Technology does not take into account any use cases that are affected by legal requirements (like official verification). For example, further parameters may be necessary for external data access or existing parameters may not be read out. A country-specific extension of the Companion Specification would be conceivable.

6.2       Accessing Data of measurement result and statisics

An important application of a scale is the data access of individual measurement results. In many cases, the measurement result is a weight value with a unit derived from the weight (e.g. flow rate, volume,...). A distinction can be made between the continuous display of the measured value (called “current Weight”) and a measurement (internal or external) that has been registered (called “registered Weight”). A registration could be triggered from an OPC UA-Client. The use case also includes the needed meta-data (e.g. product id, unit) for identifiing the result in further processing.

In some cases, the individual measurement result is not or only minor relevant. In some cases a statistic (mean value, standard deviation) over several measured values or over a period of time is required.

6.3       Reserved for a further version

Reserved for a further version.

6.4       Production Preset

Part of the access of a higher-level system to a weighing system is the management of products. This standard describes a way of creating, editing and selecting products on the scale. The entire information flow via OPC UA can also run completely or in parts via different interfaces. The schematic structure of production management is described in Section 5.1.3.

NOTE: For recipe scales, this use case also includes the creation, editing and administration of recipes. Recipe management is based on the OPC UA Companion Specification for machine vision. The structure and concept for recipes are described in section 5.1.4 and Annex B.

7       Weighing Technology Information Model overview

7.1       General

The information model for Weighing Technology has three main aspects: the generic part for all scale devices, the production management and the scale type specific part.

7.2       Overview of generic Scales

Figure 10 shows an overview of the different ObjectTypes for the Weighing Technology devices and the references to the types from the Companion Specification for devices. Four subtypes of the ComponentType are defined:

·         FeederModuleType

·         PrinterModuleType

·         ScaleSystemType

·         ScaleDeviceType

The entrypoint of a server is an instance of the ScaleSystemType or a ScaleDeviceType. The ScaleSystemType represents a multi-scale system and includes one ore more scales and has some common information (e.g. serial number). The ScaleDeviceType is abstract and only subtypes of it can be instantiated (see section 7.3). Both Types (ScaleDeviceType and ScaleSystemType) can optionally have an Object of the ProductionPresetType (see section 8.7) and/or an Object (called ProductionOutput) of the StatisticType.

Figure 10 shows the most important Object types used in the information model and the relations between them.

Figure 10 – Notation Overview of the OPC UA Weighing Technology information model

 

7.3       Modular scale devices

A modular scale device is represented by a (subtype of) ScaleDeviceType or ScaleSystemType that is composed of a top-device and a set of subdevices (modules). It uses the modular devices concept of OPC UA Companion Specification for Devices (see OPC 10000-100 9.2). The modules (subdevices) of modular scale devices are aggregated in the SubDevices Object . The SupportedTypes folder for SubDevices is used to maintain the set modules that can be added to the ScaleDevice or scale system(see Figure 11).

Figure 11 – Modular scale devices and scale systems

This Companion Specification defines the following supported types (including the subtypes) for the ScaleDeviceType:

      FeederModuleType

      PrinterModuleType

      WeighingModuleType

This Companion Specification defines the following supported type (including the subtypes) for the ScaleSystemType:

      ScaleDeviceType

The SupportedTypes folder may only refer to a subset of all possible subdevices for the modular device. Other vendor-specific modules or modules of other Companion Specifications can be defined. For more details of the concepte see OPC 10000-100.

7.4       Subtypes of the ScaleDeviceType

In the information model different subtypes of a ScaleDeviceType are defined for the different scale types (see section 5.1.2). For many subtypes of the ScaleDeviceType, a subtype of the ProductType exists as a counterpart. The ProductFolder defined in the ScaleDeviceType is overload and can only contain the specific subtype of the ProductType or a subtype of them.

Figure 12 shows the main Object types used in the information model and the relations between them.

Figure 12 – Overview of the scale types in the information model

 

8       OPC UA ObjectTypes

8.1       FeederModuleType Definition

8.1.1      Overview

The FeederModuleType defines the structure of an Object of the FeederModuleType. Figure 13 shows the hierarchical structure and details of the composition. It is formally defined in Table 12.

An Object of the FeederModuleType represents a feeder system. A feeder system is a subdevice of an automatic scale for conveying the product (e.g. a belt or a screw conveyor) to or from the weighingBridge. A feeder must be part of another device (e.g. an Object of the ScaleDeviceType).

The Type defines a general communication interface for a feeder system. It contains only variables and methods.

Figure 13 – Overview FeederModuleType

 

8.1.2      ObjectType Definition

Table 12 – FeederModuleType Definition

Attribute

Value

BrowseName

FeederModuleType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ComponentType defined in OPC 10000-100

0:HasComponent

Variable

FeederLoad

0:Number

MeasuredItemType

Optional

0:HasProperty

Variable

FeederRunning

Boolean

0:PropertyType

Optional

0:HasComponent

Variable

FeederSpeed

0:Number

TargetItemType

Optional

0:HasComponent

Method

SetFeederSpeed

 

 

Optional

0:HasComponent

Variable

MaximumFeederSpeed

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

MinimalFeederSpeed

0:Number

AnalogItemType

Optional

 

8.1.3      ObjectType Description

FeederLoad defines the current loaded weight on the feeder system.

FeederRunning indicates that the feeder system is running.

FeederSpeed defines the current speed of a feeder system. The unit of the FeederSpeed depends on the construction system. Possible values are velocity or a flow rate (kg/s).

MaximumFeederSpeed defines the maximum possible speed of the feeder.

MinimalFeederSpeed defines the minimal possible speed of the feeder.

8.1.4      Method SetFeederSpeed

Allows to set a new value for the speed of the feeder system. The OPC UA server must check if the value is between the minimal and maximum allowed speed and if the unit is allowed. The signature of this Method is specified below. Table 13 and Table 14 specify the Arguments and AddressSpace representation, respectively.

Signature

SetFeederSpeed(

[in]  Float       FeederSpeed

[in]  EUInformation     EngineeringUnits);

 

Table 13 – SetFeederSpeed Method Arguments

Argument

Description

FeederSpeed

The target speed of a feeder system.

EngineeringUnits

The unit of the target feeder speed. The server must check the unit.

 

Table 14 – SetFeederSpeed Method AddressSpace definition

Attribute

Value

BrowseName

SetFeederSpeed

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.2       PrinterModuleType Definition

8.2.1      Overview

The PrinterModuleType defines the structure of an Object of the PrinterModuleType. Figure 14 shows the hierarchical structure and details of the composition. It is formally defined in Table 15.

An Object of the PrinterModuleType represents a printing device. A printing device is a subdevice of a scale that prints labels or other documents related to the scale or to the measurement results. The variables of the module are only readable. So the primary use case of the module is to monitor the label and printmedia status.

 

Figure 14 – Overview PrinterModuleType

8.2.2      ObjectType Definition

Table 15 – PrinterModuleType Definition

Attribute

Value

BrowseName

PrinterModuleType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ComponentType defined in OPC 10000-100

0:HasComponent

Variable

LabelLength

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

LabelStock

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

LabelTypeId

0:String

BaseDataVariableType

Optional

0:HasComponent

Variable

LabelWidth

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

PrintMediaStock

0:Number

AnalogItemType

Optional

 

8.2.3      ObjectType Description

LabelLength defines the length of the labels in stock.

LabelStock indicates the level of labels in stock in percent.

LabelTypeId defines the id of the label to be printed.

LabelWidth defines the width of the labels in stock.

PrintMediaStock defines the level of the print media in percent (e.g. ink, wear of thermal element, etc).

8.3       ScaleSystemType Definition

8.3.1      Overview

The ScaleSystemType defines the structure of an Object of the ScaleSystemType. Figure 15 shows the hierarchical structure and details of the composition. It is formally defined in Table 16.

An Object of the ScaleSystemType represents a scale system and contains one or more scales. The VisionSystemType defines a general communication interface for a scale system and is the entrypoint for clients. This interface makes it possible to interact with this system independent of the knowledge of the internal structure and the underlying processes of the scale system.

The system is modeled with a finite state machine and contains primary information about the state and the status of the system. It optionally can also contain the objects ProductionPreset and ProductionOutput.

Figure 15 – Overview ScaleSystemType

 

8.3.2      ObjectType Definition

Table 16 – ScaleSystemType Definition

Attribute

Value

BrowseName

ScaleSystemType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ComponentType defined in OPC 10000-100

0:HasProperty

Variable

Policy

0:LocalizedText[]

0:PropertyType

Optional

0:HasProperty

Variable

ProcessStateId

0:String

0:PropertyType

Optional

0:HasProperty

Variable

ProcessStateMessage

0:LocalizedText

0:PropertyType

Mandatory

0:HasComponent

Object

ProductionPreset

 

ProductionPresetType

Optional

0:HasComponent

Object

ProductionOutput

 

StatisticType

Optional

0:HasComponent

Object

SubDevices

 

2:ConfigurableObjectType

Optional

0:HasComponent

Method

ResetGlobalStatistics

 

 

Optional

 

The following nodes are override from ComponentType and the Modelling Rule change to Mandatory

0:HasProperty

Variable

2:DeviceClass

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:HardwareRevision

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:Manufacturer

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:Model

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:SerialNumber

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:SoftwareRevision

 

0:PropertyType

Mandatory

8.3.3      ObjectType Description

A scale system can contain one ore more scales. The scales must be a subtype of the ScaleDeviceType but must not be of the same type. The ScaleDeviceType is described in section 8.4.

Policy defines the legal guidelines that apply for the scale or need to be complied by the scale.

ProcessStateId contains a relating identification for the occurring ProcessStateMessage.

ProcessStateMessage contains the message of the current overall state of the scale.

ProductionPreset contains the production presets. See section 8.7 for the complete definition of the ProductionPresetType.

ProductionOutput defines the overall statistic for the scale production.

The modules (subdevices) of a scale system are aggregated in the SubDevices Object (see section 7.3 and OPC 10000-100).

The components of the ScaleSystemType have additional references which are defined inTable 17.

Table 17 – ScaleSystemType Additional Subcomponents

Source Path

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

SubDevices

0:HasComponent

Object

ScaleDevice

ScaleDeviceType

OptionalPlaceholder

 

8.3.4      Method ResetGlobalStatistics

All statistics relating to the scale system but not to a product are reset.

Signature

ResetGlobalStatistics (

);

8.4       ScaleDeviceType Definition

8.4.1      Overview

The ScaleDeviceType defines the structure of an Object of the ScaleDeviceType. Figure 16 shows the hierarchical structure and details of the composition. It is formally defined in Table 18.

The ScaleDeviceType is an abstract ObjectType. An Object of a subtype of the ScaleDeviceType represents a scale. The ScaleDeviceType contains all information that is relevant for most of the scale types. The system is modeled with a finite state machine and contains primary information about the state and the status of the system.

Figure 16 – Overview ScaleDeviceType

8.4.2      ObjectType Definition

Table 18 – ScaleDeviceType Definition

Attribute

Value

BrowseName

ScaleDeviceType

IsAbstract

True

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ComponentType defined in OPC 10000-100

0:HasProperty

Variable

AllowedEngineeringUnits

0:EUInformation[]

0:PropertyType

Optional

0:HasComponent

Method

ClearTare

 

 

Optional

0:HasComponent

Variable

CurrentWeight

WeightType

WeightItemType

Mandatory

0:HasComponent

Object

ListOfWeighingRanges

 

WeighingRangeElementType

MandatoryPlaceholder

0:HasProperty

Variable

MaterialClass

0:LocalizedText

0:PropertyType

Optional

0:HasProperty

Variable

ProcessStateId

0:String

0:PropertyType

Optional

0:HasProperty

Variable

ProcessStateMessage

0:LocalizedText

0:PropertyType

Optional

0:HasComponent

Object

ProductionPreset

 

ProductionPresetType

Optional

0:HasComponent

Variable

RegisteredWeight

WeightType

WeightItemType

Optional

0:HasComponent

Method

RegisterWeight

 

 

Optional

0:HasComponent

Method

SetPresetTare

 

 

Optional

0:HasComponent

Method

SetTare

 

 

Optional

0:HasComponent

Method

SetZero

 

 

Optional

0:HasComponent

Object

SubDevices

 

2:ConfigurableObjectType

Optional

 

The following nodes are override from ComponentType and the Modelling Rule change to Mandatory

0:HasProperty

Variable

2:DeviceClass

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:HardwareRevision

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:Manufacturer

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:Model

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:SerialNumber

 

0:PropertyType

Mandatory

0:HasProperty

Variable

2:SoftwareRevision

 

0:PropertyType

Mandatory

 

8.4.3      ObjectType Description

AllowedEngineeringUnits contains an array of engineering units that can be handled by the OPC UA server. A server that supports a method with the input argument EUInformation must also provide this array.

CurrentWeight defines the current value that is measured at the sensor at the current timestamp. This might be a highly fluctuating value.

MaterialClass defines the allowed material the scale may measure. It is only relevant for certain scales (e.g. totalizing hopper scale or continuous scale).

SubDevices: the modules (subdevices) of a modular scale are aggregated in the SubDevices Object . See OPC Unified Architecture for Device for more information.

ProcessStateId contains an relating identification for the occurring ProcessStateMessage.

ProcessStateMessage contains the message of the current overall state of the scale.

ProductionPreset contains the production presets. See section 8.7 for the complete definition of the ProductionPresetType.

RegisteredWeight defines the last valid measurement that was recorded and will be used for further processing.

ListOfWeighingRanges defines the weighing range and resolution the scale may operate in with a structure of range and resolution.

The components of the ScaleDeviceType have additional references which are defined in Table 19.

Table 19 – ScaleDeviceType Additional Subcomponents

Source Path

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

SubDevices

0:HasComponent

Object

FeederModule

FeederModuleType

OptionalPlaceholder

SubDevices

0:HasComponent

Object

PrinterModule

 

PrinterModuleType

OptionalPlaceholder

SubDevices

0:HasComponent

Object

WeighingModule

 

WeighingModuleType

OptionalPlaceholder

 

8.4.4      Method ClearTare

The tare value is set to zero or deleted.

Signature

 ClearTare(

);

8.4.5      Method RegisterWeight

Triggers the registration of a measured value and a new value for the registeredWeight will be calculated.

Signature

RegisterWeight(

);

8.4.6      Method SetPresetTare

The method set the current presetTare.

Signature

SetPresetTare (

[in]  Double            PresetTare

[in]  EUInformation     EngineeringUnits);

 

Table 20SetPresetTare Method Arguments

Argument

Description

PresetTare

The value which should be set as tare value.

EngineeringUnits

The unit of the preset. The server must check the unit.

 

Table 21SetPresetTare Method AddressSpace definition

Attribute

Value

BrowseName

SetPresetTare

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.4.7      Method SetZero

The method sets zero point. It uses the gross value of the CurrentWeight value.

Signature

SetZero (

);

8.4.8      Method SetTare

The method triggers the tare operation. The CurrentWeight value is used as the tare.

Signature

SetTare(

);

 

8.5       WeighingRangeElementType Definition

8.5.1      Overview

The WeighingRangeElementType defines the structure of an Object of WeighingRangeElementType. Figure 17 shows the hierarchical structure and details of the composition. It is formally defined in Table 22.

For each weighing range a scale supports, the OPC UA server provides an Object of WeighingRangeElementType that contains the properties of the weighing range like the ScaleDivision.

 

Figure 17 – Overview WeighingRangeElementType

8.5.2      ObjectType Definition

Table 22 – WeighingRangeElementType Definition

Attribute

Value

BrowseName

WeighingRangeElementType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasComponent

Variable

ActualScaleInterval

0:Double

AnalogUnitType

Mandatory

0:HasComponent

Variable

Range

0:Range

BaseDataVariableType

Mandatory

0:HasComponent

Variable

VerificationScaleInterval

0:Double

AnalogUnitType

Mandatory

 

8.5.3      ObjectType Description

ActualScaleInterval defines the difference between two consecutive indicated values.

Range defines the range within the scale that may be operated depending on the additional parameters within this type.

Range.EngineeringUnit defines the engineering unit of the range.

VerificationScaleInterval defines the value, expressed in units of mass, used for the classification and verification of an instrument.

The components of the WeighingRangeElementType have additional references which are defined in Table 23

Table 23 – WeighingRangeElementType Additional Subcomponents

Source Path

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

Range

0:HasProperty

Variable

0:EngineeringUnits

0:EUInformation

0:PropertyType

M

8.6       StatisticType Definition

8.6.1      Overview

The StatisticType defines the structure of an Object of StatisticType. Figure 18 shows the hierarchical structure and details of the composition. It is formally defined in Table 24.

The StatisticType is a container for the different statistic values. All variables are optional so that the statistics can be instanced application-specific. The StatisticType can be instanced with parent nodes (e.g. ScaleDeviceType,…). Parent nodes other than those described in this Companion Specification are possible.

Figure 18 – Overview StatisticType

8.6.2      ObjectType Definition

Table 24 – StatisticType Definition

Attribute

Value

BrowseName

StatisticType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasProperty

Variable

StartTime

0:DateTime

0:PropertyType

Optional

0:HasProperty

Variable

ResetCondition

0:String

0:PropertyType

Optional

0:HasComponent

Variable

Tare

0:Double

AnalogItemType

Optional

0:HasComponent

Variable

Throughput

0:UInteger

AnalogItemType

Optional

0:HasComponent

Object

TotalPackages

 

StatisticCounterType

Optional

0:HasComponent

Object

TotalPackagesWeighed

 

StatisticCounterType

Optional

0:HasComponent

Object

LastItem

 

WeighingItemType

Optional

 

8.6.3      ObjectType Description

StartTime defines the point in time at which the system starts acquiring the statistic (e.g. 15:00) . This value is relevant for time statistics. For example, it can be used to create statistics for the last 3 hours.

ResetCondition is a vendor-specific, human readable string that describes the reason and context for the reset of the statistics. For example after 4 hours or after 1000 items. Please note that the subtype FloatingStatisticType is used for floating Statistics.

Examples:

ResetCondition::= “AFTER 4 HOURS”

ResetCondition::= “AFTER 1000 ITEMS”

ResetCondition::= “OPERATOR”

Tare defines the last occurring tare value of the period of time which is used for the statistic.

Throughput defines the number of items registered over the period of the statistic (e.g. packages/min).

TotalPackages defines the totalized number of packages of one cell for weight determination. Contains packages that were sorted out but were physically transported via the scale. This value may be calculated by TotalPackagesAccepted + TotalPackagesRejected.

TotalPackagesWeighed defines the totalized number of packages for which a weight was measured. No reference to acceptance or rejection of the package.

LastItem contains the values of the last item.

8.7       ProductionPresetType Definition

8.7.1      Overview

The ProductionPresetType defines the structure of an Object of ProductionPresetType. Figure 19 shows the hierarchical structure and details of the composition. It is formally defined in Table 25.

ProductionPresetType provides methods to manage the Production preset.

Figure 19 – Overview ProductionPresetType

8.7.2      ObjectType Definition

Table 25 – ProductionPresetType Definition

Attribute

Value

BrowseName

ProductionPresetType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasComponent

Method

AddProduct

 

 

Optional

0:HasComponent

Variable

CurrentProducts

0:String[]

BaseDataVariableType

Optional

0:HasComponent

Method

DeselectProduct

 

 

Optional

0:HasComponent

Method

RemoveProduct

 

 

Optional

0:HasComponent

Method

SelectProduct

 

 

Optional

0:HasComponent

Method

SwitchProduct

 

 

Optional

0:HasComponent

Object

Products

 

 

FolderType

Optional

8.7.3      ObjectType Description

CurrentProducts is an array containing the Ids of all product objects currently in processing mode. The product process can be started using the SelectProduct method or another interface or an external trigger signal.

Products contains the products used in the scale aggregated in the Products Object . The objects in the folder should have the type ProductType or a subtype of it.

8.7.4      Method AddProduct

The method creates an Object with a subtype of ProductType from the address space. The Object needs a reference of the type "0:HasComponent" to the product folder of the scale device. The signature of this Method is specified below. Table 26 and Table 27 specify the Arguments and AddressSpace representation, respectively.

Note: To simplify the handling, it is recommended that during the creation of the product the object is immediately locked for the client. (see section 8.8)

 

Signature

AddProduct(

[in]  String       ProductName

[in]  String      ProductId

[in]  NodeId      ProductType

[out] NodeId      ProductNodeId

);

 

Table 26 – AddProduct Method Arguments

Argument

Description

ProductName

A user-readable name of this Batch.

ProductId

A unique Id of this product

ProductType

The NodeId of a subtype of the ProductType or the NodeId of the ProductType itself

ProductNodeId

The NodeId of the created Object

 

 

Table 27 – AddProduct Method AddressSpace definition

Attribute

Value

BrowseName

AddProduct

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

0:HasProperty

Variable

OutputArguments

Argument[]

0:PropertyType

Mandatory

 

8.7.5      Method SelectProduct

Selects the product. The scale is now able to process the product. This includes that the Id is saved in the currentProduct array and that the ProductMode switches from "Not processing" to "Processing". Table 28 and Table 29 specify the Arguments and AddressSpace representation, respectively.

Signature

SelectProduct (

[in]  String      ProductId

);

 

Table 28SelectProduct Method Arguments

Argument

Description

ProductId

The ProductId of the product Object that represents the product to be selected

 

Table 29SelectProduct Method AddressSpace definition

Attribute

Value

BrowseName

SelectProduct

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.7.6      Method DeselectProduct

Deselects the product. The scale should stop to process the product. This includes that the Id is removed in the currentProduct array and that the ProductMode switches from "Processing" to "Not processing". The signature of this Method is specified below. Table 30 and Table 31 specify the Arguments and AddressSpace representation, respectively.

Signature

DeselectProduct (

[in]  String      ProductId

);

Table 30DeselectProduct Method Arguments

Argument

Description

ProductId

The ProductId of the product Object that represents the product to be selected

 

Table 31DeselectProduct Method AddressSpace definition

Attribute

Value

BrowseName

DeselectProduct

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.7.7      Method RemoveProduct

The method removes an Object from the address space with a subtype of the ProductType. The signature of this Method is specified below. Table 32 and Table 33 specify the Arguments and AddressSpace representation, respectively.

Signature

RemoveProduct (

[in]  String      ProductId

);

Table 32RemoveProduct Method Arguments

Argument

Description

ProductId

The ProductId of the product Object that represents the product to be selected

 

Table 33RemoveProduct Method AddressSpace definition

Attribute

Value

BrowseName

RemoveProduct

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.7.8      Method SwitchProduct

Selects the new product and deselects the old product. The scale is now able to process the new product. This includes that the new Id is saved in the currentProduct array and that the ProductMode switches from "Not processing" to "Processing". Additionally, the old ID is removed in the currentProduct array and the ProductMode of the old product switches from "Processing" to "Not Processing". This method is only possible if only one product is used. The signature of this Method is specified below. Table 34 and Table 35 specify the Arguments and AddressSpace representation, respectively.

Signature

SwitchProduct (

[in]  String      ProductId

);

Table 34SwitchProduct Method Arguments

Argument

Description

ProductId

The Id of the product Object that represents the product to be selected

 

Table 35SwitchProduct Method AddressSpace definition

Attribute

Value

BrowseName

SwitchProduct

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.8       ProductType Definition

8.8.1      Overview

The ProductType is an abstract type that defines the basic structure of all objects that represent a product. Figure 20 shows the hierarchical structure and details of the composition. It is formally defined in Table 36. An Object of the type ProductType represents a product related to the scale.

The different Subtypes of the ProductType are described in the following sections. The ProductType only contains the basic information about a product. The scale type-specific information is modeled in the subtypes for the different scale types. The Create Method makes it possible that a vendor can add own variables and extend the Create Method.

Figure 20 – Overview ProductType

8.8.2      ObjectType Definition

Table 36 – ProductType Definition

Attribute

Value

BrowseName

ProductType

IsAbstract

True

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasProperty

Variable

BatchId

0:String

0:PropertyType

Optional

0:HasProperty

Variable

BatchName

0:LocalizedText

0:PropertyType

Optional

0:HasProperty

Variable

JobId

0:String

0:PropertyType

Optional

0:HasProperty

Variable

JobName

0:LocalizedText

0:PropertyType

Optional

0:HasComponent

Object

Lock

 

LockingServicesType

Optional

0:HasComponent

Variable

PresetTare

 

AnalogItemType

Optional

0:HasComponent

Variable

ProductId

0:String

BaseDataVariableType

Mandatory

0:HasComponent

Variable

ProductMode

Boolean

TwoStateDiscreteType

Optional

0:HasProperty

Variable

ProductName

0:LocalizedText

0:PropertyType

Mandatory

0:HasComponent

Object

Statistic

 

StatisticType

Optional

8.8.3      ObjectType Description

BatchId is the id of the batch to which this product belongs.

BatchName is the human-readable name of the batch to which this product belongs.

JobId is the id of the job to which this product belongs.

JobName is the human-readable name of the job to which this product belongs.

PresetTare defines the predefined tare weight. The value must be written before the item is measured.

ProductId defines a unique Id of this product.

The ProductMode displays the current mode of the product. The Product can be in the mode "Processing" or "Not Processing". The mode is independent from the LockingService. Thus, it is possible that a product is in the "Processing mode" and writeable. The combination of these both modes should be used with care as the writeable element may be in an inconsistent state. If the ProductMode is true the Object is in "Processing". Otherwise, it is in the mode "Not Processing".

ProductName defines the name of this product.

Lock is used as container for the LockingServices Methods and Properties. It is defined in OPC 10000-100 (Locking). Additonal to this definition also the server can lock an object of the ProductType. In this case the property LockingClient contains the ProductUri of the server and LockingUser contains a empty String.

NOTE: If an Object is writeable not all variables must be writeable. There can be additional restrictions based on the implementation.

Statistic contains the different statistic values of the product. The statistic can’t be reset manually. All measurements that relate to the product of the job will be used in the statistics.

8.9       AutomaticFillingScaleType Definition

8.9.1      Overview

The AutomaticFillingScaleType defines the structure of an Object of the AutomaticFillingScaleType. Figure 21 shows the hierarchical structure and details of the composition. It is formally defined in Table 37.

An Object of AutomaticFillingScaleType represents an automatic filling scale. It defines additional methods and properties required for managing automatic filling scales.

Figure 21 – Overview AutomaticFillingScaleType

8.9.2      ObjectType Definition

Table 37 – AutomaticFillingScaleType Definition

Attribute

Value

BrowseName

AutomaticFillingScaleType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ScaleDeviceType

0:HasComponent

Variable

Deviation

0:Number

AnalogItemType

Optional

0:HasProperty

Variable

ToleranceState

ToleranceState

0:PropertyType

Optional

8.9.3      ObjectType Description

Deviation defines the relative amount of over (positive value) or under (negative value) dosed value in relation to the TargetWeight.

ToleranceState describes the state of the tolerance deviation. Under: underneath the lower tolerance value. Over: above the upper tolerance value. In: within the tolerance values. The options “under” and “over” need to be determined via the TargetItemType information of TargetWeight.

ProductionPreset, which is inherited from ScaleDeviceType shall have instances of AutomaticFillingProductType or a subtype in the Products folder.

8.10    AutomaticFillingProductType Definition

8.10.1    Overview

The AutomaticFillingProductType defines the structure of an Object of the AutomaticFillingProductType. Figure 22 shows the hierarchical structure and details of the composition. It is formally defined in Table 38.

An Object of AutomaticFillingProductType represents a product of an automatic filling scale. It defines additional methods and properties required for managing the product.

Figure 22 – Overview AutomaticFillingProductType

8.10.2    ObjectType Definition

Table 38 – AutomaticFillingProductType Definition

Attribute

Value

BrowseName

AutomaticFillingProductType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ProductType

0:HasComponent

Variable

FeedRateMeasuringInterval

Duration

BaseDataVariableType

Optional

0:HasComponent

Variable

FillingTime

Duration

BaseDataVariableType

Optional

0:HasComponent

Variable

FineFeedWeight

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

InFlightWeight

0:Number

AnalogItemType

Mandatory

0:HasComponent

Variable

JogFeed

Boolean

BaseDataVariableType

Optional

0:HasComponent

Variable

MinimumDeltaPerFeedRateMeasuringInterval

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

SettlingTime

Duration

BaseDataVariableType

Optional

0:HasProperty

Variable

TareId

0:String

0:PropertyType

Optional

0:HasComponent

Variable

TargetWeight

0:Number

TargetItemType

Mandatory

 

8.10.3    ObjectType Description

FeedRateMeasuringInterval defines the measuring interval for evaluating the current flowrate.

FillingTime defines the maximum duration for the filling process to take place. Needs to be completed during this period.

FineFeedWeight defines the volume to be dosed in fine flow.

InFlightWeight defines the volume that is behind the valve/in flight after feeding is stopped.

JogFeed defines if an additional dosage is necessary.

MinimumDeltaPerFeedRateMeasuringInterval defines the minimum amount of weight data which needs to change within the FeedRateMeasuringInterval. Otherwise the filling procedure is not valid.

SettlingTime defines the Time that needs to be passed before the measurement process can be triggered.

TareId defines an Id of tare value for the current product or item.

TargetWeight defines the preset of the volume to be processed.

8.11    CatchweigherType Definition

8.11.1    Overview

The CatchweigherType defines the structure of an Object of the CatchweigherType. Figure 23 shows the hierarchical structure and details of the composition. It is formally defined in Table 39.

An Object of the CatchweigherType represents a catchweigher. It has no method or properties defined. The CheckweigherType and the AutomaticWeightPriceLablerType inherit from the catchweigher.

Figure 23 – Overview CatchweigherType

8.11.2    ObjectType Definition

Table 39 – CatchweigherType Definition

Attribute

Value

BrowseName

CatchweigherType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ScaleDeviceType

8.11.3    ObjectType Description

ProductionPreset, which is inherited from ScaleDeviceType shall have instances of CatchweigherProductType or a subtype in the Products folder.

8.12    CatchweigherProductType Definition

8.12.1    Overview

The CatchweigherProductType defines the structure of an Object of the CatchweigherProductType. Figure 24 shows the hierarchical structure and details of the composition. It is formally defined in Table 40.

An Object of the CatchweigherProductType represents a product of a catchweigher. It defines additional methods and properties required for managing the product.

Figure 24 – Overview CatchweigherProductType

8.12.2    ObjectType Definition

Table 40 – CatchweigherProductType Definition

Attribute

Value

BrowseName

CatchweigherProductType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ProductType

0:HasComponent

Object

<Zones>

 

ZoneType

OptionalPlaceholder

0:HasComponent

Method

AddZone

 

 

Optional

0:HasComponent

Object

LastItem

 

WeighingItemType

Optional

0:HasComponent

Variable

PresetHeight

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

PresetLength

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

PresetWidth

0:Number

AnalogItemType

Optional

0:HasComponent

Method

RemoveZone

 

 

Optional

0:HasComponent

Variable

TargetThroughput

0:Number

TargetItemType

Optional

 

8.12.3    ObjectType Description

<Zones> is an OptionalPlaceholder for the different zones. Each zone defines different weighing ranges a product has to be within.

LastItem contains the measured values of the last item that was processed by the catchweigher.

PresetHeight defines the predefined height (in direction of global gravity, see Figure 25) of the measured item. If the PresetHeight value is used, the value must be written before the item is measured.

PresetLength defines the predefined length (in direction of travel, see Figure 25) of the measured item. If the PresetLength value is used, the value must be written before the item is measured.

PresetWidth defines the predefined width (in third possible orthogonal direction to height and length, see Figure 25) of the measured item. If the PresetWidth value is used, the value must be written before the item is measured.

 

Figure 25 – Orientation of an Object

TargetThroughput is the target value for the throughput.

8.12.4     Method AddZone

Adds a zone to the zone array. The signature of this Method is specified below. Table 41 and Table 42 specify the Arguments and AddressSpace representation, respectively.

 

Signature

AddZone(

[in]  LocalizedText     ZoneName

[in]  Double            LowerLimit

[in]  Double            UpperLimit

[in]  EUInformation     EngineeringUnits

[out] NodeId            ZoneNodeId);

Table 41 – AddZone Method Arguments

Argument

Description

ZoneName

User-readable name of the zone

LowerLimit

Lower weight limit of this zone. The lower limit is prior to the upper limit if two zones are beside eacht other

UpperLimit

Upper weight limit of this zone

EngineeringUnits

Unit of the Lower and the UpperLimit. The two Limits must have the same unit

ZoneNodeId

NodeId of the created Object

 

Table 42 – AddZone Method AddressSpace definition

Attribute

Value

BrowseName

AddZone

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

0:HasProperty

Variable

OutputArguments

Argument[]

0:PropertyType

Mandatory

 

8.12.5    Method RemoveZone

Removes a zone from the zone array. The signature of this Method is specified below. Table 43 and Table 44 specify the Arguments and AddressSpace representation, respectively.

 

Signature

RemoveZone(

[in]  NodeId      ZoneNodeId);

Table 43RemoveZone Method Arguments

Argument

Description

ZoneNodeId

NodeId of the Object that should be deleted

 

Table 44RemoveZone Method AddressSpace definition

Attribute

Value

BrowseName

RemoveZone

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.13    WeighingItemType Definition

8.13.1    Overview

The WeighingItemType defines the structure of an Object of an item. Figure 26 shows the hierarchical structure and details of the composition. It is formally defined in Table 45.

Figure 26 – Overview WeighingItemType

8.13.2    ObjectType Definition

Table 45 – WeighingItemType Definition

Attribute

Value

BrowseName

WeighingItemType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasProperty

Variable

ItemId

0:String

0:PropertyType

Optional

0:HasComponent

Variable

MeasuredWeight

WeightType

WeightItemType

Mandatory

0:HasComponent

Variable

MeasuredHeight

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

MeasuredLength

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

MeasuredVolume

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

MeasuredWidth

0:Number

AnalogItemType

Optional

0:HasProperty

Variable

ZoneName

0:String

0:PropertyType

Optional

8.13.3    ObjectType Description

ItemId defines a unique number that is assigned to an item.

MeasuredWeight defines the registered weight that may be unmistakeable referenced to one item.

MeasuredHeight defines the maximum measured height (in direction of global gravity, see Figure 25) of the measured item.

MeasuredLength defines the maximum measured length (in direction of travel, see Figure 25) of the measured item

MeasuredWidth defines the maximum measured width (in third possible orthogonal direction to height and length, see Figure 25) of the measured item.

MeasuredVolume defines the volume of the item.

ZoneName defines the name of the zone in which the item was sorted.

8.14    AutomaticWeightPriceLabelerType Definition

8.14.1    Overview

The AutomaticWeightPriceLabelerType defines the structure of an Object of the AutomaticWeightPriceLabelerType. Figure 27 shows the hierarchical structure and details of the composition. It is formally defined in Table 46.

An Object of AutomaticWeightPriceLabelerType represents an automatic weight-price-labeler. It defines additional methods and properties required for managing the automatic weight-price-labeler.

NOTE: Most Catchweighers or Automatic Weight Price Labelers have a feeder system and a printer. These can be modeled as subdevices with the ObjectType FeederModuleType and the PrinterModuleType.

Figure 27 – Overview AutomaticWeightPriceLabelerType

8.14.2    ObjectType Definition

Table 46 – AutomaticWeighPriceLabelerType Definition

Attribute

Value

BrowseName

AutomaticWeightPriceLabelerType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the CatchweigherType

8.14.3    ObjectType Description

ProductionPreset, which is inherited from ScaleDeviceType shall have instances of AutomaticWeighPriceLabelerProductType or a subtype in the Products folder.

8.15    AutomaticWeightPriceLabelerProductType Definition

8.15.1    Overview

The AutomaticWeightPriceLabelerProductType defines the structure of an Object of the AutomaticWeightPriceLabelerProductType. Figure 28 shows the hierarchical structure and details of the composition. It is formally defined in Table 47.

An object of AutomaticWeightPriceLabelerProductType represents a product of an automatic weight-price-labeler. It defines additional methods and properties required for managing the product.

Figure 28 – Overview AutomaticWeightPriceLabelerProductType

8.15.2    ObjectType Definition

Table 47 – AutomaticWeightPriceLabelerProductType Definition

Attribute

Value

BrowseName

AutomaticWeightPriceLabelerProductType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the CatchweigherProductType

0:HasComponent

Variable

UnitPrice

0:Number

BaseDataVariableType

Optional

The following nodes are override from CatchweigherProductType and the TypeDefinition changed

0:HasComponent

Object

LastItem

 

PriceItemType

Optional

 

8.15.3    ObjectType Description

UnitPrice defines the price per weight unit.

The components of the SimpleProductType have additional references which are defined inTable 48.

Table 48 – AutomaticWeightPriceLabelerProductType Additional Subcomponents

Source Path

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

UnitPrice

0: HasProperty

Variable

CurrencyUnit

CurrencyUnitType

0:PropertyType

M

 

8.16    PriceItemType Definition

8.16.1    Overview

The PriceItemType defines the structure of an Object of an item that also has a price. Figure 29 shows the hierarchical structure and details of the composition. In the AutomaticWeightPriceLabeler the PriceItemType is used instead of the ItemType for the LastItem Object. It is formally defined in Table 49.

Figure 29 – Overview PriceItemType

8.16.2    ObjectType Definition

Table 49 – PriceItemType Definition

Attribute

Value

BrowseName

PriceItemType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the WeighingItemType

0:HasComponent

Variable

ItemPrice

0:Number

BaseDataVariableType

Optional

8.16.3    ObjectType Description

ItemPrice defines the price related to measured weight and UnitPrice.

The components of the PriceItemType have additional references which are defined in Table 50.

Table 50 – PriceItemType Additional Subcomponents

Source Path

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

ItemPrice

0: HasProperty

Variable

CurrencyUnit

Subcomponents

0:PropertyType

M

 

8.17    CheckweigherType Definition

8.17.1    Overview

The CheckweigherType defines the structure of an Object of the CheckweigherType. Figure 30 shows the hierarchical structure and details of the composition. It is formally defined in Table 51.

An Object of the CheckweigherType represents a checkweigher. It defines additional methods and properties required for managing the checkweigher.

Figure 30 – Overview CheckweigherType

8.17.2    ObjectType Definition

Table 51 – CheckweigherType Definition

Attribute

Value

BrowseName

CheckweigherType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the CatchweigherType

0:HasComponent

Variable

TU1Percent

0:Number

DataItemType

Optional

8.17.3    ObjectType Description

TU1Percent is the permitted percentage of items with a weight of less than TU1 and upper TU2.

ProductionPreset, which is inherited from ScaleDeviceType shall have instances of CheckweigherProductType or a subtype in the Products folder.

8.18    CheckweigherProductType Definition

8.18.1    Overview

The CheckweigherProductType defines the structure of an Object of the CheckweigherProductType. Figure 31 shows the hierarchical structure and details of the composition. It is formally defined in Table 52.

An Object of the CheckweigherProductType represents a product of a checkweigher. It defines additional methods and properties required for managing the product.

Figure 31 – Overview CheckweigherProductType

8.18.2    ObjectType Definition

Table 52 – CheckweigherProductType Definition

Attribute

Value

BrowseName

CheckweigherProductType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the CatchweigherProductType

0:HasComponent

Variable

NominalWeight

0:Number

TargetItemType

Mandatory

 

 

 

 

 

 

The following nodes are override from CatchweigherProductType and the TypeDefinition changed

0:HasComponent

Object

Statistic

 

CheckweigherStatisticType

Optional

8.18.3    ObjectType Description

NominalWeight defines the nominal (printed) weight of the product.

For this ObjectType the Statistic is overridden with the specific CheckweigherStatisticType.

8.19    CheckweigherStatisticType Definition

8.19.1    Overview

The CheckweigherStatisticType defines the structure of an Object that represents the statistic for a checkweigher. Figure 32 shows the hierarchical structure and details of the composition. It is formally defined in Table 53.

The StatisticType is a container for the different statistic values needed in a checkweigher.

Figure 32 – Overview CheckweigherStatisticType

8.19.2    ObjectType Definition

Table 53 – CheckweigherStatisticType Definition

Attribute

Value

BrowseName

CheckweigherStatisticType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the StatisticType

0:HasComponent

Object

<PackagesRejectedBySystem>

 

StatisticCounterType

OptionalPlaceholder

0:HasComponent

Object

PackagesRejectedByMetal

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByVision

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByXRay

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByDistanceFault

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByLength

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByMeanValueRequirement

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByLowerToleranceLimit1

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

PackagesRejectedByLowerToleranceLimit2

 

RejectedStatisticCounterType

Optional

0:HasComponent

Object

<PackagesAcceptedWithProperty>

 

AcceptedStatisticCounterType

OptionalPlaceholder

0:HasComponent

Object

PackagesAcceptedWithLowerToleranceLimit1

 

AcceptedStatisticCounterType

Optional

0:HasComponent

Variable

PercentageLowerToleranceLimit

0:Number

AnalogItemType

Optional

0:HasComponent

Object

TotalPackagesAccepted

 

StatisticCounterType

Optional

0:HasComponent

Object

TotalPackagesRejected

 

StatisticCounterType

Optional

0:HasComponent

Variable

GiveAway

0:Number

AnalogItemType

Optional

8.19.3    ObjectType Description

PackagesRejectedBySystem defines an optional placeholder for additional categories in which rejected packages may be counted in. The StatisticCounter must have set the flag rejected (see flag definition in section 8.20). The Object should be named like TotalPackagesRejectedBy<SYSTEM>. <SYSTEM> can be an additional system or reason why the packages are rejected. Some reasons could be:

      OpenFlap

      AskewPackage

      UpperToleranceLimit1

      UpperToleranceLimit2

      Presorting

     

PackagesRejectedByMetal defines an StatisticCounter for items rejected by a metal detection system.

PackagesRejectedByVision defines an StatisticCounter for items rejected by a machine vision system.

PackagesRejectedByXRay defines an StatisticCounter for items rejected by a x ray detection system.

PackagesRejectedByDistanceFault defines an StatisticCounter for items rejected by a distance fault.

PackagesRejectedByLength defines an StatisticCounter for items that rejected due to the item length.

PackagesRejectedByMeanValueRequirement defines an StatisticCounter for items that rejected due to the required mean value.

PackagesRejectedByLowerToleranceLimit1 defines an StatisticCounter for items that are lower than the ToleranceLimit1

PackagesRejectedByLowerToleranceLimit2 defines an StatisticCounter for items that are lower than the ToleranceLimit2

PackagesAcceptedWithProperty defines an optional placeholder for additional categories in which accepted packages may be counted in. The StatisticCounter must have set the flag accepted (see flag definition in section 8.20). The Object should be named like TotalPackagesAccepted<PROPERTY>. <PROPERTY> can be an additional system or reason why the package is rejected.

PackagesAcceptedWithLowerToleranceLimit1 defines an StatisticCounter for items that are lower than TU1 and upper TU2 but accepted to the “The 3 Packers Rules” of the Welmec 6.4

TotalPackagesRejected defines the totalized number of packages, which were rejected during verification, controlling or weighing processes, that may be upstream or downstream of the weighing process itself.

TotalPackagesAccepted defines the totalized number of packages, which successfully completed all verification, controlling and weighing processes.

GiveAway defines the totalized value of volume deviation from NominalWeight. The giveaway is an indicator of overproduction and is calculated as follows:

PercentageLowerToleranceLimit1 defines the current precentage of accepted items which are lower TU1 and upper TU2 as defined in the CheckweigherType.

8.20    StatisticCounterType Definition

8.20.1    Overview

The StatisticCounterType defines the structure of an Object of the StatisticCounterType. Figure 33 shows the hierarchical structure and details of the composition. It is formally defined in Table 54.

The StatisticType is a container for the different statisticvalues needed in a checkweigher. Each zone has a StatisticCounterType. There are also different total packages counters. The flags Rejected, Accpeted and Weighed must be set if packages of this statistic should be counted in the counters TotalPackagesRejected, TotalPackagesAccpted or TotalPackagesWeighed.

Figure 33 – Overview StatisticCounterType

8.20.2    ObjectType Definition

Table 54 – StatisticCounterType Definition

Attribute

Value

BrowseName

StatisticCounterType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasComponent

Variable

ItemCount

0:UInteger

BaseDataVariableType

Mandatory

0:HasComponent

Variable

MaxValue

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

MeanValue

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

MinValue

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

PercentageOfTotal

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

StandardDeviation

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

SumWeight

0:Number

AnalogItemType

Optional

0:HasProperty

Variable

Weighed

Boolean

0:PropertyType

Mandatory

8.20.3    ObjectType Description

ItemCount is the totalized count of measurements within the scope of this statistic.

SumWeight is the totalized weight of all items in the ItemCount.

PercentageOfTotal is the percentage of this statistic in relation to the total. The total is the count of the overall statistic, just regarding the ItemCount.

MaxValue defines the highest registered weight value.

MeanValue defines the mean value of all registered weight values.

MinValue defines the lowest registered weight value.

StandardDeviation defines as follows:

         for samples

              for 100% check

Weighed indicates that the element is considered also in the TotalPackageWeighed variable of the StatisticType.

8.21    AcceptedStatisticCounterType Definition

8.21.1    Overview

The AcceptedStatisticCounterType defines the structure of an Object of the AcceptedStatisticCounterType. It is formally defined in Table 55.

The AcceptedStatisticCounterType is subtype of the StatisticCounterType and changes the semantic meaning of the StatisticCounterType. An object with the AcceptedStatisticCounterType is used, if counted items are accepted by the scale. The items are considered also in the TotalPackagesAccepted variable of the CheckweigherStatisticType.

8.21.2    ObjectType Definition

Table 55 – AcceptedStatisticCounterType Definition

Attribute

Value

BrowseName

AcceptedStatisticCounterType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the StatisticCounterType

 

8.22    RejectedStatisticCounterType Definition

8.22.1    Overview

The RejectedStatisticCounterType defines the structure of an Object of the RejectedStatisticCounterType. It is formally defined in Table 56.

The RejectedStatisticCounterType is subtype of the StatisticCounterType and changes the semantic meaning of the StatisticCounterType. An object with the RejectedStatisticCounterType is used, if counted items are rejected by the scale. The items are considered also in the TotalPackagesRejected variable of the CheckweigherStatisticType.

8.22.2    ObjectType Defintion

Table 56 – RejectedStatisticCounterType Definition

Attribute

Value

BrowseName

RejectedStatisticCounterType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the StatisticCounterType

 

8.23    ZoneType Definition

8.23.1    Overview

The ZoneType defines the structure of an Object of the ZoneType. Figure 34 shows the hierarchical structure and details of the composition. It is formally defined in Table 57.

The ZoneType is a container for the weighing zones in a checkweigher. It defines additional methods and properties required for managing the different zones and provides a ZoneStatistic.

 

Figure 34 – Overview ZoneType

8.23.2    ObjectType Definition

Table 57 – ZoneType Definition

Attribute

Value

BrowseName

ZoneType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the BaseObjectType defined in OPC 10000-5

0:HasComponent

Variable

LowerLimit

0:Number

AnalogItemType

Mandatory

0:HasComponent

Variable

Name

0:LocalizedText

BaseDataVariableType

Mandatory

0:HasComponent

Variable

UpperLimit

0:Number

AnalogItemType

Mandatory

0:HasComponent

Object

ZoneStatistic

 

StatisticCounterType

Optional

8.23.3    ObjectType Description

LowerLimit defines the lower weight limit of this zone. The lower limit is prior to the upper limit if two zones are next to each other.

Name defines the user-readable name of the zone.

UpperLimit defines the upper weight limit of this zone.

ZoneStatistic contains statistics regarding this zone.

8.24    ContinuousScaleType Definition

8.24.1    Overview

The ContinuousScaleType defines the structure of an Object of the ContinuousScaleType. Figure 35 shows the hierarchical structure and details of the composition. It is formally defined in Table 58.

An Object of the ContinuousScaleType represents a continuous scale. It defines additional methods and properties required for managing the continuous scale.

Figure 35 – Overview ContinuousScaleType

8.24.2    ObjectType Definition

Table 58 – ContinuousScaleType Defintion

Attribute

Value

BrowseName

ContinuousScaleType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ScaleDeviceType

0:HasComponent

Object

<Totalizer>

 

TotalizerType

Optional Placeholder

0:HasComponent

Variable

FlowRate

BaseDataType

MeasuredItemType

Mandatory

0:HasComponent

Variable

HopperWeight

BaseDataType

MeasuredItemType

Optional

0:HasComponent

Object

MasterTotalizer

 

TotalizerType

Mandatory

0:HasComponent

Variable

MaxFlowRate

0:Number

AnalogItemType

Mandatory

0:HasComponent

Variable

MinFlowRate

0:Number

AnalogItemType

Mandatory

 

8.24.3    ObjectType Description

Totalizer defines the overall volume that was conveyed over a defined duration. Multiple objects may be instantiated depending on the use case (OptionalPlaceholder).

FlowRate defines current mass flow in mass per time.

HopperWeight defines the remaining amount of the supplied product in the hopper (e.g. for loss in weight scales).

MasterTotalizer defines the overall volume that was conveyed over the lifetime of the scale.

MaxFlowRate defines the maximum mass flow that may be conveyed. It is the largest mass per time.

MinFlowRate defines the minimum mass flow that can be conveyed. It is the smallest mass per time.

ProductionPreset, which is inherited from ScaleDeviceType shall have instances of ContinuousProductType or a subtype in the Products folder.

8.25    ContinuousProductType Definition

8.25.1    Overview

The ContinuousProductType defines the structre of an Object of the ContinuousProductType. Figure 36 shows the hierarchical structure and details of the composition. It is formally defined in Table 59.

An Object of the ContinuousProductType represents a product of a continuous scale. It defines additional methods and properties required for managing the product.

Figure 36 – Overview ContinuousProductType

8.25.2    ObjectType Definition

Table 59 – ContinuousProductType Definition

Attribute

Value

BrowseName

ContinuousProductType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ProductType

0:HasComponent

Variable

MaterialDensity

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

TargetFlowRate

0:Number

TargetItemType

Optional

0:HasComponent

Variable

TargetWeight

0:Number

TargetItemType

Optional

 

8.25.3    ObjectType Description

MaterialDensity defines the density of the used material.

TargetFlowRate defines a preset of flowrate that needs to be conveyed. This value defines the setpoint for the FlowRate control loop.

TargetWeight defines a preset of the volume to be processed.

8.26    LossInWeightScaleType Definition

8.26.1    Overview

The LossInWeightScaleDeviceType defines the structure of an Object of the LossInWeightScaleDeviceType. Figure 37 shows the hierarchical structure and details of the composition. It is formally defined in Table 60.

An Object of the LossInWeightScaleDeviceType represents a loss in weight scale. It defines additional methods and properties required for managing the loss in weight scale.

 

Figure 37 – Overview LossInWeightScaleType

8.26.2    ObjectType Definition

Table 60 – LossInWeightScaleType Definition

Attribute

Value

BrowseName

LossInWeightScaleType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ContinuousScaleType

0:HasComponent

Method

DischargeStart

 

 

Mandatory

0:HasComponent

Method

DischargeStop

 

 

Mandatory

0:HasProperty

Variable

Discharging

Boolean

0:PropertyType

Mandatory

0:HasProperty

Variable

Refilling

Boolean

0:PropertyType

Mandatory

0:HasComponent

Method

RefillStart

 

 

Mandatory

0:HasComponent

Method

RefillStop

 

 

Mandatory

 

8.26.3    ObjectType Description

Discharging indicates that a discharging process is taking place.

Refilling indicates that refilling is in progress this may be initiated by the scale.

8.26.4    Method DischargeStart

Starts a discharging process.

Signature

DischargeStart(

);

8.26.5    Method DischargeStop

Stops a discharging process.

Signature

DischargeStop(

);

8.26.6    Method RefillStart

Starts a refilling process.

Signature

RefillStart(

);

8.26.7    Method RefillStop

Stops a refilling process.

Signature

RefillStop(

);

8.27    PieceCountingScaleType Definition

8.27.1    Overview

The PieceCountingScaleType defines the structure of an Object of the PieceCountingScaleType. Figure 38 shows the hierarchical structure and details of the composition. It is formally defined in Table 61.

An Object of the PieceCountingScaleType represents a piece counting scale. It defines additional methods and properties required for managing the piece counting scale.

Figure 38 – Overview PieceCountingScaleType

8.27.2    ObjectType Definition

Table 61 – PieceCountingScaleType

Attribute

Value

BrowseName

PieceCountingScaleType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ScaleDeviceType

0:HasComponent

Variable

CurrentPieceCount

0:Number

MeasuredItemType

Mandatory

0:HasComponent

Variable

ReferenceOptimisationRange

0:Number

AnalogItemType

Optional

0:HasComponent

Method

SetReferencePieceWeight

 

 

Mandatory

0:HasComponent

Method

StartReference

 

 

Optional

0:HasComponent

Method

SetNumberOfReferencePieces

 

 

Mandatory

8.27.3    ObjectType Description

CurrentPieceCount defines the number of pieces that are currently measured related to the ReferencePieceWeight.

ReferenceOptimisationRange defines the tolerance range within which the scale may optimize the ReferencePieceWeight.

ProductionPreset, which is inherited from ScaleDeviceType shall have instances of PieceCountingProductType or a subtype in the Products folder.

 

8.27.4    Method SetReferencePieceWeight

Sets the value for the ReferencePieceWeight (product-specific data). The signature of this Method is specified below. Table 62 and Table 63 specify the Arguments and AddressSpace representation, respectively.

Signature

SetReferencePieceWeight(

[in]  UInt32      ReferencePieceWeight

[in]  0:EUInformation EngineeringUnits);

Table 62SetReferencePieceWeight Method Arguments

Argument

Description

ReferencePieceWeight

The reference weight of a piece

EngineeringUnits

Unit of the ReferencePieceWeight

 

Table 63SetReferencePieceWeight Method AddressSpace definition

Attribute

Value

BrowseName

SetReferencePieceWeight

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.27.5    Method StartReference

Triggers the reference weighing process. The signature of this Method is specified below. Table 64 and Table 65 specify the Arguments and AddressSpace representation, respectively.

Signature

StartReference(

[in]  UInt32      NumberOfReferencePieces);

Table 64 – StartReference Method Arguments

Argument

Description

NumberOfReferencePieces

The number of the references Pieces that should used by the next references process

 

Table 65 – StartReference Method AddressSpace definition

Attribute

Value

BrowseName

StartReference

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.27.6    Method SetNumberOfReferencePieces

Sets the value for NumberOfReferencePieces (product-specific data). The signature of this Method is specified below. Table 66 an Table 67 specify the Arguments and AddressSpace representation, respectively.

Signature

SetNumberOfReferencePieces (

[in] UInt32 NumberOfReferencePieces);

Table 66SetNumberOfReferencePieces Method Arguments

Argument

Description

NumberOfReferencePieces

The number of the references Pieces that should used by the next references process

 

Table 67SetNumberOfReferencePieces Method AddressSpace definition

Attribute

Value

BrowseName

SetNumberOfReferencePieces

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

0:HasProperty

Variable

InputArguments

Argument[]

0:PropertyType

Mandatory

 

8.28    PieceCountingProductType Definition

8.28.1    Overview

The PieceCountingProductType defines the structure of an Object of the PieceCountingProductType. Figure 39 shows the hierarchical structure and details of the composition. It is formally defined in Table 68.

An Object of the PieceCountingProductType represents a product of a piece counting scale. It defines additional methods and properties required for managing the product.

Figure 39 – Overview PieceCountingProductType

8.28.2    ObjectType Definition

Table 68 – PieceCountingProductType Definition

Attribute

Value

BrowseName

PieceCountingProductType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ProductType

0:HasComponent

Variable

CurrentItemCount

0:UInteger

BaseDataVariableType

Optional

0:HasComponent

Variable

FeedRateMeasuringInterval

Duration

BaseDataVariableType

Optional

0:HasComponent

Variable

FillingTime

Duration

BaseDataVariableType

Optional

0:HasComponent

Variable

InFlightCount

0:UInteger

BaseDataVariableType

Optional

0:HasComponent

Variable

JogFeed

Boolean

BaseDataVariableType

Optional

0:HasComponent

Variable

MinimumDeltaPerFeedRateMeasuringInterval

0:Number

AnalogItemType

Optional

0:HasComponent

Variable

NumberOfReferencePieces

0:UInteger

BaseDataVariableType

Mandatory

0:HasComponent

Variable

ReferencePieceWeight

0:Number

AnalogItemType

Mandatory

0:HasComponent

Variable

RegisteredPieceCount

0:UInteger

BaseDataVariableType

Mandatory

0:HasComponent

Method

SetTargetItemCount

 

 

Optional

0:HasComponent

Method

SetTargetPieceCount

 

 

Optional

0:HasComponent

Variable

SettlingTime

Duration

BaseDataVariableType

Optional

0:HasComponent

Variable

TareId

0:String

BaseDataVariableType

Optional

0:HasComponent

Variable

TargetItemCount

0:UInteger

BaseDataVariableType

Optional

0:HasComponent

Variable

TargetPieceCount

0:UInteger

TargetItemType

Optional

0:HasComponent

Variable

TotalizedItemCount

0:UInteger

BaseDataVariableType

Optional

0:HasComponent

Variable

TotalizedWeight

WeightType

WeightItemType

Optional<