Mitsubishi Electronics MELSEC-F Bedienungsanleitung

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296

Zur Seite of

Richtige Gebrauchsanleitung

Die Vorschriften verpflichten den Verkäufer zur Übertragung der Gebrauchsanleitung Mitsubishi Electronics MELSEC-F an den Erwerber, zusammen mit der Ware. Eine fehlende Anleitung oder falsche Informationen, die dem Verbraucher übertragen werden, bilden eine Grundlage für eine Reklamation aufgrund Unstimmigkeit des Geräts mit dem Vertrag. Rechtsmäßig lässt man das Anfügen einer Gebrauchsanleitung in anderer Form als Papierform zu, was letztens sehr oft genutzt wird, indem man eine grafische oder elektronische Anleitung von Mitsubishi Electronics MELSEC-F, sowie Anleitungsvideos für Nutzer beifügt. Die Bedingung ist, dass ihre Form leserlich und verständlich ist.

Was ist eine Gebrauchsanleitung?

Das Wort kommt vom lateinischen „instructio”, d.h. ordnen. Demnach kann man in der Anleitung Mitsubishi Electronics MELSEC-F die Beschreibung der Etappen der Vorgehensweisen finden. Das Ziel der Anleitung ist die Belehrung, Vereinfachung des Starts, der Nutzung des Geräts oder auch der Ausführung bestimmter Tätigkeiten. Die Anleitung ist eine Sammlung von Informationen über ein Gegenstand/eine Dienstleistung, ein Hinweis.

Leider widmen nicht viele Nutzer ihre Zeit der Gebrauchsanleitung Mitsubishi Electronics MELSEC-F. Eine gute Gebrauchsanleitung erlaubt nicht nur eine Reihe zusätzlicher Funktionen des gekauften Geräts kennenzulernen, sondern hilft dabei viele Fehler zu vermeiden.

Was sollte also eine ideale Gebrauchsanleitung beinhalten?

Die Gebrauchsanleitung Mitsubishi Electronics MELSEC-F sollte vor allem folgendes enthalten:
- Informationen über technische Daten des Geräts Mitsubishi Electronics MELSEC-F
- Den Namen des Produzenten und das Produktionsjahr des Geräts Mitsubishi Electronics MELSEC-F
- Grundsätze der Bedienung, Regulierung und Wartung des Geräts Mitsubishi Electronics MELSEC-F
- Sicherheitszeichen und Zertifikate, die die Übereinstimmung mit entsprechenden Normen bestätigen

Warum lesen wir keine Gebrauchsanleitungen?

Der Grund dafür ist die fehlende Zeit und die Sicherheit, was die bestimmten Funktionen der gekauften Geräte angeht. Leider ist das Anschließen und Starten von Mitsubishi Electronics MELSEC-F zu wenig. Eine Anleitung beinhaltet eine Reihe von Hinweisen bezüglich bestimmter Funktionen, Sicherheitsgrundsätze, Wartungsarten (sogar das, welche Mittel man benutzen sollte), eventueller Fehler von Mitsubishi Electronics MELSEC-F und Lösungsarten für Probleme, die während der Nutzung auftreten könnten. Immerhin kann man in der Gebrauchsanleitung die Kontaktnummer zum Service Mitsubishi Electronics finden, wenn die vorgeschlagenen Lösungen nicht wirksam sind. Aktuell erfreuen sich Anleitungen in Form von interessanten Animationen oder Videoanleitungen an Popularität, die den Nutzer besser ansprechen als eine Broschüre. Diese Art von Anleitung gibt garantiert, dass der Nutzer sich das ganze Video anschaut, ohne die spezifizierten und komplizierten technischen Beschreibungen von Mitsubishi Electronics MELSEC-F zu überspringen, wie es bei der Papierform passiert.

Warum sollte man Gebrauchsanleitungen lesen?

In der Gebrauchsanleitung finden wir vor allem die Antwort über den Bau sowie die Möglichkeiten des Geräts Mitsubishi Electronics MELSEC-F, über die Nutzung bestimmter Accessoires und eine Reihe von Informationen, die erlauben, jegliche Funktionen und Bequemlichkeiten zu nutzen.

Nach dem gelungenen Kauf des Geräts, sollte man einige Zeit für das Kennenlernen jedes Teils der Anleitung von Mitsubishi Electronics MELSEC-F widmen. Aktuell sind sie genau vorbereitet oder übersetzt, damit sie nicht nur verständlich für die Nutzer sind, aber auch ihre grundliegende Hilfs-Informations-Funktion erfüllen.

