Annex D : Revision / Change Log

Main changes from V1.00 to V1.01

Inconsistencies in description fixed as well as several misspellings. These are not explicit listed in the chapter.

Topic PackMLBaseObjectType – PackMLVersion data type change
Errata Version 1.0
Spec Reference 6.3.2 – Table 3
Mantis Reference
Problem Statement Variable showed before only PackML Version. It should include also OPC UA Comp.Spec Version
Solution / Change

Change back to solution like used in Version 1.0 with PackMLVersion as HasProperty in the object with String as datatype. See “option 2” in the remark the line below.

Remark

Option 1:

Change from BaseDataVariableType to PackMLVersionVariableType ? Could be easier to read for OPC UA clients. => to be discussed

Option 2:

Change back from “HasComponent” back to “HasProperty” with Variable PackMLVersion, DataTyp String and PropertyType like it was used in V1.0. The OPC version is available in NamespaceMetaData

=> Preference

Topic Variable name changed from „UnitCurrentMode” to “UnitModeCurrent”
Errata Version 1.0
Spec Reference 6.3.3 – Table 4
Mantis Reference
Problem Statement

Difference in wording between PackML TR88 and Companion Spec.

Reference “HasComponent” and TypeDefinition as “PropertyType”

Solution

Take over wording from PackML TR88 in companion spec and make it compatible.

Change TypeDefinition from “PropertyType” to “BaseDataVariableType” to reflect Reference.

Topic Spelling variable “Parameter” changed
Errata Version 1.0
Spec Reference 6.3.3
Mantis Reference
Problem Statement Name „Parameters“ different to PackML Document
Solution

Change name from „Parameters“ to “Parameter” to make it compliant to PackML TR88.

Typo fixing in Typedefinition from “BasedDataVariableType” to “BaseDataVariableType”

See also 6.3.4 – Table 5, PackMLAdminObjectType – change from “Parameters” to “Parameter”
Topic Variable “MaterialInterlock” - TypeDefiniton and Modelling Rule
Errata Version 1.0
Spec Reference 6.3.3
Mantis Reference
Problem Statement Harmonize Types between PackML TR88 and Companion Spec
Solution

In TR88 MaterialInterlock is an array of Boolean. No need for OptionalPlaceholder rule, replaced by Optional. OptionalPlaceholder made it possible to define several MaterialInterlock arrays. This is not in line with TR88.

DataType only as Boolean, no need for PackML specific TypeDefinition.

PackML specific TypeDefiniton “InterlockVariableType” replaced by “BaseDataVariableType”.

Topic Variable “RemoteParameter” – Typo fixed, DataType and TypeDefiniton changed
Errata Version 1.0
Spec Reference 6.3.3
Mantis Reference
Problem Statement Different spelling from RemoteParameters in PackML and companion spec and wrong DataType
Solution

“RemoteParameter” instead of “RemoteParameters” to harmonize comp spec compliant to PackML TR88.

Assign to DataType “PackMLRemoteInterfaceDataType” instead of “PackMLDescriptorDataType”. DataType was specified but not linked to RemoteParameter Variable

Typo fixing in TypeDefinition from “BasedDataVariableType” to “BaseDataVariableType”

Topic Spelling variable “Products” changed
Errata Version 1.0
Spec Reference 6.3.3
Mantis Reference
Problem Statement Name „Products“ different to PackML Document
Solution

Change name from „Products“ to “Product” to make it compliant to PackML TR88.

Topic TypeDefinition and Modelling Rule changed for Alarm, AlarmHistory, Warning, StopReason
Errata Version 1.0
Spec Reference 6.3.4 – Table 5
Mantis Reference
Problem Statement Reduction of PackML specific TypeDefinitions
Solution

In TR88 Alarm, AlarmHistory, Warning and StopReason is an array of structure. No need for OptionalPlaceholder rule, replaced by Optional. OptionalPlaceholder made it possible to define several Alarm arrays. This is not in line with TR88.

PackML specific TypeDefinitons replaced by “BaseDataVariableType” instead of “PackMLAlarmVariableType”. Harmonization with TypeDefinition from “Parameter”, “RemoteParameter” and “Product” in 6.3.3 – Table 4

StopReason changed from array to single structure to harmonize with TR88

Topic Description PackML StateMachines
Errata Version 1.0
Spec Reference 6.3.5
Mantis Reference
Problem Statement Short description and Clear as typo from parent statemodel
Solution Extended description and fixing parent state from “Clear” to “Cleared” like in the rest of the document
Topic PackMLBaseStateMachineType – Initial State
Errata Version 1.0
Spec Reference 6.3.6
Mantis Reference
Problem Statement Adopting companion spec to PackML leading document
Solution Change from parent state “Cleared” as initialStateType to “Stopped” as possible initial state in the state model
Topic Transfer table to template design
Errata Version 1.0
Spec Reference 6.3.6
Mantis Reference
Problem Statement Validation Tool labeled table 7 „PackMLBaseStateMachineType” as non-conform
Solution Transfer table in compliant table as defined in the companion spec template
Topic Transfer table to template design
Errata Version 1.0
Spec Reference 6.3.7
Mantis Reference
Problem Statement Validation Tool labeled table 9 „PackMLMachineStateMachineType” as non-conform
Solution Transfer table in compliant table as defined in the companion spec template
Topic Transfer table to template design
Errata Version 1.0
Spec Reference 6.3.8
Mantis Reference
Problem Statement Validation Tool labeled table 11 „ PackMLExecuteStateMachineType” as non-conform
Solution Transfer table in compliant table as defined in the companion spec template
Topic Transfer from PackML specific VariableTypes in BaseDataVariableType
Errata Version 1.0
Spec Reference 6.4.1 & 6.4.2
Mantis Reference
Problem Statement Reduction of PackML specific Variable Types
Solution InterlockVariableType and PackMLCountVariableType replaced by BaseDataVariableType
Topic Extend PackMLCountDataType Structure
Errata Version 1.0
Spec Reference 6.5.3
Mantis Reference
Problem Statement Variables were missing in compliance to TR88
Solution Extend structure with “Name” – Type String and “Unit” – Type EUInformation
Topic Adopt SetUnitMode Method parameter
Errata Version 1.0
Spec Reference 6.7.2
Mantis Reference
Problem Statement

Adopt parameter to PackML wording.

Remove parameter “ModeSelection” from method call because of redundant and unnecessary information in the method call. Information available in parameter “UnitSupportedModes” from statusobject

Solution

Change parameter from “ModeSelectionRequestedMode” to “RequestedMode”. Similar to TR88, shorter and without losing information

Remove ModeSelection

	SetUnitMode(
		[in] NodeId ModeSelection
		[in] Int32 ModeSelectionRequestedMode
		);

Topic Parameter “Products” change in SetProduct Method
Errata Version 1.0
Spec Reference 6.7.4
Mantis Reference
Problem Statement Name „Products“ different to PackML Document
Solution Change parameter name from „Products“ to “Product” to make it compliant to PackML TR88.
Topic Change naming of “ToComplete” Method
Errata Version 1.0
Spec Reference 6.7.9
Mantis Reference
Problem Statement Adopt to PackML wording
Solution Change naming from “ToCompleted” to “ToComplete” to make it PackML compliant
Topic Replacing single parameter in method “RemoteCommand” by structure
Errata Version 1.0
Spec Reference 6.7.15
Mantis Reference
Problem Statement Parameter in RemoteCommand Method were used twice as single element and within the strucutre.
Solution Replacing single parameter by structure “RemoteInterface – PackMLRemoteInterfaceDataType”
Topic PackMLAlarmVariableType
Errata Version 1.0
Spec Reference 6.8.2.1
Mantis Reference
Problem Statement PackMLAlarmVariableType not used anymore in the companion spec
Solution deleted
Topic Annex A – All links to documents and NodeSets must by updated !
Errata Version 1.0
Spec Reference
Mantis Reference
Problem Statement
Solution