TAMAGAWA TS5013N68 TS5013N68 TS5013N68 TS5013N68 TS5013N68 TS5013N68

TS5013N68

Guang Zhou Lai Jie Electric Co.,LTD

Please contact with “Tommy” for the price

TS3624N2E3

TS3624N2E4

TS3624N3E6

TS3630N1E1

TS3630N2E3

TS3630N1306

TS3630N1303E9

TS3630N1214E3

TS5013N60

TS5013N61

TS5016N60

TS5013N63

TS5013N64

TS5016N61

TS5013N66

TS5016N63

TS5016N64

TS5017N60

TS5019N60

TS5420N60

TS5778N155

TS5013N68

TS5013N69

TS5208N131

TS5208N23

TS2025N471E69

TS2014N181E32

TS5208N111E78

TS5208N141E78

TS5631N224

PULSE

GENERATOR

RP-182

(that allows both symbolic and direct access) or a M memory.
8200 Port is busy processing a transmit request.
Table 12- 72 MB_MASTER execution condition codes (Modbus protocol errors) 1
STATUS (W#16#) Response code from
slave
Modbus protocol errors
8380 - CRC error
8381 01 Function code not supported
8382 03 Data length error
8383 02 Data address error or address outside the valid range of the
DATA_PTR area
8384 Greater than 03 Data value error
8385 03 Data diagnostic code value not supported (function code 08)
8386 - Function code in the response does not match the code in the request.
8387 - Wrong slave responded
8388 - The slave response to a write request is incorrect. The write request
returned by the slave does not match what the master actually sent.
1 In addition to the MB_MASTER errors listed above, errors can be returned from the underlying PtP communication The MB_SLAVE instruction allows your
program to communicate as a Modbus slave
through a PtP port on the CM (RS485 or
RS232) and CB (RS485). When a remote
Modbus RTU master issues a request, your
user program responds to the request by
MB_SLAVE execution. STEP 7 automatically
creates an instance DB when you insert the
instruction. Use this MB_SLAVE_DB name
when you specify the MB_DB parameter for
the MB_COMM_LOAD instruction. The station address of the Modbus slave:
Standard addressing range (1 to 247)
Extended addressing range (0 to 65535)
MB_HOLD_REG IN Variant Pointer to the Modbus Holding Register DB: The Modbus holding
register can be M memory or a data block.
NDR OUT Bool New Data Ready:
 0 – No new data
 1 – Indicates that new data has been written by the Modbus
master
DR OUT Bool Data Read:
 0 – No data read
 1 – Indicates that data has been read by the Modbus master
ERROR OUT Bool The ERROR bit is TRUE for one scan, after the last request was
terminated with an error. If execution is terminated with an error,
then the error code value at the STATUS parameter is valid only
during the single scan where ERROR = TRUE.
STATUS OUT Word Execution error code Modbus communication function codes (1, 2, 4, 5, and 15) can read and write bits and words
directly in the input process image and output process image of the CPU. For these function
codes, the MB_HOLD_REG parameter must be defined as a data type larger than a byte.
The following table shows the example mapping of Modbus addresses to the process image
in the CPU.Modbus communication function codes (3, 6, 16) use a Modbus holding register which can
be a M memory address range or a data block. The type of holding register is specified by
the MB_HOLD_REG parameter on the MB_SLAVE instruction.
Note
MB_HOLD_REG data block type
A Modbus holding register data block must allow both direct (absolute) and symbolic
addressing. When you create the data block the "Standard" access attribute must be
selected.
The following table shows examples of Modbus address to holding register mapping that is
used for Modbus function codes 03 (read words), 06 (write word), and 16 (write words). The
actual upper limit of DB addresses is determined by the maximum work memory limit and M
memory limit, for each CPU model.
Table 12- 76 Mapping of Modbus addresses to CPU memory
Modbus Master MB_HOLD_REG Description
08 0000H Return query data echo test: The MB_SLAVE will echo back to a Modbus master a
word of data that is received. Clear communication event counter: The MB_SLAVE will clear out the communication
event counter that is used for Modbus function 11.
11 Get communication event counter: The MB_SLAVE uses an internal communication
event counter for recording the number of successful Modbus read and write requests
that are sent to the Modbus slave. The counter does not increment on any Function 8,
Function 11, or broadcast requests. It is also not incremented on any requests that
result in a communication error (for example, parity or CRC errors).
The MB_SLAVE instruction supports broadcast write requests from any Modbus master as
long as the request is for accessing valid addresses. MB_SLAVE will produce error code
0x8188 for function codes not supported in broadcast.
Modbus slave communication rules
● MB_COMM_LOAD must be executed to configure a port, before a MB_SLAVE instruction
can communicate through that port.