To get more information about modbus application: modbus documentation
Web APP:
To run modbus container you can execute following command:
docker run -d -it \
-p 4443:4443 \
-v /mnt/logs \
-v /mnt/conf \
-v /mnt/data \
-e "CONTAINER_TIMEZONE=Europe/Madrid" \
--restart always \
--name edge.modbus \
onesaitplatform/edge-modbus:community
Another way to launch database application is to use docker-compose schema; docker-compose.yml file must be located at the same execution directory .
docker-compose pull
docker-compose up -d
version: '2'
services:
#Inner mqtt broker mandatory by Edge Engine architecture.
mqtt:
restart: always
image: onesaitplatform/edge-mqtt:community
container_name: edge.mqtt
#Remember define these volumes with edge device local paths.
volumes:
- /mosquitto/log
- /mosquitto/data
networks:
- edgenet
#Edge Engine Modbus contanier for working with TCP & RTU devices.
modbus:
restart: always
image: onesaitplatform/edge-modbus:community
container_name: edge.modbus
environment:
CONTAINER_TIMEZONE: Europe/Madrid
#Remember define these volumes with edge device local paths.
volumes:
- /mnt/logs
- /mnt/data
- /mnt/conf
# If you need Modbus RTU over serial port on /dev/ttyS0.
#devices:
# - /dev/ttyS0:/dev/ttyS0
depends_on:
- mqtt
links:
- mqtt
ports:
- 4443:4443
networks:
- edgenet
networks:
edgenet:
driver: bridge
Content type
Image
Digest
Size
84.6 MB
Last updated
about 7 years ago
docker pull onesaitplatform/edge-modbus:community