edgexfoundry / edgexfoundry/device-modbus-go
Regarding MODBUS communication through an MQTT broker.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 120
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone, I hope you are well. I have the following case: This code is the MODBUS response that I receive through the MQTT topic.
{"id":"26cd17d9-aa6d-45d7-b3dc-1fd5fadd5ca1","device":"Modbus-TCP-Device-2","created":1607981337586,"origin":1607981337581736137,"readings":[{"id":"77437133-9d56-4b5a-8445-ca19cd39b902","origin":1607981337473057323,"device":"Modbus-TCP-Device-2","name":"DemandWindowSize","value":"500","valueType":"Uint16"},{"id":"2345f849-0f64-4ada-9ba6-cf3b40ad6710","origin":1607981337581112262,"device":"Modbus-TCP-Device-2","name":"LineFrequency","value":"120","valueType":"Uint16"}]}
However, I don't know how to post to the topic to upload data to the ModbusPal simulator. I appreciate the guidance you can give me, I look forward to your valuable comments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue describes receiving a MODBUS response through an MQTT topic and asks how to post data to the topic for the ModbusPal simulator. No files, tests, or entry points are identified, so first determine whether this repository documents publishing commands or simulator integration. Done would be a documented, verified way to upload data to ModbusPal through MQTT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- embedded-iot, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100