r
Copy code
Data validation error
We encountered an issue while processing the data. This could be due to unexpected data formats sent by unsupported Companion versions. Ensure that the corresponding Companion is up-to-date and try again.

View details
                  [
  {
    "code": "too_small",
    "minimum": 1,
    "type": "number",
    "inclusive": true,
    "exact": false,
    "message": "Number must be greater than or equal to 1",
    "path": [
      "connection",
      "port"
    ]
  },
  {
    "code": "invalid_type",
    "expected": "array",
    "received": "null",
    "path": [
      "templateInfo",
      "variables"
    ],
    "message": "Expected array, received null"
  }
]
r
How does the config look ?
First time doing this - I took the inputs required and used gpt to help with the config, not sure if something's wrong here.
j
can you give me a screenshot where you are getting the error message?
ahh, i see you have no connection. I suggest you start by going to data flows and follow there the flow with creating a bridge. And then once oyu have one working bridge you can let the AI loose and help you in adjusting it
r
I'll try this out, thanks!
I'm unable to make the connection, is there anyone that can help with first time set up?
j
what errors do you get?
j
ok, let me create a ticket here. there seems to be something wrong with your configuration - maybe caused by GPT? in the meantime, can you create a new bridge with a new name?
it still seems you are not following exactly the umh-core format when looking closely at it. Can you create a new bridge using the UI?
in general: editing the config file directly is something that needs to be used carefully as with invalid configurations you will cause errors like this
r
I emptied the config file and restarted the docker to try building a bridge with the UI using the same IP and Port. This however causes a failed deployment of the bridge. https://cdn.discordapp.com/attachments/1417139063135408149/1417443777550876692/image.png?ex=68ca80e3&is=68c92f63&hm=c9aafd904f032a0e9cdf9fbed9ea529446c92cc93f1ef5923ab4e9a4f4cf1cdf&
b
Hi, before trying this connection have you tested your connection from a opc UA client tool like UAExpert? I'm just wondering about your IP-adres, since 192.168.0.1 is usually used by your gateway.
j
what @bertvb1 is saying
you can use the UI to also check on yoru connction and latencuy
b
I also see in your config you have configured s7comm instead of opc ua. in the config you send earlier. To connect to OPC UA, it should look something like this under dataflowcomponent_read: benthos: input: opcua: endpoint: opc.tcp://{{ .IP }}:{{ .PORT }} nodeIDs: - ns=4;s=GVL.gAlarmCfg1 - ns=4;s=GVL.gAlarmIn1 - ns=4;s=GVL.gAlarmOut1 - ns=4;s=GVL.blinkBit password: password securityMode: SignAndEncrypt securityPolicy: Basic256Sha256 subscribeEnabled: true useHeartbeat: true username: admin
Can you share your most recent config?
r
Thanks, I just tried with UAExpert and the data is reflecting accurately from the PLC. However, the data validation error persists when trying to click on the connection or throughput. The following is what my config looks like:
Copy code
internal:
    topicbrowser:
        desiredState: active
    redpanda:
        desiredState: active
protocolConverter:
    - name: opcua-bridge-plc1
      desiredState: active
      protocolConverterServiceConfig:
        location:
            "4": Machine-1
        config:
            connection:
                nmap:
                    target: 192.168.0.1
                    port: "4840"
            dataflowcomponent_read:
                benthos:
                    input:
                        opcua:
                            endpoint: opc.tcp://192.168.0.1:4840
                            nodeIDs:
                                - ns=4;i=2
                                - ns=4;i=3
                                - ns=4;i=4
                                - ns=4;i=5
                                - ns=4;i=6
                                - ns=4;i=7
                    pipeline:
                        processors:
                            - tag_processor:
                                defaults: |
                                    msg.meta.location_path = "{{ .location_path }}";
                                    msg.meta.data_contract = "_raw";
https://cdn.discordapp.com/attachments/1417139063135408149/1417501713257988138/image.png?ex=68cab6d8&is=68c96558&hm=02bb103e6e9821be1801f6862ce49321a5eb1d6c8c707edb539cd6ccb2136134& https://cdn.discordapp.com/attachments/1417139063135408149/1417501717829910639/image.png?ex=68cab6d9&is=68c96559&hm=fe6f22f11b641a6c6ba5d5a99cff6460d98f69901466a6c7e09d1f53b28f0620& https://cdn.discordapp.com/attachments/1417139063135408149/1417501719327412316/image.png?ex=68cab6d9&is=68c96559&hm=3cf5b8a18ee4bd729f488be4deb95ff2106360ea54e95345f61d97d617036ea5&
r
This helped, thank you! The protocol converter is now active and I can view live data in the topic broswer. The data validation error, however, still persists when the bridge, connection-id, or throughput are clicked on.
2 Views