Manual name [manual number] Description Available form C Controller/C Intelligent Function Module SECS/ GEM Communication Software Pre-installed Model User's Manual [BCN-89999-6494] (this manual) Explains the specifications, procedure before operation, wiring, functions, and troubleshooting of a C Controller pre-installation module. PDF
C Controller/C Intelligent Function Module SECS/GEM Communication Software Pre-installed Model User's Manual
-Q12DCCPU-V-BZ11 -Q12DCCPU-V-BZ13 -Q12DCCPU-V-BZ15 -RD55UP06-V-BZ11 -RD55UP06-V-BZ13 -RD55UP06-V-BZ15
SAFETY PRECAUTIONS
(Read these precautions before using this product.) Before using this product, please read this manual and the relevant manuals carefully, and pay full attention to safety to handle the product correctly. The precautions in this manual concern this product only. Regarding the safety precautions as a programmable controller system, refer to the user manual of the module to be used.
1
CONDITIONS OF USE FOR THE PRODUCT
(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions; i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident; and ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries. MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT. ("Prohibited Application") Prohibited Applications include, but not limited to, the use of the PRODUCT in; · Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the public could be affected if any problem or fault occurs in the PRODUCT. · Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality assurance system is required by the Purchaser or End User. · Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator, Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other applications where there is a significant risk of injury to the public or property. Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details, please contact the Mitsubishi representative in your region.
2
INTRODUCTION
Thank you for purchasing the SECS/GEM communication software. This manual describes the necessary system configuration, specifications, wiring, and troubleshooting to use the SECS/GEM communication software. Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the functions and performance of the SECS/GEM communication software to handle the product correctly. Please make sure that the end users read this manual.
About this manual
This manual describes the SECS/GEM communication software that has been installed on a C Controller module or C intelligent function module. Before using the SECS/GEM communication software, carefully read the relevant manuals of the C Controller module or C intelligent function module to thoroughly understand the functions and performance of the module. For details of the SEMI standards, please check the SEMI standards.
3
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Scope of operation description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
CHAPTER 1 SPECIFICATIONS
10
1.1 SEMI standards compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.2 GEM standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.3 Communication Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.4 Message specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.5 GEM related specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
CHAPTER 2 PROCEDURE BEFORE OPERATION
15
2.1 Network Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.2 SECS/GEM communication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CHAPTER 3 SYSTEM CONFIGURATION
18
3.1 Overall System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.2 Software Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
SECS/GEM Communication Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Configuration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.3 Connected Device Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.4 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
CHAPTER 4 WIRING
22
CHAPTER 5 INSTALLATION AND UNINSTALLATION
24
5.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Configuration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 SECS/GEM communication software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 License registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.3 Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 SECS/GEM communication software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CHAPTER 6 FUNCTION LIST
29
CHAPTER 7 BASIC FUNCTIONS
36
7.1 Management of projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Sample transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.2 Programmable Controller CPU link function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Handshake (for each transaction) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Handshake (for each message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 None handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4
CONTENTS
7.3
7.4 7.5 7.6
7.7 7.8 7.9 7.10 7.11 7.12 7.13
7.14
Periodic message transmission to the host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 How to link with devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Transaction definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Transaction list display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Display of transaction data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Editing of transaction information definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Format specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Message Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Item Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Message structure of the SECS/GEM communication software pre-installed model module . . . . . . . . . . . . . . . 60 Communication Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 SECS communication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Communication Setting by PLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Device Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Shared Memory Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 I/O assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Option Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Control 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Control 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Retry setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 CA Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Control Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 SECS Error Notification Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 S9 Transmission Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Console Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Scenario definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Scenario Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Alarm Definition (non-GEM version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Alarm List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Alarm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Alarm Notification Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Spooling function (non-GEM version). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Spool Definition Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Spooled message sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Project Archive File Get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Updating the SECS/GEM communication software pre-installed model module . . . . . . . . . . . . . . . . . . . 112 IP address setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Changing the IP address from the setting tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 IP Address Setting by PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Data Mapping Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Command Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Mapping Setting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Conversion Table Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Conversion Table Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Conversion Data List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Conversion Data Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Example of Conversion Table Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Format conversion definition setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5
7.15 7.16 7.17
Device Find/Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Display all devices in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Device Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Replace Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Log Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Log Output Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Real Time Trace Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 View the Log on Display Device (GOT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Considerations when the log output function is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 SECS Message Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Device Assignment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
CHAPTER 8 GEM Compliant Functions
156
8.1 8.2 8.3 8.4 8.5 8.6 8.7
8.8
8.9 8.10 8.11
8.12
8.13
GEM PERFORMANCE DEFINITION SETTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 About State Model Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 GEM MODEL STATE NOTIFICATION SETTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 COMMUNICATION STATE MODEL MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Communication state model setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 CONTROL STATE MODEL MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Control state model setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 PROCESSING STATE MODEL MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Process state model setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Alarm Definition (GEM / GEM advanced version). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Alarm List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Alarm Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Common Alarm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Spool Function (GEM / GEM advanced version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Spool list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Spool Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Common Spool Definition settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 PROCESS PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Process Program Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Clock setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 VARIABLE SETTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Cache settings variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Variable definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 List setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Variables defined by default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 LIMIT ATTRIBUTE DEFINITION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Limit attribute list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Limit attribute definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 REPORT SETTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Report list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Report definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Create Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Default Definition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6
CONTENTS
8.14
8.15 8.16 8.17
8.18
EVENT SETTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Event definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Create Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Events defined by default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 DYNAMIC SETTING CHANGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 EQUIPMENT CONSTANT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 ADVANCED SETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Multi-block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Limit monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 SECS items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Dynamic setting exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Data acquisition exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 DVVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Reply Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 GEM COMPLIANT TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
CHAPTER 9 SECS/GEM Communication Software Knowledge
222
9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 9.11 9.12 9.13 9.14 9.15 9.16 9.17
Checking that start-up of the SECS/GEM communication software completed . . . . . . . . . . . . . . . . . . . . 222 Checking the SECS line state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Checking the registration state of the SECS/GEM communication software license . . . . . . . . . . . . . . . 223 Sending and receiving messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Sending alarm messages (S5F1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Using the spool function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Changing the communication settings from the ladder program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Using the mapping function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Using the conversion table function (table conversion) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Using the conversion table function (format conversion). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Using the conversion table function (index conversion) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Remote command control using the selection list function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Synchronizing the clocks of the equipment and host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Transitioning to a communication state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Transitioning to a control state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Configuring collected events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Using the process program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Usage method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
CHAPTER 10 TROUBLESHOOTING
253
10.1 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
APPENDIX
260
Appendix 1 Input/output signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Initialization setting of host station device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Appendix 2 Data type conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Appendix 3 Reserved Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
List of reserved transactions and format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Special Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 System Error (S9Fx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Appendix 4 SECS item list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Appendix 5 Communication Specifications Check Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
7
Appendix 6 SEMI E30(GEM) Support Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Appendix 7 SECS/GEM communication software unique ACK code list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Appendix 8 Added and Changed Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
8
RELEVANT MANUALS
Manual name [manual number]
C Controller/C Intelligent Function Module SECS/ GEM Communication Software Pre-installed Model User's Manual [BCN-89999-6494] (this manual) MELSEC iQ-R C Intelligent Function Module User's Manual (Startup) [SH-081566ENG] MELSEC iQ-R C Intelligent Function Module User's Manual (Application) [SH-081567ENG] MELSEC-Q C Controller Module User's Manual [SH-081130ENG]
Setting/Monitoring Tools for the C Controller Module Version 4 Operating Manual [SH-081131ENG]
Terms
Description
Explains the specifications, procedure before operation, wiring, functions, and troubleshooting of a C Controller pre-installation module.
Explains the specifications, procedure before operation, wiring, and operation examples of a C intelligent function module.
Explains the functions, input/output signals, buffer memory, parameter setting, and troubleshooting of a C intelligent function module.
Explains the system configuration, specifications, functions, handling, wiring, troubleshooting, and functions and programming of C Controller modules (Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, Q12DCCPU-V (Extended mode)). Explains the system configuration and operation methods of the C Controller setting/monitor tools (SW4PVC-CCPU).
Available form
PDF
Print book e-Manual PDF Print book e-Manual PDF Print book PDF
Print book PDF
Unless otherwise specified, this manual uses the following terms.
Terms
MELSEC iQ-R series SECS/GEM communication software preinstalled model module MELSEC-Q series SECS/GEM communication software preinstalled model module SECS/GEM communication software
SECS/GEM communication software pre-installed model module Setting tool Non-GEM version GEM version GEM advanced version DM CM memory card
Description
Generic name of RD55UP06-V-BZ11, RD55UP06-V-BZ13, and RD55UP06-V-BZ15.
Generic name of Q12DCCPU-V-BZ11, Q12DCCPU-V-BZ13, and Q12DCCPU-V-BZ15.
Generic product names of the following software pre-installed on SECS/GEM communication software pre-installed model modules. SW1PVC-Q12V-EBZ11, SW1PVC-Q12V-EBZ13, SW1PVC-Q12V-EBZ15, SW1PVC-RD55-EBZ11, SW1PVC-RD55EBZ13, SW1PVC-RD55-EBZ15 Generic name of Q12DCCPU-V-BZ11, Q12DCCPU-V-BZ13, Q12DCCPU-V-BZ15, RD55UP06-V-BZ11, RD55UP06-VBZ13, and RD55UP06-V-BZ15.
Abbreviation of the SECS/GEM communication software setting tool pre-installed on a PC. Generic name of Q12DCCPU-V-BZ11 and RD55UP06-V-BZ11. Generic name of Q12DCCPU-V-BZ13 and RD55UP06-V-BZ13. Generic name of Q12DCCPU-V-BZ15 and RD55UP06-V-BZ15. Abbreviation of Data Message(Stream Function). Abbreviation of Command Message(linktest, Connect, etc.). Generic name of CF card and SD memory card.
Scope of operation description
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The table above in this manual indicates the SECS/GEM communication software subject to the operation description. : Subject to operation description ,: Not subject to operation description
9
1 SPECIFICATIONS
This section shows the specifications of the SECS/GEM communication software.
1.1 SEMI standards compliance
The SECS/GEM communication software complies with the following SEMI standards. : Compliant : Partially compliant : Not compliant
Standard number
E4 E5 E37 E37.1 E37.2 E30 E82*5 E88*5 Draft 6263*5
Compliant version
E4-0699 E5-1106E E37-0303 E37.1-0702 E30-0307N E82-1106 E88-0307
Standard name
SECS/GEM communication software compliance list
Q12DCCPU-V-/RD55UP06-V-
BZ11 (Non-GEM version)
BZ13
BZ15
(GEM version) (GEM advanced
version)
SEMI Equipment Communications Standard 1
*2
*2
*2
Message Transfer (SECS-)*1
SEMI Equipment Communications Standard 2
Message Content (SECS-)
High-Speed SECS Message Services (HSMS) Generic Services*3
High-Speed SECS Message Services Single Selected-Session Mode (HSMS-SS or HSMS-SSS)
High-Speed SECS Message Services General
Session (HSMS-GS)
Generic Model for Communications and Control of Manufacturing Equipment (GEM)
*4
Specifications for Interbay/Intrabay AMHS SEM (IBSEM)
Specifications for AMHS Storage SEM (Stocker SEM)
PCB equipment communication interface (PCBECI)
*1 Standards of communication that uses RS-232C. *2 Supported by Q12DCCPU-V edition only. *3 Standards of communication that uses TCP/IP. *4 Basic requirements of GEM are compliant. *5 Subset of GEM E30.
For the details of specifications and terms of SEMI standards when using the SECS/GEM communication software, check the SEMI standards.
10
1 SPECIFICATIONS 1.1 SEMI standards compliance
1.2 GEM standards compliance 1
The SECS/GEM communication software complies with the following GEM standards. : Supported : Unsupported
Required conditions of GEM standards
Basic Requirements
Additional performance
State model
Host-started communication establishment
Control state switching
Device processing state model
Event notification
Online check
Error message
Documentation
Communication establishment
Dynamic event report setting change
Variable data acquisition
Trace data acquisition
State data acquisition
Alarm management
Remote Control
Device constant
Process recipe management
Process program E42 recipe
E139 recipe
Material transfer
Device terminal service
Clock
Limit monitoring
Spooling
SECS/GEM communication software compliance list
Q12DCCPU-V-/RD55UP06-V-
BZ13 (GEM version)
BZ15 (GEM advanced version)
BZ11 (Non-GEM version)
1 SPECIFICATIONS 1.2 GEM standards compliance
11
1.3 Communication Specifications
This section shows the specifications of SECS communication.
SECS-I(SEMI E4)
Item
Device ID
Communication port Logical line Communication speed Number of retries Master/Slave Serial setting
Timer setting
Number of settings Value
Data length Parity Stop bit Flow control T1 T2 T3 T4
Description
1 0 to 32767 RS-232C, 1 port Single line (full duplex) 9600 to 115200bps 0 to 31 retries Master/Slave B8, B7 None, even, odd S1, S2 None, XON/XOFF, hardware 0.1 to 10s 0.2 to 25s 1 to 120s 1 to 120s
HSMS(SEMI E37)
Item
Device ID
Communication port Logical line Interface Data transmission rate Connection mode Timer setting
Line disconnection
Number of settings Value
Link test timer T3 T5 T6 T7 T8
Description
1 0 to 32767 Ethernet, 1 port Single line 10BASE-T/100BASE-TX 10Mbps, 100Mbps Passive/Active 1 to 65535s 1 to 120s 1 to 240s 1 to 240s 1 to 240s 1 to 120s Disconnection/connection by trigger relay
12
1 SPECIFICATIONS 1.3 Communication Specifications
1.4 Message specifications 1
This section shows the specifications of messages.
SECS-(SEMI E5)
Item
Stream/Function message definition range
Stream Function
Transactions with same Stream/Function
Variable length message transmission/reception
Transmission Reception
Reconnection Delay After Line Disconnection
Maximum number of transmission interleave (Number of multi-transaction queues for PLC transmission)
Maximum number of queues waiting transmission (Number of transaction queues for PLC transmission)
Maximum number of reception interleave (Number of multi-transaction queues for PLC receiving) Other SECS functions*1
*1 Handled by the C Controller module.
Description
1 to 127 0 to 255 Possible (however, must define different transaction name) For L,n, only transmit "n" lists. For L,n, up to "n" lists can be received and the number of lists received ("n") can be output to the control register. 1 to 60s 256
256
256
Scenario transmission/reception (execute more than one Stream/Function in a row)
1 SPECIFICATIONS 1.4 Message specifications
13
1.5 GEM related specifications
This section shows specifications related to GEM.
GEM related performance specifications
Item
Maximum variable setting Number of Variables that can be linked to 1 list variable Maximum number of limits that can be set for 1 variable Limit monitoring cycle Variables subjected to limit monitoring Maximum number of report definitions Number of variables that can be linked to 1 report Maximum number of events that can be defined Maximum number of reports than can be linked to 1 event Traceable variable Maximum numbers of variables that can be set for 1 Trace ID Number of variables set for 1 Trace ID × Number of Groups Number of Trace IDs that can be traced simultaneously Maximum number of processing units Maximum SECS message length Maximum ASCII data length Number of dynamic messages that can be simultaneously created Number of Cache area that can be set Maximum communication establishment timeout Maximum number of alarms that can be set
Description
65535 32767, up to 8 layers 16 1000 to 4294967294ms SV with data type other than ASCII/JIS8/BIN 512 256 512 64 SV with data type ASCII/JIS8/BIN supports up to 32 bytes. 256 4096 or below 16 99 5M Bytes (5242880 Bytes) 256 Bytes 128 32 240s 4096
14
1 SPECIFICATIONS 1.5 GEM related specifications
2 PROCEDURE BEFORE OPERATION
The following section shows the procedure until operation.
1. Mounting modules on a base unit
Install the programmable Controller CPU and SECS/GEM communication software pre-installed model module on the base
2
module.
For the installation on the base module, see the following reference.
Module to be used
C intelligent function module C Controller module
Reference
MELSEC iQ-R Module Configuration Manual C Controller Module User's Manual (Hardware Design, Function Explanation)
2. Wiring of equipment
Connect the SECS/GEM communication software pre-installed model module, personal computer, and other network equipment.
3. Installation of setting tools
Install the setting tools on the PC. For the installation method, see the following reference. Page 24 Configuration tool
When the SECS/GEM communication software pre-installed model module has been initialized, install the SECS/GEM communication software, and then activate the license again. For the method to install the SECS/GEM communication software, see the following reference. Page 112 Updating the SECS/GEM communication software pre-installed model module For the license registration method, see the following reference. Page 27 License registration
4. Setting parameters
Configure the parameters of the programmable controller CPU and the SECS/GEM communication software pre-installed model module. For the setting method of the parameters, see the following reference.
Module to be used
C intelligent function module C Controller module
Reference
MELSEC iQ-R C Intelligent Function Module User's Manual (Startup) Setting/Monitoring Tools for the C Controller Module Version 4 Operating Manual
5. Network settings
Configure the network parameters. For the configuration method, see the following reference. Page 16 Network Setting
6. SECS/GEM communication settings
Use the setting tool to configure the transaction information, communication settings, device assignment settings, etc. For the configuration procedure, see the following reference. Page 17 SECS/GEM communication settings
7. Setting update
Update the setting file stored on the SECS/GEM communication software pre-installed model module. For the update procedure, see the following reference. Page 112 Updating the SECS/GEM communication software pre-installed model module
2 PROCEDURE BEFORE OPERATION
15
2.1 Network Setting
This section explains the network configuration.
Devices
SECS/GEM communication software pre-installed model module
Host Computer for configuration
Setting method
Configure the parameters using GX Works3 or the Setting/monitoring tools for the C Controller module. Configure the PC network. Configure the PC network.
Network setting for connection
Operating procedure 1. Configure the network section of each device in the same manner.
(1) (2)
A
B
192.168.3.
3
255.255.255.
0
SECS/GEM communication software pre-installed model module
A
B
192.168.3.
15
255.255.255.
0
Host
A
B
192.168.3.
30
255.255.255.
0
Computer for configuration
A: Network section B: Host section (1) Configure the same value. (2) Configure different values.
2. Configure the network settings of the personal computer using the "Internet Protocol Version 4 (TCP/IPv4) Properties"
screen.
(Example) Windows 7 Select [Control Panel] [Network and Internet] [Network and Sharing Center] [Change adapter settings]. Select "Local Area Connection" and select [Properties] on the shortcut menu. At the "Local Area Connection Properties" screen, choose "Internet Protocol Version 4 (TCP/IPv4)", and then click the
[Properties] button. The "Internet Protocol Version 4 (TCP/IPv4) Properties" screen appears.
16
2 PROCEDURE BEFORE OPERATION 2.1 Network Setting
2.2 SECS/GEM communication settings
This section shows the procedure to use the setting tools to configure SECS/GEM communication.
1. Setting transaction information
Configure the transaction name, and then select the handshake method.
2
For the configuration procedure, see the following reference.
Page 46 Transaction definition
2. Setting message information
Configure items such as Stream Function, response monitoring setting, and triggers to report sending/reception.
For the configuration procedure, see the following reference.
Page 52 Message Information
3. Setting Item information
Configure items such as the data type, data quantity, and control register to acquire or register data.
For the configuration procedure, see the following reference.
Page 55 Item Information
4. Communication setting
Select the SECS communication method.
When HSMS is selected, configure items such as the connection mode, IP address, and timer values.
When SECS- is selected, configure items such as the RS-232C communication port setting and timer values.
For the configuration procedure, see the following reference.
Page 61 Communication Setting
5. Device assign
Register the device to be used for control of triggers, registers, etc.
For the configuration procedure, see the following reference.
Page 65 Device Assignment
6. Other settings
Configure the settings to use the alarms, spools, and other functions arbitrarily.
Always save the project after configuring each type of data and before updating the SECS/GEM communication software pre-installed model module.
2 PROCEDURE BEFORE OPERATION 2.2 SECS/GEM communication settings
17
3 SYSTEM CONFIGURATION
This section explains the configuration of the system upon which the SECS/GEM communication software runs. Use the SECS/GEM communication software pre-installed model module together with the programmable controller CPU. For the system configuration of the MELSEC iQ-R series and the programmable controller CPUs that can use the C intelligent function module, see the following reference. MELSEC iQ-R Module Configuration Manual For the system configuration of the MELSEC-Q series and the programmable controller CPUs that can use the C Controller module, see the following reference. MELSEC-Q C Controller Module User's Manual
3.1 Overall System Configuration
This section shows the overall system configuration when the SECS/GEM communication software pre-installed model module is used.
MELSEC iQ-R series SECS/GEM communication software pre-installed model module
This section shows a system configuration example when the MELSEC iQ-R series SECS/GEM communication software preinstalled model module is used.
(1) (2)
(3)
(4)
(5) (6)
(1) Programmable controller CPU (2) MELSEC iQ-R series SECS/GEM communication software pre-installed model module (3) Host (4) Computer for configuration (5) SD memory card (6) Ethernet cable
18
3 SYSTEM CONFIGURATION 3.1 Overall System Configuration
MELSEC-Q series SECS/GEM communication software pre-installed model module
This section shows a system configuration example when the MELSEC-Q series SECS/GEM communication software preinstalled model module is used.
(1) (2)
(3)
(4)
3
(6) (6) (5)
(1) Programmable controller CPU (2) MELSEC-Q series SECS/GEM communication software pre-installed model module (3) Host (4) Computer for configuration (5) CF card (6) Ethernet cable
3 SYSTEM CONFIGURATION 3.1 Overall System Configuration
19
3.2 Software Configuration
This section shows the configuration of the SECS/GEM communication software.
SECS/GEM Communication Software
Software to perform SECS/GEM communication. The software is preinstalled on the SECS/GEM communication software pre-installed model module before product shipping.
Configuration tool
Tool to configure the interface of SECS/GEM communication.
License
A license file is necessary to use the SECS/GEM communication software. The license file is activated on the SECS/GEM communication software pre-installed model module before product shipping. If the license file has been lost because of initialization of the SECS/GEM communication software pre-installed model module, activate the license again. For the license registration method, see the following reference. Page 27 License registration
Precautions
· One license file is assigned to one SECS/GEM communication software pre-installed model module. · The product CD-ROM of the SECS/GEM communication software is required to recover the license file. Store the product
CD-ROM carefully so that it is not lost.
20
3 SYSTEM CONFIGURATION 3.2 Software Configuration
3.3 Connected Device Configuration
This section shows equipment that can be connected to the SECS/GEM communication software pre-installed model module.
SD memory card (need to purchase separately)
For SD memory cards that can be used with the MELSEC iQ-R series SECS/GEM communication software pre-installed
model module, see the following reference.
MELSEC iQ-R C Intelligent Function Module User's Manual (Startup)
3
CF card (sold separately)
For CF cards that can be used with the MELSEC-Q series SECS/GEM communication software pre-installed model module, see the following reference. MELSEC-Q C Controller Module User's Manual
Precautions
Always install a memory card when using the SECS/GEM communication software. Because the number of writes to a memory card is limited, determine the necessity of writing functions, such as link test logs and programmable-controller detailed log collection, before using a card. Before removing a memory card, make sure that there is no file access. If the card is removed during data writing, internal files may become corrupted.
3.4 Operating Environment
This section shows the operating environment for configuration tool.
Item
Personal computer
Free space of installation drive
OS (English language version)
Necessary software
Description
A personal computer on which Microsoft Windows operates
During installation: free storage space of 20 MB or more
Windows 10 Windows 7 (Service Pack 1 or later) Windows XP (Service Pack 3 or later) Windows 2000 (Service Pack 4 or later)
Internet Explorer (6.0 or later)
3 SYSTEM CONFIGURATION 3.3 Connected Device Configuration
21
4 WIRING
This section explains the wiring of a SECS/GEM communication software pre-installed model module.
Ethernet cable
For Ethernet, a cable that complies with the IEEE802.3 100BASE-TX/10BASE-T standards can be used. For the specifications of cables that can be used, see the following reference. MELSEC iQ-R C Intelligent Function Module User's Manual (Startup) MELSEC-Q C Controller Module User's Manual
RS-232 cable
For the specifications of RS-232 cables that can be used, see the following reference. MELSEC-Q C Controller Module User's Manual
22
4 WIRING
MEMO
4
4 WIRING
23
5 INSTALLATION AND UNINSTALLATION
This section explains installation and uninstallation.
5.1 Installation
This section explains the installation of setting tools and the SECS/GEM communication software.
Configuration tool
Preparation for installation
Confirm the following before installing the setting tools. · Before installing the setting tools, log in as an Administrator user. · Do not run multiple installers at the same time. If multiple installers were run at the same time, installation may not be
completed normally. If installation of the tools was not completed normally, uninstall the tools, and then install them again. · If the confirmation screen for User Account Control appears during installation of the setting tools, click the "Allow" or "Yes"
button to proceed with the installation.
Installation of tools
The following procedure is an example of installing the setting tool for Q12DCCPU-V-BZ15 on a PC running Windows 7.
1. Insert the product CD-ROM into the PC.
The setup wizard starts.
If the setup wizard does not start, double-click 'setup.exe' in the "CA-SECS for GEM ADVANCED"*1 folder on the product CDROM.
*1 The folder name of the product CD-ROM differs for each product.
2. Click the [Next] button.
24
5 INSTALLATION AND UNINSTALLATION 5.1 Installation
3. Check the installation folder setting, and then click the [Next] button.
4. Click the [Next] button.
5
Installation of the setting tool starts.
5 INSTALLATION AND UNINSTALLATION 5.1 Installation
25
If installation of the setting tools is completed normally, the following screen appears.
Environment after installation
This section describes the environment after installation of the setting tools.
Menus to be registered
The menus of the installed setting tools are registered to the Start Menu of Windows.
Menu name
MELSEC
CA*1
CA-SECS E CA-SECS for GEM E CA-SECS for GEM ADVANCED E CA-SECS RD55 E CA-SECS for GEM RD55 E CA-SECS for GEM ADVANCED RD55 E
Description
Starts the setting tool for Q12DCCPU-V-BZ11. Starts the setting tool for Q12DCCPU-V-BZ13. Starts the setting tool for Q12DCCPU-V-BZ15. Starts the setting tool for RD55UP06-V-BZ11. Starts the setting tool for RD55UP06-V-BZ13. Starts the setting tool for RD55UP06-V-BZ15.
*1 Does not appear in Windows 8 or later.
SECS/GEM communication software
For the method to install the SECS/GEM communication software, see the following reference. Page 112 Updating the SECS/GEM communication software pre-installed model module
26
5 INSTALLATION AND UNINSTALLATION 5.1 Installation
5.2 License registration
The license of the SECS/GEM communication software has been activated on the SECS/GEM communication software pre-
installed model module in advance.
If the SECS/GEM communication software pre-installed model module has been initialized, the license is deleted.
In such a case, you must use the license file stored on the product CD-ROM to register the license again.
The following shows the procedure for registering the license again:
1. Copy the license file*1 from the product CD-ROM to a personal computer.
2. Select [Help][License registration]
3. Select the license file copied from the product CD-ROM.
The "Update Module" screen appears.
4. Set each item.
*1 The license file is stored in the following folder on the product CD-ROM: \\Backup\LF****.DAT
5
The license file name is 'LF****.DAT' and '****' contains 16 alphanumeric characters.
The activation destination of the license is the transfer destination (ROM or memory card) selected at the "Update Module" screen or "Update C intelligent module" screen.
Precautions
· Do not specify the license file of the product CD-ROM directly.
Checking a license
Whether a genuine license is registered can be checked by either of the following methods:
Module
MELSEC iQ-R series SECS/GEM communication software pre-installed model module
MELSEC-Q series SECS/GEM communication software pre-installed model module
Checking method
Check it in the event history of the control CPU.
Check it in the event history of Setting/monitoring tools for the C Controller module.
Registering a license again
Before registering a license again, check the following settings: · In the case of an MELSEC iQ-R series SECS/GEM communication software pre-installed model module, have the settings
that enable Ethernet communication been configured by GX Works3? · In the case of a MELSEC-Q series SECS/GEM communication software pre-installed model module, has Channel 1 of the
Ethernet port been enabled by the Setting/monitoring tools for the C Controller module?
5 INSTALLATION AND UNINSTALLATION 5.2 License registration
27
5.3 Uninstallation
This section explains the uninstallation method for setting tools and the SECS/GEM communication software.
Configuration tool
This section explains the method to uninstall the settings tool from the PC. The settings tool is uninstalled from the Control Panel of Windows.
Environment after uninstallation
During uninstallation, registered menus and files are deleted. Page 26 Environment after installation
SECS/GEM communication software
If the SECS/GEM communication software pre-installed model module is initialized, the SECS/GEM communication software is deleted. For the method to initialize the SECS/GEM communication software pre-installed model module, see the following reference. MELSEC iQ-R C Intelligent Function Module User's Manual (Application) MELSEC-Q C Controller Module User's Manual
28
5 INSTALLATION AND UNINSTALLATION 5.3 Uninstallation
6 FUNCTION LIST
This section explains the functions of the SECS/GEM communication software and setting tools.
SECS communication
: Supported : Unsupported
Function
Overview
Q12DCCPU-V-
RD55UP06-V-
BZ11 BZ13 BZ15 BZ11 BZ13 BZ15
SECS- communication function
Use a [SEMI E4 compliant] RS-232C port
to correspond with the host.
HSMS communication function
Use a [SEMI E37 compliant] Ethernet port
to correspond with the host.
Device ID specify function
Specify an arbitrary device ID.
SECS-
StreamFunction
Define SF arbitrarily within the scope of
definition (SF definition) the SECS standards and user definitions.
same SF definition
Define the same SF.
Abort Frame Sending Abort Frame Reception
Send an abort frame. Receive an abort frame.
6
Variable length frame transmission
Send a message containing a variable length item.
Variable length frame reception
Receive a message containing a variable length item.
Others
Scenario transmission/ Link and process arbitrary transactions.
reception
Reconnect upon line
Contact the host again after line recovery.
disconnection
Single transaction control
Do not process another transaction until the transaction is complete.
Multi-transaction control Process multiple transactions simultaneously.
Sending waiting queue Queue messages waiting to be sent.
Basic Requirements of GEM
: Supported : Unsupported
Function
[State model] compliance
Communication state
Control state Processing state
Spooling state [Device process state] compliant
[S1F13/F14 scenario started by host] compliant
[Event notification] compliant
[Online check] compliant
[Error messages] compliant
Overview
Manage the communication state automatically. Manage the control state automatically. Manage the processing state automatically. Manage the spooling state automatically. During transition of the processing state, report the event to the host automatically. Deals with communication establishment from the host Report the equipment event to the host automatically/manually. Respond to an online check from the host automatically. Send errors detected by the equipment to the host by an S9 message
Q12DCCPU-V-
BZ11 BZ13
BZ15
RD55UP06-V-
BZ11 BZ13
BZ15
6 FUNCTION LIST
29
Function
Overview
[Control (started by operator)] compliant
Controlling the communication state from the equipment
Control the communication state from the equipment.
Controlling the control Control the control state from the state from the equipment equipment.
[Documentation] compliant
Output documents required by GEM.
Q12DCCPU-V-
BZ11 BZ13 BZ15
RD55UP06-V-
BZ11 BZ13
BZ15
Additional GEM performance
: Supported : Unsupported
Function
[Communication establishment] compliant
[Dynamic event report setting change] compliant
[Variable data collection] compliant
[Trace data collection] compliant
Sampling Trace data sending
[State data collection] compliant
[Alarm management] compliant
Report to host Change from host
[Remote control] compliant
[Equipment constant] compliant
Configuration of equipment constants
Change from host
Report to host
[Process Recipe
Formatted process
Management] compliant programs
Equipment process program directory information
Equipment-side process program update
Deletion of equipmentside process programs
[Material transfer] compliant
[Device terminal service] compliant
[Clock] compliant
Terminal display data registration
Terminal request sending
Synchronizing the time of the module with the host time
Registration of host time to device
Time inquiry from the host
Overview
Establish communication with a host that complies with GEM. Enable the change of event reports settings dynamically from the host. Notify the host by report of the equipment variables requested from the host. Sample equipment variables periodically by an instruction from the host. Send the sampling result to the host as trace data. Report data related to state variables requested from the host to the host. Report equipment alarms to the host. Enable the change of alarm settings dynamically from the host. Deal with commands received from the host Configure the equipment constants by the setting tools. Change the equipment constants from the host. Report equipment constants requested from the host to the host. Register formatted process program from the host to the device. Send directory information of the process programs of the equipment by a request from the host. Notify the host of the update state of process programs at the equipment. Delete equipment-side process programs at the request of the host. Send a [Port transfer event] to the host by an instruction from the programmable controller CPU. Register terminal display data from the host to the device. Send a text message to the host.
Set the time of the module to the time data reported from the host.
Register the time data reported from the host to the device. Return time data that complies with the time inquiry from the host.
Q12DCCPU-V-
BZ11 BZ13
BZ15
RD55UP06-V-
BZ11 BZ13
BZ15
30
6 FUNCTION LIST
Function
[Limit monitoring] compliant
[Spooling] compliant
Monitoring of upper and lower limits of variables Event notification
Spooling target specification Spooling
Automatic spooling
Spooled data sending Spool data deletion [Control (started by host)] compliant
Overview
Monitor the transfer of the upper and lower limits of variables. Send an event to the host when a transition occurs. Specify messages subject to spooling.
Q12DCCPU-V-
BZ11 BZ13
BZ15
Spool messages subject to spooling to the memory card.
Spool messages subject to spooling to a memory card automatically during a communication disconnection.
Send spool data to the host by an instruction from the host.
Delete spool data by an instruction from the host.
Deal with instructions of online/offline
switching from the host.
RD55UP06-V-
BZ11 BZ13
BZ15
Programmable controller interface
6
: Supported : Unsupported
Function
Trigger handshake Data Type Conversion
Handshake (for each transaction)
Handshake (for each message)
No handshakes
SECS message (ASCII) internal data
Internal data SECS message (ASCII)
Shared memory synchronization
Overview
Use a trigger handshake for handshakes (for each transaction). Use a trigger handshake for handshakes (for each message). Do not use trigger handshakes. Convert from ASCII to an arbitrary data format when storing data received by an SECS message to the device. Convert an arbitrary data format to ASCII when creating an SECS message from device values. Adjust the checking interval of the multiple CPU auto refresh area.
Q12DCCPU-V-
BZ11 BZ13
BZ15
RD55UP06-V-
BZ11 BZ13
BZ15
6 FUNCTION LIST
31
Function
Status notification
Control Ready status
Control error status
Online status
Line disconnecting status Establishing communication status Queue full of messages waiting to be sent
Spooling state
Spooled message sending
Memory card error
Battery error
FTP server log output error
Overview
Reports that the SECS/GEM communication software that started is in a controllable state.
Checks the operation state of the SECS/ GEM communication software.
Reports that an online state was established with the host (S1F1S1F2).
Reports that the line with the host was disconnected.
Reports that communication was established with the host.
Reports that the count of the sending message queue from the SECS/GEM communication software became full.
Reports that messages subject to spooling are being spooled.
Reports that the SECS/GEM communication software is sending messages subject to spooling.
Reports that some kind of error was detected in the memory card.
Reports that the built-in battery has been depleted.
Reports that the log output to the FTP server failed.
Q12DCCPU-V-
BZ11 BZ13
BZ15
RD55UP06-V-
BZ11 BZ13
BZ15
32
6 FUNCTION LIST
Function
Overview
Q12DCCPU-V-
RD55UP06-V-
BZ11 BZ13 BZ15 BZ11 BZ13 BZ15
SECS communication error notification
Abort Frame Reception
Reports that an abort message was received from the host.
Abort Frame Sending
Reports that an abort message was sent from SECS/GEM communication software.
Sending failure
Reports that data sending to the host failed.
T1 timeout occurred
Reports that a timeout occurred between
characters during reception from the host.
T2 timeout occurred
Reports that a protocol timeout occurred with the host.
T3 timeout occurred
Reports that a response timeout occurred
with the host.
T4 timeout occurred
Reports that a timeout occurred between
message blocks during reception from the
host.
T9 timeout occurred
Reports that a T9 timer management
timeout occurred.
Scenario Interruption
Reports that the scenario execution was
interrupted for some reason.
6
Handshake failure
Reports that a handshake link with the
programmable controller CPU failed
during data reception.
Communication error
Reporting the Stream Function number generated by a transmission error. Reporting the trigger relay generated by a transmission error.
System error (S9) message sending
Reports that a system error (S9) message was sent.
Control Request
Line Connection
Specify port open in the case of SECS- communication. Specify Connect or Select in the case of HSMS.
Line Disconnection
Specify port close in the case of SECS- communication. Specify Disconnect in the case of HSMS.
Offline
Specify a transfer to offline state.
Online Start
Start in an online state.
Abort Frame Sending
Specifies sending of an abort frame for the
received primary message.
S9F7 sending
Specify S9F7 sending.
Spool function ON/OFF Switches the spooling function on and off
switching
by a relay.
Spooled message sending
Specifies sending of spool messages.
Spooled message discarding
Specifies discarding of spool messages.
Scenario Interruption
Specifies interruption of the scenario.
Log output start/end
Specifies the start/end of output of SECS
transmission logs, programmable
controller CPU logs, and user logs.
6 FUNCTION LIST
33
Basic Functions
: Supported : Unsupported
Function
Transaction Monitoring timer Data processing
Transaction list display Defining the transaction property Cache settings
Message Information
Defining the item property Fixed-length ASCII item correction function
PLC Response Monitoring Timer
Secondary Monitoring Timer
Transaction response monitoring timer
Overview
Display defined transactions as a list. Define the names of transactions.
Q12DCCPU-V-
BZ11 BZ13 BZ15
Define the cache of the device to be used by the transaction.
Define the message information of transactions.
Define the item properties of messages.
During fixed-length ASCII item data sending, correct so that the data length is fixed length.
Monitors and detects non-response of the programmable controller CPU by the PLC Response Monitoring Timer.
Monitor and detect secondary sendingback non-requests by the Secondary Monitoring Timer.
Monitor and detect the transaction execution interval by the transaction response monitoring timer.
Table Convert Setting
Transmission data mapping processing settings
RD55UP06-V-
BZ11 BZ13
BZ15
Logs
: Supported : Unsupported
Function
Logging
SECS transmission log
Link Test Log
Programmable controller log
User Log
Real time trace
Save Destination
Memory card
FTP server
Logging output to device (display log on display device)
Log trigger start/end
Log data acquisition method Log View
Overview
Summary display, list structure display, detailed display Transmission data file saving (number of retention days specification, one-hour units)
Link Test log output selection is possible.
Select all SECS/GEM Communication Software link I/Os or only trigger relays, and then output.
Output logs of character string data stored in a designated register.
Output SECS data and device I/O information to registers.
Output logs to a memory card.
Output logs to the FTP server.
Display SECS transmission logs, programmable controller CPU logs, and user logs on a display device via registers.
Available (SECS communication log output, programmable controller log output, and user log output relay trigger specifications) FTP/RS-232C*1
Displays acquired logs.
Q12DCCPU-V-
BZ11 BZ13
BZ15
RD55UP06-V-
BZ11 BZ13
BZ15
*1 Supported for only the MELSEC-Q series SECS/GEM communication software pre-installed model module.
34
6 FUNCTION LIST
Others
: Supported : Unsupported
Function
Overview
Q12DCCPU-V-
RD55UP06-V-
BZ11 BZ13 BZ15 BZ11 BZ13 BZ15
Conversion
Supplements the differences of project file
structures due to product version
upgrades.
Definition content network download function
Transfer the setting content to the SECS/ GEM communication software preinstalled model module.
User definition archive function
Archive the setting file, and then save it to the SECS/GEM communication software pre-installed model module.
Automatic restart after update function
Re-import an updated settings file by restarting the control software, but not stopping the equipment.
Definition information documentation output
Output the SECS message definitions and
device assignment definitions as a .csv
file.
IP address setting
Configuration from
Configure the IP address of the SECS/
6
function
setting tools
GEM communication software pre-
installed model module from the setting
tool.
Configuring via registers
Configure the IP address of the SECS/ GEM communication software preinstalled model module via registers.
Device Find/Replace
Device search
Search for devices in use.
Replace Device
Replace devices in use.
6 FUNCTION LIST
35
7 BASIC FUNCTIONS
7.1 Management of projects
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Projects of the SECS/GEM communication software are managed by .xml files that define transactions and other environment setting files. There are two methods to create a new project: open an existing transaction and then arrange it following company use or create a new transaction. This section explains how to manipulate projects, such as creating new projects, opening projects and saving projects.
Creating a new project
Create a project. In the transaction list of the newly created project, there is blank data by the name "New transaction".
[File][New Create]
Opening a project
Import a saved project. [File][Open]
Save / Save as New
Save an edited project. [File][Overwrite Save] or [Save As]
Conversion
Convert a project created by a previous version of the setting tool so that it can be opened by the setting tool currently in use.
Window
[File][Convert]
Displayed items
Item
Folder File [Convert] button
Description
Select the folder that is storing the setting file. Select the transaction setting file for conversion. Convert the type of file in the selected folder.
36
7 BASIC FUNCTIONS 7.1 Management of projects
Sample transactions
A sample that collects generally used transactions is saved in the following folder during installation. You can use the sample as well when learning the usage of the SECS/GEM communication software. Sample transactions: (SECS/GEM communication software installation folder)/SAMPLE/SAMPLE.XML
7
7 BASIC FUNCTIONS 7.1 Management of projects
37
7.2 Programmable Controller CPU link function
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
A relay must be linked between the programmable controller CPU and the SECS/GEM communication software when messages are transmitted. There are three methods to link the relay. · Handshake (for each transaction) · Handshake (for each message) · None handshake The following table shows the features of each method.
Type
Relay Operation of relay
Ladder programming
Link with programmable controller CPU Feature
Handshake (for each transaction)
· A same relay is used for both reception and transmission.
· Number of relays used = Number of transactions
Primary message reception secondary message sending: SECS/GEM communication software turns the relay ON during a reception notification, and then programmable controller turns the relay OFF during a sending request. Primary message sending secondary message reception: The programmable controller turns the relay ON during a sending request, and then SECS/GEM communication software turns the relay OFF during a reception notification.
Processing is necessary to switch the trigger detection method ON or OFF depending on the distinction of the operations above.
Detectable for each transaction
Handshake (for each message) None handshake
· Different relays are used for reception and transmission. · Number of relays used = Number of transactions × 2
Reception: The SECS/GEM communication software turns the relay ON, and then sends notification, and then the programmable controller turns the relay OFF. Transmission: The Programmable Controller CPU turns the relay ON to request the transmission and then SECS/GEM communication software turns the relay OFF.
Reception: The SECS/GEM communication software turns the relay ON, and then turns it OFF after keeping the trigger for a predetermined time. Transmission: The programmable controller CPU turns the relay ON, and then turns it OFF after holding the trigger for a predetermined time.
A same trigger detection mechanism should be used.
Detectable for each message
A same trigger detection mechanism should be used, but the system should be programmed to turn the transmission request relay OFF after a fixed monitoring time and to prevent double detection after the receive notification detection.
This mode cannot be used for S9 related messages (only primary messages) or messages subject to spooning (no secondary message during spooling)
Precise processing is available for each message.
This mode has less effect on existing ladders and is preferred for modifying existing equipment into an on-line system.
38
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
The following diagram shows the timing to link relays in each method.
Message transmission
Transmission processing completion
Transmission data acquisition
Transmission trigger detection
Transmission request
Transmission data registration
Reception processing completion
Reception data acquisition
Reception trigger detection
Receive notification
Reception data registration
Message ception
(1)
Handshake (for each message)
Reception
Transmission
Handshake
(5)
(for each transaction)
Reception
(2) (3)
Transmission (6)
(4) (7)
(8)
(9)
None handshake
Reception
Trigger keep time
(10)
(11)
Transmission
Processing by Programmable
(12)
7
Controller CPU
Processing by SECS/GEM communication software (1) SECS/GEM communication software starts. (2) Programmable Controller CPU turns off. (3) Programmable controller CPU starts. (4) SECS/GEM communication software turns off.
(5) The SECS/GEM communication software starts. (6) Programmable Controller CPU turns off. (7) The sending request trigger is detected by the trigger relay switching OFF. *1
(8) The SECS/GEM communication software starts. (9) SECS/GEM communication software turns off. (10) Programmable controller CPU starts. (11) Programmable Controller CPU turns off. (12) The trigger is detected when the relay remains ON for the predetermined hold time.
*1 The same sequence applies to the transaction from sending request to reception notification.
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
39
Handshake (for each transaction)
This section shows the operation flow to link trigger relays by handshakes for each transaction. The following section is an example of when receiving a message from the host.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
(2)
(1)
(4) (3)
The trigger relay is turned on.
(5)
(6)
(8) (7)
The trigger relay is turned off.
(9)
(10)
(1) A message is received from the host. (2) The SECS/GEM communication software stores the received data in the shared memory/device. (3) SECS/GEM communication software turns the trigger relay ON (OFFON control) to inform the Programmable Controller CPU of the reception. (4) The programmable controller CPU detects the trigger relay. (5) After the programmable controller CPU acquires the received data in the shared memory/device, the received data is processed by a program of the programmable controller CPU. At this time, the programmable controller CPU does not turn the trigger relay OFF. (6) The programmable controller CPU configures the sending data to the shared memory/device. (7) The Programmable Controller CPU turns the trigger relay OFF (ONOFF control) to request a transmission. (8) The SECS/GEM communication software detects the trigger relay. (9) The SECS/GEM communication software acquires the data of the item section of the sending transaction from the shared memory/device of the programmable controller CPU. (10) After editing the data into a SECS- transaction message, SECS/GEM communication software transmits the message to the host.
The procedure when data is sent from the programmable controller CPU is the same as above. The programmable controller CPU stores the sending data in the shared memory/device, and then turns the trigger relay ON. During return receipt, the SECS/GEM communication software stores the received data in the shared memory/device, and then switches the trigger relay OFF. After this, the programmable controller CPU acquires the data.
40
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
Handshake (for each message)
This section shows the operation flow to link trigger relays by handshakes for each message. The following section is an example of when receiving a message from the host.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
(2)
(1)
(4) (3)
The receive notification relay is
turned on.
(5)
The receive notification relay is
turned off
(6)
7
(8) (7)
The transmission request relay is turned
on
(9)
(11)
(10)
(1) A message is received from the host.
The transmission request relay is turned
off
(2) The SECS/GEM communication software stores the received data in the shared memory/device.
(3) SECS/GEM communication software turns the receive notification trigger relay ON (OFFON control) to inform the Programmable Controller CPU of the reception.
(4) The Programmable Controller CPU detects the receive notification trigger on state.
(5) After the programmable controller CPU acquires the received data in the shared memory/device, it turns the reception notification trigger relay OFF, and then performs response confirmation. (ON to OFF control) The reception data is processed by a program of the programmable controller CPU.
(6) The programmable controller CPU configures the sending data to the shared memory/device.
(7) The Programmable Controller CPU turns the transmission request trigger relay ON (OFFON control). (8) The SECS/GEM communication software detects the sending request trigger.
(9) The SECS/GEM communication software acquires the data of the item section of the sending transaction from the shared memory/device of the programmable controller CPU.
(10) After editing the data into a SECS- transaction message, SECS/GEM communication software transmits the message to the host.
(11) The sending request trigger relay is switched OFF. (ON to OFF control)
The procedure when data is sent from the programmable controller CPU is the same as above.
The programmable controller CPU stores the sending data in the shared memory/device, and then turns the sending request
trigger relay ON.
During return receipt, the SECS/GEM communication software stores the received data in the shared memory/device, and
then switches the reception notification trigger relay ON.
After this, the programmable controller CPU acquires the data.
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
41
Important points when configuring to Handshake (for each message)
Reception delay
Configure a 20 ms trigger hold time in the settings of secondary message sending for transactions during primary message reception.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
Receive notification detection
Receive notification relay off
Transmission request relay on
Receive notification
Primary message reception
Transmission request detection
(20ms hold time)
Secondary message transmission
Primary message sending after secondary message sending
Make sure that the sending request trigger of the secondary message has been switched OFF by the SECS/GEM communication software after the secondary message was sent and before the primary message of the next transaction is sent.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
Transmission request relay on
Transmission request detection
Transmission request relay on*1
Transmission request relay off
Secondary message transmission
Transmission request detection
*1 Turns ON after checking that the sending request is OFF.
Transmission request relay off
Primary message transmission
42
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
Handshaking operations for each message
This section shows the handshake operations when message sending was successful, unsuccessful, and canceled.
No. Event
1
Transmission completed
Spooling succeeded
2
Transmission failed
Spooling failed
3
Transmission cancelled
Description
The message was transmitted. The spool message was spooled.
The message was not transmitted (including the message creation failure). The spool message was not spooled.
The transmission request was cancelled due to line disconnection or offline status.
Operation
Sending request trigger relay: OFF
Sending request trigger relay: Not OFF Transmission failed relay: ON
Sending request trigger relay: OFF Transmission failed relay: ON
When a message excluded from spooling is sent during spooling, operation depends on the communication state. · When the communication state is Online, message sending fails. · When the communication state is Offline or a line disconnection has occurred, sending is canceled.
7
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
43
None handshake
This section shows the operation flow to send messages without using handshakes. SECS/GEM communication software that receives a message from the host turns the trigger relay for reception notification ON and then OFF. Similarly, the transmission request relay turned ON by the Programmable Controller CPU should be turned OFF by the Programmable Controller CPU itself. The following section is an example of when receiving a message from the host.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
(2)
(1)
(4) (3)
The receive notification relay is turned on.
It is turned off after a predetermined keep time.
(5)
(6)
(8) (7)
The transmission request
relay is turned on.
It is turned off after a
predetermined hold time.
(9)
(10)
(1) A message is received from the host. (2) The SECS/GEM communication software stores the received data in the shared memory/device. (3) SECS/GEM communication software turns the receive notification trigger relay ON (OFFON control) to inform the Programmable Controller CPU of the reception. This receipt notification trigger relay will remain ON for a predetermined time and then be turned OFF by SECS/GEM communication software itself. (4) The Programmable Controller CPU detects the receive notification trigger on state. (5) After the programmable controller CPU acquires the received data in the shared memory/device, the received data is processed by a program of the programmable controller CPU. (6) The programmable controller CPU configures the sending data to the shared memory/device. (7) The Programmable Controller CPU turns the transmission request trigger relay ON (OFFON control). Note that this sending request trigger relay is switched OFF by the programmable controller CPU after a prescribed hold time. (8) The SECS/GEM communication software detects the sending request trigger. (9) The SECS/GEM communication software acquires the data of the item section of the sending transaction from the shared memory/device of the programmable controller CPU. (10) After editing the data into a SECS- transaction message, SECS/GEM communication software transmits the message to the host.
The procedure when data is sent from the programmable controller CPU is the same as above.
44
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
Periodic message transmission to the host
Message transmission from the Programmable Controller CPU to the host at fixed intervals does not involve trigger handshake. The following shows the flow:
1. The programmable controller CPU turns ON the sending request trigger relay of a message for which periodic sending is
configured after sending data is stored in the shared memory/device of the programmable controller CPU.
2. The SECS/GEM communication software sends periodic messages to the host while an ON status of the sending
request trigger relay configured for periodic sending is detected. If the transmission data is updated by the Programmable Controller CPU during periodic message transmission, subsequently the updated data will be transmitted.
3. The programmable controller CPU turns OFF the sending request trigger relay configured for periodic sending to end the
cyclic message sending.
Precautions
When a secondary message was received, turn OFF the reception notification trigger relay. Otherwise, it causes the reception queue to become full.
How to link with devices
When defining message information and item information, it is possible to use a device as a control register.
7
It is necessary to configure in advance the device information to link the SECS/GEM communication software pre-installed
model module, programmable controller CPU, and I/O unit.
For the configuration procedure, see the following reference.
Page 65 Device Assignment
7 BASIC FUNCTIONS 7.2 Programmable Controller CPU link function
45
7.3 Transaction definition
This section explains the definition method of transactions, message information, and item information.
Transaction list display
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Display defined transactions as a list. In the non-GEM version, the main screen is the "Transaction definition" screen. For the GEM version and GEM advanced version, select the [Transaction] tab of the Main screen, and then switch to the "Transaction definition" screen.
Window
Displayed items
Display content
Handshake Primary message
Secondary message
Cyclic measurement
SF Sending request
Reception notification
SF Sending request
Reception notification
Details
When the handshake specification is Handshake (for each transaction), "T" is displayed. When the handshake specification is Handshake (for each message), "M" is displayed. When the handshake specification is None, "N" is displayed.
Displays the SF information of primary messages.
Displays the sending request trigger relay of primary messages. When there is no setting, "" is displayed. In the case of a reserve transaction, "-" is displayed.
Displays the reception notification trigger relay of primary messages. When there is no setting, "" is displayed. In the case of a reserve transaction, "-" is displayed.
Display the SF information of secondary messages.
Display the sending request trigger relay of secondary messages. When there is no setting, "" is displayed. When the handshake specification is Handshake (for each transaction) or in the case of a reserve transaction, "-" is displayed.
Display the reception notification trigger relay of secondary messages. When there is no setting, "" is displayed. When the handshake specification is Handshake (for each transaction) or in the case of a reserve transaction, "-" is displayed.
When the interval is specified, the interval value is displayed in units of ms. When the interval storage register is specified, the assigned register is displayed. When there is no cyclic sending, "" is displayed.
46
7 BASIC FUNCTIONS 7.3 Transaction definition
Operations of transaction list
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the Scenario Explorer screen to edit the content of the selected transaction. Insert a new transaction. Copy the selected transaction, and then copy the copied transaction to the row below. Move the selected transaction.
Delete the selected transaction.
7
7 BASIC FUNCTIONS 7.3 Transaction definition
47
Display of transaction data
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Display the message (primary/secondary) information and item information that belong to transactions.
Window
Select a transaction from the transaction list, right-clickShortcut menu [Edit]
Operations of the Scenario Explorer screen
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert Child] Right-clickShortcut menu [Insert Sibling Before] Right-clickShortcut menu[Insert Sibling Before] Right-clickShortcut menu[Copy] Right-clickShortcut menu[Paste] Right-clickShortcut menu[Paste Insert Child] Right-clickShortcut menu[Paste Insert Sibling Before] Right-clickShortcut menu[Paste Insert Sibling After] Right-clickShortcut menu[Import]
Right-clickShortcut menu[Export] Right-clickShortcut menu[Delete]
Description
Edit the content of the selected transaction, message, or item. Add the new item data to the level below the selected data. Add the new item data to the same level as the selected data.
Copy the selected message/item. Paste the copied data to the position of the selected data. Paste the copied data to the level below the selected data. Paste the copied data to the same level as the selected data.
Import the content of the selected message to a .csv file. Data is overwritten by the content to be imported, so take care if the item has already been defined. Export the content of the selected message to a .csv file. Delete the selected data.
The message import/export function allows you to edit data using Microsoft Excel or another external editor when the item data is voluminous or redundant. If some data items are defined and then exported to a file, you can check and edit the content of the item definitions using an external editor. Next, import the results of the editing.
48
7 BASIC FUNCTIONS 7.3 Transaction definition
Editing of transaction information definitions
Series
MELSEC-Q series MELSEC iQ-R series
Edit the transaction information.
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
Window
Select a transaction at the "Scenario Explorer" screen, right-click Shortcut menu [Edit]
Non-GEM version
GEM / GEM advanced version
7
Displayed items
Item
Description
Name
Configure the transaction name. (,),", <, >, ', and & cannot be used.
Comment Handshake specification Format specification*1 [Advanced Settings] button
Configure the comment. ", <, >, ', and & cannot be used.
Specify the trigger handshake method. For details on trigger handshakes, see the following reference. Page 38 Programmable Controller CPU link function
Specify the format. For details on formats, see the following reference. Page 51 Format specification
Displays the cache setting screen. For details on cache settings, see the following reference. Page 50 Cache settings
*1 Appears in the non-GEM version only.
When defining a transaction with the same Stream-Function number but a different message configuration, you can configure by distinguishing the transaction name.
7 BASIC FUNCTIONS 7.3 Transaction definition
49
Cache settings
This section explains the cache settings. Configure cache when a large volume of registers defined by I/O assignment are used by item data.
Window
[Transaction information screen][Detail]
Displayed items
Item
No. Use Start Register Counts Frame Type
Description
Select the setting number by Handshake (for each transaction). When cache settings will be used, select the checkbox. Configure the first register to be used. Configure the quantity of registers to be used. Select the frame to use the cache settings (primary message / secondary message / both).
Up to 20 KB can be configured for one cache setting. Up to 10240 registers can be configured at 20 KB. Up to 2048 shared memory units can be configured at 20 KB. To obtain maximal performance, edit the related data in the continuous region so that the register range to be registered by the cache setting is reduced as low as possible.
50
7 BASIC FUNCTIONS 7.3 Transaction definition
Format specification
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Send a reserved transaction frame or special transaction frame configured by the SECS/GEM communication software by an arbitrary frame.
Window
For details on reserved transactions, see the following reference.
Page 268 List of reserved transactions and format
For details on special transactions, see the following reference.
Page 269 Special Transactions
This section shows the settings that can be selected by frame specification.
7
Setting
Description
NORMAL
Run the action of the general transaction message.
ALARM
· Send this specification message in place of S5F1 of automatic sending. · By selecting ALARM, it is possible to specify ALCD/ALID/ALTX for the storage destination type of items. · Because sending is performed automatically by the alarm function, the sending request trigger relay and
reception notification trigger relay cannot be configured. For details on alarms, see the following reference. Page 100 Alarm Definition (non-GEM version)
OFFLINE
Specify when you want to use an arbitrary message as an offline notification. This setting message can be sent by preference due to transition to offline.
Use messages configured to "ALARM" and "OFFLINE" for primary messages of equipment origin. "ALARM" and "OFFLINE" can be specified only for a single message each for all transaction definitions.
7 BASIC FUNCTIONS 7.3 Transaction definition
51
Message Information
Series
MELSEC-Q series MELSEC iQ-R series
Edit the message information.
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
Window
Select a message at the "Scenario Explorer" screen, right-click Shortcut menu [Edit]
52
7 BASIC FUNCTIONS 7.3 Transaction definition
Displayed items
Item
Description
Name
Configure the message name.
Comment
Configure the comment.
Stream
Select a stream (SECS message section: 1 to 127).
Function
Select a function (designated message within stream: 1 to 255).
Response Monitoring
Select this checkbox to monitor the secondary message response corresponding to the primary message sending. When a primary message is sent from the SECS/GEM communication software, the wait bit (W bit) of the primary message is configured to ON, which indicates that there must be a secondary message to the other party.
Transmission Request Trigger
Control Register Trigger hold time
Select this checkbox to send a message by a trigger notification from the programmable controller CPU.
Configure the sending request trigger relay.
A sending request trigger results when the sending request trigger relay was held for the configured time. If the "Disable" checkbox is selected, sending request trigger processing is carried out without hold monitoring.
Cyclic
Transmission*1
Select this checkbox to send in cycles. When the sending request trigger is ON, sending occurs at the time interval configured for Interval.
Interval unit
Configure the unit of time for cyclic sending.
Interval
Select to configure the time interval of cyclic sending.
For details on the configurable range, see the following reference.
Page 54 Interval unit and configuration range
7
Interval
Select when a register is used for the Interval setting.
Storage
For details on the configurable range, see the following reference.
Register
Page 54 Interval unit and configuration range
Response
Message
Monitor Setting*1
Select this checkbox when dialog monitoring is necessary for sequence processing between the equipment and host. This time is monitored when the primary message is sent, the secondary message is received, and then the primary message to be received from the host has been determined.
T9 Timer
Specify the monitoring time.
Response Message
Select the message subject to receipt monitoring. For details of reserve messages, see the following reference. Page 268 List of reserved transactions and format Page 270 System Error (S9Fx)
Reception Notification Trigger
Control Register
Select this checkbox when message reception is reported to the programmable controller CPU. A trigger notification is sent to the programmable controller CPU during receipt.
Configure the relay to be the reception notification trigger.
Trigger Keep Time Auto Reply*1
Fill this field when "None" was selected for "Handshake specification" at the "Transaction information" screen. After the reception notification trigger relay is held for the specified time, control switches OFF automatically.
Select this checkbox to return a response message without waiting for a response from the programmable controller CPU after message receipt. A reception notification handshake is required even for an automatic response.
*1 Displayed only by the "Primary message information" screen.
7 BASIC FUNCTIONS 7.3 Transaction definition
53
Interval unit and configuration range
The following table shows the configurable range of each interval unit.
Interval unit
msec sec min hour
millisecond Second Minute Time
Setting range Fixed Value
1000 to 86400000 1 to 86400 1 to 1440 1 to 24
Registers Used
1000 to 65535 1 to 65535 1 to 1440 1 to 24
Precautions
T9 timer monitor setting of message information
When an error has occurred due to T9 timer monitoring, a T9 timer timeout notification is sent using the trigger relay from the SECS/GEM communication software. For details on SECS error notifications, see the following reference. Page 90 SECS Error Notification Setting When it is necessary to notify the host of a T9 timer occurrence by S9F13, a new transaction must be defined by the user. For details on S9F13, see the following reference. Page 270 System Error (S9Fx) A primary receipt message is necessary for T9 monitoring. Always configure the reception notification trigger for this primary receipt message.
When the reception notification trigger is on
The following events occur.
Item
S9 and F3 occurrence S9 and F5 occurrence
Abort Return
Description
S9 and F3 occur when there is no other definition configured that has the same stream as the message. S9 and F3 also occur when no reception notification trigger has been configured.
S9 and F5 occur when there is one receipt definition or more with the same stream as the corresponding message, and there is no definition that has the same transaction. S9 and F3 also occur when no reception notification trigger has been configured.
Abort return occurs when there is one reception definition or more that has the same stream and function as the corresponding message. In such a case, an error log indicating that the reception notification trigger was not configured is output to the SECS log for primary messages. While the operation ends normally without issuing any notifications for secondary messages, data is not stored in the register.
54
7 BASIC FUNCTIONS 7.3 Transaction definition
Item Information
Series
MELSEC-Q series MELSEC iQ-R series
Edit the item information.
SECS/GEM communication software
Non-GEM version
GEM version
Window
Select an item at the "Scenario Explorer" screen, right-click Shortcut menu [Edit]
GEM advanced version
Displayed items
Item
Name Comment Data Type
Variable Length
Data Counts
7
Description
Configure the item name. Configure the comment. Select the item format code. For more details, see the following reference. Page 57 Data types (item format codes) To specify an item structure under the item, specify "LIST". Select this checkbox to configure the data count to a variable length. For more details, see the following reference. Page 58 Variable Length Configure the number of items of data to be sent/received. When ASCII or JIS-8 is configured for the data type, configure the character count for this item. When DCHAR was configured for the data type, configure the character count in units of two bytes for this item. For details on the number of units of data that can be set, see the following reference. Page 57 Data types (item format codes)
7 BASIC FUNCTIONS 7.3 Transaction definition
55
Item
Description
Control Register
Select when a control register will be used for transmission. · During sending: refers to the control register value, and then sends it as item data. · During receipt, refers to the value of the received item data, and then writes it to the prescribed
control register.
Control Register
Configure the control register.
Data type
Fixed Value*2 Not set*3
The data format can be changed during reception and sending by configuring the "Data type" of the control register. For details of data type conversion, see the following reference. Page 261 Data type conversion By configuring the conversion table settings in advance, you can select processing to convert register values in accordance with item values. For details of conversion tables, see the following reference. Page 124 Conversion Table Setting ALCD/ALID/ALTX/AlarmItem1 to 4 can be configured for "Data type" when "ALARM" has been selected for "Format specification" at the "Transaction information" screen. *1 For details on the alarm function, see the following reference. Page 100 Alarm Definition (non-GEM version)
Select this checkbox to configure the content of sending data to a fixed value, and then configure the value. Up to 30000 alphanumeric characters can be entered for "Fixed Value."
Select this checkbox if the list quantity is determined by the item data structure. In case of a variable, register the list quantity to the control register.
Select List
Select this checkbox to configure as the parent list of the select list function. This item can be configured when "LIST" is selected for "Data Type", and the "Variable Length" checkbox has been selected. In the items defined, only items specified by the programmable controller CPU can be sent. In case of reception, items can be saved to the specified register by specifying the key items.
Select Register
Configure the Select register of the Select list function. · During sending From the programmable controller CPU, configure to 1 to enable and 0 to disable. When a relay device was specified, configure the relay to ON to enable this item and to OFF to disable this item. · During reception From the SECS/GEM communication software, configure to 1 if the received data is valid or 0 if it is invalid in comparison with the Select Key Item. When a relay device was specified, configure the relay to ON or OFF when the reception data is valid or invalid.
Select Key Item
Select this checkbox to configure this item as the key item of the select list function of the reception message.
Repeat Define List
Select this checkbox to configure as the parent list of the Repeat Define List function. The setting can be simplified in case of a configuration that repeats the same elements.
Repeat Item Number
Configure the maximum element quantity of the Repeat Define List function.
Register offset value
Configure the offset of the register No. of the Repeat Define List function.
*1 Supported by the non-GEM version only. *2 Displayed when an option other than "LIST" has been selected for "Data Type". *3 Displayed when "LIST" has been selected for "Data Type".
56
7 BASIC FUNCTIONS 7.3 Transaction definition
Precautions
· When the "Select Key Item" checkbox was selected, configure so that the value configured for "Fixed Value" does not overlap with other key items.
· In the case of two or more data sets, the continuous range of the data quantity amount from the specified control register is subject. Make sure not to overlap with any control register specified in other item information.
· When sending an ASCII character string, the specified control register is referenced from the start address. If there is a NULL character midway, a character string from the start point to the NULL character is sent. If the character string is shorter than the specified number of characters to be sent, a NULL character or a space character is inserted into the string depending on the type of terminator defined in the option settings.
· When an ASCII character string was received, the character string is registered to the control register, and then finally a NULL character is registered. The following section shows when the data quantity setting is even or odd.
String [ABCDEF] When (data quantity is 6 (even)) has been received (Control register is configured at D1000)
BA DC FE
4241 4241 4241 0000 D1000 D1001 D1002 D1003
NULL
String [ABCDE] When (data quantity is 5 (odd)) has been received (Control register is configured at D1000)
BA DC
E
4241 4241 4241 NULL D1000 D1001 D1002
Data types (item format codes)
Item
Description
Number of units of available data
7
MELSEC-Q series
MELSEC iQ-R series
LIST BIN
Non-GEM version
List (length of elements) Binary
No need to specify*2 0 to 1024
GEM version, GEM advanced version
No need to specify*2
0 to 32000
Non-GEM version (Ver.1.28E or later)*1
No need to specify*2
0 to 262144
GEM version, GEM advanced version
No need to specify*2
0 to 1024
BOOL ASCII JIS8 DCHAR I1
Truth value ASCII JIS8 ASCII 1-byte integer (signed)
0 to 1024 0 to 1024 0 to 1024 0 to 1024 0 to 1024
0 to 32000 0 to 32000 0 to 16000 0 to 16000 0 to 32000
0 to 262144 0 to 262144 0 to 262144 0 to 131072 0 to 262144
0 to 1024 0 to 1024 0 to 512 0 to 512 0 to 1024
I2
2-byte integer (signed)
0 to 1024
I4
4-byte integer (signed)
0 to 1024
U1
1-byte integer (unsigned) 0 to 1024
U2
2-byte integer (unsigned) 0 to 1024
U4
4-byte integer (unsigned) 0 to 1024
0 to 16000 0 to 8000 0 to 32000 0 to 16000 0 to 8000
0 to 131072 0 to 65536 0 to 262144 0 to 131072 0 to 65536
0 to 512 0 to 256 0 to 1024 0 to 512 0 to 256
F4
4-byte floating-point
0 to 1024
number
F8
8-byte floating-point
0 to 1024
number
0 to 8000 0 to 4000
0 to 65536 0 to 32768
0 to 256 0 to 128
*1 When using Ver.1.27D or earlier, the number of units of available data is the same as that of non-GEM version of MELSEC-Q series. *2 When "LIST" is selected for "Data Type," the number of units of data is automatically determined based on the setting of the element in
the list. For more details, see the following reference. Page 58 Variable Length
7 BASIC FUNCTIONS 7.3 Transaction definition
57
Variable Length
The following shows the details on the variable length setting for each selected data type.
"LIST" is selected
The following table shows the operations when "LIST" is selected for "Data Type" and the checkbox of "Variable Length" is
selected:
Message type
Sending message
Reception message
Operation
Refers to the control register, and then determines the list quantity. Example: When the list structure was defined by 10 items by the message definition, and the value of the register referenced for the list quantity is "6" during sending, data of 6 items is sent.
Registers the quantity of the received item data to the control register. Example: When the list structure was defined by 10 items by the message definition, and data of 7 items was received during reception, "7" is registered to the control register.
An item other than "LIST" is selected
When an item other than "LIST"*1 is selected for "Data Type" and the checkbox of "Variable Length" is selected, two methods are available to specify the number of units of data: compatibility mode and extended mode.
*1 Excluding ASCII and JIS8.
Specify the number of units of data in the extended mode when sending items with 65535 or more units of data. The compatibility mode and extended mode are automatically switched according to the number of units of data in a received item at the time of receiving. The following table shows the methods for specifying the number of units of data in the compatibility mode and extended mode.
Item
Number of words in the start area of a control register
Contents stored in the start area of a control register
Compatibility mode
1 word
Number of units of data to send and receive (1 word)
Number of units of data when sending an item*2
0 to 65534 (0x0000 to 0xFFFE)
Number of units of data when receiving an item*2 0 to 65534 (0x0000 to 0xFFFE)
Extended mode
3 words
Identifier (65535 (0xFFFF)) (1 word) Number of units of data to send and receive (2 words) 0 to 262144 (0x00000000 to 0x00040000) 65535 to 262144 (0x0000FFFF to 0x00040000)
*2 The upper limit of the number of units of data that can be sent and received differs depending on the data type. For more details, see the following reference. Page 57 Data types (item format codes)
Compatibility mode (when the start value of the control register is 0 to 65534)
Ex. Data type: U2 (2-byte integer (unsigned)) Control register: D0 Value of D0: 3 (0x0003) Data to send and receive: 0x0123, 0x4567, 0x89AB (3 words)
D0
0x0003
(1)
D1
0x0123
D2
0x4567
(2)
D3
0x89AB
... ...
(1) Number of units of data to send and receive (2) Data to send and receive
58
7 BASIC FUNCTIONS 7.3 Transaction definition
Extended mode (when the start value of the control register is 65535)
Ex. Data type: U2 (2-byte integer (unsigned)) Control register: D0 Value of D0: 65535 (0xFFFF) Data to send and receive: 0x0123, 0x4567, 0x89AB, ...0x89AB (131072 words)
D0
0xFFFF
(1)
D1
0x0000
(2)
D2
0x0002
D3
0x0123
D4
0x4567
D5
0x89AB
(3)
... ...
D131074
0x89AB
(1) Identifier (2) Number of units of data to send and receive (3) Data to send and receive
Special data type conversion
7
When the data type is configured to "ASCII" in the sending message setting, [DATE-A], [DATE-Q], [TIME16], [TIME14],
[TIME12], and/or conversion table (when defined) options will be available.
The [DATE-A] and [DATE-Q] are used when the item data is ASCII time data.
For reception data, ASCII time data is converted to numerical time data and registered to a specified register. For sending
data, the register is referenced, and then the data is converted to ASCII time data and sent.
For details of data type conversion, see the following reference.
Page 261 Data type conversion
[TIME16], [TIME14], and [TIME12] are used to configure and send the calendar data held by the SECS/GEM communication
software pre-installed model module to the item data.
· [TIME16]: 16-byte format (YYYYMMDDhhmmsscc)
· [TIME14]: 14-byte format (YYYYMMDDhhmmss)
· [TIME12]: 12-byte format (YYMMDDhhmmss)
If conversion of these data types was specified by the reception frame, the time of the SECS/GEM communication software
pre-installed model module is overwritten. It is not registered to a register.
7 BASIC FUNCTIONS 7.3 Transaction definition
59
Message structure of the SECS/GEM communication software pre-installed model module
Calculate the byte length of the actual item data, and then configure the maximum length of the message using up to 5 MB as reference. When the MELSEC iQ-R series SECS/GEM communication software pre-installed model module is used, the maximum item count of one message is 3000.
Item
Description
Transmission buffer Log Output
Messages of up to 5 MB can be transmitted. The transmission buffer may be exceeded depending on the communication status.
Messages of up to 5 MB can be logged. However, this is exceeded during logging of another message, and only the header is logged.
If too much data is transmitted, the SECS/GEM communication software operates in the following manner.
Operation
Description
Many transactions that have large messages have been defined
An excessive message was sent A primary message that became an excessive message was received
A secondary message that became an excessive message was received
The CIM control READY relay does not switch ON. (The SECS/GEM communication software does not start)
Sending fails.
An abort message is returned, and there is no writing to the prescribed register. (S9F11)
Abort reception is reported, and there is no writing to the prescribed register.
60
7 BASIC FUNCTIONS 7.3 Transaction definition
7.4 Communication Setting
Configure the communication method.
SECS communication configuration
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Configure the SECS communication method, various timer times, and other parameters.
Window
[Setting][Communication Setting]
GEM advanced version
7
7 BASIC FUNCTIONS 7.4 Communication Setting
61
Displayed items
Item
Port Type
Description
Select the communication method used for SECS communication (SECS1*1/HSMS).
Device ID SECS-
Serial port Master/Slave
Configure the device ID of the SECS/GEM communication software. Select the COM port number used for SECS communication (COM1 only). Select the master or slave of serial communication.
Baud Rate Number of Retries Serial setting Data Length
Parity Stop Bit
Select the communication speed of the RS-232C port. Select the number of retries when data sending fails. Select the length of one data item. Select the parity check method. Select the stop bit.
Timer setting
Flow Control T1 T2 T3 T4
Select the handshake method. Select the timeout time between reception characters. Select the protocol timeout time. Select the response timeout time. Select the inter-block timeout time.
HSMS
Connection mode (Passive/ Active)
IP address (Local)
IP Address (Remote)
Select an HSMS connection method from Passive (wait to receive a connection procedure) or Active (initiate a connection procedure with the destination).
Configure the IP address of the SECS/GEM communication software used for HSMS communication.
Configure the IP address of the connection destination used for HSMS communication.
IP Port (Local) IP Port (Remote)
Configure the port number of the SECS/GEM communication software used for HSMS communication. Configure the port number of the connection destination used for HSMS communication.
Timer setting
Link Test Timer T3 T5
Configure the fixed interval at which the destination link test is performed. Select the response timeout time. Select the connection separation timeout time.
T6
Select the control transaction timeout time.
T7
Select the Not Selected timeout time.
T8
Select the timeout time between network characters.
*1 Can be selected for only the MELSEC-Q series SECS/GEM communication software pre-installed model module.
Precautions
· If it is necessary to send a multi-block permission frame to the host when sending multiple blocks with SECS- communication, define the transaction separately, and then carry out sending processing.
· The "T5" setting of HSMS communication is synchronized with the Reconnection delay after Line Disconnection setting of the [Control 1] tab of the Option settings.
62
7 BASIC FUNCTIONS 7.4 Communication Setting
Communication Setting by PLC
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Change the communication setting by the value acquired from the register. You can configure the parameters of the communication method selected by "Port type" of the "Communication settings" screen.
Window
[Setting][Communication Setting by PLC]
7
Displayed items
Item
Communication Setting by PLC Device ID
Setting Request Trig SECS-
HSMS
Description
Select this checkbox to change communication settings from a ladder program.
Configure the reference-destination register of the device ID value to be changed. The Device ID parameter is necessary for both SECS- and HSMS.
Configure the trigger relay to apply setting information.
Configure the reference-destination register of the parameter value. For the value to be stored to the register, see the following reference. Page 64 SECS-I configuration
Configure the reference-destination register of the parameter value. For the value to be stored to the register, see the following reference. Page 64 HSMS settings
Operating procedure 1. Start the SECS/GEM communication software.
During start-up, the current setting values of the SECS/GEM communication software are applied to the register.
2. The register value is changed, and the setting trigger is configured to ON.
The setting value of the SECS/GEM communication software is changed by the register value, and the setting trigger is configured to OFF by the SECS/GEM communication software. When an invalid value has been configured to the register, the register value returns to the value before the change.
3. Reset the programmable controller CPU.
7 BASIC FUNCTIONS 7.4 Communication Setting
63
Precautions
Configure the register settings by programmable controller CPU management or the I/O Assignment section.
SECS-I configuration
The following section shows the SECS- parameter values stored to registers.
Item
Device ID
Setting Request Trig
SECS-
Serial port
Master/Slave
Communication speed [bps]
Number of Retries Serial setting Data Length
Parity
Stop Bit Flow Control
Timer setting T1 T2 T3 T4
Setting value
0 to 32767
Trigger relay to apply setting information.
"1" only.
· 0: Master · 1: Slave
9600, 14400, 19200, 38400, 57600, and 115200 only (Only 2 consecutive registers are used.)
0 to 31
· 7: B7 · 8: B8
· 0: PN · 1: P0 · 2: PE
· 1: S1 · 2: S2
· 0: NON · 1: XON · 2: RTS
100 to 10000 (increments of 100)
200 to 25000 (increments of 200)
1 to 120 (increments of 1)
1 to 120 (increments of 1)
HSMS settings
The following section shows the HSMS parameter values stored to registers.
Item
Setting value
Device ID
Setting Request Trig
HSMS
Connection mode
IP address (Local)
IP Address (Remote)
IP Port (Local) IP Port (Remote) Timer setting Link Test Timer
T3 T5 T6 T7 T8
0 to 32767 Trigger relay to apply setting information. · 0: Active · 1: Passive (0 to 255) (Four consecutive registers are used.) (0 to 255) (Four consecutive registers are used.) 1 to 65535 1 to 65535 1 to 65535 1 to 120 (increments of 1) 1 to 240 (increments of 1) 1 to 240 (increments of 1) 1 to 240 (increments of 1) 1 to 120 (increments of 1)
64
7 BASIC FUNCTIONS 7.4 Communication Setting
7.5 Device Assignment
Configure the range of each device type used by the SECS/GEM communication software. There are 2 types of device assignment: shared memory and I/O assignment.
Precautions
The device assignment settings differ with the shared memory settings for the programmable controller CPU and SECS/GEM communication software pre-installed model module.
Shared Memory Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
When the refresh area in the multi-CPU settings of the programmable controller CPU and MELSEC-Q series SECS/GEM communication software pre-installed model module is used by the SECS/GEM communication software, configure the refresh area as shared memory.
Window
7
[Setting][Device Assign Setting]
Displayed items
Item
Counts(CPU) Shared Memory
CPU No. Self Unit
Device Memory Start
Device Start Counts(Words)
Description
Select the number of programmable controller CPUs. Select the number of a CPU. Select this checkbox to allocate for the MELSEC-Q series SECS/GEM communication software preinstalled model module. Select a device. Configure the start of a memory number in the programmable controller CPU or MELSEC-Q series SECS/GEM communication software pre-installed model module. Configure the start of device numbers. Configure the number of devices to be used in units of words.
7 BASIC FUNCTIONS 7.5 Device Assignment
65
Ex. For a 2 device configuration of the programmable controller CPU and MELSEC-Q series SECS/GEM communication software pre-installed model module, configure M device to 256 points and D device to 1024 points, respectively.
Using Shared Memory
The following section shows the advisability of using the shared memory by the type of transmission message.
Refresh range
Within programmable controller CPU
Within C Controller module
Device configuration example
M0 to M255
D0 to D1023 M256 to M511
D1024 to D2047
Transmission message
Availabil ity
Sending
Receiving
Sending Receiving Sending
Receiving
Sending Receiving
Programmable controller CPU turns trigger ON · SECS/GEM communication software detects trigger by automatic refresh · SECS/GEM communication software directly turns trigger device OFF to
establish trigger handshake
Available
SECS/GEM communication software directly turns trigger device ON · Programmable controller CPU detects trigger and turns device OFF. · SECS/GEM communication software detects trigger by automatic refresh
to establish trigger handshake
Available
Programmable controller CPU writes data to register
Available
SECS/GEM communication software directly controls device and writes data to register *1
Available
Programmable controller CPU turns trigger ON · This action will not rewrite the refresh area of the C Controller module, so
the shared memory is not available. Suitable for assignment of CA status notification setting.
Not available
SECS/GEM communication software directly turns trigger device ON · Programmable controller CPU detects trigger and turns device OFF. · This action will not rewrite the refresh area of the C Controller module, so
the shared memory is not available.
Not available
Writing data to the register by the programmable controller CPU will not rewrite the refresh area of the C Controller module, so the shared memory is not available.
Not available
SECS/GEM communication software writes data to refresh area
· Programmable controller CPU can refer to the refresh area as a device.*1,*2
Available
*1 Higher speed performance can be obtained if items contained in the received message are written in the refresh area. *2 If a device in which received data is stored is not updated when a reception notification trigger is detected, use a device in the I/O
assignment area for which the cache settings are configured instead of the refresh area.
When it is not possible to secure a region for transmission messages by shared memory
Configure and use devices of the programmable controller CPU by I/O assignment. In the region of I/O assignment, the SECS/GEM communication software controls devices directly. Configure the cache settings to ensure performance. For details on cache settings, see the following reference. Page 50 Cache settings
66
7 BASIC FUNCTIONS 7.5 Device Assignment
I/O assignment
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The I/O assignment needs to be configured for the SECS/GEM communication software to use the devices of the programmable controller CPU, SECS/GEM communication software pre-installed model module, or I/O module.
Window
[Setting][Device Assign Setting]
MELSEC-Q series
MELSEC iQ-R series
7
Displayed items
Item
Channel*1 Network number*1 STA#*1
CPU number *2 Device
Description
Select "Q-bus". Do not enter data. Configure the CPU number. Use the device function of the Setting/Monitoring Tools for the C Controller module to configure the station number to "255" (own station) to access the station device ("M" or "D"). Configure the CPU number of the control CPU. Select a device.
Device Start Counts(Words)
Configure the start of device numbers.
Configure the number of devices to be used in units of words. · When a MELSEC-Q series SECS/GEM communication software pre-installed model module will be used, and relay
devices only are configured by I/O assignment for relay devices (M, B, X, and Y), a maximum of 4096 points (256 words) can be used in total. · When a MELSEC iQ-R series SECS/GEM communication software pre-installed model module will be used, and relay devices only are configured by I/O assignment for relay devices (M, B, X, and Y), a maximum of 3584 points (224 words) can be used in total. · For each I/O assignment record other than a relay device, the maximum number of points for relay devices is decreased by 256 points (16 words). · Relay devices are recommended to be set in units of 256 points (16 words). The maximum number of points for relay devices is decreased for the points less than 256.
*1 Displayed for only the MELSEC-Q series SECS/GEM communication software pre-installed model module. *2 Displayed for only the MELSEC iQ-R series SECS/GEM communication software pre-installed model module.
7 BASIC FUNCTIONS 7.5 Device Assignment
67
Available device ranges
The following table shows the device ranges to set for the I/O assignment.
Module
MELSEC iQ-R series SECS/GEM communication software pre-installed model module
MELSEC-Q series SECS/GEM communication software pre-installed model module
SECS/GEM communication software
Non-GEM version*1
GEM version GEM advanced version Non-GEM version GEM version GEM advanced version
Device range
M, B, X, Y: 0 to 32767 D, W, R, ZR: 0 to 2147483647 M, D, B, X, Y, W, R: 0 to 32767 ZR: 0 to 65535
M, D, B, X, Y, W, R: 0 to 32767 ZR: 0 to 2147483647
*1 When using Ver.1.27D or earlier, the following devices can be used: M, D, B, X, Y, W, R: 0 to 32767 ZR: 0 to 65535
Precautions
In the region of I/O assignment, the SECS/GEM communication software controls devices directly. Configure the cache settings to ensure performance. For details on cache settings, see the following reference. Page 50 Cache settings
68
7 BASIC FUNCTIONS 7.5 Device Assignment
7.6 Option Setting
Configure the advanced operations of the SECS/GEM communication software.
Control 1
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][Control 1] tab
MELSEC-Q series
GEM advanced version
7
MELSEC iQ-R series
7 BASIC FUNCTIONS 7.6 Option Setting
69
Displayed items
Item
PLC Response Monitoring Timer
Secondary Monitoring Timer
Reconnection Delay After Line Disconnection Maximum Number Of Retries After Line Disconnection Transaction Response Monitoring Timer*1
ASCII Character Terminator
Number of Multi-Transaction Queues For PLC Transaction Number of Transaction Queues For PLC Transaction Number of Multi-Transaction Queues For PLC Receiving Switch Into Offline Status Upon Disconnection*2
Description
Configure the monitoring time from when the SECS/GEM communication software turns ON the programmable controller CPU reception notification relay to when the programmable controller CPU turns the relay OFF to confirm the handshake. If the relay is ON after the specified time passes, the SECS/GEM communication software turns the relay OFF. For the operation of the PLC Response Monitoring Timer, see the following reference. Page 72 PLC Response Monitoring Timer and Secondary Monitoring Timer
Configure the monitoring time from when a primary message is received, and the SECS/GEM communication software turns ON the reception notification trigger relay to when the programmable controller CPU turns the secondary message sending request trigger relay ON. If the secondary message sending request trigger relay was not switched ON after the specified time has past, the programmable controller CPU is notified if there are queued received messages. The setting must be larger than the PLC Response Monitoring Timer. For the operation of the Secondary Monitoring Timer, see the following reference. Page 72 PLC Response Monitoring Timer and Secondary Monitoring Timer
Configure the delay time until a reconnection is attempted when a disconnection was detected. Reconnection Delay After Line Disconnection is synchronized with the T5 timer setting.
Configure the number of reconnection attempts when a disconnection was detected. Setting the maximum number of retries to "" (infinity) results in an infinite number of retries.
Configure the time from when a transaction is executed to when the next transaction is executed in the course of a scenario that sequentially executes a series of transactions. For details of scenario settings, see the following reference. Page 97 Scenario definition
When the ASCII data type is selected for SECS sending data, and the actual number of characters is fewer than the predetermined number, specify the space filling method (NULL character or space character). When the sending data is configured as a fixed value, a number of characters that is fewer than the number of SECS data sets is still valid. Sending string data is referenced from the start control register. If there is a NULL character midway, a character string from the start point to the NULL character is sent.
For operation and configuration of the number of multi-transaction queues, see the following reference. Page 73 Configuration of number of multi-transaction queues
Select this checkbox to switch the system into offline status upon detection of line disconnection. After the status has switched to offline, the SECS/GEM communication software turns OFF the online status of CA status notification. When this checkbox is cleared, the online status continues even after detection of line disconnection.
70
7 BASIC FUNCTIONS 7.6 Option Setting
Item
Description
Use S1F13 For The
Communication
Establishment Sequence
Select this checkbox to consider a communication request transaction (S1F13/14) as the necessary condition for establishing communication between the equipment and host. The following operations are performed depending on the checkbox state. · Selected: When the communication request transaction (S1F13/14) is executed, communication is
established, and the communication established relay turns ON. Any other transactions are discarded before communication is established. · Cleared: The communication request transaction (S1F13/14) is considered as a normal transaction. For an HSMS connection, communication is established when the state is HSMS Selected, and the communication established relay turns ON. For an SECS- connection, communication is established when the SECS/GEM communication software opens the port immediately after start-up. For details on the Communication established relay, see the following reference. Page 82 CA Status
Set communication as
disconnected by a T3 timeout *3
When a T3 timeout has occurred after a primary message was sent from the SECS/GEM communication software, this is treated as a sending failure, and a communication-disconnected state results. Select this checkbox to turn OFF the Communication established relay. If this checkbox is not selected, the Communication established state is maintained even after a T3 timeout. For details on the Communication established relay, see the following reference. Page 82 CA Status
Set communication as When an abort message is received from the host after a message subject to spooling was sent from
disconnected by receipt the SECS/GEM communication software, this is treated as a sending failure, and a communication-
of an abort of message subject to spooling*3
disconnected state results. Select this checkbox to turn OFF the Communication established relay. Furthermore, if the Communication established relay turns OFF, spooling occurs simultaneously.
If this checkbox is cleared, communication remains established, and spooling is not performed even
when an abort message is received from the host.
For details on the Communication established relay, see the following reference.
Page 82 CA Status
7
Automatically Transmit S1F13 Upon Line Reconnection*4
Select this checkbox to cause the SECS/GEM communication software to automatically send S1F13 when the communication line is reconnected after disconnecting.
When this checkbox is cleared, automatic sending is not performed, so the programmable controller
CPU needs to request sending.
Send An Abort Message Before Transmitting S9Fx Send Complete Waiting Timer*5
When a primary message, such as an undefined device ID message, is received from the host, the SECS/GEM communication software automatically sends an S9 related error message. Select this checkbox to interrupt the transaction associated with the received primary message and send an abort message (SnF0: "n" indicates the S code of the reception message). For content of S9 errors, see the following reference. Page 270 System Error (S9Fx)
Configure the time to monitor from when the SECS/GEM communication software starts the sending process for a message until the completion of sending. If the transmission is not completed within the configured timer value (default: 20 seconds), "DM sending failure" is output to the SECS log. In such a case, configure a large Send Complete Waiting Timer value.
*1 Can be configured for only the MELSEC-Q series SECS/GEM communication software pre-installed model module. *2 If the "Control State Model" checkbox has been selected under GEM Performance Definition Setting in the GEM version or GEM
advanced version, operation is based on the control state model regardless of this setting. *3 Can be configured only by a non-GEM version. *4 If the "Communication State Model" checkbox has been selected under GEM Performance Definition Setting in the GEM version or
GEM advanced version, this setting is always enabled, regardless of the status of the checkbox. *5 Can be configured for only a GEM version and GEM advanced version.
Precautions
· Before configuring the number of transaction cues, check the advisability and quantity of interleaving (simultaneous processing of multiple transactions) in the specifications of the host.
· When S1F13 is used in the communication establishment sequence, a communication established state cannot occur until a communication establishment request transaction (S1F13/14) is established. Therefore, the S1F13/14 transaction must be defined.
· When [Communication state model] is enabled in GEM performance definition / basic requirements of GEM, a GEM version of the SECS/GEM communication software operates as though the checkbox was selected, regardless of the "Use S1F13 For The Communication Establishment Sequence" setting.
· An abort message is not returned if the primary message to be received has no return request (W-bit), even if "Send An Abort Message Before Transmitting S9Fx" is set. Note that S9F9 (transaction timeout) is a timeout for sending messages and is not covered by this setting.
7 BASIC FUNCTIONS 7.6 Option Setting
71
PLC Response Monitoring Timer and Secondary Monitoring Timer
Handshake for each transaction
The PLC Response Monitoring Timer monitors the time from "(2) Reception notification trigger relay ON" to "(6) Sending request detection". The Secondary Monitoring Timer is not used for a handshake for each transaction.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
(3) Receive notification detection
(4) Reception processing
(5) Transmission request relay off
(2) Receive notification relay on
(1) Primary message
(6) Transmission request detection
(7) Secondary message
Handshake for each message
The PLC Response Monitoring Timer monitors the time from "(2) Reception notification trigger relay ON" to "(4) Reception notification trigger relay OFF". Furthermore, the Secondary Monitoring Timer monitors the time from "(2) Reception notification trigger relay ON" to "(6) Sending request trigger relay ON".
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
(3) Receive notification detection
(4) Receive notification relay off
(5) Reception processing
(6) Transmission request relay on
(2) Receive notification relay on
(1) Primary message
(7) Transmission request detection
(8) Transmission request relay off
(9) Secondary message
72
7 BASIC FUNCTIONS 7.6 Option Setting
Configuration of number of multi-transaction queues
For multi-transactions, the next primary message is issued without waiting for the arrival of the prescribed secondary message. (In the case of single transactions, the next transaction is never issued until a secondary message is sent for a primary message. ) If interleaving (simultaneous processing of multiple transactions) is required, the number of multi-transaction queues should be configured to two or more according to the communication specifications. The following table shows the objectives and operations of each multi-transaction queue.
Item
Objective
Operation
Number of Multi-Transaction Queues For PLC Transaction
Number of Transaction Queues For PLC Transaction
Number of Multi-Transaction Queues For PLC Receiving
Configure the number of primary messages that can be sent simultaneously.
Configure the number of queued messages that can be retained simultaneously.
Configure the number of received messages that can be retained simultaneously.
Messages are queued in the sending transaction queue when the queue is full.
Any subsequent messages are discarded when the queue is full. (Sending failure)
Any subsequent messages are aborted when the queue is full.
Operation when the "Number of Multi-Transaction Queues For PLC Transaction" has been configured multiple times
Messages of the number specified by "Number of Multi-Transaction Queues For PLC Transaction" are sent simultaneously.
When the Number of Multi-Transaction Queues For PLC Transaction becomes full, messages that arrive later are
accumulated (interleaved) in the Number of Transaction Queues For PLC Transaction.
Programmable controller CPU
Device
SECS/GEM communication
Host
7
software
Transmission request relay A on
Transmission request relay B on
Transmission request relay C on
The transmission messages, A, B, and C, are acquired.
Transmission request A, B, and C
detection
Primary A
Primary B
Primary C
Precautions
If the Number of Transaction Queues For PLC Transaction becomes full, sending fails and later messages are discarded. When "Number of Multi-Transaction Queues For PLC Transaction" has been configured multiple times, configure "Number of Transaction Queues For PLC Transaction" multiple times as well.
7 BASIC FUNCTIONS 7.6 Option Setting
73
Operation when the "Number of Multi-Transaction Queues For PLC Receiving" has been configured multiple times
Messages of the number of specified by "Number of Multi-Transaction Queues For PLC Receiving" are interleaved
(accumulated). Interleaved messages are processed after transactions being processed are completed.
Programmable controller CPU
Device
SECS/GEM communication software
Host
Receive notification A
detection
Transmission request relay A on
Receive notification A
Queuing (accumulation)
Primary A Primary B Primary C
Transmission request A detection
Secondary A
Receive notification B
detection
Receive notification B
Implementation of processing of queued (accumulated) content
Thereafter, the same processing in proportion to queued (accumulated) content continues
Precautions
When the Number of Multi-Transaction Queues For PLC Receiving becomes full, messages that come later are aborted.
74
7 BASIC FUNCTIONS 7.6 Option Setting
Operation during sending when multiple items are set for "Number Of Transaction Queues For PLC Transmission"
Messages of the number of specified by "Number of Transaction Queues For PLC Transaction" are interleaved (accumulated). In the case of interleaved messages, the number configured by "Number of Multi-Transaction Queues For PLC Transaction" for each transaction is sent. Messages are sent one by one when "Number of Multi-Transaction Queues For PLC Transaction" has been configured to "1". )
Programmable controller CPU
Device
SECS/GEM communication software
Host
Transmission request relay A on
Transmission request relay B on
Transmission request relay C on
Receive notification A
detection
Transmission requests
A, B, and C detection
The transmission messages, A, B, and C, are acquired and put on the queue.
Primary A
7
Receive notification A
Secondary A
Primary B
Thereafter the sequence will be repeated.
Secondary B
Precautions
If the Number of Transaction Queues For PLC Transaction becomes full, sending fails and later messages are discarded.
7 BASIC FUNCTIONS 7.6 Option Setting
75
Operation during reception when multiple items are set for "Number Of Transaction Queues For PLC Transmission"
Programmable controller CPU
Device
SECS/GEM communication software
Host
Receive notification A
detection Transmission request relay A on
Receive notification C
detection Transmission request relay C on
Receive notification A
Primary A Primary B
Abort notification B
Transmission request A detection
The transaction will be aborted until the transaction A is completed.
Secondary A
Receive notification C
Primary C
The transaction will be processed normally after the transaction A is completed.
Transmission request C detection
Secondary C
76
7 BASIC FUNCTIONS 7.6 Option Setting
Control 2
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][Control 2] tab
MELSEC-Q series
GEM advanced version
7
MELSEC iQ-R series
7 BASIC FUNCTIONS 7.6 Option Setting
77
Displayed items
Item
Shared Memory Synch. Waiting Timer*1
Change the C Controller module time by S2F31/ S2F18 reception
Change the C intelligent function module time by S2F31/S2F18 reception
Description
Configure the shared memory synchronization adjustment timer. Sometimes adjustments are required when shared memory is assigned to a trigger relay. When shared memory is assigned, the SECS/GEM communication software controls the relay by handshaking and then verifies that the prescribed relay status has been updated by a refresh of the multiple CPUs in accordance with the value of this simultaneous adjustment timer. When ladder program processing requires time, a change in the relay status is not detected even if the SECS/GEM communication software is delayed by the configured time, resulting in status inconsistency. At this time, adjust the timer value, taking into consideration ladder program scan processing.
Select this checkbox to configure the time of the MELSEC-Q series SECS/GEM communication software pre-installed model module when an S2F31 or S2F18 was received. The SECS/GEM communication software uses an S2F18 or S2F31 for reserved transactions and, upon receipt of time data from the host, replaces the time of the MELSEC-Q series SECS/GEM communication software pre-installed model module. However, it synchronizes with the time of CPU No. 1 automatically when Multiple CPU Setting has been configured. For details on S2F18 and S2F31 transactions, see the following reference. Page 268 List of reserved transactions and format The SECS/GEM communication software uses the SECS/GEM communication software pre-installed model module time in log data. As a result, when the logs are viewed, the order of the data may appear different from actual data transmission and reception, in accordance with the time changes.
The MELSEC iQ-R series SECS/GEM communication software pre-installed model module does not have a function to replace the time of the module. The SECS/GEM communication software treats S2F18 and S2F31 as reserve transactions. For details on S2F18 and S2F31 transactions, see the following reference. Page 268 List of reserved transactions and format
Queue Clear Settings
HOST/GATEWAY mode settings*2
Number of Transaction Queues for PLC Transmission
T3 timeout
Select this checkbox to clear the messages accumulated in the SECS/GEM communication software sending queue when a T3 timeout has occurred.
T9 timeout
Select this checkbox to clear the messages accumulated in the SECS/GEM communication software sending queue when a T9 timeout has occurred.
Dialog Violation
Select this checkbox to clear the messages accumulated in the SECS/GEM communication software sending queue when a dialog violation has occurred.
HOST mode
Select this checkbox to use the SECS/GEM communication software as a host to communicate with the equipment. When the SECS/GEM communication software will be installed on the equipment, clear the checkboxes of HOST mode and GATEWAY mode.
GATEWAY mode
Select this checkbox to use the SECS/GEM communication software as a gateway to intermediate messages. When the SECS/GEM communication software will be installed on the equipment, clear the checkboxes of HOST mode and GATEWAY mode.
Queue Counts
If a register is assigned in this setting, the number of messages currently in queue is output to the specified register.
Maximum Queue Counts When the checkbox of "Maximum Queue Counts" is selected, a value set for "Number Of Transaction Queues For PLC Transmission" is stored in the configured register No. + 1 word.
Communication Interruption Time*2
Communication disconnection time storage format
Configure the data type when storing the Communication disconnection occurrence time. If "DATE-Q" or "DATE-A" is selected for the storage format, the time is stored in binary. For an example of a value stored to a register, see the following reference. Page 79 Register storage formats
Communication disconnection occurrence time
File Output Stop setting File Output Stop
Configure the register to store the time when the communication state changed from "COMMUNICATING" to "NOT COMMUNICATING". The updating of this register is synchronized with the switching of the CA state notification relay and Communication established relay from ON to OFF. This is normally when a line disconnection detection and Communication failure (sending error) occur, but "T3 timeout" and "Set communication as disconnected by receipt of an abort of message subject to spooling" may also be included in the conditions depending on the settings of the [Control 1] tab.
File output can be stopped to prevent file corruption before a reset of a SECS/GEM communication software pre-installed model module. When the file output stop relay is ON, it operates as though the Mode switch of the SECS/GEM communication software pre-installed model module is OFF.
*1 Can be configured for only the MELSEC-Q series SECS/GEM communication software pre-installed model module. *2 Can be configured only by a non-GEM version.
78
7 BASIC FUNCTIONS 7.6 Option Setting
HOST/GATEWAY mode operations
Name
HOST mode setting
GATEWAY mode setting
Operation
· S9 messages are not sent automatically. However, there is notification when there is a setting of the S9 sending notification relay.
· During S9 message receipt, messages are not discarded. · The spool is normally disabled.
· No restrictions are applied to the transmission of messages, even in the case of communication disconnection or an offline state.
· The spool is normally disabled. · Time is synchronized by sending of S2F31 and S2F18.
Register storage formats
The following table shows examples of the communication disconnection occurrence times stored to registers. · "Communication disconnection occurrence time" is configured to D201 · Communication disconnection occurrence time is "2009/12/15 9:46:15.195"
Register No.
DATE-Q
DATE-A
ASCII 12
ASCII 14
ASCII 16
D201
2009 (Year)
9 (Year)
"09" (Year)
"20" (Year)
"20" (Year)
D202
12 (Month)
12 (Month)
"12" (Month)
"09" (Year)
"09" (Year)
D203
15 (Day)
15 (Day)
"15" (Day)
"12" (Month)
"12" (Month)
D204
9 (Hour)
9 (Hour)
"09" (Hour)
"15" (Day)
"15" (Day)
D205 D206
46 (Minute) 15 (Second)
46 (Minute) 15 (Second)
"46" (Minute) "15" (Second)
"09" (Hour) "46" (Minute)
"09" (Hour) "46" (Minute)
7
D207
2 (Day of week)
2 (Day of week)
00(NULL)
"15" (Second)
"15" (Second)
D208
Not used
Not used
Not used
00(NULL)
"19"(1/100)
D209
Not used
Not used
Not used
Not used
00(NULL)
7 BASIC FUNCTIONS 7.6 Option Setting
79
Retry setting
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][Retry Setting] tab
GEM advanced version
Displayed items
Item
Sending retry function
Retry upper limit
Retry interval Offline transition Number of retries notification Counting method
Count clearing
80
7 BASIC FUNCTIONS 7.6 Option Setting
Description
Select this checkbox to enable the SECS/GEM communication software function to resend automatically when an equipment-issued transaction has failed. A retry occurs when a response timeout (T3 timeout) or sending error of the communication protocol results. A new transaction ID of the retry message is assigned.
Configure the number of retries. When this number of retries is attempted, and the final message results in a response timeout, it is treated as a T3 timeout error, S9 and F9 are sent, and spooling starts. The initial message is not included in the count. For more details, see the following reference. Page 81 Retry operations during T3 timeouts
Configure the retry interval in milliseconds. The default is 5000 ms (5 seconds).
Configure whether to cancel retrying and transfer to an offline state (retry cancel) or transfer to an offline state after retry completion when an "Offline" control request occurred and an offline transition occurred due to a ladder program during message retry.
Configure the register to store the number of retries performed.
Select the counting method for the number of retries. · When "By message" was selected for the counting method, the number of message retries during the
current retry attempt is stored in the number of retries notification. If the transaction was successful while retrying, this is initialized to 0. When the retry limit was reached, it is initialized to 0 when the next message sent successfully. Normally, it is initialized to 0 at the sending of S9 and F9. · When "Accumulate" was selected as the counting method, the number of retries to be added with
each retry occurrence is stored in the number of retries notification. When the value reaches 65535, counting stops.
Configure the trigger to initialize the value of the number of sending retries notification register to "0" at the arbitrary timing of the programmable controller CPU. After initialization is run, this trigger is switched OFF by the SECS/GEM communication software. Use this mainly to clear the accumulated number.
Item
Description
Number of HSMS connection attempts setting
Number of HSMS connection attempts
Counting method
Configure the register to store the number of times Select.req was sent from a line disconnection state.
Select the counting method for the number of HSMS connection attempts. · When "By message" was selected for the counting method, the number of times Select.req was sent
is stored in the HSMS connection attempts notification register. Initialized to 0 by a Selected state transition. · When "Accumulate" was selected for the counting method, the number of times Select.req was sent is stored in the HSMS connection attempts notification register. When the value reaches 65535, counting stops.
Count clearing
Configure the trigger to initialize the value of the number of HSMS connection attempts notification register to "0" at the arbitrary timing of the programmable controller CPU. After initialization is run, this trigger is switched OFF by the SECS/GEM communication software. Use this mainly to clear the accumulated number.
Number of SECS-2 communication establishment attempts notification setting
Number of SECS-2 communication establishment attempts notification
Configure the register to store the number of times S1 and F13 were sent from a communication disconnection state.
Counting method Count clearing
Select the counting method for the number of SECS-2 communication establishment attempts.
· When "By message" was selected for the counting method, the number of times an S1F13 was sent
from a communication suspended state is stored in the SECS-2 communication establishment
attempt notification register. Initialized to 0 by a communication execution state transition.
· When "Accumulate" was selected for the counting method, the number of times an S1F13 was sent
from a communication suspended state is stored in the SECS-2 communication establishment
attempt notification register. When the value reaches 65535, counting stops.
Note that the number of message retries is not included in this count.
Configure the trigger to initialize the value of the number of SECS-2 communication establishment
7
attempts notification register to "0" at the arbitrary timing of the programmable controller CPU.
After initialization is run, this trigger is switched OFF by the SECS/GEM communication software.
Use this mainly to clear the accumulated number.
Retry operations during T3 timeouts
The following diagram is an example of retry operations during T3 timeouts
Ex. When "3" was configured, the 1st normal-send plus 3 retry-sends equals 4 sends.
SECS/GEM communication software
Host
1.Primary message transmission
Return error occurrence
(1) 2.1st Retry message transmission
(2)
(1) 3.2nd Retry message transmission
(2)
(1) 4.3rd Retry message transmission
(2)
(1) 5.S9F9 transmission
(1) T3 Timeout Timer (2) Retry interval
7 BASIC FUNCTIONS 7.6 Option Setting
81
CA Status
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][CA Status] tab
MELSEC-Q series
GEM advanced version
MELSEC iQ-R series
82
7 BASIC FUNCTIONS 7.6 Option Setting
Displayed items
Item
Description
Online
Configure the relay to notify the programmable controller CPU when an online status (S1F1S1F2) was established between the host and equipment. S1F1/F2 is treated as a special transaction.
Disconnected
Configure the relay to notify the programmable controller CPU when the line was disconnected between the host and equipment. The relay is ON immediately after start-up of the SECS/GEM communication software. In the case of HSMS, the relay is turned OFF when TCP/IP connection is completed, and Select.reqSelect.rsp was received. For SECS- communication, the relay remains OFF after the SECS/GEM communication software opens the port immediately after start-up. The relay cannot be turned ON even if the line was disconnected. (A T2 protocol timeout error occurs when sending data.) Do not use the relay as a disconnection detection condition of the Programmable Controller CPU.
Reconnection Retry
Configure the relay to notify the programmable controller CPU during a line reconnection when the line with the host was disconnected. The reconnection retry relay is switched OFF when reconnection was completed or the Maximum Number of Retries after Line Disconnection was exceeded. For configuration of the Maximum Number of Retries after Line Disconnection, see the following reference. Page 69 Control 1 To determine whether communication retries are being performed, see the following reference. Page 84 Reconnection Retrying
CIM Control READY
Configure the relay to notify the programmable controller CPU when the SECS/GEM communication
software starts completely and enters a controllable state. Note that the processing should be programmed so that the programmable controller CPU does not
7
detect errors before the CIM Control READY relay is turned ON.
Communication Established
Configure the relay to notify the programmable controller CPU when communication (S1F13S1F14) was established between the host and equipment. Note that the determination of communication establishment depends on the setting that determines whether S1F13 is used for the communication establishment sequence. S1F13/F14 is treated as a special transaction. For setting content, see the following reference. Page 69 Control 1
Transmission Queue Full
Spooling*1
Spool Outputting*1
Trigger Keep Time *1
Configure the relay to notify the programmable controller CPU when the sending message queue from the SECS/GEM communication software reaches a value set for "Number Of Transaction Queues For PLC Transmission". The SECS/GEM communication software performs sending processing until the sending queue is full. After that, however, even when sending is requested, sending fails, and the subsequent messages are not sent. Perform sending processing after clearing the sending queue full status.
Configure the relay to notify the programmable controller CPU when messages subject to spooling have been spooled. For details on the spooling function, see the following reference. Page 106 Spool Definition Settings
Configure the relay to notify the programmable controller CPU when the SECS/GEM communication software is sending messages subject to spooling automatically. If there is no spool data when an S6F23 was received from the host, this relay is ON only for the time configured by the trigger keep time. For details on the spooling function, see the following reference. Page 106 Spool Definition Settings
CA Error Detection
Configure the relay to verify that the SECS/GEM communication software application is running from the ladder program.
Detection period
CF Error Detection*2 SD Error Detection*3 Battery Error Detection*2
The SECS/GEM communication software follows the configured detection period and turns OFF the CA Error Detection relay.
Configure the relay to notify of any error detection when the SECS/GEM communication software accessed the memory card.
Configure the relay to notify the programmable controller CPU that the built-in battery of the MELSEC-Q series SECS/GEM communication software pre-installed model module has died.
*1 Can be configured only by a non-GEM version. *2 Can be configured for only the MELSEC-Q series SECS/GEM communication software pre-installed model module. *3 Can be configured for only the MELSEC iQ-R series SECS/GEM communication software pre-installed model module.
7 BASIC FUNCTIONS 7.6 Option Setting
83
Reconnection Retrying
Refer to the following table to determine whether a connection retry is being performed by combining the Disconnected relay and Reconnection retrying relay.
Disconnected relay
Connection retry relay
Status
ON
ON
Reconnection Retry
ON
OFF
Connection retry end
The "Online" relay and "Communication established" relay are used to notify the programmable controller CPU that the exchange of some specific transaction was performed. Such transactions are treated as special transactions of the SECS/GEM communication software. For details on special transactions, see the following reference. Page 269 Special Transactions
Precautions
Setting an X device for each relay
It is possible to configure "OWN (host station)" as the CPU number and device to "X" when the MELSEC iQ-R series SECS/ GEM communication software pre-installed model module is being used.
84
7 BASIC FUNCTIONS 7.6 Option Setting
Control Request
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][Control Request] tab
MELSEC-Q series
GEM advanced version
7
MELSEC iQ-R series
7 BASIC FUNCTIONS 7.6 Option Setting
85
Displayed items
Item
Line Connection
Line Disconnection Scenario Interruption *1 Dialog Interruption *2 Offline
Trigger Hold Time Online Start*3
Startup Connection Mode Reconnection Mode
SECS communication is disabled by an offline transition*3 Disconnect Line By Offline Transition*3
Description
Configure the line connection relay. In case of an HSMS connection, the line is connected, and a Select request is sent by the line connection relay trigger. In case of an SECS- connection, the port is opened. The mode can be configured to specify an automatic connection attempt (AUTO) or a connection attempt based on a request from the programmable controller CPU (MANUAL) during startup and upon line disconnection detection. If the startup connection mode and the reconnection mode were configured to "MANUAL", the line connection relay only is the connection method.
Select the mode during start-up. · AUTO After SECS/GEM communication software start-up, TCP/IP and HSMS connections are attempted automatically. · MANUAL After SECS/GEM communication software start-up, TCP/IP and HSMS connections are not attempted until there is a request by the line connection trigger.
Select the mode during disconnection detection. · AUTO When a line disconnection was detected, such as a T6 Timer timeout, TCP/IP and HSMS connections are attempted automatically. If the disconnection was intentionally triggered by the disconnection trigger, TCP/IP and HSMS connections are not attempted until there is a request by the line connection trigger. · MANUAL Even when a line disconnection was detected, TCP/IP and HSMS connections are not attempted until there is a request by the line connection trigger.
Configure the line disconnection relay. In case of an HSMS connection, the line is disconnected by the line connection relay trigger. In case of an SECS- connection, the port is closed.
Configure the scenario interruption relay. Scenario execution is interrupted by the trigger of the scenario interruption relay. T9 dialog interruption is also possible.
Configure the dialog interruption relay. Dialog execution is interrupted by the trigger of the dialog interruption relay. T9 dialog interruption is also possible.
Configure the offline relay. An offline transition is requested of the SECS/GEM communication software by the offline relay trigger. When the "Switch Into Offline Status Upon Disconnection" checkbox is cleared at the [Control 1] tab, the SECS/GEM communication software does not transition to offline other than by this request. Nothing occurs when this request was detected in an already offline state. The SECS/GEM communication software completes the transition to the offline state by this request. When there is an offline procedure, have it complete before this relay is switched ON. However, it is not necessary to wait for sending completion of an offline report message or secondary message reception. The SECS/GEM communication software switches OFF the offline relay immediately after detecting that the offline relay is ON. The relay is switched OFF immediately even when there is already is an offline state. Completion of offline transition is checked by the "Online" relay.
Select this checkbox to configure a communication-disabled state following the offline transfer. In a communication-disabled state, messages other than S1F13/F14 received from the host are discarded. Furthermore, sending requests other than S1F13/14 are canceled.
Select this checkbox to close the TCP/IP port after the Separate procedure following the offline transition. The reconnection procedure is not performed automatically. To start reconnection, use the line connection relay.
The times that the Line Connection, Line Disconnection, Scenario Interruption, Dialog Interruption, and Offline relays are held are monitored, and triggers are detected. If the "Not Monitored" checkbox is selected, trigger processing is carried out without hold monitoring.
Configure the online-start relay to instruct a start in an online state. When you want to return to an online state after communication establishment (S1F13F14) without performing an online transfer (S1F1F2) because, for example, a reset was performed while maintaining an online state, set the online start relay to ON, and then start the SECS/GEM communication software. Use the programmable controller CPU to determine advisability of the online start.
86
7 BASIC FUNCTIONS 7.6 Option Setting
Item
Description
Abort Return
Configure the abort return relay. While the abort return relay is ON, an abort message is returned, instead of a secondary message, after a primary message is received. For more details, see the following reference. Page 88 Operations of Abort Return and S9F7 Return
S9F7 Return Enable Spooling*3 Spool Output Request*3
Spool Data Disposal*3 Trigger Hold Time*3
Configure the S9F7 return relay. While the S9F7 return relay is ON, an S9F7 message is returned, instead of a secondary message, after a primary message is received. For more details, see the following reference. Page 88 Operations of Abort Return and S9F7 Return
Configure in the Enable spooling relay to enable the spooling function. When the Enable spooling relay has been disabled, the spooling function is always available. If this is OFF during spooling, the Enable spooling relay to be defined at the [CA Status] tab is also OFF. However, all messages being spooled are sent, even after an operation to switch the Enable spooling flag from ON to OFF while spool data is being output. Regarding the spooling relay, see the following reference. Page 82 CA Status
Configure the spool output request relay to request an output of the spool (transfer or discarding).
The SECS/GEM communication software outputs the spool upon receipt of the S6F23 (Spooled data
request) from the host.
This operation complies with GEM standards.
However, this relay is used, and the spool is output when the spool request message is not used due to
communication standards or the format of the spool request message differs from the standards.
Turn ON the relay from a ladder program to start transfer of the spool. The SECS/GEM communication
software turns OFF this relay either after all transfers are completed or the transfer process ends with
an error. To determine whether all transfers were completed, check "No. of Spool Items". For "No. of Spool Items", see the following reference.
7
Page 106 Spool Definition Settings
When the spool is to be discarded, with the spool data disposal relay ON, turn ON the spool output
request relay.
Configure the spool data disposal relay to discard the spool data and initialize it. This relay does not function on its own. This relay is referenced when the Enable spooling relay is switched ON or OFF or when the Spool output request relay is controlled to ON. After the spool data is discarded, the SECS/GEM communication software turns OFF the relay. To dispose of spool data, it is necessary for the programmable controller CPU to turn ON the relay before manipulating the spool enabled flag.
The times that the Enable Spooling, Spool Output Request, and Spool Data Disposal relays are held are monitored, and triggers are detected. If the "Not Monitored" checkbox is selected, trigger processing is carried out without hold monitoring.
*1 Can be configured for only the MELSEC-Q series SECS/GEM communication software pre-installed model module. *2 Can be configured for only the MELSEC iQ-R series SECS/GEM communication software pre-installed model module. *3 Can be configured only by a non-GEM version.
7 BASIC FUNCTIONS 7.6 Option Setting
87
Operations of Abort Return and S9F7 Return
Use to send an abort or S9F7 in accordance with the data content or return an abort or S9F7 when some processing is being carried out at the equipment after a primary message was received. When a primary message was received, and a secondary message is to be sent, the SECS/GEM communication software refers to the status of this relay. If the relay is ON, it sends an abort or S9F7 message. If the relay is OFF, the prescribed secondary message is sent. Accordingly, it is necessary to carry out a sending request of a secondary message as usual, even when an abort or S9F7 is to be sent. Furthermore, when Abort return or S9F7 return has been switched ON, the SECS/GEM communication software does not switch OFF the abort relay but switches OFF the S9F7 relay. That is why the setting of Abort return is enabled when a transaction other than a special transaction is aborted due to processing being performed at the equipment.
Precautions
Setting a Y device for each relay
It is possible to configure "OWN (host station)" as the CPU number and device to "Y" when the MELSEC iQ-R series SECS/ GEM communication software pre-installed model module is being used. When "Y" has been configured for the device, the SECS/GEM communication software does not switch the output signal (Y) from ON to OFF. To enable the output signal again, switch the output signal one time from ON to OFF, and then from OFF to ON.
Online Start Relay
· For the online start relay, configure the link relay of B devices, etc., and the M device specified to automatic refresh from the X device that directly inputs the equipment switch.
· Before CIM control READY is switched ON, the SECS/GEM communication software references the online start relay state. If it is ON, an online start is performed. After CIM control READY turns ON, an online start is not performed even when the online start relay is controlled.
Abort Return Relay and S9F7 Return Relay
Regardless of the setting content, the receipt of primary messages is carried out by normal operation. It is not the case that an automatic return is performed for primary messages while these relays are ON.
Spool Control
Spool data is saved to the memory card in the SECS/GEM communication software pre-installed model module. Configure so that the Enable spooling relay is not switched frequently during queuing, spool data output, and other spool processing.
88
7 BASIC FUNCTIONS 7.6 Option Setting
About forced offline during emergencies
When the offline relay was switched ON, any unsent messages in the sending queue are discarded. When there is an emergency offline transition after an offline report message was sent, the format specified "OFFLINE" function is used.
Ex. When multiple messages that have accumulated in the sending queue are discarded, an offline report only is sent, and there is a transition to offline Setting: configure the S6F101 format specification to "OFFLINE"
Programmable controller CPU
SECS/GEM communication software
Host
MessageÒ transmission request Primary messageÒ transmission
MessageÓ transmission request
MessageÔ transmission request
S6F101 transmission request
7
Off-line relay trigger ON
Secondary messageÒreception
S6F101 transmission
S6F102 receive notification
S6F102 reception
[Online] relay is OFF
Same sequence applies for disconnection.
In the example above, the S6F101 "Trigger Hold Time" is configured to a value less than the offline "Trigger Hold Time". This is the setting to send S6F101 first when the S6F101 sending request trigger and offline trigger were switched ON simultaneously. S6F101 is not sent until a secondary message of message is received or a T3 timeout occurs. This function sends offline reports by priority for queued messages and . It does not prioritize and send just by a sending request of S6F101. Switching ON the offline trigger relay prioritizes and sends S6F101. Messages and are discarded. However, the offline spool is configured to enabled, and messages subject to spooling are spooled. When message resulted in a T3 timeout, the operation differs by the retry setting. When the retry function is disabled or "Retry cancel" has been selected for offline transition, S6F101 is sent immediately. When "Retry priority" has been selected for offline transition, S6F101 is not sent until the retries are complete.
7 BASIC FUNCTIONS 7.6 Option Setting
89
SECS Error Notification Setting
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][SECS Error Notification Setting] tab
MELSEC-Q series
GEM advanced version
MELSEC iQ-R series
90
7 BASIC FUNCTIONS 7.6 Option Setting
Displayed items
Item
Description
Abort Frame Reception Abort Frame Transmission
Configure the relay to notify the programmable controller CPU that the SECS/GEM communication software has received an abort message.
Configure the relay to notify the programmable controller CPU that an abort message has been sent from the SECS/GEM communication software.
Sending Failure
PLC Handshake Failure
T3 Timer Timeout
Notice Cancel By Disconnection/Offline
Configure the relay to notify the programmable controller CPU that a data sending failure has occurred from the SECS/GEM communication software.
Configure the relay to notify the programmable controller CPU that a handshake link with the programmable controller CPU failed during data receipt.
Configure the relay to notify the programmable controller CPU that a response timeout occurred with the host.
Configure the relay to notify the ladder program that the T3 timer is canceled for a transaction in a secondary message standby state due to a line disconnection or offline transition.
T9 Timer Timeout
T1 Timer Timeout *1 T2 Timer Timeout *1 T4 Timer Timeout *1 Scenario Interruption *1 Trigger Keep Time Handshake
Communication error
Frame
Trigger
Configure the relay to notify the programmable controller CPU that a timeout of T9 timer management occurred. For details on the T9 timer, see the following reference. Page 52 Message Information
Configure the relay to notify the programmable controller CPU that a timeout occurred between characters during reception from the host.
Configure the relay to notify the programmable controller CPU that a protocol timeout occurred with the host.
Configure the relay to notify the programmable controller CPU that a timeout occurred between message blocks during communication with the host.
7
Configure the relay to notify the programmable controller CPU that the scenario execution was interrupted for some reason.
Configure the time to keep the configured notification relay.
Select this checkbox to link handshakes between the programmable controller CPU and SECS/GEM communication software pre-installed model module with regard to SECS error notification. When this checkbox is selected, the specified relay is monitored for handshaking. Note that programmable controller CPU handshaking fails unless the specified relay is turned OFF by the programmable controller CPU within the time defined by the PLC response monitoring timer. For details on the PLC Response Monitoring Timer, see the following reference. Page 69 Control 1
Configure the register to write the number of the Stream Function that had a transmission error. The Stream number is written to the start register and the Function number is written into the next register.
Configure the register to write the type and number of the trigger relay that had a transmission error. The defined register is the first register, and the next register will also be used for registration. The device type is written to the start register and the device number is written into the next register. The following section shows the values to be written as device types. · Device type is M: 4 · Device type is B: 23
*1 Can be configured for only the MELSEC-Q series SECS/GEM communication software pre-installed model module.
7 BASIC FUNCTIONS 7.6 Option Setting
91
S9 Transmission Notification
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][S9 Transmission Notification] tab
GEM advanced version
Displayed items
Item
S9F1 S9F3 S9F5 S9F7 S9F11
S9Fx
Trigger Keep Time Handshake
Description
Configure the register to notify the programmable controller CPU of sending of an undefined device ID message.
Configure the register to notify the programmable controller CPU of sending of an undefined stream type message.
Configure the register to notify the programmable controller CPU of sending of an undefined function type message.
Configure the relay to notify the programmable controller CPU of sending of an incorrect data message.
Configure the register to notify the programmable controller CPU of sending of a message with an incorrect data length.
Configure the relay to notify the programmable controller CPU when one of the following was sent: undefined device ID, undefined stream type, undefined function type, incorrect data, or message with incorrect data length. Operation of S9Fx relays is enabled regardless of the settings of the S9F1, S9F3, S9F5, S9F7, and S9F11 relays.
Configure the time to keep the notification relay.
Select this checkbox to link handshakes between the SECS/GEM communication software pre-installed model module and programmable controller CPU with regard to S9 sending notification. If this checkbox is selected, S9 sending notifications are subject to handshake monitoring. Programmable controller CPU handshaking fails unless the notification relay is turned OFF by the programmable controller CPU within the time configured by the PLC Response Monitoring Timer. For details on the PLC Response Monitoring Timer, see the following reference. Page 69 Control 1 For details on programmable controller CPU handshake failures, see the following reference. Page 90 SECS Error Notification Setting
92
7 BASIC FUNCTIONS 7.6 Option Setting
Precautions
· To send S9F7 when the data received from the host is illogical, enable the S9F7 return relay setting. · Detect S9F9 by notification of the T3 timer timeout. · Detect S9F13 by notification of the T9 timer timeout. Note that a message needs to be created by the programmable
controller CPU since S9F13 is not automatically sent.
When "S9Fx" and individual notification relays have been enabled
Ex. When "S9Fx" and "S9F7" have been enabled First, the S9Fx notification relay turns ON, and then the S9Fx notification relay is turned OFF by the programmable controller CPU. Next, the S9F7 notification relay turns ON, and then the S9F7 notification relay is turned OFF by the programmable controller CPU.
7
7 BASIC FUNCTIONS 7.6 Option Setting
93
Console Setting
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][Console] tab
GEM advanced version
Displayed items
Item
Console Setting
User Password Serial port information Baud Rate Data Length Parity Stop Bit Flow Control
Description
Select this checkbox to acquire log data of the SECS/GEM communication software from the MELSECQ series SECS/GEM communication software pre-installed model module through serial communication. If this checkbox is selected, the console function always runs within the SECS/GEM communication software.
Configure the user name when logging into the console.
Configure the password when logging into the console.
Configure the communication setting information for the console connection.
94
7 BASIC FUNCTIONS 7.6 Option Setting
How to use the console
Use HyperTerminal, which is included with the Windows operating system, to connect the MELSEC-Q series SECS/GEM communication software pre-installed model module via serial communication. HyperTerminal can be used with Windows 2000 and Windows XP.
Start-up and login of HyperTerminal
1. Select Windows Start[Programs][Accessories][Communication][HyperTerminal]. 2. Enter the user name and password.
Directory confirmation and manipulation
Use the following commands.
Command
dir cd ***(directory name) mkdir ***(directory name) rmdir ***(directory name)
Description
Check a directory. Move a directory. Create a new directory. Delete a directory.
Downloading of files
Download a file from the current directory.
1. Enter the download command "down ***(filename)".
2. From the HyperTerminal menu, select [Transfer][Receive File].
7
3. Configure the file save destination, and configure the protocol to "Xmodem".
4. Click [Receive].
Uploading of files
Upload a file to the current directory.
1. Enter the upload command "up ***(filename)". 2. From the HyperTerminal menu, select [Transfer][Send File]. 3. Configure the file to be sent, and configure the protocol to "Xmodem". 4. Click the [Send] button.
Browsing Help
Use the following commands.
Command
help
Description
Check the commands that can be used.
7 BASIC FUNCTIONS 7.6 Option Setting
95
Version Information
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Option Setting][Version Information] tab
GEM advanced version
Displayed items
Item
Version Information
License Registration
License Matching
Description
Configure the register to store the version of the SECS/GEM communication software currently running. The version is stored as a character string in a register of 5 consecutive words starting from the configured register. The storage method is the same as the ASCII format item storage method. For the ASCII format item storage method, see the following reference. Page 261 Data type conversion
Configure the register to store the presence of the license file. If the license file is recognized, the SECS/GEM communication software turns ON the designated trigger. The activation destination of the license is the transfer destination (ROM or memory card) selected at the "Update Module" screen or "Update C intelligent module" screen. If the registration destination is different, the SECS/GEM communication software does not recognize the license file.
Configure the relay to store the compliance regarding the content registered to the license file. When a genuine license is been registered, the SECS/GEM communication software turns ON the designated trigger. For license registration, see the following reference. Page 27 License registration
96
7 BASIC FUNCTIONS 7.6 Option Setting
7.7 Scenario definition
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Defining a scenario allows sequential operation of two or more transactions with a single bit trigger.
Window
[Setting][Scenario Setting]
7
Operations of the Scenario List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Scenario Setting" screen to modify the content of the selected scenario. Add a new scenario. Copy the selected scenario, and then copy the copied scenario to the row below. Move the selected scenario.
Delete the selected scenario.
7 BASIC FUNCTIONS 7.7 Scenario definition
97
Scenario Setting
Modify the scenario selected at the "Scenario" screen.
Window
Select a scenario at the "Scenario" screen, right-clickShortcut menu [Edit]
Displayed items
Item
Scenario name Scenario Start Request Trigger Trigger Hold Time
Scenario Definition transaction
[Add To SND] button [Add To RCV] button [Delete] button [Up] button [Down] button
Description
Configure the scenario name. Configure the trigger relay to request a scenario start from the programmable controller CPU. When the scenario start request trigger is held for the configured time, a scenario start trigger results. If the "Disable" checkbox is selected, scenario start request trigger processing is carried out without hold monitoring. Lists the transactions registered to the scenario. Displays the defined transaction name and Stream and Function numbers. If an arbitrary transaction is selected, the [Add To SND] button or [Add To RCV] button can be clicked in correspondence with the transmission type of that transaction. Register the transaction selected by "Definition transaction" to the scenario.
Delete the transaction selected under "Scenario". Change the order of transactions of "Scenario".
98
7 BASIC FUNCTIONS 7.7 Scenario definition
Scenario transaction operation sequence
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
Scenario start request trigger on
Scenario start request trigger
off
Start request trigger on detection
Transmission data
Reception data registration
Reception data registration
SECS message transmission SECS message reception
SECS message reception
Scenario transaction Ò
Scenario transaction Ó
Transmission data
SECS message transmission
Transmission data
SECS message transmission
Scenario transaction
7
Ô
SECS message reception
Reception data registration
Scenario start request trigger off
In the course of transaction operations within a scenario, the software refers to (for sending) or writes data to (for receiving) the related register without controlling the trigger relay. Be aware that the registration-destination register is overwritten every time a message is received.
7 BASIC FUNCTIONS 7.7 Scenario definition
99
7.8 Alarm Definition (non-GEM version)
Alarm notification definitions allow arbitrary definition and sending of the content of the alarm notification used by S5F1. This is completed just by controlling the alarm occurrence/recovery trigger and the register that corresponds to the prescribed alarm at the programmable controller CPU.
Operations during Alarm Notification
When the occurrence of (or recovery from) an alarm has been detected, the fact that a prescribed alarm occurred (or was recovered from) is reported (S5F1 alarm sending) regarding a location in which the register status changed.
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
Alarm type registration
Alarm occurrence trigger on
Alarm status register
~
11
Error 17 Error 18
Alarm occurrence trigger detection*1, Trigger off
S5F1 alarm transmission (Error 16 occurrence) S5F2 reception
S5F1 alarm transmission (Error 17 occurrence) S5F2 reception
Alarm type registration
Alarm occurrence trigger on
Alarm status register
~
10
Error 17 Error 18
Alarm reset trigger detection*2, Trigger off
S5F1 alarm transmission (Error 17 reset) S5F2 reception
*1 Compares with the internal state to detect items in which the register status changed from 0 to 1. (For occurrence trigger) *2 Compares with the internal state to detect items in which the register status changed from 1 to 0. (For recovery trigger)
100
7 BASIC FUNCTIONS 7.8 Alarm Definition (non-GEM version)
Alarm List
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Displays a list of defined alarms. Up to 4096 alarms can be defined here.
Window
[Setting][Alarm]
GEM advanced version
7
Operations of the Alarm List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Alarm Settings" to modify the content of the selected alarm. Add a new alarm. Copy the selected alarm, and then copy the copied alarm to the row below. Move the selected alarm.
Delete the selected alarm.
The content of the alarm list is saved to the following file. (Project save destination)\ALARM.CSV When the alarm content is large or redundant, it is convenient to use Microsoft Excel or another external editor to modify this file. After the corresponding file is edited, the content is updated by opening the same project again.
7 BASIC FUNCTIONS 7.8 Alarm Definition (non-GEM version)
101
Alarm Settings
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
Select an alarm at the "Alarm List" screen, right-clickShortcut menu [Edit]
GEM advanced version
Displayed items
Item
Alarm No. Alarm code Hexadecimal
Alarm ID Alarm text User-defined items
Description
Configure the number that corresponds to the prescribed alarm state register. (Start from 1)
Configure the content of the alarm code <ALCD > related to the alarm number.
Select this checkbox to convert the alarm code notation to hexadecimal. If this checkbox is cleared, the notation is decimal.
Configure the content of the alarm ID <ALID > related to the alarm number.
Configure the content of the alarm text <ALTX > related to the alarm number.
Configure the content of the user-defined items related to the alarm number. To configure user-defined items, browse to the "Alarm Notification Settings" screen and configure "User-defined item quantity" in advance. For details on alarm notification settings, see the following reference. Page 103 Alarm Notification Setting User-defined items can be used only for transactions with ALARM configured for the format specification. The content of user-defined items is sent by selecting the user-defined item name for the storage destination type of the item information.
102
7 BASIC FUNCTIONS 7.8 Alarm Definition (non-GEM version)
Alarm Notification Setting
Series
MELSEC-Q series MELSEC iQ-R series
Window
SECS/GEM communication software
Non-GEM version
GEM version
[Setting][Alarm notification]
GEM advanced version
Displayed items
7
Item
Alarm Notification Setting
Alarm Occurrence Notification Alarm Reset Notification Alarm Processing Notification
Alarm Status Register (Start) No. of Alarm Status Registers
Trigger Hold Time
Clearing the alarm status register during an online transition
User-defined item quantity
Report cancel notification relay
Description
Select this checkbox to use the alarm notification setting.
Configure the trigger relay to notify the SECS/GEM communication software of an alarm occurrence.
Configure the trigger relay to notify the SECS/GEM communication software of an alarm reset.
Configure the relay to report that alarm sending is being processed. Turned OFF by receipt of a secondary message of the final alarm message. It is possible to check that the ladder program is performing sending processing when a large number of alarms occur at once.
Configure the register to display the alarm status.
One register can manage the alarm status of 16 items. Configure the quantity of registers to be used according to the number of alarm items. Up to 256 registers can be configured (maximum alarm count is 4096).
A notification trigger results when the register configured for the alarm occurrence notification trigger or alarm recovery notification trigger was held for the configured time. If the "Not Monitored" checkbox is selected, notification trigger processing is carried out without hold monitoring.
Select this checkbox to clear the content of the alarm status register when an online state is established (S1F1/F2 transmission). When the alarm status register is cleared, the internal alarm status of the SECS/GEM communication software is cleared as well. If this checkbox is cleared, make the programmable controller CPU clear the alarm status register and internal alarm status as needed.
Configure the maximum number of user-defined items used by transactions with ALARM configured for the format specification. For details on user-defined items, see the following reference. Page 102 Alarm Settings
Configure the relay to report that the alarm is being canceled when a large number of alarms occurred at the same time. For more details, see the following reference. Page 105 Alarm Cancel Notification
7 BASIC FUNCTIONS 7.8 Alarm Definition (non-GEM version)
103
Precautions
Alarm report sending (S5F1/F2)
Alarm report sending (S5F1/F2) is a reserved transaction and is automatically sent. Configuring a transaction for this purpose is not required. For details on reserved transactions, see the following reference. Page 268 List of reserved transactions and format
No. of Alarm Status Registers
When multiple registers are used, the consecutive registers from the specified start alarm status register up to the configured quantity targeted. Make sure not to overlap with any register defined in other item settings.
Editing of ALARM.CSV
ALARM.CSV is a text file with items delimited by commas. When editing the data, take care not to change the file format. Furthermore, back up and store the file before modifying it.
104
7 BASIC FUNCTIONS 7.8 Alarm Definition (non-GEM version)
Alarm Cancel Notification
The SECS/GEM communication software may be affected when a large number of alarms occur at the same time. To prevent this, the SECS/GEM communication software cancels alarms when 33 or more alarm reports are sent at the same time. Even when the number of alarm reports is 32 or less, alarm reports are canceled when the sending queue becomes full before all sending is finished. With regard to canceled alarm reports, sending is started again by switching the alarm occurrence (or alarm recovery) trigger to ON, and the report cancel notification relay is switched OFF when all reports are completed. In addition to the interlock of the alarm status register, a lock by the ladder program is necessary so that recovery processing is not performed until all alarm occurrences are completed when alarms are canceled during alarm occurrence processing. Similarly, a lock is used to prevent occurrence processing midway when alarms are canceled during alarm recovery processing. The following section shows the processing flow when 50 alarms have occurred.
Programmable controller CPU
SECS/GEM communication software
Host
Alarm Occurrence trigger ON
Scan status register
(50 Alarms occur simultaneously)
7
Send 32 Alarm reports
Alarm Processing Notification relay ON
Interruption Notification relay ON
Alarm occurrence trigger OFF
Alarm Processing Notification relay OFF
Secondary (Reception of 32 secondary messages)
(1) Alarm occurrence trigger ON
Scan status register
Alarm Processing Notification relay ON Interruption Notification relay ON Alarm occurrence trigger OFF
Send 18 Alarm reports
Secondary (Reception of the remaining 18 secondary Alarm Processing Notification relay OFF messages)
(1) Locked by the ladder program so that alarm recovery processing is not carried out until all alarm report sending is complete
7 BASIC FUNCTIONS 7.8 Alarm Definition (non-GEM version)
105
7.9 Spooling function (non-GEM version)
Messages that failed to be sent for some reason can be kept as spool messages. Spooled messages can be resent when communication is recovered. Spooled messages are stored on the memory card.
Spool Definition Settings
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
Common Spool Definition settings Window
[Setting][Spool][Spool Common Setting]
Displayed items
Item
Maximum No. Of Spool Items Action when data is exceeded
No. of Spool Items
Maximum number of data items output
Number of output items
Spool during offline Spool due to a T3 timeout Spool activity start timing
Spool activity cancel timing
Description
Configure the maximum number of messages to be spooled.
Select the operation method when the maximum number of items is exceeded. Overwrite: overwrite spooled messages. Discard: discard the overflow.
Configure the register to store the number of spool items. Data items being spooled are stored to the register in 2-word, 32-bit integers.
Select this checkbox to output the maximum number of data items. The maximum number of data items output is stored from the register configured for spool items plus 2 word positions in data of two-word, 32-bit integers.
Configure the register to store the number of output items. The number of spool output items is stored to the register in 2-word, 32-bit integers.
Select this checkbox to use the spool function in an offline state.
Select this checkbox not to cancel communication and perform spooling due to a T3 timeout.
Select the spool activity start timing. · Treat initial spool occurrence time as start: the spooling relay switches ON when messages were
spooled, and the "Spool start time" is stored. · Treat communication error occurrence time as start: the spooling relay switches ON when a
communication error (T3 timeout, etc.) occurred by a sending message, and the "Spool start time" is stored.
Select the spool activity cancel timing. · Treated as cleared by empty spool: the spool is cleared when all spool messages of the spool buffer
have been transferred or deleted.
106
7 BASIC FUNCTIONS 7.9 Spooling function (non-GEM version)
Item
Description
Operation when spool is full
Select the spooling operation after the spool buffer becomes full. · Spooling possible after spool transfer completion/deletion: after the number of spool items reaches
the maximum, spooling is not possible again if the entire spool has not been transferred or deleted. · Spooling possible with empty spool buffer: after the number of spool items has reached the
maximum, spooling is possible, even when previous spool data remains, when the spool buffer could be emptied by spool transfer, etc.
Abort receipt during spool transmission
Select the operation when an abort message is sent for a spool transmission message. · Message is retained and transfer is canceled: the transfer of the spool is canceled. At the next
transfer, the transfer is started from a message that returned an abort. · Skipped and transfer is continued: the spool transfer message that returned an abort is skipped, and
transfer is continued automatically from the next spooled message. Transfer is completed when there is finally a spooled message.
Spool time storage format
Select the format of the spool start time, spool cancel time, and spool-full time to be stored to the specified register. For more details of each format, see the following reference. Page 79 Register storage formats
Spool-start time
Configure the register to store the time the spool started.
Spool-cancel time
Configure the register to store the time the spool cancelled.
Spool-full time
Configure the register to store the time until the maximum number of spool items was reached.
Number of output items
· The number of spool output items is counted from receipt of an S6F23 (Spooled data request) transfer request.
· Previous values are not retained due to a reset. (Values are not retained after reset.)
· Counted as output items when the spool was discarded.
· Counted as one item by spool transmission success. (When there is a W-bit, when a secondary message is received).
7
· The final result is stored before the Spooling relay or Spool outputting relay is turned OFF.
· Two words each are used for the number of spool items, maximum number of data items, and number of output items, so take care not to overlap with other register settings.
Abort receipt during spool transmission setting
· If "Set communication as disconnected by receipt of an abort of message subject to spooling" is enabled at the [Control 1] tab of Option Configure tings and "Skip and continue transfer" is configured, "Skip and continue transfer" is prioritized, and communication is not disconnected when an abort message is received during spool transmission. At times other than spool transmission, communication is disconnected when the conditions are met.
· In the case of "Abort Frame Reception" at the SECS Error Notification Setting tab of the Option settings, a relay notification is performed regardless of the "Abort receipt during spool transmission" setting.
Important points regarding spool definition settings
· The SECS/GEM communication software does not turn OFF the sending request relay unless message sending is completed. Accordingly, when primary messages are to be sent, it is necessary to describe the handshake response monitoring timer processing of the SECS/GEM communication software at the programmable controller CPU. At this time, the spooling relay turns ON when there are messages subject to spooling.
· When the spooling relay is ON, the SECS/GEM communication software does not send a message when the equipment attempts to send a primary message not subject to spooling. However, S1 and S9 related messages are sent.
Considerations when switching the power ON or OFF
· Before turning OFF the power of the C Controller module, disable spooling or move the Mode switch of the C Controller module from RUN to STOP, and then wait 3 seconds or more. To prevent corruption of logs and spooling files, all file writing is stopped. Furthermore, return the Mode switch to RUN before turning ON the power. Operation may be affected because there are limits on file access during start-up.
· Before turning OFF the power of the C intelligent function module, disable spooling or unmount the SD card (by moving the Mode switch of the C intelligent function module from the center to SELECT for 3 seconds or more). To prevent corruption of logs and spooling files, all file writing is stopped. Furthermore, return the Mode switch to the center before turning ON the power. Operation may be affected because there are limits on file access during start-up.
7 BASIC FUNCTIONS 7.9 Spooling function (non-GEM version)
107
Spool message settings Window
[Setting][Spool][Spool Message Settings]
Displayed items
Item
Message selection Item specification
Spooling setting list display [Up] button [Down] button [Add] button [Modify] button [Delete] button
Description
Select the defined message name and Stream/Function number. Select an item. Use when a spool flag is included in the item of a message subject to spool. In this way, the spool flag distinguishes between normal sending and spooling sending. · Normal sending: conforms to item information · Spooling sending: fixed to "1" When the corresponding item is used as a spool flag, the defined item name is displayed for messages with the spool flag selected, so click the [Search] button. Confirm the message flag path, and then click and configure each button. A list of defined spool messages is displayed. If a message is selected, the message content and spool flag path are displayed. Change the order of messages of "Spooling setting list display"
Configure new spool messages. Change a spool flag of an already configured message. Cancel messages subject to spooling.
Precautions
The setting of the spool flag path is defined for content already configured. Accordingly, be aware that it is necessary to configure the spool flag path setting again when the corresponding message was changed.
108
7 BASIC FUNCTIONS 7.9 Spooling function (non-GEM version)
Spooled message sending
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
For messages subject spooling, operations are performed particular to the status. The following section shows operations of messages that can and cannot be sent due to status.
Message classification
Online
Spooling online
Offline*1
Message subject to spooling Message not subject to spooling
S1 message S9 message*2
Sending possible Sending possible
Sending possible
Sending possible (automatic)
Spooling Sending not possible
Sending possible
Sending possible (automatic)
Spooling
Sending not possible (sending cancellation)
Sending possible only for S1F1 and S1F13
Sending possible (automatic)
*1 When the "Spool during offline" setting is enabled *2 For S9 messages, sending is automatic, so handshakes are not performed.
Spooling Operation Sequence
If message sending fails due to a line disconnection, etc., messages subject to spooling are stored on the memory card. Also,
messages subject spooling are not sent and are all stored on the memory card while the spooling relay is ON.
7
Programmable controller CPU
Shared memory/ Device
SECS/GEM communication software
Host
Transmission request detection
(1) The spooling relay is ON.
Messages subject to spooling are saved to the CF card/SD card
(1)
Transmission request detection
Transmission request relay off
Messages subject to spooling are saved to the CF card/SD card
7 BASIC FUNCTIONS 7.9 Spooling function (non-GEM version)
109
Operation sequence during spool message sending
All spool sending is performed by the SECS/GEM communication software. The spool outputting relay is ON during spool sending, and then switches OFF when complete. At this time, the spooling relay is also OFF.
Programmable controller CPU
SECS/GEM communication software
Host
Spooled data request(S6F23)
Spooled data request response (S6F24 (spooled data present)) (1)
Spooled message transmission
Spooled message response (2)
Spooled message transmission
(3)
Spooled message response
(1) The spooling relay switches ON. (2) The spooling outputting relay switches ON. (3) The spool outputting relay and spooling relay switch OFF.
110
7 BASIC FUNCTIONS 7.9 Spooling function (non-GEM version)
7.10 Project Archive File Get
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Acquire the user definition archive (USRSET.LZH) transferred to the SECS/GEM communication software pre-installed model module and put it in the prescribed folder. The user definition archive is obtained from the "Destination" configured by the C intelligent module update or C Controller update.
In the case of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module, change "C Controller" to "C intelligent function module".
Window
[Setting][Project Archive File Get]
7
Displayed items
Item
IP Address User Password
Description
Configure the IP address of the SECS/GEM communication software pre-installed model module. Configure the username (login name) of the SECS/GEM communication software pre-installed model module. Configure the password of the SECS/GEM communication software pre-installed model module.
Operating procedure
1. Specify the folder to store the user definition archive to be acquired at the "Browse Folder" screen. 2. Configure the items of the "Project Archive File Get" screen. 3. Click [Get]. 4. Click [OK].
111 7 BASIC FUNCTIONS
7.10 Project Archive File Get
7.11 Updating the SECS/GEM communication software
pre-installed model module
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
From the setting tool, connect to the SECS/GEM communication software pre-installed model module, and then update the setting file stored on the standard ROM or memory card. If the file is updated, the setting tool is used to apply the configured content to the SECS/GEM communication software.
Precautions
· Always save the project before using this function. · Set the same location (standard ROM or memory card) for the application installation destination, setting file update
destination, and the license registration destination. · When the application was installed on the standard ROM and memory card, the application on the memory card runs. · Do not switch the power supply from OFF to ON while the SECS/GEM communication software pre-installed model module
is updating. Otherwise, the internal file system may be corrupted.
Window
[Setting] [Update C intelligent function module] (When a MELSEC iQ-R series SECS/GEM communication software pre-installed model module is used) [Setting] [Update C Controller module] (When a MELSEC-Q series SECS/GEM communication software pre-installed model module is used)
112
7 BASIC FUNCTIONS 7.11 Updating the SECS/GEM communication software pre-installed model module
Displayed items
Item
Description
C intelligent module
Select to transfer the setting file to the Standard ROM or memory card.
C Controller module SD card transfer CF card transfer
IP Address User
Password Destination Operation After Updating
Operations at start-up
Variable Setup*1
Configuration File Browse*1
Select to save the setting file to the memory card via a card reader.
Configure the IP address of the SECS/GEM communication software pre-installed model module. Configure the username (login name) of the SECS/GEM communication software pre-installed model module. Configure the password of the SECS/GEM communication software pre-installed model module. Select the transfer destination of the setting file. Select an operation after updating. For more details, see the following reference. Page 113 Operation After Updating Select whether to change to match the variable definition content the next time the SECS/GEM communication software starts. Select the setting file to be referenced the next time the SECS/GEM communication software starts.
Project Archive File Transfer
Select this checkbox to archive and transfer the setting file information. If the information is transferred, the file "USRSET.LZH" is created in the folder of the transfer destination.
Applications Install
Select this checkbox to transfer the application file of the SECS/GEM communication software from the SECS/GEM communication software pre-installed model module.
7
*1 Can be configured for only a GEM version and GEM advanced version.
Operation After Updating
The following section shows the operations after an update of the SECS/GEM communication software pre-installed model module.
No Operation (Only Update)
The setting file is updated. The setting content is applied the next time the SECS/GEM communication software pre-installed model module is started.
Restart (Reboot the Software)
Update the setting file, and then restart only the SECS/GEM communication software. Do not restart the SECS/GEM communication software pre-installed model module. The shared memory / device information is not changed. The settings can be updated without stopping the equipment.
7 BASIC FUNCTIONS 7.11 Updating the SECS/GEM communication software pre-installed model module
113
7.12 IP address setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
You can change the IP address of the SECS/GEM communication software pre-installed model module using the setting tool. The IP address is stored in a register of the programmable controller CPU and can also be changed from the ladder program that uses this register. Note that changes of the IP address of the SECS/GEM communication software pre-installed model module by this function are effective only when the SECS/GEM communication software is running. By using this function, the IP address and subnet mask can be changed but not the default gateway. This section shows the procedure to configure the IP address.
Operating procedure
1. Configure the IP address using one of the following methods.
· Page 116 Changing the IP address from the setting tool · Page 117 IP Address Setting by PLC
2. Reset the SECS/GEM communication software pre-installed model module.
The IP address is changed after the reset. (An event is registered to the event history of the Setting/monitoring tools for the C Controller module or GX Works3. )
To change the IP address of the SECS/GEM communication software pre-installed model module, it is recommended to use Setting/monitoring tools for the C Controller module or GX Works3.
Precautions
Change of the IP address
Carefully check the IP address before changing it. If the IP address of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module is changed to an incorrect address, it may be necessary to initialize the MELSEC iQ-R series SECS/GEM communication software preinstalled model module. Even when the IP address of the MELSEC-Q series SECS/GEM communication software pre-installed model module was changed to an incorrect address, the address can be corrected by obtaining the file and updating it via serial communication when the console of the Option settings is configured. If the console is not configured, it may be necessary to initialize the MELSEC-Q series SECS/GEM communication software pre-installed model module. For details on initialization, see the following reference. MELSEC iQ-R C Intelligent Function Module User's Manual (Application) MELSEC-Q C Controller Module User's Manual
Application of settings
The IP address is not changed during system operation. Always perform a reset to change the IP address.
reset
Before performing a reset, make sure that the CIM control ready relay is ON. In addition, if the MELSEC-Q series SECS/GEM communication software pre-installed model module is operating in the basic mode, two reset operations are required to change the IP address.
114 7 BASIC FUNCTIONS 7.12 IP address setting
When the IP address of the MELSEC iQ-R series SECS/GEM communication software preinstalled model module was changed
When this function is used to configure the IP address of the MELSEC iQ-R series SECS/GEM communication software preinstalled model module, 'IP address configuration file' remains in the standard ROM. Therefore, IP address settings from GX Works3 to the MELSEC iQ-R series SECS/GEM communication software preinstalled model module are not effective when the SECS/GEM communication software is running. Refer to the following file before deleting the IP address configuration file without initializing the Standard ROM. · (CA-SECS installation folder)/RECOVERY/ReadMe.txt
7
115 7 BASIC FUNCTIONS
7.12 IP address setting
Changing the IP address from the setting tool
Change the IP address of the SECS/GEM communication software pre-installed model module from the setting tool. In the case of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module, change "C Controller" to "C intelligent function module".
Window
[Function][IP Address Setting]
Operating procedure 1. Choose the Ethernet port to change the IP address. 2. Set each item. 3. Click the [Update] button. 4. A screen appears. Enter the IP address, user, and password of the target SECS/GEM communication software pre-
installed model module.
5. Click the [Update] button.
After transfer, the IP addresses is changed by resetting the SECS/GEM communication software pre-installed model module.
Precautions
· The default gateway cannot be changed by using this function. · The MELSEC iQ-R series SECS/GEM communication software pre-installed model module has only one Ethernet port, so
CH2 cannot be configured.
116 7 BASIC FUNCTIONS 7.12 IP address setting
IP Address Setting by PLC
The IP address of the SECS/GEM communication software pre-installed model module can be changed by a handshake with the SECS/GEM communication software. Use this procedure, for example, when changing the IP address from the equipment display.
In the case of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module, change "C Controller" to "C intelligent function module".
Window
[Function][IP Address Setting by PLC]
7
Displayed items
Item
IP Address (CH1) Setting By PLC
IP Address (CH2) Setting By PLC
Setting Request Trigger Start Register (12w) Setting Request Trigger Start Register (12w)
Description
Select this checkbox to change the IP addresses of CH1. Configure the trigger to configure the IP address of CH1. Configure the register to store the IP address information to be configured to CH1. Select this checkbox to change the IP addresses of CH2. Configure the trigger to configure the IP address of CH2. Configure the register to store the IP address information to be configured to CH2.
117 7 BASIC FUNCTIONS
7.12 IP address setting
Operating procedure
1. Configure "Setting Request Trigger" and "Start Register" at the "IP Address Setting By PLC" screen. 2. The IP address information is configured by the ladder program as shown below.
Storage destination register
Description
0 to +3 +4 to +7 +8 to +11
IP Address Subnet Mask Not used
3. Configure the setting trigger.
The SECS/GEM communication software switches OFF the setting trigger. The file necessary to change the IP address on the SECS/GEM communication software pre-installed model module is created by the SECS/GEM communication software.
4. Reset the SECS/GEM communication software pre-installed model module.
After resetting, the IP address of the SECS/GEM communication software pre-installed model module is changed.
Precautions
· The default gateway cannot be changed by using this function. · The MELSEC iQ-R series SECS/GEM communication software pre-installed model module has only one Ethernet port, so
CH2 cannot be configured.
IP address information
The IP address, subnet mask, and default gateway are configured by four words each. When the SECS/GEM communication software starts, the IP address information currently configured for the SECS/GEM communication software pre-installed model module is stored in the IP address information. The following section shows a configuration sample.
Register
Description
+0W
+1W
+2W
+3W
+0W
192
168
3
3
(IP address)
+4W
255
255
255
0
(Subnet mask)
+8W
0
0
0
0
(Unused)
118 7 BASIC FUNCTIONS 7.12 IP address setting
7.13 Data Mapping Settings
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The mapping function can add sending request trigger relays and reception notification trigger relays to the selected transactions and map offsets to the data control register as a command. In this way, it is possible to configure as shown below for one transaction definition. · Sending message: report data from control registers with different offsets by separating sending request trigger relays. · Receiving message: assign control registers and reception notification trigger relays to register reception data by the values
of items.
Window
[Function][Data Mapping Setting]
7
Operations of the Command List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Command Setting" screen to modify the content of the selected command setting. Add a new command setting. Copy the selected command setting, and then add the copied command setting to the row below. Move the selected command setting.
Delete the selected command setting.
119 7 BASIC FUNCTIONS
7.13 Data Mapping Settings
Command Setting
Window
Select a command setting at the "Command List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
Message
Use The Key Item
Key Item Key Item Path
Use Same Offset As Secondary Message
Use Same Offset As Select Register
Parameter List
Description
Select the message to configure the command setting.
Select this checkbox to use the item property defined in the transaction as the key item. The checkbox selection is fixed when a primary message to be received is selected.
Select the item property to serve as the key item.
Select the item path for the item property selected as the key item. When there are multiple names identical to the key item within the same message, select the corresponding key item path.
Select this checkbox to use the same offset in the transmission area of the secondary message information of the selected message.
Select this checkbox to use the same offset Select Register of the selected message.
Window
Select a command setting at the "Command List" screen, right-clickShortcut menu [Edit][Parameter List]
Operations of the Parameter List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Parameter Setting" screen to modify the content of the selected parameter. Add a new parameter. Copy the selected parameter, and then copy the copied parameter to the row below. Move the selected parameter.
Delete the selected parameter.
120 7 BASIC FUNCTIONS 7.13 Data Mapping Settings
Parameter setting
Window
Select a parameter to be configured at the "Parameter List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
Comment Parameter
Offset Primary message
Secondary message
Description
Enter a comment.
Configure the value of the key item defined in the command setting.
The value depends on the item property data type specified as the key item.
Configure the offset value for the control register to be defined by the item information.
7
Configure the sending request trigger relays and reception notification trigger relays to be added to the primary
messages subject to command settings.
The device type retains the settings of target primary messages.
Configure the sending request trigger relays and reception notification trigger relays to be added to the secondary messages subject to command settings. The device type retains the setting of target secondary messages.
121 7 BASIC FUNCTIONS
7.13 Data Mapping Settings
Mapping Setting Example
The following section describes an example of the register configuration and settings of the mapping by command function. In this example, transmission messages have the following structure.
Message format
<Message> <L, 2>
A <KeyItem> <L, 256>
U2 <Item1> U2 <Item2> U2 <Item3> U2 <Item256>
Notes
Control Register: W(0x0000) Control Register: W(0x0001) Control Register: W(0x0002) Control Register: W(0x00FF)
Sending message example
Select the transactions of trigger settings below for targets of command settings. Because this is a primary message sending example, the reception notification trigger of the primary message and the sending request trigger of the secondary message are not defined.
Primary message information Sending request trigger
B100
Reception notification trigger
Secondary message information
Sending request trigger
Reception notification trigger
B400
The parameters are configured by the command settings as indicated below.
Parameter
ParameterA ParameterB
Offset
100 200
Primary message information
Sending request trigger
Reception notification trigger
B101
B102
Secondary message information
Sending request trigger
Reception notification trigger
B401
B402
When a message added by parameter settings is sent, the specified offset is executed for the control register devices of each item defined in the message by the sending procedure as shown below, and the command register to be used is changed.
Control Register
W 0x0000
W 0x0100
W 0x0200
Item1 Item2 Item3 Item256 Item1 Item2 Item3 Item256 Item1 Item2 Item3 Item256
Operation Procedure
When B100 was switched ON as the sending request trigger, the software acquires data from the control registers configured in the items defined in the message.
When B101 was switched ON as the sending request trigger, the software acquires data from the register area that offsets the device numbers of the control registers configured in the items defined in the message by 100.
When B102 was switched ON as the sending request trigger, the software acquires data from the register area that offsets the device numbers of the control registers configured in the items defined in the message by 200.
122 7 BASIC FUNCTIONS 7.13 Data Mapping Settings
Reception message example
Select the transactions of trigger settings below for targets of command settings. Because this is a primary message receiving example, the sending request trigger of the primary message and the reception notification trigger of the secondary message are not defined.
Primary message information Sending request trigger
Reception notification trigger
B200
Secondary message information
Sending request trigger
Reception notification trigger
B300
The parameters are configured by the command settings as indicated below.
Parameter
ParameterA ParameterB
Offset
100 200
Primary message information
Sending request trigger
Reception notification trigger
B201
B202
Secondary message information
Sending request trigger
Reception notification trigger
B301
B302
When a message added by parameter settings is received, the specified offset is executed for the control register devices of each item defined in the message by the reception procedure as shown below, and the command register to be used is changed.
Control Register
W 0x0000
W 0x0100
W 0x0200
Item1 Item2 Item3 Item256 Item1 Item2 Item3 Item256 Item1 Item2 Item3 Item256
Operation Procedure
When the value of the received key item does not match the value configured
for the parameter, configure the data to the control register configured by the item defined in the message.
7
When the value of the received key item matches "ParameterA", configure the data to the register area offset by 100 to the number of the control register configured by the item defined in the message.
When the value of the received key item matches "ParameterB", configure the data to the register area offset by 200 to the number of the control register configured by the item defined in the message.
Precautions
Comparison of values of key items is determined after removing the space padding of the received item value.
123 7 BASIC FUNCTIONS
7.13 Data Mapping Settings
7.14 Conversion Table Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The data before and after replacement can be registered to the conversion table. Flexible data transfer between the programmable controller CPU and SECS/GEM communication software is possible by applying a conversion table to the message items.
Window
[Function][Data Convert Setting]
Operations of the Conversion Table List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Conversion Table" screen to modify the content of the selected conversion table. Add a new conversion table. Copy the selected conversion table, and then copy the copied conversion table to the row below. Move the selected conversion table.
Delete the selected conversion table.
124 7 BASIC FUNCTIONS 7.14 Conversion Table Setting
Conversion Table Setting
Window
Select a conversion table at the "Conversion Table List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
Description
Table name
Configure the table name.
Comment SECS Data Type
PLC Data Type Data Counts
default value SECS Data
PLC Data
Conversion definition
Table
Configure the comment.
Select the data type to be handled in SECS messages.
The number of data sets and variable length setting are in accordance with the definition of the item to
be applied. Select the data type to be handled in control registers.
7
Configure the number of data sets when saving to a register. Set from 1 through 128 when "ASCII" or "JIS8" is the SECS and PLC data type Set 0 or 1 in other cases.
Configure the default value of data to be handled in SECS messages. Data is regarded as before replacement during reception and after replacement during sending. When the data does not match the conversion data created at the "Conversion data definition" screen, operation is performed using this value.
Configure the default value of data to be handled in control registers. Data is regarded as after replacement during reception and before replacement during sending. When the data does not match the conversion data created at the "Conversion data definition" screen, operation is performed using this value.
Select to register data before and after replacement to the conversion table. Clicking the [Conversion Data] button displays the Conversion Data List screen.
Format Exponent
Number of digits in the integer part*1
Select to define the conversion string format to be applied to the data before replacement. Clicking the [Conversion Data] button displays the Format Conversion Definition Setting screen.
Select to define n of the index (nth power of 10) to be applied to the data before replacement. The exponential range is from -6 to 6.
Specify the number of digits in the integer part. The number of digits is 0 to 16. If the integer part is less than the number of digits, fill it with "0". If 1 is specified, 0 suppression results; if 0 is specified, 0 suppression also results for the fractional part as well.
[Conversion Data] button
Configure the details when "Table" or "Format" was selected at "Conversion Definition".
*1 Cannot be configured by a GEM or GEM advanced version of the MELSEC iQ-R series SECS/GEM communication software preinstalled model module.
Precautions
Comparison with the conversion table is determined after removing the space padding of the received item value.
125 7 BASIC FUNCTIONS
7.14 Conversion Table Setting
Conversion Data List
Window
Click the [Conversion Data] button at the "Conversion Table" screen.
Operations of the Conversion Data List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Conversion Data" screen to modify the content of the selected conversion data. Add a new conversion data. Copy the selected conversion data, and then copy the copied conversion data to the row below. Move the selected conversion data.
Delete the selected conversion data.
Conversion Data Setting
Window
Select conversion data at the "Conversion Data List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
SECS Data
PLC Data
Comment
Description
Configure the data to be handled in SECS messages. Data is regarded as before replacement during reception and after replacement during sending.
Configure the data to be handled in control registers. Data is regarded as after replacement during reception and before replacement during sending.
A comment can be entered.
126 7 BASIC FUNCTIONS 7.14 Conversion Table Setting
Example of Conversion Table Use
Message sending
Register Value
1 2 3 Other than above
Description
Send START. Send STOP. Send ABORT. Send DEF (default value). When a default value (SECS data) has not been entered, sending fails.
Message reception
7
Reception Data
START STOP ABORT Other than above ("SETUP," etc.)
Operation
Configures "1" to the item storage register. Configures "2" to the item storage register. Configures "3" to the item storage register. Configures "0" to the item storage register. When a default value (stored data) has not been entered, S9F7 is returned.
127 7 BASIC FUNCTIONS
7.14 Conversion Table Setting
Format conversion definition setting
While normally BIN ASCII conversion format is left-aligned with space padding, the format conversion definition setting function allows you to freely define the format, such as right-aligned with zeros suppressed. At the "Conversion Table Setting" screen, configure all items below, and then click [Conversion Data]. The "Format Conversion Definition Setting" screen opens. · SECS Data Type: ASCII · Conversion Definition: Format
Window
Displayed items
Item
Format Definition Input Form
Register Input Data [Conversion] button
Description
Configure the conversion string format. For the format, see the following reference. Page 129 Conversion string format
Configure how conversion string data is to be treated. · ASCII: Conversion strings are treated as ASCII. · Decimal: Conversion strings are treated as a numerical value (decimal). · Hexadecimal: Conversion strings are treated as a numerical value (hexadecimal).
Configure the conversion verification value. The value is configured as test data for verifying the format defined as the format conversion format.
Check the conversion results of the defined format definition.
Precautions
"ASCII" must be configured for the SECS data type. When a data type other than ASCII is configured in an item on the reception side, a format invalid (S9F7) error occurs.
128 7 BASIC FUNCTIONS 7.14 Conversion Table Setting
Conversion string format
The format is as follows: %[Flag][Field width].[Accuracy][h/l modification][Conversion string]. The following table indicates the details of each item.
Flag
Flag
+ Blank
0 #
#0 #x, #X #f
Description
Outputs the conversion string justified to the right when the field width is specified. Outputs the conversion string with a leading positive or negative (+/-) sign. Outputs the conversion string with a leading space (single-byte space) for positive values, and aligns the conversion string with a negative sign for negative values. Fills areas corresponding to spaces with zeros for numerical output of a specified field width. Adds a leading zero to octal data. Adds a leading '0x' to hexadecimal data. Always adds a zero to outputs.
Field Width
Field Width
Description
Numerical value
Specifies the output width.
Left pads with spaces when the number of significant digits is less than the specified width.
Ignores the width specification and outputs the significant digits of the data when the number of significant digits
specified is greater than the specified width.
Counts a decimal point as one place when the width is specified for a real number.
7
h/l Modification
h/l Modification
h
l
Description
Indicates that the corresponding argument is "short int" or "unsigned short int" when the conversion string is d, i, o, u, x, or X.
Indicates that the corresponding argument is "long int" or "unsigned long int" when the conversion string is d, i, o, u, x, or X.
Conversion String
Conversion String
%s %d, %i %u %o %x, %X %f
Description
Outputs the string as a character string.
Outputs the string in decimal format.
Outputs the string in unsigned decimal format.
Outputs the string in octal format.
Outputs the string in hexadecimal format. x is output as lower case, and X is output as upper case.
Outputs the string as floating decimal point data in decimal format. The conversion result always includes a decimal point. Applicable when numbers do not continue after the decimal point as well. Determines the number of significant digits after the decimal point according to the specified accuracy. (Default: 6 digits)
Ex. To send a control register value (binary value) in 5 digit (zero suppression) format, configure "%05d".
Precautions
To perform conversion in units of single characters, use %s. (%c cannot be used.)
129 7 BASIC FUNCTIONS
7.14 Conversion Table Setting
7.15 Device Find/Replace
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
This section explains the find and replace method for devices used in the project. The following table shows the ranges of devices that can be found/replaced.
Device
B D M R W X Y ZR
Range of devices that can be found/replaced
MELSEC-Q series
Non-GEM version
GEM version, GEM advanced version
B0 to BFFFF
B0 to BFFFF
D0 to D32767
D0 to D32767
M0 to M2147483647
M0 to M2147483647
R0 to R32767
R0 to R32767
W0 to W7FFF
W0 to W7FFF
X0 to X7FFF
X0 to X7FFF
Y0 to Y7FFF
Y0 to Y7FFF
ZR0 to ZR2147483647
ZR0 to ZR2147483647
MELSEC iQ-R series Non-GEM version (Ver.1.28E or later)*1
B0 to B7FFFFFFF D0 to D2147483647 M0 to M2147483647 R0 to R2147483647 W0 to W7FFFFFFF X0 to X7FFF Y0 to Y7FFF ZR0 to ZR2147483647
GEM advanced version
GEM version, GEM advanced version
B0 to BFFFF D0 to D32767 M0 to M2147483647 R0 to R32767 W0 to W7FFF X0 to X7FFF Y0 to Y7FFF ZR0 to ZR2147483647
*1 When using Ver.1.27D or earlier, the ranges of devices that can be found/replaced are the same as those of non-GEM version of MELSEC-Q series.
Window
[Setting][Device Find/Replace]
Displayed items
Item
Device List
130 7 BASIC FUNCTIONS 7.15 Device Find/Replace
Description
For details of items displayed in the device list, see the following reference. Page 131 Device list
Item
Find device Find Option Replace Device Replace Option
Find Device Top Find Tgt. Range Find Range(points) Replace Device Top Replace Range Move
[Select All] button [Unselect All] button [Exclude Select] button [Clear List] button [Use All Device] button [Find] button [Replace Select Device] button
[Replace All Device] button
Device list
Description
Configure devices to be found. Displays the top of the device to be found. Configure the search range. Configure the number of points to be found. Configure devices to be replaced. Displays the top of the device to be replaced. Configure whether to replace the specified range. Replace the range from "Replace Device Top" to the number of points specified by "Range (points)". Select all rows in the device list. Unselect selections in the device list. Delete selected rows from the device list. Clear the device list. Display all devices in use in the project. Search for devices that match the conditions of "Find device" and "Find Option". Replace the devices selected in the device list with the devices configured by "Replace Device" and "Replace Option". Replace all devices selected in the device list with the devices configured by "Replace Device" and "Replace Option".
Item
Assignment Device Points Kind
Setting Remarks
Description
Shared memory I/O assignment
Notes
Device allocated CPU shared memory
7
I/O assignment device
No assignment
Device not assigned
Device type and device number
n
Consecutive quantity in use
Option Setting
By setting type
Cache settings
Primary sending settings
Primary sending (interval) settings
Primary receiving settings
Secondary sending settings
Secondary receiving settings
Item settings
Item (selection register) settings
Command mapping settings (primary sending)
Command mapping settings (primary receiving)
Command mapping settings (secondary sending)
Command mapping settings (secondary receiving) Variable settings*1 Variable cache settings*1 Event settings (sending)*1 Event settings (receiving)*1 GEM trigger information settings*1 Model state notification settings*1
Setting location
Setting item name, etc.
Remarks
User comments, setting item explanations, etc.
*1 Can be used with the GEM version and GEM advanced version.
131 7 BASIC FUNCTIONS
7.15 Device Find/Replace
Display all devices in use
Display all devices in use in the project. Replacement is not possible while devices are being displayed by this function.
Operating procedure 1. Click [Use All Device].
Device Search
Search for devices.
Search by device
Find specified devices.
Operating procedure 1. Configure "Find Device Top". 2. Click [Find]. Range search
Find devices in the specified range.
Operating procedure 1. Configure "Find Device Top". 2. Select the "Range Find" checkbox. 3. Configure "Range(points)". 4. Click [Find].
132 7 BASIC FUNCTIONS 7.15 Device Find/Replace
Replace Device
Replace found devices. The correspondence of device types that can be replaced is as follows.
Before replacement
B, M X Y D, R, W, ZR
After replacement
B, M B, M, X B, M, Y D, R, W, ZR
Precautions
Devices cannot be replaced while all devices in use are displayed.
Replace by device
Replace specified devices.
Operating procedure
1. Select devices to be replaced in the Device List.
2. Configure "Replace Device Top".
3. Click the [Replace Select Device] or [Replace All Device] button.
7
Replacement by range
Group and replace consecutive devices.
Ex. Replace (move) devices included in the range from D0 through D99 to D100 through D199. Specifying a range and replacing can only be done when a range was specified and devices were found.
Operating procedure 1. Select devices to be replaced in the Device List. 2. Configure "Replace Device Top". 3. Select the "Range Move" checkbox. 4. Click the [Replace Select Device] or [Replace All Device] button.
Application of replacement results
Apply the results of device replacement to settings.
Operating procedure 1. In the "Device Find/Replace" screen, click the [OK] button. 2. In the confirmation screen, click [OK].
The replacement results are applied to the settings.
133 7 BASIC FUNCTIONS
7.15 Device Find/Replace
7.16 Log Output
Logs of device access with the programmable controller CPU registers and logs of SECS communication with the host can be output.
Log Output Setting
Configure the details of the logs to be output.
Common Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Configure the common settings of the log output function.
Window
GEM advanced version
[Log] [Log Output Setting] [Common Setting] tab
Displayed items
Item
Log Storage Period
Log Output
Description
Configure the number of days to store log data. The log data is compiled into time-sliced files (in increments of hours), and saved for the specified number of days. A log outputted according to FTP settings to the FTP server is not deleted using the SECS/GEM communication software.
Configure the log output destination. MELSEC-Q series · 0: CF · 1: FTP MELSEC iQ-R series · 0: SD · 1: FTP
134 7 BASIC FUNCTIONS 7.16 Log Output
Item
Description
SECS Log Setting
Select this checkbox to enable SECS log collection.
SECS Log Output
Select this checkbox to control the start or end of log collection by a trigger from the programmable controller CPU. By specifying the trigger relay, SECS log collection will be started when the specified trigger relay turns ON and will be terminated when the trigger relay turns OFF. If this item is not configured, SECS communication logs are always collected from when the SECS/ GEM communication software starts.
Output The Link Test Frame Log
Select this checkbox to save the host link test log in the SECS communication log. By specifying the trigger relay, the link test log with the host is output to the SECS communication log when the specified trigger relay turns ON and the log collection of link tests will be ended when the trigger relay turns OFF. When this item is not configured, the link test log is not output.
Programmable controller log setting
Programmable controller log output trigger
Select this checkbox to enable Programmable controller log collection.
Select this checkbox to control the start or end of log collection by a trigger from the programmable controller CPU. By specifying the trigger relay, programmable controller log acquisition will be started when the specified trigger relay turns ON and will be terminated when the trigger relay turns OFF. When the detailed programmable controller CPU log will not be collected, only the status change of the device assigned to the sending request trigger relay and reception notification trigger relay of the message is recorded. If this item is not configured, programmable controller logs are always output from when the SECS/ GEM communication software starts.
Collect The Detailed
Select this checkbox to record the status change of all relays defined to the device assignment to the
PLC Log
programmable controller log.
By specifying the trigger relay, a detailed log is output to the programmable controller log when the
specified trigger relay turns ON and will be terminated when the trigger relay turns OFF.
7
When this item is not configured, the detailed programmable controller log is not output.
135 7 BASIC FUNCTIONS 7.16 Log Output
FTP Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Configure the details for access the FTP server. By using this setting, it is possible to output logs to the FTP server. By outputting the logs to the FTP server, the number of writes to the memory card can be mitigated.
Window
[Log] [Log Output Setting] [FTP Setting] tab
Displayed items
Item
IP Address User Password Home Directory
Action After FTP Disconnection
Number of Retries After FTP Disconnection Retry Delay At FTP Disconnection
FTP Error Notification
Trigger Keep Time State Notification
Description
Configure the IP address of the FTP server.
Configure the username of the FTP account.
Configure the password of the FTP account.
Configure when the log will be output to a sub directory of the FTP account. When left blank, the logs are output under the home directory of the FTP account.
Select the operation when the connection with the FTP server has been disconnected. MELSEC-Q series · 0: Cancel log output: Logs are not output after FTP disconnection · 1: Output to CF: Logs are output to the CF card after FTP disconnection. MELSEC iQ-R series · 0: Cancel log output: Logs are not output after FTP disconnection · 1: Output to SD: Logs are output to the SD memory card after FTP disconnection.
Specify the number of retries to connect with the FTP server after FTP disconnection.
Specify the delay time for connection retries after FTP disconnection. The time is configured in increments of 10 (msec).
Select this checkbox to turn ON the notification relay to report when log output to the FTP server has failed. Furthermore, configure the device to be used as the notification relay.
Hold the trigger relay for FTP error notification for the specified time. The time is configured in increments of 10 (msec).
Select this checkbox to enable the trigger keep time. Furthermore, switch OFF the FTP error notification relay by the SECS/GEM communication software after reconnecting with the FTP server.
136 7 BASIC FUNCTIONS 7.16 Log Output
Precautions
· When a subdirectory has not been created in the FTP server, Action After FTP Disconnection results, even when an FTP subdirectory has been configured. However, the FTP error notification relay does not turn ON.
· When the MELSEC iQ-R series SECS/GEM communication software pre-installed model module is used, FTP log output uses the same network as SECS communication.
7
137 7 BASIC FUNCTIONS 7.16 Log Output
CF Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Configure the storage destination of log files to be output to the CF card.
Window
[Log] [Log Output Setting] [CF Setting] tab
GEM advanced version
Displayed items
Item
Log Output Destination Folder
Description
Configure the home directory on the CF card to output the log files.
138 7 BASIC FUNCTIONS 7.16 Log Output
User Log Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The User Log Settings tab allows you to output string data stored in the specified register as a log when the specified trigger switching ON is detected and browse data using the "Log View" screen in the setting tool.
Window
[Log] [Log Output Setting] [User Log Setting] tab
7
Displayed items
Item
User Log Setting
User Log Output Request
User Log Start Register Register Counts
Description
Select this checkbox to enable the user log setting.
Configure the user log output trigger. If the trigger is turned ON by the programmable controller CPU, and the log output ends, it is switched OFF by the SECS/GEM communication software.
Configure the start register where the data (ASCII strings) to be output to a log are to be stored.
Configure the number of registers (number of words) to be used for data storage counting. When the data does not satisfy this size, fill the terminating byte with NULL characters (0x00).
139 7 BASIC FUNCTIONS 7.16 Log Output
Display Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Configure the details to display logs on a display.
Window
[Log] [Log Output Setting] [Display Setting] tab
GEM advanced version
Displayed items
Item
View the Log in Programmable Display
Display Log Storage Period
EOL processing
Maximum characters of 1 line Maximum rows The register of top for operation (16bit)
The register of top for drawing (5448Word)
Description
Select this checkbox to view the log on the Programmable Display (GOT, etc.).
Configure the number of days to store log data to be displayed on the Programmable Display. The log data is compiled into time-sliced files (in increments of hours) and saved for the specified number of days.
Select the end-of-line processing when the number of characters per line is less than the maximum number of characters.
Configure the maximum number of characters to be displayed on one line on the Programmable Display.
Configure the maximum number of rows to be displayed on one screen on the Programmable Display.
Configure the device to be used for the operation register. The 16 continuous points from the configured device can be used as the operation register. Select "CPU-OWN" to specify an M device of the host station for the MELSEC-Q series SECS/GEM communication software pre-installed model module. For details on the operation register, see the following reference. Page 149 View the Log on Display Device (GOT)
Configure the device to be used for the display register. The 5448 continuous words from the configured device can be used as the display register. Select "CPU-OWN" to specify a D device of the host station for the MELSEC-Q series SECS/GEM communication software pre-installed model module. For details on the display register, see the following reference. Page 149 View the Log on Display Device (GOT)
Precautions
· The display log file is saved to the SD memory card when the MELSEC iQ-R series SECS/GEM communication software pre-installed model module is being used.
· When a MELSEC-Q series SECS/GEM communication software pre-installed model module is being used, the display log file is saved to the directory configured by the following setting: [CF Setting] [Log Output Destination Folder].
· When a device of this host station is used, it must be configured in advance at a row lower than a device of another station in the "I/O assignment" of the "Device Assignment Setting" screen.
140 7 BASIC FUNCTIONS 7.16 Log Output
Real Time Trace Setting
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The real-time trace function allows you to display SECS communication and device I/O information in real-time using a GOT.
Window
[Log][Real Time Trace Setting]
Displayed items
Item
Real Time Trace Setting
Start Register Counts
Trace Counts Device I/O Trace
Description
7
Select this checkbox to use the real time trace function.
Configure the start register where the data (ASCII strings) used for a real-time trace is to be stored.
Configure the number of registers (number of words) to be used for data storage counting. When the output message does not satisfy the register count, NULL characters (0x00) are stored at the message end.
Configure the number of real time traces to be output.
Select this checkbox to display the device I/O information in real time.
Precautions
In case of multi-line output of real time trace, the total number of registers to be used is calculated as [Register Counts] × [Trace Counts].
Real Time Trace Output Message List
Example of output messages of communication trace
Type
Message sending Message reception Message spool Message spool output CA-SECS start-up Connection (TCP/IP) Disconnection Communication established (COMMUNICATING) ONLINE OFFLINE Spool start Spool stop
Message example
S1,F1
SEND
S1,F1
RECEIVE
S6,F11
SPOOL
S66,F115
SPOOL OUT
CA-SECS READY
CONNECT
DISCONNECT
COMMUNICATING
ONLINE OFFLINE SPOOL ACTIVE SPOOL INACTIVE
2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100
2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100
141 7 BASIC FUNCTIONS 7.16 Log Output
Example of output messages of device I/O trace
Type
Device relay ON CA-SECS relay ON Device relay OFF CA-SECS relay OFF Registry read error Registry write error Handshake error
Message example
M101
ON(EQ)
M1024
ON(CA-SECS)
M5
OFF(EQ)
M28
OFF(CA-SECS)
D2049
READ ERROR
D16
WRITE ERROR
M512
HANDSHAKE ERROR
2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100 2008/10/21 17:06:05:100
142 7 BASIC FUNCTIONS 7.16 Log Output
Log View
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Display the log acquired from the SECS/GEM communication software pre-installed model module.
Window
[Log][Log View]
(1) (2)
7
(3)
Displayed items
Item
Find
(1)Log list (2)Data View Display Log
[Load] button
Description
All
Select to find all logs.
Period
Select to specify the period for search.
Search conditions
To find for log data that matches conditions, either select from the pulldown lists of the search conditions or enter character strings, and then click the [TOP], [Previous], or [Next] button.
[TOP] button
Move to the start of the search target.
[Previous] button
Move to the previous search target.
[Next] button
Move to the next search target.
Displays log data as a list. If the title "DATE" is clicked, the data is sorted by date in ascending or descending order. If data in the Log list is right clicked while SECS logs or user logs are displayed, the content displayed in the Data View can be selected by a shortcut menu.
Displays content of log data.
SECS Log
Select this checkbox to display SECS logs.
Programmable controller Select this checkbox to display programmable controller logs. log
User Log
Select this checkbox to display user logs.
(3)Time specification
Specify the date, hour, and minute of logs to be displayed.
[Update View] button
Import and display the updated log data from the SECS/GEM communication software pre-installed model module.
[Destination Target] button
Configure the SECS/GEM communication software pre-installed model module to import log data.
Open a saved log data file.
143 7 BASIC FUNCTIONS 7.16 Log Output
Item
[Save] button
Description
Save the log data currently displayed. The following file formats can be selected. · Binary log file (file extension: .log): The binary log data is saved as it is. Use the [Load] button on the
screen to view the log later. · Text log file (file extension: .txt): The log data is configured as a list and saved as text data. The text
data can be opened and browsed with any text editor.
Log Types
Display the correspondence of the symbols displayed in log data and log types.
Symbol
O(Output)
I(Input)
S(Send) R(Receive) U(User) M(Management)
E(Error)
Description
Log for which the SECS/GEM communication software changed the relay status Log for which the programmable controller CPU changed the relay status Message sending log Message reception log User Log Log to display the SECS status by the SECS/GEM communication software Error Log
Log Types
Programmable controller log
Programmable controller log
SECS Log SECS Log User Log SECS status message
Error Log
SECS Log
The following section shows the display of SUMMARY.
Item
S F Dev No. LEN
Description
Stream number Function number Device ID Line number Byte length
If an SECS log is selected in the Log list, the content of the SECS communication log appears in the Data View. The following section explains the operations of the Log list.
Summary display
Provides a summary view showing the data header in binary in the Data View.
Right-clickShortcut menu[Summary]
Dump display
Dumps the SECS communication data content in the Data View.
Right-clickShortcut menu[Dump]
Text display
Shows the SECS communication data content in the Data View in a tree structure.
Right-clickShortcut menu[Text]
144 7 BASIC FUNCTIONS 7.16 Log Output
Programmable controller log
The following section shows the display of SUMMARY.
Item
CPU Ch
Ex Dev No
Description
CPU No. Channel number (0: 0xFF, other than 0: Channel number for communication function) STA# Device type Device number and status (ON/OFF display)
If a programmable controller log is selected in the Log list, the content of the I/O log appears in the Data View.
User Log
The following section shows the display of SUMMARY.
Item
TYPE LEN
Description
Log type (TEXT: Text log, BINARY: Binary log) Byte length
If a user log is selected in the Log list, the content of the user log appears in the Data View. The following section explains the operations of the Log list.
Summary display
7
Provides a summary view showing the data header in binary in the Data View.
Right-clickShortcut menu[Summary]
Dump display
Dumps the user log content stored in the specified register in the Data View.
Right-clickShortcut menu[Dump]
Text display
Displays the user log content stored in the specified register in the Data field. Even when the data is long, a new line will not be created. A new line appears when "CR + LF" exists within the data.
Right-clickShortcut menu[Text]
145 7 BASIC FUNCTIONS 7.16 Log Output
SECS status message
Log to display the SECS status managed by the SECS/GEM communication software. The following table shows the item content to be displayed.
Message
Description
Notes
CIMREADY
CONNECT(Selected) DISCONNECT(NotSelected) Communicating NotCommunicating ON-LINE OFF-LINE SpoolEnabled
SpoolDisabled
SpoolActive SpoolInactive SpoolTransmitStart SpoolTransmitFailure
SpoolTransmitComplete
PurgeSpool
ControllerClock-Changed
CIM control is ready.
The line is connected. Disconnection was detected. Communication is established. Communication is disconnected. The mode transitioned to online. The mode transitioned to offline. The spool function is configured to enabled. The spool function is configured to disabled. Spooling has started. Spooling has stopped. Spool transmission has started. An error occurred during spool transmission, resulting in transmission cancellation. All spool transmission has been completed. The spool was purged.
The controller time was changed.
Output is enabled only when the SECS communication log output trigger is not used (SECS logs are always acquired). Indicates a Selected state for HSMS communication. Indicates a Not Selected state for HSMS communication. Indicates that the S1F13 transaction was successful. The ON status of the Enable spooling relay is detected.
The OFF status of the Enable spooling relay is detected.
Triggered by S6F23 (Spooled data request) reception. T3 timeout, line disconnection, etc.
Triggered by S6F23 (Spooled data request) reception or the use of the spool data discard trigger.
Precautions
The order of log output before and after a SECS status message may differ from the actual time series.
146 7 BASIC FUNCTIONS 7.16 Log Output
Error Log
Error logs are displayed in red characters. The following table shows the details of error messages.
Programmable controller CPU error messages
Message
READ_ERR(error code) WRITE_ERR(error code) Assignment invalid
Response monitoring timeout
Description
Data was not read.
Data was not written.
An area not defined in device assignments was specified in an item storage register, etc.
There was no programmable controller CPU response (OFF) to a SECS/GEM communication software trigger notification (ON) within the response monitoring timer setting, causing the trigger to be forcibly turned OFF.
Notes
An error code is added at the end of the message. An error code is added at the end of the message.
When a handshake is specified for the reception notification trigger, SECS error notification, etc.
SECS error messages
Message
Description
Notes
DM reception error
Reception error
· HSMS: Data with unknown communication level · SECS1: Checksum error*1
· SECS2: Full-queue error
DM sending error
DM was not sent.
CM sending error Sending DM creation failed (1) Sending DM creation failed (2)
CM sending error Initialization failed. Creation failed.
CPU reset is recommended.
7
This error also applies to the register read error, which is often caused by an incorrect register assignment setting.
DM sending failure
Sending Failure
The SECS/GEM communication software may be under load.
Secondary request timeout
After reception of a primary message, no secondary sending request trigger was detected within the response monitoring timer setting.
This error is not output for a secondary reception notification handshake timeout.
Reception data format error
The reception data includes an incorrect SECS header.
Data length invalid
Reception error (too long)
S9F11 sending
Incorrect format
Incorrect format
S9F7 sending, the message received from the host is different from the one configured in terms of item type, list structure, or data length.
Incorrect device ID
Incorrect device ID
S9F1 sending
Undefined SF code
Undefined SF code
S9F3/F5 sending, a message is regarded as an undefined message if the reception notification trigger option is not selected in the Message Property window.
Data error
Reception data error
This error also applies to the register write error, which is often caused by an incorrect register assignment setting.
Full SECS queue
A memory acquisition error occurred when creating a reception data storage buffer
The CPU must be reset.
Full reception queue
Full reception queue
This error may also occur even for single transactions when the software continuously receives the same message and fails to establish handshaking.
Full transmission queue
Full transmission queue
· This error may also occur even for multitransactions if sending processing is delayed due to too much load.
· No spooling is available.
Full multi-transaction queue
The multi-transaction queue for sending is full.
Message discarded because no communication has been established
The requested sending message was discarded because communication has not been established.
An attempt was made to send a message other than S1F13 before communication was established.
Message discarded because it is out A non-spooled sending message requested during spooling
of spool scope
was discarded.
Message discarded due to full spool
A spooled sending message requested during spooling was discarded because the spool is full.
· The spool must be transferred or discarded. · This error is not output during overwriting.
147 7 BASIC FUNCTIONS 7.16 Log Output
Message
Description
Notes
Message discarded because spooling A spooled sending message requested during spooling was
is disabled
discarded because spooling is disabled.
Check the Enable spooling relay. Note that the Enable spooling relay can be configured only by a non-GEM version.
Cyclic measurement cancelled
Although the cyclic message sending request trigger is ON, sending was cancelled due to an offline status, etc.
· Offline, line disconnected, spooling in progress (excluding cases where the message is a spooled message)
· An error is output periodically until either the status changes to sending enabled or the request trigger is turned OFF. (Measurement resumes once the status changes to sending enabled.)
Sending cancelled due to offline (1)
Although a message sending request trigger was detected, sending was not performed because the status was offline.
· An attempt was made to send a message other than S1F1 while offline.
· Cyclic messages are excluded.
Sending cancelled due to offline (2)
Although a message sending request trigger was detected, a message was not created since the status was offline and the message is a non-spooled message.
· When the "Spool during offline" option is enabled · Cyclic messages are excluded.
Sending cancelled due to offline (3)
Although a message sending request trigger was detected, a message was not created because the status was offline and the spooling is disabled.
· When the "Spool during offline" option is enabled · Cyclic messages are excluded.
Sending cancelled due to line disconnection (1)
Although a message sending request trigger was detected, This error is for secondary messages only. the message was not sent because the line is disconnected.
Sending cancelled due to line disconnection (2)
Although a message sending request trigger was detected, the message was not created because the line is disconnected and the message is a non-spooled message.
Cyclic messages are excluded.
Sending cancelled due to line disconnection (3)
Although a message sending request trigger was detected, a message was not created because the line is disconnected and spooling is disabled.
Cyclic messages are excluded.
Dialog interrupted due to dialog violation
A message with the response message monitoring (dialog) setting was sent, but a notification was received from the host regarding a message other than the one subject to monitoring.
The output SF is the one of the sending message with the dialog setting.
Dialog monitoring target
This error is output in combination with "Dialog interrupted due to dialog violation" or "T9 timeout error".
The SF output is the one of the monitoring target configured to dialog.
T1 timeout error
T1 timeout
Only for SECS-
T2 timeout error
T2 timeout
Only for SECS-
T3 timeout error
T3 timeout
S9F9 sending
T4 timeout error
T4 timeout
Only for SECS-
T6 timeout error
T6 timeout
Only for HSMS
T7 timeout error
T7 timeout
Only for HSMS
T8 timeout error
T8 timeout
Only for HSMS
T9 timeout error
T9 timeout
The output SF is the one of the sending message with the dialog setting.
Reception notification trigger not set
Although there is a format definition, notification of message reception is not possible since the reception notification trigger is disabled.
For primary messages, an abort is returned after detection of this error. For secondary messages, this error is not detected.
Unclear secondary reception
Abort reception (transfer continued)*2 Abort reception (transfer interrupted)*2
A secondary message that is not transaction-monitored by the SECS/GEM communication software has been received.
An abort message was received during spool transmission. An abort message was received during spool transmission.
· A T3 timeout already occurred for the secondary message.
· The SF code does not match the code of the sent primary message (the stream is different; the function is not primary message +1).
· A response was returned from the host for a primary message without a wait bit.
· The host sent a message with even-numbered functions as a primary message.
Issued when the "Abort receipt during spool transmission" setting of Common Spool Setting is configured to "Skip and continue transfer".
Issued when the "Abort receipt during spool transmission" setting of Common Spool Setting is configured to "Retain message and cancel transfer".
*1 Displayed for only the MELSEC-Q series SECS/GEM communication software pre-installed model module. *2 Appears in the non-GEM version only.
148 7 BASIC FUNCTIONS 7.16 Log Output
View the Log on Display Device (GOT)
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Using a register, display logs saved to the memory card on the display. Since the data has been displayed via a register, you do not need to configure the script in the Programmable Display. If the SECS/GEM communication software receives an operation instruction by an operation register, the logs are deployed to the display register. To display logs on the display, select the checkbox of "View the log in Programmable Display" in the Log Output Settings. Configure the devices used by the operation register and display register in the device assignment settings. The following image shows when a log is displayed on a GOT.
7
Precautions
To display a log on a GOT, a screen must be created on the GOT in advance. For the GOT drawing method, see the following reference. GT Designer3 Version1 Screen Design Manual (Fundamentals) GT Designer3 Version1 Screen Design Manual (Functions)
Operation Register List
No. Name
1
Prev_Time
2
Next_Time
3
Prev_Page
4
Next_Page
5
Top_Line
6
End_Line
7
Jump_Data
8
Jump_Line
Description
ON = Move to the previous hour. ON = Move to the next hour. ON = Move to the previous page. ON = Move to the next page. ON = Move to the top line. ON = Move to the end line. ON = Move to the specified date and time. ON = Move to the specified line.
Programmable Display Setting Operation
Bit set*1
149 7 BASIC FUNCTIONS 7.16 Log Output
No. Name
Description
9
SECS_S_Mask
10
SECS_D_Mask
ON = Display the target log. OFF = Do not display the target log.
11
PLC_Mask
12
USER_Mask
13
WRAP
ON = Wrap at the maximum number of characters. OFF = Do not wrap at the maximum number of characters.
14
CLEAR
ON = Clear the screen.
15
Info
ON: Operation error (when there is no move-destination file) OFF: Operation normal
16
Not used
Not used
*1 Turned OFF by the SECS/GEM communication software. *2 Switched ON/OFF by the SECS/GEM communication software.
Programmable Display Setting Operation
Bit invert
Bit set*1 Reference*2 Not used
150 7 BASIC FUNCTIONS 7.16 Log Output
Display Register List
No. Name
1
Log_Year
2
Log_Month
3
Log_Day
4
Log_Hour
5
Line_No
6
Not used
7
Log_Area
*1 Data format is unsigned BIN16. *2 Data format is unsigned BIN32. *3 Display by an ASCII string.
Description
Enter the year of the log to be displayed. (YYYY: 0000 to 9999)
Enter the month of the log to be displayed. (MM: 01 to 12)
Enter the day of the log to be displayed. (DD: 01 to 31)
Enter the time of the log to be displayed. (HH: 00 to 23)
Enter the line number of the jump destination.
Not used
Start register of the log display area.
Size (Word)
1
1
1
1
2 2 5440
Programmable Display Setting Operation
Read/Write*1
Read/Write*2 Not used Read*3
Precautions
7
Log_Area (log display area) does not support the new line character in text display objects. Set only single line text in each text display object.
Ex. Ex.) Display text is 100 characters, 40 lines and start is from D0 device. Text display objects that can display 100 characters are arranged as 40 units. The text display objects that can display 100 characters will be arranged into 40 items. Each register will be assigned consecutively as D0, D50, D100, D150...D1800, D1850, D1900, and D1950.
Considerations when the log output function is used
· If a large volume of logs are collected in a short interval, the control function performance of the SECS/GEM communication software may be affected. Fully take this precaution into account when collecting log data during normal operation.
· If logs are referenced, the control function performance of the SECS/GEM communication software may be affected. It is recommended to terminate log data collection (turn OFF the output trigger relay) before referencing log data.
· If logs are collected during operation of the SECS/GEM communication software, log collection may fail. In such cases, collect the logs again.
· Log data is stored on the memory card. See the log on the memory card. · Log writing occurs at an interval of 10 seconds. Logs are not output just after operation.
151 7 BASIC FUNCTIONS 7.16 Log Output
Considerations when switching the power ON or OFF
Never switch the power supply of the SECS/GEM communication software pre-installed model module OFF during log output. Perform one of the following actions before switching OFF the power supply. · Make sure that the log output bit is OFF. · Unmount the SD card of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module (by
moving the Mode switch of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module from the center to SELECT for 3 seconds or more) · Move the Mode switch of the MELSEC-Q series SECS/GEM communication software pre-installed model module from RUN to STOP, and then wait 3 seconds or more To prevent corruption of logs and spooling files, all file writing is stopped. Furthermore, perform the following actions before switching ON the power supply. · Return the Mode switch of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module to the center. · Return the Mode switch of the MELSEC-Q series SECS/GEM communication software pre-installed model module to RUN. Operation may be affected because there are limits on file access during start-up.
152 7 BASIC FUNCTIONS 7.16 Log Output
7.17 Documentation
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The definition information of the SECS/GEM communication software is output as electronic data. You can check the SECS message definitions, device assignment definitions, and other setting content as a list.
Window
[Documentation][Documentation]
7
Displayed items
Item
Folder Output ASCII NULL output
Description
Specify the folder to output the file. Select the data to output as a file. Select this checkbox to output device assignment definitions when one word was added to the NULL stopper register for an ASCII-format item for which an even number is configured for the data count.
Non-GEM version
The following files can be output by a non-GEM version.
File name
SECS Message Definition
Form Description at
csv
Output the content of SECS messages as a list.
Device assignment definition
csv
Output devices that have undergone device assignment
definition as a list.
Notes
For more details, see the following reference. Page 154 SECS Message Definition For more details, see the following reference. Page 155 Device Assignment Definition
GEM version
The following files can be output by a GEM version.
File name
Form Description at
SECS Message Definition
csv
Output the content of SECS messages as a list.
Device assignment definition
csv
Output devices that have undergone device assignment
definition as a list.
Notes
For more details, see the following reference. Page 154 SECS Message Definition For more details, see the following reference. Page 155 Device Assignment Definition
153 7 BASIC FUNCTIONS 7.17 Documentation
GEM advanced version
The following files can be output by an advanced GEM version.
File name
GEM settings
Form Description at
csv
Output GEM settings as a list.
GEM Compliant Table
csv
Output GEM performance definitions as a list.
Alarm Definition Spool Definition Variable Definition Report Definition Event Definition Limit Attribute Definition Communication State Model Control State Model Processing State Model Alarm State Model Spool State Model Limit State Model SECS Message Definition
csv
Output alarms as a list.
csv
Output spools as a list.
csv
Output variables as a list.
csv
Output reports as a list.
csv
Output events as a list.
csv
Output limit attributes as a list.
doc Output a communication state model diagram.
doc
Output a control state model diagram.
doc Output a processing state model diagram.
doc Output an alarm state model diagram.
doc
Output a spool state model diagram.
doc
Output a limit state model diagram.
csv
Output the content of SECS messages as a list.
Device Assignment Definition
csv
Output devices that have undergone device assignment
definition as a list.
Notes
Contents same as GEMALM.CSV. Contents same as GEMSPL.CSV. Contents same as VALLST.CSV. Contents same as RPTLST.CSV. Contents same as EVTLST.CSV. Contents same as LMTLST.CSV. Copy the file created in advance. Copy the file created in advance. Copy the file created in advance. Copy the file created in advance. Copy the file created in advance. Copy the file created in advance. For more details, see the following reference. Page 154 SECS Message Definition For more details, see the following reference. Page 155 Device Assignment Definition
SECS Message Definition
Output SECS messages created in transaction definitions to a .csv format file. The following section describes the keywords listed in each line of the file.
Keyword
Description
TR
Transaction information
PM
Primary message information
SM
Secondary message information
IT
Item information
154 7 BASIC FUNCTIONS 7.17 Documentation
Device Assignment Definition
Output devices configured by device assignment as a .csv file. Because the files are sorted in order of device number before output, it is possible to check for duplicate settings. The following section describes the keywords listed in each line of the file.
Keyword
PM-SND PM-RCV SM-SND SM-RCV IT SC OP CM-PM-SND
CM-PM-RCV
CM-SM-SND
CM-SM-RCV
PM-SND-INTREG CM-IT VAL*1 GEMTRG*1 STSMDL-COM*1 STSMDL-CNT*1 STSMDL-PRC*1 STSMDL-SPL*1 CCH*1 EVT-SND*1 EVT-RCV*1
Description
Control relay for sending request trigger of the primary message
Control relay for reception notification trigger of the primary message
Control relay for sending request trigger of the secondary message
Control relay for reception notification of the secondary message
Control register for item information screen
Scenario Start Request Trigger
Trigger setting of option settings
Primary message sending request trigger defined by the mapping setting function
Primary message reception notification trigger defined by the mapping setting function
Secondary message sending request trigger defined by the mapping setting function
Secondary message reception notification trigger defined by the mapping setting function
Primary message interval storage register Offset value of the mapping setting function
7
Storage register of variable
Control relay of each GEM function
State notification relay of the communication state model
State notification relay of the control state model
State notification relay of the processing state model
State notification relay of the spool state model
Register defined by variable cache settings
Control relay for sending request trigger of event definition
Control relay for reception notification trigger of event definition
*1 Output by the GEM version and GEM advanced version.
155 7 BASIC FUNCTIONS 7.17 Documentation
8 GEM Compliant Functions
8.1 GEM PERFORMANCE DEFINITION SETTING
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Configure the GEM performance definition conditions implemented by the SECS/GEM communication software. Select the checkboxes of performances to be implemented at the "GEM Performance Definition" screen.
Window
Main screen [GEM Performance] tab
Displayed items
Messages used in basic requirements of GEM
Performance
Used message Message name
Communication state model
Control state model
S6F11/12
Device process state
S6F11/12
S1F13/F14 scenario started by host
S1F13/14
Event notification
S6F5/6
S6F11/12
S6F15/16
Online check
S1F1/2
Event Report Send/Event Report Acknowledge
Event Report Send/Event Report Acknowledge
Establish Communication Request/ Establish Communication Request Acknowledge
Multi-Block Data Send Inquire/MultiBlock Grant
Event Report Send/Event Report Acknowledge
Event Report Request/Event Report Data
Are You There Request/On Line Data
Directio n
HE HE HE
HE HE HE HE
Notes
See S1F13/F14 scenario started by host, communication establishment See control (started by operator), control (started by host) Transition of control state
Process start/end, process state change
156
8 GEM Compliant Functions 8.1 GEM PERFORMANCE DEFINITION SETTING
Performance
Used message Message name
Error message
S9F1
Unrecognized Device ID
S9F3
Unrecognized Stream Type
S9F5
Unrecognized Function Type
S9F7
Illegal Data
S9F9
Transaction Timer Timeout
S9F13
Conversation Timeout
Control (started by operator)
S1F1/2
Are You There Request/On Line Data
Documentation
Messages used in additional GEM performance
Directio n
HE HE HE HE HE HE HE
Notes
Automatic SECS/GEM communication software transmission upon detection Automatic SECS/GEM communication software transmission upon detection Automatic SECS/GEM communication software transmission upon detection Automatic SECS/GEM communication software transmission upon detection Automatic SECS/GEM communication software transmission upon detection Defined by user and transmitted upon request from ladder program Implements Operator offline setting; operator local switching Supported by GEM advanced version
Performance
Used message Message name
Directio Notes n
Communication establishment
S1F13/14
Establish Communication Request/
HE
Establish Communication Request
Acknowledge
Dynamic event report setting change
S2F33/34
Define Report/Define Report Acknowledge
HE
S2F35/36
Link Event Report/Link Event Report HE
S2F37/38
Acknowledge
Enable/Disable Event Report/Enable/ HE
8
Disable Event Report Acknowledge
S2F39/40
Multi-Block Inquire/Multi-Block Grant HE
Variable data acquisition
S6F19/20
Individual Report Request/Individual HE
Report Data
Trace data acquisition
S2F23/24
Trace Initialize Send/Trace Initialize Acknowledge
HE
Supported by GEM advanced version
S6F1/2
Trace Data Send/Trace Data Acknowledge
HE
Supported by GEM advanced version
State data acquisition
S1F3/4
Selected Equipment Status Request/ HE
Selected Equipment Status Data
S1F11/12
Status Variable Namelist Request/
HE
Status Variable Namelist Reply
Alarm management
S5F1/2
Alarm Report Send/Alarm Report
HE
Acknowledge
S5F3/4
Enable/Disable Alarm Send/Enable/ HE
Disable Alarm Acknowledge
S5F5/6
List Alarm Request/List Alarm Data
HE
S5F7/8
List Enabled Alarm Request/List Enabled Alarm Data
HE
Supported by MELSEC-Q series SECS/ GEM communication software pre-installed model module
S6F11/12
Event Report Send/Event Report
HE
Acknowledge
Remote control
Requires message definition by user
Device constant
S2F13/14
Equipment Constant Request/ Equipment Constant Data
HE
S2F15/16
New Equipment Constant Send/New HE
Equipment Constant Acknowledge
S2F29/30
Equipment Constant Namelist Request/Equipment Constant Namelist
HE
S6F11/12
Event Report Send/Event Report
HE
Acknowledge
8 GEM Compliant Functions 8.1 GEM PERFORMANCE DEFINITION SETTING
157
Performance
Process recipe management
Material transfer Device terminal service Clock Limit monitoring
Spooling
Control (started by the host)
Used message
S7F17/18 S7F19/20 S7F23/24
S6F11/12 S2F17/18 S2F31/32 S2F45/46 S2F47/48 S6F11/12 S2F43/44
S6F23/24 S6F11/12 S1F15/16 S1F17/18
Message name
Delete Process Program Send/Delete Process Program Acknowledge
Current EPPD Request/Current EPPD Data
Formatted Process Program Send/ Formatted Process Program Acknowledge
Event Report Send/Event Report Acknowledge
Date and Time Request/Date and Time Data
Date and Time Set Request/Date and Time Set Acknowledge
Define Variable Limit Attributes/ Variable Limit Attribute Acknowledge
Variable Limit Attribute Request/ Variable Limit Attributes Send
Event Report Send/Event Report Acknowledge
Reset Spooling Streams and Functions/Reset Spooling Acknowledge
Request Spooled Data/Request Spooled Data Acknowledgment Send
Event Report Send/Event Report Acknowledge
Request OFF-LINE/OFF-LINE Acknowledge
Request ON-LINE/ON-LINE Acknowledge
Directio n
HE HE HE
HE HE HE HE HE HE HE
HE HE HE HE
Notes
Supported by GEM advanced version Supported by GEM advanced version Requires message definition by user
Transport event Requires message definition by user Supported by GEM advanced version Supported by GEM advanced version Inter-area transition event
Spooling stopped//transfer failure
158
8 GEM Compliant Functions 8.1 GEM PERFORMANCE DEFINITION SETTING
8.2 About State Model Management
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
Of the state models required by GEM, communication state, control state, and spooling state are managed automatically by the SECS/GEM communication software. Therefore, define the notification destination register of the default state (state arbitrarily definable by the equipment) and state number for the setting content. The current processing state of the equipment must be managed by the programmable controller CPU by the processing state model, and, in addition to the above, the setting content must define the notification content for changes to the SECS/ GEM communication software. Regardless of the state, the operation of the state model must be understood. The following section provides explanatory notes for the state model. Check the transfer operation of each model by each item. For the message content and scenario operations, see the GEM standards document.
State Model
Description
State name
Transition destination
Initial state
8
Historical selector (return to previous state)
Conditional Selector
8 GEM Compliant Functions 8.2 About State Model Management
159
8.3 GEM MODEL STATE NOTIFICATION SETTING
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The model state notification setting is used to display the model state, such as the communication state or control state, on an external display device such as a GOT. Each state is assigned to a relay device. To enable this function, select [GEM Function][Model State Notification].
Window
[GEMFunction] [Model State Notification Settings]
Displayed items
Item
Communication state model Control State Model Processing State Model
Spooling state model
Description
Select this checkbox to report the state of the communication state model. The state is reported using 8 relays from the start.
Select this checkbox to report the state of the control state model. The state is reported using 8 relays from the start.
Select this checkbox to report the state of the processing state model. The state is reported using 8 relays from the start. This model state can be output processing unit-wise as far as the processing state is concerned No. of relay devices equal to (8 items from the top × no. of processing units) are used, based on the no. of processing units set in the "Processing State Settings" screen.
Select this checkbox to report the state of the spooling state model. The state is reported using 8 relays from the start.
160
8 GEM Compliant Functions 8.3 GEM MODEL STATE NOTIFICATION SETTING
Details of state notification relays
State notification relays used in communication state model
Relay (from top)
1 2 3 4 5 6 7 8
Value
DISABLED (Communication disabled) ENABLED(Communication enabled) NOT COMMUNICATING Communication interrupted) WAIT CR FROM HOST WAIT CRA WAIT DELAY COMMUNICATING (Communication in progress) Reserved
State notification relays used in control state model
Relay (from top)
1 2 3 4 5 6 7 8
Value
OFF-LINE EQUIPMENT OFF-LINE ATTEMPT ON-LINE HOST OFF-LINE ON-LINE LOCAL REMOTE Reserved
State notification relays used in processing state model
8
Relay (from top)
Value
1
IDLE
2
PROCESSING ACTIVE
3
PROCESS
4
SETUP
5
READY
6
EXECUTING
7
PAUSE
8
Reserved
State notification relays used in spooling state model
Relay (from top)
1 2 3 4 5 6 7 8
Value
SPOOL INACTIVE(Spool stopped) SPOOL ACTIVE(Spool activity) NO SPOOL OUTPUT SPOOL OUTPUT(Spool output) TRANSMIT SPOOL PURGE SPOOL SPOOL NOT FULL SPOOL FULL(Spool full)
8 GEM Compliant Functions 8.3 GEM MODEL STATE NOTIFICATION SETTING
161
8.4 COMMUNICATION STATE MODEL MANAGEMENT
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Communication link state between host and SECS- level is managed using the following state model. Communication between the device and the host is established once the state becomes COMMUNICATING (communication in progress).
The communication state model is completely managed by the SECS/GEM communication software.
Using the communication state settings, configure the device assignment, default values of the communication state, etc. to
notify the programmable controller CPU about the current communication state.
COMMUNICATIONS
(1) ENABLED
(4) NOT COMMUNICATING (HOST-INITIATED
DISABLED
(2)
(3)
(EQUIPMENT-INITIATED
WAIT CR (10) FROM HOST
(5) (7) (8)
WAIT
WAIT CRA (6)
(12)
COMMUNICATING
(9)
(11)
No. Current state
Trigger
New state
Operation
Comments
(1)
(Enter
System initialization
COMMUNICATIONS
state)
System default state
Disabled
System default state can be either Communication DISABLED or ENABLED state
(2)
DISABLED
(Communication
disabled)
Operator switches from communication disabled to enabled
ENABLED (Communication enabled)
Disabled
SECS- communication is enabled
(3)
ENABLED
(Communication
enabled)
Operator switches from communication enabled to disabled
DISABLED (Communication disabled)
Disabled
SECS- communication is disabled
(4)
(Enter to communication Communication enabled NOT COMMUNICATING
Disabled
ENABLED)
state is activated.
(Communication interrupted)
Communication enabled state is activated during system initialization, or alternately it can be switched into by operator
(5)
(Enter equipment
initiated connect)
(Entered NOTCOMMUNICATING state)
WAIT CRA (Awaiting communication establishment request confirmation)
Communication initialization Communication delay timer is set for timeout S1F13 is sent
Communication establishment is started through equipment initiated connect
(6)
WAIT CRA
(Awaiting
S1F13 transaction failure*1
communication
establishment request
confirmation)
WAIT DELAY (Awaiting delay timer timeout)
Communication delay timer is initialized All messages awaiting transmission are removed from the queue*2
Timeout is awaited
(7)
WAIT DELAY
(Awaiting delay timer
timeout)
Communication delay timer is timed out
WAIT CRA (Awaiting communication establishment request confirmation)
S1F13 is sent
S1F14 is awaited (In some cases S1F13 may be received from the host)
162
8 GEM Compliant Functions 8.4 COMMUNICATION STATE MODEL MANAGEMENT
No. Current state
Trigger
New state
Operation
(8)
WAIT DELAY
(Awaiting delay timer
timeout)
A message other than S1F13 is received
WAIT CRA (Awaiting communication establishment request confirmation)
Message is discarded (no response) Communication delay timer is set for timeout S1F13 is sent
(9)
WAIT CRA
S1F14 with COMMACK COMMUNICATING
Disabled
(Awaiting
= 0 is received as
(Communication in progress)
communication
expected
establishment request
confirmation)
(10) (Enter host initiated connect)
(Entered NOTCOMMUNICATING state)
WAIT CR FROM HOST (Awaiting communication establishment)
Disabled
(11) WAIT CR FROM HOST S1F13 is received (Awaiting communication establishment from the host)
COMMUNICATING
S1F14 is sent with
(Communication in progress) COMMACK=0
(12) COMMUNICATING (Communication in progress)
Communication loss
NOT COMMUNICATING (Communication interrupted)
All messages awaiting transmission are removed from the queue
*1 Communication loss, response timeout, etc. *2 Messages to be transmitted from the queue are spooled in the order of creation.
Comments
It means that there is a possibility of communication establishment
Communication shall be established
S1F13 is awaited from the host
Communication is established.
Messages removed from the queue are spooled if necessary
8
8 GEM Compliant Functions 8.4 COMMUNICATION STATE MODEL MANAGEMENT
163
Communication state model setting
Configure the details of the communication state model.
Default Window
[GEMFunction] [Communication State] [Default] tab
Displayed items
Item
Default communication state
Communication establishment timeout
Description
Select the default communication state of the SECS/GEM communication software upon power. This setting is reflected in the equipment variable DefaultCommunicationsState.
Configure the timeout value for communication delay timer. Values from 1 to 240 seconds can be specified. This setting is reflected in the equipment variable EstablishCommunicationsTimeout.
State notification Window
[GEMFunction] [Communication State] [State Notification] tab
Displayed items
Item
Communication state notification
Interlock relay
Description
Set the register used by the SECS/GEM communication software to notify the current state of the communication state model to the Programmable Controller CPU. This setting is reflected in the state variable CommunicationsState. For more details of values, see the following reference. Page 198 Variables defined by default
To lock transition of the communication state and transition operations, use an interlock relay to switch this relay ON from the programmable controller CPU.
164
8 GEM Compliant Functions 8.4 COMMUNICATION STATE MODEL MANAGEMENT
State Change Window
[GEMFunction] [Communication State] [State Change] tab
Displayed items
Item
ENABLED/DISABLED
Trigger Hold Time
Description
This relay enables the Programmable Controller CPU to change the communication state of the SECS/ GEM communication software. When this setting is enabled, turn the trigger ON to configure an ENABLED state and turn the trigger OFF to configure a DISABLED state.
An ENABLED/DISABLED trigger results when the ENABLED/DISABLED relay was held for the configured time. If the "Not Monitored" checkbox is selected, ENABLED/DISABLED trigger processing is carried out without hold monitoring.
Control
Window
8
[GEMFunction] [Communication State] [Control] tab
Displayed items
Item
Communication establishment attempt
Communication establishment request Trigger Hold Time
Description
Select whether communication establishment is to be attempted automatically by the SECS/GEM communication software or upon request from the programmable controller CPU. · AUTO: SECS/GEM communication software attempts to establish communication automatically. · SEMI-AUTO: Attempted automatically by the SECS/GEM communication software only when the
Communication establishment request relay is ON. · MANUAL: Attempts to establish communication upon request from the programmable controller
CPU. Determine the value of the communication state notification register by the programmable controller CPU and switch ON the communication establishment relay defined below.
Configure the relay to notify the SECS/GEM communication software about the communication establish attempt when SEMI-AUTO/MANUAL was selected. When this relay is switched ON, the SECS/GEM communication software attempts to establish communication.
A communication establishment request trigger results when the communication establishment request relay is held for the configured time. If the "Not Monitored" checkbox is selected, Communication establishment request trigger processing is carried out without hold monitoring.
8 GEM Compliant Functions 8.4 COMMUNICATION STATE MODEL MANAGEMENT
165
8.5 CONTROL STATE MODEL MANAGEMENT
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The following state model is used by the host to manage the state of the 3 control levels (high: remote, medium: local, low: offline) of the equipment. · Remote: equipment can the controlled from host · Local: the host can access the information of the equipment, but operations are limited · Offline: the equipment cannot be controlled from the host, and access to information is also limited SECS/GEM communication software manages the control state model completely, such as device assignment for notifying the current control state to the Programmable Controller CPU, assignment of the control transition switch relay and setting of the control state default value.
CONTROL OFF-LINE
(1)
Equipment
(2)
OFF-LINE
(6) (3)
ON-LINE (7)
LOCAL
(12)
Attempt
(4)
ON-LINE
(5)
(8)
(9)
(11) HOST OFF-LINE
(10)
REMOTE
No. Current state
Trigger
(1)
(Enter CONTROL state) System initialization
New state
System default state
Operation
Disabled
(2)
(Enter OFF-LINE state) Enters offline state
OFF-LINE (Offline) Any one of these. · EQUIPMENT OFF-LINE · HOST OFF-LINE · ATTEMPT ON-LINE
Disabled
(3)
EQUIPMENT OFF-LINE Operator changes the
ATTEMPT ON-LINE
(Equipment offline)
switch to online
(Online establishment
attempt)
S1F1 is sent.
(4)
ATTEMPT ON-LINE
Any one of these.
Depends on the setting
(Online establishment
· Communication loss conditions
attempt)
· S1F1 reply timeout
· Received S1F0
Disabled
(5)
ATTEMPT ON-LINE
Expected S1F2 is
(Online establishment
received
attempt)
ON-LINE (Online)
Disabled
(6)
ON-LINE
(Online)
Operator changes the switch to offline
EQUIPMENT OFF-LINE (Equipment offline)
Disabled (Event occurrence)
(7)
(Enter ON-LINE state) Enters Online state
ON-LINE (Online) The lower state is determined based on remote/local switch setting
Disabled (Event occurrence)
(8)
LOCAL
(Local)
Operator sets the switch REMOTE
to remote
(Remote)
Disabled (Event occurrence)
166
8 GEM Compliant Functions 8.5 CONTROL STATE MODEL MANAGEMENT
Comments
System default state is set to online or offline
Equipment enters any of the lower states of the offline state in accordance with default setting
On entering the ATTEMPT ON-LINE state, S1F1 shall be sent definitely
Depending on the setting, equipment is set to offline or host is set to online.
No.(7) is entered and transition to online is notified to the host.
"Equipment offline" event occurs*1. In offline state reply to the event is discarded
"Control state local" event or "control state remote" event occurs. The actual online lower state to which the transition is done is indicated
"Control state remote" event occurs.
No. Current state
Trigger
New state
Operation
Comments
(9)
REMOTE
(Remote)
Operator sets the switch LOCAL
to local
(Local)
Disabled (Event occurrence)
"Control state local" event occurs
(10) ON-LINE (Online)
S1F15 (transition to offline) is received
HOST OFF-LINE (Host offline)
Disabled (Event occurrence)
"Host offline" event occurs
(11) HOST OFF-LINE (Host offline)
S1F17 (online transition request) is received and accepted
ON-LINE (Online)
Disabled
No.(7) is entered and transition to online is notified to the host.
(12) HOST OFF-LINE (Host offline)
Operator sets the switch EQUIPMENT OFF-LINE
to offline
(Equipment offline)
Disabled (Event occurrence)
"Equipment offline" event occurs.
*1 When there is a transaction started by the host, the SECS/GEM communication software sends an abort message after event message transaction completion.
8
8 GEM Compliant Functions 8.5 CONTROL STATE MODEL MANAGEMENT
167
Control state model setting
Configure the details of the control state model.
Default Window
[GEMFunction] [Control State] [Default] tab
Displayed items
Item
Default control state
Default setting at the time of online attempt failure
Description
Select the control state of the SECS/GEM communication software when the power is turned ON. This cannot be changed from the Programmable Controller CPU. This setting is reflected in the equipment variable DefaultControlState.
Select the default state when online transition fails. This cannot be changed from the Programmable Controller CPU. This setting is reflected in the equipment variable DefaultOfflineState.
State notification Window
[GEMFunction] [Control State] [State Notification] tab
Displayed items
Item
Control state notification
Interlock relay
Description
Set the register used by the SECS/GEM communication software to notify the current state of the control state model to the Programmable Controller CPU. This value is the state variable ControlState. For more details of values, see the following reference. Page 198 Variables defined by default
To lock transition of the control state, use an interlock relay to switch this relay ON from the programmable controller CPU.
168
8 GEM Compliant Functions 8.5 CONTROL STATE MODEL MANAGEMENT
State Change Window
[GEMFunction] [Control State] [State Change] tab
Displayed items
Item
ON-LINE/OFF-LINE
Trigger Hold Time
REMOTE/LOCAL
Trigger Hold Time
Description
Set the relay used to notify the SECS/GEM communication software about the transition to ON-LINE/ OFF-LINE from the Programmable Controller CPU. When this setting is enabled, turn the trigger ON to configure an ON-LINE state and turn the trigger OFF to configure an OFF-LINE state.
An ON-LINE/OFF-LINE trigger results when the ON-LINE/OFF-LINE relay is held for the configured time. If the "Not Monitored" checkbox is selected, ON-LINE/OFF-LINE trigger processing is carried out without hold monitoring.
Configure the relay to notify the SECS/GEM communication software from the programmable controller
CPU of a REMOTE/LOCAL switch.
When this setting is enabled, turn the trigger ON to configure a REMOTE state and turn the trigger OFF
8
to configure a LOCAL state.
A REMOTE/LOCAL trigger results when the REMOTE/LOCAL relay is held for the configured time. If the "Not Monitored" checkbox is selected, REMOTE/LOCAL trigger processing is carried out without hold monitoring.
Control Window
[GEMFunction] [Control State] [Control] tab
8 GEM Compliant Functions 8.5 CONTROL STATE MODEL MANAGEMENT
169
Displayed items
Item
Attempt ON-LINE
Online request Trigger Hold Time
Description
Select whether online establishment is to be attempted automatically by the SECS/GEM communication software or upon request from the programmable controller CPU. · AUTO: SECS/GEM communication software attempts to establish an online state automatically. · MANUAL: Attempts to establish an online state upon request from the programmable controller CPU.
Determine the value of the control state notification register by the programmable controller CPU and switch ON the online request relay defined below.
Configure the relay to notify the SECS/GEM communication software about the online establishment attempt when MANUAL was selected for "On-Line Establishment Trial". When this relay is switched ON, the SECS/GEM communication software attempts to establish an online state.
An online request trigger results when the On-Line Request relay is held for the configured time. If the "Not Monitored" checkbox is selected, online request trigger processing is carried out without hold monitoring.
170
8 GEM Compliant Functions 8.5 CONTROL STATE MODEL MANAGEMENT
8.6 PROCESSING STATE MODEL MANAGEMENT
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The processing state of the equipment is managed with the following model. When the equipment enters a PROCESS state, it indicates that the process is ready or executing. When it enters an EXECUTING state, it means that the process is running. The programmable controller CPU must manage the processing state model. Register assign or assign setting of state transition switch relay are implemented in SECS/GEM communication software to enable reception of a notification from the Programmable Controller CPU regarding the current processing state.
INIT (1) IDLE
(5)
PROCESSING ACTIVE PROCESS
(2) (6) (7)
SETUP (3)
READY
(4)
EXECUTING
(8)
PAUSE (10)
(9)
8
No. Current state
Trigger
New state
(1)
INIT
System initialization
IDLE
(2)
IDLE
Setup command is issued
SETUP
(3)
SETUP
Setup is completed and preparation for reception of start instruction is also completed
READY
(4)
READY
Start instruction (START) is received from the host or console
EXECUTING
(5)
EXECUTING
Processing operation is completed
IDLE
(6)
PROCESSING ACTIVE Stop instruction (STOP) IDLE
is received from the host
or console
(7)
PROCESSING ACTIVE Abort instruction
IDLE
(ABORT) is received
from the host or console
(8)
PROCESS
Decided to pause the process due to alarm occurrence, etc.
PAUSE
(9)
PROCESS
Pause instruction (PAUSE) is received from the host or console
PAUSE
(10) PAUSE
Resume instruction (RESUME) is received from the host or console.
PROCESS Previous state within the PROCESS
Operation
Disabled Disabled
Comments
Depends on the equipment
Depends on the equipment
Disabled
Disabled
Depends on the equipment
Depends on the equipment Depends on the equipment
The decision about this transition is normally needs support from the operator
Depends on the equipment
Lower state is the previous state before transition to PAUSE
8 GEM Compliant Functions 8.6 PROCESSING STATE MODEL MANAGEMENT
171
Process state model setting
Configure the details of the processing state model.
Default Window
[GEMFunction] [Processing State] [Default] tab
Displayed items
Item
No. of processing units
Description
Set the number of the processing units in the equipment. Up to 99 units can be set. This setting is reflected in the equipment variable ProcessPartsCount. Page 198 Variables defined by default
State notification Window
[GEMFunction] [Processing State] [State Notification] tab
Displayed items
Item
Processing Section
Processing state notification
Pre-Processing State Notification
Description
Select the processing section to configure the register for state notification.
Configure the register to notify the programmable controller CPU of the current processing state. This setting is reflected in the state variable ProcessState_part01. For more details of values, see the following reference. Page 198 Variables defined by default
Configure the register to notify the programmable controller CPU of the processing state before transition. This setting is reflected in the state variable PreviousProcessState_part01. For more details of values, see the following reference. Page 198 Variables defined by default
172
8 GEM Compliant Functions 8.6 PROCESSING STATE MODEL MANAGEMENT
State Change Window
[GEMFunction] [Processing State] [State Change] tab
Displayed items
Item
Description
State change trigger
Set the replay used by the Programmable Controller CPU to notify SECS/GEM communication software about the transition of the processing state. The processor and processing state changes are reported when the trigger was detected.
Processing Section
Configure the register to notify the SECS/GEM communication software from the programmable controller CPU of a processor number that changed its processing state. This setting is reflected in the discrete variable ProcessChangePart. For more details of values, see the following reference. Page 198 Variables defined by default
Processing State
Configure the register to notify the SECS/GEM communication software from the programmable
controller CPU of a processing state number that changed its processing state. This setting is reflected in the discrete variable ProcessChangeStatus.
8
Processing state numbers
For the processing state number to be stored to the processing state register, see the following reference.
No.*1 State/Command
Notes
1
IDLE
State variable ProcessState_part01
2
SETUP
State variable ProcessState_part01
3
READY
State variable ProcessState_part01
4
EXECUTING
State variable ProcessState_part01
5
PAUSE
State variable ProcessState_part01
32
SETUP
33
READY
34
START
35
COMPLETE
36
STOP
Setup command IDLESETUP Setup completed SETUPREADY Start instruction READYEXECUTING Processing completed EXECUTINGIDLE Stop instruction Switch to IDLE
37
ABORT
Abort instruction Switch to IDLE
38
PAUSE
39
RESUME
Pause instruction PROCESSPAUSE Resume instruction PAUSEPROCESS previous state
*1 From 6 through 31, specify any state as a user defined range.
8 GEM Compliant Functions 8.6 PROCESSING STATE MODEL MANAGEMENT
173
8.7 Alarm Definition (GEM / GEM advanced version)
Alarm notification definitions allow arbitrary definition and sending of the content of the alarm notification used by S5F1. This is completed just by controlling the alarm occurrence/recovery trigger and the register that corresponds to the prescribed alarm at the programmable controller CPU. For operations during alarm notifications, see the following reference. Page 100 Operations during Alarm Notification
Alarm List
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Displays a list of defined alarms. Up to 4096 alarms can be defined.
Window
GEM advanced version
[GEM Function][Alarm]
Operations of the Alarm List
The following section explains the operations of the "Alarm List" screen.
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Alarm Definition" screen to modify the content of the selected alarm. Add a new alarm. Copy the selected alarm, and then copy the copied alarm to the row below. Move the selected alarm.
Delete the selected alarm.
174
8 GEM Compliant Functions 8.7 Alarm Definition (GEM / GEM advanced version)
The content of the alarm list is saved to the following file. (Project save destination)\GEMALM.CSV When the alarm content is large or redundant, it is convenient to use Microsoft Excel or another external editor to modify this file. After the corresponding file is edited, the content is updated by opening the same project again.
8
8 GEM Compliant Functions 8.7 Alarm Definition (GEM / GEM advanced version)
175
Alarm Definition
Series
MELSEC-Q series MELSEC iQ-R series
Edit the alarm definition.
SECS/GEM communication software
Non-GEM version
GEM version
Window
Select an alarm in the "Alarm list" screen, right-click Shortcut menu [Edit]
GEM advanced version
Displayed items
Item
Enable Alarm
Alarm No. ALID ALCD Hexadecimal
ALTX Comment
Link Event
Alarm Occurrence
Alarm Cancel
Description
Select this checkbox to use alarms. The alarm enabled status may be switched by instruction from the host. Configure the number that corresponds to the prescribed alarm state register. (Start from 1) Configure the content of the alarm ID <ALID > related to the alarm number. Configure the content of the alarm code <ALCD > related to the alarm number. Select this checkbox to configure ALCD in hexadecimal. If this checkbox is cleared, the notation is decimal. Configure the content of the alarm text <ALTX > related to the alarm number. Configure the alarm comment. The content of the comment is not sent as an alarm message. Select an event report to send when an alarm has occurred.
Select whether to send an event report when an alarm was cancelled.
176
8 GEM Compliant Functions 8.7 Alarm Definition (GEM / GEM advanced version)
Common Alarm Settings
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Configure the common settings to control the content configured by the Alarm list.
Common Window
[GEM Function][Common Alarm][Common] tab
GEM advanced version
Displayed items
Item
Alarm Occurrence Notification Alarm Cancel Notification Alarm Status Synchronization Request
Trigger Hold Time
Alarm Processing Notification
Alarm Status Register (Start)
No. of Alarm Status Registers
8
Description
Configure the trigger relay to notify the SECS/GEM communication software of an alarm occurrence.
Configure the trigger relay to notify the SECS/GEM communication software of an alarm reset.
Configure the trigger relay to match the alarm status managed by the programmable controller CPU internally and the alarm status managed by SECS/GEM communication software internally. Upon receiving this trigger request, the alarm state managed by the SECS/GEM communication software is revised to the contents of the prescribed state register.
A trigger results when the relays configured for Alarm Cancel Notification and Alarm Status Synchronization Request were held just for the configured time. If the "Not Monitored" checkbox is selected, trigger processing is carried out without hold monitoring.
Configure the relay to report that alarm sending is being processed. Switches OFF when a secondary message of the final alarm message was received. It is possible to check that the ladder program is performing sending processing when a large number of alarms occur at once.
Configure the register to display the alarm status. This setting is reflected in the state variable AlarmsSet. For more details of values, see the following reference. Page 198 Variables defined by default
One register can manage the alarm status of 16 items. Configure the quantity of registers to be used according to the number of alarm items. Up to 256 registers can be registered (maximum alarm count is 4,096).
8 GEM Compliant Functions 8.7 Alarm Definition (GEM / GEM advanced version)
177
SECS Item Window
[GEM Function] [Common Alarm] [SECS Item] tab
Displayed items
Item
Item
Data Type Data Count Variable Length
Description
Configure the data type and data count of items used by the message. Select the data type of the item. Configure the data count of the item. Select this checkbox to configure the data count to a variable length.
Exclusion Window
[GEM Function] [Common Alarm] [Exclusion] tab
Displayed items
Item
Scenario
Enable Processing Notification Data Lock
ABORT
Description
Select the transaction in the GEM alarm scenario.
Select this checkbox to enable automated response of the selected transaction.
Configure the relay for the SECS/GEM communication software to notify the programmable controller CPU that the selected scenario is being executed.
Configure the relay to deny the above-mentioned transaction request because of equipment processing, errors, etc. When this relay is ON, secondary messages are not returned when a message related to the selected transaction is received from the host.
When the "ABORT" checkbox is selected, an S5F0 secondary message is sent.
178
8 GEM Compliant Functions 8.7 Alarm Definition (GEM / GEM advanced version)
Reply Setting Window
[GEM Function] [Common Alarm] [Reply Setting] tab
Displayed items
Item
W-bit
Description
Select this checkbox to send an S5F1 message with a W-bit. If this checkbox is cleared, the Alarm Processing Notification relay cannot be used because its original function is no longer satisfied.
Precautions
Alarm report sending (S5F1/F2)
Alarm report sending (S5F1/F2) is a reserved transaction, so transaction settings are not necessary.
8
For details on reserved transactions, see the following reference.
Page 268 List of reserved transactions and format
No. of Alarm Status Registers
When multiple registers are used, the consecutive registers from the specified start alarm status register up to the configured quantity targeted. Make sure not to overlap with any register defined in other item settings.
Editing of GEMALM.CSV
GEMALM.CSV is a text file with items delimited by commas. When editing the data, take care not to change the file format.
Furthermore, back up and store the file before modifying it.
When reporting multiple alarms simultaneously
If there are too many alarms to be reported simultaneously, some notifications to the host may be missed.
As a guideline, set up to 32 alarms to perform sending requests at one time.
8 GEM Compliant Functions 8.7 Alarm Definition (GEM / GEM advanced version)
179
8.8 Spool Function (GEM / GEM advanced version)
Messages that failed to be sent for some reason can be kept as spool messages. Spooled messages can be resent when communication is recovered. Spooled messages are stored on the memory card. For the spooling operation, see the following reference. Page 109 Spooling Operation Sequence For the operation during spool message sending, see the following reference. Page 110 Operation sequence during spool message sending
Spool list
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Shows a list of messages subject to spooling.
Window
GEM advanced version
[GEM Function][Spool]
Operations of the Spool List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Spool Definition" screen to modify the content of the selected spool. Add a new spool. Move the selected spool.
Delete the selected spool.
180
8 GEM Compliant Functions 8.8 Spool Function (GEM / GEM advanced version)
Spool Definition
Series
MELSEC-Q series MELSEC iQ-R series
Edit the spool definition.
SECS/GEM communication software
Non-GEM version
GEM version
Window
Select a message in the "Spool list" screen, right-click Shortcut menu [Edit]
GEM advanced version
Displayed items
Item
Stream/Function Transaction
Description
Select when setting spool targets by Stream/Function. Select when setting a defined transaction to be subject to spooling.
8
8 GEM Compliant Functions 8.8 Spool Function (GEM / GEM advanced version)
181
Common Spool Definition settings
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
Common Window
[GEM Function][Common Spool][Common]
GEM advanced version
Displayed items
Item
System Default Settings
Maximum No. of Spool Transmission
Maximum no. of spool items
Overwrite Spool
State Notification Register Assignment
Enable Spooling
Spooling State Notification
Description
Specify the maximum number of spool data items to be sent at once from the equipment for an S6F23 (spooled data request) from the host. To have no limit on the maximum number, set 0. The maximum number is reflected in the equipment variable MaxSpoolTransmit and can be changed by an S2F15 (new equipment variable change) from the host.
Configure the maximum number of messages to be spooled at the equipment. This setting is reflected in the equipment variable MaxSpoolCount.
Select the operation method when the maximum number of spool items is exceeded. · "0: Not performed": discard the overflow. · "1: Perform": overwrite spooled messages. This setting is reflected in the equipment variable OverWriteSpool.
Configure whether to use the spooling function. This setting is reflected in the equipment variable EnableSpooling.
This register enables the SECS/GEM communication software to notify the programmable controller CPU of spooling state. This setting is reflected in the state variable SpoollingState. For more details of values, see the following reference. Page 198 Variables defined by default
182
8 GEM Compliant Functions 8.8 Spool Function (GEM / GEM advanced version)
SECS Item Window
[GEM Function][Common Alarm][SECS Item]
Displayed items
Item
Item
Data Type Data Count Variable Length
Description
Configure the data type and data count of items used by the message. Select the data type of the item. Configure the data count of the item. Select this checkbox to configure the data count to a variable length.
Exclusion
Window
8
[GEM Function][Common Spool][Exclusion]
Displayed items
Item
Scenario
Enable Processing Notification Data Lock
ABORT
Description
Select the transaction in the GEM spool scenario. The following transactions can be selected. · S2F43: Reset Spooling Streams and Functions · S6F23: Spooled data request
Select this checkbox to enable automated response of the selected transaction.
Configure the relay for the SECS/GEM communication software to notify the programmable controller CPU that the selected transaction is being executed.
Configure the relay to deny the above-mentioned transaction request because of equipment processing, errors, etc. When this relay is ON, secondary messages are not returned when a message related to the selected transaction is received from the host.
When the "ABORT" checkbox is selected, an SxF0 secondary message is sent.
8 GEM Compliant Functions 8.8 Spool Function (GEM / GEM advanced version)
183
Important points about spooling
· If spool transmission and trace and fixed cycle sending messages are implemented at the same time, performance may drop. It is recommended that trace / fixed-cycle sending messages are stopped during spool transmission.
· Spool data is saved as files on a memory card so the data is retained even after a power reset. However, if the power is cut suddenly during spooling, the spool files may be corrupted. If the files are corrupted, spooling does not function normally. Please restart the system after deleting the SPOOL.IDX file under the root folder of the memory card. In this case, spool data cannot be recovered.
· If the "overwrite spool" is not implemented, the maximum number of spool items may be lower than the specified spool maximum due to the size of messages to be spooled. When "overwrite spool" is implemented, operations are implemented with the minimum guaranteed number of items.
· The SECS/GEM communication software does not turn OFF the sending request relay if message sending is not complete. Accordingly, describe the handshake response monitoring timer processing of the SECS/GEM communication software at the programmable controller CPU, and switch OFF the sending request trigger relay during a timeout. When the message is subject to spooling at this time, the value of the spooling state notification (SpoolingState) is active.
· While the spooling state notification (SpoolingState) is active, the SECS/GEM communication software does not send a message when the equipment attempts to send a primary message not subject to spooling. However, S1 and S9 related messages are sent.
184
8 GEM Compliant Functions 8.8 Spool Function (GEM / GEM advanced version)
8.9 PROCESS PROGRAM
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The following actions are possible: an automatic return of S7F20 (current EPPD data) for an S7F19 (current EPPD request) from the host, deletion of a process program set by an S7F17 (process program deletion command) from the host, and automatic return of S7F18 (confirmation of deletion of process program). If the process program was changed at the equipment, the host is notified of the change information of the process program by an S6F11 (event report sending). This function supports the scenario that use S7F23 (Formatted Process Program Send). In order to use an S7F3 (process program sending), define the transaction and use with the method for device association. For usage method of process programs, see the following reference. Page 248 Using the process program
Process Program Settings
Configure the details of the process program. [GEMFunction] [Process Program]
Directory
Sets the directory information and no. of directory entries that can be registered for the process program.
8
Window
Displayed items
Item
Directory Entry (Start)
Directory Information (Start)
No. Of Directory Entries
Description
Configure the start of the register to store the entry information of the process program directory. For more details of entry information, see the following reference. Page 186 Directory entry information of process program
Configure the start of the register to store the directory information. For more details of directory information, see the following reference. Page 186 Directory information of process program
Configure the number of directory entries. Up to 1024 directory entries can be configured.
185 8 GEM Compliant Functions
8.9 PROCESS PROGRAM
Directory entry information of process program
Name
USE flag DevNo
Required no. of devices
1 1
Description
0 (disabled)/1 (enabled) Device no. of the EPPD to be associated
Directory information of process program
Name
PPID ChangeStatus Host delete instruction Selection state DSNAME UDStatus RECLEN RTYPE ACK
Required no. of devices
41 1 1 1 17 1 1 1 1
Description
Process program ID 0 (no state change)/1 (create)/2 (edit)/ 3 (delete) 0 (not specified)/1 (specified) 0 (not selected)/1 (selected) Data set name 0 (none)/1 (upload)/2 (download) Discrete Maximum record length 0 (stream)/1 (discrete) ACK value during upload/download
Change notification
Configure the trigger information to report that a process program was changed or selected from the programmable controller CPU to the SECS/GEM communication software. To use the process program deletion function, select the [Enable S7F17 Scenario] checkbox, and then define the information of the device to detect notification of deletion, deletion completion, etc. by the programmable controller CPU.
Window
Displayed items
Item
Process Program Change Process Program Select Directory State Synchronization Request Trigger Hold Time
Description
Configure the trigger to report that the process program was changed at the equipment to the SECS/ GEM communication software.
Configure the trigger to report that the process program was selected at the equipment to the SECS/ GEM communication software.
Configure the trigger to request directory state synchronization to the SECS/GEM communication software.
A trigger results when the relays configured for Process Program Change, Process Program Select, and Directory State Synchronization Request were held just for the configured time. If the "Not Monitored" checkbox is selected, trigger processing is carried out without hold monitoring.
186 8 GEM Compliant Functions 8.9 PROCESS PROGRAM
Item
Enable S7F17 Scenario
Process Program Deletion Notification
Process Program Deletion Completion Notification
Trigger Hold Time
Register to Save Process Program Deletion Results
Description
Select this checkbox to enable the S7F17 (Process program deletion instruction). Configure the trigger to report that an S7F17 (process program deletion command) was received from the host to the programmable controller CPU. Configure the trigger to report that the process program was deleted to the SECS/GEM communication software.
A notification trigger results when the relays configured for Process Program Deletion Notification and Process Program Deletion Completion Notification were held just for the configured time. If the "Not Monitored" checkbox is selected, notification trigger processing is carried out without hold monitoring. Configure the register to report that the process program was deleted by a deletion command to the SECS/GEM communication software.
8
187 8 GEM Compliant Functions
8.9 PROCESS PROGRAM
SECS items
Configure the SECS-data item-format related to process programs.
Window
Displayed items
Item
Item
Data Type Data Count Variable Length
Exclusion Window
Description
Configure the data type and data count of items used by the message. Select the data type of the item. Configure the data count of the item. Select this checkbox to configure the data count to a variable length.
Displayed items
Item
Scenario
Enable Processing Notification Data lock
ABORT
Description
Select the transaction in the GEM process program scenario.
Select this checkbox to enable automated response of the selected transaction.
Configure the relay for the SECS/GEM communication software to notify the programmable controller CPU that the selected scenario is being executed.
Configure the relay to deny the above-mentioned transaction request because of equipment processing, errors, etc. When this relay is ON, secondary messages are not returned when a message related to the selected transaction is received from the host.
If ABORT option is checked, S7F0 secondary message is sent.
188 8 GEM Compliant Functions 8.9 PROCESS PROGRAM
8.10 CLOCK
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Clock function is used to synchronize internal time of the equipment with the host time. The SECS/GEM communication software registers the time data received by an S2F18 (date and time data) or an S2F31 (date and time set request) from the host to the clock data storage destination register. The time of the equipment can be synchronized with the host by changing the clock data to this time at the programmable controller CPU. When an S2F17 (date and time request) was received from the host, the clock data of the C Controller module or C intelligent function module is sent to the host by an S2F18 (date and time data) automatically. · When the equipment requests the time from the host An S2F17 (date and time request) is sent from the equipment, and the time of the host is configured to the equipment by an S2F18 (date and time data) received from the host.
Equipment
Host
S2F17(date and time request)
S2F18(date and time data)
synchronized with date and time obtained from the host
8
· When the time is designated by the host to the equipment The time of the host is received by an S2F31 (date and time set request) from the host, and the equipment sends an S2F32 (date and time set confirmation).
Equipment
Host
S2F31(date and time set request)
S2F32(date and time set Acknowledge) synchronized with date and time from the host instruction
189 8 GEM Compliant Functions 8.10 CLOCK
Clock setting
Configure the details of the clock function.
Common Window
[GEMFunction] [Clock] [Common] tab
Displayed items
Item
Clock Data Format Clock data storage destination
Clock Data Lock Relay Time Synchronization Request
Time Synchronization Notification
Description
Selects whether clock data received in SECS message is of ASCII12Byte or ASCII16Byte. This setting is reflected in the equipment variable TimeFormat.
Configure the register to notify the programmable controller CPU about the received clock data. This setting is linked to the state variable Clock. To convert received ASCII data to numerical data that the programmable controller CPU can process easily, select the "Store Clock Data In DATE Format" checkbox and select either "DATE-A" or "DATE-Q".
To lock the update of clock data, a clock-data lock relay is used, and this relay is turned ON from the Programmable Controller CPU.
Configure the relay to request sending of an S2F17 (date and time synchronization request) to the SECS/GEM communication software from the programmable controller CPU when there is a time synchronization request from the equipment to the host. It is necessary to select the checkbox in addition to "Request From Device To The Host (S2F17)" of Advanced Settings.
Configure the relay for the SECS/GEM communication software to notify the programmable controller CPU of receipt of clock data when the host request time synchronization to the equipment.
190 8 GEM Compliant Functions 8.10 CLOCK
Detail Window
[GEMFunction] [Clock] [Details] tab
Displayed items
Item
Description
Request from Equipment to Host (S2F17)
Select this checkbox to send an S2F17 (date and time synchronization request) from the equipment to the host. It is necessary to also define the Time Synchronization Request relay of the Common settings.
S9F7 transmission in
Select this checkbox when it is necessary to send a S9F7 (incorrect format) message to the host when
case of incorrect clock the received clock data is of an incorrect format.
data
Request from the Host to
Select this checkbox to receive an S2F17 (date and time synchronization request) from the host.
8
the Equipment (S2F17) Time synchronization
Select this checkbox when a time synchronization notification to the programmable controller CPU is
notification is set
necessary.
It is necessary to also define the Time Synchronization Notification relay of the Common settings.
Request from the Host to the equipment to set time (S2F31)
Select this checkbox to receive an S2F31 (date and time set request) at equipment from the host. Configure the content of the response message if the received clock data format is incorrect (Return TIACK =1 / Return ABORT / Send S9F7 / No judgment) and the content of the response message if clock data update is locked (Return TIACK = 1 / Return ABORT).
191 8 GEM Compliant Functions 8.10 CLOCK
8.11 VARIABLE SETTING
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Configure the various state variable data and equipment variables stored in the equipment. Variable data can be reported as an event report. Furthermore, it is possible to change settings via instructions from the host and report list data.
Variable list
Display the default variable stored in the SECS/GEM communication software, and a list of added user defined variables. Up to 65,535 variables can be configured.
Window
[GEMData] [Variable]
Operations of the Variable List
Operation
Right-clickShortcut menu[Modify] Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Variable Definition" screen to modify the content of the selected variable. Add a new variable. Copy the selected variable, and then copy the copied variable to the row below. Move the selected variable.
Delete the selected variable.
192 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Cache settings variables
If there are many storage registers of registered variables, and these are defined by I/O assignment, configure the cache settings to ensure performance.
Window
[GEMData] [Variable Cache]
Operating procedure 1. Select the variable cache number to be configured by "Setting". 2. Select the "Use" checkbox. 3. Configure the first register to be used and the number of registers to be used.
Precautions
Up to 32 items for variable cache can be configured.
One cache setting must be up to 4 KB (2048 registers).
However, restrict the range of cache registration to a smaller one, to secure the SECS/GEM communication software
8
operation performance.
193 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Variable definition
Configure the variables.
Basic Window
Select a variable in the "Variable list" screen, right-click Shortcut menu [Edit] [Basic] tab
Displayed items
Item
Class
Management classification
VID
Variable name Comment Unit Data type settings
Data type
SECS type Data count
Variable length
[List Setup] button
Description
Configure the variable attribute. · SV: state variable · ECV: Equipment constant · DVVAL: Discrete variable · MEMBER: variables used as list members
Displays the management classification. · System: variable defined in advance by the SECS/GEM communication software. · Equipment: newly added variable
Configure the variable ID. A unique value is set to VID in all classes except for MEMBER class.
Configure the variable name.
Configure a comment for the variable.
Select a unit for the value defined in GEM.
Configure the data type to be stored in the register. If SECS data stored in the register as a numerical value is to be sent as ASCII, the SECS/GEM communication software can automatically convert the data and send it just by setting the respective data type.
Configure the format code of SECS data based on communication specifications.
Configure the data count. The Data Count displayed differs by the configured Data Type. · BIN: Byte count · ASCII/JIS8: Character count (one-byte character) · LIST: Number of member variables configured by the list setting · Other data types: Fixed to 1
Select this checkbox to configure the data count to a variable length. The Variable Length setting is enabled when the data type is "ASCII" or "LIST". Operation when the variable length was configured is as follows. · ASCII: the size up to Null stopper of the register is the number of data items. · LIST: The number of member variables received from the programmable controller CPU is the
number of data items.
Configure the member variables. Available when the data type is "LIST". For more details, see the following reference. Page 197 List setting
194 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Item
Variable value settings
Variable Type
Variable Value Storage register
Description
Select the handling method of the value configured to "Variable Value". · Fixed value: "Variable Value" is the fixed value of the variable. This setting cannot be changed from
the programmable controller CPU or host. · Setup value: "Variable Value" is the initial value of the "Storage destination register". Applied as the
initial value when "Variable Setup" is "With Setup" of operations at start-up and the "Configuration File Browse" was set to "Tool Configuration File" when updating the SECS/GEM communication software pre-installed model module. ( Page 112 Updating the SECS/GEM communication software pre-installed model module) · Default value: "Variable Value" is the default value of the "Storage destination register".
Configure the variable value.
Configure the register to store the value of the variable. Variable Type can be configured to "Setup Value" or "Default Value".
Detail Window
Select a variable in the Variable list, right-clickShortcut menu [Edit][Details] tab
8
Displayed items
Item
Description
Has Upper limit value/Lower limit value Limit attribute setting*1
No. of limit monitoring
If the variable is data that has upper and lower limit values, select the "Upper Limit Value/Lower Limit Value Defined" checkbox, and then configure the values.
If the variable is subject to limit monitoring, select the "With Limit Monitoring" checkbox. It is necessary to click the [Limit Attribute Definition] button, and then configure the limit settings. For details of limit attribute definitions, see the following reference. Page 202 LIMIT ATTRIBUTE DEFINITION
Configure the number of limit attributes to be monitored using this variable.
Event link
Select the event to be reported to the host when the variable value crosses the region configured by the limit attribute.
*1 Handled by only the GEM advanced version.
Limit attributes can be configured for variables that satisfy all the following conditions. · At the [Basic] tab, configure [SV] for "Class" · At the [Basic] tab, configure a numeric type (BOOL, I1, I2, I4, U1, U2, U4, F4, or F8) for "Data Type" · At the [Details] tab, select the "Upper Limit Value/Lower Limit Value Defined" checkbox
195 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Precautions
If the limit monitoring function is enabled, a sampling operation of the device that is storing the variable value is performed. Pay sufficient attention to performance when using this function.
Changing default variables
· Variables with [System] as the management classification cannot be deleted. · To disable variables with [System] as the management classification, set a blank for "VID", and configure "Variable Type" to
"Fixed Value". · When changing "VID", variables subject to reports cannot have "VID" changed. Change the setting after either excluding
from reports or deleting reports. Page 206 Default Definition Reports
196 8 GEM Compliant Functions 8.11 VARIABLE SETTING
List setting
When the data type is "LIST", it is possible to add member variables to the list. It is necessary to predefine the variables to be added in the variable list. Variables that do not have the class of MEMBER can also be added to member variables. It is possible to link up to 256 member variables with a maximum of 8 levels (hierarchies) for a single list variable.
Window
Select a variable in the "Variable list" screen, right-click Shortcut menu [Edit] [List Setting] button
Operations of List Setting
Add
8
Add a member variable.
1. Select a member variable to be added by "Member variable".
2. Click the [Add] button.
When a list of variable with two or more levels is configured, return to the "Variable List" screen, select the parent list variable, and then repeat the addition procedure.
Move Up / Move Down
Move the selected variable. Right-clickShortcut menu[Move Up]/[Move Down]
Delete
Delete the selected variable. Right-clickShortcut menu[Delete]
197 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Variables defined by default
The following section shows predefined variables of the SECS/GEM communication software. These include variables independently defined by SECS/GEM communication software also.
Name
MDLN
Classi ficatio n
ECV
Description
Module name
SOFTREV
ECV
Software revision
EstablishCommunication ECV sTimeout
Attempt Communication establishment attempt timer
Format
ASCII 6Byte ASCII 6Byte U2
DefaultCommunications ECV State
Default communication state U1
CommunicationsState SV
Communication state
U1
DefaultControlState
ECV
Default control state
U1
DefaultOfflineState
ECV
Default state upon online
U1
establishment failure
ControlState
SV
Control state
U1
ProcessPartsCount
ECV
No. of processing units
U1
ProcessChangePart
DVVAL Process state change
U1
processing unit number
E30 stan dard
Variable value settings
Fixed value Can be set Fixed value Can be set Can be set
Can be set
Register notification Can be set
Fixed value Can be set
Fixed value Can be set
Register notification Can be set
Fixed value Can be set Can be set
Notes
It is defined in system default settings. It is used in S1F13 and S1F2.
It is defined in system default settings. It is used in S1F13 and S1F2.
It is defined in communication state model settings. Default value: 10s (1 to 240)
It is defined in communication state model settings. 0: DISABLED 1: ENABLED
It is defined in communication state model settings. 1: Communication disabled (DISABLED) 2: Communication interrupted (WAIT CRA/WAIT CR FROM HOST) 3: Communication interrupted (WAIT DELAY/WAIT CR FROM HOST 4: Communication in progress (COMMUNICATING) Default value: 1
It is defined in control state model settings. 1: equipment offline 2: transition to online in progress 3: host offline 4: Online Default value: 1
It is defined in control state model settings. 1: equipment offline 3: host offline Default value: 1
It is defined in control state model settings. 1: equipment offline 2: transition to online in progress 3: host offline 4: online local 5: online remote Default value: 1
It is defined in processing state model settings. Default value: 1 (0 to 99)
It is defined in processing state model settings. Programmable Controller CPU notifies the processing unit number whose state has been changed.
198 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Name
Classi ficatio n
Description
Format
E30 stan dard
Variable value settings
Notes
ProcessChangeStatus DVVAL Process state change state U1
Register reference It is defined in processing state model
Can be set
settings.
State number related to the processor
with the changed state is reported from
the programmable controller CPU
1: IDLE
2: SETUP
3: READY
4: EXECUTING
5: PAUSE
32: Setup command IDLE SETUP
33: Setup completed SETUP READY
34: Start instruction READY
EXECUTING
35: Process completed EXECUTING
IDLE
36: Stop instruction, switch to IDLE
37: Abort instruction, switch to IDLE
38: Pause instruction PROCESS
PAUSE
39: Resume instruction PAUSE
Previous PROCESS state
ProcessState_part01
SV
Current process state
U1
Register notification It is defined in processing state model
Can be set
settings.
State number related to the
corresponding processor can be
configured for notification to a register
1: IDLE
2: SETUP 3: READY
8
4: EXECUTING
5: PAUSE
PreviousProcessState_p SV art01
State prior to process state U1 change
Register notification It is defined in processing state model
Can be set
settings.
State number related to the
corresponding processor can be
configured for notification to a register
1: IDLE
2: SETUP
3: READY
4: EXECUTING
5: PAUSE
AlarmsEnabled
SV
Show the list of alarm IDs in LIST
the current alarm occurrence
state
Cannot be set
It is managed within SECS/GEM communication software. (0 to 4096)
AlarmsSet
SV
Show the list of currently
LIST
occurring alarm IDs
(Refer to Remarks) It is defined in alarm definition settings.
The occurring state details are defined in
the alarm state register.
AlarmID
DVVAL Occurred/ Cancelled Alarm ID
It is managed within SECS/GEM communication software
MaxSpoolTransmit
ECV
Maximum no. of spool
U4
transmission
Can be set
It is defined in spool settings. Default value: 1024 (0 to 4294967295, 0 means all is transmitted)
OverWriteSpool
ECV
Operation upon full spool
BOOL
Can be set
It is defined in spool settings. 0: do not spool further 1: overwrite from the oldest Default value: 0
MaxSpoolCount
ECV
Maximum no. of spool items U4
Can be set
It is defined in spool settings. Default value: 32767(1 to 4294967295)
EnableSpooling
ECV
Enable spool
BOOL
Can be set
It is defined in spool settings. 0: disable spool 1: enable spool Default value: 0
199 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Name
SpoolingState
SpoolCountActual SPoolCountTotal SpoolFullTime SpoolStartTime Clock TimeFormat ChangeECID HostChangeECID LimitsSamplingInterval EventLimit
LimitVariable TransitionType
EventsEnabled PPChangeName PPChangeStatus
PPExecName
Classi ficatio n
SV
SV SV SV SV SV ECV DVVAL DVVAL ECV DVVAL
DVVAL DVVAL
SV DVVAL DVVAL
SV
Description
Spooling state
Format
BIN
No. of actual spool messages U4
No. of cumulative spool messages
Spool full time
Spool start-up time
Current time within equipment
U4
ASCII ASCII ASCII 16/12Byte
Time data format
U1
Changed Equipment
constant ID
Equipment constant ID
changed by host
Sampling cycle for limit
U4
monitoring
Limit/Cross limit ID
VID that exceeded limit
monitoring area
Transition direction of the
BIN
monitoring scope of the
occurred limits
List of events enabled for report
Process program name changed by operator
LIST
Process program changed
U1
event contents
Process program ID of the selected Process program
LIST
E30 stan dard
Variable value settings
Notes
Register notification Can be set
Cannot be set Cannot be set Cannot be set Cannot be set Can be set
Register reference Can be set Register notification Can be set Fixed value Can be set Cannot be set
Cannot be set
Cannot be set
Cannot be set Cannot be set
Cannot be set
Cannot be set
It is defined in spool settings. 00H: spool stopped 01H: active, no input, empty spool 02H: active, spool transmission, empty spool 03H: active, purge spool, empty spool 81H: active, no output, full spool 82H: active, spool transmission, full spool 83H=active, purge spool, full spool
It is managed within SECS/GEM communication software (0 to 4294967295).
It is managed within SECS/GEM communication software (0 to 4294967295).
Format: YYYYMMDDhhmmsscc (Compliant with TimeFormat)
Format: YYYYMMDDhhmmsscc (Compliant with TimeFormat)
Time data of the SECS/GEM communication software pre-installed model module (Format: YYYYMMDDhhmmsscc)
It is defined in clock settings 0: 12 byte format 1: 16 byte format Default value: 16 byte
The format is the same as that of Equipment constant ID
The format is the same as that of Equipment constant ID
It is defined in limit monitoring settings. Default value: 5000ms (1000 to 4294967295)
It is managed within SECS/GEM communication software The format is the same as that of limit ID (list structure in case of multiple occurrence)
It is managed within SECS/GEM communication software The format is the same as that of variable ID
It is managed within SECS/GEM communication software 0: transition from downward direction to upward direction 1: transition from upward direction to downward direction
It is managed within SECS/GEM communication software.
It is managed within SECS/GEM communication software The format is the same as that of Process program ID
It is managed within SECS/GEM communication software 1: created 2: edited 3: deleted 4 to 63: held (pending)
200 8 GEM Compliant Functions 8.11 VARIABLE SETTING
Name
PPDeleteResult PPEnabled EPPD
Classi ficatio n
DVVAL
ECV
Description
Process program deletion results Effective process program
ECV
Process program directory
Format
BIN
E30 stan dard
Variable value settings
Can be set
Cannot be set
LIST
Notes
It is used in S7F18 return It is managed within SECS/GEM communication software Process program directory information
8
201 8 GEM Compliant Functions 8.11 VARIABLE SETTING
8.12 LIMIT ATTRIBUTE DEFINITION
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
If limit attributes are defined, events can be reported to the host when the variable value crosses the region configured by the limit attribute.
Limit attribute list
The list displays the defined limits. The limit attribute settings of the selected variables are displayed on the "Limit Attribute List" screen. Up to 16 limits can be configured.
Window
Select a variable in the Variable list, right-clickShortcut menu [Edit][Limit Attribute] button
Operations of the Limit Attribute List
Operation
Right-clickShortcut menu[Modify]
Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Limit Attribute Definition" screen to modify the content of the selected limit. ( Page 203 Limit attribute definition) Add a new limit. Copy the selected limit, and then copy the copied limit to the row below. Move the selected limit.
Delete the selected limit.
202
8 GEM Compliant Functions 8.12 LIMIT ATTRIBUTE DEFINITION
Limit attribute definition
Define the limit attribute.
Window
Select the limit attribute at the "Limit Attribute List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
LIMITID Comment Information Of Variable To Be Monitored Dead band
Description
Configure the management number of the limit attribute. Configure the comment of the limit attribute. The variable name, and the upper and lower values are displayed.
Configure the upper and lower limit dead-band values for limit monitoring region.
8
8 GEM Compliant Functions 8.12 LIMIT ATTRIBUTE DEFINITION
203
8.13 REPORT SETTING
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Event report data transmitted from the equipment consists of one or more reports, and a report consists of one or more collections of variables.
Report list
Display the default reports in the SECS/GEM communication software, and a list of added user reports. Up to 512 reports can be configured.
Window
[GEMData] [Report]
Operations of the Report List
Operation
Right-clickShortcut menu[Modify]
Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Report Definition" screen to modify the content of the selected report. ( Page 205 Report definition) Add a new report. Copy the selected report, and then copy the copied report to the row below. Move the selected report.
Delete the selected report.
204 8 GEM Compliant Functions 8.13 REPORT SETTING
Report definition
Define the report.
Window
Select a report at the "Report List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
RPTID Report Name Comment [Create Report] button
Create Report
Description
Configure the report ID.
Configure the report name.
Configure the comment.
Display the "Create Report" screen. For details, see the following reference. Page 205 Create Report
Configure the report content.
Up to 256 variables can be configured for one report.
8
Window
Click the [Create Report] button at the "Report Definition" screen. Or [GEM Data][Create Report]
205 8 GEM Compliant Functions 8.13 REPORT SETTING
Operations of Create Report
Add
Add a variable.
1. Select the report to be edited from "Report".
When the [Create Report] button was clicked on the "Report Definition" screen, and the "Create Report" screen was opened, the report is fixed to report selected at the "Report Definition" screen.
2. Select the variable to be added to the report by using "Variable". 3. Click the [Add] button.
Move Up / Move Down
Move the selected variable.
Right-clickShortcut menu[Move Up]/[Move Down]
Delete
Delete the selected variable.
Right-clickShortcut menu[Delete]
Default Definition Reports
The following table shows reports that are predefined in the SECS/GEM communication software.
Report name
CONTROL STATE PROCESSING PROCESSING STATE
ALARMS EQP.CONSTANT CHANGE LIMITS MONITORING PP-CHANGE PP-SELECT SPOOL ACTIVE SPOOL INACTIVE SPOOL-TRANSMIT FAILURE CLOCK
Used variable
ControlState, Clock Clock, PreviousProcessState_part01 Clock, ProcessState_part01, PreviousProcessState_part01 Clock, AlarmID, AlarmSet ChangeECID Clock, LimitVariable, EventLimit, TransitionType PPChangeName, PPChangeStatus PPExecName SpoolStartTime SpoolCountTotal Clock, SpoolCountActual, SpoolCountTotal Clock
Remarks, related events
Control state transition event Process start, completion and stop event Equipment process state transition event
Basic format of report linked to alarm Equipment constant change event Event of transition within the Limit area Process program change event Process program selection event Spooling start-up event Spooling stop event Spool transmission failure event Material transfer, terminal service event, etc.
206 8 GEM Compliant Functions 8.13 REPORT SETTING
8.14 EVENT SETTING
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Events are created by combining the timing of the event occurrence and the defined report. The event timing can be configured as the time of occurrence of an event recognized by the SECS/GEM communication software, such as online confirmation or an alarm occurrence, or an arbitrary timing from the programmable controller CPU.
Event list
Display the default variable events stored in the SECS/GEM communication software, and a list of added user defined events. Up to 512 events can be configured.
Window
[GEMData] [Event]
8
Operations of the Event List
Operation
Right-clickShortcut menu[Modify]
Right-clickShortcut menu[Insert] Right-clickShortcut menu[Duplicate] Right-clickShortcut menu[Move Up] Right-clickShortcut menu[Move Down] Right-clickShortcut menu[Delete]
Description
Display the "Event Definition" screen to modify the content of the selected event. ( Page 208 Event definition) Add a new event. Copy the selected event, and then copy the copied event to the row below. Move the selected event.
Delete the selected event.
207 8 GEM Compliant Functions 8.14 EVENT SETTING
Event definition
Define the event.
Window
Select an event at the "Event List" screen, right-clickShortcut menu [Edit]
Displayed items
Item
Enable event CEID Event name Comment Automatic event transmission
Sequencer Transmission Request
Response monitoring Response monitoring
[Create Event] button
Description
Select this checkbox to enable the event.
Configure the event ID based on communication specifications.
Configure the event name based on communication specifications.
Configure the comment.
Select this setting to set the timing of the occurrence of the event as the control event occurrence time of the SECS/ GEM communication software. The control event of the SECS/GEM communication software must be configured.
Select to set the timing of the event occurrence as the detection time of the trigger from the programmable controller CPU. The sending request trigger relay, handshake specification, and trigger hold time must be configured.
Select this checkbox to perform response monitoring of S6F11 (event report sending) to be sent. When this option is checked, W bit (response request) is added to the message to be transmitted.
Select this checkbox to detect whether the secondary message was received normally. If the handshake unit of "Sequencer Transmission Request" is configured to "Handshake (for each message)", configure a relay that is different from the sending request trigger.
Display the "Create Event" screen. For details, see the following reference. Page 209 Create Event
208 8 GEM Compliant Functions 8.14 EVENT SETTING
Create Event
Configure the report to be sent by the event. Up to 64 reports can be configured for one event.
Window
Click the [Create Event] button at the "Event Definition" screen. Or [GEM Data][Create Event]
Operations of Create Event
Add
Add a report.
8
1. Select the event to be configured the report by using "Event".
When the [Create Event] button was clicked on the "Event Definition" screen, and the "Create Event" screen was opened, the
event is fixed to the selected event of the "Event Definition" screen.
2. Select the report to be configured to the event by using "Report".
3. Click the [Add] button.
Move Up / Move Down
Move the selected variable.
Right-clickShortcut menu[Move Up]/[Move Down]
Delete
Delete the selected variable.
Right-clickShortcut menu[Delete]
209 8 GEM Compliant Functions 8.14 EVENT SETTING
Events defined by default
The following table shows events that are predefined in the SECS/GEM communication software.
Event name
EQUIPMENT OFF-LINE CONTROL STATE LOCAL
CONTROL STATE REMOTE
PROCESSING STARTED PROCESSING COMPLETED
PROCESSING STOPPED
PROCESSING STATE SETUP PROCESSING STATE READY PROCESSING STATE EXECUTING PROCESSING STATE IDLE PROCESSING STATE PAUSE ALARM DETECTED
ALARM CLEARED
EQUIPMENT CONSTANT CHANGE LIMIT ZONE TRANSITION
PROCESS PROGRAM CHANGE PROCESS PROGRAM SELECTED MATERIAL RECEIVED MATERIAL REMOVED SPOOLING ACTIVATED SPOOLING DEACTIVATED SPOOL TRANSMIT FAILURE MESSAGE RECOGNITION
Trigger
Automatic (ON-LINE->OFF-LINE) Automatic (OFF-LINE->ON-LINE, REMOTE>LOCAL) Automatic (OFF-LINE->ON-LINE, LOCAL>REMOTE) Automatic (->EXECUTING) Automatic (COMPLETE)
Automatic (STOP)
Automatic (->SETUP) Automatic (->READY) Automatic (->EXECUTING) Automatic (->IDLE) Automatic (->PAUSE) Automatic (ALARM n occurred)
Automatic (ALARM n cancelled)
Automatic (Equipment constant change) Automatic (Transition within LIMIT area)
Automatic (Process Program change) Automatic (Process Program selection) Relay request Relay request Automatic (SPOOL INACTIVE->SPOOL ACTIVE) Automatic (SPOOL ACTIVE->SPOOL INACTIVE) Automatic (SPOOL transmission failure) Relay request
Link report and remarks
Control state report Control state report
Control state report
Process report Process report (enabled only for transition based on command) Process report (enabled only for transition based on command) Processing state report Processing state report Processing state report Processing state report Processing state report Alarm report (defined only for alarms required by event) Alarm report (defined only for alarms required by event) Equipment constant change report Limit transition report (defined for each limit variable) Process program change report Process program selection report Time report Time report Spool start report Spool stop report Spool transmission failure report Time report
210 8 GEM Compliant Functions 8.14 EVENT SETTING
8.15 DYNAMIC SETTING CHANGE
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The SECS/GEM communication software can change settings dynamically from the host by using the following messages. · S2F33 (Define Report) · S2F35 (Link Event Report) · S2F37 (Enable/Disable Event Report) · S2F43 (Reset Spooling Streams and Functions (RSSF)) · S2F45 (Define Variable Limit Attributes) · S5F3 (Enable/Disable Alarm Send) Content for which settings have been changed dynamically from the host can be saved to the SECS/GEM communication software pre-installed model module and acquired and referenced by the setting tool.
Check the [GEM Function][Create Dynamic Configuration File] option to store dynamic setting changes in the SECS/GEM communication software.
Window
[GEMFunction] [Acquire Dynamic Configuration File]
8
Operating procedure 1. Enter the IP address, user, and password of the SECS/GEM communication software pre-installed model module. 2. Select the checkboxes of the files to be acquired from the SECS/GEM communication software pre-installed model
module.
3. Click the [Capture] button.
8 GEM Compliant Functions 8.15 DYNAMIC SETTING CHANGE
211
8.16 EQUIPMENT CONSTANT
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Configure the necessary settings to change equipment variables (ECV) from the host and report changes of equipment variables from the equipment to the host.
Change from device
Configure the setting to notify the SECS/GEM communication software from the programmable controller CPU of a change of the equipment constant.
Window
[GEMData] [Device Constant] [Change From Device] tab
Displayed items
Item
Device constant change trigger
Trigger Hold Time
Device constant change ID notification
Description
Configure the relay to notify the SECS/GEM communication software from the programmable controller CPU of a change of the equipment variable. The SECS/GEM communication software switches OFF the equipment variable change trigger.
A notification trigger results when the register configured for the Device Constant Change was held for the configured time. If the "Not Monitored" checkbox is selected, notification trigger processing is carried out without hold monitoring.
Configure the equipment constant change ID notification register to store the variable ID of the changed constant. Before a trigger notification, it is necessary to configure the variable ID at the programmable controller CPU.
212
8 GEM Compliant Functions 8.16 EQUIPMENT CONSTANT
Change from host
Configure the settings when the equipment constant is changed from the host.
Window
[GEMData] [Device Constant] [Change From Host] tab
Displayed items
Item
Description
Enable S2F15 scenario
Device constant change trigger
Select this checkbox to change the equipment constant from the host.
Defines the relay used by SECS/GEM communication software to notify the Programmable Controller CPU that S2F15 (New Equipment Constant Send) is received.
Device constant
Configure the register to store the variable ID of the changed constant.
change ID
No. of Device
Configure the number of equipment variables that can be changed at one time by an
notification
constant change ID S2F15 (new equipment variable change) from the host.
notifications
Up to 32 items can be configured.
8
Data lock
To block changes of equipment variables from the host, switch ON the data lock relay from the programmable controller CPU. Select the "ABORT" checkbox to return an abort message.
Required Quantity of Device Constant Change ID Notification Registers
The required quantity of registers is found by the following formula: 2 start items (number of changes n, overall result) + (device constant change ID notification quantity × 2) However, when the data type of ECID (equipment constant ID) is [U4], the formula is as follows: 2 start items (number of changes, overall result) + (equipment variable change ID notification quantity × 3) The data type of the ECID can be checked at the [SECS item] of the "Detailed Setting" screen. ( Page 216 SECS items)
(1)
A
(2)
(3)
(4)
B
(3)
(4)
A: Start register B: No. of Notifications Of Device Constant Change ID (1) Number of changes n (2) Overall result (0: normal / -1: error) (3) Equipment constant ID (4) Results
Precautions
The changed equipment constant is not saved to the memory card of the SECS/GEM communication software pre-installed model module. Please assign the Equipment constant to the File register if required to save.
8 GEM Compliant Functions 8.16 EQUIPMENT CONSTANT
213
8.17 ADVANCED SETTINGS
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Make settings required to implement the various scenarios defined in GEM.
GEM advanced version
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 multi-block inquiry (S6F5) during event transmission
Treat single block data ID as Zero length item Enable multi-block inquiry of the host (S2F39)
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.
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.
214 8 GEM Compliant Functions 8.17 ADVANCED SETTINGS
Limit monitoring
The SECS/GEM communication software configures the sampling cycle to monitor the limits of variables.
Window
[GEMData] [Details] [Limit Monitoring] tab
Displayed items
Item
sampling period
Description
Configure the cycle to monitor devices that store variable values. The sampling cycle can be configured from 1000 through 4294967295 ms. This setting is reflected in the equipment variable LimitsSamplingInterval.
8
215 8 GEM Compliant Functions
8.17 ADVANCED SETTINGS
SECS items
Configure the SECS-data item-format used by the SECS/GEM communication software.
Window
[GEMData] [Details] [SECS Item] tab
Displayed items
Item
Item
Data Type Data Count Variable Length
Description
Select an item to be defined. Select the data type of the item. Configure the data count of the item. Select this checkbox to configure the data count to a variable length. Configuring a variable length enables 0 length reception.
Default data type of SECS items
The following table shows default formats by item.
Item
VID UNITS ECID ECNAME SVID SVNAME CEID RPTID CEED DATAID DATALENGTH TRID DSPER TOTSMP REPGSZ SMPLN LIMITID MEXP
Description
Variable ID Unit Equipment constant ID Equipment constant name State variable ID State variable ID Acquired event ID Report ID Trace YES/NO code Data ID Total no. of data bytes Trace request ID Data acquisition time Total sample count Report group size Sample number Limit ID Message SxFy to be received
Data type
U2 ASCII 16Byte U2 ASCII 32Byte U2 ASCII 32Byte U2 U2 BOOL U2 U2 U2 ASCII 8Byte U2 U2 U2 BIN ASCII 6Byte
216 8 GEM Compliant Functions 8.17 ADVANCED SETTINGS
Dynamic setting exclusion
This setting is used to enable host to notify Programmable Controller CPU that event report pertaining to the equipment etc. is subjected to dynamic changes, and in order to enable Programmable Controller CPU to prohibit host from introducing dynamic changes.
Window
[GEMData] [Details] [Dynamic Configuration Exclusion] tab
Displayed items
Item
Scenario
Description
Select a scenario.
The following scenarios can be selected.
· S2F33: Specified report
· S2F35: link event report
· S2F37: enable/disable event report
Enable
· S2F45: variable limit attribute definition Select this checkbox to enable dynamic configuration exclusion control of scenarios.
8
Processing notification
Configure the relay for the SECS/GEM communication software to notify the programmable controller CPU that processing is occurring for each scenario.
Data lock
To lock changes when a change notification of a dynamic setting is received from the host, the data lock relay is used, and this relay is turned ON from the Programmable Controller CPU. Lock cannot be enabled after receiving the change notification message from the host. The lock should be turned ON in advance based on the equipment state. Select the "ABORT" checkbox to return an abort message.
217 8 GEM Compliant Functions
8.17 ADVANCED SETTINGS
Data acquisition exclusion
Configure to notify the programmable controller CPU that data, such as equipment variables, is being collected from the host to the equipment and to prohibit data collection by the host from the programmable controller CPU.
Window
[GEMData] [Details] [Data Acquisition Exclusion] tab
Displayed items
Item
Scenario
Enable Processing notification Data lock
Description
Select a scenario. The following scenarios can be selected. · S2F23: Trace condition setting · S6F15: Event report request · S6F19: Individual report request · S1F3: Specified device state request · S1F11: State variable name list request · S2F13: Equipment constant request · S2F29: Equipment constant name list request · S2F47: Variable limit attribute request
Select this checkbox to enable data collection exclusion control of scenarios.
Configure the relay for the SECS/GEM communication software to notify the programmable controller CPU that processing is occurring for each scenario.
Select this checkbox to turn the data lock relay ON from the programmable controller CPU when locking data collection from the host. Lock cannot be enabled after receiving the acquisition message from the host. The lock should be turned On in advance based on the equipment state. Select the "ABORT" checkbox to return an abort message.
218 8 GEM Compliant Functions 8.17 ADVANCED SETTINGS
DVVAL
Configure the conditions to disable the variables of the DVVAL class.
Window
[GEMData] [Details] [DVVAL] tab
Displayed items
Item
Description
DVVAL Disable Settings Always Enabled
Select to have the variables of the DVVAL class always enabled. Actual data is sent when sending an S6F11/S6F16/S6F20.
Enabled only During Event Report Occurrence
Select to have the variables of the DVVAL class enabled only for S6F11 sending. When reporting in S6F16 and S6F20, send it as a 0 length item.
Individually Specify The Select to specify enable/disable for registers individually and dynamically for variables of the DVVAL
Enable/Disable
class.
Registers
The first word of the specified register is used as the enable/disable register for all user-defined variables that specify the DVVAL class.
8
The actual data is stored in the first + one word.
The Enable/disable register specifies "1" If the variable is valid, and "0" from the Programmable
Controller CPU if it is disabled.
219 8 GEM Compliant Functions
8.17 ADVANCED SETTINGS
Reply Setting
Set the W-bit of S6F1 message.
Window
[GEMData] [Details] [Reply Setting] tab
Displayed items
Item
W-bit
Description
Select this checkbox to send an S6F1 message with a W-bit.
220 8 GEM Compliant Functions 8.17 ADVANCED SETTINGS
8.18 GEM COMPLIANT TABLE
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Configure whether to comply with the items of the basic requirements and additional performance of GEM. This setting is applied to the GEM compliant table that is output by the documentation function. GEM compliant table is created based on the functions specified in "GEM performance definition" screen and based on contents specified in the original GEM compliant table.
Window
[Documentation] [GEM Compliant Table]
8
Select the checkboxes of compliant items. To update and retain details displayed on "GEM performance definition" screen as it is, press [Retain performance] button.
8 GEM Compliant Functions 8.18 GEM COMPLIANT TABLE
221
9 SECS/GEM Communication Software
Knowledge
This section describes the points and knowledge to conveniently use SECS/GEM communication when using SECS/GEM communication software.
9.1 Checking that start-up of the SECS/GEM
communication software completed
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
In the case of a ladder program of a programmable controller CPU, always first make sure that the [CIM Control READY] relay that reports from the SECS/GEM communication software is ON after starting the SECS/GEM communication software. When the start-up process of the SECS/GEM communication software finishes, the CIM Control READY relay switches ON. A handshake with SECS/GEM communication software cannot be used until this relay switches on.
Usage method
To use notification of the CIM control ready relay, it is necessary to configure the relay to report. ( Page 82 CA Status) After the SECS/GEM communication software starts, first make sure that the CIM control ready relay is ON. A handshake with SECS/GEM communication software cannot be used until the [CIM Control READY] notification relay turns ON.
9.2 Checking the SECS line state
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The connection state of the SECS communication line is reported by the Disconnected relay. This relay turns OFF when the line is connected and turns ON when the line is disconnected. In the case of HSMS communication, the TCP/IP communication line is established, the "select" control procedure is completed via a HSMS message, and then a line connection is created by the Selected state. In the case of SECS- communication, a line connection is created when the RS-232C line is completely opened.
Usage method
To use notification of the Disconnected relay, it is necessary to configure the relay to report. ( Page 82 CA Status)
Precautions
The line connection state of the SECS communication line can be checked by the Disconnected relay. In the case of HSMS communication, a line connection state is not formed by just a TCP/IP line connection.
222
9 SECS/GEM Communication Software Knowledge 9.1 Checking that start-up of the SECS/GEM communication software completed
9.3 Checking the registration state of the SECS/GEM
communication software license
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The SECS/GEM communication software license is pre-installed on the SECS/GEM communication software pre-installed model module, but the license is erased when the SECS/GEM communication software pre-installed model module has been initialized. In such a case, you must use the license file stored on the product CD-ROM to register the license again. If the license state notification function is used, an automatic stop of the SECS/GEM communication software due to a license registration error can be detected in advance.
Usage method
To use notification of the license state, it is necessary to configure the relay and register to report. ( Page 96 Version Information) Configuring the setting makes it possible to check the following states.
License state
Version Information License Registration
License Matching
Notification content
The version of the SECS/GEM communication software is stored as an ASCII character string (null termination). Five words are used.
The registration state of the license file is reported by relay. 0: No registration 1: Registration
The validity of the license file is reported by relay. 0: Non-genuine license 1: Genuine license
When the License Registration and License Matching relays are both ON, a genuine license has been registered. Whether a genuine license has been registered can be determined by the [License Matching] relay.
9 SECS/GEM Communication Software Knowledge 9.3 Checking the registration state of the SECS/GEM communication software license
223
9.4 Sending and receiving messages
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The SECS/GEM communication software sends and receives SECS messages by handshakes of trigger relays from the Programmable Controller CPU and the data register. The format of messages to be sent and received, sending and receiving trigger relays, and mapping of sending and receiving message items with storage registers must be defined in advance using the setting tool. Understand the basic structure of SECS message sending and receiving by the SECS/GEM communication software before using the message sending and receiving function.
Usage method
Receiving SECS messages
When an SECS message is received from the host, the SECS/GEM communication software stores the received data in the prescribed register mapped to the corresponding message item, and then the receiving notification trigger relay configured for the corresponding message is switched on. The Programmable Controller CPU detects that a message was received by the receiving notification trigger being switched on, and then extracts the received data from the register. Next, the receiving notification trigger is switched off, and the SECS/ GEM communication software is informed that receipt is complete.
Programmable Controller CPU
Register
SECS/GEM communication software
Host
Receiving process
Ó
Ò
Sending process
Ø Ö
Ô Õ
Receiving process ×
No. Description
The SECS/GEM communication software receives a SECS message The received data is stored in the register specified by the item property definition of the message (Page 55 Item Information) The reception notification trigger relay of the programmable controller CPU specified by the message property definition is switched ON (Page 52
Message Information) The programmable controller CPU detects the message reception by the reception notification trigger relay switching ON Received data is read from the register After the received data is read, the reception notification trigger relay is switched OFF The programmable controller reports receipt completion to the SECS/GEM communication software
The reception notification trigger relay is configured at the "Primary message information" screen or "Secondary message information" screen. Select the "Reception Notification Trigger" checkbox, and then configure the notification destination. ( Page 52 Message Information)
224
9 SECS/GEM Communication Software Knowledge 9.4 Sending and receiving messages
Sending SECS messages
When an SECS message is sent from programmable controller CPU to the host, the sent data is stored in the prescribed
register mapped to the corresponding sending message item, and then the sending request trigger relay configured for the
9
corresponding message is switched ON.
The SECS/GEM communication software detects that the transmission request trigger relay is on, extracts the data of the
corresponding message item from the configured prescribed register, creates an SECS message, and then sends the
message to the host according to the SECS protocol. After sending, the transmission request trigger relay is switched off, and
the Programmable Controller CPU is notified of the completion of sending.
Programmable Controller CPU
Register
SECS/GEM communication software
Host
Sending process
Receiving process
Õ
Ö
Ò
Ô Ó Sending process Ø
×
No. Description
The sent data is stored in the register specified by the item property definition (Page 55 Item Information) The sending request trigger relay specified by the message property definition is switched ON (Page 52 Message Information) The SECS/GEM communication software detects storage of sent data to the register from the sending request trigger relay of the programmable
controller CPU switching ON The SECS/GEM communication software reads the sent data from the register of the programmable controller CPU The SECS/GEM communication software constructs a SECS message based on the imported data, and then sends it to the host The sending request trigger relay of the programmable controller CPU switches OFF Sending completion is reported to the programmable controller CPU by the sending request trigger relay switching OFF
The sending request trigger relay is configured at the "Primary message information" screen or "Secondary message information" screen. Select the "Transmission Request Trigger" checkbox, and then configure the notification destination. ( Page 52 Message Information)
· Configure the transmission request trigger hold time at the message settings screen of the scenario explorer. The SECS/GEM communication software confirms that the time trigger relay configured here is ON before it recognizes that the relay is ON.
· To notify of an error during SECS communication, configure it at the [SECS Error Notification Setting] tab of the "Option Setting" screen. Select the checkboxes for information to be reported, and then configure the notification destination. ( Page 82 CA Status) In the case of a sending failure, select the [Sending failure] checkbox, and then configure the relay for reporting.
9 SECS/GEM Communication Software Knowledge 9.4 Sending and receiving messages
225
Important points regarding message sending and receiving handshakes
· When sending consecutive messages, make sure that the sending request trigger relay of the previous message is OFF before switching ON the sending request trigger relay of the next message.
· Set a 20 ms trigger hold time for the transmission request trigger of the secondary message after receipt of the primary message. This allows the SECS/GEM communication software to be notified that the primary message receiving notification trigger relay is off before the notification that the transmission request trigger relay of the secondary message is on.
· When sending has failed, the sending request trigger relay is switched OFF. The sending-failed relay switches ON. The programmable controller CPU must not only switch OFF the sending request trigger relay, it must also monitor that the sending failure relay is ON.
226
9 SECS/GEM Communication Software Knowledge 9.4 Sending and receiving messages
9.5 Sending alarm messages (S5F1)
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
When an alarm message (S5F1) is sent from the Programmable Controller CPU, the SECS/GEM communication software notifies the host of the alarm message automatically simply by Alert Status and a handshake operation of Alert Set/Reset Notification, without defining multiple alarm messages as transactions.
Usage method
Alarm information definitions
Alarms to be disclosed by the equipment are defined by the setting tool in advance. Each alarm is managed by a unique identifier and alarm number appended to each alarm. The SECS/GEM communication software and Programmable Controller CPU transfer the alarm state by setting the "Alarm No." as a key. The alarm information is configured as shown below. · Non-GEM version: configured at the "Alarm Settings" screen. ( Page 102 Alarm Settings) · GEM version and advanced GEM version: configured at the "Alarm Definition" screen. ( Page 176 Alarm Definition)
Alarm notification settings
Configure the handshake to report the alarm.
Setting item
Alarm Notification Setting*1 Alarm Set Notification Alarm Reset Notification Alarm Status (Start) Number Of Alarm Status
Setting content
Select the checkbox. Configure the relay to report the alarm occurrence. Configure the relay to report the alarm reset. Specify the first register of alarm status information to retain the alarm status. Specify the size of the alarm status information by word count. Because alarm statuses are retained by a bit map, one word retains 16 alarm statuses.
*1 Configure the non-GEM version only.
Handshakes are configured as shown below. · Non-GEM version: configured at the "Alarm Notification Setting" screen. ( Page 103 Alarm Notification Setting) · GEM version and advanced GEM version: configured at the "Alarm Settings" screen. ( Page 177 Common Alarm
Settings)
9 SECS/GEM Communication Software Knowledge 9.5 Sending alarm messages (S5F1)
227
Alarm status
The alarm information retains the alarm states as bits. Each word retains 16 alarm statuses, and the alarm Status 0 and 1 indicate reset and occurrence, respectively.
Register b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
+0W +1W +2W +3W
No.16 No.32 No.48 No.64
No.15 No.31 No.47 No.63
No.14 No.30 No.46 No.62
No.13 No.29 No.45 No.61
No.12 No.28 No.44 No.60
No.11 No.27 No.43 No.59
No.10 No.26 No.42 No.58
No.9 No.25 No.41 No.57
No.8 No.24 No.40 No.56
No.7 No.23 No.39 No.55
No.6 No.22 No.38 No.54
No.5 No.21 No.37 No.53
No.4 No.20 No.36 No.52
No.3 No.19 No.35 No.51
No.2 No.18 No.34 No.50
No.1 No.17 No.33 No.49
Alarm report procedure
The following diagram shows the sequence of reporting the alarms of Alarm No. 10 (alarm 10) and Alarm No. 20 (alarm 20). In the case of an alarm reset, the alarm status is set to 0 (reset), and then Alarm Reset Notification is switched ON.
Programmable Controller CPU
SECS/GEM communication software
Host
No.10 Bit ON No.20 Bit ON
Alarm status
Alarm occurrence notification trigger relay ON
Alarm occurrence notification trigger relay OFF
Alarm in processing notification relay ON
Alarm 10 report sending (S5F1)
Alarm 10 report confirmation (S5F2)
Alarm 20 report sending (S5F1)
Alarm 20 report confirmation (S5F2)
Alarm in processing notification relay OFF
Precautions
· When multiple alarms are reported by the set/reset notification triggers simultaneously, the alarms are sent in order from the alarm with the lowest alarm number.
· Considering the load of the number of alarms to be reported simultaneously, set the number of alarms to the lowest value possible.
228
9 SECS/GEM Communication Software Knowledge 9.5 Sending alarm messages (S5F1)
9.6 Using the spool function
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Of the messages to be reported to the host, the spool function temporarily saves messages that must not be lost due to communication failure at the equipment, and then reports the saved messages to the host when communication is restored. Configure messages that must not be lost (primary messages) to be subject to spooling. When a message subject to spooling fails to be sent, the message is saved in the spool queue. Once communication is restored, the message saved in the spool queue is sent back or discarded by a Spooled data request (S6F23) from the host.
Operation
The following figure shows the spooling operation sequence. Both Message 1 and Message 2 are configured for spooling.
Programmable Controller CPU
SECS/GEM communication software
Host
Message 1 transmission request trigger ON
Sending failure
Spool output relay ON
Message 2 transmission reque trigger ON Message 2 transmission request trigger OFF
Messages subject to spooling are saved to the CF card/SD card
Messages subject to spooling are saved to the CF card/SD card
Spooling data request (S6F23) Spooling data request response
Spool output relay OFF
Message 1 sent Message 1 sent response
Message 2 sent Message 2 sent response
9 SECS/GEM Communication Software Knowledge 9.6 Using the spool function
229
Usage method (non-GEM version)
Configuring messages for spooling
Configure messages subject to spooling at the [Spool Message Settings] tab of the "Spool Settings" screen. ( Page 108 Spool message settings) Select a message to be subject to spooling from the pull-down list of [Message selection] and click the [Add] button to configure the selected message for spooling.
Configuring the spooling function
Configure the spooling function at the [Common Spool Definition Settings] tab of the "Spool Settings" screen. ( Page 106 Common Spool Definition settings)
Turning spooling on or off
Configure the setting to enable or disable the spooling function at the [Control Request] tab of the "Option Setting" screen. ( Page 85 Control Request) To toggle spooling at the equipment, select the [Turn spooling on/off] checkbox, and then configure the relay to turn spooling on or off. The spool is OFF or ON when the relay is OFF or ON, respectively. If the "Turn spooling on" checkbox is not selected, the spool is always active.
Spooling actions
Configure the Spool Outputting Relay at the [CA Status] tab of the "Option Setting" screen. Select the "Spool Outputting Relay" checkbox, and then configure the notification destination. ( Page 82 CA Status)
Spooling data request from Programmable Controller CPU
Configure the Spool Request Relay at the [Control Request] tab of the "Option Setting" screen. ( Page 85 Control Request) Spooling data can also be sent to the host or discarded by operations via trigger relays from the Programmable Controller CPU. If the "Spool Output Request" checkbox is selected, and a trigger relay is configured, spooling data transfer to the host is started when the trigger relay is on. The SECS/GEM communication software switches off the trigger relay. If the "Discard Spooled Data" checkbox is selected, and a trigger relay is configured, spooled data is discarded when the trigger relay is on. The SECS/GEM communication software switches off the trigger relay.
230
9 SECS/GEM Communication Software Knowledge 9.6 Using the spool function
Usage method (GEM version and GEM ADVANCED version)
Configuring messages for spooling
9
Configure messages subject to spooling at the "Spool List" screen. Double-click a row inserted by using the shortcut menu of
the Spool List to display the "Spool Definition" screen, and then define the messages subject to spooling. ( Page 180
Spool list)
Configuring the spooling function
Configure the spooling function at the [Common] tab of the "Spool Settings" screen. ( Page 182 Common)
Turning spooling on or off
Configure the setting to enable or disable the spooling function at the [Common] tab of the "Spool Settings" screen. If "1:
Enable" is selected for "Enable Spooling", the spool is active. ( Page 177 Common)
9 SECS/GEM Communication Software Knowledge 9.6 Using the spool function
231
9.7 Changing the communication settings from the
ladder program
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
You can change the SECS communication settings via a handshake with the SECS/GEM communication software. Use this procedure when changing the communication settings from the equipment.
Usage method
Communication settings change handshake settings
Configure the handshake interface for a communication setting change at the "Communication Setting By PLC" screen. ( Page 63 Communication Setting by PLC) Select the "Communication Setting by PLC" checkbox, specify the setting request trigger, and then configure the storage address of each communication setting. IP addresses use four words. For details of IP addresses made up of four words, see the following reference. Page 118 IP address information The SECS/GEM communication software changes the communication settings when the setting request trigger is on, and then switches off the setting request trigger. Note that changes to the communication settings are applied the next time the SECS/GEM software is started. When SECS/GEM communication software is started, the communication setting information set in the SECS/GEM communication software pre-installed model module is stored in each piece of information of the communication settings.
Considerations
· Whether the settings are HSMS or SECS-, they are determined by "Port Type" at the "Communication Setting" screen displayed by selecting [Settings] [Communication Setting] in the menu.
· The communication settings are applied the next time the SECS/GEM software is started.
232
9 SECS/GEM Communication Software Knowledge 9.7 Changing the communication settings from the ladder program
9.8 Using the mapping function
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
For example, host command sending messages (S2F41) have different parameter (CPNAME, CPVAL) numbers and targets due to the remote command (RCMD), even when the message structure is the same. If the mapping function is applied to these messages, message sending request trigger relays and reception notification trigger relays of each parameter of key items and offsets for control registers of message items can be configured in one transaction definition. Therefore, the reference destination or storage destination of parameters can be changed by the values of particular key items.
Example of locations for applying mapping function · Mapping host command sending messages (S2F41) by remote command · Mapping the data of discrete variable data sending messages (S6F3) to message data by load port
Usage method
Configure messages for command mapping in the mapping settings, and then configure command parameters.
Mapping settings
Mapping settings can be configured at the "Command Setting" screen. ( Page 120 Command Setting) Under "Message", select the message to be command mapped from the pull-down list. Under "Key Item", select the item to be the mapping key from the pull-down list. When offsets will be applied to secondary messages as well, select the "Use the same offset for secondary messages" checkbox.
Parameter settings (mapping settings by parameters of key items)
At the "Parameter Setting" screen, configure offsets message sending request trigger relays, reception notification trigger relays, and offsets for control registers of message items for each parameter of key items. ( Page 121 Parameter setting)
9 SECS/GEM Communication Software Knowledge 9.8 Using the mapping function
233
Usage example
The host controls the equipment using the four host command sending messages (S2F41) described below. Each message has different command parameters <CPNAME> and <CPVAL> for each remote command <RCMD>. A remote command <RCMD> is set as a key item, and reception notification trigger relays, sending request trigger relays, and offsets of control registers are mapped to each remote command <RCMD>.
Board retrieval message
The equipment retrieves the board of the specified slot from the carrier placed in the specified load port, and then sets the board in the specified equipment processing unit. The message has three parameters
Message format
<HCS> <L, 2> 1. ASCII <RCMD> 2. <L, 3>
1. <L, 2> 1. ASCII <CPNAME1> 2. U2 <CPVAL1>
2. <L, 2> 1. ASCII <CPNAME2> 2. U2 <CPVAL2>
3. <L, 2> 1. ASCII <CPNAME3>
2. U2 <CPVAL3>
Item value
LOAD
PORT 1 to 2 SLOT 1 to 4 PNO 1 to 2
Notes
Board retrieval command Number of parameters
Load port number parameter name Load port number
Slot number parameter name Slot number
Equipment processing unit number parameter name Equipment processing unit No.
Processing-start message
The equipment performs processing using the specified temperature and pressure parameters at the processing unit specified by the host. The message has three parameters.
Message format
<HCS> <L, 2> 1. ASCII <RCMD> 2. <L, 3>
1. <L, 2> 1. ASCII <CPNAME1>
2. U2 <CPVAL1> 2. <L, 2>
1. ASCII <CPNAME2> 2. U2 <CPVAL2> 3. <L, 2> 1. ASCII <CPNAME3> 2. U2 <CPVAL3>
Item value
START
PNO 1 to 2 TEMP 0 to 800 PRESS 2000 to 8000
Notes
Processing-start command Number of parameters
Equipment processing unit number parameter name Equipment processing unit No.
Temperature parameter name Temperature
Pressure parameter name Pressure
234
9 SECS/GEM Communication Software Knowledge 9.8 Using the mapping function
Processing-stop message
The equipment stops current processing at the processing unit specified by the host.
The message has one parameter.
9
Message format
Item value
Notes
<HCS> <L, 2> 1. ASCII <RCMD> 2. <L, 1>
1. <L, 2> 1. ASCII <CPNAME1>
2. U2 <CPVAL1>
STOP
PNO 1 to 2
Processing-stop command Number of parameters
Equipment processing unit number parameter name Equipment processing unit No.
Board withdrawal message
The equipment withdraws the board of the processing unit specified by the host to the specified slot of the carrier of the specified load port. The message has three parameters.
Message format
<HCS> <L, 2> 1. ASCII <RCMD> 2. <L, 3>
1. <L, 2> 1. ASCII <CPNAME1> 2. U2 <CPVAL1>
2. <L, 2> 1. ASCII <CPNAME2> 2. U2 <CPVAL2>
3. <L, 2> 1. ASCII <CPNAME3>
2. U2 <CPVAL3>
Item value
UNLOAD
PORT 1 to 2 SLOT 1 to 4 PNO 1 to 2
Notes
Board withdrawal command Number of parameters
Load port number parameter name Load port number
Slot number parameter name Slot number
Equipment processing unit number parameter name Equipment processing unit No.
9 SECS/GEM Communication Software Knowledge 9.8 Using the mapping function
235
Command mapping setting example
Definitions of messages
· Define the transactions of base host command sending messages (S2F41). · Because the number of parameters is variable, the number of parameters in the list is defined by a variable length list. · Because the maximum number of parameters is three, three parameter lists are defined.
Definitions of command mapping by parameters of key items
· Use the mapping setting function to specify the remote commands <RCMD> of the host command sending messages (S2F41) for the keywords of message mapping. Because receiving data of primary messages and return data of secondary messages are both subject to mapping, specify "Use the same offset for secondary messages".
· Specify the item value of <RCMD> to the parameter, and then specify the sending request trigger relays and reception notification trigger relays of messages and offsets for the command registers of message items.
Setting example for host command sending message (S2F41) definitions
The following section shows a setting example for host command sending messages (S2F41) and an example of command
mapping by remote command.
Message format
<HCS> <L, 2> 1. ASCII <RCMD> 2. <L, 3>
1. <L, 2> 1. ASCII <CPNAME1> 2. U2 <CPVAL1>
2. <L, 2> 1. ASCII <CPNAME2> 2. U2 <CPVAL2>
3. <L, 2> 1. ASCII <CPNAME3> 2. U2 <CPVAL3>
Data type
ASCII U2
ASCII U2
ASCII U2
ASCII U2
Data count
16 1
16 1
16 1
16 1
Control register
R2500 R2509
R2510 R2519
R2520 R2529
R2530 R2539
Command mapping setting example
Item value of remote command (RCMD)
LOAD START STOP UNLOAD
Primary message reception notification trigger relay
M160 M162 M164 M166
Secondary message sending request trigger the relay
M161 M163 M165 M167
Message data control register offset
0 100 200 300
236
9 SECS/GEM Communication Software Knowledge 9.8 Using the mapping function
9.9 Using the conversion table function (table
conversion)
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Table conversion definitions are used to switch to the relevant data during message transmission between SECS message items and control registers data. For example, an ASCII character string of the remote command of host message sending (S2F41) can be converted automatically to code easily processed by the Programmable Controller CPU.
Usage method
Add a conversion table at the "Conversion Table List" screen, and then configure a conversion table to be used at the "Item Information" screen.
Adding a conversion table
Configure the conversion table settings at the "Conversion Table Setting" screen. (Page 124 Conversion Table Setting,
Page 125 Conversion Table Setting)
Setting item
Conversion Definition Table Name Comments SECS Data Type PLC Data Type Data Counts
Default (SECS Data)
Default (PLC Data)
Setting content
Select "Table". Enter a conversion table name. An arbitrary comment can be entered. Specify the data type of the SECS item. Specify the data type stored in the Programmable Controller CPU. Specify the number of characters when the storage type is ASCII. For other types, set 1. Specify the data to be configured to an SECS item when conversion data that matches the conversion table was not found. Specify the data to be stored in the storage register of the Programmable Controller CPU when conversion data that matches the conversion table was not found.
Configure the conversion data at the "Conversion Data Setting" screen. ( Page 126 Conversion Data Setting)
Specification of table conversion
Specify a table added at the "Conversion Table List" screen by "Data Type" of the control register at the "Item Information"
screen. ( Page 55 Item Information)
The function is also used when messages are sent
9 SECS/GEM Communication Software Knowledge 9.9 Using the conversion table function (table conversion)
237
9.10 Using the conversion table function (format
conversion)
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Format conversion definitions are used to change data stored in control registers to data that follow format definitions and send the data as an SECS message.
Usage method
Add a conversion table at the "Conversion Table List" screen, and then configure a conversion table to be used at the "Item Information" screen.
Adding a conversion table
Configure the format conversion settings at the "Conversion Table Setting" screen. (Page 124 Conversion Table Setting,
Page 125 Conversion Table Setting)
Setting item
Conversion Definition Table Name Comments SECS Data Type PLC Data Type Data Counts
Setting content
Select "Format". Enter a conversion table name. An arbitrary comment can be entered. Specify the data type of the SECS item. (Specify ASCII.) Specify the data type stored in the Programmable Controller CPU. Specify the number of characters when the storage type is ASCII. For other types, set 1.
Configure the formatting at the "Format conversion definition setting" screen. ( Page 128 Format conversion definition setting)
Format conversion specification
Specify a table added at the "Conversion Table List" screen by "Data Type" of the control register at the "Item Information"
screen. ( Page 55 Item Information)
The format conversion function can be checked in advance. You can check whether the format of the specified format conversion is correct by using the data conversion simulator function at the "Format Conversion Definition Setting" screen. Enter the data before conversion into the "Register Input Data" field, and then select the data format of this data for "Input Form". Click [Conversion] button to display the editing result.
238
9 SECS/GEM Communication Software Knowledge 9.10 Using the conversion table function (format conversion)
9.11 Using the conversion table function (index
conversion)
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Index conversion definitions are used to send floating-point number data stored as integers in control registers as a decimalpoint format ASCII string by an SECS message.
Usage method
Adding a conversion table
Configure the index conversion settings at the "Conversion Table Setting" screen. (Page 124 Conversion Table Setting, Page 125 Conversion Table Setting) When adding a table, select "Index", and then configure "Index" and "Number of digits of integer section" to the number of decimal places and number of digits of the integer section, respectively.
Specifying index conversion
Specify a table added at the "Conversion Table List" screen by "Data Type" of the control register at the "Item Information" screen. ( Page 55 Item Information)
You can convert indexes using the format conversion function as well. The same functions as index conversion can be used by the format of format conversion.
If the example above is listed by the format of format conversion, the result is "%9.2f". The total number of characters including the decimal point is "9", and the number of decimal places is "2".
9 SECS/GEM Communication Software Knowledge 9.11 Using the conversion table function (index conversion)
239
9.12 Remote command control using the selection list
function
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
Use the selection list function to select items to be sent within the limit of the defined message structure or distinguish only items received in messages to change the item list number by the conditions.
Usage example
Sending only disabled parameters during host command confirmation message (S2F42) sending
Use the selection list to return only disabled parameters of the parameters (<L, 2 <CPNAME/><CPVAL/>>) received by a host command sending message (S2F41) such as with a host command confirmation message (S2F42). Configure disabled parameters of the host command confirmation message (S2F42) to the selection list, and then configure each disabled parameter below to the selection register. The SECS/GEM communication software sends only parameters with a value other than zero configured to the selection register during message sending. The following table shows the configuration of the host command confirmation message (S2F42) format.
Message format
<HCA> <L, 2> 1. BIN <HCACK>
2. <L, 3> 1. <L, 2> 1. ASCII <CPNAME1> 2. U2 <CPACK1>
2. <L, 2> 1. ASCII <CPNAME2> 2. U2 <CPACK2>
3. <L, 2> 1. ASCII <CPNAME3> 2. U2 <CPACK3>
Item
Notes
Host command parameter confirmation code
Invalid parameter list Invalid parameter 1 Invalid parameter name 1
Invalid parameter 2 Invalid parameter name 2 Invalid parameter reason 2 Invalid parameter 3 Invalid parameter name 3 Invalid parameter reason 3
0: confirmation (command was executed) 1: command cannot be confirmed 2: currently cannot be executed 3: at least one parameter is invalid 4: confirmed (the command was executed, and confirmation has been reported by an event) 5: denied (already requested) 6: this object does not exist
1: parameter name does not exist 2: invalid as a parameter value specified by the parameter name 3: not a format of a parameter value specified by the parameter name >3: equipment specific definition
240
9 SECS/GEM Communication Software Knowledge 9.12 Remote command control using the selection list function
Received parameters are distinguished upon receipt of a host command sending message
(S2F41)
When there is a parameter list that differs by remote command, such as with a host command sending message (S2F41), it is
9
possible to send and receive messages by simply defining one message that includes all parameter elements without defining
messages for each remote command if the selection list function is used.
By configuring the selection register for each parameter list, and furthermore specifying a selection keyword for each
parameter name of each parameter list, whether the parameter names of the received parameters match the keywords
specified for each parameter list is sent back to each selection register.
When there was a match, 1 is returned. When there is no match, 0 is returned.
It is possible to conserve data storage space because message definition is concluded by a single item and the assignment is
completed only by the data storage area of the necessary parameter element count.
Usage method
Configuring selection lists
Select the "Select List" checkbox for the new list of the parameter list. The following section is an example of the case of a host command confirmation message (S2F42).
9 SECS/GEM Communication Software Knowledge 9.12 Remote command control using the selection list function
241
Configuring selection registers
Configure "Select Register" for each parameter list.
In the case of a sending message, configure as shown below at the programmable controller CPU.
Sending message
In case of a register
In the case of a relay
Sending target
Not 0
ON
Not sending target
0
OFF
In the case of a reception message, the SECS/GEM communication software configures in the following manner.
Reception message
Received Not received
In case of a register
1 0
In the case of a relay
ON OFF
The following section is an example of the case of a host command confirmation message (S2F42).
Configuring selection key items
Configure the fixed value and selection key item for the parameter name. If a parameter that matches this fixed value is received, 1 is stored in the selection register of the new parameter list. It is necessary to configure the selection list and selection register in advance to use the selection key item. The following section is an example of the case of a host command sending message (S2F41).
Ladder program processing can be reduced by using both the mapping and selection list / selection register function.
242
9 SECS/GEM Communication Software Knowledge 9.12 Remote command control using the selection list function
9.13 Synchronizing the clocks of the equipment and
host
9
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Three time synchronization scenarios can be used through settings.
GEM advanced version
Time synchronization scenarios
Time request from equipment to host
Scenario
S2F17 (Date and time request)
Function
A date and time request message (S2F17) is sent from the equipment, and the host time is received by a date and time data message (S2F18) from the host. The time received from the host can be stored in the register.
Time request from host to equipment
Scenario
S2F17 (Date and time request)
Function
A date and time request message (S2F17) is received from the host, and the equipment time is sent by a date and time data message (S2F18) from the equipment. The return of the time to the host can be reported by the time synchronization notification relay.
Time set instruction from host to equipment
Scenario
S2F31 (Date and time set request)
Function
The host time is received by a date and time set request message (S2F31) from the host, and the equipment sends a date and time set confirmation message (S2F32). The synchronization of the time by the instruction from the host can be reported by the time synchronization notification relay. The time received from the host can be stored in the register.
Usage method
In the case of the MELSEC-Q series SECS/GEM communication software pre-installed model module
The clock of the C Controller module can be changed to the time of the received item <TIME>. However, because the time zone of CPU No. 1 is followed for a multi-CPU system, change the time of CPU No. 1 by the programmable controller CPU. The setting to change the clock of the C Controller module to the time of <TIME> is configured at [Control 2] of the "Option setting" screen. ( Page 77 Control 2) If the "Change C Controller's Clock Upon S2F31/S2F18 Receipt" checkbox is selected, the clock of the C Controller module is changed automatically to the date and time of the item <TIME> received by an S2F18 (date and time data) or S2F31 (date and time setting request) message from the host.
In the case of the MELSEC iQ-R series SECS/GEM communication software pre-installed model module
The clock of the C intelligent function module cannot be changed to the time received by item <TIME>. Because the time zone of the CPU module (CPU No.1 for a multi-CPU system) is followed, change the time of the CPU module by the programmable controller CPU.
If a date and time request message (S2F17) is received from the host, the SECS/GEM communication software returns the date and time of the SECS/GEM communication software pre-installed model module automatically.
9 SECS/GEM Communication Software Knowledge 9.13 Synchronizing the clocks of the equipment and host
243
9.14 Transitioning to a communication state
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
The communication state is managed according to the communication model state of GEM. The following three control methods can be selected by SECS/GEM communication software.
Control method
AUTO
SEMI-AUTO
MANUAL
Function
The SECS/GEM communication software controls the communication state automatically according to the communication state model of GEM.
The SECS/GEM communication software controls the communication state automatically only while the communication establishment request relay is ON.
A communication establishment request message (S1F13) is sent when triggered by the communications establishment request relay switching ON. If a communication establishment request confirmation message (S1F14) is received, the state transitions to a communication establishment state. The SECS/GEM communication software switches OFF the communications establishment request relay.
Usage method
Switching communication on and off
Operator actions switch communication on and off. Configure the setting from the screen displayed by the [State Change] tab of the "Communication State Settings" screen. ( Page 165 State Change) Select the "ENABLED/DISABLED" checkbox, and then configure the communication on/off switching relay. Communication is on or off when the relay is on or off, respectively.
Communication state control settings
Configure the setting at the [Control] tab of the "Communication state settings" screen. ( Page 165 Control) Select the control method. With a setting other than AUTO, configure the communication establishment request relay.
The communication state can be saved in a state variable in the settings at the [State Notification] tab of the "Communication State Settings" screen.
244
9 SECS/GEM Communication Software Knowledge 9.14 Transitioning to a communication state
9.15 Transitioning to a control state
Series
MELSEC-Q series MELSEC iQ-R series
SECS/GEM communication software
Non-GEM version
GEM version
9
GEM advanced version
The control state is managed according to the control model state of GEM. The following two control methods can be selected by SECS/GEM communication software.
Control method
AUTO
MANUAL
Function
The SECS/GEM communication software controls the control state automatically according to the control state model of GEM.
An online confirmation request message (S1F1) is sent when triggered by the online request relay switching ON. If an online data message (S1F2) is received, the state transitions to an online state. The SECS/GEM communication software switches OFF the online request relay.
Usage method
Control state switching by the operator
Configure the setting at the [State Change] tab of the "Control State Settings" screen. ( Page 169 State Change) Select the checkbox of the switching functions to be used, and then configure the switching request trigger relays. Operator actions control the switch from online to offline, and online local and online remote.
Configuring the control state switching control
Configure the setting at the [Control] tab of the "Control State Settings" screen. ( Page 169 Control) Select the control method. When MANUAL is selected, configure the On-Line Request trigger relay.
The control state can be set in a state variable in the settings at the [State Notification] tab of the "Control State Settings" screen. If the automatic event sending function of GEM is used, the host can be notified of the control state via an event when transitioning the control communication state.
9 SECS/GEM Communication Software Knowledge 9.15 Transitioning to a control state
245
9.16 Configuring collected events
Series
SECS/GEM communication software
Non-GEM version
GEM version
MELSEC-Q series
MELSEC iQ-R series
Events are made up of report lists, and reports are made up of variable lists. Both are configured by the setting tool. Events and reports are identified by event IDs and report IDs.
GEM advanced version
V(#1)
CEID
RPTID(#1) RPTID(#2)
V(#2) V(#n)
RPTID(#n)
CEID: Event ID RPTID: Report ID V: Variables
There are three variable (V) types: state variables (SV), dispersal variables (DV), and equipment constants (ECV), which are configured by the setting tool.
ECV
V
SV
DV
Usage method
Configuring variables
Variables disclosed by the equipment are configured by the setting tool. Double-click a row inserted by [Insert] of the shortcut menu of the "Variable List" screen to display the "Variable Definition" screen, and then configure the settings. (Page 192 Variable list, Page 194 Variable definition)
Configuring reports
Double-click a row inserted by [Insert] of the shortcut menu of the "Report List" screen to display the "Report Definition" screen, and then configure the settings. (Page 204 Report list, Page 205 Report definition) To create a report, click [Create Report] button in the "Report Definition" screen, and then create the report at the "Create Report" screen. ( Page 205 Create Report) For variables, select the variable to be added from the "Variables" pull-down list of the "Create Report" screen, and then click the [Add] button.
Configuring events
Double-click a row inserted by [Insert] of the shortcut menu of the "Event List" screen to display the "Event Definition" screen, and then configure the settings. (Page 207 Event list, Page 208 Event definition) To create an event, click [Create Event] button in the "Event Definition" screen, and then create the event at the "Create Event" screen. ( Page 209 Create Event) For the report, select the report to be added from the [Reports] pull-down list of the "Create Event" screen, and then click the [Add] button.
246
9 SECS/GEM Communication Software Knowledge 9.16 Configuring collected events
Event notification method
Automatic and manual notifications can be selected at the "Event Definition" settings screen.
· Automatic notification: If "Automatic Event Transmission" is selected, and a GEM automatic notification time is selected via
9
the pull-down list just below, the selected event is reported to the host at the specified timing.
· Manual notification (sending via a trigger instruction from a Programmable Controller CPU): If "Sequencer Transmission
Request" is selected, and the transmission request trigger is configured, the host is notified of the corresponding event
when the transmission request trigger is on. The trigger is switched off after the SECS/GEM communication software
reports to the host. (When a handshake has been selected)
The SECS/GEM communication software processes the following event functions automatically. · A report or event can be also generated dynamically by an instruction from the host. · The event report or individual report requested by the host is sent back automatically.
9 SECS/GEM Communication Software Knowledge 9.16 Configuring collected events
247
9.17 Using the process program
Series
SECS/GEM communication software
Non-GEM version
GEM version
GEM advanced version
MELSEC-Q series
MELSEC iQ-R series
The GEM advanced version of the SECS/GEM communication software provides functions that assist the management of the process program directory (PPID list). The three helper functions are as follows. · Response to process program deletion command (S7F17)*1 · Automatic response to current EPPD request (S7F19) · Sending of process program change event (S6F11) from equipment *1
*1 Manage the process programs by the equipment application.
Example of management by the host
Equipment
Host
S7F19 (Current EPPD Request) S7F20 (Current EPPD Data)
S7F17 (Delete Process Program Send) S7F18 (Delete Process Program Acknowledge)
S7F23 (Process Program Send) S7F24 (Process Program Acknowledge)
S7F25 (Process Program Request) S7F26 (Process Program Data)
Host Equipment
Equipment action
S7F19 (Process program directory request)
The process program directory is sent back to the host. The following information is returned. · List of the process program names (PPID) retained by the equipment
S7F17 (Process program deletion instruction)
S7F23 (Process program sending)
S7F25 (Process program request)
Deletes the process program requested (PPID).
Reports the received process program to the equipment.*1 The process program requested (PPID) is sent back to the host.*1
*1 Define the transaction, and process via equipment application.
248
9 SECS/GEM Communication Software Knowledge 9.17 Using the process program
Example of management by the equipment
9
Equipment
Host
S6F11 (Process Program Change Notification) S6F12 (Prosess Program Change Confirmation)
S7F23 (Process Program Send) S7F24 (Process Program Acknowledge)
S7F25 (Process Program Request) S7F26 (Process Program Data)
Equipment operation
Change of process program
Equipment Host
S6F11 (Event report: Change of process program)
Upload of process program to host
S7F23 (Process program sending)
Download of process program from host
S7F25 (Process program request)
*1 Define the transaction, and process via equipment application.
Description
When a process program is created, modified, or deleted at the equipment, the host is notified of the change of the process program via an event. The notification contains the following information. · Process program name (PPID) · Changed state (creation/modification/deletion)
The process program retained at the equipment is uploaded to the host.*1
The process program is obtained from the host.*1
9 SECS/GEM Communication Software Knowledge 9.17 Using the process program
249
Usage method
Directory settings
The directory of the process program (EPPD) is configured by the setting tool. Configure the settings at the [Directory] tab of the "Process program settings" screen. ( Page 185 Directory) Configure the number of directory entries, and the start register for the directory entry and directory information.
Directory entry table
inDfiorermctaotriyonen(#tr1y) inDfiorermctaotriyonen(#tr2y) inDfiorermctaotriyonen(#tr3y)
USE flag Direcfitrosrtyreingfiosrtmeration
PPID (#1) ChangeStatus (#1)
inHsotrsutcdtieolnet(io#n1) Selection state (#1)
DSNAME (#1) UIDStatus (#1)
RECLEN (#1) RTYPE (#1)
ACK (#1)
Directory entry information
For the directory entry (start), configure the first register of the directory entry information table. The directory entry information table holds the entry (first register) of each directory information item and defines consecutively the number of directory entries set by "No. Of Directory Entries". The following section shows the structure of the directory entry information.
Item
USE flag
Directory information first register
Word count
1
1
Description
0: not used 1: used
First register of directory information linked to the corresponding entry
The following table shows a directory entry table with three directory entries. The first register of the directory entry table is configured in "Directory Entry (Start)".
Offset
+0W
+2W
+4W
Directory entry table
Directory entry information 1
Directory entry information 2
Directory entry information 3
USE flag Directory information first register USE flag Directory information first register USE flag Directory information first register
Description
1 (use) Directory information 1 first register 1 (use) Directory information 2 first register 1 (use) Directory information 3 first register
250
9 SECS/GEM Communication Software Knowledge 9.17 Using the process program
Structure of directory information
The following section shows the structure of each directory information item.
Directory information of the amount specified by the number of directory entries is assigned.
9
The entry of each directory information item is linked and defined by each directory entry of the directory entry information
table.
The following directory information items must be initialized when the equipment is started.
The current process program ID retained by the equipment is set to PPID.
Item
PPID ChangeStatus
Host deletion instruction Selection state DSNAME UIDStatus
RECLEN RTYPE ACK
Word count
41 1
1 1 17 1
1 1 1
Description
Process program ID
0: no change 1: creation 2: modification 3: deletion
0: no instruction 1: instruction
0: no selection 1: selected Data set name*1
0: none 1: upload 2: download*1 Directory maximum record length*1
0: stream 1 = discrete*1 ACK during upload/download*1
*1 Items reserved for future functions. Initialize using "0" at equipment startup processing.
9 SECS/GEM Communication Software Knowledge 9.17 Using the process program
251
Directory request from host
When a current EPPD request message (S7F19) was received from the host, the SECS/GEM communication software creates a current EPPD data message (S7F20) from the current directory information content, and then sends it to the host automatically.
Directory deletion request from host
Configure the handshake to delete the process program of the PPID specified by the host at the [Change notification] tab of the "Process Program Settings" screen. ( Page 186 Change notification) Select the "Enable S7F17 Scenario" checkbox, and then configure the notification destination trigger and storage register.
Handshake methods
When a process program deletion instruction message (S7F17) has been received from the host, the SECS/GEM communication software configures [Deletion instruction] for the directory information of the corresponding process program, and then switches ON the Process Program Deletion Notification. When this relay is ON, the programmable controller CPU deletes the process program it was instructed to delete. The result of the deletion is set to the register to save process program deletion results. Next, the process program deletion notification trigger is switched OFF, and the process program deletion completion notification trigger is switched ON. The SECS/GEM communication software receives that the process program deletion completion notification is ON, sends a process program deletion confirmation message (S7F18) message to the host, and then switches OFF the process program deletion completion notification.
Notification of process program change from the equipment
Configure the notification to the host that the process program was changed at the equipment at the screen of the [Change Notification] tab of the "Process Program Settings" screen. ( Page 186 Change notification) Specify the notification destination using "Process Program Change".
Handshake methods
When the process program has been changed at the equipment, the change status is configured for [Change Status] of the corresponding directory information, and the process program change trigger relay is switched ON. The SECS/GEM communication software sends a process program change notification (S6F11) to the host, and then switches OFF the process program change trigger relay.
Notification of process program selection at the equipment
Configure the notification to the host that the process program was selected at the equipment at the screen of the [Change Notification] tab of the "Process Program Settings" screen. ( Page 186 Change notification) Specify the notification destination using "Process Program Select".
Handshake methods
When a process program has been selected at the equipment, the selection status is set for [Selection State] of the corresponding directory information, and the process program select trigger relay is switched ON. The SECS/GEM communication software sends the selection of a process program (S6F11) to the host, and then switches OFF the process program select trigger relay.
When the automatic process program processing function of the SECS/GEM communication software is not used, select the [Exclusion] tab of the "Process program settings" screen, and then clear the [On] checkbox of each scenario.
252
9 SECS/GEM Communication Software Knowledge 9.17 Using the process program
10 TROUBLESHOOTING
This section explains the troubleshooting of a SECS/GEM communication software pre-installed model module.
10.1 Troubleshooting by Symptom
This section shows the troubleshooting by phenomenon for a SECS/GEM communication software pre-installed model module.
Symptom
A multi-CPU error occurred with a programmable controller CPU and MELSEC-Q series SECS/GEM communication software pre-installed model module A ladder program cannot be written to the programmable controller CPU
The user login settings of the C Controller module or C intelligent function module are unknown
C language settings cannot be written to the C Controller module
The SECS/GEM communication software cannot be installed on the personal computer The project file of the SECS/GEM communication software cannot be opened
Check item
Do the multi-CPU settings of the programmable controller CPU and MELSEC-Q series SECS/GEM communication software pre-installed model module match? There is a problem with the GX Works2 or GX Works3 settings
There is an error during Ethernet diagnosis.
The C Controller module or C intelligent function module has been initialized.
There is a problem with the settings of Setting/monitoring tools for the C Controller module.
The user currently logged in does not have administrative rights for the personal computer Was the PC restarted after installing the setting tool?
Corrective action
During use with a multi-CPU configuration, the settings of the parameters of the CPU must match. Review the parameter settings. For the parameter setting method, see the manual of the programmable controller CPU to be used.
When the GX Works2 or GX Works3 cannot connect with the Programmable Controller CPU, check for problems in the settings of the GX Works2 or GX Works3 . For the parameter setting method, see the manual of the programmable controller CPU to be used.
When the GX Works2 or GX Works3 and Programmable Controller CPU are connected via Ethernet, check the details of the Ethernet diagnosis error, and then remove the cause of the error.
The following table shows the default values when the C Controller module or C intelligent function module has been initialized. IP address (CH1): 192.168.3.3 Username: "target" Password: "password" For the initialization method, see the manual of the C Controller module or C intelligent function module. The pre-installed SECS/GEM communication software license is erased when the C Controller module or C intelligent function module has been initialized.
When Setting/monitoring tools for the C Controller module cannot connect with the Programmable Controller CPU, check for problems in the settings of Setting/monitoring tools for the C Controller module. For the configuration method, see the manual of Setting/monitoring tools for the C Controller module.
A user with administrative rights must login and install the software.
Restart the PC after installing the setting tool.
10
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
253
Symptom
The SECS/GEM communication software pre-installed model module cannot be updated
Check item
Is there a response from the SECS/ GEM communication software preinstalled model module with a ping command?
The user and password entered by using [Setting] and then [Update C language controller] / [Update C intelligent function module] is incorrect The program is blocked by the firewall settings
A proxy server is being used
Is the network device connected to the SECS/GEM communication software pre-installed model module enabled? [Work Offline] is configured in Internet Explorer Is antivirus software installed?
Corrective action
Check for problems with the LAN cable connection. From the command prompt of the PC, etc., issue a ping command. Specification method: ping (IP address) Example: ping 192.168.3.3 If there is no response, the IP address of the SECS/GEM communication software pre-installed model module may be different. Check the IP address using GX Works3 or the Setting/monitoring tools for the C Controller module. Connection is not possible when the IP address settings of the computer differ with the subnet mask of the SECS/GEM communication software pre-installed model module. Configure the correct IP address.
The entry may be incorrect if the caps lock key is on. Switch off the caps lock key, and then make sure there are no mistakes in the entered information.
If ["CA-SECS (product name)"] is blocked in the firewall settings, communication is not possible. Check the firewall settings, and then changes the setting to allow ["CA-SECS (product name)"].
If a proxy server is being used, the IP address of the SECS/GEM communication software pre-installed model module must be configured so that a proxy server is not used.
In the network connection settings, enable the network device connected to the SECS/GEM communication software pre-installed model module. Furthermore, an update may not be possible if other network devices are enabled. In this case, check by disabling other network devices temporarily.
When Internet Explorer 10 or earlier is being used during offline work, click the [File] menu, and then clear the checkbox beside [Work offline].
It may not be possible to update the SECS/GEM communication software preinstalled model module due to the antivirus software. Switch off the antivirus software temporarily, and then see if the problem is resolved.
254
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
Symptom
Check item
Corrective action
The SECS/GEM communication software transferred to the SECS/ GEM communication software preinstalled model module does not start
The CIM control READY relay is not on
If the CIM Control READY relay is on, SECS/GEM communication software is running. For the settings of the CIM control READY relay, see the following reference. Page 82 CA Status
Is there CA-SECS event information in the event history of the SECS/GEM communication software pre-installed model module?
If the SECS/GEM communication software starts, version information and license registration information appear in the event history of the SECS/GEM communication software pre-installed model module. Check if there is event information described in the following: · When using a non-GEM version of MELSEC-Q series SECS/GEM
communication software pre-installed model module, check if there is event information with "CAS" displayed for "Source." · When using a GEM or GEM advanced version of MELSEC-Q series SECS/ GEM communication software pre-installed model module, check if there is event information with "CASECS" displayed for "Source." · When using a MELSEC iQ-R series SECS/GEM communication software pre-installed model module, check if there is event information that "RD55UP06-V" is displayed in "Source" and that starts with 'detail information: [CAS]' in "Detailed event log information."
Is the SECS/GEM communication software installed on the SECS/GEM communication software pre-installed model module?
Make sure that the SECS/GEM communication software is installed at the transfer destination of the SECS/GEM communication software pre-installed model module. Transfer destination: /CF, /SD, or /ROM Transfer file name: CIMOP.OUT or CIMOP_GEM.OUT For the method to install the SECS/GEM communication software on the SECS/GEM communication software pre-installed model module, see the following reference. Page 112 Updating the SECS/GEM communication software pre-installed model module
Is the Mode switch of the MELSEC-Q series SECS/GEM communication software pre-installed model module set to RUN?
If the Mode switch of the MELSEC-Q series SECS/GEM communication software pre-installed model module set to "STOP", device control to the programmable controller CPU is not possible. When SECS/GEM communication is used, always set the switch to "RUN".
Are they are any other applications on the SECS/GEM communication software pre-installed model module?
If other applications are running, SECS/GEM communication software may be affected. Do not run any other applications.
Is a CF card installed in the MELSEC-Q series SECS/GEM communication software pre-installed model module?
SECS/GEM communication software requires a CF card. For CF cards with confirmed operation, see the following reference. Technical bulletin No. FA-D-0023 For the specifications of CF cards, see the website of the product.
Is an SD memory card installed in the MELSEC iQ-R series SECS/GEM communication software pre-installed model module?
SECS/GEM communication software requires a SD memory card. For SD memory cards with confirmed operation, see the following reference. MELSEC iQ-R C Intelligent Function Module User's Manual (Startup) Technical bulletin No. FA-D-0023 For the specifications of SD cards, see the website of the product.
There is incorrect device assignment settings in SECS/GEM communication software
Define all device assignment settings for devices used by SECS/GEM communication software. If devices not defined by the device assignment settings are configured by various functions, access is not authorized. When the MELSEC-Q series SECS/GEM communication software preinstalled model module will be used, the multi-CPU settings of the programmable controller CPU unit and MELSEC-Q series SECS/GEM communication software pre-installed model module must also be defined in the range settings of shared memory. For the multi-CPU settings, see the manual of each unit.
10
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
255
Symptom
SECS communication via HSMS is not possible between SECS/GEM communication software and host
Check item
SECS/GEM communication software is not started
The line disconnection relay is off
Communication settings with the correspondence destination are incorrect
The communication port of the correspondence destination is not open
Corrective action
Refer to "The SECS/GEM communication software transferred to the SECS/ GEM communication software pre-installed model module does not start" in "Troubleshooting", and then check that the SECS/GEM communication software has started.
After starting, SECS/GEM communication software attempts to connect with the correspondence destination automatically. If the HSMS communication state is SELECTED, the line disconnection relay is switched off, so check whether this relay is off. For the settings of the line disconnection relay, see the following reference. Page 82 CA Status
When SECS/GEM communication software is running, and the line disconnection relay is on, the communication setting content may be incorrect. Check whether the following items have matching settings at the equipment and host. (Example: is the connection mode setting Active on one side and Passive on the other?) · Connection mode: Active/Passive · IP address: Local/Remote · IP port: Local/Remote
Using the netstat command, check whether the port of the correspondence destination is open.
256
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
Symptom
An SECS message is not sent even when the sending request trigger is ON
Check item
The communication-established relay is not on
The online relay is not on
The programmable controller CPU is set to "STOP", and the sending request trigger is set to ON manually There is no spooling state
There is incorrect device assignment settings in SECS/GEM communication software
Is a device of the MELSEC-Q series SECS/GEM communication software pre-installed model module within the shared memory being used for a trigger? "Shared Memory Synch Waiting Timer" setting is inappropriate
Corrective action
SECS/GEM communication software manages the communication establishment state, and establishing an S1F13/14 transaction results in a communication establishment state, and the communication-established relay switches on. When communication is not established, messages other than S1F13/14 cannot be sent. For the settings of the Communication established relay, see the following reference. Page 82 CA Status
SECS/GEM communication software manages the online state, and establishing an S1F1/2 transaction establishes an online state, and the online relay is switched on. During an online state, messages other than S1Fx cannot be sent. For the settings of the online relay, see the following reference. Page 82 CA Status
If the Programmable Controller CPU is set to "STOP", and messages can be sent, check the program of the Programmable Controller CPU. If the messages cannot be sent even when the programmable controller CPU is set to "STOP", check the above check items: "The communicationestablished relay is not on" and "The online relay is not on".
A spooling state results if there is an attempt to send a message subject to spooling in an offline state. In a spooling state, the following messages subject to spooling are spooled and not sent. The spooling state is not cleared until a S6F23/24 transaction is established from the correspondence destination. For the settings of the spooling state, see the following reference. Page 106 Spooling function (non-GEM version) Page 180 Spool Function (GEM / GEM advanced version)
Define all device assignment settings for devices used by SECS/GEM communication software. If devices not defined by the device assignment settings are configured by various functions, access is not authorized. When the MELSEC-Q series SECS/GEM communication software preinstalled model module will be used, the multi-CPU settings of the programmable controller CPU unit and MELSEC-Q series SECS/GEM communication software pre-installed model module must also be defined in the range settings of shared memory. For the multi-CPU settings, see the manual of each unit.
When a device within the shared memory range is used as a trigger relay, configure a device of the Programmable Controller CPU. When a device of the MELSEC-Q series SECS/GEM communication software pre-installed model module has been configured, access from the programmable controller CPU is not possible, and it cannot be used as a trigger relay.
SECS/GEM communication software performs a synchronization check to confirm the handshake with the Programmable Controller CPU. By default, the "Shared Memory Synch. Waiting Timer" is configured to 10 ms. Adjust the shared memory synch. waiting timer according to the scan time of the programmable controller CPU. For the settings of the Shared Memory Synch. Waiting Timer, see the following reference. Page 77 Control 2
10
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
257
Symptom
The reception notification trigger does not switch ON even when receiving an SECS message
Communication erroneously stops during SECS communication
The sending and receiving of SECS messages are delayed
An SECS message is sent twice erroneously by a single sending request
Check item
A S9 related error has occurred
The transaction created by the settings tool does not match the list structure of the receiving message
Is the Mode switch of the MELSEC-Q series SECS/GEM communication software pre-installed model module set to RUN? There is incorrect device assignment settings in SECS/GEM communication software
A line disconnection request has been received from the Programmable Controller CPU A line disconnection request has been received from the correspondence destination Check for physical problems with the LAN cable. IP addresses are conflicting
CIM Control READY is off
The cache settings of the referent device are not set
The trigger hold time of the sending request trigger is inappropriate
"Shared Memory Synch Waiting Timer" setting is inappropriate
Corrective action
Check whether a S9 related error has occurred in the SECS communication log. If an error has occurred, remove the cause of the error. For the log reference method, see the following reference. Page 134 Log Output
When the message received from the correspondence destination is different from the list structure, item type, and data length of the transaction created by the setting tool, a S9 related error message is sent, and the corresponding reception notification trigger is not switched ON. Review the structure of the transaction. For the transaction creation method, see the following reference. Page 46 Transaction definition
If the Mode switch of the MELSEC-Q series SECS/GEM communication software pre-installed model module set to "STOP", device control to the programmable controller CPU is not possible. When SECS/GEM communication is used, always set the switch to "RUN".
Define all device assignment settings for devices used by SECS/GEM communication software. If devices not defined by the device assignment settings are configured by various functions, access is not authorized. When the MELSEC-Q series SECS/GEM communication software preinstalled model module will be used, the multi-CPU settings of the programmable controller CPU unit and MELSEC-Q series SECS/GEM communication software pre-installed model module must also be defined in the range settings of shared memory. For the multi-CPU settings, see the manual of each unit.
Check the PLC log and check whether a line disconnection request has been received. If an unintentional request has been received, remove the cause.
Check the SECS log, and then check whether a line disconnection request has been received. If an unintentional request has been received, remove the cause.
Check whether the LAN cable has been unplugged or disconnected.
If the IP address of the C Controller module is conflicting, the line may be disconnected. If the IP address was conflicting, remove the cause.
If the CIM Control READY is set to off in the program of the Programmable Controller CPU, SECS/GEM communication software no longer operates. Do not operate by the program of the Programmable Controller CPU.
When a device defined for the I/O assignment in the device assignment settings is configured as the data referent of the transaction item, setting the cache settings of the corresponding transaction can improve the speed performance. For the transaction cache settings, see the following reference. Page 50 Cache settings
The detection time of the sending request trigger can be adjusted by the settings of the trigger hold time. Configure an appropriate time. For the settings of the trigger hold time, see the following reference. Page 52 Message Information
SECS/GEM communication software performs a synchronization check to confirm the handshake with the Programmable Controller CPU. By default, the "Shared Memory Synch. Waiting Timer" is configured to 10 ms. Adjust the shared memory synch. waiting timer according to the scan time of the programmable controller CPU. For the settings of the Shared Memory Synch. Waiting Timer, see the following reference. Page 77 Control 2
258
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
Symptom
The log cannot be accessed by the settings tool of the SECS/GEM communication software
An SECS error message is generated A 'Memory insufficient.' message is displayed by SECS/GEM communication software setting tool
Check item
The log output settings are not configured
The log output trigger is not on before SECS/GEM communication software starts
The mode switch of the C Controller module is "STOP" The connection destination settings are incorrect The C Controller module or C intelligent function module time is offset
The settings tool is not installed on the personal computer
The online relay is not on
SECS/GEM communication software setting tool is being used when the personal computer is under a high load SECS/GEM communication software is consuming a large amount of virtual memory
Corrective action
Browse to [Log] [Log Output Setting], and then check the settings to output the log. For log output settings, see the following reference. Page 134 Log Output
When log aggregation is to be controlled by the log output trigger, use the CIM Control READY relay, make sure that SECS/GEM communication software has started, and then switch on the log output trigger. For log output trigger settings, see the following reference. Page 134 Log Output
If the mode switch of the C Controller module is "STOP", SECS/GEM communication software cannot output the log. When SECS/GEM communication is used, always set the switch to "RUN".
Make sure that the entries of the IP address, username, and password of the connection destination are correct.
The time information of the log data is dependent on the time of the C Controller module or C intelligent function module. Check the time of the C Controller module or C intelligent function module, and then specify the referenced time. For the method to access the log using the settings tool, see the following reference. Page 143 Log View
When settings are configured at [Log] [Log Output Setting] [Device Display Setting] to display the log on the equipment display, a text-format log file (*.log) is output under the "Log output destination/GOT/" folder. The text-format log file can be acquired and accessed via FTP. Furthermore, it is possible to use the display register to access the content of the text-format log file at the equipment display, etc. For details on the text-format log file, see the following reference. Page 149 View the Log on Display Device (GOT)
SECS/GEM communication software manages the online state, and establishing an S1F1/2 transaction establishes an online state, and the online relay is switched on. During an online state, messages other than S1Fx cannot be sent. For the settings of the online relay, see the following reference. Page 82 CA Status
Close unnecessary applications to reduce the load of the personal computer before using SECS/GEM communication software setting tool.
Check the device assignment settings. Do not configure devices that will not or cannot be used. Furthermore, when the number of bit devices (word count) is configured, make sure the entered value is the word count. For details on settings of device assignment, see the following reference. Page 65 Device Assignment
10
10 TROUBLESHOOTING 10.1 Troubleshooting by Symptom
259
APPENDIX
Appendix 1 Input/output signals
This section explains the input/output signals of a MELSEC iQ-R series SECS/GEM communication software pre-installed model module. Only specifications that differ with the C intelligent function module are explained. For common specifications, see the following reference. MELSEC iQ-R C Intelligent Function Module User Manual (Application Edition)
Initialization setting of host station device
input signal
Device number
X10 X11 X12 X13 X14 X15 X16 X17 X18 X19 X1A X1B X1C X1D X1E X1F
Output signal
Device number
Y10 Y11 Y12 Y13 Y14 Y15 Y16 Y17 Y18 Y19 Y1A Y1B Y1C Y1D Y1E Y1F
Description
CIM Control READY Disconnected Communication Established Online Not set Not set Not set Not set Not set Not set Not set Not set Not set Not set Not set SD error
Description
Not set Line Disconnection Line Connection Online Start Offline Not set Not set Not set Not set Not set Not set Not set Not set Not set Not set Not set
260 APPX Appendix 1 Input/output signals
Appendix 2 Data type conversion
This section explains data type conversion.
Conversion from the SECS/GEM communication software to a programmable controller CPU
BinaryASCII
Source
Dest
· I1, I2, U1, or U2
· ASCII
I2 or U2
· I4 or U4 I4 or U4
I1 or U1
D D+1 D+2 D+3
· ASCII
D D+1 D+2 D+3 D+4 D+5
Ten thousands Hundred One 0
Billion Ten millions Hundred thousands Thousand Ten 0
Sign Thousand Ten
Sign Hundred millions Million Ten thousands Hundred One
ASCIIBinary
Source
Dest
· ASCII
· I1, I2, U1, or U2
A
Sign
D
I1, I2, U1, or U2
Ten thousands
Thousand
Hundred
Ten
One
From the sign, specify a numerical character string to the stopper. Signs can be omitted. Treated as + when signs were omitted.
261 APPX
Appendix 2 Data type conversion
Source
· ASCII
0
Sign
1
Billion
2
Hundred millions
3
Ten millions
4
Million
5
Hundred thousands
6
Ten thousands
7
Thousand
8
Hundred
9
Ten
10
One
11
From the sign, specify a numerical character string to the stopper. Signs can be omitted. Treated as + when signs were omitted.
ASCIIDATE-A
Source
· ASCII
0
y
1
y
2
y
3
y
4
m
5
m
6
d
7
d
8
h
9
h
10
m
11
m
12
s
13
s
14
c
15
c
Dest
· I4 or U4
D
Low-order word
D+1
High-order word
Dest
· DATE-A
D
Year
(0 to 99)
D+1
Month
(1 to 12)
D+2
Date
(1 to 31)
D+3
Hour
(0 to 23)
D+4
Minute
(0 to 59)
D+5
Second
(0 to 59)
D+6
Day of week
(0 to 6: Sunday to Saturday)
For year data, only the last two digits are effective. (The first two digits are ignored. ) cc is not registered to a register.
262 APPX Appendix 2 Data type conversion
ASCIIDATE-Q
Source
· ASCII
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
ASCIIFloat
Source
· ASCII
y y y y m m d d h h m m s s c c
Sign Number 1 Number 2 Decimal point Number n Number n+1
Signs can be omitted. Treated as + when signs were omitted. 0 is the stopper. · ASCII
Sign Number 1 Number 2 Decimal point Number n Number n+1
Signs can be omitted. Treated as + when signs were omitted. 0 is the stopper.
Dest
· DATE-Q
D
Year
D+1
Month
D+2
Date
D+3
Hour
D+4
Minute
D+5
Second
D+6
Day of week
cc is not registered to a register.
(2000 to xxxx) (1 to 12) (1 to 31) (0 to 23) (0 to 59) (0 to 59) (0 to 6: Sun to Sat)
Dest
· F4
D
Float type: Bit 0 to Bit 15
A
D+1
Float type: Bit 16 to Bit 31
· F8
D
Double type: Bit 0 to Bit 15
D+1
Double type: Bit 16 to Bit 31
D+2
Double type: Bit 32 to Bit 47
D+3
Double type: Bit 48 to Bit 63
263 APPX
Appendix 2 Data type conversion
FloatASCII
Source
· F4 Float type
· F8 Double type
Dest
· ASCII
D
Number 1
Sign
D+1
Number 3
Number 2
D+2
Number 5
Number 4
-
Decimal point
Number m
(Decimal) Number 2
(Decimal) Number 1
(Decimal) Number 4
(Decimal) Number 3
-
0
(Decimal) Number n
Signs can be omitted. Treated as + when signs were omitted. 0 is the stopper.
· ASCII
D
Number 1
Sign
D+1
Number 3
Number 2
D+2
Number 5
Number 4
-
Decimal point
Number m
(Decimal) Number 2
(Decimal) Number 1
(Decimal) Number 4
(Decimal) Number 3
-
0
(Decimal) Number n
Signs can be omitted. Treated as + when signs were omitted. 0 is the stopper.
264 APPX Appendix 2 Data type conversion
Conversion from programmable controller CPU to SECS/GEM communication software
BinaryASCII
Source
Dest
· I1, I2, U1, or U2
· ASCII
D
I1, U1, I2, or U2
0
Sign
1
Number 1
2
Number 2
3
Number 3
-
Number n
· I4 or U4
D
Low-order word
D+1
High-order word
Signs (+) are omitted. · ASCII
0 1 2 3
Sign Number 1 Number 2 Number 3 Number n
Signs (+) are omitted.
ASCIIBinary
Source
Dest
A
· ASCII
· I1, I2, U1, or U2
D
Ten thousands
D+1
Hundred
D+2
One
D+3
0
Fixed format · ASCII
Sign Thousand Ten
I1, I2, U1, or U2 · I4 or U4
D
Billion
D+1
Ten millions
D+2
Hundred thousands
D+3
Thousand
D+4
Ten
D+5
0
Fixed format
Sign Hundred millions Million Ten thousands Hundred One
I4 or U4
265 APPX
Appendix 2 Data type conversion
DATE-AASCII
Source
· DATE-A
D
Year
D+1
Month
D+2
Date
D+3
Hour
D+4
Minute
D+5
Second
D+6
Day of week
DATE-QASCII
Source
· DATE-Q
D
Year
D+1
Month
D+2
Date
D+3
Hour
D+4
Minute
D+5
Second
D+6
Day of week
Dest
· ASCII
(0 to 99) (1 to 12) (1 to 31) (0 to 23) (0 to 59) (0 to 59) (0 to 6: Sunday to Saturday)
0
y
1
y
2
y
3
y
4
m
5
m
6
d
7
d
8
h
9
h
10
m
11
m
12
s
13
s
14
c
15
c
Dest
· ASCII
(2000 to xxxx) (1 to 12) (1 to 31) (0 to 23) (0 to 59) (0 to 59) (0 to 6: Sun to Sat)
0
y
1
y
2
y
3
y
4
m
5
m
6
d
7
d
8
h
9
h
10
m
11
m
12
s
13
s
14
c
15
c
266 APPX Appendix 2 Data type conversion
FloatASCII
Source
· F4
D
Float type: Bit 0 to Bit 15
D+1
Float type: Bit 16 to Bit 31
· F8
D D+1 D+2 D+3
Double type: Bit 0 to Bit 15 Double type: Bit 16 to Bit 31 Double type: Bit 32 to Bit 47 Double type: Bit 48 to Bit 63
Dest
· ASCII
· ASCII
Sign Number 1 Number 2 Number 3 Number m Decimal point (Decimal) Number 1 (Decimal) Number 2 (Decimal) Number n
Sign Number 1
Number 2
Number 3
-
Number m
Decimal point (Decimal) Number 1
A
(Decimal) Number 2
-
(Decimal) Number n
267 APPX
Appendix 2 Data type conversion
Appendix 3 Reserved Transactions
This section shows transactions and message formats used internally by the SECS/GEM communication software.
List of reserved transactions and format
This section shows reserved transactions and message formats. The names and formats of reserved transactions are reserved and defined by the SECS/GEM communication software and cannot be used for user definitions.
No. Name
1
DTR*1
(Date and time request)
2
RSD*1
(Spooled data request)
3
CA_ARS*1
(Alarm report transmission)
4
H_SCABT
(Host scenario interruption
request)
5
E_SCABT
(Equipment scenario
interruption notification)
Transaction
Primary message: S2F17(HE) Secondary message: S2F18(HE)
Primary message: S6F23(HE) Secondary message: S6F24(HE) Primary message: S5F1(HE) Secondary message: S5F2(HE) Primary message: S99F1(HE) Secondary message: Unused
Primary message: S99F3(HE) Secondary message: Unused
Description
Sends clock data of the SECS/GEM communication software preinstalled model module. The programmable controller CPU is not notified. Requests the spooled data transfer from the host.
Used by the CA-SECS alarm function.
Interrupts the ongoing scenario from the host.
Notifies that the ongoing scenario was interrupted by equipment request or processing error.
*1 Reserved transaction of non-GEM version.
1. DTR (Date and time request)
<S2F17>(HE) (Header only) <S2F18>(HE)
A<TIME>YYYYMMDDhhmmsscc
Acquires the time configured to the CPU of the SECS/GEM communication software pre-installed model module, and then returns it as 16-byte ASCII data. This transaction does not involve notification to the Programmable Controller CPU or acquisition of the equipment time data.
2. RSD (Spooled data request)
<S6F23>(HE) U1<RSDC>...(1)
<S6F24>(HE) B<RSDA>...(2)
(1) The following code will apply. 0: Transfer the spooled message(s) 1: Discard the spooled messages(s) (2) One of the following values is returned. 0: OK (initiate the spool output) 1: Error 2: No spooled data exists. · If communication has been established, this transaction can be executed even
before CA-SECS becomes online (i.e., before the transaction S1F1 is executed). · The reception of this message will not be notified to the Programmable Controller
CPU.
3. CA_ARS (Alarm report transmission)
<S5F1>(HE) <L, 3> B<ALCD>...(1) U2<ALID>...(2) A<ALTX>...(3)
<S5F2>(HE) B<ACKC5>
(1) The settings in the Alarm Data Setting window are edited as follows and then transmitted. When an alarm occurs: The first bit is "1". When an alarm is reset: The first bit is "0". (2) The set value is transmitted as it is. (3) The set text is transmitted as it is. Up to 40 characters can be transmitted. · Response monitoring is enabled in accordance with the standard for SECS-.
However, the reception notification of a secondary message will not be reported to the programmable controller CPU. · To send an alarm report as a normal transaction triggered by the sending request, set the user definition by another transaction name.
4. H_SCABT (Host scenario interruption request)
<S99F1>(HE) (Header only)
This transaction is transmitted from the host to interrupt the ongoing scenario.
5. E_SCABT (Equipment scenario interruption notification)
<S99F3>(HE) (Header only)
When the ongoing scenario was interrupted by any other than the host scenario interruption request, this transaction is transmitted to the host.
268 APPX Appendix 3 Reserved Transactions
Special Transactions
This section shows special transactions and message formats. The special transactions shown below are user definable transactions but are specially processed by the SECS/GEM communication software internally at the same time as a notification to the programmable controller CPU.
No. Name
Transaction
Description
1
R
(Online request)
2
CR
(Communication request)
3
DTR_2
(Date and time request)
4
DTS
(Date and time setting)
Primary message: S1F1(HE) Secondary message: S1F2(HE) Primary message: S1F13(HE) Secondary message: S1F14(HE)
Primary message: S2F17(HE) Secondary message: S2F18(HE) Primary message: S2F31(HE) Secondary message: S2F32(HE)
Establishes the SECS/GEM communication software online status when this transaction is completed
Where line disconnection is not considered as offline, this transaction will be automatically transmitted when the line is reconnected.
Configures the time data returned from the host to the clock of the SECS/GEM communication software pre-installed model module.
Configures clock data of the SECS/GEM communication software pre-installed model module.
1. R (Online request)
<S1F1>(HE) (Header only) <S1F2>(HE)
<L, 2> A<MDLN> A<SOFTREV>
SECS/GEM communication software becomes online when this transaction is completed. Online status established based on this transaction is determined from the SF code. Even if this transaction has a different name or format from that shown in the left, the same processing will be performed.
2. CR (Communication request)
<S1F13>(HE) <L, 2>
A<MDLN> A<SOFTREV> <S1F14>(HE) <L, 2> B<COMMACK> <L, 2>
A<MDLN> A<SOFTREV>
When the "Automatically Transmit S1F13 Upon Line Reconnection" is
enabled in the Option Setting window, this transaction is transmitted
automatically to the host when the line is reconnected.
If the transaction is undefined, automatic transmission will not be performed.
Online status established based on this transaction is determined from the SF
code. Even if this transaction has a different name or format from that shown
in the left, the same processing will be performed.
· Setting the parent list of MDLN and SOFTREV to a variable length list makes it possible for the host to transmit this as <L, 0>.
A
· When handshake for each transaction is enabled, note that the reception of
secondary messages at the time of automatic transmission will no longer be
notified to the Programmable Controller CPU.
3. DTR_2 (Date and time request)
<S2F17>(HE) (Header only) <S2F18>(HE)
A<TIME>YYYYMMDDhhmmsscc*1
In the case of a MELSEC-Q series SECS/GEM communication software preinstalled model module, the time received by <TIME> is configured to the clock of the SECS/GEM communication software pre-installed model module. However, because the time zone of CPU No. 1 is followed by a multi-CPU system, configure the time of CPU No. 1 by the programmable controller CPU. Notification to the programmable controller CPU is performed according to the setting. This differs with a DTS transaction in that the time of the host is acquired by a request on the programmable controller CPU. The transaction name "DTR" is not available since it is already used for a reserved transaction. When any other name is given, the sequence above will be executed and the reserved transaction "DTR" will be invalid. (The reserved transaction "DTR" is a time request from the host).
*1 When data count in <TIME> is set to 16 and variable length setting is enabled, it supports the reception of the following three formats: 16 byte format (YYYYMMDDhhmmsscc) 14 byte format (YYYYMMDDhhmmss) 12 byte format (YYMMDDhhmmss)
269 APPX
Appendix 3 Reserved Transactions
4. DTS (Date and time setting)
<S2F31>(HE) A<TIME>YYYYMMDDhhmmsscc*1
<S2F32>(HE)
B<TIACK>
In the case of a MELSEC-Q series SECS/GEM communication software preinstalled model module, the time configured by <TIME> is configured to the clock of the SECS/GEM communication software pre-installed model module. However, because the time zone of CPU No. 1 is followed by a multi-CPU system, configure the time of CPU No. 1 by the programmable controller CPU. Notification to the programmable controller CPU is performed according to the setting. The online status setting of the C Controller module with this transaction is based on the SF code. Even if the transaction name differs from the name on the left, the processing will be the same.
*1 When data count in <TIME> is set to 16 and variable length setting is enabled, it supports the reception of the following three formats: 16 byte format (YYYYMMDDhhmmsscc) 14 byte format (YYYYMMDDhhmmss) 12 byte format (YYMMDDhhmmss)
System Error (S9Fx)
The SECS/GEM communication software provides the following error messages.
No. Name
Transaction
Description
1
UDN
(Incorrect device ID)
S9F1(HE)
2
USN
S9F3(HE)
(Unrecognized Stream Type)
3
UFN
S9F5(HE)
(Unrecognized Function Type)
4
IDN
(Illegal Data)
S9F7(HE)
5
TTN
(Transaction time-out)
S9F9(HE)
6
DLN
(Data Too Long)
S9F11(HE)
Notifies that the device ID in the header of the received message is different from the device ID set in SECS/GEM communication software. The Stream code of a received message notifies of a lack of the definition at the SECS/GEM communication software. The Function code of a received message notifies of a lack of the definition at the SECS/GEM communication software. Notifies that the format of the received message from the host is different from the message format set in SECS/GEM communication software. Notifies that T3 timer (host response monitoring timer) time-out occurred.
Notifies that CA-SECS received an improperly sized message that cannot be processed by SECS/GEM communication software.
1. Incorrect device ID, 2. Unrecognized Stream Type, 3. Unrecognized Function Type, 4. Illegal Data, 6. Data Too Long
Example: S9F1 <S9F1>(HE)
B10<MHEAD> <S9F2> (Unused)
The header of the received message (erroneous message) is configured to <MHEAD>.
5. Transaction time-out
S9F9 <S9F9>(HE)
B10<SHEAD> <S9F10> (Unused)
The header of the sending message (primary) in the timed-out transaction is configured to <SHEAD>.
S9F13. CTN (Conversation Timeout)
S9F13 <S9F13>(HE) <L, 2>
A<MEXP> -<EDID> <S9F14> (Unused)
User definition of S9F13 is necessary.
270 APPX Appendix 3 Reserved Transactions
Appendix 4 SECS item list
This section is a list of items the SECS/GEM communication software uses with GEM scenarios.
Item name
Description
Item format
Supported data type
Supported data size (Byte)
Changeability
ACKC5
Confirmation code
BIN
1
ACKC6
Confirmation code
BIN
1
ACKC7
Confirmation code
BIN
1
ALCD
Alarm code
BIN
1
ALED
Alarm on/off code
BIN
1
ALID
Alarm ID
U1, U2, U4
1
ALTX
Alarm text
ASCII
Maximum of 40
CEED
Collected events or trace on/off code BOOL
1
CEID
Acquired event ID
U1, U2, U4
1
COMMACK
Communication establishment
BIN
1
confirmation code
DATAID
Data ID
U1, U2, U4
1
DATALENGTH
Total number of sending data bytes U1, U2, U4
1
DRACK
Definition report agreement code
BIN
1
DSPER
Data acquisition time
ASCII
6, 8
EAC
Equipment confirmation code
BIN
1
ECDEF
Equipment variable default value
ECID
Equipment constant ID
U1, U2, U4
1
ECMAX
Equipment variable maximum value
ECMIN
Equipment variable minimum value
ECNAME
Equipment constant name
ASCII
Maximum of 32
ECV
Device constant
BIN, BOOL, ASCII, JIS8, I1, Maximum of 32,000 for BIN,
A
I2, I4, U1, U2, U4, F4, F8
ASCII, and JIS8
Otherwise, 1
EDID
Date ID that should be received
U1, U2, U4
1
ERACK
Enable/disable event report
BIN
1
confirmation code
FCNID
Function identification
U1
1
GRANT
Permission code
BIN
1
GRANT6
Sending permission
BIN
1
LIMITACK
Confirmation code for variable limit
BIN
1
attribute setting
LIMITID
Specific limit for a variable referenced BIN
1
by a corresponding limit attribute
LIMITMAX
Maximum permitted value for limit
value of specific variable
LIMITMIN
Minimum permitted value for limit
value of specific variable
LOWERDB
Dead band lower limit
LRACK
Link report confirmation code
BIN
1
LVACK
Response code for variable limit
BIN
1
attribute setting
MDLN
Equipment form
ASCII
Maximum of 20
MEXP
Message SxxFyy that should be received
ASCII
Minimum of 2, maximum of 6
OFLACK
Confirmation code for offline request BIN
1
ONLACK
Confirmation code for online request BIN
1
PPID
Process program ID
ASCII
Maximum of 80
REPGSZ
Report group size
U1, U2, U4
1
RPTID
Report ID
U1, U2, U4
1
271 APPX
Appendix 4 SECS item list
Item name
RSDA RSDC RSPACK SMPLN SOFTREV STIME STRACK STRID SV
SVID SVNAME TIAACK TIACK TIME TOTSMP TRID UNITS UPPERDB V VID VLAACK
Description
Spooled data request confirmation Spooled data request code Spooled data setting confirmation Sample number Revision code of software Sample time Spool stream response Stream identification State variable data
State variable ID State variable name Equipment response code Time confirmation code Date and time Total sample count Trace request ID Item to identify unit Dead band upper limit Variable data Variable ID Limit attribute confirmation code
Item format Supported data type
BIN U1 BIN U1, U2, U4 ASCII ASCII BIN U1 LIST, BIN, BOOL, ASCII, JIS8, I1, I2, I4, U1, U2, U4, F4, F8 U1, U2, U4 ASCII BIN BIN ASCII U1, U2, U4 U1, U2, U4 ASCII U1, U2, U4 BIN
Supported data size (Byte)
1 1 1 1 Maximum of 20 12, 16 1 1 Maximum of 32,000 for BIN, ASCII, and JIS8 Otherwise, 1 1 Maximum of 32 1 1 12, 16 1 1 Maximum of 16 1 1
Changeability
272 APPX Appendix 4 SECS item list
Appendix 5 Communication Specifications Check
Sheet
The check sheet shows what to check in definition of SECS communication. The check sheet is useful for checking the specifications.
Setting item
Communication port Device ID SECS- setting
Mode Transmission speed [bps] T1 [sec] (0.1 to 10) T2 [sec] (0.2 to 25) T3 [sec] (1 to 120) T4 [sec] (1 to 120) HSMS setting Host IP address Own station IP address Host port number Own station port number Mode T3 [sec] (1 to 120) T5 [sec] (1 to 240) T6 [sec] (1 to 240) T7 [sec] (1 to 240) T8 [sec] (1 to 120) Link Test timer [sec] (1 to 65535) Number of retries after line disconnection (Endless retries / specified number of times) Line disconnection from own station Sending-side interleaving (multi-open transaction)
Interleaving for reception (open multi-transactions)
Variable length lists Variable length items
Switch into offline status upon disconnection Spooling Multi-block transmission permission by host
SxF0 transmission SxF0 reception S9F1/F3/F5/F9/F11 transmission S9F7(item data error) transmission
S9F13 transmission
SECS communication log storage
Setting
SECS-/HSMS
Master / Slave
Passive / Active
Endless /
times
Enable / Disable Enable / Disable
Enable / Disable
Enable / Disable Enable / Disable
Enable / Disable Enable / Disable Enable / Disable
Enable / Disable Enable / Disable Automatic transmission Enable / Disable
Enable / Disable
Enable / Disable
Notes
Inter-character time-out
Protocol time-out
Response time-out
Inter-block time-out
Response time-out
Connection separation time-out
Control transaction time-out
Not Selected time-out
Inter-character time-out for network
A
Number of multi-transaction queues for PLC transmission Number of multi-transaction queues for PLC reception
Set the maximum value for the number of data sets.
If Enable is set, a scenario for permission frame must be defined.
A scenario for illogical data processing must be defined. If Enable is set, a scenario must be defined for this purpose.
APPX Appendix 5 Communication Specifications Check Sheet
273
Appendix 6 SEMI E30(GEM) Support Message
This section shows a list of SEMI E30(GEM) compliant messages.
Stream1 Equipment Status
: Defined, : Definition required
Message
Sender
Name
S1F0 S1F1 S1F2 S1F3 S1F4 S1F5 S1F6 S1F11 S1F12 S1F13 S1F14 S1F15 S1F16 S1F17 S1F18
HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE
Abort Transaction (S1F0) Are You There Request (R) On Line Data (D) Selected Equipment Status Request (SSR) Selected Equipment Status Data (SSD) Formatted Status Request (FSR) Formatted Status Data (FSD) Status Variable Namelist Request (SVNR) Status Variable Namelist Reply (SVNRR) Establish Communication Request (CR) Establish Communication Request Acknowledge (CRA) Request OFF-LINE (ROFL) OFF-LINE Acknowledge (OFLA) Request ON-LINE (RONL) ON-LINE Acknowledge (ONLA)
Stream2 Equipment Control and Diagnostics
: Defined, : Definition required
Message
Sender
Name
S2F0 S2F13 S2F14 S2F15 S2F16 S2F17 S2F18 S2F21 S2F22 S2F23 S2F24 S2F25 S2F26 S2F29 S2F30 S2F31 S2F32 S2F33 S2F34 S2F35 S2F36 S2F37 S2F38 S2F39 S2F40
HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE
Abort Transaction (S2F0) Equipment Constant Request (ECR) Equipment Constant Data (ECD) New Equipment Constant Send (ECS) New Equipment Constant Acknowledge (ECA) Date and Time Request (DTR) Date and Time Data (DTD) Remote Command Send (RCS) Remote Command Acknowledge (RCA) Trace Initialize Send (TIS) Trace Initialize Acknowledge (TIA) Loopback Diagnostic Request (LDR) Loopback Diagnostic Data (LDD) Equipment Constant Namelist Request (ECNR) Equipment Constant Namelist (ECN) Date and Time Set Request (DTR) Date and Time Set Acknowledge (DTA) Define Report (DR) Define Report Acknowledge (DRA) Link Event Report (LER) Link Event Report Acknowledge (LERA) Enable/Disable Event Report (EDER) Enable/Disable Event Report Acknowledge (EERA) Multi-block Inquire(DMBI) Multi-Block Grant (MBG)
274 APPX Appendix 6 SEMI E30(GEM) Support Message
Supp ort
Supp ort
*1 *1
Message
Sender
Name
S2F41
HE
Host Command Send (HCS)
S2F42
HE
Host Command Acknowledge (HCA)
S2F43
HE
Reset Spooling Stream and Function (RSSF)
S2F44
HE
Reset Spooling Acknowledge (RSA)
S2F45
HE
Define Variable Limit Attributes (DVLA)
S2F46
HE
Variable Limit Attribute Acknowledge (VLAA)
S2F47
HE
Variable Limit Attributes Request (VLAR)
S2F48
HE
Variable Limit Attributes Send (VLAS)
S2F49
HE
Enhanced Remote Command
S2F50
HE
Enhanced Remote Command Acknowledge
*1 A GEM version requires a definition.
Stream5 Exception Handling
: Defined, : Definition required
Message
Sender
Name
S5F0 S5F1 S5F2 S5F3 S5F4 S5F5 S5F6 S5F7 S5F8
HE HE HE HE HE HE HE HE HE
Abort Transaction (S5F0) Alarm Report Send (ARS) Alarm Report Acknowledge (ARA) Enable/Disable Alarm Send (EAS) Enable/Disable Alarm Acknowledge (EAA) List Alarm Request (LAR) List Alarm Data (LAD) List Enabled Alarm Request (LEAR) List Enabled Alarm Data (LEAD)
*1 A MELSEC iQ-R series requires a definition.
Stream6 Data Collection
: Defined, : Definition required
Message
Sender
Name
S6F0 S6F1 S6F2 S6F5 S6F6 S6F11 S6F12 S6F15 S6F16 S6F19 S6F20 S6F23 S6F24
HE HE HE HE HE HE HE HE HE HE HE HE HE
Abort Transaction (S6F0) Trace Data Send (TDS) Trace Data Acknowledge (TDA) Multi-Block Data Send Inquire (MBI) Multi-Block Grant (MBG) Event Report Send (ERS) Event Report Acknowledge (ERA) Event Report Request (ERR) Event Report Data (ERD) Individual Report Request (IRR) Individual Report Data (IRD) Request Spooled Data (RSD) Request Spooled Data Acknowledgment Send (RSDAS)
Supp ort
*1 *1 *1 *1
Supp ort
*1 *1
A
Supp ort
Stream7 Process Program Management
: Defined, : Definition required
Message
Sender
Name
S7F0 S7F1
HE HE
Abort Transaction (S7F0) Process Program Load Inquire (PPI)
Supp ort
275 APPX
Appendix 6 SEMI E30(GEM) Support Message
Message
Sender
Name
S7F2
HE
Process Program Load Grant (PPG)
S7F3
HE
Process Program Send (PPS)
S7F4
HE
Process Program Acknowledge (PPA)
S7F5
HE
Process Program Request (PPR)
S7F6
HE
Process Program Data (PPD)
S7F7
HE
Process Program ID Request (PIR)
S7F8
HE
Process Program ID Data (PID)
S7F17
HE
Delete Process Program Send (DPS)
S7F18
HE
Delete Process Program Acknowledge (DPA)
S7F19
HE
Current EPPD Request (RER)
S7F20
HE
Current EPPD Data (RED)
S7F23
HE
Formatted Process Program Send (FPS)
S7F24
HE
Formatted Process Program Acknowledge (FPA)
S7F25
HE
Formatted Process Program Request (FPR)
S7F26
HE
Formatted Process Program Data (FPD)
S7F27
HE
Process Program Verification Send (PVS)
S7F28
HE
Process Program Verification Acknowledge (PVA)
*1 A GEM version requires a definition.
Stream9 System Errors
: Defined, : Definition required
Message
Sender
Name
S9F0 S9F1 S9F3 S9F5 S9F7 S9F9 S9F11 S9F13
HE HE HE HE HE HE HE HE
Abort Transaction (S9F0) Unrecognized Device ID (UDN) Unrecognized Stream Type (USN) Unrecognized Function Type (UFN) Illegal Data (IDN) Transaction Timer Timeout (TTN) Data Too Long (DLN) Conversation Timeout (CTN)
Stream10 Terminal Services
: Defined, : Definition required
Message
Sender
Name
S10F0 S10F1 S10F2 S10F3 S10F4 S10F5 S10F6 S10F7
HE HE HE HE HE HE HE HE
Abort Transaction (S10F0) Terminal Request (TRN) Terminal Request Acknowledge (TRA) Terminal Display, Single (VTN) Terminal Display, Single Acknowledge (VTA) Terminal Display, Multi-block (VTN) Terminal Display, Multi-BlockAcknowledge (VMA) Multi-block Not Allowed(MNN)
276 APPX Appendix 6 SEMI E30(GEM) Support Message
Supp ort
*1 *1 *1 *1
Supp ort
Supp ort
Appendix 7 SECS/GEM communication software
unique ACK code list
This section shows the list of ACK codes.
Name
ACKC5 DRACK
Item Format Code
10
10
EAC
10
LIMITACK
10
LRACK
10
TIAACK
10
Description
Value E5-1107
SECS/GEM communication software inherent
Applicati on
Confirmation code, 1 byte
0 = Agreement >0 = Error, cannot be comprehended 1 to 63: reserved
1 = ALID does not exist
S5F2, F4
Definition report agreement code, 1 byte
0 = Agreement 1 = Denied, space insufficient 2 = Denied, disabled format 3 = Denied, at least one RPTID is already defined. 4 = Denied, not even one VID exists. >4 = Other error 5 to 63: reserved
5 =RPTID value incorrect (RPTID=0) 6 = Excessive linkable VID for one RPTID
S2F34
Equipment confirmation code, 1 byte
0 = Agreement 1= Denied, not even one variable exists. 2 = Denied, busy 3 = Denied, at least one variable is outside the range >3 = Other equipment inherent error 4 to 63: reserved
4 = Batch conversion ECV value exceeded 5 = Variable cannot be changed 6 = System error (register writing)
S2F16
Confirmation code for
1 = LIMITID does not exist.
8 = Limit definition cannot be
S2F46
variable limit attribute
2=UPPERDB > LIMITMAX
registered
setting,
3=LOWERDB < LIMITMIN
1 byte
4=UPPERDB < LOWERDB
5 = Clearly incorrect format for
UPPERDB or LOWERDB
6 = Cannot be interpreted as a
A
numerical value because it is an ASCII
value
7 = Limit definitions overlap for this
variable
>7 = Other equipment specific error
8 to 63: reserved
Link report confirmation code, 1 byte
0 = Agreement 1 = Denied, space insufficient 2 = Denied, disabled format 3 = Denied, at least one CEID link is already defined. 4 = Denied, not even one CEID exists. 5 = Denied, not even one RPTID exists. >5 = Other error 6 to 63: reserved
6 = Excessive linkable RPTID for one CEID
S2F36
Equipment response code, 1 byte
0 = Normal 1 = Too many state variable IDs (SVID) 2 = Trace not possible after this 3 = Invalid trace interval >3 = Machine inherent error 4 to 63: reserved
4 = SV not registered 5 = SV incorrect format 6 = TRID value incorrect (TRID=0) 7 = Excessive reportable sample number at one time
S2F24
APPX Appendix 7 SECS/GEM communication software unique ACK code list
277
Appendix 8 Added and Changed Functions
The following section shows the functions added or changed for the SECS/GEM communication software, and the software versions of the SECS/GEM communication software for these functions.
Added/changed contents
Device find/replace function Display setting for logs View the Log on Display Device (GOT) Extending the ranges of devices that can be used for I/O assignment Extending the number of units of data in an item information definition Extending the ranges of devices that can be found/replaced
Software version of SECS/GEM communication software
MELSEC-Q series
MELSEC iQ-R series
NonGEM version
GEM version
GEM advance d version
NonGEM version
GEM version
GEM advance d version
Ver.1.26C Ver.1.26C Ver.1.26C Ver.1.26C Ver.1.26C Ver.1.26C
Ver.1.01B Ver.1.26C Ver.1.26C Ver.1.26C Ver.1.26C Ver.1.26C
Ver.1.28E
Ver.1.28E
Ver.1.28E
Reference
Page 130 Device Find/ Replace Page 140 Display Setting Page 149 View the Log on Display Device (GOT) Page 68 Available device ranges Page 57 Data types (item format codes) Page 130 Device Find/ Replace
278 APPX Appendix 8 Added and Changed Functions
REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date
January 2020 February 2020
*Manual number
BCN-89999-6494-A BCN-89999-6494-B
Description
First edition
Added or modified parts Section 9.8, Appendix 4, Appendix 6
Japanese manual number: BCN-89999-6493-B
This manual confers no industrial property rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.
2020 MITSUBISHI ELECTRIC CORPORATION
279
TRADEMARKS
The company names, system names and product names mentioned in this manual are either registered trademarks or trademarks of their respective companies. In some cases, trademark symbols such as '' or '' are not specified in this manual.
280
BCN-89999-6494-B(2002)
HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN
When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission. Specifications subject to change without notice.