9 OperationType

This ObjectType contains components which are necessary to operate the LDS. It is formally defined in Table 3.

Table 3 – OperationType Definition
Attribute Value
BrowseNameOperationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of 0:BaseObjectType defined in OPC UA Part 5
0:HasPropertyVariableDeviceMappingNumber0:UInt320:PropertyTypeM, RW
0:HasComponentMethodIdentifyDeviceO
0:HasPropertyVariableHighestActiveAlarmSeverity0:UInt160:PropertyTypeM, RO
0:HasComponentVariableActiveErrors3:Classified
ActiveError
DataType[]
0:BaseDataVariableTypeM, RO
0:HasComponentMethodResetAllErrorsO
0:HasComponentMethodResetErrorByIdO
0:HasComponentMethodSetCycleNumberO
0:HasPropertyVariableMaterialBalanceSystemTypeMaterialBalance
SystemType
Enumeration
0:PropertyTypeM, RO
0:HasPropertyVariableActivateMaterialBalance
System
0:Boolean0:PropertyTypeO, RW
0:HasComponentVariableDeliveryType0:UInt160:MultiStateValue
DiscreteType
M, RW
0:HasComponentObjectDeliveryPressure3:ControlledParameterTypeO
0:HasComponentVariableDeliveryPressure
MeasuringPoint
0:UInt160:MultiStateValueDiscreteTypeO, RW
0:HasComponentObjectDeliveryFlowrate3:ControlledParameterTypeO
0:HasComponentVariableActualShotWeight0:Double0:AnalogItemTypeO, RO
0:HasComponentVariableSetShotWeight0:Double0:AnalogItemTypeO, RW
0:HasComponentVariableSetValueCompositeDensity0:Double0:AnalogItemTypeO, RW
0:HasComponentVariableMixingRatioTarget0:Double0:AnalogItemTypeO, RW
0:HasComponentVariableMaxDeviationMixingRatio0:Double0:AnalogItemTypeO, RW
0:HasComponentVariableTargetDeviationMixingRatio0:Double0:AnalogItemTypeO, RO
0:HasComponentVariableActualDeviationMixingRatio0:Double0:AnalogItemTypeO, RO
0:HasComponentVariableRemainingMaterialTime0:Duration0:BaseDataVariableTypeO, RO
0:HasComponentVariablePurgeMode0:UInt160:MultiStateValue
DiscreteType
O, RW
0:HasPropertyVariablePurgeStatusPurgeStatus
Enumeration
0:PropertyTypeO, RO
0:HasComponentVariablePurgeQuantity0:Double0:AnalogItemTypeO, RW
0:HasComponentVariablePurgeTimeout0:Duration0:BaseDataVariableTypeO, RW
0:HasComponentVariablePurgeCyclicQuantity0:Double0:AnalogItemTypeO, RW
0:HasComponentVariablePurgeCyclicIdleTime0:Duration0:BaseDataVariableTypeO, RW
0:HasComponentVariablePurgeCyclicActive0:Boolean0:BaseDataVariableTypeO, RO
0:HasComponentVariableActivateRemoteControl0:UInt160:MultiStateValueDiscreteTypeM, RW
0:HasComponentVariableRemoteControlActivated0:UInt160:MultiStateValueDiscreteTypeM, RO
0:HasComponentMethodStartDosingO
0:HasComponentMethodStopDosingO
0:HasComponentVariableDosingActive0:Boolean0:BaseDataVariableTypeO, RO
0:HasComponentObjectComponent_AComponentTypeM
0:HasComponentObjectComponent_BComponentTypeM
0:HasComponentObjectAdditive_<Y>AdditiveTypeOP
0:GeneratesEventObject
Type
LDSCycleParameters
EventType
Defined in 9.29
Conformance Units
OPC 40082-3 Basic
OPC 40082-3 DosingFunction
OPC 40082-3 Purge
OPC 40082-3 PurgeCyclic
OPC 40082-3 SelectableMaterialBalanceSystem
OPC 40082-3 DeliveryPressure
OPC 40082-3 DeliveryFlowrate
OPC 40082-3 MixingRatioTarget
OPC 40082-3 BalanceSystem
OPC 40082-3 Identify Device
OPC 40082-3 ResetAllErrors
OPC 40082-3 ResetErrorById
OPC 40082-3 SetCycleNumber
OPC 40082-3 ActualShotWeight
OPC 40082-3 SetShotWeight
OPC 40082-3 SetValueCompositeDensity
OPC 40082-3 RemainingMaterialTime
OPC 40082-3 Additive

