6F8C1048 25
5.3Common Memory Information
5
5.3 Common Memory Information
5.3.1 Socket unit information
This information to be refreshed indicates the status of each socket of the AN712
module.
The sockets 0 to 11 installed in the AN712 module are allocated to word offset addresses
as follows. The structure of each socket is shown in figure 5-3.
Socket 0: 32640 (0x7F80)
Socket 1: 32641 (0x7F81)
Socket 2: 32642 (0x7F82)
Socket 3: 32643 (0x7F83)
Socket 4: 32644 (0x7F84)
Socket 5: 32655 (0x7F85)
Socket 6: 32656 (0x7F86)
Socket 7: 32657 (0x7F87)
Socket 8: 32658 (0x7F88)
Socket 9: 32659 (0x7F89)
Socket 10: 32660 (0x7F8A)
Socket 11: 32661 (0x7F8B)
Figure 5-3 Status Information on Each Socket
Socket-by-socket information covers each of the sockets used by a user application.
Note: In socket communication using FB instruction, for example of the S3 controller, a
socket number is acquired from an instruction word using USEND_T instruction.
Such socket number is managed by the controller, so that it must be converted
into a socket ID to be managed in the AN712 module. On the basis of the con-
verted socket ID, the AN712 module refers to the socket unit information avail-
able to the station bus.
Offset
32640～
（0ｘ7F80～）
TCP： 1 with socket using TCP, always 0 for AN712
UDP： 1 with socket using UDP; 0 if UDP is unused (closed)
AOP： 1 with socket opened active (only when TCP is used); always 0 for AN712
POP： 1 with socket opened passive (only when TCP is used); always 0 for AN712
CON： 1 with socket connection established (only when TCP is used); always 0 for AN712
RCV： 1 for received data, 0 for no received data
TCP UDP AOP
POP
CON
RCV
RCL
(Reserv ed)
15 14 13
12
11
10
9
8
7
0
AN_TALKMAP_s
To Next Page
Loading...
