OPC UA Base Specifcation Version

1.04

Maximum number of Sessions/Clients

5 (mandatory 2)

"Core 2017 Server Facet" Profile - "Session Minimum 2 Parallel"

MonitoredItems / Subscriptions

• DataChange Subscription

"Embedded DataChange Subscription Server Facet"

•  

  • Max. number of Subscriptions per Session

5

"Subscription Minimum 02" Conformance Unit

•  

  • Max. number of MonitoredItems per Subscription

100 (mandatory 10)

Total number of MonitoredItems =
MaxSessions * MaxSubscriptionPerSession * MaxMonItemsPerSubscription.

"Monitor Items 10" Conformance Unit

•  

  • Monitored Items Deadband Filter

DataChange filter - "absolute"

"Monitored Items Deadband Filter" Conformance Unit

• Minimum Sampling Interval

50ms, server internal and Npx Element mapped VariableNodes

Hilscher-specific

- this value specifies the fastest possible sampling interval for the firmware. Only greater values possible.

• Minimum Publishing Interval

100ms

Hilscher-specific

- this value specifies the fastest possible publishing interval for the firmware. Only greater values possible.

Transport

UA-TCP UA-SC UA-Binary

"UA-TCP UA-SC UA-Binary"

User Token

•  

  • Anonymous

User Token – Anonymous Facet

•  

  • User name Password

User Name – Password Server Facet

Security Policy

•  

  • None

"SecurityPolicy – None"

Information models

• Support of minimum required 'Base Information Model'

 reduced, mandatory Conformace Units, NOT complete BaseNodeSet

•  

  • Base Info Server Capabilities (optional)

"Base Info Server Capabilities" Conformance Unit

•  

  • Base Info Engineering Units

EUInformation, EngineeringUnits

"Base Info Engineering Units" Conformance Unit

• Support of subset of information model 'DataAccess'

 reduced, mandatory Conformance Units

"Data Access Server Facet"

•  

  • Data Access DataItems

BaseAnalogType and its subtypes

"Data Access Server Facet"

• Subset of information model 'Device Integration - Part 100'

 reduced

DeviceType

•  

  • BaseDevice_Server_Facet

mandatory Conformance Units

"BaseDevice_Server_Facet"

•  

  • DeviceIdentification_Server_Facet

mandatory Conformance Units

"DeviceIdentification_Server_Facet"

• Support of Methods with simple built-in data types

"Method Server Facet"

• Support of Array with simple netPROXY Data types

• Support of Structure Data Type as Variant/ExtensionObject for Variable Nodes

Structure definition shall be modelled in IOT Configurator plugin from Communication Studio.

Content is modifiable from application itself.

FullFeatured Server profile

fullfilled OPC UA Server profile

"Micro Embedded Device 2017 Server" Profile

MQTT Version

3.1.1

Payload Encoding

Binary, JSON

Default Sampling Interval

100msec

Maximum number of topics (publications and subscriptions)

32

Maximum size of each topic

256 byte

Maximum number of sessions (broker)

4

Maximum number of transactions per session

8

Authentication

Username and user password

Will message, will topic

yes

UA DataTypes

• Only netPROXY mappable data types could be used within the information model
  
  

  • UA DataType: Boolean, Byte, SByte, Uint16/32/64, Int16/32/64, Float, Double and ByteString

• Structured DataType (fixed)
  
  

  • The supported structures EURange and EUInformation can only be configured during offline-engineering time (in the IOT Configurator)

• Support of Structure Data Type as Variant/ExtensionObject for Variable Nodes (modifiable by application)
  
  

  • Structure definition shall be modelled in IOT Configurator plugin from Communication Studio. Content is modifiable from application itself.

     

UA Variable Access

• Each OPC UA Client request is a single-element netPROXY access

• Variable as an array can be mapped to multiple instances from a netPROXY object. (not via IOT Configurator, only Object API over netPROXY)

• No fast path via DPM available

OPC UA Events, Alarm and Conditions

• Not supported

OPC UA History Read/Write

• Not supported

Locale

• The (OPC UA-) locale "en" is only supported.

Dynamic nodes

• Creation during startup phase possible. Hide/Unhide nodes after startup phase possible too.

Type of NodeId

• imported NodeSet files could contain at least NodeId types Numerical and String

• custom created NodeIds only from NodeId type Numerical supported

ServerNamespaceUri, ApplicationUri, NamespaceArray[1] and ServerArray[0]

• The application shall provide the Server package the required information about the ProductUri as well as the ServerNamespaceUri via the related netPROXY object "OPC UA Server - Extended Component Info".

Supported Value Rank

• Only Variable attribute Value Rank "Scalar" shall be supported (in the IOT Configurator).

Supported ModellingRules

• Modelling rules Mandatory/Optional and its placeholder are supported.

Annotations to Standard Information Model "Device - Part 100"

• No DI-Lock supported

OPC UA Server diagnostics

• No supported. Not mandatory in "Micro Embedded Device 2017 Server" profile.

Extended resources in relation to "Micro Embedded Device Server" profile

• Up to 100 MonitoredItems per subscription (10 items are mandatory)

• Up to 5 Subscriptions per session.
  
  

Runtime details

• Many monitoreditems with small sampling interval causes increased CPU load. (also valid for subscriptions with low keep-alive or publishing rate)

• If during parsing the TLV file an error occurs, the server will reachable via TCP.

Implementation details

• It shall be ensure that the netPROXY object "OPC UA Server - Extended Component Info" is updated by the application before the server starts.

• OPC UA Data Type Enumeration or MultiStateDiscreteType

  • The related string description is only in the TLV and NOT by the netPROXY for the application available
    
    

Configuration details

• The MinimumPublishingInterval is two time the MonitoredItemSamplingInterval.