|
<< Click to Display Table of Contents >>
Configuring Properties |
This topic contains information about the properties available on the ModbusSlave tab, also informing the value of Strings for offline properties, which can be programmed by users when starting an application in Offline mode. These Strings can be listed on a table, according to the next example.
In addition to the Properties Window, these settings can be defined at run time in Elipse E3, Elipse Power, or Elipse Water applications. To do so, start this Driver in Offline mode, that is, execute an application with its Start driver OFFLINE option enabled, which is configurable on the Setup tab of the Properties Window. The configuration options of this Driver are described on the next table.
Available options on the ModbusSlave tab
Option |
String |
Data Type |
Description |
|---|---|---|---|
Modbus Protocol Settings |
ModbusSlave.MB_Protocol |
Number |
Defines the protocol format. Valid offline values are 0: Modbus RTU or 1: Modbus ASCII |
Use Modbus TCP in Ethernet |
ModbusSlave.UseModbusTCP |
Boolean |
If this option is enabled, uses the Modbus TCP protocol in Ethernet TCP/IP mode. If this option is disabled, uses the RTU/ASCII serial protocol in Ethernet TCP/IP mode. Valid offline values are 0: Disabled or 1: Enabled |
Stores data from Master with base 1 memory address |
ModbusSlave.UseMemBase1 |
Boolean |
The internal memory of Slave Modbus devices uses a base addressing 0 (zero, hardware level), that is, starts at address 0x0000. Usually, Master Modbus devices use a base addressing 1 (one, user level), that is, start at address 0x0001 but, when sending some data to a Slave, the protocol already handles the addressing on base 0 (zero), decrementing -1 (minus one) at the user-informed address. If this option is enabled, data sent by a Master is stored with addresses on base 1 (one), incrementing +1 (plus one) to the destination address of the internal memory of a Slave Modbus device, which is equivalent to the addressing of a Master Modbus device at user level. Valid offline values are 0: Disabled or 1: Enabled |
Use Slave IDs (1, 2, 3, ..., 247, or empty for all) |
ModbusSlave.UseSlaveID |
Text |
Defines a list of specific identifiers of Slave Modbus devices, separated by commas, for communication with a Master Modbus device. Leave this field blank so that any Slave identifier responds to a Master. The valid format for this parameter is 1, 2, 3, ... 'n' (Address of Slave one, Address of Slave two, Address of Slave three, ..., Address of Slave n) |
Use Buffer Memory |
ModbusSlave.UseBuffMemory |
Boolean |
If this option is enabled, it allows storing more than one data record in the same memory register. Valid offline values are 0: Disabled or 1: Enabled |
Amount of data per register |
ModbusSlave.DataPerRegister |
Number |
Defines the amount of data that can be stacked in the same memory register |
Hold latest data (prevents 'zero' value when the buffer is empty) |
ModbusSlave.HoldLatestData |
Boolean |
If this option is enabled, it preserves the presence of the last data received in a memory register. Valid offline values are 0: Disabled or 1: Enabled |
All offline properties must be configured via PLC Tags in String format using the N1 parameter equal to -1 (minus one), the N2 parameter equal to 0 (zero), the N3 parameter equal to 0 (zero), and the N4 parameter equal to 3 (three). For more details and configuration examples of the other tabs, please check topic Documentation of I/O Interfaces.
NOTES |
•For communication in Ethernet mode, the default TCP/IP port used by the Modbus TCP is port 502. •With the Use Buffer Memory option enabled, the list of existing data in each memory register must be collected using an OnRead event of a PLC or Block Tag. |