Modbus RTU - Server Setup
Modbus RTU - Server Setup — Configures one or multiple
Modbus RTU server nodes
Library
Simulink Real-Time - Speedgoat

Description
The Setup block configures one or multiple Modbus RTU server nodes and enables the
read and write blocks to exchange data with the local Modbus data tables. Every
Modbus RTU Server node requires a runtime license.
For serial interface configuration, the Modbus RTU Server Setup block requires the
Setup block of the corresponding serial I/O module to be placed in the model. If you
use an IO503, for example, add an IO503 Setup block to the model and make sure both
Setup blocks have the same Module ID.
Ports
This driver block has no input or output ports.
Parameters
Physical Layer
-
Serial Interface
Select the type of the serial interface you want to use for Modbus
communication. The list consists of supported serial I/O modules.
-
Module ID
Enter the Module ID of the related serial module's Setup block.
-
Channel
Enter the channel number of the serial I/O module to which you want to
assign the Modbus RTU server nodes.
Parameters
-
Interface ID
The Server Setup block defines one Modbus RTU server interface bound
to a specific serial channel. The interface ID is used to assign Setup,
Read and Write blocks to that interface. Interface IDs range between 0
to 65535 and must be unique along all Modbus RTU Client and Server setup
blocks in a model. You can define multiple server interfaces by placing
a Setup block in your model with a unique interface ID for each
interface. One server interface can manage multiple server nodes.
-
Automatic Interface ID
The automatic interface ID checkbox enables the automatic generation
of a unique interface ID, based on the above physical layer selection.
-
Nodes
Defines the Node IDs the server interface should manage in the range
of 1 to 247. Each node has its own data tables for coils, discrete
inputs, holding registers and input registers. Modbus clients can
address a certain node with the node identifier in the Modbus request
frame.
According to the Modbus standard, Node ID 255 means NON-SIGNIFICANT.
If the node identifier received is 255 but Node 255 is not configured in
the server, the requested command is performed on the first node
specified in the nodes parameter.
Default: [1] creates one node with ID 1. Modbus requests with node
identifier 1 or 255 are passed to Node 1.
Example: [1,247] creates two nodes with ID 1 and 247. Modbus requests
with node identifier 1 are passed to Node 1. Modbus requests with node
identifier 247 are passed to Node 247.
Example: [1,2,3,247] creates four nodes with ID 1, 2, 3 and 247.
Modbus requests with node identifier 1 are passed to Node 1. Modbus
requests with node identifier 2 are passed to Node 2. Modbus requests
with node identifier 255 are passed to Node 1.
-
Data Table Dimensions
Defines the number of coils, discrete inputs, holding registers and
input registers of each Modbus node. The value must be an n-by-4 matrix,
where n is the number of Modbus nodes. One row represents one node, the
four columns represent the four Modbus data tables. The number of items
per data table must range between 1 and 65535.
Example: [1,2,3,4;5,6,7,8] The first node has 1 coil, 2 discrete
inputs, 3 holding registers and 4 input registers. The second node has 5
coils, 6 discrete inputs, 7 holding registers and 8 input
registers.
-
Response Delay
Defines the number of milliseconds the server should delay a Modbus
response after having received a request. The number must range between
0 (no delay) and 60000.
-
Sample Time
Defines the base sample time at which this driver block gets its sample hit. This
parameter can also be set to -1 for inherited
sample time. The units are in seconds.