Multiprotocol Access Product Introduction
Profile Architecture Resource model Protocol applications Definitions
QuickStart
Account and Login
Account Registration Account Authentication
Products and Devices
Create Product Create single device Create devices in batch Export devices in batch
Data Stream and Data Point
User Guide
Rule Engine
Service Introduction Rule Configuration Basic Data Format SQL
HTTP push
Service Introduction Service configuration Development Guide SDK
Security Authentication
Overview token Algorithm Algorithm Examples
java python
Application Management
Service Introduction Controls Introduction Operating Instructions
Development Guide
EDP
Device
Files and tools Protocol introduction Development Process FAQ
API
API Usage SDK API list
New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload Data Points Upload file Get file Send command Query command status Query command response Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey
TCP transparent transmission
Device
Files and tools Protocol introduction Development Process
API
API Usage SDK API List
New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload data point Upload file Get file Send command Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey
MQTT
Device
Files and tools Protocol introduction Development Process FAQ
API
API Usage SDK API List
New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Delete device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload data point Upload file Get file Send command Query command status Query command response Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey Publish message Query subscription topic equipment Query device subscription topic Query product topic
Modbus
Device
Files and tools Protocol introduction Development Process
API
API Usage SDK API List
New device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload Data Points Send command Query command status Query command response Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey
HTTP
API Usage SDK List of Protocol Interfaces
New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload Data Points Upload file Get file Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey
FAQ
List of Platform Addresses Technology category Business category OCP category

Introduction

The Modbus protocol supported by OneNET is based on TCP connection, i.e. Modbus over TCP. As the host, OneNET sends and receives the data packaged by TCP. Due to the simple transparent transmission of DTU, communication can be performed between the bus device and platform according to the Modbus protocol. This can be widely applied in a variety of industries involving the Modbus protocol.

Features

  • Long connection protocol

  • The OneNET platform is used as the Modbus host to issue host commands periodically.

  • The content and issuing cycle of commands are determined according to the properties of a single data stream.

  • The data reported by the terminal is automatically converted into data points in the data stream.

  • The processing formula can be preset for preliminary processing of data.

Typical application scenarios

The Modbus communication protocol is an industrial field bus communication protocol, which is widely used for industrial data collection and control in industrial automation control applications. It can be widely applied in DTU + Modbus scenarios (using the Modbus protocol and DTU connection platform), as shown below:

pic

个搜索结果，搜索内容 “”

    0 个搜索结果，搜索内容 “”