controllers.
The master
can address individual slaves, or can initiate a broadcast message to all slaves.
Slaves return a message (response) to queries that are addressed to them individually.
Responses are not returned to broadcast queries from the master.
The Modbus protocol establishes the format for the master's query by placing into it the device
(or broadcast) address, a function code defining the requested action, any data to be sent, and an
error-checking field. The slave's response message is also constructed using Modbus protocol. It
contains fields
confirming the action taken, any data to be returned, and an error-checking field.
If an error occurred in receipt of the message, or if the slave is unable to perform the requested
action, the slave will construct an error message and send it as its response.
1.1.2 Transactions
on Other Kinds of Networks
In addition to their standard Modbus capabilities, some Modicon controller models can
communicate over Modbus Plus using built-in ports or network adapters,
and over MAP, using
network adapters.
On these networks, the controllers communicate using a peer-to-peer technique, in which any
controller can initiate transactions with the other controllers. Thus
a controller may operate
either as a slave or as a master in separate transactions. Multiple internal paths are frequently
provided to allow concurrent processing of master and slave transactions.
At the message level, the Modbus protocol still applies the master-slave principle even though
the network communication method is peer-to-peer. If a controller
originates a message, it does
so as a master device, and expects a response from a slave device. Similarly,
when a controller
receives a message it constructs a slave response and returns it to the originating controller.
Chia sẻ với bạn bè của bạn: