influxdata/telegraf

[inputs.modbus] Modbus UDP Feature Resquest

Open

#10,664 opened on Feb 16, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (4,161 forks)batch import
area/modbusfeature requesthelp wantedsize/s

Repository metrics

Stars
 (9,892 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

Feature Request

Add the ability to use Modbus/TCP over a UDP transport.

Proposal:

Add the ability to poll Modbus/TCP slaves over UDP controller = "udp://localhost:502"

Current behavior:

controller = "tcp://localhost:502" modbus plugin establishes a TCP connection to the modbus slaves and polls registers

Desired behavior:

controller = "udp://localhost:502" modbus plugin send modbus request over UDP to poll registers

Use case:

Modbus slaves that support UDP would benefit from the reduced overhead especially when telegraf isn't the only master polling the device for data. The same RTUoverTCP and ASCIIoverTCP options could remain.

Contributor guide

Research direction
Examine the existing modbus input plugin's TCP implementation and identify how to add UDP transport support. Look at the controller string parsing and connection handling, then implement a UDP client following Modbus/TCP protocol over UDP.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoUDP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55