Aller au contenu principal

OPC UA configuration

You need an approved, authenticated connector, assigned work centers, and network access to the machine's OPC UA endpoint. The PLC owner must supply actual node IDs, types, units, counter semantics, and write permissions.

Create a mapping​

  1. Open the connector and add a machine mapping for an assigned work center.
  2. Enter the endpoint, such as opc.tcp://plc.example:4840.
  3. Select the server's supported security mode/policy and authentication.
  4. Configure read/write nodes with exact node IDs and data types.
  5. Enable the mapping, synchronize it to the host, and verify connection status and one read-only value.
  6. Test supported writes separately with the machine owner before operational use.

Node IDs are exact identifiers, for example ns=2;s=Machine.Counter or ns=2;i=12345. Copy them from the actual server address space. Namespace indices can differ between machines or after configuration changes.

Supported security settings​

The client requires SignAndEncrypt and Basic256Sha256. Missing settings use those secure defaults; None, Sign, obsolete or unrecognized policies are rejected. Trust the PLC server certificate explicitly in OPCUA_TRUST_DIR/client and trust the Edge application certificate on the PLC. Unknown certificates are rejected. Configure machine-specific username/password credentials where the PLC requires user authentication; without them the client requests an anonymous user session over the authenticated encrypted application channel.

Read and write semantics​

Read configuration entries include nodeId and eventType. The current generic subscription dispatcher handles production and status events. Status maps 1/running/true to operational, 0/stopped/false to idle, and other values to malfunctioning. Check that this matches the machine before connecting it to operational data.

The generic production subscription currently emits an empty order number. A production counter mapping alone therefore does not prove that the intended order will be updated. Use a tested reporting interface with explicit order/work-center identity or an agreed adapter.

Write mappings can select supported order values, such as order number, planned quantity, and custom-field values. Declare the matching data type. A stored write mapping is not proof that the deployed synchronization path has written the value. Verify the actual PLC value and the selected order.

Scrap, malfunction signals, cycle-time nodes, and custom transformations are not all handled by the generic subscription dispatcher. Validate the exact event or method path rather than inferring support from a field name.

PLC calls into the Edge host​

The local OPC UA server exposes an EnneaMES folder with GetNextOrder, GetRecipe, ReportProduction, ReportScrap, and ReportStatus. Its default endpoint path is /UA/EnneaEdge on port 4841. Browse the deployed server for the exact namespace and method argument signatures.

A successful local report means local acceptance/buffering. Verify the corresponding cloud outcome too. See the API reference for quantity and identifier differences and Security for local network boundaries.

Diagnose a mapping​

Connection refusal: check endpoint, route, firewall, and server state. Security error: compare mode/policy and server trust/authentication. Bad node: copy exact identifier and type from the server. Missing cloud progress: inspect order identity, assignment, event buffer, and per-event result. See Troubleshooting.