FX3U-ENET-L USER'S MANUAL - Automation Systems and Controls

More documents

Recommendations

Info

5COMMUNICATION PROCEDUREMELSEC-F1) After the parameters are sent, the normal completion of the Ethernetmodule initial processing is confirmed (Initial normal completion signalBFM#27 "0001H")After the initial processing is normally completed, the connection isplaced in the open allowed status and the Ethernet module waits for anopen request from the external device.2) The Ethernet module starts the open processing upon receiving the openrequest (SYN) from the external device.When the open processing is normally completed (Open/close status(BFM#1602 "0005H")), the open completion signal (BFM#20480 b0) turnson and data communication is enabled.3) The Ethernet module starts the close processing upon receiving theclose request (FIN) from the external device.When the close processing is completed (BFM#1602 "0000H"), the opencompletion signal (BFM#20480 b0) turns off and data communication isdisabled.4) After the Ethernet module's internal processing is Rissn/completed, theconnection returns to the open acknowledge enabled status.NOTEFor Passive open connections for which [Always wait for OPEN (Communicationpossible at STOP time)] is selected in [Operational settings], the connection open/close processing of the Ethernet module side is performed according to the open/close request from the external device.When the close processing is performed from the Ethernet module (this station), theapplicable connection will not return to the open acknowledge enabled status afterthe close processing, even if [Always wait for OPEN (communication possible atSTOP time)] is selected in [Operational settings].(It requires the same open processing and close processing as the connection forPassive open for which [Do not wait for OPEN (communication impossible at STOP)]is selected.)(2) When "Do not wait for OPEN" is selected in the operational settingWhen initial timing settings of operational settings are at [Do not wait for OPEN(communication impossible at STOP time)], the (BFM #24 b8: OFF) openprocessing/close processing is performed as explained below.Since open processing/close processing is executed by a sequence program, anexternal device can be changed while the connection is established.5 - 345 - 34
5COMMUNICATION PROCEDUREMELSEC-F• Program example for the unit No. 1M8000[=U1\G27InitialH1 ]completionsignalX0:ON OpenX0:OFF Close[MOVU1\G28 K4M110 ]Status Read of status(M0InitialcompletionstatusX000OpenrequestM0InitialcompletionstatusM103Cancel ofselfholdingat close(M100 )Openrequest(Selfholding)M100Open request(Self-holding)[MOVU1\G1602 D100 ]OPEN Readinginstruction/ valuestatus of #1602U1\[MOVP H1 G1602 ]OPENinstruction/status[= D100 H3 ]Readingvalueof #1602(M101 )Rissn/Opencompleted[= D100 H5 ]Readingvalueof #1602[INCP D0 ]Number of normal open completionsNormal open[= D100 H10 ]Readingvalueof #1602[INCP D1 ]Number ofabnormalopencompletions[= D100 H15 ]Readingvalueof #1602X000OpenrequestU1\[MOVP H8000 G1602 ]OPENinstruction/statusM102Closed(Selfholding)(M102 )Closed(Selfholding)[=D100Readingvalueof #1602H0](M103 )Cancel ofself-holdingat close[INCP D2 ]Close normal completion countClose normal processing[END ]User applications are described at the area enclosed with .5 - 355 - 35
Page 1:
FX3U-ENET-LUSER'S MANUAL
Page 5 and 6:
[Wiring Instructions]DANGERBefore m
Page 7 and 8:
CONTENTSSAFETY PRECAUTIONS ........
Page 9 and 10:
8 COMMUNICATION USING MC PROTOCOL 8
Page 11 and 12:
About ManualsThis manual explains t
Page 13 and 14:
Caution to conform with EC Directiv
Page 15 and 16:
(3) Connection between the Ethernet
Page 17 and 18:
1OVERVIEWMELSEC-F1OVERVIEWThis manu
Page 19 and 20:
1OVERVIEWMELSEC-F1.2 Features of th
Page 21 and 22:
1OVERVIEWMELSEC-F(4) Connecting FX
Page 23 and 24:
1OVERVIEWMELSEC-F1.3 Software Confi
Page 25 and 26:
1OVERVIEWMELSEC-F3) PSH (Push Flag)
Page 27 and 28:
2SYSTEM CONFIGURATIONSMELSEC-F2.2 D
Page 29 and 30:
3SPECIFICATIONSMELSEC-F3 SPECIFICAT
Page 31 and 32:
3SPECIFICATIONSMELSEC-F3.2 Data Cod
Page 33 and 34:
3SPECIFICATIONSMELSEC-F3.3 Relation
Page 35 and 36:
3SPECIFICATIONSMELSEC-F3.5 List of
Page 37 and 38:
3SPECIFICATIONSMELSEC-F(2) Assignme
Page 39 and 40:
3SPECIFICATIONSMELSEC-F(b) Communic
Page 41 and 42:
3SPECIFICATIONSMELSEC-F(c) Communic
Page 43 and 44:
3SPECIFICATIONSMELSEC-F(d) Error lo
Page 45 and 46:
3SPECIFICATIONSMELSEC-F(e) Router r
Page 47 and 48:
3SPECIFICATIONSMELSEC-F(Continued f
Page 49 and 50:
3SPECIFICATIONSMELSEC-F(h) Mail sen
Page 51 and 52:
3SPECIFICATIONSMELSEC-F(i) Connecti
Page 53 and 54: 3SPECIFICATIONSMELSEC-FBFM numberDe
Page 55 and 56: 4SETTINGS AND PROCEDURES PRIOR TO O
Page 71 and 72: 5COMMUNICATION PROCEDUREMELSEC-F5 C
Page 73 and 74: 5COMMUNICATION PROCEDUREMELSEC-F5.2
Page 75 and 76: 5COMMUNICATION PROCEDUREMELSEC-F(1)
Page 77 and 78: 5COMMUNICATION PROCEDUREMELSEC-FPOI
Page 79 and 80: 5COMMUNICATION PROCEDUREMELSEC-F(b)
Page 101 and 102: 5COMMUNICATION PROCEDUREMELSEC-FPro
Page 103: 5COMMUNICATION PROCEDUREMELSEC-F5.6
Page 109 and 110: 5COMMUNICATION PROCEDUREMELSEC-F•
Page 111 and 112: 5COMMUNICATION PROCEDUREMELSEC-F•
Page 117 and 118: 6FIXED BUFFER COMMUNICATION (WITH T
Page 149 and 150: 8COMMUNICATION USING MC PROTOCOLMEL
Page 155 and 156:
9WHEN COMMUNICATING DATA USING THE
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
10USING THE E-MAIL FUNCTIONMELSEC-F
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
11TROUBLESHOOTINGMELSEC-F11 TROUBLE
Page 215 and 216:
11TROUBLESHOOTINGMELSEC-F6 SD7 RDLE
Page 217 and 218:
11TROUBLESHOOTINGMELSEC-F(4) How to
Page 219 and 220:
11TROUBLESHOOTINGMELSEC-F11.2.1 Buf
Page 221 and 222:
11TROUBLESHOOTINGMELSEC-F11.2.2 Eth
Page 223 and 224:
11TROUBLESHOOTINGMELSEC-F11.4 Error
Page 225 and 226:
11TROUBLESHOOTINGMELSEC-F(5) Error
Page 227 and 228:
11TROUBLESHOOTINGMELSEC-F(6) E-mail
Page 229 and 230:
11TROUBLESHOOTINGMELSEC-F11.4.2 End
Page 231 and 232:
11TROUBLESHOOTINGMELSEC-F11.4.4 Err
Page 233 and 234:
11TROUBLESHOOTINGMELSEC-FStorage de
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
11TROUBLESHOOTINGMELSEC-F(2) When c
Page 245 and 246:
11TROUBLESHOOTINGMELSEC-F1)Is initi
Page 247 and 248:
11TROUBLESHOOTINGMELSEC-F11.5.1 Sen
Page 249 and 250:
11TROUBLESHOOTINGMELSEC-F11.5.2 Rec
Page 251 and 252:
11TROUBLESHOOTINGMELSEC-FPOINTIf th
Page 253 and 254:
11TROUBLESHOOTINGMELSEC-F1)Is the I
Page 255 and 256:
APPENDIXMELSEC-FAPPENDIXAppendix 1
Page 257 and 258:
APPENDIXMELSEC-F[Calculation exampl
Page 259 and 260:
APPENDIXMELSEC-FAppendix 4 Program
Page 261 and 262:
APPENDIXMELSEC-F(3) FX Configurator
Page 263 and 264:
APPENDIXMELSEC-F/ *****************
Page 265 and 266:
APPENDIXMELSEC-FCloseflag=FLAG_ON;/
Page 267 and 268:
APPENDIXMELSEC-F}case ERROR_BIND:pr
Page 269 and 270:
APPENDIXMELSEC-F(4) Window example
Page 271 and 272:
APPENDIXMELSEC-FDim RxResponse As S
Page 273 and 274:
APPENDIXMELSEC-FAppendix 5 Differen
Page 275 and 276:
APPENDIXMELSEC-FRecording sheet 2[B
Page 277 and 278:
APPENDIXMELSEC-FRecording sheet 4[B
Page 279 and 280:
APPENDIXMELSEC-FAppendix 8 Versioin
Page 281 and 282:
WarrantyPlease confirm the followin
Page 284:
FX3U-ENET-LUSER’S MANUALHEAD OFFI
show all

FX3U-ENET-L USER'S MANUAL - Automation Systems and Controls

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?