vogler75 / automation-gateway Goto Github PK

Currently a CTRL+C or SigTerm does not stop the docker container. This seems to be the same issue and could help to solve it.

Hi,

This 'issue' is mainly for asking some help about how to read a topic from Kepware OPC-UA Server. I created a very simple config.yaml file:

Servers:
  Mqtt:
    - Id: Mqtt
      Port: 1883
      Host: 0.0.0.0

  OpcUa:
    - Port: 4000
      Path: server
      Topics:
        - Topic: opc/my_opc_id/Root/Objects/Machine1/PLC/#

Drivers:
  OpcUa:
    - Id: my_opc_id
      EndpointUrl: "opc.tcp://192.168.10.11:49320/Kepware.KEPServerEX.V6"
      UpdateEndpointUrl: true
      SecurityPolicy: None

Unfortunately, I cannot see anything using UAExpert Client. But, with UAExpert Client, I double checked that I have tags in path:

Root
  |- Objects
      |- Machine1
          |- PLC
              |- Type (INT16)
              |- Temp (FLOAT)

Moreover, regarding container logs, I do not have any error. The OpcUaClient driver is connected to Kepware Server, I am able to connect to Frankestein OPC-UA server or MQTT server.

Am I missing something?

Thank you.

Charly

Unhandled error “Unhandled class [] in JsonObject” is shown in the logs on GraphQL read if a timeout occurs on the ModBus read request.

Logger to JDBC currently writes the wildcard address opc/test/path/Objects/Test/Test00003/+ as NodeId in the table, it should be the resolved name/address or at least additionally the resolved address to identify the tag.

If you use wildcards in MQTT subscribe (OPC UA browse path and wildcards, for example: opc/test/path/Objects/Test/Test00003/+) the result for the resolved tags is delivered with the origin topic. It is not published wit the resolved topic/tag name. So you have to use the JSON format to find out which tag the value belongs to. Is this correct from the MQTT specification point of view?

When I put my host into sleep mode (where the OPC UA server runs on), then following errors are thrown during a write value. Potential solution: writing should be done in a dedicated thread, so that the vert.x eventloop is not blocked.

[2021-10-20 20:03:48][WARNING][io.vertx.core.impl.BlockedThre] Thread Thread[vert.x-eventloop-thread-3,5,main] has been blocked for 20438 ms, time limit is 2000 ms
[2021-10-20 20:03:49][WARNING][unified ] Write value threw exception [UaException: status=Bad_Timeout, message=io.netty.channel.ConnectTimeoutException: connection timed out: /192.168.1.190:4890]
[2021-10-20 20:03:49][WARNING][unified ] Converting value to variant exception [NodeId{ns=1, id=2.336.1.0.0.0}] [6] [io.netty.channel.ConnectTimeoutException: connection timed out: /192.168.1.190:4890]