The BrowseName of ComponentType shall be built of “Component_” and a character ‘A’, ‘B’ , … (e.g. Component_A, Component_B).

The BrowseName of AdditiveType shall be built of “Additive_” and a number from 1 to n (e.g. Additive_1).

9.1 DeviceMappingNumber

Description:Unique identifier/address/number for devices of the same DeviceType within a local network. Several peripheral devices of the same DeviceType can be connected to an IMM. In most applications, the IMM must map the connected peripheral devices to internal logical devices and zones in a fixed configuration (e.g. hot runner systems according to the wiring or temperature control devices according to the tubing).

The mapping shall be stable after reconnecting the devices and is therefore not possible via IP addresses, which can be assigned dynamically via DHCP. DeviceMappingNumber sets the mapping order of peripheral devices of the same type on the local network and is therefore of type UInt32.

Example:1

9.2 IdentifyDevice

Description:The peripheral device on which this method is called shows itself by e.g. activation of a LED.

Signature:

	IdentifyDevice ();

The method has no Input- or OutputArguments.

Table 4 – IdentifyDevice Method AddressSpace Definition
Attribute Value
BrowseNameIdentifyDevice
References Node Class BrowseName DataType TypeDefinition Modelling Rule

9.3 HighestActiveAlarmSeverity

Description:Indication of the severity of the highest active alarm (0 = no active alarm – 1000 = possible error). It provides a minimal error handling for devices without alarm support. However, the variable shall be filled even if alarms are supported.
Example:400

9.4 ActiveErrors

Description:List of the active errors of the device. It provides a minimal error handling for devices without alarm support. However, the variable shall be filled even if alarms are supported. The ClassifiedActiveErrorDataType is defined in OPC 40083. If there is no active error, the array is empty.

9.5 ResetAllErrors

Description:Method to reset all errors on the device.

Signature:

	ResetAllErrors();

The method has no Input- or OutputArguments.

Table 5 – ResetAllErrors Method AddressSpace Definition
Attribute Value
BrowseNameResetAllErrors
References Node Class BrowseName DataType TypeDefinition Modelling Rule

9.6 ResetErrorById

Description:Method to reset one error of the device.

Signature:

	ResetErrorById(
		[in]	0:String	Id);
Table 6 – ResetErrorById Method Arguments
Argument Description
IdId of the error, listed in ActiveErrors, that shall be reset.
Table 7 – ResetErrorById Method AddressSpace Definition
Attribute Value
BrowseNameResetErrorById
References Node Class BrowseName DataType TypeDefinition Modelling Rule
HasPropertyVariableInputArgumentsArgument[]PropertyTypeMandatory

9.7 SetCycleNumber

Description:Method to set the cycle number of the LDS to synchronize it with the cycle number of the injection moulding machine.

Signature:

	SetCycleNumber(
		[in]	0:UInt64	CycleNumber);
Table 8 – SetCycleNumber Method Arguments
Argument Description
CycleNumberNumber, to which the cycle counter of the LDS shall be set. The next LDSCycleParametersEvent will use this value.
Table 9 – SetCycleNumber Method AddressSpace Definition
Attribute Value
BrowseNameSetCycleNumber
References Node Class BrowseName DataType TypeDefinition Modelling Rule
HasPropertyVariableInputArgumentsArgument[]PropertyTypeMandatory

9.8 MaterialBalanceSystemType

Type of the material balance system.

Table 10 – MaterialBalanceSystemTypeEnumeration
Name Value Description
NOT_AVAILABLE0No material balance system available on the LDS. ActivateMaterialBalanceSystem is not present, because it is not possible to switch a material balance system on
ALWAYS_ACTIVE1Material balance system is available on the LDS and is always active. ActivateMaterialBalanceSystem is not present, because it is not possible to switch a material balance system off
SELECTABLE2Material balance system is available on the LDS and it can be switched on and off via the interface via the variable ActivateMaterialBalanceSystem.

9.9 ActivateMaterialBalanceSystem

If the value is true, the material balance system is activated.

9.10 DeliveryType

The dosing system works with delivery pressure or volumetric flow. As some LSR dosing systems support the selection of the DeliveryType, the Property can be writeable. Therefore, the TypeDefinition is MultiStateValueDiscreteType, so the Properties EnumValues and ValueAsText must be filled with the supported values out of Table 11.

