Warning
The main branch of this repository contains work-in-progress development code for the upcoming release, and is not guaranteed to be stable or working. It is only compatible with the main branch of edgex-compose which uses the Docker images built from the main branch of this repo and other repos.The source for the latest release can be found at Releases.
Modbus Micro Service - device service for connecting Modbus devices to EdgeX.
Currently, the NATS Messaging capability (NATS MessageBus) is opt-in at build time. This means that the published Docker images do not include the NATS messaging capability.
The following make commands will build the local binary or local Docker image with NATS messaging capability included.
make build-nats
make docker-natsThe locally built Docker image can then be used in place of the published Docker image in your compose file.
See Compose Builder nat-bus option to generate compose file for NATS and local dev images.
Users can refer to the document to learn how to use this device service.
The ProfilesDir and DevicesDir in the configuration.yaml are empty string by default.
To use the example Profile and Device in this repository, please fill './res/profiles' and './res/devices'
to ProfilesDir and DevicesDir respectively.
modbus.test.device.profile.yml and modbus.test.devices.yaml will be loaded and created when the Device Service starts up.
Users can modify those files or add additional Profile YAML to meet their needs.
Build and run the Modbus simulator
$ cd simulator
$ go build
$ ./simulator
Modbus TCP address: 0.0.0.0:1502
Start up a Modbus TCP simulator.
For docker, please refer to the Dockerfile and Docker Compose Builder scripts.
Users can refer to the document to set up the Modbus RTU device.
- Discussion: https://github.com/orgs/edgexfoundry/discussions
- Mailing lists: https://lists.edgexfoundry.org/mailman/listinfo