OPC UA Rebrowse slow on complex-type nodes (BadWaitingForInitialData)

Communication Knowledgebase
OPC UA Rebrowse slow on complex-type nodes (BadWaitingForInitialData)
none 5.0 1
1
  • HMI Model: All Models (cMT3108XP)
  • EasyBuilder Pro Version: 6.10.02.231

Hello everyone,

We are using EasyBuilder Pro with OPC UA as our primary communication protocol, and we have run into a serious performance issue during the variable import stage that makes project setup nearly impractical.

Environment:

  • Software: EasyBuilder Pro (Weintek HMI)
  • Protocol: OPC UA
  • Issue area: Tag browser / Rebrowse function

Problem description:

When browsing the OPC UA address space and adding tags to the project, everything works fine for simple scalar nodes. However, as soon as a node exposes a complex data type — that is, a node that contains child attributes such as Value, StatusCode, and SourceTime — the import process becomes extremely slow: each such variable can take 20–30 minutes to be added, effectively making it impossible to work with servers that expose many structured nodes.

During this process, the EasyBuilder log repeatedly outputs the following errors:

read value failed with status BadWaitingForInitialData
failed to read node <NodeName> with error code 80320000, retry one more time
read value failed with status BadWaitingForInitialData

It appears that EasyBuilder is attempting to read each child attribute of the complex node individually, timing out, retrying, and only proceeding after exhausting its retry cycle — which accounts for the enormous delay per variable.

What we have tried:

  • Verified the OPC UA server is healthy and responding correctly to external clients (UaExpert reads all nodes instantly)
  • Confirmed the issue only occurs with structured/complex-type nodes, not with plain scalar tags
  • Checked that the server-side node attributes (StatusCode, SourceTime) are valid and not intentionally suppressed

Questions:

  1. Is there a way to configure EasyBuilder to skip reading StatusCode / SourceTime child attributes during browsing, and only import the Value?
  2. Is there a timeout or retry setting that can be reduced to speed up the fallback?
  3. Is there a known workaround — for example, importing tags via an XML/CSV file directly instead of using the live Rebrowse function?
  4. Has anyone encountered this and resolved it through server-side configuration (e.g., suppressing certain node attributes)?

Any help or pointers to relevant documentation would be greatly appreciated. This is a recurring issue across multiple projects and is significantly impacting our development workflow.

Thank you in advance.