Table 11 – Values for DeliveryType
EnumValue ValueAsText Description
0PRESSUREDosing system with delivery pressure
1VOLUMETRIC_FLOWRATEDosing system with volumetric flow

A server can provide manufacturer specific values with EnumValues ≥ 100.

9.11 DeliveryPressure, DeliveryPressureMeasuringPoint

With the objects DeliveryPressure and DeliveryPressureMeasuringPoint the client can set (and monitor) the delivery pressure of the LDS. Both are optional, but the two elements shall always be used together.

For systems with DeliveryPressure the components ActualValue, SetValue, UpperTolerance and LowerTolerance defined in the ControlledParameterType are mandatory. If the upper or lower tolerance band is passed it is documented in the ErrorStatus.

Unit: bar or psi (=lbf/in²)

The variable DeliveryPressureMeasuringPoint represents the position of the pressure sensor used for the DeliveryPressure. As some LSR dosing systems support the selection of the position, the Property can be writeable. Therefore, the TypeDefinition is MultiStateValueDiscreteType, so the Properties EnumValues and ValueAsText must be filled with the supported values out of Table 12.

Table 12 – Values for PressureMeasuringPoint
EnumValue ValueAsText Description
0PUMP_APressure sensor position pump A
1PUMP_BPressure sensor position pump B
2BLENDERPressure sensor position blender
3MANUALPressure is manually adjusted

A server can provide manufacturer specific values with EnumValues ≥ 100.

NOTE: The actual pressure for each component (for monitoring) is included in the ComponentType and the cyclic events.

9.12 DeliveryFlowrate

For system with delivery volumetric flow rate the components ActualValue, SetValue, UpperTolerance and LowerTolerance are mandatory. If the upper or lower tolerance band is passed it is documented in the ErrorStatus.

Unit: l/h or gal/h

9.13 ActualShotWeight

Specifies the value determined by the feeder as the shot weight.

Unit: g or lb

9.14 SetShotWeight

Reference value determined by the IMM or defined by the user on the IMM side.

Unit: g or lb

9.15 SetValueCompositeDensity

The composite set point of density.

Unit: g/cm³ or lb/in³

9.16 MixingRatioTarget

Target of the mixing ratio (includes ratio change when MaterialBalanceSystem is active). The share of component A (in percent) defines the value:

Examples:50 (A 50 : 50 B) without MaterialBalanceSystem
51,25(A 51,25 : 48,75 B) active MaterialBalanceSystem

9.17 MaxDeviationMixingRatio, TargetDeviationMixingRatio, ActualDeviationMixingRatio

If a material balance system is used these variables are used to set and monitor the deviation from the set mixing ratio of component A and B.

MaxDeviationMixingRatio is writeable by the client and used to limit the maximum deviation in percent.

TargetDeviationMixingRatio: This deviation (in percent) is set/used by the material balance system

ActualDeviationMixingRatio: Actual deviation (in percent)

The values are given related to the mixing ratio of component A. If the maximum allowed mixing ratio is 51% component A and 49% component B MaxDeviationMixingRatio is 1%.

9.18 RemainingMaterialTime

Remaining time until first material is empty.

9.19 PurgeMode

Purge functions can be activated directly when the PurgeMode is selected on the LDS. Each device is allowed to set the PurgeMode. When in remote control and purging by the IMM is activated with a hard wired dosing signal, PurgeTimeout and PurgeQuantity has no effect.

When in remote control and purging by the IMM is activated with the StartDosing Method, either PurgeTimeout/PurgeCyclicIdleTime or PurgeQuantity/PurgeCyclicQuantity must be set.

After the dosing signal is deactivated again, the PurgeMode will be reset to OFF by the LDS.

Table 13 – Values for PurgeMode
EnumValue ValueAsText Description
0OFFNo purge function. Normal dosing via dosing signal.
1WITH_COMPONENT_APurge A
2WITH_COMPONENT_BPurge B
3WITH_COMPONENT_A_BVenting
4WITH_COMPONENT_A_OR_BSystem chooses the component which is used for purging (usually the component with the larger remaining quantity)
5CYCLIC_COMPONENT_A_BPurge A and B cyclic

Figure 3 shows the interactions between ActivateRemoteControl, RemoteControlActivated, PurgeMode, PurgeStatus and the dosing signal.

Figure 3: Purge Scenario

Note: “LDS Auto” and “LDS Manual” are LDS internal parameters which are not covered by this specification.

