Configuring Fields: Modbus
When a gateway is running Edge Lite and connected to a Zoho IoT application, you can remotely push configurations for devices that communicate to the gateway using the Modbus protocol. Based on the Modbus communication type, the application provides different fields for configuration.
Modbus RTU
If the communication is via Modbus RTU, you can configure the RS485 port settings and Modbus registry mapping of the connected Modbus device along with the following details.
RS485 Port Settings
Serial Port Name | Identifies the physical or virtual serial port used by the gateway. |
Baud Rate | Defines the communication speed between the gateway and Modbus devices, commonly 9600, 19200, or 115200 bps. Both gateway and Modbus device must use the same baud rate. |
Parity | Adds an error-checking mechanism. |
Data Bit | Number of data bits transmitted per character. |
Stop Bit | Indicates the end of a character. Usually 1 or 2 stops bits, depending on the device requirements. |
Device Details
Product | The device product representing the peripheral device. The Modbus registry mapping of this device product will be sent to the gateway. |
Name | An tag to identify the Modbus device. |
Slave ID | The unique Modbus address of the Modbus device. This ensures the gateway communicates with the correct device on the RS485 bus. |
Edge Key | A unique key used to identify data from the correct device in the JSON payload. The parameter value for the selected modbus device is appended under this edge key in the payload. |
Timeout | The maximum time, in milliseconds, the gateway waits for a response from the device before considering the request failed. |
Serial Port
Device | Port |
TRB145 | dev/ttyHS0 |
TRB245 | dev/ttyUSB0 |
TRB246 | dev/ttyS1 |
TRB255 | dev/ttyUSB0 |
RUT956 | dev/ttyS1 |
AG207 | dev/ttyUSB1 |
AG702 | dev/ttyUSB1 |
Modbus TCP & Modbus RTU over TCP
If the communication is via Modbus TCP or Modbus RTU over TCP, you can configure the Modbus registry mapping of the connected Modbus device and the following details.
Product | The device product representing the peripheral device. The Modbus registry mapping of this device product will be sent to the gateway. |
Name | An tag to identify the Modbus device. |
Slave ID | The unique Modbus address of the Modbus device. This ensures the gateway communicates with the correct device on the network. |
IP Address | The network address of the Modbus device. This allows the gateway to locate and connect to the device over TCP/IP. It must match the static or assigned IP of the peripheral device. |
Port | The communication port number on which the Modbus device is listening. |
Edge Key | A unique key used to identify data from the correct device in the JSON payload. The parameter value for the selected modbus device is appended under this edge key in the payload. |
Timeout | The maximum time, in milliseconds, the gateway waits for a response from the device before considering the request failed. |
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
Zoho FSM Video Tutorials
Centralize Knowledge. Transform Learning.
All-in-one knowledge management and training platform for your employees and customers.
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Configuring Modbus Registry Mapping
In Zoho IoT, modbus registry mapping can be configured individually for each datapoint definition of a peripheral device product. Prerequisites Before configuring Modbus registry mapping, ensure the following conditions are met: The datapoint ...Configuring fields: Device products
This document provides a detailed overview of the various fields you will encounter when creating a custom device product in the Zoho IOT application. The field values specified during the configuration of a device product are not permanent ...Configuring Fields: Devices
This document provides a detailed overview of the various fields you will encounter when creating a device instance in the Zoho IOT application. Field Name Description Model The specific model on which the device creation is based. Learn more about ...Configuring Modbus RTU over TCP
With your gateway device running the Edge Lite, you can remotely push modbus based configurations to connected gateway devices to communicate with its device/sensor supporting Modbus RTU over TCP protocol directly from the Zoho IoT application. This ...Modbus Registry Mapping
Modbus registry mapping is the process of assigning registry specific details to parameters defined in the Modbus protocol, enabling a device to communicate and collect data. In Zoho IoT, Modbus registry mappings are configured when adding a ...
New to Zoho LandingPage?
Zoho LandingPage Resources