Difference between revisions of "Modbus Master"
Line 60: | Line 60: | ||
<span style="font-size:medium;">EdgeSense Modbus Master can manage multiple Modbus Slave setting and individual sensor's parameters, below settings are default after Modbus Master installation.</span> | <span style="font-size:medium;">EdgeSense Modbus Master can manage multiple Modbus Slave setting and individual sensor's parameters, below settings are default after Modbus Master installation.</span> | ||
+ | |||
+ | |||
+ | |||
<pre> | <pre> | ||
− | < | + | metadata: |
+ | name: "Modbus devices" | ||
+ | labels: ["Modbus"] | ||
+ | Description: "Modbus TCP/RTU devices with 3 sensors in holding register area 40001~40003" | ||
+ | UpdateData: 2020-01-08-14:25:30 | ||
+ | |||
+ | # DeviceInfo: You can add a new device with unique name | ||
+ | # <DeviceName>: Unique Device Name | ||
+ | # Params: | ||
+ | |||
+ | LinkInfo: | ||
+ | COM1: | ||
+ | Params: | ||
+ | Driver: Modbus-RTU | ||
+ | ConnectType: Serial | ||
+ | PortName: COM1 | ||
+ | BaudRate: 9600 | ||
+ | DataBits: 8 | ||
+ | StopBits: 1 | ||
+ | Parity: None | ||
+ | |||
+ | Info: | ||
+ | PollingInterval: 1000 # Polling interval ( milliseconds ) | ||
+ | Timeout: 100 # A request timeout ( milliseconds ) | ||
+ | Retry: 3 # Retries min:0 max:3 ( count ) | ||
+ | AliveTime: 60 # Link Timeout in second: SDK will release this link if there are any request over this AliveTime ( second ) | ||
+ | CheckLinkInterval: 5 # Check link status interval (second) | ||
+ | |||
+ | DevList: | ||
+ | - Device-1 | ||
+ | |||
+ | TCP-IP-1: | ||
+ | Params: | ||
+ | Driver: Modbus-TCP | ||
+ | ConnectType: Net | ||
+ | IP: 127.0.0.1 | ||
+ | Port: 502 | ||
+ | |||
+ | Info: | ||
+ | PollingInterval: 1000 # Polling interval in milliseconds | ||
+ | Timeout: 100 # A request timeout in milliseconds | ||
+ | Retry: 3 # Count of retry min:0 max:3 | ||
+ | AliveTime: 60 # Link Timeout in second: SDK will release this link if there are any request over this AliveTime ( second ) | ||
+ | CheckLinkInterval: 5 # Check link status interval (second) | ||
+ | |||
+ | DevList: | ||
+ | - Device-2 | ||
+ | |||
+ | |||
+ | DeviceInfo: | ||
+ | Device-1: | ||
+ | Params: | ||
+ | Station: 1 | ||
+ | |||
+ | Profile: MODBUS_DEVICE_01.yaml | ||
+ | |||
+ | Device-2: | ||
+ | Params: | ||
+ | Station: 2 | ||
+ | |||
+ | Profile: MODBUS_DEVICE_02.yaml | ||
+ | </pre> | ||
= Demonstration = | = Demonstration = |
Revision as of 08:09, 10 January 2020
Contents
Introduction
Modbus enables communication among many devices connected to the same network, for example, a system that measures temperature and humidity and communicates the results to a computer. Modbus is often used to connect a supervisory computer with a remote terminal unit (RTU) in supervisory control and data acquisition (SCADA) systems.
Many of the data types are named from its use in driving relays: a single-bit physical output is called a coil, and a single-bit physical input is called a discrete input or a contact.
Modbus Service is a Windows/Linux system service for WISE Agent to read sensor data from Modbus device or write data into Modbus device. After sensor data are acquired, WISE Agent will upload the data to the WISE-PaaS Cloud.
Features
EdgeSense Modbus-Master aims to collect data from Modbus Slave.
Feature:
- Support connection with multiple Modbus slave.
- Support Modbus TCP and Modbus RTU.
- Support individual sensor upload interval.
- Configurable sensor alias.
- Support byte swap.
- Currently support up-link Modbus data to WISE-PaaS , not support down-link from WISE-PaaS.
How to
Software Requirements
- MQTT broker
- Node.js
Installation
Windows:
1. Download Modbus-Master for Windows from Release Table.
2. Double click the installer to launch the installer to install it to the machine.
Linux:
N.A.
Configuration
EdgeSense Modbus Master can manage multiple Modbus Slave setting and individual sensor's parameters, below settings are default after Modbus Master installation.
metadata: name: "Modbus devices" labels: ["Modbus"] Description: "Modbus TCP/RTU devices with 3 sensors in holding register area 40001~40003" UpdateData: 2020-01-08-14:25:30 # DeviceInfo: You can add a new device with unique name # <DeviceName>: Unique Device Name # Params: LinkInfo: COM1: Params: Driver: Modbus-RTU ConnectType: Serial PortName: COM1 BaudRate: 9600 DataBits: 8 StopBits: 1 Parity: None Info: PollingInterval: 1000 # Polling interval ( milliseconds ) Timeout: 100 # A request timeout ( milliseconds ) Retry: 3 # Retries min:0 max:3 ( count ) AliveTime: 60 # Link Timeout in second: SDK will release this link if there are any request over this AliveTime ( second ) CheckLinkInterval: 5 # Check link status interval (second) DevList: - Device-1 TCP-IP-1: Params: Driver: Modbus-TCP ConnectType: Net IP: 127.0.0.1 Port: 502 Info: PollingInterval: 1000 # Polling interval in milliseconds Timeout: 100 # A request timeout in milliseconds Retry: 3 # Count of retry min:0 max:3 AliveTime: 60 # Link Timeout in second: SDK will release this link if there are any request over this AliveTime ( second ) CheckLinkInterval: 5 # Check link status interval (second) DevList: - Device-2 DeviceInfo: Device-1: Params: Station: 1 Profile: MODBUS_DEVICE_01.yaml Device-2: Params: Station: 2 Profile: MODBUS_DEVICE_02.yaml