Difference between revisions of "Modbus Master"
From ESS-WIKI
| (80 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | |||
= Introduction = | = Introduction = | ||
| Line 7: | Line 8: | ||
<span style="font-size:medium;">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.</span> | <span style="font-size:medium;">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.</span> | ||
| + | | ||
| + | | ||
= Features = | = Features = | ||
| Line 15: | Line 18: | ||
<span style="font-size:medium;">Feature:</span> | <span style="font-size:medium;">Feature:</span> | ||
| − | *<span style="font-size:medium;">Support connection with multiple Modbus slave.</span> | + | *<span style="font-size:medium;">Support connection with multiple Modbus slave.</span> |
| − | *<span style="font-size:medium;">Support Modbus TCP and | + | *<span style="font-size:medium;">Support access both Modbus TCP and RTU in one service.</span> |
| − | *<span style="font-size:medium;">Support individual | + | *<span style="font-size:medium;">Support individual read interval by connection.</span> |
| − | *<span style="font-size:medium;">Configurable sensor alias.</span> | + | *<span style="font-size:medium;">Configurable sensor alias.</span> |
| − | *<font size="3">Support byte swap.</font> | + | *<font size="3">Support byte swap.</font> |
| − | *<span style="font-size:medium;"> | + | *<span style="font-size:medium;">Support Modbus Coil, Descrete input, Input register & Holding register data.</span> |
| − | + | *<font size="3">Support maximal 10 links, 5 devices for each link, and 10 sensors for each device.</font> | |
| − | < | ||
| − | < | ||
= How to = | = How to = | ||
| − | == | + | == Login == |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | Step 1. Launch a web browser (Google Chrome, Microsoft Edge ...) and open iEdge local web '''[http://127.0.0.1:8080 http://127.0.0.1:8080]''' | ||
| + | Step 2. Login iEdge local web: | ||
| − | + | Account: '''root''' | |
| − | + | Password: '''P@ssw0rd''' | |
| + | [[File:Ros2-iedge-plugin-config-01.png|frameless|900x520px|Ros2-iedge-plugin-config-01.png]] | ||
| + | | ||
== Configuration == | == Configuration == | ||
| − | + | === How to config Model === | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Step 1. Go to "Plug-ins" / Plugin Config to select Modbus-Master Plug-in | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Modbus config bQUoHri.png|border|800x480px|Modbus config bQUoHri.png]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Setp 2. From Modbus-Master Configuration, open Model Management tab, click "+" to add new Model. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Modbus config qpMUDCj.png|border|800x480px|modbus_config_qpMUDCj.png]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Setp 3. Input Model name and Description for new Model. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Modbus config XLSJYyn.png|border|800x480px|modbus_config_XLSJYyn.png]] | |
| + | Step 4. Click "+" to add Sensor - Input Sensor Name - Select Address Space, Access mode, Data Type, Data Format and input Address, Data Length, Minimal/Maximal Value for new sensor's attributes. - Input below timing attributes: Period (second) . Delay (ms, range: 0~1000ms) and Retry (range: 0~5) | ||
| + | *Click "Save" button to save the new sensor. | ||
| − | + | [[File:Modbus config qsox6hM.png|border|800x480px|modbus_config_qsox6hM.png]] | |
| − | + | Step 5. Repeat Step 4 to add another sensor. | |
| − | [[File:Modbus | + | [[File:Modbus config DPdBICk.png|border|800x480px|modbus_config_DPdBICk.png]] |
| + | Step 6. Click "Save" button to save the new sensors. | ||
| + | [[File:Modbus config oXbCCsc.png|border|800x480px|modbus_config_oXbCCsc.png]] | ||
| − | + | Step 5. Click "Save" button to save the new model. | |
| − | + | [[File:Modbus config kXoLU5M.png|border|800x480px|modbus_config_kXoLU5M.png]] | |
| − | |||
| − | |||
| − | |||
| − | < | + | <br/> |
| + | === How to config Link === | ||
| + | Step 1. From Modbus-Master Configuration, open Link Management tab, click "+" to add a new Link. | ||
| − | + | [[File:Modbus config Sz3fL8f.png|border|800x480px|modbus_config_Sz3fL8f.png]] | |
| − | + | Step 2. Input Link Name, Link Type for the new Link. | |
| − | |||
| + | for Modbus-TCP link, set parameters: - IP - Port | ||
| + | for Modbus-RTU link, set parameters: - COM port - Baudrate - Data bits - Stop bits - Parity mode | ||
| − | + | Click "+" icon to add a new device. | |
| + | [[File:Modbus config Dvkgjc2.png|border|800x480px|modbus_config_Dvkgjc2.png]] | ||
| + | Step 3. Input Device Name, Station Id and select Model Profile for the new device. Model Profile should be added by upper Model Management steps. | ||
| + | Click "Save" button to save the new device. | ||
| + | [[File:Modbus config CkZoH3H.png|border|800x480px|modbus_config_CkZoH3H.png]] | ||
| − | + | Step 4. Click "Save" button to save the new link. | |
| − | + | [[File:Modbus config jGIBhIa.png|border|800x480px|modbus_config_jGIBhIa.png]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Step 5. Click "Apply" button to apply the new link. | |
| + | [[File:Modbus config YudsLa4.png|border|800x480px|modbus_config_YudsLa4.png]] | ||
| + | Apply new settings Successfully | ||
| − | + | [[File:Modbus config 7rvJoo5.png|border|800x480px|modbus_config_7rvJoo5.png]] | |
| − | + | Step 6. Go to Plugin List and select Modbus-Master plugin, the new sensor will be shown in this page | |
| − | |||
| − | |||
| − | + | [[File:Modbus config Sys1ZZH.png|border|800x480px|modbus_config_Sys1ZZH.png]] | |
| + | <br/> | ||
| + | === How to import plugin settings === | ||
| + | Step 1. Click Import button from Modbus-Master Configuration | ||
| + | [[File:Modbus config T6zjSoj.png|border|800x480px|modbus_config_T6zjSoj.png]] | ||
| − | + | Step 2. Select target file you like to import | |
| − | + | [[File:Modbus config ZYeZTw5.png|border|800x480px|modbus_config_ZYeZTw5.png]] | |
| + | Import successful | ||
| + | [[File:Modbus config k3N8BQO.png|border|800x480px|modbus_config_k3N8BQO.png]] | ||
| + | Step 3. Click APPLY to use imported configuration | ||
| + | [[File:Modbus config JTgo9CB.png|border|800x480px|modbus_config_JTgo9CB.png]] | ||
| + | Apply new settings Successfully | ||
| + | [[File:Modbus config WZGsmXR.png|border|800x480px|modbus_config_WZGsmXR.png]] | ||
| − | < | + | <br/> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === How to export plugin settings === | |
| − | |||
| − | |||
| − | + | Step 1. Click Export button from Modbus-Master Configuration | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Modbus config tH3zFyI.png|border|800x480px|modbus_config_tH3zFyI.png]] | |
| − | |||
| − | + | Step 2. Explore the exported file | |
| − | |||
| − | |||
| − | |||
| − | + | [[File:Modbus config IU83MxX.png|border|800x480px|modbus_config_IU83MxX.png]] | |
| − | </ | + | <br/> |
| + | == Use case == | ||
| + | === Connect and upload data for Modbus Temperature and Humidity sensor === | ||
| − | + | Use Modsim32 to simulate a modbus TCP device with a temperature sensor and a humidity sensor, config Modbus-Master to read these two sensors and upload iEdge cloud. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ==== Config Modbus simulator ==== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Step1. Open Modbus Simulator: Launch ModSim32 and click "New" in program menu to create a new simulator page. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Modbus config GskBtAL.png|800x480px|Modbus config GskBtAL.png]] | |
| + | Step2. Set parameter as below: | ||
| + | *Device Id: '''1''' | ||
| + | *Address: '''0001''' | ||
| + | *Length: '''2''' | ||
| + | *Modbus Point Type: '''INPUT REGISTER''' | ||
| − | + | [[File:Modbus config wVMbXWs.png|800x480px|Modbus config wVMbXWs.png]] | |
| − | + | Step3. Enable Auto Simulation: | |
| − | |||
| − | |||
| + | *Double click on the sensor address 30001 | ||
| + | *Click "Auto Simulation" | ||
| + | [[File:Modbus config PaxcEE3.png|320x200px|Modbus config PaxcEE3.png]] | ||
| + | Step4. Set simulation parameters: | ||
| + | *Check "Enable" | ||
| + | *Simulation Type: Increment | ||
| + | *Change Interval (secs): 5 | ||
| + | *Step VAlue: 1 | ||
| + | *Low Limit: 10 | ||
| + | *High Limit: 20 | ||
| − | + | [[File:Modbus config maLqhtS.png|600x320px|Modbus config maLqhtS.png]] | |
| − | + | Step5. Do the same step for the address 30002 and set simulation parameter as below: | |
| + | *Simulation Type: Decrement | ||
| + | *Change Interval (secs): 5 | ||
| + | *Step VAlue: 1 | ||
| + | *Low Limit: 60 | ||
| + | *High Limit: 80 | ||
| + | [[File:Modbus config K98RWgN.png|600x320px|Modbus config K98RWgN.png]] | ||
| − | + | Step6. Set Connection to Modbus/TCP Svr: | |
| − | + | *Click Connection | |
| + | *Click Modbus/TCP Svr to simulate Modbus TCP connection | ||
| − | + | [[File:Modbus config ZhpooZd.png|800x480px|Modbus config ZhpooZd.png]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | |||
| − | |||
| − | + | Step7. Config Modbus-Master | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | *Config Modbus-Master plugin as upper steps to complete the settings. | |
| − | |||
| − | + | | |
Latest revision as of 05:24, 8 August 2023
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 access both Modbus TCP and RTU in one service.
- Support individual read interval by connection.
- Configurable sensor alias.
- Support byte swap.
- Support Modbus Coil, Descrete input, Input register & Holding register data.
- Support maximal 10 links, 5 devices for each link, and 10 sensors for each device.
How to
Login
Step 1. Launch a web browser (Google Chrome, Microsoft Edge ...) and open iEdge local web http://127.0.0.1:8080
Step 2. Login iEdge local web:
Account: root
Password: P@ssw0rd
Configuration
How to config Model
Step 1. Go to "Plug-ins" / Plugin Config to select Modbus-Master Plug-in
Setp 2. From Modbus-Master Configuration, open Model Management tab, click "+" to add new Model.
Setp 3. Input Model name and Description for new Model.
Step 4. Click "+" to add Sensor - Input Sensor Name - Select Address Space, Access mode, Data Type, Data Format and input Address, Data Length, Minimal/Maximal Value for new sensor's attributes. - Input below timing attributes: Period (second) . Delay (ms, range: 0~1000ms) and Retry (range: 0~5)
- Click "Save" button to save the new sensor.
Step 5. Repeat Step 4 to add another sensor.
Step 6. Click "Save" button to save the new sensors.
Step 5. Click "Save" button to save the new model.
How to config Link
Step 1. From Modbus-Master Configuration, open Link Management tab, click "+" to add a new Link.
Step 2. Input Link Name, Link Type for the new Link.
for Modbus-TCP link, set parameters: - IP - Port
for Modbus-RTU link, set parameters: - COM port - Baudrate - Data bits - Stop bits - Parity mode
Click "+" icon to add a new device.
Step 3. Input Device Name, Station Id and select Model Profile for the new device. Model Profile should be added by upper Model Management steps.
Click "Save" button to save the new device.
Step 4. Click "Save" button to save the new link.
Step 5. Click "Apply" button to apply the new link.
Apply new settings Successfully
Step 6. Go to Plugin List and select Modbus-Master plugin, the new sensor will be shown in this page
How to import plugin settings
Step 1. Click Import button from Modbus-Master Configuration
Step 2. Select target file you like to import
Import successful
Step 3. Click APPLY to use imported configuration
Apply new settings Successfully
How to export plugin settings
Step 1. Click Export button from Modbus-Master Configuration
Step 2. Explore the exported file
Use case
Connect and upload data for Modbus Temperature and Humidity sensor
Use Modsim32 to simulate a modbus TCP device with a temperature sensor and a humidity sensor, config Modbus-Master to read these two sensors and upload iEdge cloud.
Config Modbus simulator
Step1. Open Modbus Simulator: Launch ModSim32 and click "New" in program menu to create a new simulator page.
Step2. Set parameter as below:
- Device Id: 1
- Address: 0001
- Length: 2
- Modbus Point Type: INPUT REGISTER
Step3. Enable Auto Simulation:
- Double click on the sensor address 30001
- Click "Auto Simulation"
Step4. Set simulation parameters:
- Check "Enable"
- Simulation Type: Increment
- Change Interval (secs): 5
- Step VAlue: 1
- Low Limit: 10
- High Limit: 20
Step5. Do the same step for the address 30002 and set simulation parameter as below:
- Simulation Type: Decrement
- Change Interval (secs): 5
- Step VAlue: 1
- Low Limit: 60
- High Limit: 80
Step6. Set Connection to Modbus/TCP Svr:
- Click Connection
- Click Modbus/TCP Svr to simulate Modbus TCP connection
Step7. Config Modbus-Master
- Config Modbus-Master plugin as upper steps to complete the settings.