Inhaltsverzeichnis der Gebrauchsanleitungen

  • Seite 1

    FX 3U -ENET USER'S MANUAL[...]

  • Seite 2

    [...]

  • Seite 3

    A - 1 A - 1 SAFETY PRECAUTIONS (Read these preca utions before use.) Before installation, opera tion, maintenance or insp ec tion of this product, thorou ghly read through and understand this manual an d all of the associated manuals. Also, take care to han dle the module properly and safely. This manual classifies the safety precautions into two c[...]

  • Seite 4

    A - 2 A - 2 [Design Precautions] [Installation Precautions] CAUTION When the status control (remote RUN/STOP) of t he PLC is performed from the external device, select the "Always wait for OPEN" parameter set by an user in advance. (Select with the in itial timing setting (BFM#24 b8) in the operational sett ing.) When "Do not wait fo[...]

  • Seite 5

    A - 3 A - 3 [Wiring Instructions] DANGER Before mounting or wiring the module, make sure to shut off all of the external power supply . Failure to do so may cause elec tric shocks or damage the module. When turning on the power and operating after mounting or wiring the module, make sure to install the accessory terminal covers to the product. Othe[...]

  • Seite 6

    A - 4 A - 4 [Setup and Maintenance Precautions] [Precautions When Disposing of This Product] [Trans Portation Precautions] DANGER Do not touch any terminal while the PLC's power is on. Doing so may cause electric shock or malfu nctions. Before cleaning or retightening terminal screw s and module mounting screws, externally cut off all phases o[...]

  • Seite 7

    A - 5 A - 5 CONTENTS SAFETY PRECAUTIONS .............. ................. ................ ................ ................ ................ .............. ........ A- 1 CONTENTS ............. ................ ................ ................ ................ ................. ............ ............. ................... A- 5 About Manuals .....[...]

  • Seite 8

    A - 6 A - 6 5 COMMUNICATION PROCEDURE 5- 1 to 5-46 5.1 Overview of the C ommunication Procedure ..................... ................. ................ ................... ......... 5 - 1 5.2 Initial Processing ............... ................ ................ ................ ................. ................ ........ .............. ...... 5- 3 [...]

  • Seite 9

    A - 7 A - 7 8 COMMUNICATION USING MC PROTOCOL 8- 1 to 8- 4 8.1 Data Communication Functi on .......... ............. ................ ................ ................ ................. ....... ........ 8- 1 8.1.1 Accessing the PLC using MC protocol ............... ................ ................ ................ ................... ... 8- 1 8.1.[...]

  • Seite 10

    A - 8 A - 8 11 TROUBLESHOOTING 11- 1 to 11-45 11.1 How to Check Errors Using LED Displays ...... .......... ................ ............. ................ ................ .... 11 - 2 11.1.1 Checking error display .... ................. ... ......... ................. ............. ................ ................ .. ........ 11- 2 11.1.2 How to [...]

  • Seite 11

    A - 9 A - 9 About Manuals This manual explains the mounting of FX 3U -ENET , the specifications, broadcast functions and communicati on methods. For the instructions and programs of the sequence as well as the p arameter setting s by FX Configurator-EN, also refer to the following manuals. Associated Manuals How to obt ain manuals For the necessary[...]

  • Seite 12

    A - 10 A - 10 Applicable Standard Certification of UL, cUL stand ards The following product has UL an d cUL certification. UL, cUL File Number: E95239 Models: MELSEC FX 3U se ries manufactured FX 3U -ENET Regarding the standar ds that comply with the main unit, please refe r to either the FX series product cat alog or consult with yo ur neare st Mi[...]

  • Seite 13

    A - 11 A - 11 Caution to conform with EC Directiv es • Installation in Enclosur e Programmable logic controllers are op en-type device s that must be installed and used within conductive control cab inets. Please use the programmable logic controller while inst alled within a conductive shielded control cabinet. Please secure the cabinet door to [...]

  • Seite 14

    A - 12 A - 12 The Manual's Usage and Structure How to use this manual In this manual, explanations ar e given fo r each application of the Ethernet modules (FX 3U -ENET). Please use this manual using the following key items below as a reference. (1) Features and utility lists (a) Features and functions • C hapter 1 describes the featur es of[...]

  • Seite 15

    A - 13 A - 13 (3) Connection between the Ethernet module and ex ternal devices (a) Communica tion procedur es • S ection 5.1 describes an outli ne of the comm unication procedures (b) Connections with the external device s • S ection 5.6 describes the conn ecti ons (open and close processing) for each communication method (TCP/IP) and the open [...]

  • Seite 16

    A - 14 A - 14 About the Generic Term s and Abbreviations This manual uses the following generic terms and abbreviation s to describe the Model FX 3U -ENET Ethernet inte rface block. Generic T erm/Abbre viation Description Ethernet Address A machine-specific a ddress that is also referred to as the MAC (Media Access Control Address). This is us ed t[...]

  • Seite 17

    1 - 1 OVERVIEW 1 1 - 1 1 MELSEC-F 1O V E R V I E W This manual provides infor mation on the spec ifications of the Ethe rnet interface block, FX 3U -ENET (hereinaf ter called FX 3U -ENET or the Ethernet module), as well as the procedures be fore star ting operation, th e control procedur es and dat a communication method for communicating wi th ext[...]

  • Seite 18

    1 - 2 OVERVIEW 1 1 - 2 1 MELSEC-F 1) Collection and mo dification of PLC data (Communication using the MELSEC Co mmunication Protocol (referred to below as the MC Prot ocol)) 2) T ransmission and r eception of arbitrar y data to/fro m external devices (Communication using fixed buf fers) 3) Dat a transmission/reception by e-mail (When using the e-m[...]

  • Seite 19

    1 - 3 MELSEC-F OVERVIEW 1 1 - 3 1.2 Features of t he Ethernet Module (1) Data communication using MC protocol (Details are explained in Chapter 8 and Chapter 9) Using MC protocol, the device dat a of the PLC can be read from/written to the host system. This protocol is a passive pr otocol that communicates dat a solely according to the requests fro[...]

  • Seite 20

    1 - 4 MELSEC-F OVERVIEW 1 1 - 4 (3) Communication by e-mails (Detai ls are explained in Chapter 10) Data can be sent to and receive d from an external device at a remote locatio n using e-mail via an Internet line. (a) Sending/receiving e-mail from the PLC The following dat a can be sent/received by e-mai l. 1) Sending/receiving da ta as attached f[...]

  • Seite 21

    1 - 5 MELSEC-F OVERVIEW 1 1 - 5 (4) Connecting FX Configurator-EN (Details are explained in the Operating Manuals for FX Configurator-EN) (a) Simplifying sequence prog rams using FX Configurator- EN FX Configurator-EN suppo rts the p arameter settin g function to perform the Ethernet module initializat ion and the open processing with external devi[...]

  • Seite 22

    1 - 6 MELSEC-F OVERVIEW 1 1 - 6 (b) Connecting multiple MELSOFT prod ucts (GX Developer , MX Component) This product can be connected with one or more MELSOFT pro duct, via TCP/IP communication (through the in-house LAN, etc.). 1) Connection via TCP/IP co mmunication • If a ME LSOFT prod uct is to be conn ected with the FX Configurator-EN open se[...]

  • Seite 23

    1 - 7 MELSEC-F OVERVIEW 1 1 - 7 1.3 Software Configuration The Ethernet modules support the TCP/IP and UDP/IP protocols. (1) TCP (T ransmission Control Protocol) This protocol guarantees data credibilit y and reliability in communication between a personal computer/work st ation and PL C that are connected via ne twork, and provides the following f[...]

  • Seite 24

    1 - 8 MELSEC-F OVERVIEW 1 1 - 8 (2) UDP (User Datagram Protocol) This protocol may not guarantee data cr edibility or reliabilit y in communication between a personal computer /work station and PL C that are connected via network. Thus, even if the data does no t reach the t arget n ode, it will not be retransmitt ed. • Because it is connectionle[...]

  • Seite 25

    1 - 9 MELSEC-F OVERVIEW 1 1 - 9 3) PSH (Push Flag) When this bit is ON (1), the host th at has received this segment sends the data to the up per application with high priority . This bit is to be turned ON when the dat a should be sent to an external device as soon as possible. When this bit is OFF (0), the timing wh en the received dat a is sent [...]

  • Seite 26

    2 - 1 SYSTEM CONFIGURATIONS 2 2 - 1 2 MELSEC-F 2 SYSTEM CONFIGURA TIONS This section explains the system configurations that may be combined with the Ethernet modules. 2.1 Applicable Systems Ethernet modules can be used with the following systems: (1) Applicable PLC and number of modules t hat can be mounted The following t able lists the PLC where[...]

  • Seite 27

    2 - 2 SYSTEM CONFIGURATIONS 2 2 - 2 2 MELSEC-F 2.2 Devices Required fo r Network Configuration This section explains the devices that are requ ired to configure a netwo rk. Network installation work re quires suf ficient safeguard; ask a network specialist for installation. When connecting Ethernet module to a network, either a 10BASE-T or 100BASE-[...]

  • Seite 28

    2 - 3 MELSEC-F SYSTEM CONFIGURATIONS 2 2 - 3 (2) Connection usi ng the 10BASE-T Use devices that satisfy the standards of IEEE802.3 and 10BASE-T . • Shielded twisted pair cable (STP cable), categor y 3 (4, 5) * U se a straight cable for co nnection between a hub and the Ethe rnet module. (When connecting an external device to the Ethernet module [...]

  • Seite 29

    3 - 1 SPECIFICATIONS 3 3 - 1 3 MELSEC-F 3 SPECIFICA TIONS This section exp lains the Ethernet m odule performan ce specifications and transmission specifications. For the genera l specificat ions, refer to the INST ALLA TION MANUAL of FX 3U -ENET and the User’s Manual of the PL C main unit. 3.1 Performance S pecifications The following explains t[...]

  • Seite 30

    3 - 2 SPECIFICATIONS 3 3 - 2 3 MELSEC-F *1 Ethernet modules V . 1.10 or later support port numbers 1 to 65535. The port number is fixed t o "25" in Ethernet modules earl ier than V . 1.01. *2 Ethernet modules V . 1.10 or later support the authentication function. The port number is fixed without aut hentication in Et hernet modules earlie[...]

  • Seite 31

    3 - 3 MELSEC-F SPECIFICATIONS 3 3 - 3 3.2 D ata Codes for Communication This sectio n explains th e data codes us ed in the com munication b etween the Ethernet module and the ex ternal de vice or the PLC. (1) The dat a codes used while commu nicating are listed below . 1) Ethernet module External device Data ca n be communicated by selecting eithe[...]

  • Seite 32

    3 - 4 MELSEC-F SPECIFICATIONS 3 3 - 4 2) Ethernet module PLC Data is sent and received in binary co de. (2) When communicating using ASCII code, 1-by te binary co de data is auto matically converted int o 2-byte ASCII code da ta and then transmitted. (3) The a mount of da ta that can be c ommuni cated at one time between the Ethernet module and an [...]

  • Seite 33

    3 - 5 MELSEC-F SPECIFICATIONS 3 3 - 5 3.3 R elationship between the External De vices and Additional Functions for Each Communication Function This sectio n explains wh ich external devices data commu nication can b e perform ed with and which additional function s can be used fo r each function. (1) Communicability with external devices usi ng var[...]

  • Seite 34

    3 - 6 MELSEC-F SPECIFICATIONS 3 3 - 6 3.4 E thernet Module Function List This section shows a list of Ethernet module functions. (1) Basic functions of the Ethernet module The Ethernet module can perform the communications shown in the t able below via TCP/IP or UDP/IP communication. (2) Additional functions of the Ethernet module The following t a[...]

  • Seite 35

    3 - 7 MELSEC-F SPECIFICATIONS 3 3 - 7 3.5 L ist of Setting It ems for Ethernet Modules The following ta ble lists the p arameter settin g items that are set using Etherne t Module. : Must be set when the applicable funct ion is used. : Set as needed : Setting is not required. *1 The meanings of t he abbreviation s us ed in the t able above are as f[...]

  • Seite 36

    3 - 8 MELSEC-F SPECIFICATIONS 3 3 - 8 3.6 L ist of Applications and A ssignments of the Buff er Memory Data tr ansmission/reception betwe en Ether net Module and PLC is performed via the Ethernet Module buf fer memory (hereinafter called BFM) . Reading/wr iting data in the buffer memory from the PLC must be performe d by the FROM/TO instructions (i[...]

  • Seite 37

    3 - 9 MELSEC-F SPECIFICATIONS 3 3 - 9 (2) Assignments of the buf fer memory A buffer memory consists of 16 bits per ad dress. <Bit configuration diagram> The following shows the buf fer memory addresses. (a) Initial pr ocessing parameter (BF M #0 to 31) (Continues on the next p age) *1 Attrib ute R : Read, W : Write, — : Use pro hibited *2 [...]

  • Seite 38

    3 - 10 MELSEC-F SPECIFICATIONS 3 3 - 10 (Continued from the previous p age) BFM number Attribute Applica tion Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decim al (Hexadecimal) 25 (19 H ) R/W Flash ROM control Flash ROM writing control area Flash ROM writing control 0000 H : Normal status 9872 H : Write command for con[...]

  • Seite 39

    3 - 11 MELSEC-F SPECIFICATIONS 3 3 - 11 (b) Communica tion p arameter setting ar ea (BFM #32 to 102) (Continues on the next p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 32 (20 H ) R/W Communication parameters setting area Connection usage setting area Connect[...]

  • Seite 40

    3 - 12 MELSEC-F SPECIFICATIONS 3 3 - 12 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 40 (28 H ) R/W Communication parameters setting area Communication address setting area Connection No. 1 Local stat ion Port No. 0 (0 H ) Section[...]

  • Seite 41

    3 - 13 MELSEC-F SPECIFICATIONS 3 3 - 13 (c) Communicati on status storage area (BFM #103 to 226 ) (Continues on the next p age) *1 Initial processing writes IP and Et hernet address. BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 103 to 104 (67 to 68 H ) — Communica[...]

  • Seite 42

    3 - 14 MELSEC-F SPECIFICATIONS 3 3 - 14 (Continued from the previous p age) *1 It varies af ter initialization. *2 V alues written to BFM #202 will become active the next time the module is powered ON. (The value returns to 0 when each running mode execut ion is complete.) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Fl[...]

  • Seite 43

    3 - 15 MELSEC-F SPECIFICATIONS 3 3 - 15 (d) Error log par tition area (BFM #227 to 51 1) (Continues on the next p age) BFM number Attribute Appli cation Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 227 (E3 H ) R Error log area Number of error occurrences 0 (0 H ) Secti on 1 1.4 228 (E4 H ) R Error [...]

  • Seite 44

    3 - 16 MELSEC-F SPECIFICATIONS 3 3 - 16 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 376 to 377 (178 to 179 H ) R Error log area S tatus fo r each protocol IP Received IP packet co unt 0 (0 H ) Section 1 1.3 378 to 379 (17A to 17B[...]

  • Seite 45

    3 - 17 MELSEC-F SPECIFICATIONS 3 3 - 17 (e) Router relay p arameter setting ar ea (BFM #512 to 1599) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 512 to 513 (200 to 201 H ) R/W Router relay para met er setting area Sub-net mask 0 (0 H ) Section 5. 3 514 to 515 (202 [...]

  • Seite 46

    3 - 18 MELSEC-F SPECIFICATIONS 3 3 - 18 (f) Open/close contro l (BFM #1600 to 1663) (Continues on the next p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 1600 (640 H ) R/W Re- initialization • Write value Re-initialization r equest 0001 H : Re-initialization [...]

  • Seite 47

    3 - 19 MELSEC-F SPECIFICATIONS 3 3 - 19 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 1610 (64A H ) R/W For fixed buf fer communicati on Fixed buffer communication Transmission/ reception request/Execution result When sending reque[...]

  • Seite 48

    3 - 20 MELSEC-F SPECIFICATIONS 3 3 - 20 (g) Fixed buf fer area (BFM #1664 to 9855) BFM number Attribute Application Name Initial value Decim al (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 1664 (680 H ) R/W Fixed buffe r data area Fixed buffer No. 1 Data length 0 (0 H ) Chapter 6, Chapter 7 1665 to 2687 (681 to A7F H ) R/W F[...]

  • Seite 49

    3 - 21 MELSEC-F SPECIFICATIONS 3 3 - 21 (h) Mail send p arameter settings (BFM #9856 to 14499) (Continues on the next p age) BFM number Attribute Application N ame Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 9856 to 9887 (2680 to 269F H ) R/W Shared area for e-mail buf fers Local station mail address ([...]

  • Seite 50

    3 - 22 MELSEC-F SPECIFICATIONS 3 3 - 22 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 10333 (285D H ) R/W Mail sending command • Write value Mail sending instruction (0001 H ) • Read value Returns to "0000 H " when ma[...]

  • Seite 51

    3 - 23 MELSEC-F SPECIFICATIONS 3 3 - 23 (i) Mail rece ive param eter settings (BFM #14500 to 20479) BFM number Attribute Applicati on Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 14500 (38A4 H ) R/W Mail receiving command • Write val ue Receive mail instructio n (0001 H ) • Read value Initial s[...]

  • Seite 52

    3 - 24 MELSEC-F SPECIFICATIONS 3 3 - 24 (j) Connection status storage a rea (BFM #20480 to 22639) BFM number Attribute Applica tion Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 20480 (5000 H ) R Connection status storage area Connection status information area Open complete signal 0: Open i ncomple[...]

  • Seite 53

    3 - 25 MELSEC-F SPECIFICATIONS 3 3 - 25 (k) E-mail status stor age area (BFM #2264 0 to 31999) (Continues on the next p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 22640 (5870 H ) R E-mail status storage area Receive Number of mails remaining on the server 0 ([...]

  • Seite 54

    3 - 26 MELSEC-F SPECIFICATIONS 3 3 - 26 (Continued from the previous p age) (Continues on the next p age) *1 The timestamp fo r an email that had a communication error with the mail server is store d in BCD code in the following manner . BFM number Attribute Applica tion Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Deci[...]

  • Seite 55

    3 - 27 MELSEC-F SPECIFICATIONS 3 3 - 27 (Continued from the previous p age) (Continues on the next p age) *2 The mail function of BFM#24320 to #24575 is supported in Ethernet modules V . 1.10 or later . (This area is inaccessible in V 1.01 or earli er because it is handl ed as t he system area.) BFM number Attribute Applica tion Name Initial value [...]

  • Seite 56

    3 - 28 MELSEC-F SPECIFICATIONS 3 3 - 28 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecim al)) Flash ROM save Reference section Decimal (Hexadecimal) 31800 (7C38 H ) R/W Error information clear Error information to be clea red Designates the error information to be cleared 0000 H : Clears ini[...]

  • Seite 57

    4 - 1 SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 1 4 MELSEC-F 4 SETTINGS AND PROCEDURES PRIOR T O OPERA TION This chapter explains the settings and pr ocedur es required prior to operating the Ethernet module in a system. 4.1 L oading and Installation This sectio n explains pr ecautions f or Et hernet module han dling from unp a cking to inst[...]

  • Seite 58

    4 - 2 SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 2 4 MELSEC-F 4.1.2 I nstallation environment This section explains the installation en vironment for the PLC. When installing the PLC, the following environment s must be avoided: • Locations where the ambient temperature exceeds the range of 0 to 55 . • Locations where the ambi ent humidit[...]

  • Seite 59

    4 - 3 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 3 4.2 S ettings and Procedures Prio r to S tarting the Operation The following shows a flow of the procedur e that is re quired prior to operating: POINT (1) When the p arameter settings are added or modified using the FX Configurator-EN, the settings di f fers depending on the connect[...]

  • Seite 60

    4 - 4 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 4 Important (1) Do not write any data in the "System area" of Ethernet m odule buf fer memory . (2) When sta tus control (such as remote RUN/STOP) fro m a external device is used for the PLC, the user should se lect "Always wait fo r OPEN" beforehand using the setti[...]

  • Seite 61

    4 - 5 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 5 4.3 C omponents of the Ethernet Module This section shows the component s of the Ethernet module. Name Description 1) LED display Refer to the content s of the LED displays (1). 2) 10BASE-T/100BASE- TX connector (RJ45) Connector for connecting th e Ethernet module to the 10BA SE-T/10[...]

  • Seite 62

    4 - 6 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 6 (1) LED display contents (*1) *1 Refer to Subsection 1 1.1.1 for causes of error displays and the correspond ing corrective actions. *2 The [ERR.] LED turns on in the following cases: • When the parameter wr itten is incorrect. • When the checksum of the para meter written is not[...]

  • Seite 63

    4 - 7 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 7 4.4 C onnecting to the Network The following explains how to connect the Ethernet module to the 100BASE-TX/ 10BASE-T networks. Some precautions that should be obse rved while connecting the Ethernet module are also shown below . Pay close attention to safety and use the Ethernet modu[...]

  • Seite 64

    4 - 8 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 8 4.4.1 Connecting to the 10B ASE-T/100BASE-TX network This sectio n explains ho w to connect the Etherne t module to t he 10BASE-T , 100BASE-TX network. The following shows the connection diag ram for the twisted pa id cable. <Opera ting procedur e> (S tep 1) Connect the twisted[...]

  • Seite 65

    4 - 9 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 9 4.5 E thernet Module Setting Setting the Ethernet mod ule as a network module. The settings found must always be se t in order to use the Ether net module. (1) "Operational settings" (Details are explained in Section 4.6) This is for setting common ite ms for when other mod[...]

  • Seite 66

    4 - 10 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 10 4.6 O perational Settings This section explains how to set the operations p arameters. (1) Communication dat a code (BFM#24 b1) (a) Select the format of the communicati on data when commu nicating with an external device . (b) For more det ails on the data communication codes, see [...]

  • Seite 67

    4 - 11 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 11 (2) TCP Existence confirma tion setting (BFM #24 b4) Select the existence check method for TCP commun ication. For the existence check function, refer to Subsection 5.2.2. NOTE When adjusting settings with FX Configurator-EN, select "Operating Settings" at the initial scr[...]

  • Seite 68

    4 - 12 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 12 (4) Initial Timing (BFM#24 b8) (a) Select the timing to open conn ections for w hich TCP-Passiv e open or UDP open are sele cted with th e "Open set tings" parameter (*1). *1 For more details on the open set tings, see Section 5.5 "Open Sett ings". *2 If the seq[...]

  • Seite 69

    4 - 13 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 13 (5) IP Address settings - IP address (B FM #0 to 1) (a) Set the IP address of the local station according to the sp ecified input form at (decimal or hexadecima l). It should be set so that the local station Ethernet module and the communicating external device have the same class [...]

  • Seite 70

    4 - 14 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 14 4.7 S elf-Diagnostic T ests This section expl ains the self-diagn ostic tests for checking the hardwa re and transmission and reception fu nction of the Ethernet mo dule. 4.7.1 Self loopback test The following explains the self loopb ack test that is used to check the hardware incl[...]

  • Seite 71

    4 - 15 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 15 4.7.2 Hardware test (H/W T est) This sectio n explains th e RAM and RO M test s for the Ethern et module. The procedure for the har dware test is as shown in the table be low . The test results are judg ed from the LED displays on the front of the Eth ernet module. : Lit : Off The [...]

  • Seite 72

    4 - 16 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 16 4.8 M aintenance and Inspection This section explains the ma intenance and ins pection as well as the installing and uninstalling of the Ethernet module. 4.8.1 Maintenance and inspection The Ethernet module does not need to be in spected for anything pa rticular other than checking[...]

  • Seite 73

    4 - 17 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 17 4.8.2 Installing and uni nstalling the module Before installing or uninst a lling the Ethernet module, make sure to read Section 4.1, "Handling Precautions" thoroug hly , ensure the safety of the installation, and handle the module properly accor ding to the instructions.[...]

  • Seite 74

    5 - 1 COMMUNICATION PROCEDURE 5 5 - 1 5 MELSEC-F 5 COMMUNICA TION PROCEDURE This chapter gives an overview of the co mmunication proced ure using the Ethernet module, as well as the requir ed initial processing of the Ethernet prior to dat a communication and the open processing fo r commu nication with an external device. The sequence program can [...]

  • Seite 75

    5 - 2 COMMUNICATION PROCEDURE 5 5 - 2 5 MELSEC-F NOTE The following communication can be perfor med with an open device on other end. • Communication using MC protocol • Sending/receiving in fixed buf fer communication (procedure exist s) Request from an external device (receive) Header Ethernet IP TCP Sub header Application data Response to th[...]

  • Seite 76

    5 - 3 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 3 5.2 I nitial Processing This sectio n explains th e initial process ing of the Et hernet modu le. 5.2.1 Initial processing The initial processing enables dat a communication with an external device by setting the parameters required fo r data communicat ion via the Ethernet mo dule. Set the following p[...]

  • Seite 77

    5 - 4 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 4 5.2.2 Initial settings This section explains the initial s ettings. *1 Details ar e explained in Section 10.6 . Setting item name BFM number [Decima l] Description of setting Setti ng range/options T imer setting TCP ULP timer 4 Set the time of packet e xis tence at TCP data transmissio n. 2 to 32767 T[...]

  • Seite 78

    5 - 5 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 5 (1) Timer setting - TCP ULP timer (BFM#4) (a) This item sets the time of p acket existence during TCP data sending. This timer is p assed through the parameter whe n TCP opens or dat a is sent. (b) Set the value in the range fr om 2 to 32767. (c) T imer s etting = setting value 500 ms (2) Timer setting[...]

  • Seite 79

    5 - 6 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 6 (5) T imer setting - IP assembly timer (BFM#8) (a) Communicati on data may be divided on the IP level due to the buf fer restriction at the sendin g or receiving station. (b) Set the value in the range fr om 1 to 32766. (c) T imer s etting = setting value 500 ms (6) T imer setting - Respons e monitorin[...]

  • Seite 80

    5 - 7 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 7 NOTE (1) Set the value of ea ch timer on the Etherne t module sid e such that th e following relations are met. • • Furthermore, when con necting a line using Mit subishi products, you should make sure that both nodes have the same settings. (2) Set t he value of each timer on the ex ternal device [...]

  • Seite 81

    5 - 8 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 8 TCP ULP timer value TCP end timer value = TCP resend timer value = (Each timer value should be identical.) (3) When communication errors occur , the setting value should be changed to increase the nu mber of retries . The number of retries is obt ained by using the following equation: (In case of the i[...]

  • Seite 82

    5 - 9 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 9 1) Checking by KeepAlive This method is used for a conne ction opened via the TCP/IP protocol. The Ethernet module perfor ms an existence check by sending an existence check ACK message to a remote device with which communication has not been performe d for a certain perio d of time and waiting to see [...]

  • Seite 83

    5 - 10 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 10 5.2.3 Re-initialization Re-initialization is performe d in order to place the Ethernet module into it s startup status without actua lly restartin g the PLC. Re-initializatio n of the Ethernet module can be perfor med in a sequence prog ram. The purpo ses of and how to prog ram the re -initialization[...]

  • Seite 84

    5 - 11 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 11 (2) Programming and timi ng for re-initialization The programming and timing for re -initia lization is shown below: •F o r F X 3U /FX 3UC Series PLCs Program example for the unit No. 1 1) It is confirmed whether the initial processing has been completed normally . 2) All data comm unication curr e[...]

  • Seite 85

    5 - 12 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 12 (3) Operation for re-initialization Operation for re-in itialization dif fers as follows, depending on the val ue written to BFM#1600. *1: When re-readin g the flash ROM, the re-i nitial ization is performed in the same status as when the pow er supply is turn ed on. NOTE It is possible to change the[...]

  • Seite 86

    5 - 13 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 13 5.3 R outer Relay Parameter This sectio n explains th e router r elay parameter . NOTE When making settings with the FX Conf igurator-EN, sele ct [Router Relay Parameters] from the initial screen and adjust the settings at the [Ethernet Route r Relay Parameter Settings] screen. (1) Router relay f unc[...]

  • Seite 87

    5 - 14 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 14 (2) Subnet mask pattern (BFM#512, 513) (a) Set the subnet mask. *1 (Setting range: C0000000 to FFFF FFFC H ) Consult the network administrator for the setting. (b) When not using the subn et mask, set any of the following table value s according to the class. *1 Ethernet networks include small-sca le[...]

  • Seite 88

    5 - 15 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 15 5.4 Confirming the Completion of the Initial Processing The initial processing for the Ethernet module completes by selectin g re-initialization, then turning the power ON again, or re-initializing via buffer memor y operations after parameters a re written to the Ethernet module. (When the processin[...]

  • Seite 89

    5 - 16 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 16 5.4.1 PING command (Personal computer Ethernet module) The following example illustra tes how to confirm the co mpletion of the initial processi ng by issuing th e PING comma nd to the local s tation's Ethernet mo dule from an external device connected on the same Ethern et network. (I n the exa[...]

  • Seite 90

    5 - 17 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 17 5.4.2 Loop back test (Communi cation using MC protocol) The loop back test can be performed with commu nication using MC protocol in order to check the completion st atus of the initia l processing for the target Ether net module. The following is an overview of the loop back test for communica tion [...]

  • Seite 91

    5 - 18 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 18 5.5 Open Settings This sectio n explains th e open set ting. A sequence progr am can perform open p roc essing (est ablishing connection ) with up to a maximum of 8 external device stations Once a connection is establish ed with an external device, it is possible to communicate using MC protocol, fix[...]

  • Seite 92

    5 - 19 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 19 (2) Open system (connection numbers 1 to 8; BFM#32 to 39 b15, b14) (a) Select the connection open syste m for each connectio n for which "TCP" is selected in "(1) Protocol". If "UDP" is se lected, the specificatio n of this item is not required . *1 Regardless of the ini[...]

  • Seite 93

    5 - 20 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 20 (3) Fixed buffer (connection numbers 1 to 8; BFM#32 to 39 b0) (a) Here it is selected whether the fixed buf fer corresponding to each applicable connection number will be used for sending or receiving when communicating using the fixed buf fers. (b) When both sending an d receiving are pe rformed wit[...]

  • Seite 94

    5 - 21 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 21 (5) Pairing open (connection numbers 1 to 8; BFM#32 to 39 b7) (a) Select whether or not the Ether net module's receivin g and sending connections are made into one pair an d connected to one po rt of an ex ternal device when using fixed buf fer communication (Either one among [Procedure ex ist],[...]

  • Seite 95

    5 - 22 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 22 (7) Local station Port No. (connection numbers 1 to 8; BFM#40 , 47, 54, 61, 68, 75, 82, 89) (a) In this item the port number of each connection for the Etherne t module is set. (b) The setting values are designated in the range from 1025 to 5548 and from 5552 to 65534. Set por t numbers that are not [...]

  • Seite 96

    5 - 23 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 23 (9) Destination Port No. (connection numbers 1 to 8; BFM#43 , 50, 57, 64, 71, 78, 85, 92) (a) Set th e port numb ers of the external de vices for eac h connectio n. (b) The port numbers of the external devices are set in the range from 1025 to 65534. (c) Set the port numbers for the exter nal de vice[...]

  • Seite 97

    5 - 24 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 24 POINT Set parameter s according to the open meth od to be used for open connection. Communication system open system TCP UDP Active Passive Parameter ARP function of external device Un-p assive Full- passi ve ARP function of external device Ye s N o Ye s N o Communication address Local station Port N[...]

  • Seite 98

    5 - 25 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 25 5.6 O pen Processing/Close Pr ocessing of t he Connection This sectio n explains th e open pr oces sing/close processing using sequence programs. (1) Open processing (a) The purpose of the op en processing is to est ablish a connection with an external device in order to per form the following forms [...]

  • Seite 99

    5 - 26 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 26 (2) Close processing (a) The purpose of the close processin g is to disconnect (cancel) th e connection with the external device est ablis hed by open processing me ntioned previously . (b) The close processing is used when terminating a co nnection with an external device, changing an external devic[...]

  • Seite 100

    5 - 27 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 27 5.6.1 Active open processing/close processing This sectio n explains the proced ure for opening and closing a connection with an external device from the Ethernet module. •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 <<Open processing for connectio n No.1>> M8000[...]

  • Seite 101

    5 - 28 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 28 1) After communicatin g the paramete r settings, confirm the no rmal completion of the Ethernet modul e initial processing. (Initial completion signal BFM#27 "0 001 H ") 2) Confirm that the E thernet mo dule and hub are connected. (B FM#28 b7:ON) 3) S tart th e open pr ocessing writin g wit[...]

  • Seite 102

    5 - 29 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 29 *1 Processing when the open processin g is abnormally completed (TCP) When opening from the Etherne t module under a normal situa tion, if the Ethernet mod ule sends a SYN, the external de vice returns an ACK and a SYN. However , if the Ethernet module sends a SYN and th en the external device return[...]

  • Seite 103

    5 - 30 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 30 1) The open request signal tu rns of f by writing "8000 H " to the BFM#1602. 2) The E thernet mo dule exec utes the clo se processin g. 3) The Ethernet module sends a FIN request to the extern al device. 4) The external device sends back FIN and ACK messages in reply to the FIN request sent[...]

  • Seite 104

    5 - 31 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 31 Program example This example explains a prog ram for open processing/close processing when Active open is selected in the Open s ystem setting. (1) Execution environment for the program example (a) The Ethernet module i s connected to the second special module . (The unit number is setting 1) (b) The[...]

  • Seite 105

    5 - 32 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 32 •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 X000 M100 M103 X000 M102 [= D100 H5 ] ] H10 D100 [= ] H0 D100 [= [MOV D100 (M100 (M101 (M102 (M103 ] ) [MOVP H0 ] [MOVP K4096 ] [MOV K8192 ] [END ] [MOVP H1 ] [MOVP H8000 ] ) ) ) H0A6155DF [DMOVP ] U1 G1602 Open request M0 Initi[...]

  • Seite 106

    5 - 33 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 33 5.6.2 Passive open processing/close processing This sectio n explains the proced ure for ope ning and clos ing a connec tion with th e Ethernet module via an external device. The operations of Passive open proc essi ng/close processing dif fer depending on whether "Always wait for OPEN" or [...]

  • Seite 107

    5 - 34 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 34 1) After the parameters ar e sent, the normal completion of the Ethernet module initial processing is confirme d (Initial normal completion signal BFM#27 "0001 H ") After the initial pr ocessing is no rm ally completed, the connection is placed in the open allowed status an d the Ethernet m[...]

  • Seite 108

    5 - 35 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 35 •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 X000 M100 M103 X000 M102 [= D100 H15 ] [= D100 H10 ] [= D100 H5 ] [= D100 H3 ] ] H0 D100 [= [MOV D100 X0:ON Open X0:OFF Close (M100 (M101 (M102 (M103 ] [MOVP H1 ] ) [INCP D0 ] [INCP D1 ] [INCP D2 ] [END ] [MOVP H8000 ] ) ) ) U1 [...]

  • Seite 109

    5 - 36 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 36 *1 If an open request (SYN) received af ter the normal completi on of an initial proces sing and befo re the Ethe rnet module is placed in t he open acknowledge enabled st atus, an error is generated, an d the Ethernet module se nds a connec tion forced close (RST) . 1) After communicatin g the param[...]

  • Seite 110

    5 - 37 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 37 NOTE (1) If the settings of the connection need modifyin g, the modifications should be done before writing th e open instruction to the buffer memory. (2) Once open processing is exe cuted, an open request cann ot be canceled befor e the open processing is completed. Write the close instruction to t[...]

  • Seite 111

    5 - 38 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 38 Program example This example explains a prog ram for open processing/close processing when Unpassive open is selected in the open system setting. (1) Execution environment for the program example (a) The Ethernet module i s connected to the second special module . (The unit number is setting 1) (b) T[...]

  • Seite 112

    5 - 39 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 39 •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 X000 M100 M103 X000 M102 [= D100 H15 ] [= D100 H10 ] [= D100 H5 ] [= D100 H3 ] ] H0 D100 [= [MOV D100 (M100 (M101 (M102 (M103 ] [MOVP H1 ] ) [INCP D0 ] [INCP D1 ] [INCP D2 ] [END ] [MOVP H8000 ] ) ) ) U1 G1602 Open request Cance[...]

  • Seite 113

    5 - 40 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 40 5.6.3 UDP/IP open processing/close processing The following explains the UDP/IP open proce ssing. The operations of the open processing/clo se processing in U DP/IP differ depen ding on whether "Always wait for OPEN" or "Do not wait for OPEN" is selected in the initial timing sett[...]

  • Seite 114

    5 - 41 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 41 •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 X000 [= D100 H15 ] [= D100 H10 ] [= D100 H5 ] [MOV D100 ] [INCP D0 ] [INCP D1 ] U1 G1602 Open request OPEN instruction/ status Open abnormal processing Open normal completion signal M0 Initial completion status M8000 [MOV K4M1 1[...]

  • Seite 115

    5 - 42 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 42 1) After communicatin g the paramete r settings, confirm the no rmal completion of the Ethernet modul e initial processing. (Initial normal completion signal (BEF# 27) : 0001 H ) 2) S tart the open pro cessing by writi ng 0001 H to the BFM#1602. 3) The E thernet m odule exec utes the open proc essing[...]

  • Seite 116

    5 - 43 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 43 5.7 Pairing Open The following explains communication using th e p aring open method via the Ethernet module. 5.7.1 Pairing open Pairing open is an opening meth od for estab lishing a connectio n in which the local station an d the external device use a single port for each, by p airing the receiving[...]

  • Seite 117

    5 - 44 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 44 5.7.2 Example of pairing open settings This section explains the settin gs in order to commun icate in the p airing open method by giving an ex ample. • Connection No. 1 and 2 are used. (When connection No. 1 is specified at pa iring open settings, connection No. 2 is automatically used as pairing.[...]

  • Seite 118

    5 - 45 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 45 (7) Local station Po rt No. (BFM#40, 47) Set this for the receiving connection for re ceivin g only . (Setting is not require d for the sending conn ection.) Set the port number upo n consul ting a network administrator . (8) Destination IP address (BFM#41 to 42, 48 to 49) (a) If the setting is not r[...]

  • Seite 119

    5 - 46 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 46 5.8 Hub Connection S tat us Monitor Function The curren t connectio n status of the Et hernet module and hub, the transmission speed, and the numbe r of times the Ether net module detected disconnection can be checked at the following buffer me mory addresses. (1) Hub connection st atus area (BFM#201[...]

  • Seite 120

    6 - 1 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 1 6 MELSEC-F 6 FIXED BUFFER COMMUNICA TION (WITH THE PROCEDURE EXIST CONTROL METHOD) This chapter explains how the PLC and externa l device communicate in a 1:1 mode using the fixed buf fers (with the procedure exist control method) of the Etherne t module. 6.1 C ontro[...]

  • Seite 121

    6 - 2 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 2 6 MELSEC-F (3) At data sending/r eceiving, the Et hernet module processes the following. (a) When sending dat a In response t o the fixed buffer communicat ion transmis sion reques t (write "0001 H " to BFM #1610 to 1617 ), the Ethernet module sends the dat[...]

  • Seite 122

    6 - 3 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 3 6.2 S ending Control Method This section explains the control me thod wh en dat a is sent from the Ethernet mod ule to an external device usin g the fixed buf fer No. 1 and the area corre sponding to connection No. 1 a s an example. •F o r F X 3U /FX 3UC S[...]

  • Seite 123

    6 - 4 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 4 1) Confirm the normal completion of the initial processing. 2) Confirm that the link status is no rmal between the Etherne t module and the connected HUB. 3) Confirm the normal completion of the open processing of co nnection No. 1 4) Write the send da ta wo[...]

  • Seite 124

    6 - 5 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 5 POINT The destination setting (see Section 5.5) for a conn ection whos e parameters ar e set in FX Configurator -EN becomes valid when the open completion si gnal (BFM#20480 corr esponding bit) of the Ethern e t module switches from of f to on. The setting a[...]

  • Seite 125

    6 - 6 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 6 6.3 R eceiving Control Method This sectio n explains th e control m ethod when t he Ethernet m odule rece ives data from an external device. 6.3.1 Receive processing with the main program This sectio n explains the receiving process to be perform ed with the[...]

  • Seite 126

    6 - 7 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 7 1) Confirm the normal completion of the open processing of co nnection No. 2. 2) Upon re ceiving data from the d esignated ex ternal devic e (set in the open processing), the Ethernet module processes th e following. • S tores the received data to the fixe[...]

  • Seite 127

    6 - 8 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 8 6.4 Data Format When communicating between the Ethernet m odule and an exte rnal device, th e data format explained be low is used. The communication dat a consists of a "header" and "application dat a" as follows: 6.4.1 Header The header[...]

  • Seite 128

    6 - 9 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 9 6.4.2 Application data As shown below , the data code in the application data can be expressed in either binary code or ASCII code. Switching between binary code an d ASCII code is performed via the communication dat a code setting (BFM #24 b1 OFF: binary co[...]

  • Seite 129

    6 - 10 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 10 (2) Subheader The format of the subheader is as shown below . The user does not need to set the subheader when using the Ethe rnet module since the Ethernet module add s and deletes it. b7 b6 b5 b4 b3 b2 b1 b0 Command/response flag 11 00000 Command/respons[...]

  • Seite 130

    6 - 11 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 11 (3) Data length setting This value indicates the dat a size of the text (command) section. (4) T ext (command) The format of the com mand/res ponse when c ommunicatin g using fixe d buffers is configured as follows. (a) Communicati on using binary code POI[...]

  • Seite 131

    6 - 12 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 12 (b) Communicati on using ASCII code (Example) (5) End codes For more det ails on the end codes added to a respon se when communicating using fixed buf fers, see Subsection 1 1.4.1. End codes are stored in the communication status storage area of the buffer[...]

  • Seite 132

    6 - 13 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 13 6.5 Programming This sectio n explains th e program ming metho d when the Et hernet modu le communicates with an external device using fixed buf fers and the procedure exist control method. 6.5.1 Precautions when creating programs (1) In orde r to commu ni[...]

  • Seite 133

    6 - 14 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 14 6.5.2 Fixed buffer communic ation program example (with the procedure e xist control method) This section explains the programmin g method in order to communicate dat a (procedure exist control method) with an external device u sing the fixe d buffers. (1)[...]

  • Seite 134

    6 - 15 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 15 (b) Receiv e program (FX 3U -2nd statio n) 1) Connection No. 1 is used to process th e fixed buf fer receiving in the main program. 2) The unit number specified at the sequen ce program and FX Configur ator-EN is 0. 3) Make Operational Settings in the foll[...]

  • Seite 135

    6 - 16 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 16 (2) Outline of the program example (a) Send progra m (Ethernet module-1 st station) 1) After setting each p arameter with FX Configurator-EN o r a sequence program and writing to the Ethern et module, select re-initial, power ON the module again, or confir[...]

  • Seite 136

    6 - 17 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 17 (Send program) (See Subsection 5.6.1) •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 0 Open processing program M8000 M200 X002 M307 M201 M202 M300 D101.2 D101.3 [= H5 ] [MOV K4M300 (M200 (M202 (M201 ] [MOVP K32 ] D1000 [BMOVP K32 ] )[...]

  • Seite 137

    6 - 18 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 18 (Receive program) •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 0 M8000 [MOV U0 G1610 D100 ] [MOV H2 ] [INCP D102 ] [BMOV D1000 D101 ] [MOV U0 G1664 D101 ] [= D100 H1 ] [= D100 H8 ] [END ] * <<Storing the data received from [...]

  • Seite 138

    7 - 1 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 1 7 MELSEC-F 7 FIXED BUFFER COMMUNICA TION (WITH THE NO PROCEDURE CONTROL METHOD) This chapter explains how the PLC and exte rnal device communicate using the fixed buffer s (with the no procedure control me thod) via the Ether net module. 7.1 C ontrol Method The followin[...]

  • Seite 139

    7 - 2 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 2 7 MELSEC-F (2) Data can be communicated with the following external devices. • Devic e on the Ethe rnet to which the Ethern et module is c onnected. • Devices connected with the router relay function (see Section 5.3) As shown in the diagram below , when using each [...]

  • Seite 140

    7 - 3 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 3 (3) At data sending/r eceiving, the Et hernet module processes the following. 1) When sending dat a The fixed buf fer communication tr ansmission reque st (writing "0001 H " in BFM#1610 to # 1617) allows the fixed buf fer data stored in the fixed buff[...]

  • Seite 141

    7 - 4 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 4 7.2 S ending Control Method This section explains the control me thod wh en dat a is sent from the Ethernet mod ule to an external device using fixe d buffer No. 1 and the area corresponding to connection No. 1 a s an example. •F o r F X 3U /FX 3UC Series PLC[...]

  • Seite 142

    7 - 5 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 5 1) Confirm normal completion o f the initial processing. 2) Confirm that the E thernet mo dule is conn ected to th e hub. (BFM#28 b7:ON) 3) Confirm the normal completion of the open processing for connection No. 1. 4) Write the byte count for send da ta an d th[...]

  • Seite 143

    7 - 6 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 6 7.3 R eceiving Control Method This sectio n explains th e control m ethod when t he Ethernet m odule rece ives data from an external device. 7.3.1 Receive processing with the main program This sectio n explains the receiving process to be perform ed with the ma[...]

  • Seite 144

    7 - 7 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 7 1) Upon re ceiving data from the d esignated ex ternal devic e (set in the open processing), the Ethernet module processes th e following. • S tores the received data to the fixed buf fer (No. 2) area. (Area beginning fr om the head addr ess of the t arget fi[...]

  • Seite 145

    7 - 8 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 8 7.4 Data Format When communicating between the Ethernet m odule and an exte rnal device, th e data format explained be low is used. The communication dat a consists of a "header" and "application dat a" as shown below . (1) Header The header[...]

  • Seite 146

    7 - 9 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 9 7.5 Programming This sectio n explains th e program ming metho d when the Et hernet modu le communicates with an external device using fixed buf fers and the no-procedure control method. 7.5.1 Precautions when creating programs (1) In order to communicate using[...]

  • Seite 147

    7 - 10 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 10 7.5.2 Fixed buffer communication program ex ample (with the no procedure control method) This section explains the programming method in orde r to communica tion dat a (through the no procedure contro l method) with an ex ternal de vice using the fixed bu ffe[...]

  • Seite 148

    7 - 11 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 11 (b) Receiv e program (FX 3U -2nd station) 1) Connection No. 2 is used to process the fixed buf fer receiving. 2) The unit number specified at the sequen ce program and FX Configur ator-EN is 0. 3) Make Operation se ttings in the following manner . Communicati[...]

  • Seite 149

    7 - 12 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 12 (2) Outline of the program example (a) Send progra m (FX 3U -1st station) 1) After setting each p arameter with FX Configurator-EN o r a sequence program and writing to the Ethernet module, power ON th e module again, or confirm that the initial processing is[...]

  • Seite 150

    7 - 13 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 13 (Send program) •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 0 M8000 X002 M300 M307 M201 D101.2 D101.3 M202 M200 D1000 [BMOVP K16 ] [MOVP K32 ] [MOV K4M300 ] [MOVP H1 ] [MOV U0 G1664 D101 ] [= H5 ] ] [END ) (M202 ) (M201 ) (M200 * <[...]

  • Seite 151

    7 - 14 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 14 (Receive program) •F o r F X 3U /FX 3UC Series PLCs Program example for the unit No. 0 U0 G2688 Received data count M8000 [ADD H1 D101 Received data count ] [MOV D100 Receiving status ] [MOV H2 ] [MOV D101 ] [INCP D102 Receive abnormal processing ] [= D100[...]

  • Seite 152

    8 - 1 COMMUNICATION USING MC PROTOCOL 8 8 - 1 8 MELSEC-F 8 COMMUNICA TION US ING MC PROT OCOL This chapter gives an overvi ew of the MC pr otocol. NOTE The frame type of MC protocol (data comm unication m essages) us ed by the external device to access the PLC via this pr oduct is equiva lent to A compatible 1E frame. 8.1 D ata Communication Functi[...]

  • Seite 153

    8 - 2 COMMUNICATION USING MC PROTOCOL 8 8 - 2 8 MELSEC-F (2) Remote control of the PLC This function executes remote RUN/STOP operations. Remote operations of the PLC can be performed from the external device side. *1 Time required for commun ication in binar y code is shorter be cause the amo unt of commun ication data is approximately a half of w[...]

  • Seite 154

    8 - 3 MELSEC-F COMMUNICATION USING MC PROTOCOL 8 8 - 3 8.1.3 Access T i ming on the PLC Side The following diagram illustrates the acc ess timing on the PLC side when an external device accesses the PLC via the Ethernet mo dule. 1) A command message is transmitted from the extern al device to the PLC side. 2) Upon receiving a command me ssage from [...]

  • Seite 155

    8 - 4 MELSEC-F COMMUNICATION USING MC PROTOCOL 8 8 - 4 8.1.4 PLC setting for perf orming data communication Data commu nication via MC protocol is e nabled by adjusting the followi ng settings using FX Configurator-EN and writing the p arameters to the Ethernet module. 1) Operational settings (see Section 4.6.) 2) Initial settings (see Section 5.2)[...]

  • Seite 156

    9 - 1 WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 1 9 MELSEC-F 9 WHEN COMMUNICA TING DA T A USING THE MC PROTOCOL This chapter explains the me ssage format, how to design ate data item s in a message and restrictions for data commu nication with an Ethernet module using MC proto col with A compatible 1E frames. 9.1 Message Formats and Contr[...]

  • Seite 157

    9 - 2 WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 2 9 MELSEC-F (2) When an external device writes data to the PLC 1) Area C indicates transmission from the external device to the PLC. 2) The program of the external device is gener ated so that the data is transmitted sequentially from lef t to right. (For example: in case of area C, data sh[...]

  • Seite 158

    9 - 3 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 3 9.1.2 Message format and control procedure This sectio n explains the messag e format a nd control pr ocedure. (1) Message format This section explains the message format for tr ansmission between the Ether net module and an external device. The communication dat a consists of &qu[...]

  • Seite 159

    9 - 4 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 4 (2) Control procedure The following diagrams illustrate the co ntrol procedure fo r communicating with the MC protocol and the order of dat a items in the application dat a field. The header section shown in the messa ge explanation dia gram of this section corresponds to the port[...]

  • Seite 160

    9 - 5 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 5 2) When writing dat a to the local st ation PLC from the external device side (b) Communicati on in binary code 1) When r eading data from the local station PLC at the exte rnal device s ide External device side PLC side (Command message) T ext (Command) (Data name) Header Subhead[...]

  • Seite 161

    9 - 6 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 6 2) When writing dat a to the local st ation PLC from the external device side External device side PLC side (Command message) PLC side External device side (Response message) (Normal completion) (Abnormal completion) T ext (Command) (Data name) (Example) Header Subheader PC No. Mo[...]

  • Seite 162

    9 - 7 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 7 9.1.3 Contents of data designation items This sectio n explains th e data it ems of commands and responses when communica ting using MC protocol. In the response that is retu rned by the Ethern et module to an external device, the data is automatically specifie d by the Ethernet m[...]

  • Seite 163

    9 - 8 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 8 (6) Character field (response) This dat a contains dat a read/processing result when an external device reads/ writes data from/to the t arget PLC station. The content s and order of dat a in the C haracter field (respo nse) dif fer depen ding on the function used. The order or da[...]

  • Seite 164

    9 - 9 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 9 NOTE The following example shows th e designation of the subheader to the mon itoring timer when com municating us ing MC pr otocol unde r the following conditions. (Designated value) (1) Format when communicating in binary code (a) The order when sending a comma nd (external devi[...]

  • Seite 165

    9 - 10 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 10 (2) Format when communicating in ASCII code (a) The order when sending a comma nd (external device Ethernet module) (b) The order when receiving a re sponse (external device Ethernet module) 30 H 30 H 46 H 46 H 30 H 30 H 30 H 41 H "0" "0" "F" "[...]

  • Seite 166

    9 - 11 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 11 9.1.4 Character area transmission data This section exp lains how to transm it the bit device data and word dev ice data handled in the character ar eas, as well as the order of transmission when communicating dat a between an external device and the PLC by each command . The tr[...]

  • Seite 167

    9 - 12 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 12 (b) When reading from or writin g to a word device memory Each word of the word device memory is expressed in he xadecimal values in 4-bit units sequentially from the h igher bit. (Example) Indicating the storage conten ts of dat a registers D350 and D351 POINT (1) When designat[...]

  • Seite 168

    9 - 13 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 13 (2) Data communication using binary code (a) When reading to or writing from the bit device memory The bit device me mory can be re ad and written in bit un its (one device point) or word units (1 6 device point s). How data is transmitte d in each case is explained belo w . 1) [...]

  • Seite 169

    9 - 14 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 14 (b) Reading from or writing to a word device me mory Each word of a word device memory is designated by 16 bit s and the designated number of point s from the designated head device are sequentially expressed in on e-point unit s in the order , low byte (L: bits 0 to 7) to high [...]

  • Seite 170

    9 - 15 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 15 9.2 List of Commands and Func tions for The MC protocol The following tab le list s the commands a nd functions when an external d evice accesses the PLC. *1 When the double word data is re ad using the us er program, etc., read out the 3 2bit data at once. Function - Command/re[...]

  • Seite 171

    9 - 16 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 16 9.3 D evice Memory Read/Write This section explains the designations in the control procedure wh en reading from and writing to the device memor y by providing an example. 9.3.1 Commands and device range (1) Commands used for reading from and writi ng to the device memory Item C[...]

  • Seite 172

    9 - 17 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 17 (2) Designation met hod and accessible range of devices. (a) In device read/write, each device is set by a device code and number as shown in the diagram be low . (b) The following table outlines the device codes and numbers. Device list Device Device code Device range Device nu[...]

  • Seite 173

    9 - 18 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 18 POINT (1) Bit devices and word devices are classified according to the following. Bit devices : X, Y , M, S, T (contact), C (contact) Word devices : T (current val ue), C (curre nt value), D, R (2) When word units a re designated, always make the head de vice number of a bit dev[...]

  • Seite 174

    9 - 19 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 19 9.3.2 Batch read in bit units (command: 00) The exam ples show n in this se ction ex plain the command/response format when batch-reading the bit device memory . For more deta ils on the order and contents of dat a items of the areas marked by " " shown in the control [...]

  • Seite 175

    9 - 20 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 20 (2) Communication in ASCII code NOTE (1) Use th e designation "00 H " when the number of device points is 256 points. (2) If the n umber of device points designated is an odd number, one byte of dummy data (30 H ) will be added to the response data. For example, if thr[...]

  • Seite 176

    9 - 21 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 21 9.3.3 Batch write in bit units (command: 02) The exam ples show n in this se ction ex plain the command/response format when batch writing to the bit device memory . For more deta ils on the order and contents of dat a items of the areas marked by " " shown in the cont[...]

  • Seite 177

    9 - 22 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 22 (2) Communication in ASCII code NOTE If the number of device points to be set is an odd number, ad d one byte of dummy data (30 H ) at the end of d ata written. For e xam ple, when writing three points, add the dummy data (30 H ) at the end. (Data name) External device side (Exa[...]

  • Seite 178

    9 - 23 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 23 9.3.4 T est in bit units (r andom write) (command: 04) The exam ples show n in this se ction ex plain the command/response format when writing dat a by designating bit device memories ar bitrarily . For more deta ils on the order and contents of dat a items of the areas marked b[...]

  • Seite 179

    9 - 24 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 24 (2) Communication in ASCII code (Data name) External device side (Example) Designated device Y45 Designated device M60 S38 ON Y45 OFF M60 ON S38 Designated device 9 39 H 0 30 H 4 34 H F H 46 H L F 46 H H 0 30 H 0 30 H 0 30 H L A 41 H H 0 30 H L 3 33 H 0 30 H 0 30 H H 5 35 H 2 32[...]

  • Seite 180

    9 - 25 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 25 9.3.5 Batch read in word units (command: 01) The exam ples show n in this se ction ex plain the command/response format when batch reading the word device memory and the bit device me mory (16 point unit s). For more deta ils on the order and contents of dat a items of the areas[...]

  • Seite 181

    9 - 26 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 26 (2) Communication in ASCII code 30 H 38 H 30 H 0 31 H 41 H 35 H Y100 32/16 = 2 points 31 H 1 46 H F HL F 46 H 0 HL 00 A 5 30 H 30 H 39 H 9 32 H 2 30 H 0 30 H 0 30 H 0 30 H 0 30 H 0 30 H 0 30 H 0 HL 34 H 4 30 H 0 H 30 H 0 L 32 H 2 30 H 0 30 H 0 8 H 1 0 30 H L 0 30 H HL 8 38 H 2 3[...]

  • Seite 182

    9 - 27 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 27 NOTE C200 to C255 (Current Valu es) Batch Read Since C200 to C255 are 32 bit devices, th e device points should be specified as twice as much as the points actually read. Also, make sure that the device points are specified by an even number . If they are specified by an odd num[...]

  • Seite 183

    9 - 28 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 28 (2) When communicating in ASCII code * 0 30 H H F 46 H * 1 31 H L F 46 H H 0 30 H - 0 30 H - 0 30 H L A 41 H 8 38 H 1 31 H L 0 30 H H 0 30 H 34 H 33 H 34 H 45 H 30 H 30 H 30 H 30 H 30 H 30 H 44 H 43 H 12345678=00BC614E H 45678912=02B90140 H 36 H 31 H 34 H 45 H 30 H 30 H 42 H 43 [...]

  • Seite 184

    9 - 29 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 29 9.3.6 Batch write in wo rd units (command: 03) The exam ples show n in this se ction ex plain the command/response format when batch writing to a word device memory and bit device memor y (16 point unit s). For more deta ils on the order and contents of dat a items of the areas [...]

  • Seite 185

    9 - 30 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 30 (2) Communication in ASCII code F 30 H 0 38 H D100 33 H 3 46 H 46 H 30 H 0 30 H 0 30 H 0 41 H A 34 H 4 34 H 4 32 H 2 30 H 0 30 H 0 30 H 0 30 H 0 30 H 0 30 H 0 30 H 0 36 H 6 34 H 4 30 H 0 33 H 3 30 H 0 30 H 0 31 H 1 32 H 2 33 H 3 34 H 4 39 H 9 38 H 8 37 H 7 36 H 6 30 H 0 31 H 1 3[...]

  • Seite 186

    9 - 31 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 31 NOTE C200 to C255 (Current Values) Batch Write Since C200 toC255 are 32 bit de vices, the device points should be specified twice as much as the points actually read. Also, make sure that the device points are specified by even numbe r. If they are specified by odd number, the b[...]

  • Seite 187

    9 - 32 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 32 (2) When communicating in ASCII code * 0 30 H H F 46 H * 3 33 H L F 46 H H 0 30 H - 0 30 H - 0 30 H L A 41 H 8 38 H 3 33 H L 0 30 H H 0 30 H 34 H 33 H 34 H 45 H 30 H 30 H 30 H 30 H 30 H 30 H 44 H 43 H 12345678=00BC614E H 45678912=02B90140 H 36 H 31 H 34 H 45 H 30 H 30 H 42 H 43 [...]

  • Seite 188

    9 - 33 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 33 9.3.7 T est in word units (random write) (command: 05) The exam ples show n in this se ction ex plain the command/response format when writing dat a by designating word device memories and bit device mem ories (16 point units) arb itrarily . These examples are not app licable fo[...]

  • Seite 189

    9 - 34 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 34 (2) Communication in ASCII code Y20 30 H 35 H 46 H 46 H 30 H 30 H 30 H 41 H 30 H 33 H 30 H 30 H 35 H 39 H 32 H 30 H 31 H 30 H 37 H 42 H 32 H 39 H 35 H 32 H 32 H 30 H 31 H 41 H 34 H 33 H 34 H 45 H 30 H 30 H 30 H 30 H 30 H 30 H 31 H 32 H 30 H 30 H 38 H 35 H 30 H 30 H Designated de[...]

  • Seite 190

    9 - 35 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 35 9.4 R emote RUN/STOP , PLC model name code read This function is used to remotely RUN/ST OP a PLC and read the model name of a PLC from a n external device. 9.4.1 Commands and control contents This section describe s the commands and control contents of the control procedur e wh[...]

  • Seite 191

    9 - 36 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 36 9.4.2 Remote RUN (command: 13) / Remo te STOP(command: 14) The examples shown in this section explain the control pr ocedure of remote RUN. The order and content of dat a items of the areas marked by " " shown in the control procedure diagr am diff er depending on the [...]

  • Seite 192

    9 - 37 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 37 POINT • When executing the remote RUN/STOP using other external devices or computer link, the remo te RUN/STOP is executed in the order o f execution. • Whe n the power of PLC is turned on, then off, and then on again with the remote RUN/STOP executed, the remote RUN/STOP st[...]

  • Seite 193

    9 - 38 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 38 9.4.3 PLC model name read (command: 15) The exam ples show n in this se ction expl ains the con trol proced ure for re ading the model name of the PLC. The order and content of dat a items of the areas marked by " " shown in the control procedure diagr am diff er depen[...]

  • Seite 194

    9 - 39 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 39 9.5 Loopback T est A loopback test checks whether or not the communication function between an external device and the Eth ernet module op erates normally . The examples show the control procedure using th is function. 9.5.1 Loopback test (command: 16) The examples shown in this[...]

  • Seite 195

    9 - 40 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 40 (2) Performing a loopback test wh ile communicating in ASCII code POINT The number of the loopback dat a transmitted by an external device is returned to the external device it is. 31 H 36 H 46 H 46 H 30 H 30 H 30 H 41 H 6 H F H L 1 H 0 0 L A 0 L H L H L H L H 39 H 36 H 30 H 30 [...]

  • Seite 196

    10 - 1 USING THE E-MAIL FUNCTION 10 10 - 1 10 MELSEC-F 10 USING THE E-MAIL FUNCTION This chapter explains e-mail func tions of the Ethernet module. 10.1 E-mail Function The e-mail function sends e-mails to a personal computer or PLC at a re mote location using the network (via the mail server). Executed by operating the bu ffer memory in a sequence[...]

  • Seite 197

    10 - 2 USING THE E-MAIL FUNCTION 10 10 - 2 10 MELSEC-F (2) Data conversion method used by the Ethernet module The following shows the dat a conversion method used by the Eth ernet module. (3) Flow of the e-mail The following diagram illustrates the flow of e-mail sent by the PLC to the external devic e: [When sending by the Etherne t module] 1) Sen[...]

  • Seite 198

    10 - 3 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 3 10.2 Configuration and Environment of the Applicable System This section exp lains the environ ment and system co nfiguration fo r using the e-mail function from the Ethe rnet module. (1) E-mails can be sent and received in an environment wh ere the Internet se rvice is available as show n above. [...]

  • Seite 199

    10 - 4 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 4 10.3 Precautions for Us ing the E-mail Function The following explains precautions when using the e-mail function of the Ether net module. (1) Precautions regarding the system (a) Design the system so that the entire system op erates normally at all times when sending/receiving e -mails to/from a [...]

  • Seite 200

    10 - 5 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 5 (f) When e-mail communica tion errors occur , check the error codes stored in the mail send/reception er ror log area of the buf fer memory . (g) If e-mails ca nnot be rece ived, try one of the following. 1) Execute the mail receive instruction (BFM#14 500:0001 H ) once. 2) Shorten the "Inqui[...]

  • Seite 201

    10 - 6 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 6 10.4 E-mail S pecifications The following table list s the specifications of the e-mail function. *1 Ethernet modules V1.10 or later suppo rt port numbers 1 to 65535. The port number is fixed to "25 " in Ethernet modules earlie r than V1.01. *2 Ethernet modules V 1.10 or later support th[...]

  • Seite 202

    10 - 7 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 7 10.5 Processing Procedure of the E-mail Function The following flowchart illustrates the proced ure that is required before sending and receiving e-mails: Start When DNS is not used When DNS is used Register the DNS server See Section 10.6 (1) Register the mail address of the local station's [...]

  • Seite 203

    10 - 8 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 8 10.6 E-mail Settings This sectio n explains th e settings req uired to send and receive e -mails. (1) DNS settings S pecify the IP address of the DNS server when setting the mail serve r name using the domain name from the e-mai l settings (see (2)). (a) DNS settings Set the IP addr esses of the d[...]

  • Seite 204

    10 - 9 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 9 (2) E-mail settings Set in order to use the e-mail function . [Setting item] *1 Supported in Ethernet modules V . 1 .10 or later Setting item BFM number [Decimal] Description of setting item Setting range/option General setting Password 9913 to 9920 Set the password to the POP3 server (16 characte[...]

  • Seite 205

    10 - 10 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 10 (a) General settings Designate the mail setting values th at have been register ed with the mail registration informatio n designated by the system administrator . 1) Password: Designate the mail password of th e local station's Ethe rnet module. 2) Mail address: Designate the mail address [...]

  • Seite 206

    10 - 11 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 11 (c) SMTP authentication setting 1) Set the authentication method for the outgoing mail server (SMTP). The steps 2) and 3) below are re quired when "SMTP-AUTH" is selected in the SMTP authentication method. 2) Set the log in ID of the outgoing mail se rver (SMTP). 3) Set the password of[...]

  • Seite 207

    10 - 12 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 12 10.7 Sending/Receiving E-mail (Attached Files) by the PLC This sectio n explains ho w to send an d receive attached files by e-mail. 10.7.1 When sending data as an att ached file The following explains the buf fer memory addresses and program for sending e-mail. The following instruction shows h[...]

  • Seite 208

    10 - 13 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 13 The tabl e below shows the buffer memory to be used for sending mail. (1) Send using the se quence program The following explains how an e-mail is sent by the sequence program. See (3) sending dat a for detail. BFM number Items Contents Decimal (Hexadecimal) 10333 (285D H ) Mail sending command [...]

  • Seite 209

    10 - 14 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 14 •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 X000 M100 M102 M103 M101 D100.1 D100.0 D100.F M8029 M101 [MOV D100 K1000 (C1 ] [MOV D101 ] [PLS M103 ] [PLS M102 ] [CALLP P0 ] [MOVP H3 ] [MOVP H1 ] [MOVP K3 U1 G10403 ] [MOVP H1 U1 G10333 ] "testmail msend" [$MO[...]

  • Seite 210

    10 - 15 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 15 NOTE When an error occurs wh ile sending e-mail from the sending mail server to an external device, an erro r code is stored in the receiving error log ar ea. M8000 [MOV R1234 R1000 ] ] [MOV H5678 R1001 R1002 ] [MOV R9ABC ] [FEND [SRET ] [END ] P0 Head of attached data [ZRST R1000 R1002 ] Head o[...]

  • Seite 211

    10 - 16 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 16 (2) Execution timing of the instruction 1) Check whether the initial pr ocessing ha s been comple ted normally . 2) Write mail dat a to the buf fer memory . (Mail sending destinatio n: BFM#10337...b0 to b 9) (Subject: BFM#10339 to 10402 ) (Atta ched file format: BFM#1033 8) (Wor d count of attac[...]

  • Seite 212

    10 - 17 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 17 (3) Receiving with a personal computer The following explains how a PC/UNIX rece ives e-mails sent from the Ethernet module. After setting an environment with application soft ware that processes e-mails, e-mails can be receive d on a receive message screen as sh own below . (Example) The follow[...]

  • Seite 213

    10 - 18 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 18 10.7.2 When receiving data in an att ached file This section exp lains the buffer memory ad dresses and a pr ogram to receive e- mail from external devices. The following instruction shows how to read th e received attached file. 1) Read the value in BFM#22640 to chec k if there is incoming mail[...]

  • Seite 214

    10 - 19 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 19 POINT (1) The Ethernet module checks whether there is incoming mail in the mail server at the time inter val set in the Mail parameter (BFM#9904). If there is incoming mail, the rece ptio n information is stored in the fol lowing areas of the buf fer memory . • The number of received mail on t[...]

  • Seite 215

    10 - 20 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 20 (1) Reception using the seque nce program The following explains the designation me thod in a sequence program . •F o r F X 3U /FX 3UC Series PLCs Program example for the un it No. 1 M201 M200 D200.1 D200.0 M202 M203 (M200 (M202 (M203 [<> ] K0 U1 G14501 [> H8000 ] [MOVP H1 ] [INCP D2[...]

  • Seite 216

    10 - 21 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 21 (2) Execution timing of the instruction 1) Check whether the initial processing has been completed nor mally or not. 2) Read the value in BFM#22640 to see whether there is incom ing mail in th e mail server . 3) Write "0001 H " in BFM#1 4500 to read e-mail from the server . *E-mail rea[...]

  • Seite 217

    10 - 22 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 22 (3) Sending from a perso nal computer This section explains how to send e-ma ils from a PC/UNIX to the Ethernet module. Once an environmen t that is capab le of using the In ternet throug h an application program that handles e- mail is set up, e-mail can be created an d sent on the New Message [...]

  • Seite 218

    10 - 23 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 23 10.7.3 Contents of the att ached files The following explains the conten ts of the att a ched file dat a. The data format of the att ached file is ASCII code (ASCII format, CSV format ) or binary code (binary form at). The following example shows the tran smission content s for each data fo rmat[...]

  • Seite 219

    10 - 24 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 24 (3) Data configurat ion in CSV format Data in CSV format can be used as contro l data for the cell unit s in Excel, etc. Data in CSV format h andled by the Ether net mo dule is the dat a expressed as follows. • 1 wor d (16 bits) binar y data is converted to four digit ASCII code wh en expresse[...]

  • Seite 220

    10 - 25 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 25 10.8 Sending E-mail (Main T ext) by the PLC This sectio n explains ho w to send t he main text o f e-mail. 10.8.1 When sending data as main text of e-mail The following explains the buf fer memory address a nd sequence prog ram for sending e-mail. This section exp lains how to store the data in [...]

  • Seite 221

    10 - 26 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 26 The table be low shows the buffer me mory to be used for sending mail. BFM number Item Description Decimal (Hexadecimal) 10333 (285D H ) Mail sending command S tart mail sending (0001 H ) Ignored (0000 H ) 10334 (285E H ) Mail sending status Initial status (0000 H ) Mail sending normal completed[...]

  • Seite 222

    10 - 27 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 27 (1) Send using the se quence program Method for sending e-mails by th e sequence program is similar to the one by an attach ed file. See Subsection 10.7.1 for sample pr ograms for sending e-m ail from PLC. (2) Receiving by a p ersonal computer The following explains how a PC/UNIX/po rtable termi[...]

  • Seite 223

    11 - 1 TROUBLESHOOTING 11 11 - 1 11 MELSEC-F 1 1 TROUBLESHOOTING This section explains the co ntent s of the errors that may occur during comm unication between the Ethernet module a nd an external device as well as the troublesho oting procedures. The following are methods for checking if ther e is an error on the Ethernet module side and the cont[...]

  • Seite 224

    11 - 2 TROUBLESHOOTING 11 11 - 2 11 MELSEC-F 1 1.1 How to Check Errors Using LED Displays This sectio n describes th e errors th at can be c hecked with the LED displays on the front of the Ethernet module. 1 1.1.1 Checking error display The following can be checked with the LED d isplays on the fr ont of the Ethernet module. <Ethernet module LE[...]

  • Seite 225

    11 - 3 MELSEC-F TROUBLESHOOTING 11 11 - 3 (Continued from the previous p age) *1 Confirm the complet ion for the init ial processing and chec k whether or not there is any prob lem in the ca ble connection and the Ethern et lines. See Section 5.4, "Confirmin g the completion of the Initial Processing" for details on confirmin g the comple[...]

  • Seite 226

    11 - 4 MELSEC-F TROUBLESHOOTING 11 11 - 4 1 1.1.2 How to turn off COM.ERR LED a nd to read/clear error information This section explains how to turn off [COM .ERR] LED and to read/clear error information using a sequence program. (1) How to turn off [COM.E RR] LED using buffer memory The [COM.ERR] LED on the front of the Ethernet module is turned o[...]

  • Seite 227

    11 - 5 MELSEC-F TROUBLESHOOTING 11 11 - 5 (4) How to clear error informat ion by writing to buffer memory Writing to BFM# 31800 to 31802 allows clearing the error in formation and turn ing off COM.ERR. •F o r F X 3U /FX 3UC Series PLCs MOV SET HFFFF U G31800 U G31802 MOV H0000 U G31801 MOV H0001 M100 U G31802 Set error information to clea[...]

  • Seite 228

    11 - 6 MELSEC-F TROUBLESHOOTING 11 11 - 6 1 1.2 How to Check an Error Through FX Configurator-EN The status of the vario us settings for the Ethernet module can be checked using th e FX Configurator-EN functions. (1) Ethernet diagnostics (S ee Section 1 1.2.2.) The block sta tus of an Ethernet module, pa rameter settings, communication status, erro[...]

  • Seite 229

    11 - 7 MELSEC-F TROUBLESHOOTING 11 11 - 7 1 1.2.1 Buffer memory that can be monitore d with the FX Config urator-EN diagnostic function The following is a list o f the buf fer memory addresses that can be displayed on th e "Ethernet diagnostics" scr een of FX Configur ator-EN. BFM address Decim al (hexadecimal) Applicable buffer memor y E[...]

  • Seite 230

    11 - 8 MELSEC-F TROUBLESHOOTING 11 11 - 8 BFM address Decimal (hexadecimal) Applicable buf fer memory Ethernet di agnostics display screen Display contents 440 to 441 (1B8 to 1B9 H ) TCP Received TCP packet count S tatus of each protocol TCP packet T otal number of receives 442 to 443 (1BA to 1BB H ) Received TCP packet count discarded due to Sum c[...]

  • Seite 231

    11 - 9 MELSEC-F TROUBLESHOOTING 11 11 - 9 1 1.2.2 Ethernet diagnostics [Purpose] The block status of an Ether net module, paramete r settings, communication st atus, error log and others can be checked usi ng the Ethern et diagn ostic function of FX Configurator-EN. [Operatin g procedur e] FX Configurator-EN [Ethernet diagnostics scr een] [Explanat[...]

  • Seite 232

    11 - 10 MELSEC-F TROUBLESHOOTING 11 11 - 10 1 1.3 Checking the error inform ation by the buff er memory batch monitoring function It is explained here how the Ethernet m odu le errors can be checked fr om GX Developer . Error codes stored in the buf fer memory of the Ethernet module can be mo nitored using the "Buf fer memory batch moni toring[...]

  • Seite 233

    11 - 11 MELSEC-F TROUBLESHOOTING 11 11 - 11 11 . 4 E r r o r C o d e L i s t This section exp lains the erro r codes (abnorm al codes) for the error s that may occur in each processing when communicating dat a between the Ethernet module an d an external device as well as those generated b y processing request s from the local station's FX ser[...]

  • Seite 234

    11 - 12 MELSEC-F TROUBLESHOOTING 11 11 - 12 (1) Initial error code (BF M#105) (a) This address stores th e error codes g enerated when the initial processing is executed. (b) Error codes are stored as binary values when the initial abnormal completion signal (BFM#28...b5) is on. (c) An erro r code is cleared when th e initial normal completion sign[...]

  • Seite 235

    11 - 13 MELSEC-F TROUBLESHOOTING 11 11 - 13 (5) Error log area (BFM#227 to 372) This area stores the following errors. • Errors whose source cannot be confirmed • Errors that occurred during communica tions using the random access buf fer • Errors that occurred during co mmun ications using MC protocol (a) Number of e rror occurr ences (BFM#2[...]

  • Seite 236

    11 - 14 MELSEC-F TROUBLESHOOTING 11 11 - 14 (f) Error log block - Connection No. (sta rting from BFM#232) 1) The faulty connection No. is stored in bit s 0 to 7 of the corresponding area. ("0" is stored in bit s 8 to 15). 2) For errors below the TCP and UDP levels, "0" is stored. (g) Error log blo ck - Local station Port No. (st[...]

  • Seite 237

    11 - 15 MELSEC-F TROUBLESHOOTING 11 11 - 15 (6) E-mail status storage area (BFM#22640 to 24575) * When the storage coun t exceeds FFFF H times, the count starts from 0 H again. (a) E-mail status storag e area for reception (BFM#2 2640 to 23352) 1) Number of mails remaining on the server ( BFM#22640) • This area stores the number of mails remainin[...]

  • Seite 238

    11 - 16 MELSEC-F TROUBLESHOOTING 11 11 - 16 7) Receiving error log wr ite pointer (BFM#22648) • This address stores the error log block number where the latest e rror logging is register ed. * If the pointer value is "16", it mean s that the latest error logging is registered in the error log block 16 ar ea. • When 17 or more receivin[...]

  • Seite 239

    11 - 17 MELSEC-F TROUBLESHOOTING 11 11 - 17 (b) E-mail status stor age area for sending (BFM#23 355 to 23712) 1) Number of mails normally complete d (BFM#23355) • This address stores a cumulative count of how many times the Ethernet m odule tran sferred se nd mails to t he Send ma il server . 2) Attached file sendin g count (BFM#23 356) • This [...]

  • Seite 240

    11 - 18 MELSEC-F TROUBLESHOOTING 11 11 - 18 6) Sending error log write pointer (BFM# 23360) • This address stores the error log block area number where the latest sending error logging is registered. * If the pointer value is "8", it means that the latest error logging is registered in the sending error log blo ck 8 area. • When 9 or [...]

  • Seite 241

    11 - 19 MELSEC-F TROUBLESHOOTING 11 11 - 19 1 1.4.2 End codes (Complete codes) retu rned to an external device during data communication This sectio n explains th e end code s (compl ete codes) that are added to response s when com municating u sing the fixe d buffer or the M C protocol. For more deta ils on the error co des that are added to respo[...]

  • Seite 242

    11 - 20 MELSEC-F TROUBLESHOOTING 11 11 - 20 1 1.4.3 Abnormal codes returned during communication using MC protocol This section explains the abnorm al codes (error codes) that are added to responses when communicating using MC protocol (A n abnor mal code is added only when an end code is "5B".) For more deta ils on the end codes (err or [...]

  • Seite 243

    11 - 21 MELSEC-F TROUBLESHOOTING 11 11 - 21 1 1.4.4 Error codes stored in the buffer memory When an error occurs at each da ta communi cation processing be tween the Et hernet module and an external device, the error co de (ab normal code) is stored in the buf fer memory of the Ethernet module. This section explains the content s of this type of er[...]

  • Seite 244

    11 - 22 MELSEC-F TROUBLESHOOTING 11 11 - 22 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C001 H • At initial processing, t he IP address setting value of the Ethernet module is incor rect. • [...]

  • Seite 245

    11 - 23 MELSEC-F TROUBLESHOOTING 11 11 - 23 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C020 H Data length exceeds the allowable range. • Correct the dat a length. • If the data tra nsmitted[...]

  • Seite 246

    11 - 24 MELSEC-F TROUBLESHOOTING 11 11 - 24 *1 When this error occurs, the COM.ERR light turns on, but turns off again about one second later . Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C041 H[...]

  • Seite 247

    11 - 25 MELSEC-F TROUBLESHOOTING 11 11 - 25 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C05F H The request could not b e executed on the t arget PLC. • Correct the network number and PC numbe [...]

  • Seite 248

    11 - 26 MELSEC-F TROUBLESHOOTING 11 11 - 26 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C0C7 H An Ethernet module system error occurred. • Execute the initial pr ocessing again. • Execute th[...]

  • Seite 249

    11 - 27 MELSEC-F TROUBLESHOOTING 11 11 - 27 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C0F9 H Handshake error on T O instruction with a base module • Check whether or not t here is a contact [...]

  • Seite 250

    11 - 28 MELSEC-F TROUBLESHOOTING 11 11 - 28 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C1 13 H An e-mail was received that did n ot have an attach ed file. (This will generate when the att ache[...]

  • Seite 251

    11 - 29 MELSEC-F TROUBLESHOOTING 11 11 - 29 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C124 H A response from the SMTP server timed out . • Check whether or not the SMTP server is faulty . ?[...]

  • Seite 252

    11 - 30 MELSEC-F TROUBLESHOOTING 11 11 - 30 Error code (abnormal code) Description of error Error handling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 22649 C143 H Cannot communicate wit h the POP3 ser ver . (Reset r esponse) • Check if the POP3 server is busy [...]

  • Seite 253

    11 - 31 MELSEC-F TROUBLESHOOTING 11 11 - 31 * 1 T ake corrective action using the following procedure. 1) Check wh ether the expansion conn ectors are conn ected correctly . 2) Check whether the opera ting environmen t of the Ethernet module is within the general specifications range of the module. 3) Check whether the power supply cap acity is suf[...]

  • Seite 254

    11 - 32 MELSEC-F TROUBLESHOOTING 11 11 - 32 NOTE Depending on the restriction s of the buffers o f the local station and ex ternal device, data may be divided for commu nication. Data received separately is restored (r ea ssembled) by the Ethernet module to be communicated using th e fixed buffer, etc. The received da ta is restored (reassembled) b[...]

  • Seite 255

    11 - 33 MELSEC-F TROUBLESHOOTING 11 11 - 33 (2) When communication is perfor med using fixed buf fer (non-procedure ) Since no message data length is specif ied in non-pro cedure commu nication, the data received is stor ed in the receive buf fer area as is. It is recommended to set up some method of checking that th e data is received correctly . [...]

  • Seite 256

    11 - 34 MELSEC-F TROUBLESHOOTING 11 11 - 34 1 1.5 Troubleshooting Flowchart This section explains some simple troubleshooting proce dures when the Ether net module and an externa l device have c ommunication problems in a flowchart format. (*1) POINT If trouble occurs when using the Eth ernet module, check the block st atus, error status and others[...]

  • Seite 257

    11 - 35 MELSEC-F TROUBLESHOOTING 11 11 - 35 *1 See Section 1 1.1 when the value of BFM# 27 is "0000 H " or when the display LED COM.ERR (communication error detection display) lights up. (Check an error code that is stored in the buffer memory in r eaction to an error o ccurrence, then check the contents of the error and take corrective a[...]

  • Seite 258

    11 - 36 MELSEC-F TROUBLESHOOTING 11 11 - 36 POINT (1) When the Ethernet module is replaced due to an error , reboot the following external devices and rest art dat a communication: (If the external device ret ains the Ethernet address, it may be impossible to continue communica tion because when a module is repl aced the Ethernet address changes.) [...]

  • Seite 259

    11 - 37 MELSEC-F TROUBLESHOOTING 11 11 - 37 1 1.5.1 Sending errors during fixed buffer communication (common to procedure exist and no procedure) Sending error Check the open status of the connection with an external device. Are the corresponding connection LEDs (C1-C8) lit? If so, modify the program. Read the open abnormal code (BFM #229...) of th[...]

  • Seite 260

    11 - 38 MELSEC-F TROUBLESHOOTING 11 11 - 38 POINT If the external device communicates normally , the following conditions occur . For TCP communication When the external device's open st atus is complete, LEDs C1-C 8, which are in correspondence with connections 1-8 , turn on. For UDP communication When external device communication is possibl[...]

  • Seite 261

    11 - 39 MELSEC-F TROUBLESHOOTING 11 11 - 39 1 1.5.2 Receiving errors during fixed buffer communication (common to procedure exist and no procedure) POINT Perform erro r code reading while the connection is open . NO YES 1) NO YES Receiving err or Check the open status of the connection with an ext ernal device. NO YES Execute the open processing o [...]

  • Seite 262

    11 - 40 MELSEC-F TROUBLESHOOTING 11 11 - 40 Does the external device operate normally? YES The Ethernet module hardware on the sending side may be faulty . Consult your nearest branch office or dealer with the details of the errors. NO Check the device on the sending side. (If the sending side is also an Ethernet module, see Section 1 1.4.) NO 1) D[...]

  • Seite 263

    11 - 41 MELSEC-F TROUBLESHOOTING 11 11 - 41 POINT If the external device communicates normally , the following conditions occur . For TCP communication When the external device's open st atus is complete, LEDs C1-C 8, which are in correspondence with connections 1-8 , turn on. For UDP communication When external device communication is possibl[...]

  • Seite 264

    11 - 42 MELSEC-F TROUBLESHOOTING 11 11 - 42 1 1.5.3 Errors in communica tion using MC protocol Communication error Check the open status of the connection with the external device. Are the corres- ponding connection LEDs (C1-C8) lit? NO YES W as a command sent form the external device? NO YES Send the command to the Ethernet module. W as a response[...]

  • Seite 265

    11 - 43 MELSEC-F TROUBLESHOOTING 11 11 - 43 POINT • If the external device communicates no rmally, the following conditions occur. For TCP co mmunication When the ex ternal devic e's open status is com plete, LEDs C 1-C8, which are in correspondence with conne ctions 1-8, turn on. For UDP communication When external device communicat ion is [...]

  • Seite 266

    11 - 44 MELSEC-F TROUBLESHOOTING 11 11 - 44 1 1.5.4 Sending errors dur ing e-mail communication Is "0001 H " written to BFM#10333? NO YES Correct the condition for writing to BFM#10333. Is the value of BFM#10334 set to "0001 H "? NO YES Can the error response be received from the mail server using the mail receiving operation? C[...]

  • Seite 267

    11 - 45 MELSEC-F TROUBLESHOOTING 11 11 - 45 1 1.5.5 Receiving errors during e-mail communication YES YES Was the e-mail successfully stored? Is the e-mail receiving error log normal? Is "0001 H " written to BFM#14500? Is the value of BFM#14501 set to "0001 H "? YES Can the receive data be stored in the device? YES No inquiry? YE[...]

  • Seite 268

    App - 1 APPENDIX App - 1 App MELSEC-F APPENDIX Appendix 1 Processing T ime Calculate the minim um proces sing time f or each fu nction usin g the expr essions be low . Note that th e processing time may be come lo nger depending on the load facto r on the network (how congested the line is), the window size of each connected device, the number of c[...]

  • Seite 269

    App - 2 APPENDIX App - 2 App MELSEC-F (2) Minimum processing time of communication usi ng MC protocol (batch read and batch write) Tfs = Ke + (Kdt Df) + Scr number o f scans requ ired for pr ocessing + ACK processing time of external device *1 The timing sequence from when the Ethernet mo dule receives the request dat a from the personal comp ut er[...]

  • Seite 270

    App - 3 MELSEC-F APPENDIX App - 3 [Calculation example 1] Calculate the required time (unit: ms) to complete the processing of a data req uest from a PC after rece iving it, when the Etherne t module and the PC perform TCP/IP communi cation and read 32 point s of ASCII code dat a from the data regi ster (D) in the PLC using MC protocol communicatio[...]

  • Seite 271

    App - 4 MELSEC-F APPENDIX App - 4 Appendix 2 ASCII Code List Appendix 3 References For details on TCP/IP , refer to the DDN Protocol Handbook (3 volumes). Publisher DDN Network Info r mation Center SRI International 333 Ravenswood A venue, EJ291 Menlo Park, California 9402 5 RFC Number TCP RFC793 UDP RFC768 IP RFC791 ICMP RFC792 ARP RFC826 MSD LSD [...]

  • Seite 272

    App - 5 MELSEC-F APPENDIX App - 5 Appendix 4 Program Examples The program examples pres ented in this section test the connection between the Ethernet module and an external device (p ersonal computer) that is connected to the same Ethe rnet. For each program, only the minimum pro gramming that is required to perfor m the communication test is done[...]

  • Seite 273

    App - 6 MELSEC-F APPENDIX App - 6 Appendix 4.1 Program example for communication using MC protocol -1 The following explains a program, its e xecution environment and the contents of d ata communication . (1) Execution environment of the program example (a) PLC sid e (b) External device side (2) Outline of the program example (a) Sequence program o[...]

  • Seite 274

    App - 7 MELSEC-F APPENDIX App - 7 (3) FX Con figurator-EN settings Set the PLC parameters as follows. (a) Operation settings (b) Open settings Communication dat a code : ASC II Initial timing : Always wait for OPEN (Communication possible at STOP time) IP address : 172.16.56.99 (AC.10 .38.63 H ) Protocol : TCP Open system : Unpassive (MC) Fixed buf[...]

  • Seite 275

    App - 8 MELSEC-F APPENDIX App - 8 (4) Program on the external device side The program example o f the external device shown be low accesse s the FX 3U of the station in which the Ethe rnet module is installed. When this program is exe cuted, the contents of th e following communication messages are displaye d in sequence: 1) Batch write command mes[...]

  • Seite 276

    App - 9 MELSEC-F APPENDIX App - 9 #include <std io.h> #include <winsock.h> #define FLAG_OFF 0 // Completion flag OFF #define FLAG_ON 1 // Completion flag ON #define SOCK_OK 0 // Normal completion #define SOCK_NG -1 // Abnormal completion #define BUF_SIZE 4096 // Receive buffer size #define ERROR_INITIA L 0 // Initial error #define ERROR[...]

  • Seite 277

    App - 10 MELSEC-F APPENDIX App - 10 int main() { WORD wVersionRe quested=MAKEWORD( 1,1); // Winsock Ver 1.1 request WSADATA wsaData; int length; // Communication data length unsigned char s_buf[BUF_SIZE]; // Send buffer unsigned char r_buf[BUF_SIZE]; // Receive buffer int rbuf_idx; // Receive data storage hea d index int recv_size; // Number of rec[...]

  • Seite 278

    App - 11 MELSEC-F APPENDIX App - 11 Closeflag=FLAG_ON; // Connection completio n flag ON // Go to non-blocking mode ulCmdArg = 1; ioctlsocket(socketno, FIONBIO, &ulC mdArg); // Set to non-blocking mode strcpy(s_buf, "03FF000A442 0000000000500 1122334455667 78899AA"); // D0 to D4 batch write request (1E frame) length=(int) strlen(s_buf[...]

  • Seite 279

    App - 12 MELSEC-F APPENDIX App - 12 while(1) { length = re cv(socketno, &r _buf[rbuf_ idx], (BUF_SIZE - rbuf_idx), 0); // Response data receiving if(length == 0) { // Is connection cut off? Sockerror(ERROR_RECI EVE); // Error handling return (SOCK _NG); } if(length == SOCKET_ERROR) { nErrorStatus = WSAGetLastError(); if(nErrorStatus != WSAE WOU[...]

  • Seite 280

    App - 13 MELSEC-F APPENDIX App - 13 case ERROR_BIND: printf("Faile d to bind."); break; case ERROR_CONNECT: printf("Failed to establish connection."); break; case ERROR_SEND: printf("Send ing failed."); break; case ERROR_RECIEVE: printf("Receiving failed."); break; case ERROR_SHUTDOWN: printf("Failed to [...]

  • Seite 281

    App - 14 MELSEC-F APPENDIX App - 14 Appendix 4.2 Program example for communication using MC protocol -2 This section ex plains an ex ample of an ex ternal device program that r eads/writs dat a from the PLC. A sample p rogram, its executio n environmen t and cont ents of data communicat ion are shown below . (1) Execution environment of the program[...]

  • Seite 282

    App - 15 MELSEC-F APPENDIX App - 15 (4) Window example (Form 1) (5) Sample program (Form 1) Parts in italic are created automatically by Visual Basic .NET, so no input is required. Only input where written in bold. Option Explicit On Option Strict On Imports System. Net.Sockets Public Class Form1 Inherits System.Windows.Forms.Form #Region " Wi[...]

  • Seite 283

    App - 16 MELSEC-F APPENDIX App - 16 Memo: The following proced ure is necessary for Windows Fo rm Designer. Change by using Windows Form Designe r. Do not use code editor to change. Friend WithEvents Start As System.Windows.Forms.Button Friend WithEvents lstOutput As System.Windows.Forms.ListBox <System.Diagnostics.DebuggerStepThrou gh( )> Pr[...]

  • Seite 284

    App - 17 MELSEC-F APPENDIX App - 17 Dim RxResponse As String Dim Temp As String Dim j As Integer Dim Dreg(5) As Double Dim DregStr$ Dim SubHeader$ ' IP Address specification IpAddress = "172.16.56.99" ' Port Number specific ation PortNum = 10000 Client = New TcpClient 'Line connection proces sing Try Client.Connect(IpAddres[...]

  • Seite 285

    App - 18 MELSEC-F APPENDIX App - 18 End If lstOutput.Select edIndex = lstOutput.Items.Coun t - 1 End If ' Line disconnection pro cessing Client.GetStrea m().Close() Client.Close() End Sub End Class[...]

  • Seite 286

    App - 19 MELSEC-F APPENDIX App - 19 Appendix 5 Differences between the Ethernet and the IEEE802.3 The following shows the Ethernet header in the dat a link layer supported by the Ethernet module. (1) Ethernet (2) IEEE802.3 Appendix 6 ICMP Protoc ol Supported by t he Ethernet Module The following t able outlines the types o f ICMP supported by the E[...]

  • Seite 287

    App - 20 MELSEC-F APPENDIX App - 20 Appendix 7 Setting V a lue Recording Sheets This secti on provides settin g value re cording sheets fo r parame ters set with FX Configurator-EN Make copies as need ed. Recording sheet 1 [Block number ] Setting value recording sheet No. FX Configurator-EN sett ing screen Recording sheet 1 Ethernet oper ations Rec[...]

  • Seite 288

    App - 21 MELSEC-F APPENDIX App - 21 Recording sheet 2 [Block number ] FX Configurator-EN setting screen Data item Settin g data Setting value Remark Ethernet Initial settings T imer setting TCP ULP T imer initial: 60 (unit: 500 ms) TCP zero window T imer initial: 20 (unit: 500 ms) TCP resend timer init ial: 20 (unit: 500 ms) TCP end timer initial: [...]

  • Seite 289

    App - 22 MELSEC-F APPENDIX App - 22 Recording Sheet 3 [Block number ] FX Configurator-EN setting screen Data item Setting dat a Setting value Remark Ethernet open settings Connection No. Protocol TCP UDP Open system Active Setting not required if UDP is selected. Unpassive Fullpassive Fixed buf fer Send Receive Fixed buf fer communication Procedure[...]

  • Seite 290

    App - 23 MELSEC-F APPENDIX App - 23 Recording sheet 4 [Block number ] FX Configurator-EN setting screen Data item Setting dat a Setting value Remark Setting the Ethernet relay parameter Sub-net mask pat tern . . . Adjust to in put format Default rout er IP address . . . Adjust to input forma t Input format Decimal Router information Inp ut format H[...]

  • Seite 291

    App - 24 MELSEC-F APPENDIX App - 24 Recording sheet 5 [Block number ] FX Configurator-EN setting screen Data item Setting data Setting value Remark Ethernet e-mail settings General settings Password Mail address Check of received mail Check received mails Check: Check mark Interval of inquiry Set interval va lue to check received mail. s Select uni[...]

  • Seite 292

    App - 25 MELSEC-F APPENDIX App - 25 Appendix 8 V ersioin Information Ethernet Module ver sion is shown as "VERSION" on the label att ached to the right side of the module as seen from the front. V ersion Right side[...]

  • Seite 293

    W arranty Please confirm the following product warr anty details before using this pro duct. 1. Gratis Warranty Term and Gratis Warranty Range If any faults or defects (he reinafter "Failure") found to be the responsibility of Mitsubi shi occurs during use of the product within the gratis warr anty term, the product shall be repaired at n[...]

  • Seite 294

    Revised History Date Revi sion Desc riptio n 10/2005 A First Edition 9/2007 B - The FX 3UC Series was added - Clerical error co rrection 9/2008 C Clerical error correction 1 1/2009 D - Change for the Ethern et module V1.10 are applied. - The FX 3G Series was added - Clerical error co rrection 7/2010 E - Power supply specific ations description modi[...]

  • Seite 295

    [...]

  • Seite 296

    HEAD OFFICE: TOKY O BUILDING, 2-7-3 MA RUNOUCHI, CHIYODA- KU, TOKYO 100-8310, JAPAN HIMEJI WORKS: 840, CHIYODA CHO, HIMEJI, JAPAN JY997D18101E (MEE) Effective July 2010 Specifications are subject to chang e without notice. MODEL FX3U-ENET -U-E MODEL CODE 09R716 FX 3U -ENET USER’S MANUAL[...]