Advanced Settings; Multi-Block - Mitsubishi Electric MELSEC iQ-R Series User Manual

8.17

Advanced Settings

Series
MELSEC-Q series
MELSEC iQ-R series
Make settings required to implement the various scenarios defined in GEM.

Multi-block

If messages from device or host are exchanged across multiple blocks, it is necessary to implement multi-block inquiry in
advance.
Window
[GEMData]  [Details]  [Multi-Block] tab
Displayed items
Item
Enable The Multi-Block Inquiry
(S6F5) During Event Transmission
Treat Single Block Data ID As Zero
Length Item
Enable Multiblock Inquiry (S2F39) Of
The Host
Multi-block inquiry
Please note the following about the Multi-block inquiry of the host.
• S2F23 (trace condition configuration) is a message subject to multi-block by SEMI E5, but the SECS/GEM communication
software cannot receive multi-blocks because <DATAID> has not been attributed.
8 GEM COMPLIANT FUNCTIONS
232
8.17 Advanced Settings
SECS/GEM communication software
Non-GEM version


Description
Select this checkbox if it is necessary to send an S6F5 (multi-block data sending inquiry) at the time of an S6F11
(event report sending).
The maximum number multi-block retries is 32.
Select this checkbox to treat the item <DATAID> of an S6F11 (event report sending) to be sent in single block as a zero
length item.
Select this checkbox if an S2F39 (multi-block inquiry) may be received ahead of receiving the following messages from
the host.
S2F33 (Define Report)
S2F35 (Link Event Report)
S2F45 (Define Variable Limit Attributes)
S2F49 (Enhanced Remote Command)
Whether all messages are received within a time set for "Scenario Watchdog Timer" is monitored. If a timeout occurs,
S9F13 (Conversation Timeout) is automatically sent.
The item data in this case shall be "S2" for <MEXP> and the target DATAID for <EDID>.
The Scenario Watchdog Timer can be configured up to 999 seconds.
GEM version


GEM advanced version

