81
CHAPTER 6 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
6
6.2 Setting Metho
d
(1) Start device to store the predefined protocol operation status
In the open setting, set the start device where the predefined protocol operation status is to be stored. The
following information is stored in the area of 19 words starting from the selected device.
*1
Even after data communications by the predefined protocol function (executed by the SP.ECPRTCL instruction) is
completed, the stored values are held.
(a) Received data verification result
The following information is stored in the Received data verification result.
• Element No. where the verification result did not match (b0 to b7)
• The cause of mismatch (verification result code) (b8 to b15)
Start Device to Store
Predefined Protocol
(offset)
Name
Description
*1
+0
Protocol execution
status
The execution status of the predefined protocol function is stored. (Default: 0)
• 0: Not executed
• 1: Waiting for data to be sent
• 2: Data being sent
• 3: Waiting for data to be received
• 5: Execution completed
+1
Received data
verification result
(received packet No.1)
The verification result of received packet No.1 is stored. (Default: 0) (
• b0 to b7: Element No. where the verification result did not match
• b8 to b15: The cause of mismatch (verification result code)
+2 to 16
Received data
verification result
(received packet No.2
to 16)
The bit configuration is the same as the received packet No.1.
+17
Number of protocol
executions
The number of protocol executions is stored. (Default: 0)
• 0: No execution
• 1 to 65535: Number of executions (The value remains the same after 65535.)
+18
Protocol cancellation
specification
The protocol cancellation request status is stored. (Default: 0)
• 0: No cancellation requested
• 1: Cancellation requested (set by users)
• 2: Cancellation completed (set by the system)
Stored value
Description
0
Verification matched
1 to 32
Element No. where the verification result did not match
FF
H
Verification not performed
Stored
value
Description
Cause
00
H
Normal
⎯
01
H
Insufficient receive data
The total packet size of receive data is smaller than that set in protocol data.
10
H
Data not matched
The receive data do not match the value set in protocol data.
11
H
ASCII-Binary conversion
error
When "ASCII Hexadecimal" is set in Code Type, data not in ASCII code are
received.
12
H
Data length error
The received Length value exceeds 2046 bytes.
30
H
Data length size error
The Length value received from the external device does not match the
actual length of received data.
FF
H
Verification not performed
⎯
Содержание melsec q03ud(E)cpu
Страница 2: ......
Страница 11: ...9 Memo ...
Страница 209: ...207 APPENDICES A Appendix 4 Specifications Comparison with Ethernet Module Memo ...
Страница 213: ...211 Memo ...
Страница 219: ......