Configuration Settings
The configuration settings for a slave for a
Modbus®
master include communications and status reporting. When configuring a slave for a Modbus
master, define these properties:Property | Description | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Communications | Station ID , Modbus communications identity for the slave. This value must be unique for all slaves connected to a single Modbus master. For Ethernet-based slaves, possible communications are only single point-to-point. In this case, usually use an ID of 1.Retries , number of attempts the Modbus master makes to communicate with a slave before declaring a communications failure.Min Packet Gap , time the Modbus master waits between messages sent to the slave, in milliseconds. For slaves that must not be accessed by the Modbus master at full communications speed. | ||||||||||||||||||
Pinging | Method used by the Modbus master to test communications with an individual slave. The Modbus master pings a non-communicating slave at regular intervals. Once the non-communicating slave responds to a ping, then polling of the slave restarts on the next poll cycle. When a slave returns to the polling sequence, the first message that is sent to the slave is the first message defined in the INI file for that slave.Repeat Rate , time delay the Modbus master waits between each attempt to communicate with the slave.Command , method the Modbus master uses for testing communications. Possible methods are:
| ||||||||||||||||||
Slave Control | Modbus address of an application variable used to control the slave device. If the application does not control the slave device, leave unchecked. These are the valid values for a slave control holding register. Invalid values result in the inactive state.Use different Modbus addresses for all control and status holding registers, and control variable coils.
| ||||||||||||||||||
Status Reporting | Modbus address of an application variable which is used to report the status of the communications link to the application. If status reporting is not required, leave unchecked. These are the valid values for slave status holding register. Use different Modbus addresses for all control and status holding registers, and control variable coils.
|
To define communications and status reporting for a slave of a
Modbus
master- Click theConfigurationtab.
- In theCommunicationsarea, specify these properties:
- Station ID,Modbuscommunications identity for the slave
- Retries, number of attempts theModbusmastermakes to communicate with a slave
- Min Packet Gap, time theModbusmaster waits between messages sent to the slave
- In thePingingarea, define the pinging method theModbusmaster uses to test communications with slaves:
- Indicate theRepeat Ratetime delay theModbusmaster waits between communication attempts with slaves.
- Specify theCommandmethod theModbusmaster uses for testing communications:
- UseModbus08 Command
- Use Slave Register
- (optional) In theApplications Interfacearea forSlave Control, select theApplication Controlscheck box, and then indicate theModbusaddress for the communications control variable to enable the application to control communications for the slave.
- (optional) In theApplications Interfacearea forStatus Reporting, select theReport Statuscheck box, and then indicate theModbusaddress for the status reporting variable to report the status of the communications link to the application.
Provide Feedback