9.20 PurgeStatus

Actual status of the purge function. PurgeStatus must show OFF if no purge function is active. The PurgeStatus is also shown in Figure 3.

Table 14 – PurgeStatusEnumeration
Name Value Description
OFF0No purge function is active.
COMPONENT_A1Purge component A is active.
COMPONENT_B2Purge component B is active.
COMPONENT_A_AND_B3Venting
COMPONENT_A_AND_B_CYCLIC4Cyclic purge component A and B is active.

9.21 PurgeQuantity

The PurgeQuantity is only used in relation with PurgeMode EnumValue 1-4 and describes the amount of material during the active purge mode.

Unit: cm³ or in³

9.22 PurgeTimeout

PurgeTimeout describes the maximum time of the active PurgeMode (1-5). For PurgeMode EnumValue 1-4, the PurgeMode is set to 0 after the PurgeTimeout has expired. For PurgeMode EnumValue 5, the PurgeCyclicActive is set to false, PurgeMode is unaffected.

9.23 PurgeCyclicQuantity

The PurgeCyclicQuantity is only used in relation with PurgeMode EnumValue 5 and describes the amount of material during a purge cycle as the sum of both components. After the volume is reached, the variable PurgeCyclicActive will become false and PurgeCyclicIdleTime starts.

Unit: cm³ or in³

9.24 PurgeCyclicIdleTime

The PurgeCyclicIdleTime is only used in relation with PurgeMode EnumValue 5 and describes the time until the next purge cycle starts.

9.25 PurgeCyclicActive

PurgeCyclicActive is only used in relation with PurgeMode EnumValue 5 and indicates the difference between purging (true) and waiting (false)

9.26 ActivateRemoteControl

It is necessary to synchronize the dosing between IMM and LSR dosing systems. This can be done via a separate interface e.g. via hardwired signals or also via OPC UA (if the process is robust against small time delays that can be caused by the client/server-connection). Signal 0 can be set by IMM or LDS, signals > 0 only by IMM.

With ActivateRemoteControl the client selects the method of remote control. If the server provides only one method for remote control, the other one is not listed in the possible values of the MultiStateValueDiscreteType.

Table 15 – Values for ActivateRemoteControl and RemoteControlActivated
EnumValue ValueAsText Description
0OFFRemote control / automatic mode switched off.
1SEPARATE_INTERFACEActivating automatic mode on LDS and using a separate interface from the injection moulding machine for remote control
2OPC_UAActivating automatic mode on LDS and using this OPC UA connection with the methods StartDosing/StopDosing for remote control

A server can provide manufacturer specific values with EnumValues ≥ 100.

Figure 3 shows the interaction between ActivateRemoteControl and RemoteControlActivated.

9.27 RemoteControlActivated

With this signal, the LDS signals, if it is ready to be controlled via this or a separate interface. See Table 15 for possible values.

Figure 3 shows the interaction between ActivateRemoteControl and RemoteControlActivated.

9.28 StartDosing, StopDosing, DosingActive

Description:If RemoteControlActivated = 2, the two Methods (without arguments) are used to start and stop the dosing. With the Variable DosingActive the LDS can inform the IMM, if dosing is really active.

NOTE: The dosing can also be stopped by the LDS itself (e.g. when SetShotWeight has been reached) to avoid everlasting dosing when the client does not call the method StopDosing.

Signatures:

	StartDosing();
	StopDosing();

The methods have no Input- or OutputArguments.

Table 16 – StartDosing Method AddressSpace Definition
Attribute Value
BrowseNameStartDosing
References Node Class BrowseName DataType TypeDefinition Modelling Rule
Table 17 – StopDosing Method AddressSpace Definition
Attribute Value
BrowseNameStopDosing
References Node Class BrowseName DataType TypeDefinition Modelling Rule

9.29 LDSCycleParametersEventType

The LDSCycleParametersEventType represents information on a dosing cycle. A complete dosing is defined from the beginning of the dosing signal to the next one, i.e. the event for cycle n is fired, when the dosing signal for cycle n+1 starts. After the last cycle the event must be raised after a timeout which corresponds to the cycle time.

Note: The event data refer to the current injected material and not to the current dosing process (1 cycle offset).

The LDSCycleParametersEventType is formally defined in Table 18.

Table 18 – LDSCycleParametersEventType Definition
Attribute Value
BrowseNameLDSCycleParametersEventType
IsAbstractTrue
References Node Class BrowseName DataType TypeDefinition Other
Subtype of 0:BaseEventType defined in OPC UA Part 5
0:HasPropertyVariableCycleNumber0:UInt640:PropertyTypeM
0:HasPropertyVariableDosingTime0:Duration0:PropertyTypeO
0:HasComponentVariableMixingRatioTarget0:Double0:AnalogItemTypeO
0:HasComponentVariableMixingRatioActual0:Double0:AnalogItemTypeO
0:HasComponentVariableAdditivesRatioTarget0:Double[]0:AnalogItemTypeO
0:HasComponentVariableAdditivesRatioActual0:Double[]0:AnalogItemTypeO
0:HasComponentVariableVolumeA0:Double0:AnalogItemTypeO
0:HasComponentVariableVolumeB0:Double0:AnalogItemTypeO
0:HasComponentVariableVolumeAB0:Double0:AnalogItemTypeO
0:HasComponentVariableVolumeAdditives0:Double[]0:AnalogItemTypeO
0:HasComponentVariableVolumeTotal0:Double0:AnalogItemTypeO
0:HasComponentVariableResidualAmountA0:Double0:AnalogItemTypeO
0:HasComponentVariableResidualAmountB0:Double0:AnalogItemTypeO
0:HasComponentVariableMixingPointPressureA0:Double0:AnalogItemTypeO
0:HasComponentVariableMixingPointPressureB0:Double0:AnalogItemTypeO
0:HasComponentVariableMixingPointPressureBlender0:Double0:AnalogItemTypeO
0:HasComponentVariableAdditivesPressure0:Double[]0:AnalogItemTypeO
0:HasComponentVariableFilterPressurePrimary0:Double0:AnalogItemTypeO
0:HasComponentVariableFilterPressureSecondary0:Double0:AnalogItemTypeO

9.29.1 CycleNumber

Number of the dosing cycle. Gets counted up after each dosing cycle. The value can be set by calling the method “SetCycleNumber”. It is recommended to synchronize CycleNumber after a reconnection by calling this method.

Example: 900

9.29.2 DosingTime

Duration of the dosing cycle.

9.29.3 MixingRatioTarget

Target mixing ratio of the last cycle (includes ratio change when MaterialBalanceSystem is active). The share of component A (in percent) defines the value:

Examples:50 (A 50 : 50 B) without MaterialBalanceSystem
51,25(A 51,25 : 48,75 B) active MaterialBalanceSystem

9.29.4 MixingRatioActual

Actual mixing ratio of the components. The share of component A defines the value:

Example: 50,9(A 50,9 : 49,1 B)

9.29.5 AdditivesRatioTarget

Target ratios of additives in percentage which are set in AdditiveFraction of AdditiveType.

9.29.6 AdditivesRatioActual

Actual ratios of additives in percentage.

Example: [ 2,1 % ; 1,2 % ]

9.29.7 VolumeA

Volume of component A that was added to the process in the last cycle.

Unit: cm³ or in³

9.29.8 VolumeB

Volume of component B that was added to the process in the last cycle.

Unit: cm³ or in³

9.29.9 VolumeAB

Volume of components A + B that was added to the process in the last cycle.

Unit: cm³ or in³

9.29.10 VolumeAdditives

Volumes of the additives that were added to the process in the last cycle.

Unit: cm³ or in³

9.29.11 VolumeTotal

Volume of all components (A + B + all additives).

Unit: cm³ or in³

9.29.12 ResidualAmountA

Residual weight amount of component A at the end of the dosing cycle.

Unit: kg or lb

9.29.13 ResidualAmountB

Residual weight amount of component B at the end of the dosing cycle.

Unit: kg or lb

9.29.14 MixingPointPressureA

Average pressure of component A during the last cycle at the blender.

Unit: bar or psi

9.29.15 MixingPointPressureB

Average pressure of component B during the last cycle at the blender.

Unit: bar or psi

9.29.16 MixingPointPressureBlender

Average pressure of components A and B during the last cycle at the blender.

Unit: bar or psi

9.29.17 AdditivesPressure

Average pressure of the additive during the last cycle at the measuring point.

Unit: bar or psi

9.29.18 FilterPressurePrimary, FilterPressureSecondary

Average material pressure during the last cycle before and after the filter. The Pressure difference between FilterPressurePrimary & FilterPressureSecondary can be used to check if the filter is blocked/ will be blocked soon/ has to be maintained. Unit: bar or psi