OPCUA plugin fails to connect to OPCUA server from Codesys when running on groov RIO #15701
Labels
bug
unexpected problem or unintended behavior
waiting for response
waiting for response from contributor
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf v1.26 running in Docker on windows WSL. Connected to OPCUA server from Codesys running on a groov RIO that is available on a local ethernet network
Docker
services:
telegraf:
build:
context: .
volumes:
- ./telegraf.conf:/etc/telegraf/telegraf.conf:ro
- ./script.star:/etc/telegraf/script.star:ro
env_file:
- ./env/local.env
networks:
- reflex-docker
# depends_on:
# timescale:
# condition: service_healthy
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8080"]
interval: 10s
timeout: 10s
retries: 3
restart: unless-stopped
networks:
reflex-docker:
driver: bridge
external: true
Steps to reproduce
Expected behavior
Telegraf should pull data from the opcua server and log it in my postgres database.
Actual behavior
Telegraf successully identifies the opcua server, which is clear because it able to locate its second endpoint. Telegraf then times out with an unkown error and is unable to get any data from the opcua server.
Additional info
I have an identical setup using Codesys on the groov Epic, which works perfectly. I have both devices connected on the same Ethernet network, if I change the ip address in my config file to the Epic's IP (and make no other changes) Telegraf successfully pulls data over opcua. From the log files Telegraf clearly is able to connect to the relevant OPCUA server as it is able to find it's other endpoint, but then fails for unkown reasons. I am able to successfully talk to the server on Rio over both UA Expert and Ignition, which is what leads me to believe it is a bug with Telegraf.
For a comparison here are the log messages when I talk to the server on the Epic instead of the Rio:
I am also talking with Opto22 (the company that makes both of these products, the Epic and the RIO) to see what differences there could be at a low level on their end, but they believe both systems should be identical in this regard.
The text was updated successfully, but these errors were encountered: