UpdateBehavior TOC Previous Specification

The fields of the UpdateBehavior DataType are defined in the following table:

Name Bit No. Description
KeepsParameters 0 If KeepsParameters is not set, the device will lose its configuration during update. The Client should do a backup of the parameters before the update and restore them afterwards.
WillDisconnect 1 If WillDisconnect is set, the OPC UA Server will restart during installation. This can be the case if the update is about the firmware of the device that hosts the OPC UA Server.
RequiresPowerCycle 2 If RequiresPowerCycle is set, the devices require a manual power off / power on for installation.
WillReboot 3 If WillReboot is set, the device will reboot during the update, inclusive of embedded infrastructure elements like an integrated switch. An update Client should take this into account since the devices behind an integrated switch are not reachable for that time.
NeedsPreparation 4 If NeedsPreparation is not set, the Client can install the update without maintaining the PrepareForUpdateStateMachine. This can be used to support an installation without stopping the software.

The representation of the UpdateBehavior DataType in the address space is shown in the following table:

Name Attribute
NodeId ns=1;i=333
NamespaceUri http://opcfoundation.org/UA/DI/
BrowseName UpdateBehavior
IsAbstract False
SubtypeOf UInt32
Categories DI SU Software Update

The references from the UpdateBehavior DataType Node are shown in the following table:

Reference NodeClass BrowseName DataType TypeDefinition ModellingRule
HasProperty Variable OptionSetValues LocalizedText[] PropertyType Mandatory