Mitsubishi Electric MELSEC iQ-F Series User Manual page 41

Client function
With the UCMM message communication client function, the buffer memory of the FX5-ENET/IP is used to send command
requests to and receive command responses from the EtherNet/IP device.
The client function can be used to access the services of each EtherNet/IP device and thereby read and write items such as
the data and parameters with arbitrary timing.
CPU module
(2)
Device
(2)
Device
(1) Turn on 'EtherNet/IP communication start request' (Un\G37.b0)
(2) Transfer the stored data with a program
(3) Turn on 'Application Trigger request' (Un\G5274 to Un\G5275)
(4) Command request
(5) Command processing execution
(6) Command response
(7) Turn on 'Application Trigger completion' (Un\G5282 to Un\G5283)
UCMM message communications with the client function is performed according to the following procedure.
1.
Starting the UCMM communication execution request ((1) to (3) shown above)
Turn on 'EtherNet/IP communication start request' (Un\G37.b0) and then turn on 'Application Trigger request' (Un\G5274 to
Un\G5275) from the FX5-ENET/IP on the client side.
2.
Sending the command request ((4) shown above)
When the FX5-ENET/IP checks the UCMM data link execution request, 'Application Trigger acceptance' (Un\G5278 to
Un\G5279) is turned on, and then the command request is sent to the EtherNet/IP device.
3.
Command response acceptance ((5) to (6) shown above)
The EtherNet/IP device executes the command processing, and then returns the command response.
When the FX5-ENET/IP receives the command response from the EtherNet/IP device, the FX5-ENET/IP turns on 'Application
Trigger completion' (Un\G5282 to Un\G5283) to complete the processing.
For the operation timing of EtherNet/IP communications, refer to the following.
Page 148 Application Trigger
FX5-ENET/IP
Client
(1)
(3)
'UCMM
communications
output data area
(connection1)'
(Un\G84000 to
Un\G84749)
(7)
'UCMM
communications
input data area
(connection1)'
(Un\G36000 to
Un\G36749)
EtherNet/IP device
Server
(4)
(6)
4 FUNCTION
4.2 EtherNet/IP Communication Functions
4
(5)
39