fx1 n s fx2n communicationusermanual jy992d69901 e

MELSEC FX Series

Programmable Logic Controllers

User's Manual

Communications ModulesRS-232C, RS-485, RS-422

INDUSTRIAL AUTOMATIONMITSUBISHI ELECTRIC

MITSUBISHI ELECTRIC

Art. no.: 07014315 04 2003JY992D69901Version E

Foreword

• This manual contains text, diagrams and explanations which will guide the reader in thecorrect installation and operation of the communication facilities of FX series. It should beread and understood before attempting to install or use the unit.

• Further information can be found in the respective manual of each programmable controller.

• If in doubt at any stage of the installation of the communication facilities of FX series alwaysconsult a professional electrical engineer who is qualified and trained to the local andnational standards that applies to the installation site.

• If in doubt about the operation or use of the communication facilities of FX series pleaseconsult the nearest Mitsubishi Electric distributor.

• This manual is subject to change without notice.

FX communication

i

FX COMMUNICATION(RS-232C, RS-485, RS-422)

USER’S MANUAL

Brand and product names described by/in this manual are trademarks or registeredtrademarks of the irrespective owners.

Manual number : JY992D69901

Manual revision : E

Date : April 2003

FX communication

FX communication

ii

FAX BACK

Mitsubishi has a world wide reputation for its efforts in continually developing and pushing backthe frontiers of industrial automation. What is sometimes overlooked by the user is the careand attention to detail that is taken with the documentation. However, to continue this processof improvement, the comments of the Mitsubishi users are always welcomed. This page hasbeen designed for you, the reader, to fill in your comments and fax them back to us. We lookforward to hearing from you.

Fax numbers: Your name: ...................................................

Mitsubishi Electric.... .....................................................................

America (01) 847-478-2253 Your company: .............................................

Australia (02) 638-7072 .....................................................................

Germany (0 21 02) 4 86-1 12 Your location:................................................

Spain (34) 93-589-1579 .....................................................................

United Kingdom (01707) 278-695

Please tick the box of your choice

What condition did the manual arrive in? !Good !Minor damage !Unusable

Will you be using a folder to store the manual?!Yes !No

What do you think to the manual presentation?!Tidy !Unfriendly

Are the explanations understandable? !Yes !Not too bad !Unusable

Which explanation was most difficult to understand: ......................................................................................................................................................................................................................

Are there any diagrams which are not clear? !Yes !No

If so,which: ..................................................................................................................................

What do you think to the manual layout? !Good !Not too bad !Unhelpful

If there one thing you would like to see improved, what is it? .............................................................................................................................................................................................................................................................................................................................................................

Could you find the information you required easily using the index and/or the contents, ifpossible please identify your experience: ...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Do you have any comments in general about the Mitsubishi manuals? .....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Thank you for taking the time to fill out this questionnaire. We hope you found both the productand this manual easy to use.

FX communication

iii

FX communication

iv

FX communication

v

Guidelines for the Safety of the User and Protection of the programmable controllers

This manual provides information for the use of the FX series communication unit. The manualhas been written to be used by trained and competent personnel. The definition of such aperson or persons is as follows;

a) Any engineer who is responsible for the planning, design and construction of automaticequipment using the product associated with this manual should be of a competentnature, trained and qualified to the local and national standards required to fulfill thatrole. These engineers should be fully aware of all aspects of safety with regards toautomated equipment.

b) Any commissioning or service engineer must be of a competent nature, trained andqualified to the local and national standards required to fulfill that job. These engineersshould also be trained in the use and maintenance of the completed product. Thisincludes being completely familiar with all associated documentation for the said product.All maintenance should be carried out in accordance with established safety practices.

c) All operators of the completed equipment (see Note) should be trained to use thisproduct in a safe manner in compliance to established safety practices. The operatorsshould also be familiar with documentation which is associated with the operation of thecompleted equipment.

Note : Note: the term ‘completed equipment’ refers to a third party constructed device whichcontains or uses the product associated with this manual.

Notes on the Symbols Used in this Manual

At various times throughout this manual certain symbols will be used to highlight points ofinformation which are intended to ensure the users personal safety and protect the integrity ofequipment. Whenever any of the following symbols are encountered its associated note mustbe read and understood. Each of the symbols used will now be listed with a brief description ofits meaning.

Hardware Warnings

1) Indicates that the identified danger WILL cause physical and property damage.

2) Indicates that the identified danger could POSSIBLY cause physical and propertydamage.

3) Indicates a point of further interest or further explanation.

Software Warnings

4) Indicates special care must be taken when using this element of software.

5) Indicates a special point which the user of the associate software element shouldbe aware of.

6) Indicates a point of interest or further explanation.

FX communication

vi

• Under no circumstances will Mitsubishi Electric be liable responsible for any consequentialdamage that may arise as a result of the installation or use of this equipment.

• All examples and diagrams shown in this manual are intended only as an aid tounderstanding the text, not to guarantee operation. Mitsubishi Electric will accept noresponsibility for actual use of the product based on these illustrative examples.

• Please contact a Mitsubishi Electric distributor for more information concerning applicationsin life critical situations or high reliability.

FX communication

vii

Further Information Manual ListTable 1: Further Information Manual List

Manual name Manual No. Description

FX1S Hardware Manual JY992D83901This manual contains written hardware explanation of wiring, installation and specification, etc. regarding the FX1S Series programmable controller.

FX0 / FX0N Hardware Manual JY992D47501This manual contains written hardware explanation of wiring, installation and specification, etc. regarding the FX0 and FX0N Series programmable controllers.

FX Hardware Manual JY992D47401This manual contains written hardware explanation of wiring, installation and specification, etc. regarding the FX Series programmable controller.

FX2C Supplementary Manual JY992D50201This manual contains supplementary data regarding the FX Series programmable controller Hardware Manual

FX1N Hardware Manual JY992D88201This manual contains written hardware explanation of wiring, installation and specification, etc. regarding the FX1N Series programmable controller.

FX2N Hardware Manual JY992D66301This manual contains written hardware explanation of wiring, installation and specification, etc. regarding the FX2N Series programmable controller.

FX2NC Hardware Manual JY992D76401This manual contains written hardware explanation of wiring, installation and specification, etc. regarding the FX2NC Series programmable controller.

FX Programming Manual JY992D48301This manual contains written instructions regarding the FX0, FX0S, FX0N, FX, FX2C, FX2N and FX2NC Series programmable controllers.

FX Programming Manual ΙΙΙΙΙΙΙΙ JY992D88101This manual contains written instructions regarding the FX1S, FX1N, FX2N and FX2NC Series programmable controllers.

FX / FX0N-485ADP User’s Guide

JY992D53201This manual contains written hardware explanation of installation and specification regarding the FX-485ADP and FX0N-485ADP.

FX2NC-485ADP Installation Manual

JY997D01201This manual contains written hardware explanation of installation and specification regarding the FX2NC-485ADP.

FX-232ADP User’s Guide JY992D48801This manual contains written hardware explanation of installation and specification regarding the FX-232ADP.

FX0N-232ADP User’s Guide JY992D51301This manual contains written hardware explanation of installation and specification regarding the FX0N-232ADP.

FX2NC-232ADP Installation Manual

JY997D01101This manual contains written hardware explanation of installation and specification regarding the FX2NC-232ADP.

FX2N-232-BD User’s Guide JY992D66001This manual contains written hardware explanation of installation and specification regarding the FX2N-232-BD.

FX communication

viii

FX2N-485-BD Hardware Manual

JY992D73401This manual contains written hardware explanation of installation and specification regarding the FX2N-485-BD.







FX-485-IF Hardware Manual JY992D81801This manual contains written hardware explanation of installation and specification regarding the FX-485-IF.

Table 1: Further Information Manual ListManual name Manual No. Description

ix

Table of Contents

Further Information Manual List ................................................................... vii

1. Introduction ............................................................................................. 1-11.1 Abbreviations, Generic Names and Terms Used in This Manual ..........................1-11.2 Communication Types ...........................................................................................1-21.3 System Configuration ............................................................................................1-3

1.3.1 N:N Network ............................................................................................................................. 1-31.3.2 Parallel Link .............................................................................................................................. 1-31.3.3 Computer Link........................................................................................................................... 1-51.3.4 No Protocol Communication .................................................................................................... 1-6

1.4 Supported Functions and Applicable Versions .....................................................1-6

2. Specifications .......................................................................................... 2-12.1 Communication Specification ................................................................................2-12.2 Communication Time.............................................................................................2-2

2.2.1 N:N network ............................................................................................................................. 2-22.2.2 Parallel link ............................................................................................................................... 2-22.2.3 Computer link............................................................................................................................ 2-3

3. Wiring ...................................................................................................... 3-13.1 Caution on cable selection.....................................................................................3-2

3.1.1 FX1N-485-BD, FX2N-485-BD, FX2NC-485ADP.......................................................................... 3-23.1.2 FX0N-485ADP .......................................................................................................................... 3-23.1.3 FX2-40AW................................................................................................................................. 3-2

3.2 Using RS-232C Interface.......................................................................................3-33.2.1 Using RS Instruction or Computer Link..................................................................................... 3-33.2.2 Using FX2N-232IF ..................................................................................................................... 3-4

3.3 Using RS-485 Interface .........................................................................................3-63.3.1 Wiring Selection ........................................................................................................................ 3-63.3.2 Terminal Resistor...................................................................................................................... 3-63.3.3 One-pair Wiring ........................................................................................................................ 3-73.3.4 Two-pair Wiring ........................................................................................................................ 3-8

3.4 Parallel Link ...........................................................................................................3-93.4.1 FX2N(1N)-485-BD and FX0N-485ADP........................................................................................ 3-93.4.2 FX0N-485ADP and FX0N-485ADP .......................................................................................... 3-103.4.3 FX2N(1N)-485-BD and FX2N(1N)-485-BD ................................................................................. 3-113.4.4 FX2NC-485ADP and FX0N-485ADP ........................................................................................ 3-123.4.5 FX2N(1N)-485-BD and FX2NC-485ADP.................................................................................... 3-133.4.6 FX2NC-485ADP and FX2NC-485ADP ...................................................................................... 3-143.4.7 FX2-40AW and FX2-40AW ..................................................................................................... 3-153.4.8 FX2-40AP and FX2-40AP ....................................................................................................... 3-15

4. N:N Network............................................................................................ 4-14.1 Related Flags and Data Registers.........................................................................4-1

4.1.1 Auxiliary Relays ....................................................................................................................... 4-14.1.2 Data Registers ......................................................................................................................... 4-2

FX communication

FX communication

x

4.2 Setting....................................................................................................................4-34.2.1 Setting the Station No. (D8176) ................................................................................................ 4-34.2.2 Setting the Total Number of Slave Stations (D8177) ............................................................... 4-34.2.3 Setting the Refresh Range (D8178).......................................................................................... 4-44.2.4 Setting Retry Count (D8179)..................................................................................................... 4-54.2.5 Setting Comms Time-out (D8180) ............................................................................................ 4-54.2.6 Program Used for Setting ........................................................................................................ 4-6

4.3 Example Program..................................................................................................4-74.3.1 System Configuration ............................................................................................................... 4-74.3.2 Operations ................................................................................................................................ 4-74.3.3 Example of Setting Program..................................................................................................... 4-84.3.4 Example of Error Program ....................................................................................................... 4-84.3.5 Example of Operation Program ................................................................................................ 4-9

5. Parallel link.............................................................................................. 5-15.1 Related Flags and Data Registers ........................................................................5-15.2 Mode and Link Device ...........................................................................................5-2

5.2.1 Normal Mode (Special auxiliary relay M8162: OFF) ................................................................ 5-25.2.2 High Speed Mode (Special auxiliary relay M8162: ON) ........................................................... 5-3

5.3 Example Program..................................................................................................5-45.3.1 Normal Mode ............................................................................................................................ 5-45.3.2 High Speed Mode ..................................................................................................................... 5-4

6. Communication format (D8120) .............................................................. 6-16.1 What Is Communication Format? ..........................................................................6-16.2 Related Flags and Data Registers.........................................................................6-1

6.2.1 Special Auxiliary Relays ........................................................................................................... 6-16.2.2 Special Data Registers ............................................................................................................ 6-1

6.3 Communication Format (D8120) ..........................................................................6-26.4 Example of setting program...................................................................................6-3

7. Computer Link......................................................................................... 7-17.1 Data Flow by Link ..................................................................................................7-17.2 Information Needed Before Programming .............................................................7-3

7.2.1 Programmable Controller Operation ......................................................................................... 7-37.2.2 Computer Notes........................................................................................................................ 7-3

7.3 How to Read a Control Protocol Diagram..............................................................7-47.4 Basic Formats of Dedicated Protocol ....................................................................7-5

7.4.1 Control Protocol Format 1 ........................................................................................................ 7-67.4.2 Control Protocol Format 4......................................................................................................... 7-77.4.3 Control Protocol Parts Explained .............................................................................................. 7-87.4.4 Time-out Check Time.............................................................................................................. 7-11

7.5 Communication Timing Chart ..............................................................................7-127.5.1 Reading Data from Programmable controller ......................................................................... 7-127.5.2 Writing Data to Programmable Controller ............................................................................... 7-127.5.3 Communication Time .............................................................................................................. 7-13

7.6 Character Area Data Transmission .....................................................................7-147.6.1 Bit Device Memory.................................................................................................................. 7-147.6.2 Word Device Memory ............................................................................................................. 7-15

7.7 Commands and Device Ranges ..........................................................................7-167.7.1 Commands.............................................................................................................................. 7-167.7.2 Device specification ranges .................................................................................................... 7-17

7.8 Example Computer Program for Loopback Test .................................................7-18

FX communication

xi

8. Commands.............................................................................................. 8-18.1 Batch Read of Bit Device (BR command)..............................................................8-28.2 Batch Read of Word Device (WR command) ........................................................8-38.3 Batch Write of Bit Device (BW command) .............................................................8-58.4 Batch Write of Word Device (WW command)........................................................8-68.5 Test of Bit Device (BT command)..........................................................................8-88.6 Test of Word Device (WT command) ....................................................................8-98.7 Remote RUN/STOP (RR, RS commands) ..........................................................8-10

8.7.1 Operation of Remote RUN/STOP ........................................................................................... 8-108.7.2 Conditions for Valid Execution of Remote RUN/STOP........................................................... 8-108.7.3 Control Specification and Examples of Remote RUN/STOP .................................................. 8-11

8.8 Reading The Programmable Controller Type (PC command).............................8-128.8.1 Type Codes ............................................................................................................................ 8-128.8.2 Control Specification and Example ......................................................................................... 8-13

8.9 Global Function (GW command) .........................................................................8-148.9.1 Control Specification and Example of Global Function........................................................... 8-14

8.10 On-demand Function .........................................................................................8-158.10.1 Special Devices Used in On-demand Function .................................................................... 8-158.10.2 On-demand Control Protocol ................................................................................................ 8-168.10.3 Specification and Example of On-demand............................................................................ 8-18

8.11 Loopback Test ...................................................................................................8-21

9. RS instruction.......................................................................................... 9-19.1 Function and Operation .........................................................................................9-1

9.1.1 Send and Receive Program...................................................................................................... 9-19.1.2 Operation of RS Instruction....................................................................................................... 9-39.1.3 Related Flags and Data Registers ............................................................................................ 9-4

9.2 Hardware Hand Shake Operation..........................................................................9-69.2.1 FX, FX2C, FX0N, FX1S, FX1N and FX2N (earlier than V 2.00).................................................... 9-69.2.2 FX2N, FX2NC (V 2.00 or later) ................................................................................................. 9-10

9.3 Number of Communication Data .........................................................................9-139.3.1 Deal with 16 bits Data ............................................................................................................. 9-139.3.2 Deal with 8 bits Data ............................................................................................................... 9-14

9.4 Example Program................................................................................................9-159.4.1 Personal Computer ................................................................................................................. 9-159.4.2 Printer ..................................................................................................................................... 9-17

10. FX2N-232IF.......................................................................................... 10-110.1 Introduction ........................................................................................................10-1

10.1.1 Outline of Product ................................................................................................................. 10-110.2 Allocation of Buffer Memories (BFM’s) ..............................................................10-2

10.2.1 BFM List ............................................................................................................................... 10-210.2.2 Communication Format <BFM#0> ....................................................................................... 10-410.2.3 Command ⟨BFM #1⟩ .................................................................................................. 10−810.2.4 Receive Upper Limit Byte Count ⟨BFM #2⟩ ................................................................... 10−910.2.5 Receive Time-out Time <BFM #3> ....................................................................................... 10-910.2.6 Send Header <BFM #5 (upper), BFM #4 (lower)>................................................................ 10-910.2.7 Send Terminator <BFM #7 (upper), BFM #6 (lower)> .......................................................... 10-910.2.8 Receive Header <BFM #9 (upper), BFM #8 (lower)> ......................................................... 10-1010.2.9 Receive Terminator <BFM #11 (upper), BFM #10 (lower)>................................................ 10-1010.2.10 Receive Suspension Waiting Time <BFM #12> ............................................................... 10-1010.2.11 Number of Remaining Send Data <BFM #13> ................................................................. 10-1110.2.12 Number of Receive Buffers <BFM #14> ........................................................................... 10-11

FX communication

xii

10.2.13 Send Sum Result <BFM #15> .......................................................................................... 10-1110.2.14 Receive Sum Result <BFM #16>...................................................................................... 10-1110.2.15 Time from CS ON to Send Start <BFM #20>.................................................................... 10-1210.2.16 Time from Completion of Actual Send to RS OFF (completion flag ON) <BFM #21> ...... 10-1210.2.17 Status <BFM #28> ........................................................................................................... 10-1310.2.18 Error Code <BFM #29>..................................................................................................... 10-1410.2.19 Model Code <BFM #30>................................................................................................... 10-1410.2.20 Send Byte Count <BFM #1000> ....................................................................................... 10-1410.2.21 Send Buffers <BFMs #1001 to #1256>............................................................................. 10-1410.2.22 Receive Byte Count <BFM #2000> .................................................................................. 10-1510.2.23 Receive Buffers <BFM #2001 to #2256>.......................................................................... 10-1510.2.24 Spare Receive Buffers for Interlink Connection Mode <BFM #2257 to #2271> ............... 10-15

10.3 Hardware Hand Shake Operation....................................................................10-1610.3.1 No Hardware Hand Shake .................................................................................................. 10-1610.3.2 Standard RS-232C Mode.................................................................................................... 10-1710.3.3 Interlink Mode ..................................................................................................................... 10-18

10.4 Example Program ............................................................................................10-1910.4.1 Example of 16 Bits Data Communication ........................................................................... 10-1910.4.2 Example of 8 Bits Data Communication ............................................................................. 10-23

11. Optional Programming Port................................................................. 11-111.1 FX2N-422-BD, FX1N-422-BD............................................................................11-111.2 FX2N-232-BD FX1N-232-BD FX0N-232ADP and FX2NC-232ADP .................11-2

11.2.1 Connection cables ................................................................................................................ 11-211.3 Cautions on Use ................................................................................................11-3

11.3.1 Cautions on Setting............................................................................................................... 11-311.3.2 Cautions on use ................................................................................................................... 11-3

12. Diagnostics.......................................................................................... 12-112.1 Common Items ..................................................................................................12-112.2 N:N Network ......................................................................................................12-2

12.2.1 Error Code ............................................................................................................................ 12-212.2.2 Diagnostics ........................................................................................................................... 12-2

12.3 Parallel Link .......................................................................................................12-312.3.1 Diagnostics ........................................................................................................................... 12-3

12.4 Computer Link ...................................................................................................12-412.4.1 NAK Error Code .................................................................................................................... 12-412.4.2 Programmable Controller Error Code ................................................................................... 12-412.4.3 Diagnostics ........................................................................................................................... 12-5

12.5 RS Instruction ....................................................................................................12-612.5.1 Diagnostics ........................................................................................................................... 12-6

12.6 FX2N-232IF ........................................................................................................12-712.6.1 Error code ............................................................................................................................. 12-712.6.2 Diagnostics ........................................................................................................................... 12-7

12.7 Using Optional Programming Port .....................................................................12-812.7.1 FX1S, FX1N and FX2N(C) earlier V2.00.................................................................................. 12-812.7.2 FX2N, FX2NC whose version is V 2.00 or later ...................................................................... 12-8

Appendix A:ASCII code Lists................................................................................................... A-1

FX communication Introduction 1

1-1

11. Introduction

1.1 Abbreviations, Generic Names and Terms Used in This ManualAbbreviation List

This manual describes the following product in the new name.

Abbreviation/generic name/term Description

CPU

FX1S Series Generic name of FX1S Series main units

FX0N Series Generic name of FX0N Series main units


FX Series Generic name of FX Series main units

FX2 Series Generic name of FX2 Series main units


FX2C Series Generic name of FX2C Series main units

FX2NC Series Generic name of FX2NC Series main units

FXCPUGeneric name of FX0/FX0S/FX1S/FX0N/FX1N/FX1/FX/FX2/FX2N/FX2C/FX2NC Series main units

Others

FX/WIN Abbreviation of programming software FX-PCS/WIN-E for FX Series PLC

Windows95 Abbreviation of Microsoft Windows95

Windows98 Abbreviation of Microsoft Windows98

Windows NT4.0 Abbreviation of Microsoft Windows NT Workstation 4.0

Windows 2000 Abbreviation of Microsoft Windows 2000 Professional

WindowsGeneric name of Windows95, Windows98, Windows NT4.0 and Windows2000

Personal computer (PC)Personal computer compatible with Windows to which GX Developer or FX-PCS/WIN-E is installed

Conventional name New name Remarks

GPPW GX Developer Abbreviation of software package SW"D5C-GPPW-E


1-2

1.2 Communication TypesThe FX Series supports the following 5 types of communication.

1 ) N:N networkData transfer with FX2N, FX2NC, FX1N, FX1S, FX0N programmable controllers can beperformed on a N:N basis. They can link data of a small-scale system if using this network. For the system configuration please refer to subsection 1.2.1, specifications refer to chapter3, wiring refer to chapter 2, settings and the number of transferred data and exampleprogram refer to chapter 4,diagnostics refer to chapter 12.

2 ) Parallel linkData transfer with FX2N, FX2NC, FX1N, FX and FX2C programmable controllers can beperformed on a 1:1 basis for 100 auxiliary relays and 10 data registers. With the FX1S andFX0N data transfer is performed for 50 auxiliary relays and 10 data registers.For the system configuration please refer to subsection 1.2.2, specifications refer to chapter3, wiring refer to chapter 2, setting and example program refer to chapter 5, diagnostics referto chapter 12.

3 ) Computer link (Data transfer using dedicated protocol)Data transfer with RS-485 (RS-422) units can be performed on a 1:n (16) basis usingdedicated protocol.For the system configuration please refer to subsection 1.2.3, specifications refer to chapter3, wiring refer to chapter 2, setting of communication format refer to chapter 6, dedicatedprotocol refer to chapter 7 & 8, diagnostics refer to chapter 12.

4 ) No protocol communication (Data transfer using RS instruction)Data communication with a diversified RS-232C unit including personal computers, bar codereaders and printers can be performed using no protocol communications.This communication uses RS instruction’s or an FX2N-232IF special function block.For the system configuration please refer to subsection 1.2.3, specifications refer to chapter3, wiring refer to chapter 2, setting of communication format, RS instruction and exampleprogram refer to chapter 6 and 9, diagnostics refer to chapter 12.When using the RS instruction, for setting the communication format refer to chapter 6, forthe RS instruction and example program please refer to chapter 9. Or when using an FX2N-232IF, for setting and example program please refer to chapter 10.

5 ) Optional programming portThe port can support programming protocol, if connected to an FX2N-232-BD, FX0N-232ADP,FX2NC-232ADP, FX1N-232-BD, FX2N-422-BD and FX1N-422-BD for the FX2N, FX2NC, FX1N,FX1S Series programmable controller.For notes on use, refer to chapter 11, diagnostics refer to chapter 12.


1-3

11.3 System Configuration

For programming protocol refer to chapter 11.

1.3.1 N:N Network

1.3.2 Parallel Link

1 ) FX2N, FX2NC (Shielded twisted-pair cable)

Note:*1 When including an FX2N-485-BD in the system configuration, thais, total extension distance

has a max of 50m (164' 0").

FX Series PLC Interface

FX0N, FX2NCFX0N-485ADP

FX2NC-485ADP

FX1S, FX1N

FX1N-CNV-BD + FX0N-485ADP

FX1N-CNV-BD + FX2NC-485ADP

FX1N-485-BD

FX2N



FX2N-485-BD

####, $$$$ Using interface Extension distance

FX2N

FX2N-485-BD Max. 50m (164' 0")


Max. 500m (1640' 5") *1FX2N-CNV-BD + FX2NC-485ADP

FX2NCFX0N-485ADP

FX2NC-485ADP

RS-485communication

equipment

RS-485communication

equipment

RS-485communication

equipment

RS-485communication

equipment

RS-485communication

equipment

FX PLC FX PLC FX PLC FX PLC FX PLC

Up to eight FX series programmable controllers can be connected.The total extension distance is 500m(1640' 5") when only the FX0N-485ADP and FX2NC-485ADPare used in the configuration, and 50m(164' 0") when the FX1N-485-BD and FX2N-485-BD are used.


1-4

2 ) FX1N (Shielded twisted-pair cable)

*2 When including an FX1N-485-BD in the system configuration, thais, total extension distancehas a max of 50m (164' 0").

3 ) FX1S (Shielded twisted-pair cable)

*3 When including an FX1N-485-BD in the system configuration, thais, total extension distancehas a max of 50m (164' 0").

4 ) FX0N (Shielded twisted-pair cable)

5 ) FX, FX2C (Shielded twisted-pair cable and glassfiber cable)

Note;Parallel link is only possible between the same series of PLC’s, or between other series in the same group. However, parallel link between each group cannot be achieved. Group’s are separated as follows.


FX1N

FX1N-485-BD Max. 50m (164' 0")

FX1N-CNV-BD + FX0N-485ADPMax. 500m (1640' 5") *2



FX1S

FX1N-485-BD Max. 50m (164' 0")

FX1N-CNV-BD + FX0N-485ADPMax. 500m (1640' 5") *3



FX0NFX0N-485ADP

Max. 500m (1640' 5")FX2NC-485ADP


FX2, FX2CFX2-40AW (Shielded twisted-pair cable) Max. 10m (32' 9")

FX2-40AP (Glassfiber cable) Max. 50m (164' 0")

Group No. Series

Group 1 FX2N, FX2NC

Group 2 FX1N

Group 3 FX1S

Group 4 FX0N

Group 5 FX, FX2C


1-5

1

1.3.3 Computer Link

1 ) In the case of 1:N connection using RS-485 (RS-422)

2 ) In the case of 1:1 connection using RS-232C

Up to sixteen FX series programmable controllers can be connected.The total extension distance is 500m(1640' 5") when only the FX0N-485ADP and FX2NC-485ADP are usedin the configuration, and 50m(164' 0") when the FX1N-485-BD and FX2N-485-BD are used.

FX0N,FX2NCFX2N + FX2N-CNV-BD,FX1S + FX1N-CNV-BD,FX1N + FX1N-CNV-BD

FX2NC-485ADP,FX0N-485ADP

FX2,FX2C

FX-485ADP A series PLC +A(1S)J71UC24

FX2N + FX2N-485-BD,FX1S + FX1N-485-BD,FX1N + FX1N-485-BD

Computer

RS-232C

FX-485PC-IF

RS-485(RS-422)

Total extension distance is 15m(49' 2").

Computer

FX2N

FX2NC,FX0N

FX1N,FX1S

FX2,FX2C

:FX2N-232-BD FX2N-CNV-BD+FX0N-232ADP FX2N-CNV-BD+FX2NC-232ADP:FX0N-232ADP FX2NC-232ADP:FX1N-232-BD, FX1N-CNV-BD+FX0N-232ADP FX1N-CNV-BD+FX2NC-232ADP:FX-232ADP

%

%

%

%


1-6

1.3.4 No Protocol Communication

*1 The RS-485/RS-232C signal convertor is necessary in the case of an RS-485 interface for acomputer connection.

*2 When using an FX1N-485-BD a FX2N-485-BD in a system the total extension distance has amax of 50m(164' 0").But, RS-485/RS-232C signal convertor is necessary in the case of an RS-232C interface for acomputer connection.

*3 This system configuration can achieve full-duplex or half-duplex communication.

*4 This system configuration can only achieve half-duplex communication.

1.4 Supported Functions and Applicable Versions Items FX2N, FX2NC FX1N, FX1S FX0N FX, FX2C

N:N network

All versionsAll versions

V2.00 or more No support

Parallel link All versions All versions

Computer link V1.20 or more V3.30 or more

No protocol communication

Use RS instruction All versions V3.00 or more

Use FX2N-232IF Not supported.

FX2N +FX2N-CNV-BD

FX, FX2C

FX2N +FX2N-232-BD

FX0N-232ADP,FX2NC-232ADP

RS-232C

FX2N + FX2N-CNV-BDFX1N + FX1N-CNV-BDFX1S + FX1N-CNV-BDFX0N, FX2NC

FX2N + FX2N-485-BD

FX-232ADP


Max15m(49' 2") *1

Max 500m(1640' 5") *2

*3

*4

*3

FX0NFX1N +FX1N-CNV-BDFX1S +FX1N-CNV-BD


*4

*4 *3

Personal computer

Bar code reader

Printer

FX2NC


*3

FX1N + FX1N-485-BDFX1S + FX1N-485-BD

*4

%%

%

FX1N +FX1N-232-BDFX1S +FX1N-232-BD

*4%

%

%%%%

%%

FX2N,FX2NC + FX2NC-CNV-IF

FX2N-232IF

RS-485(RS-422)

FX communication Specifications 2

2-1

2

2. Specifications

2.1 Communication Specification

*1 FX2N, FX2NC, FX1N, FX1S and FX0N PLCs are supported.

*2 When using an FX0N-485ADP or FX2NC-485ADP, this system is only half-duplex.

N:N network Parallel link

Computer link

(dedicated protocol)

No protocol communication

Transmission standard Conforming to RS-485

Conforming to RS-485 and RS-422

Conforming to RS-485 and RS-422 or RS-232C

Transmission distance Max. 500m RS-485(RS-422): Max. 500m(1640' 5")RS-232C: Max. 15m (49' 2")

Number of stations Max. 8 stations 1:11:N

(N is Max. 16 stations

RS-232C:1:1 RS-485:1:N *1

Communication method Half-duplex communication

FX, FX2C, FX0N, FX1N, FX1S: half-duplex communicationFX2N, FX2NC*2: full-duplex

communicationData length

Fixed7 bit / 8 bit

Parity None / Odd / Even

Stop bit 1 bit / 2bitBaud rate (bps) 38,400 19,200 300/600/1,200/2,400/4,800/9,600/19,200

Header characterFixed

None / effectiveTerminator character

Control line

Protocol Format 1 / Format 4

NoneSum check Fixed None /

effectiveSupported programmable

controllerFX2N, FX2NC,

FX1N, FX1S, FX0NFX2N, FX2NC, FX1N, FX1S, FX0N, FX, FX2C

FX communication Specification 2

2-2

2.2 Communication Time

2.2.1 N:N network

Note;If a N:N network is used, the scan time of each station programmable controller becomes about 10 percent longer regardless of the number of link stations or the communication device pattern used.

2.2.2 Parallel link

Communication device

Pattern 0Bit device: 0 point

Word device: 4 points

Pattern 1Bit device: 32 points


Pattern 2Bit device: 64 points


Total station number

2 18 22 343 26 32 50

4 33 42 665 41 52 836 49 62 99

7 57 72 1158 65 82 131

Normal Mode 70ms for reciprocation + Operation cycle of master station + Operation cycle of slave station (ms)

High speed mode 20ms for reciprocation + Operation cycle of master station + Operation cycle of slave station (ms)

FX communication Specifications 2

2-3

2

2.2.3 Computer link

Calculations to determine the approximate time until communication is complete.

1 ) Programmable controller → Computer

Communication time = Total number of characters based on dedicated protocol*1 × Time to send or receive one character (ms)*2 + Programmable controller’s maximum scan time (ms) × 3+ Message wait (ms)

2 ) Computer → Programmable controller

Communication time = Number of total characters based on dedicated protocol*1 × Time to send or receive one character (ms)*2 + Programmable controller’s maximum scan time (ms) + Message wait (ms)

Note:*1 Please count the number of characters with reference section 7.4.1 and 7.4.2 and chapter 8.

*2 Please refer to the following expression for time calculation.

Time to send or receive one character = 1/baud rate × number of bits in character(start bit(1) + Data length(7 or 8) + Parity bit(0 or 1) + Stop bit(1 or 2))

Example

When 1 character = 10 bits (Data length = 7, Parity bit = 1, stop bit = 1 start bit = 1), the time is as follows.

Note;Please refer to following table for the relation between reading word points and communicationtime.“Message time = 0ms, Maximum scan time = 20ms, Dedicated protocol format = format 1, Command = WR, Baud rate = 9,600 or 19,200 bps”

Baud rate (bps) Time to send or receive one character (ms)300 33.34600 16.671200 8.342400 4.174800 2.089600 1.0419200 0.52

Reading word pointsBaud rate (bps)

9,600 19,20010 0.3 s 0.2 s32 0.4 s 0.3 s64 0.5 s 0.4 s

FX communication Specification 2

2-4

MEMO

FX communication Wiring 3

3-1

3

3. WiringTerminal layout when using a communication unit, please refer to the individual units manual.

Common1 ) This system is designed to read and write data (forced on/off) while the programmable

controller is running.If abnormal data is written to the programmable controller, due to effects of noise, theprogrammable controller may malfunction and cause machine trouble or an accident.Therefore, observe the following cautions.

• Do not lay signal cables near high voltage power cables or put them in the same trunking duct. Otherwise effects of noise or surge induction are likely to take place. Keep a safe distance of more than 100 mm (3.94") from these wires.

• Ground the shield wire or shield of a shielded cable at one point on the programmable controller. Do not, however, ground at the same point as high voltage lines.

2 ) Cut off phases of power source externally, before installation or wiring work in order to avoidelectric shock or serious damage to the product.

3 ) Replace the provided terminal cover before supplying power and operating the unit afterinstallation or wiring work in order to avoid electric shock.


3-2

3.1 Caution on cable selection

3.1.1 FX1N-485-BD, FX2N-485-BD, FX2NC-485ADP

Number of cables connected to terminal and their specification

3.1.2 FX0N-485ADP

3.1.3 FX2-40AW

1 ) The terminal screws for the terminal block of the FX2-40AW are M3.5 screws, therefore crimpstyle terminal (see drawing) suitable for use with these screws should be fitted to the cablefor wiring.

2 ) The terminal tightening torque is 0.5 to 0.8 N⋅m (5 to 8 kgf⋅cm), tighten securely to avoidmalfunction.

FX1N-485-BD, FX2N-485-BD FX2NC-485ADP

When connecting 1 cableAWG26-16

AWG26-16

When connecting 2 cables AWG26-20

Tightening torque 0.6N%m 0.4 to 0.5N%m

6mm(0.23")

FX1N-485-BD,FX2N-485-BD

8mm(0.32")

FX2NC-485ADP

To connect the RS-485(RS-422) unit, use a shielded twist-pair cable. The cable model must beAWG 26 to 16, and the maximum tightening torque must be 0.6 N%m (6 kgf%cm). If a cable otherthan the AWG 26 to 16 is used, normal communication cannot be assured as the terminal maybe imperfectly contacted. It is recommended to insert a cable integrated by a crimping tool intothe terminal.

1 ) The terminal screws of the FX(0N)-485ADP are M3 screws, therefore, crimp style terminal(see drawing) suitable for use with these screws should be fitted to the cable for wiring.

2 ) The terminal tightening torque is 0.5 to 0.8 N⋅m (5 to 8 kgf⋅cm), tighten securely to avoidmalfunction.


3-3

3

3.2 Using RS-232C InterfaceBelow is a typical wiring example. Please wire similar to the following pin name, when a pinnumber on the side of a counterpart machine differs.

3.2.1 Using RS Instruction or Computer Link

1 ) Terminal specification device

Note;When using ER and DR signals, please also check if RS and CS signals are needed according tothe RS-232C device specifications.

2 ) Modem specification device

Note;The FX0N-232ADP and FX2NC-232ADP does not monitor the CD pin (pin8).

3 ) Computer link Please refer to 2.2.1 1) for wiring.

RS-232C Device Side

Signalname

FG

RD(RXD)

SD(TXD)

RSRTS)

SG(GND)

CS(CTS)

Uses CS, RS

-

2

3

7

5

8

9-pinD-SUB

25-pinD-SUB

1

3

2

4

7

5

Uses DR, ER

9-pin D-SUB

25-pinD-SUB

-

2

3

4

5

6

1

3

2

20

7

6

Signalname

FG

RD(RXD)

SD(TXD)

ER(DTR)

SG(GND)

DR(DSR)

Programmable Controller Side

Signalname

FX0N-232ADP

FX-232ADP

- 1

RD(RXD)

SD(TXD)

FG

ER(DTR)

SG(GND)

DR(DSR)

FX2N-232-BDFX1N-232-BD

2

3

4

5

6

3

2

20

7

6

FX2NC-232ADP

Programmable Controller Side

FX2NC-232ADP

FX-232ADP

- 1

RS-232C Device Side

Uses CS, RS Uses DR, ER

- 8

Signalname

FG

RD(RXD)

SD(TXD)

ER(DTR)

SG(GND)

DR(DSR)

CD(DCD)


1

FX0N-232ADP

3

2

20

7

6

Signalname

FG

RD(RXD)

SD(TXD)

RS(RTS)

SG(GND)

CS(CTS)

CD(DCD)

-

2

3

7

5

8

9-pinD-SUB

1

25-pinD-SUB

1

3

2

4

7

5

8

Signalname

FG

RD(RXD)

SD(TXD)

ER(DTR)

SG(GND)

DR(DSR)

FG

9-pinD-SUB

-

2

3

4

5

6

1

25-pinD-SUB

1

3

2

20

7

6

8

2

3

4

5

6


3-4

3.2.2 Using FX2N-232IF

The signal wiring of the RS-232C equipment varies depending on the RS-232C connectionspecifications. Check the specifications of the RS-232C equipment used, then connect thesignals correctly. Representative wiring examples are shown below.

1 ) Terminal specification device (No control line)Setting communication format (BFM #0); b9=0, b8=0

Communication is performed inaccordance with the conditiondetermined by the software inthe FX 2 N -232 IF and thecounterpart equipment.

2 ) Terminal specification device (Use control line)a ) Standard RS-232C mode (Use cross cable)

Setting communication format (BFM #0); b9=0, b8=1 As the carrier to send (CS) signal pin of the FX2N-232IF itself receives the request to send (RS) signal, signal transfer is performed as if the counterpart equipment is functioning.

Note:

*1 When the CD signal is not monitored, the CD signal pin is not required to be connected. With regard to the CD signal, the FX2N-232IF only indicates the status.

*2 The FX2N-232IF only indicates the status.

P rogram m able C ontro lle r S ideS igna lnam e

R D (R X D )

S D (TX D )

S G (G N D )

FX 2N-232IF

2

3

5

R S -232C D evice S ideS igna lnam e

R D (R X D )

S D (TX D )

S G (G N D )

2

3

5

9-p inD -S U B

25-p inD -S U B

3

2

7


R D (R X D )

S D (TX D )

R S (R TS )

FX 2N-232IF

2

3

7

R S -232C D ev ice S ideS igna lnam e

2

3

7

9-p inD -S U B

25-p inD -S U B

3

2

4

C D (D C D )

C S (C TS )

E R (D TR )

1

8

4

1

8

4

8

5

20

6

5

6

7

D R (D TR )

S G (G N D )

6

5

R D (R X D )

S D (TX D )

R S (R TS )

C D (D C D )

C S (C TS )

E R (D TR )

D R (D TR )

S G (G N D )

*1 *1

*2 *2


3-5

3

b ) Interlink connection mode (Use interlink serial cross cable)Setting connection format (BFM #0); b9=1, b8=1

In the interlink connection mode, data exceeding 512 bytes (upper limit of the receive buffer in the FX2N-232IF) can be received.

Note:

*1 The FX2N-232IF only indicates the status.

*2 In this mode, the request to send (RS) signal functions as the signal to enable receive in the FX2N-232IF.When receiving data exceeding 512 bytes, the FX2N-232IF sets the request to send (RS) signal to “OFF” and requests the counterpart equipment to suspend the send operation. When the data saved in the receive buffers is read by the sequence program, the remaining data can be received.

3 ) Modem specification device Standard RS-232C mode (Using straight cable)Setting communication format (BFM #0); b9=0, b8=1

Note:

*1 The FX2N-232IF indicates the status exclusively.

*2 When the CD signal is not monitored, the CD signal pin is not required to be connected. With regard to the CD signal, the FX2N-232IF indicates the status exclusively.

*3 When the CI signal is not required, the CI signal pin is not required to the connected. With regard to the CI signal, the FX2N-232IF indicates the status exclusively.


R D (R X D )

S D (TX D )

R S (R TS )

FX 2N-232IF

2

3

7


2

3

7

9-p inD -S U B

25-p inD -S U B

3

2

4

C S (C TS )

E R (D TR )

8

4

8

4

5

20

6

5

6

7

D R (D TR )

S G (G N D )

6

5

R D (R X D )

S D (TX D )

R S (R TS )

C S (C TS )

E R (D TR )

D R (D TR )

S G (G N D )

*1 *1

*2 *2


R D (R X D )

S D (TX D )

R S (R TS )

FX 2N-232IF

2

3

7


2

3

7

9-p inD -S U B

25-p inD -S U B

3

2

4

C D (D C D )

C S (C TS )

E R (D TR )

1

8

4

1

8

4

8

5

20

6

5

6

7

D R (D TR )

S G (G N D )

6

5

R D (R X D )

S D (TX D )

R S (R TS )

C D (D C D )

C S (C TS )

E R (D TR )

D R (D TR )

S G (G N D )

*1 *1

*2 *2

9 22C I (R I) 9 C I (R I)*3 *3


3-6

3.3 Using RS-485 Interface

3.3.1 Wiring Selection

The wiring of RS-485 can either be one-pair or two-pair. The wiring method is decided accordingto application usage. Please select the wiring method from the table below.

&…Recommendation, '…OK, ×…Cannot use

Note:

*1 When this product is added to the system, please match the wiring to the existing method ofthe system.

*2 When using an FX2N-485-BD with this wiring method, remember to take account of/or ignorethe “echo” of the commands sent from the FX2N programmable controller.

*3 Please use the FX2N programmable controller and FX2N-485-BD together.Full-duplex combination cannot be achieved with other configurations.

*4 For wiring parallel link, see section 2.4.

3.3.2 Terminal Resistor

A terminal resistor must be used at both ends of the communication line as described in section2.3.3 and 2.3.4.

Usage One-pair wiring Two-pair wiring

No protocol(Use RS instruction) *1

Half-duplex communication &*2 '

Full-duplex communication *3 × '

Dedicated protocol (Use computer link)*1

It is necessary to set the messagewait time to 70 ms or less. × '

It is not necessary to set the massage wait time to 70 ms or less. &*2 '

Use the on-demand function × '

Parallel link *4 & '

N:N network ' ×

Orange Orange Brown

Brown Brown Brown

330 Ω1/4 W

110 Ω1/2 W

1 ) In the case of two-pair wiring, connect the terminal resistor(330Ω, 1/4W) between terminals SDA and SDB and betweenterminals RDA and RDB. Use the resistors offered asaccessories with the product.

2 ) In the case of one-pair wiring, connect the terminal resistor(110Ω, 1/2W) between terminals RDA and RDB. Use theresistors offered as accessories with the product.


3-7

3

3.3.3 One-pair Wiring

Note:

*1 R is a terminating resistor (110Ω)

*2 Make sure to connect the shield of the appropriate cable with the FX2N-485-BD, FX1N-485-BDor FX2NC-485ADP to ground that has a resistance of 100Ω or less (Class D grounding).

*3 Make sure to connect the terminal FG to the ground terminal of a programmablecontroller grounded with resistance of 100Ω or less (Class D grounding).However, for a computer link unit of the A series programmable controller, see the manual ofthe computer link unit.

*4 When using an RS-232C/485 converter, use the FX-485PC-IF.Have in mind that "echo" occurs on the RS-232C side if one-pair wiring is performed using theFX-485PC-IF.

*5 In the case of FX2NC-485ADP

Class D grounding

R*1

SDA

SDB

RDA

RDB

SDA

SDB

RDA

RDB

SDA

SDB

RDA

RDB

LINKSG*3FG

SDA

SDB

RDA

RDB

SG*3FG

R*1

RS-485 unit *4

SG

*2SG

(NC)*5

FX2NC-485ADPFX1N-485-BD,FX2N-485-BD FX

A series programmable(0N)-485ADP controller's computer link unit

StationNo. 0

StationNo. 1

StationNo. 15


3-8

3.3.4 Two-pair Wiring

Note:

*1 R is a terminating resistor (330Ω)

*2 Make sure to connect the shield of the appropriate cable with the FX2N-485-BD, FX1N-485-BDor FX2NC-485ADP to ground that has a resistance of 100Ω or less (Class D grounding).

*3 Make sure to connect the terminal FG to the ground terminal of a programmablecontroller grounded with resistance of 100Ω or less (Class D grounding).However, for a computer link unit of the A series programmable controller, see the manual ofthe computer link unit.

*4 When using an RS-232C/485 converter, use the FX-485PC-IF.

*5 In the case of FX2NC-485ADP

Class D grounding

R*1

R*1

SDA

SG

SG*3FG

StationNo. 1

StationNo. 0

SG*3FG

StationNo. 15 R*1

R*1

RS-422/RS-485 unit *4

SG

*2

(NC)*5

FX2NC-485ADPFX1N-485-BD,FX2N-485-BD FX

A series programmable(0N)-485ADP controller's computer link unit

SDB

RDA

RDB

SDA

SDB

RDA

RDB

SDA

SDB

RDA

RDB

LINK

SDA

SDB

RDA

RDB


3-9

3

3.4 Parallel Link

3.4.1 FX2N(1N)-485-BD and FX0N-485ADP

1 ) One-pair Wiring

Note:

*1 Connect the terminal FG to the ground terminal of a programmable controller grounded with a resistance of 100Ω or less (Class D grounding). If the programmable controller is not equipped with a ground terminal, connect the terminal FG directly to a ground with the resistance of 100Ω or less (Class D grounding).

2 ) Two-pair Wiring

Note:


RDB

RDA

SDA

SDB

SDA


Terminatingresistor110Ω

FX0N-485ADP

Terminatingregistor110Ω

RDA

RDB

SG

SDB

LINKSG

FG *1

RDB

RDA

SDA

SDB

SDA



FX0N-485ADP


RDA

RDB

SG

SDB

LINKSG

FG *1




3-10

3.4.2 FX0N-485ADP and FX0N-485ADP

1 ) One-pair Wiring

Note:


2 ) Two-pair Wiring

Note:


RDB

RDA

SDA

SDB

SDA


FX0N-485ADP


RDA

RDB

LINKSG

SDB

LINKSG

FG *1FG

FX0N-485ADP

RDB

RDA

SDA

SDB

SDA

FX0N-485ADP


FX0N-485ADP


RDA

RDB

LINKSG

SDB

LINKSG

FG *1FG




3-11

3

3.4.3 FX2N(1N)-485-BD and FX2N(1N)-485-BD

1 ) One-pair Wiring

2 ) Two-pair Wiring

RDB

RDA

SDA

SDB

SDA



RDA

RDB

SG

SDB

SG


Class D grounding


RDB

RDA

SDA

SDB

SDA



RDA

RDB

SG

SDB

SG



Class D grounding




3-12

3.4.4 FX2NC-485ADP and FX0N-485ADP

1 ) One-pair Wiring

Note:


2 ) Two-pair Wiring

Note:


SDB

SDA

RDA

SDA

SDB

RDA

RDB RDB

LINKSG

FG*1

FX0N-485ADPFX2NC-485ADP

SG



SDB

SDA

RDA

SDA

SDB

RDA

RDB

SG

RDB

LINKSG

FG*1

FX0N-485ADPFX2NC-485ADP






3-13

3

3.4.5 FX2N(1N)-485-BD and FX2NC-485ADP

1 ) One-pair Wiring

2 ) Two-pair Wiring

SDB

SDA

RDA

SDA

SDB

RDA

RDB

SG

RDB

SG


Class D grounding

FX2NC-485ADP



SDB

SDA

RDA

SDA

SDB

RDA

RDB

SG

RDB

SG


Class D grounding

FX2NC-485ADP






3-14

3.4.6 FX2NC-485ADP and FX2NC-485ADP

1 ) One-pair Wiring

2 ) Two-pair Wiring

SDB

SDA

RDA

SDA

SDB

RDA

RDB

SG

RDB

SG

Class D grounding

FX2NC-485ADPFX2NC-485ADP



SDB

SDA

RDA

SDA

SDB

RDA

RDB

SG

RDB

SG

FX2NC-485ADP

Class D grounding

FX2NC-485ADP






3-15

3

3.4.7 FX2-40AW and FX2-40AW

3.4.8 FX2-40AP and FX2-40AP

SB

SASA

SB

SG*1

SG*1

FX2-40AW FX2-40AW Note:

*1 Connect the terminal SG to the terminal SG of the basic unit.Two SG terminals are connected to each other internally.

R

TT

R

FX2-40AP FX2-40AP

Note:

• " " indicates an optical connector. Keep optical connectors away from cablingcarrying high loads.Output terminals (Y000 to Y003) located near optical connectors must have lightloads connector.


3-16

MEMO

FX communication N:N network 4

4-1

4

4. N:N NetworkFor diagnostics, please refer to chapter 12.

4.1 Related Flags and Data Registers

4.1.1 Auxiliary Relays

R : Read only W : Write only M : Master station L : Slave station

Note:*1 The number of communication errors that have occurred in each station cannot be counted in

the CPU error status, the program error status or the stop status.

*2 Number in accordance with the slave station No.

Example: FX0N, FX1S……………Slave station No.1 is M505, Slave station No.2 is M506, ~ Slave station No.7 is M511.

FX2N, FX2N, FX1N……Slave station No.1 is M8184, Slave station No.2 is M8185, ~ Slave station No.7 is M8190.

Attribute

Auxiliary relays

Name Description ResponsetypeFX0N,

FX1S

FX1N, FX2N, FX2NC

R M8038 N:N network parameter setting

Used to set N:N network parameters M, L

R M504 M8183 Communication error of master station

ON when communication error occurs in the master station.*1

L

RM505 to M511 *2

M8184 to M8190 *2

Communication error of slave station

ON when communication error occurs in the slave station.*1

M, L

R M503 M8191 Data communication ON when communicating to another station. M, L

Note:• Devices M503 to M511 in the FX0N and FX1S cannot be used in the program.

These devices are used by the N:N network.


4-2

4.1.2 Data Registers

R : Read only W : Write only M : Master station L : Slave station

*1 The number of communication errors occurred in its own station cannot be counted in theCPU error status, the program error status or the stop status.

*2 Number (Same meaning but looks better.) in accordance with the slave station No.Slave station No.1 is D204, D212, slave station No.2 is D205, D213, … slave station No.7 is D210, D218.

*3 Number (Same meaning but looks better.) in accordance with the slave station No.Slave station No.1 is D8204, D8212, slave station No.2 is D8205, D8213, … slave station No.7 is D8210, D8218.

Attribute

Data Registers

Name Description ResponsetypeFX0N,

FX1S

FX1N, FX2N, FX2NC

R D8173 Station No. Saves its own station No. M, L

R D8174 Total number of slave stations

Saves total number of slave stations M, L

R D8175 Refresh range Saves refresh range M, L

W D8176 Station number setting Sets its own station No. M, L

W D8177 Total slave station number setting

Sets total number of slave stations M

W D8178 Refresh range setting Sets refresh range M

W/R D8179 Retry count setting Sets retry count M

W/R D8180 Comms time-out setting Sets comms time-out M

R D201 D8201 Current network scan time Saves current network scan time M, L

R D202 D8202 Maximum network scan time

Saves maximum network scan time M, L

R D203 D8203 Number of communication error at master station

Number of communication error at master station *1

L

R D204 to D210 *2

D8204 to D8210 *3

Number of communication error at slave station

Number of communication error at slave station *1

M, L

R D211 D8211 Code of communication error at master station

Code of communication error at master station *1 L

R D212 to D218 *2

D8212 to D8218 *3

Code of communication error at slave station

Code of communication error at slave station *1 M, L

D219 to D255 Not used For internal processing

Note;• Devices M503-M511 and D201-D255 in the FX0N and FX1S cannot be used in the

program. These devices are used by the N:N network.


4-3

4

4.2 SettingN:N settings become valid when the program is run or when the power of the programmablecontroller is turned ON.

4.2.1 Setting the Station No. (D8176)

Set a value 0 to 7 to the special data register D8176.

4.2.2 Setting the Total Number of Slave Stations (D8177)

Set value Description

0 Master station

1 to 7 Slave station No.Example: 1 is slave station No.1, 2 is slave station No.2

Set a value 1 to 7 to the special data register D8177. (Default = 7)This setting is not required for the slave station. Set value Description

1 1 slave station

2 2 slave stations

: :

7 7 slave stations


4-4

4.2.3 Setting the Refresh Range (D8178)

Set a value 0 to 2 to the special data register D8178. (Default = 0)This setting is not required for the slave station.The devices used in each pattern are occupied by all the stations for the N:N network.

1 ) In the case of pattern 0 (FX0N, FX1S, FX1N, FX2N, FX2NC)

Communicationdevice

Refresh range

Pattern 0(FX0N, FX1S, FX1N,

FX2N, FX2NC)

Pattern 1(FX1N, FX2N, FX2NC)

Pattern 2(FX1N, FX2N, FX2NC)

Bit device (M) 0 point 32 points 64 points

Word device (D) 4 points 4 points 8 points

Station No.

Device No.

Bit device (M) Word device (D)

0 point 4 points

No.0 D0 to D3

No.1 D10 to D13

No.2 D20 to D23

No.3 D30 to D33

No.4 D40 to D43

No.5 D50 to D53

No,6 D60 to D63

No.7 D70 to D73

Note;• Please set the refresh range to pattern 0. When setting it other than pattern 0, all FX0N

and FX1S series units in the system experience a communications error.In this case, please note that link time becomes as long as the FX0N and FX1S

communication error is occurring.


4-5

4

2 ) In the case of pattern 1 (FX1N, FX2N, FX2NC)

3 ) In the case of pattern 2 (FX1N, FX2N, FX2NC)

4.2.4 Setting Retry Count (D8179)

Set a value 0 to 10 to the special data register D8178. (Default = 3)This setting is not required for the slave station.If a master station tries to communicate with the slave station at this retry count (or over),communication error occur in the station.

4.2.5 Setting Comms Time-out (D8180)

Set value 5 to 255 to the special data register D8179. (Default = 5)This value multiplied by 10(ms) is duration of the comms time-out.Comms time-out is the communication dwell time between the master station and slave station.

Station No.

Device No.


32 points 4 points

No.0 M1000 to M1031 D0 to D3

No.1 M1064 to M1095 D10 to D13

No.2 M1128 to M1159 D20 to D23

No.3 M1192 to M1223 D30 to D33

No.4 M1256 to M1287 D40 to D43

No.5 M1320 to M1351 D50 to D53

No.6 M1384 to M1415 D60 to D63

No.7 M1448 to M1479 D70 to D73

Station No.

Device No.


64 points 8 points

No.0 M1000 to M1063 D0 to D7

No.1 M1064 to M1127 D10 to D17

No.2 M1128 to M1191 D20 to D27

No.3 M1192 to M1255 D30 to D37

No.4 M1256 to M1319 D40 to D47

No.5 M1320 to M1383 D50 to D57

No,6 M1384 to M1447 D60 to D67

No.7 M1448 to M1511 D70 to D77


4-6

4.2.6 Program Used for Setting

Make sure to write the program above step 0 as the N:N network parameter setting program.This program does not require to be executed, because it becomes effective automatically when itis programmed in this position.

M8038 FNC 12MOV

K 0 D8176Station No. setting:Required for masterstation (Set range: 0 to 7)

FNC 12MOV

K 2 D8177Total number of slavestations: 2(Setting range: 1 to 7)

FNC 12MOV

K 1 D8178Refresh range setting:Pattern 1(Set range: 1 to 2)

FNC 12MOV

K 3 D8179 Retry count setting:3 (3times)

FNC 12MOV

K 6 D8180 Comms time-out setting:6 (60ms)

Not required forslave station

0

Note:

• Setting of the parameters for the N:N network is started at step 0 (LD M8038), and finished when any instruction or device other than the program above is processed.


4-7

4

4.3 Example Program

4.3.1 System Configuration

• Refresh range: 32 bit devices and 4 word devices (Pattern 1)• Retry count: 3 times• Comms time-out: 5 (50 ms)

4.3.2 Operations

The following operations are performed in the system configuration above.

1 ) The input points X000 to X003 (M1000 to M1003) in the master station are output to theoutput points Y010 to Y013 in the stations Nos.1 and 2.

2 ) The input points X000 to X003 (M1064 to M1067) in the station No.1 are output to the outputpoints Y014 to Y017 in the master station and the station No.2.

3 ) The input points X000 to X003 (M1128 to M1131) in the station No.2 are output to the outputpoints Y020 to Y023 in the master station and the station No.1.

4 ) The data register D1 in the master station is specified as the set value of the counter C1 inthe station No.1.The contact (M1070) status of the counter C1 is reflected on the output point Y005 in themaster station.

5 ) The data register D2 in the master station is specified as the set value of the counter C2 inthe station No.2.The contact (M1140) status of the counter C2 is reflected on the output point Y006 in themaster station.

6 ) The value of the data register D10 in the station No.1 and the value of the data register D20in the station No.2 are added in the master station, and saved to the data register D3.

7 ) The value of the data register D10 in the master station and the value of the data registerD20 in the station No.2 are added in the station No.1, and saved to the data register D11.

8 ) The value of the data register D10 in the master station and the value of the data registerD10 in the station No.1 are added in the station No.2, and saved to the data register D21.

FX 2N FX 2N

FX 2N -485-BD FX 2N -485-BD FX 2N -485-BD

Master station (No.0) Slave station (No.1) Slave station (No.2)


4-8

4.3.3 Example of Setting Program

For the setting program of the master station and the stations Nos.1 and 2, refer to the programbelow.

4.3.4 Example of Error Program

* A station cannot recognize its own error. An error program for each station is not necessary.

Master station Slave station No.1 Slave station No.2 Remarks

D8176 K0 K1 K2 Station No.

D8177 K2 Total slave station : 2 stations

D8178 K1 Refresh range : Pattern 1

D8179 K3 Retry count : 3 times (default)

D8180 K5 Comms time-out : 50 ms (default)

Not required forslave station

M8038 FNC 12MOV

K 0 D8176Station No. setting:Required for masterstation (Set range: 0 to 7)

FNC 12MOV

K 2 D8177Total number of slavestations: 2(Setting range: 1 to 7)

FNC 12MOV

K 1 D8178Refresh range setting:Pattern 1(Set range: 1 to 2)

FNC 12MOV

K 3 D8179 Retry count setting:3 (3times)

FNC 12MOV

K 5 D8180 Comms time-out setting:5 (50ms)

0

M8183Master communication error

Y000

M8184Slave 1 communication error

Y001

M8185Slave 2 communication error

Y002

M8191Data communication

Y003

Continued to a), b) or c) in "4.3.5 Program".

*

*

*


4-9

4

4.3.5 Example of Operation Program

a ) Program of master station

Slave 1communicationerror

M8184

Slave 2communication error

M8185

Contact of slave 2 C2device

M1140Y006

Operation 6)

Operation 7), 8)

Operation 5)


M8185

END

RUN monitor

M8000

Slave 1communication error

M8184

Slave 2communication errorM8185

Slave 1communication errorM8184

Contact of slave 1 C1device

M1070Y005

Operation 1)

Operation 2)

Operation 3)

Operation 4)

D 0

D 2

D 3

K1M1000

K1Y014

K1Y020

D 1

K 10

K 10

K 10

K1X000

K1M1064

K1M1128

K 10

FNC 12MOV

FNC 12MOV

FNC 12MOV

FNC 12MOV

FNC 12MOV

FNC 12MOV

FNC 12MOV


4-10

b ) Program of slave station No.1

Mastercommunicationerror

M8183K1M1000 K1Y010

Counter reset

Counter input

X000C 1

RST C 1

K1X000 K1M1064

K1M1128 K1Y020

Slave 2communicationerrorM8185

D 1

C 1Y005

M1070

Operation 4)

X001



M8185

K 10 D 10

Contact ofslave 2 C2device

M1140Y006

END

D 20 D 11D 0M8185

Operation 6), 8)

Operation 7)

Operation 1)

Operation 2)

Operation 3)

Operation 5)

FNC 12MOV

FNC 12MOV

FNC 12MOV

FNC 12MOV

FNC 20ADD


4-11

4

c ) Program of slave station No.2

MastercommunicationerrorM8183

Counter reset

RST C 2

FNC 12MOV

FNC 12MOV

Slave 1communicationerrorM8184

Y005

Contact ofslave 1 C1device

Slave 1communicationerrorM8184 M1070

FNC 12MOV

K 10 D 20

Counter inputX000

C 2

END

FNC 20ADD

D 10 D 21D 0

C 2Y006 Operation 5)

D 2

M1140

M8184


Operation 6), 7)

Operation 4)

Operation 1)

Operation 2)

Operation 3)

X001

K1Y014

K1M1128

FNC 12MOV

K1Y010

K1M1064

K1X000

K1M1000


4-12

MEMO

FX communication Parallel link 5

5-1

5

5. Parallel linkData transfer with FX2N, FX2NC, FX1N, FX, FX2C programmable controllers can be performed on a1:1 basis for 100 auxiliary relays and 10 data registers. Data transfer with FX1S, FX0N

programmable controller can be performed on a 1:1 basis for 50 auxiliary relays and 10 dataregisters.For system configuration, refer to subsection 1.2.2.

5.1 Related Flags and Data Registers Device Operation

M8070 Driven when the programmable controller is a master station in a parallel link.

M8071 Driven when the programmable controller is a slave station in a parallel link.

M8072 ON while the programmable controller is operating in a parallel link.

M8073 ON when M8070/M8071 are incorrectly set during parallel link operations.

M8162 High speed mode for parallel link, 2 data words read/write only.

M8070 Parallel link watchdog time (Default: 500 ms).


5-2

5.2 Mode and Link Device

5.2.1 Normal Mode (Special auxiliary relay M8162: OFF)

Note;Parallel link is possible between PLC’s in the same series, or in other series as long as they are in the group. However, parallel link between each different group cannot be achieved. Groups are separated as follows.

FX2N, FX2NC, FX1N, FX, FX2C FX1S, FX0N

Communication devices

Master →→→→ Slave

M800 to M899 (100 points),D490 to D499 (10 points)


Slave → → → → Master



Communication time 70 (ms) + Scan time of master (ms) + Scan time of slave (ms)

Group No. Series

Group 1 FX2N, FX2NC

Group 2 FX1N

Group 3 FX1S

Group 4 FX0N

Group 5 FX, FX2C

M8000M8071

D -D

D -D

M -M

M -M

D -D

D -D

M -M

M -M

M8000

Master Automaticcommunication

Slave

M8070


5-3

5

5.2.2 High Speed Mode (Special auxiliary relay M8162: ON)

Note;Parallel link is possible between PLC’s in the same series, or in other series as long as they are in the group. However, parallel link between each different group cannot be achieved. Groups are separated as follows.

FX2N, FX2NC, FX1N, FX, FX2C FX1S, FX0N

Communication devices

Master →→→→ Slave D490, D491 (2 points) D230, D231 (2 points)

Slave → → → → Master D500, D501 (2 points) D240, D241 (2 points)

Communication time 20 (ms) + Scan time of master (ms) + Scan time of slave (ms)

Group No. Series

Group 1 FX2N, FX2NC

Group 2 FX1N

Group 3 FX1S

Group 4 FX0N

Group 5 FX, FX2C

M8162D ,D

D ,D

M8000M8070

M8162

M8000M8071

MasterAutomaticcommunication

Slave


5-4

5.3 Example Program

5.3.1 Normal Mode

The ON/OFF status of the inputs X000 to X007 in the master station is output to Y000 to Y007 inthe slave station (#). When the calculation result (D0+D2) in the master station is 100 or less,Y010 in the slave station is turned on ($). The ON/OFF status of M0 to M7 in the slave station isoutput to Y000 to Y007 in the master station ((). The value of D10 in the slave station is set tothe timer (T0) in the master station ()).

5.3.2 High Speed Mode

When the calculation result (D0+D2) in the master station is 100 or less, Y010 in the slave stationis turned on (#). The value of D10 in the slave station is set to the timer (T0) in the master station($).

Master stationM8000

M8070

M8000

M8000

X010T0

D500END

Slave stationM8000

M8071

M8000

M8000

X010

END

M10Y010

FNC 20ADD

FNC 12MOV FNC 12

MOVFNC 12

MOV

K2M800K2X000

D490D2D0

K2Y000K2M900

K2Y000K2M800

M10D490 K100

K2M900K2M0

D500D10

FNC 12MOV

FNC 12MOV

FNC 10CMP

M8000M8070

M8000

X010T0

D500END

M8162

Master station Slave stationM8000

M8071

M8000

END

M8162

M10Y010

X010

D2D0 D490D490 K100 M10

D10 D500

FNC 20ADD

FNC 10CMP

FNC 12MOV

Note;In the normal mode, “FNC 81 PRUN” instruction can be used for #.However, this instruction is only supported for FX1S, FX1N, FX, FX2C, FX2N, FX2NC

programmable controller.

FX communication Communication format 6

6-1

6

6. Communication format (D8120)This chapter explains setting the communication between no protocol communication (RSinstruction) and computer link. For the RS instruction, refer to Section 9. For computer link, referto Sections 7 and 8.

6.1 What Is Communication Format?The communication format decides the communication setting (data length, parity, and baud rate,etc.) between computer link and no protocol communication (RS instruction).The communication format can be set using the special data register D8120* in a programmablecontroller. Set D8120 in accordance with external equipment used.After modifying the setting of the D8120, make sure to turn off the power of the programmablecontroller, then turn it on again.

* In the FX2N, FX2NC series, this setting can be performed using parameters.

6.2 Related Flags and Data Registers

6.2.1 Special Auxiliary Relays

( ) indicates the applicable application.

6.2.2 Special Data Registers

( ) indicates the applicable application.

Special auxiliary relays DescriptionM8121 Data transmission delayed (RS instruction)M8122 Data transmission flag (RS instruction)M8123 Finished receiving flag (RS instruction)M8124 Carrier detection flag (RS instruction)M8126 Global flag (computer link)M8127 On-demand handshake flag (computer link)M8128 On-demand error flag (computer link)

M8129On-demand word/byte changeover (computer link)Time out evaluation flag (RS instruction)

M8161 8 bits/16 bits changeover flag (RS instruction)

Special data registers DescriptionD8120 Communication format (RS instruction, computer link)D8121 Station No. setting (computer link)D8122 Number of remaining data to be transmitted (RS instruction)D8123 Number of receive data (RS instruction)D8124 Data header <Initial value: STX> (RS instruction)D8125 Data terminator <Initial value: ETX> (RS instruction)D8127 On-demand head device register (computer link)D8128 On-demand data length register (computer link)D8129 Data network Time-out timer value (RS instruction, computer link)


6-2

6.3 Communication Format (D8120)

*1 Make sure to set to “0” when computer link used.

*2 Make sure to set to “0” when no protocol communication used.

*3 When using RS-485 (RS-422) interface, make setting control line the same as this. But controlline of communication is the same as when not using control line operation. This connection (RS-485) is supported in the FX0N, FX1S, FX1N, FX2N, FX2NC series.

BitNo. Name

Description

0 (bit = OFF) 1 (bit = ON)b0 Data length 7 bit 8 bit

b1b2 Parity

(b2, b1)( 0, 0) : None( 0, 1) : Odd( 1, 1) : Even

b3 Stop bit 1 bit 2 bit

b4b5b6b7

Baudrate(bps)

(b7, b6, b5, b4) (b7, b6, b5, b4)( 0, 0, 1, 1) : 300 ( 0, 1, 1, 1) : 4,800( 0, 1, 0, 0) : 600 ( 1, 0, 0, 0) : 9,600( 0, 1, 0, 1) : 1,200 ( 1, 0, 0, 1) : 19,200( 0, 1, 1, 0) : 2,400

b8*1 Header None Effective (D8124) Default : STX (02H)

b9*1 Terminator None Effective (D8125) Default : ETX (03H)

b10b11b12

Controlline

Noprotocol

(b12, b11, b10)( 0, 0, 0) : No use <RS-232C interface>( 0, 0, 1) : Terminal mode <RS-232C interface>( 0, 1, 0) : Interlink mode <RS-232C interface > (FX2N V2.00 or

more)( 0, 1, 1) : Normal mode 1 <RS-232C interface>,

<RS-485 (RS-422) interface>*3( 1, 0, 1) : Normal mode 2 <RS-232C interface> (FX, FX2C only)

Computerlink

(b12, b11, b10)( 0, 0, 0) : RS-485 (RS-422) interface( 0, 1, 0) : RS-232C interface

b13*2 Sum check Sum check code is not added Sum check code is added automatically

b14*2 Protocol No protocol Dedicated protocol

b15*2Transmission

controlprotocol

Protocol format 1 Protocol format 4


6-3

6

6.4 Example of setting programWhen setting the contents shown on the left, perform programming as follows.

M8002

0000 1100 1000 1110b15 b0

0 C 8 ED8120 =

FNC 12MOV H0C8E D8120

Data length 7 bits

Parity Even

Stop bit 2 bits

Baud rate 9600 bps

Protocol No protocol

Header No used

Terminator No used

Control line Normal mode 1


6-4

MEMO

FX communication Computer link 7

7-1

7

7. Computer LinkThis chapter explains the details and methods of specifying dedicated protocol used for linking ofthe FX programmable controller and computer. The dedicated protocol is available in two types,format 1and format 4 (the format names conform to the dedicated protocols used in the computerlink unit of the A series programmable controller).In this chapter FX2N-232-BD, FX1N-232-BD, FX0N-232ADP and FX-232ADP refer to 232ADP,FX2N-485-BD, FX1N-485-BD, FX0N-485ADP and FX-485ADP refer to 485ADP, FX-485PC-IF referto 485PC-IF. When interface of programmable controller using RS-232C, please after read 232ADP instead of485ADP.

7.1 Data Flow by LinkShown below are drawings of data flow for reading, writing, and status control of theprogrammable controller.

1 ) The computer reads data from programmable controller.

2 ) The computer sends data to programmable controller.

*OS (operating system) is the software for operating (or using) effectively the resources such asthe CPU, memory, terminal, file and network.

OS*

RS-232C

(2)Command

(9)Various data

(12)Response

Device memoryinformation (Read)Programmablecontroller CPUinformation (Read)

(1)

(10) (11)

Computer

Req

uest

DataComn.Prog.

485ADP

(4)

(7)(14)

ProgramOS*

Devicememory,etc.

Programmable controller

Data(6) (5)Read

RS-485

(13)

485PC-IF

Signalconvertinginterface

(3)(8)

%

%

(3) (4)

(7) (6)

485PC-IF RS-485 485ADP

OS*

(1)

Computer

Req

uest

DataComn.Prog.

ProgramOS*

Devicememory,etc.


(5)Write

(2)Command, data,etc.

(8)Response

RS-232C

Device memoryinformation (Write)Programmablecontroller CPUinformation (Write)

%

%


7-2

3 ) Programmable controller sends data to the computer.

*OS (operating system) is the software for operating (or using) effectively the resources such asthe CPU, memory, terminal, file and network.

(6)Data (5)(4)Data

RS-232C 485PC-IF RS-485 485ADP

On-demand data

(2)ReadData(3) (1)Sendrequest+data write

ProgramOS*

Devicememory,etc.


(7)Write

OS*

Computer

DataComn.Prog.


7-3

7

7.2 Information Needed Before Programming

7.2.1 Programmable Controller Operation

The operation and the scan time of programmable controller using computer link is as follows.While the programmable controller is running, access requests to the programmable controllerfrom the computer are processed on every END processing. The processing of Send or Receivedata is performed using interrupts.Therefore, during the processing of Send or Receive, the scan time is extended; typically byabout 10%. The scan time can be monitored using the special data registers D8010 to D8012 ofthe programmable controller.

Note:

- These are in units of 0.1 ms

7.2.2 Computer Notes

1 ) Conditions under which the transmission sequence is initialized.The transmission sequence of the programmable controller is initialized during the followingconditions.

- When the power is turned on- When data communication is completed normally- When control code EOT or CL is received- When a NAK control code is received- After the time-out check time has elapsed (see section 7.4.4)

2 ) Occurrence of a framing error at the computer sideWhen a commercial RS-485 interface is used at the computer, if nothing is transmitted fromthe programmable controller to the computer at the interface, a framing error may occur atthe computer.Accordingly, read and skip the data at the computer until any one of STX, ACK, and NAK istransmitted from the programmable controller.

3 ) NAK response from programmable controllerNAK response from the programmable controller to the computer is done when an error isdetected.

4 ) Command transmission from computerWhen sending a command from the computer to the programmable controller usingdedicated protocol, only send the command after a gap of approximately two PLC scansfrom the time the data communications required by the previous command was elapsed.

Caution:When using RS-485 wiring (one pair, see section 2.3.3) remember to take account of/orignore the “echo” of the commands sent from the computer.


7-4

7.3 How to Read a Control Protocol Diagram1 ) When the computer reads data from the programmable controller

(computer ← programmable controller)

a ) Areas A and C indicate transmission from the computer to the programmable controller.b ) Area B denotes transmission from the programmable controller to the computer.c ) The computer program is created so that the data is transmitted in the order read from left

to right, and the protocol determines that the data is sent in the sequence A, B, C.(Example: In area A, ENQ is transmitted followed by all other data, starting to the right, afterthe ENQ.)

2 ) When writing data from the computer into the programmable controller (computer → programmable controller)

a ) Areas A indicates transmission from the computer to the programmable controller.b ) Area B denotes transmission from the programmable controller to the computer.c ) The computer program is created so that the data is transmitted in the order read from left

to right, and the protocol determines that the data is sent in the sequence A, B.(Example: In area A, ENQ is transmitted followed by all other data, starting to the right, afterthe ENQ.)

Computer

Programmablecontroller

Data

DataSTX

DataACK

B

ENQ

A C

Data

Data

Computer


ACK

ENQ

A

B


7-5

7

7.4 Basic Formats of Dedicated ProtocolThere are two formats for the dedicated protocol; which may be selected by setting special dataregister D8120(see chapter 6). The difference between these two formats is whether CR + LF is added to each block or not.The protocols are format 1 and format 4. (The format names conform to the computer link unit forthe A series programmable controller.)

Note:

*1 Whether or not to add sum check code can be selected using the communication formatspecial data register D8120.

*2 Whether or not to add terminating CR + LF codes is determined by the protocol selected.

(

)

Control code

Station No.

PLC No.

Command

Message wait

Character

Sum check code *1

Control code CR/LF *2

)

(

Basic format of transmitted data.


7-6

7.4.1 Control Protocol Format 1

Description Control protocol

To read data from the PLC to the computer

To write data from the computer to the PLC

Remarks

1 ) Sum check code is used when the sum check flag is set “Yes” (“b13=1” in special data registerD8120), and not used when set to “No” (“b13=0”).

2 ) When the sum check flag is set to “Yes”, the sum check is made on the characters in theasterisked area.

3 ) In the diagram, the contents of character area A, character area B, and character area Cdepend on the individual system, but do not differ depending on the format of control protocol.For details of each character area, see the link contents.

Computer


E N

Q

StationN

o.

PLC

No.

Com

mand

Message

wait tim

e

Character

area A

Sum

checkcode

StationN

o.S

T X

PLC

No.

Character

area B

E T

X

Sum

checkcode

StationN

o.A

C K

PLC

No.

StationN

o.N

A K

PLC

No.

or

N A

K

StationN

o.

PLC

No.

Error

code

or*

*

Transmission sequence

Computer


E N

Q

Station

No.

PLC

No.

Com

mand

Message

wait tim

e

Character

area C

Sum

checkcode

Station

No.A

C K

PLC

No.

N A

K

Station

No.

PLC

No.

Error code

or

*



7-7

7

7.4.2 Control Protocol Format 4

Description Control protocol

To read data from the PLC to the computer

To write data from the computer to the PLC

Remarks

1 ) Sum check code is used when the sum check flag is set “Yes” (“b13=1” in special data registerD8120), and not used when set to “No” (“b13=0”).

2 ) When the sum check flag is set to “Yes”, the sum check is made on the characters in theasterisked area.

3 ) In the diagram, the contents of character area A, character area B, and character area Cdepend on the individual system, but do not differ depending on the format of control protocol.For details of each character area, see the link contents.

Computer


E N

Q

StationN

o.

PLC

No.

Com

mand

Message

wait tim

e

Character

area A

Sum

checkcode

StationN

o.S

T X

PLC

No.

Character

area B

E T

X

Sum

checkcode

StationN

o.A

C K

PLC

No.

StationN

o.N

A K

PLC

No.

or

N A

K

StationN

o.

PLC

No.

Error code

or*

*


L FC

R

L FC

R

L FC

RL FC

R

L FC

R

Computer


E N

Q

StationN

o.

PLC

No.

Com

mand

Message

wait tim

e

Character

area C

Sum

checkcode

StationN

o.A

C K

PLC

No.

N A

K

StationN

o.

PLC

No.

Error

code

or

*


L FC

R

L FC

R

L FC

R


7-8

7.4.3 Control Protocol Parts Explained

This is to explain the content of data set in each control procedure.

1 ) Control codesThe control codes are listed below.

a ) The programmable controller initializes the transmission sequence when receiving anyone of ENQ, ACK, NAK, and starts.

b ) When EOT, or CL code is received as follows, the programmable controller initializes thetransmission sequence. At this time, no response is made from the programmablecontroller.

Signal Code(Hexadecimal) Description Signal Code

(Hexadecimal) Description

STX 02H Start of Text LF 0AH Line Feed

ETX 03H End of Text CL 0CH Clear

EOT 04H End of Transmission CR 0DH Carriage Return

ENQ 05H Enquiry NAK 15H Not Acknowledge

ACK 06H Acknowledge

Format 1 Format 4

C

LComputer


or

E

O

T

C

LComputer


or

E

O

T

C

R

C

R

L

F

L

F


7-9

7

2 ) Station number

The station number is the number provided at the programmable controller in order todetermine which programmable controller the computer accesses. In the FX seriesprogrammable controller, the station number is set by the special data register D8121(specialD8121 hereinafter). The setting range is 00H to 0FH. In the case of FX0N series turn onM8120 when using the special D8121. For the setting method of an A series programmablecontroller, see the A series manual.

The following instructions can be used to set the station number of station 0 in the above system.

↑ 485ADP Station No.15

Computer

FXseries

FXseries

FXseries

FXseries

485PC-IF ↑ 485ADP Station No.0



M8002FNC 12

MOV H0 D8121

Notes1 )When setting station numbers, don't set the same number at more than 1 station.

Otherwise, transmission data may become confused and communication irregular.2 )Station numbers need not be set in numerical order, but are free to be set within the

specified range(00H to 0FH). For example, setting in a random order or skipping numbersis acceptable.

3 )PLC numberThe PLC number is the number identifying the programmable controller CPU on the Aseries MELSECNET(II) or MELSECNET/B.Accordingly, the PLC number for an FX series programmable controller is FFH, and isrepresented as two ASCII characters; i.e. ”FF”. When using the on-demand function thePLC number is automatically converted to FFH by the programmable controller. For the PLC number of programmable controller CPU on the MELSECNET(II),MELSECNET/B see the computer link manual for A series programmable controllers.

4 )CommandUsed to specify the operation required, e.g. read, write, etc. Commands are defined usingtwo ASCII characters. For a description of the available commands, see section 7.7.1.


7-10

5 ) Message waitThis is a delay time required by some computers to switch between send and receive states.The message wait time determines the minimum delay before the programmable controllersends data after receiving a message from the computer. Set the wait time according to thecomputer specifications.The message wait time may be set between 0 to 150 ms in 10 ms increments. The value isset using a single ASCII character (“0 to “F”) representing 0H to FH (0 to 15).When using the 485PC-IF in a 1:n system always set the message to be 70 ms or longer (7or more). If scan time of programmable controller is 70 ms or more on the network, messagewait time needs to be set at maximum scan time or more.

Example: Setting the message wait time

6 ) Sum check codeThe sum check code is used to verify that the data in a message has not been corrupted. It iscalculated by adding (summing) the hexadecimal values of the ASCII character codes in thesum check area of a message. The lower two digits (in hexadecimal) of the summed result(the sum check code) are then represented as two ASCII characters at the end of themessage. (Note: The sum of the decimal ASCII character codes, converted to hexadecimal,will give the same result). Special data register D8120 (communication format) b13, sets whether or not to add the sumcheck code to the message.

• When “b13=1”, the sum check code is automatically added to messages when transmitting, and a new sum check value is calculated from the Receive data and compared with the received sum check value, thereby checking the Receive message.

• When “b13=0”, the sum check code is not added, and the Receive data is not checked.An example showing how to calculate the sum check code is given below.

Example: When transmitting station number 0, PLC number FF, command BR (device memorybatch read), message wait time 30 ms, and data ABCD in format 1, the sum check code iscalculated as follows.

Computer


Transmission starts more than 100 ms later. Wait time must be longer than two-scan time.

"A"

Message wait (100 ms)

05H30H

ENQ

30ms(Message wait time)

30H+30H+46H+46H+42H+52H+33H+41H+42H+43H+44H=2BDH

···

Computer


StationNo.

0 0

PLCNo.

F F

SumcheckcodeB D

30H46H46H 42H 52H 33H 41H42H43H44H42H44H

Messagewait time

3

Character area

A B C D

02H30H

ENQ

StationNo.

0 0

PLCNo.

F F

30H46H46H

Command

B R


7-11

7

7.4.4 Time-out Check Time

The time out check time refers to the duration after termination of receive (final characterreceived) of a failed transmission from the computer to the programmable controller, until thesend sequence is initialized. This check time is specified as follows depending on the model and version of the programmablecontroller.

To set the time-out check time as 60 ms:

It must be noted that the time-out check time is not updated until the next character is received,and hence must be set to at least more than the time necessary to receive one character at thebaud rate (transmission speed) in use. When 1 character = 12 bits, the minimum setting of time-out check time is as follows.

PC series Setting range

FX0N, FX1S, FX1N 1 to 255 (10 to 2,550 ms) ; however, a setting of “0” gives 100 ms.

FX, FX2C, FX2N, FX2NC 1 to 3,276 (10 to 32,760 ms) ; however, setting of “0” gives 100 ms.

Baud rate (bps) Time to receive one character (ms) Time-out check time (set value)

300 40 50ms (5)

600 20 30ms (3)

1200 10 20ms (2)

2400 5 10ms (1)

4800 2.5 10ms (1)

9600 1.25 10ms (1)

19200 0.625 10ms (1)

M8002FNC 12

MOV K6 D8129

Other function information: • In the case of FX0N series, turn on M8120 when using the special D8129.


7-12

7.5 Communication Timing Chart

7.5.1 Reading Data from Programmable controller

7.5.2 Writing Data to Programmable Controller

E N Q

Computer

Interface


A C K

S T X

Wait(TW) T3 T4 T5

More than two-scandelay is needed.

Read process

This time becomes 0 when the message wait time is not set orwhen the wait time is less than the processing time needed bythe programmable controller.

T0 T1 T2

Programmablecontroller program

END Step 0 END Step 0 END Step 0 END

If the wait time has expired the response is sent at completion of theEND process, otherwise the wait time is checked again during the nextEND process.

Writing data

E N Q

Computer

Interface


Wait(TW) T3

Write process

This time becomes 0 when the message wait time is not set orwhen the wait time is less than the processing time needed bythe programmable controller.

T0 T1 T2

Programmablecontroller program

END Step 0 END Step 0 END Step 0 END

If the wait time has expired the response is sent at completion of theEND process, otherwise the wait time is checked again during the nextEND process.


7-13

7

7.5.3 Communication Time

This is to explain the method of calculating the approximate time until all communication is over.

For the locations of T0 to T4, see the previous page.

1 ) When reading data from the programmable controller to the computer Communication time = T0 + (T1 + T2 or TW, whichever is longer) + T3 + T4 + T5

2 ) When writing data from the computer to the programmable controller Communication time = T0 + (T1 + T2 or TW, whichever is longer) + T3

T0, T3, T5 =1/baud rate × number of bits in 1 character (1 + 7(8) + 0(1) + 1(2)) × number of characters

T1 =max. 1 scan time (during RUN, message processing is done at END processing, amaximum delay of 1 scan could occur depending on message timing; during STOP,T1 is 1 ms)

T2 =END process time of programmable controller during data communication

T4 =A delay of at least 2 scans is required. However, using one-pair wiring on the 1:Nsystem configuration, this time need to set “Time-out timer value (D8129) + 1 scantime” or more.

TW = set time when message wait is set.

Stop bit (1 or 2)

Data length (7 or 8) Parity bit (0 or 1)Start bit

T0, T3 =1/baud rate × number of bits in 1 character (1 + 7(8) + 0(1) + 1(2)) × number of characters

T1 =max. 1 scan time (during RUN, message processing is done at END processing, amaximum delay of 1 scan could occur depending on message timing; during STOP,T1 is 1 ms)

T2 =END process time of programmable controller during data communication

TW = set time when message wait is set.

Stop bit (1 or 2)

Data length (7 or 8) Parity bit (0 or 1)Start bit


7-14

7.6 Character Area Data TransmissionThe data shown in the following examples are samples of the data used in character area B whenreading or character area C when writing data. (see section 7.4.1 and 7.4.2)

7.6.1 Bit Device Memory

Bit device memory is handled in 1 bit units (1 point) or in word unit (16 points).

1 ) Bit units (units of 1 point)When handling bit device memory in bit units, the specified number of devices, in anincreasing order from the specified head device, are represented sequentially from the left,as “1”(31H) when ON, and as “0”(30H) when OFF.

Example: When transmitting the on/off status of five points from M10

2 ) Word units (units of 16 points)When handling bit device memory in word units, each word (16 bits, highest bit being first) isexpressed as 4 hexadecimal digits (each of 4 bits) starting with the higher digit. Each digitbeing represented by the appropriate ASCII character.

Example: When transmitting the on/off status of 32 points from M16

4DH 30H31H30H30H 35H30H

Head device

M 0 0 1 0

No.ofdevicepoints0 5

Data

1 0 1 0 1

31H 31H30H31H30H

Indicating M14 is ON


Indicating M13 is OFF


Indicating M11 is OFF

41H 32H31H42H 33H 44H43H34H

The number of devices is "02" because word units are used.

1 0 1 0000000000 1111111111111 0 0000 0

B15 B11B12B13B14 B9B10 B8 B5B6B7 B4 B1B2B3 B15 B11B12B13B14 B9B10 B8 B5B6B7 B4 B1B2B3B0 B0

M31

M17

M18

M19

M20

M21

M22

M23

M24

M25

M26

M27

M28

M29

M30

M35

M36

M38

M37

M39

M40

M41

M42

M43

M44

M45

M46

M47

M16

M33

M34

M32

A B DC4321

1:Represents ON0:Represents OFF

4DH 36H31H30H30H 32H30H

Head device

M 0 0 16


Data

A B 1 2

Data

3 4 C D

Lowest bitof 2nd word

Head device:Lowest bit of 1st word


7-15

7

7.6.2 Word Device Memory

When handling word device memory, each word is expressed as 4 hexadecimal digits (each of 4bits) starting with the higher digit. Each digit being represented by the appropriate ASCIIcharacter.

Example 1) When showing the contents of data registers D350, D351

Example 2) When showing the contents of C200* (32-bit counter)

* The device code of C200 is CN200.

10 1 00 00 000000 111 111 111111 0 000

5 6 F071BA

1 1 1

Contents of D350 is 56ABH(22187 in decimal).

Contents of D351 is 170FH(5903 in decimal).


35H 42H41H36H 31H 46H30H37H44H 30H35H33H30H 32H30H

Head device

D 0 3 5 0


Data

5 6 A B

Data

1 7 0 F

1 2 876543

The content of the C200 shows 12345678H (305419896 in decimal notation).

31H 34H33H32H 35H 38H37H36H44H 30H30H32H4EH 31H30H

Head device

C N 2 0 0


Data

1 2 3 4

Data

5 6 7 8


0 0 0 1 0 0 1 0 1 0 1 1 0 0 1 1 1 1 0 0 000010110001


7-16

7.7 Commands and Device Ranges

7.7.1 Commands

* Computer except high speed (32-bit) counters C200 to C255.

Command

Description

Maximum No. of units per communication

Symbol ASCIIcode

FX0N, FX1S

FX, FX2C, FX1N, FX2N,

FX2NC

Dev

ice

mem

ory

Batchread

Bitunit BR 42H, 52H Reads a group of bit devices (X, Y, M,

S, T, C), result is in units of 1 device. 54 points 256 points

Wordunit WR 57H, 52H

Reads a group of bit devices (X, Y, M,S), result is in units of 16 devices.

13 words,208 points

32 words,512 points

Reads a group of word devices (D, T,C), result is in units of 1 device. 13 points 64 points

Batchwrite

Bitunit BW 42H, 57H Writes a group of bit devices (X, Y, M,

S, T, C), data is in units of 1 device. 46 points 160 points

Wordunit WW 57H, 57H

Writes a group of bit devices (X, Y, M,S), data is in units of 16 devices.

10 words,160 points

10 words160 points

Writes a group of word devices (D, T,C), data is in units of 1 device. 11 points 64 points

Test(select write)

Bitunit BT 42H, 54H

Set/reset individual bit devices (X, Y,M, S, T, C) selectively in units of 1device.

10 points 20 points

Wordunit WT 57H, 54H

Set/reset bit devices (X, Y, M, S)selectively in units of 16 devices.

6 words,96 points

10 words,160 points

Write word devices (D, T, C*) selectively in units of 1 device. 6 points 10 points

PC

Remote run RR 52H, 52H Remote run/stop request to programmable controller. Remote stop RS 52H, 53H

PC type read PC 50H, 43H PC type name(code) is read.

Global GW 47H, 57HSet/reset the global flag (M8126 forFX series) to all connected programmable controllers.

1 point 1 point

On-demand Send request from programmablecontroller. Possible, however, only in1:1 system configuration.

Maximum13 words

Maximum64 words

Loopback test TT 54H, 54HCharacters received from the computer are directly sent back to thecomputer.

25characters

254characters


7-17

7

7.7.2 Device specification ranges

The following is the device and device number range that can be used in the access of devicememory.Each device is composed of five characters.Device (1 character, 2 characters with timer and counter) + device number (4 characters, 2characters with timer and counter) = 5 characters.

1 ) Bit devices

In FX series, the timer coil (TC) and counter coil (CC) are not supported.

2 ) Word devices

* Only CN000 to CN199 can be used.(C200 to C255 of 32 bit counter or high speed counter cannot be used.)

Device

Device specification charactersDecimal/octal

expression

Usable command

FX0N FX1S FX, FX2C FX1NFX2N, FX2NC

BR,BW,BT

WR,WW,WT

Inputs (X) X0000∼X0177

X0000∼X0017

X0000∼X0337

X0000∼X0177

X0000∼X0267

Octal

'

'

Outputs (Y) Y0000∼Y0177

Y0000∼Y0015

Y0000∼Y0337

Y0000∼Y0177

Y0000∼Y0267

Auxiliary relays (M) M0000∼M0511 M0000∼M1535 M0000∼M3071

Decimal

States (S) S0000∼S0127 S0000∼S0999

Special auxiliary relays (M) M8000∼M8254 M8000∼M8255

Timer contacts (T) TS000∼TS063 TS000∼TS255

×Counter contacts (C)

CS000∼CS031CS235∼CS254

CS000∼CS255

Device

Device specification charactersDecimal/

octalexpression

Usable command

FX0N FX1S FX, FX2CFX1N, FX2N,

FX2NC

BR,BW,BT

WR,WW WT

Timer current value (T) TN000∼TN063 TN000∼TN255

Decimal × '

'

Counter current value(C)CN000∼CN031CN235∼CN254

CN000∼CN255 '*

Data registers (D) D0000∼D0255 D0000∼D0999 D0000∼D7999

'File registers (D) D1000∼D2499 D1000∼D2999 RAM file registers (D) D6000∼D7999 Special data registers(D) D8000∼D8255 D8000∼D8255

Notes1 ) When using bit devices specified in word units (WR, WW, WT), the number of the

head device must be a multiple of 8 (or if an octal device end in 0) e.g. X30, M24.2 ) The special auxiliary relays (M8000 to M8255) and special data registers (D8000

to D8255) can be read only, write only, and received for system use.If an attempt is made to write outside the write enable range, an error may occur inthe programmable controller. Accordingly, for details of special auxiliary relays andspecial data registers, see the programmable controller manual.


7-18

7.8 Example Computer Program for Loopback TestThis is an example of a BASIC program for communication of the computer link using acomputer, programmable controller 485PC-IF, and 485ADP. (not used outside Japan.)Pleas see loopback test command see section 8.11.

1 ) Setting of transmission specification

2 ) Program example

Personalcomputer

485PC-IF

FX seriesprogrammablecontroller

485ADP

Item Description

Communicationmethod

Half-duplex communication method

Synchronizingmethod

Start-stop synchronization method

Baud rate 9600 bps

Data form

at

Start bit 1 bit

Data length 7 bit

Parity bit None

Stop bit 1 bit

Sum check Sum check is used

Station No. Station No.0

Exclusive protocolformat Format 1

According to the above transmission specification, the transmission specification andtransmission procedure of the programmable controller are set as follows.

D8120 = H6080D8121 = H0000D8129 = K0

For setting and details, see chapter 6, and section 7.4.

10 T0 = 3000 : ′ Reception wait counter (adjusted depending on computer speed)20 STCNT = 14 : ′ Normal data length30 NACNT = 7 : ′ Data length of error code (NAK statement)40 ERFLG = 050 ENQ$ = CHR$(5)60 STX$ = CHR$(2)70 ETX$ = CHR$(3)80 NAK$ = CHR$(&H15)90 *DATASEND : ′ Data transmission100 CLOSE #1110 OPEN″COM1″:″AS#1″120 SENDDATA$ = ″00FFTT204ABCD34″ : ′ Transmission data130 PRINT #1, ENQ$; SENDDATA$;140 *REC0: ′ Reception of first character150 RVCNT = 1160 GOSUB *RECWAIT170 IF ERFLG = 99 THEN GOTO ERRORFIN1180 BUF$ = RCV$

0 0 F F T T 2 A B C D 3 4

Station N

o.

PLC

No.

Com

mand

Data w

ait

Character

0 4

Num

ber of characters

Sum

check code

Transmission data


7-19

7

190 HED$ = LEFT$(BUF$.1)200 IF HED$ = STX$ OR HED$ = NAK$ THEN GOTO *REC1 ELSE GOTO *REC0210 *REC1 : ′ Reception of remaining data220 IF HED$ = STX$ THEN RVCNT = STCNT-1230 IF HED$ = NAK$ THEN RVCNT = NACNT-1240 GOSUB *RECWAIT250 IF ERFLG = 99 THEN GOTO *ERRORFIN1260 BUF$ = BUF$ + RCV$270 *PRINTRDATA : ′ Display of received data280 PRINT ″Received data″290 PRINT ″HEX ASCII″300 FOR I=1 TO LEN(BUF$)310 PRT1$ = MID$(BUF$,I,1)320 PRT1$ = HEX$(ASC(PRT1$))330 IF PRT2$ = ″2″ THEN PRINT ″ ″;″02″;″STX″ :GOTO 370340 IF PRT2$ = ″3″ THEN PRINT ″ ″;″03″;″ETX″ :GOTO 370350 IF PRT2$ = ″15″ THEN PRINT ″ ″;″15″;″NAK″ :GOTO 370360 PRINT ″ ″;PRT2$;″ ″CHR$(&H22);PRT1$;CHR$(&H22)370 NEXT I380 IF HED$ = NAK$ THEN GOTO *ERROROFIN2390 *DATACHECK : ′ Check of received data400 DDATA$ = STX$ + ″00FF04ABCD″ + ETX$ + ″5D″ : ′ Normal data410 FOR J=1 TO LEN(BUF$)420 RDATA$ = MID$(BUF$,J,1)430 ODATA$ = MID$(DDTA$,J,1)440 IF RDATA$ <> ODATA$ THEN GOTO *ERRORFIN3450 NEXT J460 PRINT ″Received data is normal″470 PRINT ″Loopback test complete ″:GOTO *FIN480 *ERRORFIN1490 PRINT ″Data is not received at all or data content is insufficient.″500 GOTO *FIN510 *ERRORFIN2520 ERRORCODE$ = MID$(BUF$,6,2)530 PRINT ″Error code″ ;ERRORCODE$; ″H is received.″540 GOTO *FIN550 *ERRORFIN3560 PRINT ″Received data is abnormal.(″;J;″-th character)″570 *FIN580 CLOSE #1590 END600 *RECWAIT : ′ Wait for receive610 FOR I=1 TO T0620 RCV$ = ″″630 IF LOC(1) => RVCNT THEN GOTO *BUFIN640 NEXT650 IF RCV$ = ″″ THEN ERFLG=99660 RETURN670 *BUFIN : ′ Reading of received data680 RCV$ = INPUT$(RVCNT,#1)690 RETURN


7-20

3 ) Operationa ) Start the computer program.b ) Send four characters “ABCD” from the computer to the FX programmable controller.c ) The FX programmable controller returns the four characters “ABCD” back to the

computer.d ) The computer compares the data received from the programmable controller and the

original sent data, and displays a result message.4 ) List of result messages

Message Remedy

Received data is normal. Data sending and receiving is normal.

Data is not received at all or data content isinsufficient.

Check again the writing, station No., transmissionspecification, and transmission protocol.

Error code 00H is received. Refer to error code list in chapter 12.

Received character is abnormal.(0-th character) Check for faulty writing, observing writing cautions.

FX communication Commands 8

8-1

8

8. CommandsThis chapter describes the structure and gives examples for each command of the dedicatedprotocol.See also Chapter 7 “Communication using Dedicated Protocols”.

The reference pages for command are given below.

Command Description Section

BR Bit devices read in units of 1 point. 8.1

WR Bit devices read in units of 16 points, or word devices read in units of 1 point. 8.2

BW Bit devices written in units of 1 point. 8.3

WW Bit devices written in units of 16 points, or word devices written in units of 1 point. 8.4

BT Bit devices specified in units of 1 point, and set/reset (forced on/off). 8.5

WT Bit devices specified in units of 16 points, and set/reset (forced on/off), or worddevices specified in units of 1 point, and data written. 8.6

RR Programmable controller is started (RUN) by remote control. 8.7

RS Programmable controller is stopped (STOP) by remote control. 8.7

PC Programmable controller type name code is read. 8.8

GW Global signal is turned on/off on all linked programmable controllers. 8.9

On-demand function (Send request is issued from the Programmable controller.There is no command). 8.10

TT Characters received from the computer are directly returned to the computer. 8.11


8-2

8.1 Batch Read of Bit Device (BR command)1 ) Command specification

Protocol format 1 is shown.

2 ) Command exampleTo read five points of data from X040 to X044 at station No.5 (with message wait time set to100 ms).(Assuming that X040 and X043 are OFF and X41, X42 and X44 are ON)

ComputerProgrammablecontroller

E N

Q

Station

No.

PLC

No.

B R

Message

wait tim

e

Sum

checkcode

Station

No.

S T

X

PLC

No.

Data ofthe

specifieddevices

E T

X

Sum

checkcode

Station

No.

A C

K

PLC

No.

Character area B

Batch read command (bits)

Head device

(5 characters)

Number ofdevices

(2 characters,hexadecimal)

Specifies the range ofdevices to be read.

"0" (30H) indicates OFF."1" (31H) indicates ON.

Character area A

Notes• Specify the range and number of devices so as to satisfy the following conditions.

- 1 ≤ number of devices ≤ 256(54 for FX0N)(256 points are specified by 00H)

- Head device No. + number of devices -1 ≤ max. device No.• The station number, PC (PLC) number, number of devices, and sum check code are

expressed in hexadecimal.

Computer


ENQ

The sum check is calculatedover this range


35H30H

0 5

46H46H

F F

52H42H

B R

41H

A

58H 30H34H30H30H 35H30H

X 0 0 4 0 0 5

37H34H

4 7

05H

STX

35H30H

0 5

46H46H

F F

02H

0 1 1 0 1

30H 31H30H31H31H

ETX

35H30H

0 5

03H

ACK

35H30H

0 5

46H46H

F F

06H

Indicating X044 is ON

Indicating X042 is ONIndicating X043 is OFF

Indicating X040 is OFFIndicating X041 is ON

Notes• Message wait time can be specified from 0 to 150 ms in 10 ms increments, expressed

by 0H to FH (in hexadecimal). Therefore, 100 ms is expressed as “A”.


8-3

8

8.2 Batch Read of Word Device (WR command)1 ) Command specification


2 ) Command examplesa ) Example 1

To read 32 points of data from X040 to X077 at station No.5 (with message wait time set to100 ms).


E N

Q

Station

No.

PLC

No.

W R

Message

wait tim

e

Sum

checkcode

Station

No.

S T

X

PLC

No.

Data ofthe

specifieddevices

E T

X

Sum

checkcode

Station

No.

A C

K

PLC

No.

Character area B

Batch read command (words)

Head device

(5 characters)

Number ofdevices


Specifies the range ofdevices to be read.

One word device requiresfour hexadecimal digits.Therefore,one word isexpressed using fourcharacters.

Character area A

Notes• Specify the range and number of devices (16 bit words) so as to satisfy the following

conditions.- 1 ≤ number of devices ≤ 64 (32 words in the case of bit devices) (13 words for FX0N)

- Head device No. + number of devices (number of devices × 16 in the case of bit devices) -1 ≤ max. device No.

- When reading 32-bit devices (C200 to C255), the returned data is a double word. Hence, the maximum number of devices is 32.

• The station number, PC (PLC) number, number of devices, and sum check code areexpressed in hexadecimal.

Computer


ENQ



35H30H

0 5

46H46H

F F

52H57H

W R

30H

0

58H 30H34H30H30H 32H30H

X 0 0 4 0 0 2

38H34H

4 8

05H

STX

35H30H

0 5

46H46H

F F

02H

ETX

38H30H

0 8

03H

ACK

35H30H

0 5

46H46H

F F

06H

31H 34H33H32H 41H 44H43H42H

0 0 0 0101010001 1111100101010 0 0111 0

X060

1 2 DCBA43

1 2 3 4 A B C D

X061

X062

X063

X067

X070

X071

X072

X077

X040

X041

X042

X043

X047

X050

X051

X052

X057

Notes• Command WR uses word units. When reading 32 points, the number of devices is

specified by “02” (16 points (bits) per one word unit).


8-4

b ) Example 2To read the present value of two points, T123 and T124, at station No.5.


ENQ


The sum check is calculated overthis range

35H30H

0 5

46H46H

F F

52H57H

W R

30H

0

54H 33H32H31H4EH 32H30H

T N 1 2 3 0 2

34H36H

6 4

05H

STX

35H30H

0 5

46H46H

F F

02H

ETX

33H42H

B 3

03H

ACK

35H30H

0 5

46H46H

F F

06H

37H 39H43H42H 31H 34H33H32H

7 B C 9 1 2 3 4

Present value of T123: 7BC9H(hexadecimal): indicates 31689 in decimal.Present value of T124: 1234H(hexadecimal): indicates 4660 in decimal.


8-5

8

8.3 Batch Write of Bit Device (BW command)1 ) Command specification

Protocol format 1 is shown

2 ) Command exampleTo write data into five points from M903 to M907 at station No.0 (with message wait time setto 0 ms).

E N

Q

Station

No.

PLC

No.

B W

Message

wait tim

e

Sum

checkcode

Station

No.

A C

K

PLC

No.

Data ofthe

specifieddevices

Head device

(5 characters)

Number ofdevices


Batch write command (bits) Character area A

Computer

Programmablecontroller Specifies the range of devices to be written.

"0" (30H) indicates OFF."1" (31H) indicates ON.

Notes• Specify the range and number of devices so as to satisfy the following conditions.

- 1 ≤ number of devices ≤ 160

- Head device No. + number of devices -1 ≤ max. device No.• The station number, PC (PLC) number, number of devices, and sum check code are


Computer

Programmablecontoroller

ENQ

The sum check is calculated over this range

30H30H

0 0

46H46H

F F

57H42H

B W

30H

0

4DH 33H30H39H30H 35H30H

M 0 9 0 3 0 5

36H32H

2 6

05H

ACK

30H30H

0 0

46H46H

F F

06H

0 1 1 0 1

30H 31H30H31H31H

Specifies to turn OFF M903

Specifies to turn ON M905Specifies to turn ON M904

Specifies to turn ON M907Specifies to turn OFF M906


8-6

8.4 Batch Write of Word Device (WW command)1 ) Command specification


2 ) Specification examplesa ) Example 1

To write to 32 points from M640 to M671 at station No.0 (with message wait time set to 0 ms).


E N

Q

Station

No.

PLC

No.

B R

Message

wait tim

e

Sum

checkcode

Station

No.

A C

K

PLC

No.

Data ofthe

specifieddevices

Batch write Command (words)

Head device

(5 characters)

Number ofdevices


Specifies the range of devices to be read.

Character area C

One word device requires four hexadecimal digits.Therefore,one word is expressed using fourcharacters.


conditions.- 1 ≤ number of devices ≤ 64 (10 words in the case of bit devices)

- Head device No. + number of devices (number of devices × 16 in the case of bit device) -1 ≤ max. device No.



ENQ


30H30H

0 0

46H46H

F F

57H57H

W W

30H

0

4DH 30H34H36H30H 32H30H

M 0 6 4 0 0 2

05H

ACK

30H30H

0 5

46H46H

F F

06H

0 0 1 0111001000 0100100110110 0 1111 1

M656

1 2 69BA73

M657

M658

M659

M669

M670

M671

M640

M641

M642

M643

M653

M654

M655

32H 37H34H33H 41H 36H39H42H

2 3 4 7 A B 9 6

35H30H

0 5

Notes• Command WW uses word units. When writing 32 points, the number of devices is

specified by “02” (16 points (bits) per one word unit).


8-7

8

b ) Example 2To write to data to two points, D0 and D1, at station No.0 (with message wait time set to 0 ms).


ENQ


30H30H

0 0

46H46H

F F

57H57H

W W

30H

0

44H 30H30H30H30H 32H30H

D 0 0 0 0 0 2

05H

ACK

30H30H

0 5

46H46H

F F

06H

31H 34H33H32H 41H 37H44H43H

1 2 3 4 A C D 7

39H46H

F 9

1234H(hexadecimal) to D0: indicates to write 4660 in decimal.ACD7H(hexadecimal) to D1: indicates to write -21289 in decimal.


8-8

8.5 Test of Bit Device (BT command)1 ) Command specification


2 ) Specification exampleTo set ON M50, OFF S100, and ON Y001 at station No.5 (with message wait time set to 0ms).


E N

Q

Station

No.

PLC

No.

B T

Message

wait tim

e

Sum

checkcode

Station

No.

A C

K

PLC

No.

Test command(selective write,bits)

Device

(5 characters)

Number ofdevices


1 character

Character area C

Set/reset

Device

(5 characters)

Set/reset

"0" (30H) indicates reset (OFF)"1" (31H) indicates set (ON)

Notes• Specify the range and number of devices so as to satisfy the following condition.

- 1 ≤ number of devices ≤ 20(10 for FX0N)• The station number, PC (PLC) number, number of devices, and sum check code are



ENQ

Set (ON)

35H30H

0 5

46H46H

F F

54H42H

B T

30H

0

33H30H

0 3

05H

ACK

35H30H

0 5

46H46H

F F

06H

4DH 35H30H30H 30H 31H

M 0 0 5 0 1

43H45H

E C

53H 30H31H30H 30H 30H

S 0 1 0 0 0

59H 30H30H30H 31H 31H

Y 0 0 0 1 1

Set (ON)Reset (OFF)



8-9

8

8.6 Test of Word Device (WT command)1 ) Command specification


2 ) Specification exampleTo changing the present value of D500 to 1234H, bits Y100 to Y117 to BCA9H, and thepresent value of C100 to 100 at station No.5 (with message wait time set to 0 ms).


E N

Q

Station

No.

PLC

No.

W T

Message

wait tim

e

Sum

checkcode

Station

No.

A C

K

PLC

No.

Test command(selective write,word)

Device

(5 characters)

Number ofdevices


Character area C

When specifying bitdevices,specify the Headdevice.

Device

(4 characters)

Device

(5 characters)

Device

(4 characters)

One word device requires four hexadecimaldigits.Therefore,one word is expressed using fourcharacters.


conditions.- 1 ≤ number of devices ≤ 10 (6 for FX0N)(one unit is 16 points for bit devices)


• C200 to C255 (CN200 to CN255) which are 32-bit devices cannot be handled in thiscommand.


ENQ

35H30H

0 5

46H46H

F F

54H57H

W T

30H

0

33H30H

0 3

05H

ACK

30H30H

0 5

46H46H

F F

06H

44H 30H35H30H 30H 31H

D 0 5 0 0

37H30H

0 7

32H 34H33H

1 2 3 4


59H 30H31H30H 30H 42H

Y 0 1 0 0

43H 39H41H

B C A 9

43H 30H31H4EH 30H 30H

C N 1 0 0

30H 34H36H

0 0 6 4

Indicates to change thecontents of D500 to1234H or 4660 indecimal.

1 0 1 10110111 00001

B C 9A

Y106

Y107

Y110

Y111

Y112

Y113

Y114

Y115

Y116

Y117

Indicates to change thepresent value of C100 to64H or 100 in decimal.Y

100

Y101

Y102

Y103

Y104

Y105

Each bit 0/1 indicates reset (OFF) or set (ON) respectivly.


8-10

8.7 Remote RUN/STOP (RR, RS commands)

8.7.1 Operation of Remote RUN/STOP

When remote RUN/STOP is requested from the computer, the programmable controller forcedrun mode, and the special auxiliary relays M8035, M8036, M8037 are controlled as follows.

• Remote RUNWhen remote RUN (RR command) is requested, M8035 and M8036 are set ON at theprogrammable controller, and forced RUN mode becomes active; the programmablecontroller switching to RUN.However, when remote run is executed while the programmable controller is running (forcedor otherwise), the state is not changed, and the remote error code (18H) is returned to thecomputer.

• Remote STOPWhen remote STOP (RS command) is requested, M8037 is set ON at the programmablecontroller. This in turn resets M8035, M8036 and M8037 to OFF and forced RUN mode isdisabled; the programmable controller switching to STOP.However, when remote STOP is executes while the programmable controller is not in forcedRUN mode, the state is not changed, and the remote error code (18H) is returned to thecomputer.

8.7.2 Conditions for Valid Execution of Remote RUN/STOP

The RUN terminal of the programmable controller is OFF, any built-in RUN/STOP switch is atSTOP.

• Remote RUNThe programmable controller should be stopped.

• Remote STOPThe programmable controller should be in forced run mode.

Remote stop

Forced run mode

Special auxiliary relayM8037 is ON

Special auxiliary relaysM8035, M8036, M8037are OFF

Programmablecontroller is stopped.

Remote error code (18H) is returned tocomputer, and the state of programmablecontroller is not changed.

NO

YES

Notes• Forced RUN mode is not restored after a power failure. When the programmable

controller is in forced RUN mode, if the power source is turned off and on, the specialauxiliary relays M8035, M8036, M8037 are all reset to OFF, and the programmablecontroller remains in STOP.


8-11

8

8.7.3 Control Specification and Examples of Remote RUN/STOP

1 ) Control specificationProtocol format 1 is shown.

2 ) Operation examplesa ) Example 1

To execute remote RUN at station No.5 (with a message wait time set to 0 ms).

b ) Example 2To execute remote STOP at station No.0 (with message wait time set to 0 ms).


E N

Q

Station

No.

PLC

No.

RRorRS

Message

wait tim

e

Sum

checkcode

Station

No.

A C

K

PLC

No.

Programmable controller remote run command: "RR"Programmable controller remote stop command: "RS"

Notes• The station number, PC (PLC) number, number of devices, and sum check code are



ENQ

35H30H

0 5

46H46H

F F

52H52H

R R

30H

0

35H43H

C 5

05H

ACK

35H30H

0 5

46H46H

F F

06H

The sum check iscalculated overthis range


ENQ

30H30H

0 0

46H46H

F F

53H52H

R S

30H

0

31H43H

C 1

05H

ACK

30H30H

0 0

46H46H

F F

06H



8-12

8.8 Reading The Programmable Controller Type (PC command)

8.8.1 Type Codes

Programmable controller type Type code (hex.) Programmable controller type Type code

(hex.)FX1S F2H A2USCPU 82H

FX0N 8EH A2CPU-A1, A2USCPU-S1 83HFX, FX2C 8DH A3CPU, A3NCPU A3H

FX1N 9EH A3ACPU 94HFX2N, FX2NC 9DH A3HCPU, A3MCPU A4HA0J2HCPU 98H A3UCPU 84H

A1CPU, A1NCPU A1H A4UCPU 85HA1SCPU, A1SJCPU 98H A52GCPU 9AHA2CPU(-S1), A2NCPU(-S1), A2SCPU A2H A73CPU A3H

A2ACPU 92H A7LMS-F A3HA2ACPU-S1 93H AJ72P25/R25 ABHA2CCPU 9AH AJ72LP25/BR15 8BH


8-13

8

8.8.2 Control Specification and Example


2 ) Specification exampleTo read the type name from station No.15 (with message wait time set to 0 ms)


E N

Q

Station

No.

PLC

No.

P C

Message

wait tim

e

Sum

checkcode

Station

No.

S T

X

PLC

No.

PC typename

(2 characters)

E T

X

Sum

checkcode

Station

No.

A C

K

PLC

No.Character area B

Programmable controller type nameread command



Computer


ENQ

The sum check iscalculated over thisrange

The sum check iscalculated over thisrange

46H30H

0 F

46H46H

F F

43H50H

P L C

30H

0

35H43H

C 5

05H

STX

46H30H

0 F

46H46H

F F

02H

ETX

31H38H

8 1

03H

ACK

46H30H

0 F

46H46H

F F

06H

Indicates station No. 15("0F" in hexadecimal).

Indicates the type name of the Programmable controller is FX, FX2C series.

44H38H

8 D


8-14

8.9 Global Function (GW command)This function is to turn on and off the global operation flag at all stations in the multidrop link.For an FX series programmable controller this is special auxiliary M8126, and for an A seriesprogrammable controller, it is Xn2 of the computer link unit.This function can be used for initialization, resetting or simultaneous star t/stop of allprogrammable controller stations.

8.9.1 Control Specification and Example of Global Function

The global function is to turn on or off the special auxiliary relay M8126 (global operation flag) atall stations in the multidrop link.

• The station number specified in the control protocol must indicate all stations, and is hencespecified as FFH (“FF”). If other than FFH is specified as the station number, the specialauxiliary relay M8126 of the specified station is turned on/off.

• No reply is given by the programmable controller to this command.• If the programmable controller power is turned off, the communication format changed, or the

programmable controller is stopped, the special auxiliary relay M8126 of that station is turnedoff, and the global function operation is cleared.


2 ) Specification exampleTo turn on the global operation flag at all programmable controller stations in the computer link;auxiliary relay M8126 in an FX series PLC station, and Xn2 in an A series programmablecontroller station.


E N

Q

Station

No.

PLC

No.

G W

Message

wait tim

e

Sum

checkcodeControl flag

(1 characters)

Character area AGlobal function command

When data value is "1" (31H), global operation flag is tumed on.When data value is "0" (30H), global operation flag is tumed off.



ComputerPrpgrammablecontroller

ENQ


46H46H

F F

46H46H

F F

57H47H

G W

30H

0

37H31H

1 7

05H

"FF" is specified to indicate all stations.For a specific station, specify the station number between "00" to "0F"("00" to "1F" for A series).

Indicates that the global operation flag is turned ON.

1

31H


8-15

8

8.10 On-demand FunctionData transmission between the computer and programmable controller is usually initiated by thecomputer only. The on-demand function is used if there is a need to transmit data from theprogrammable controller to the computer. The range of data registers containing the data to besent is specified in special data registers.

8.10.1 Special Devices Used in On-demand Function

The special data registers and auxiliary relays used in the on-demand function are explained inthe following table.

Device Name Description

M8127 On-demand handshake signal

On during execution of on-demand ON: on-demand data being transmitted OFF: on-demand data transmission complete

M8128 On-demand error flag

On if there is error in specified value for data transmission in on-demand ON: error OFF: no error

M8129 Flag for specifying word or byte data format

Word/byte data format for on-demand data. ON: byte units (8-bits per data register) OFF: word units (16-bits per data register)

D8127 On-demand head device number register

The head device number of the data area in which the data to betransmitted is stored. Set by programmable controller’s program.

D8128 On-demand data length register

The data length to be transmitted by on-demand. Set byprogrammable controller’s program.

Program


Computer

D8127D8128

D(n)

D(n+m-1)

Head addressData length

Notes• This function can only be used when the configuration of the computer and

programmable controller is 1:1.

Notes• The on-demand handshake signal is turned on when data transmission to the

computer is started from the programmable controller, and is turned off whentransmission of the specified data is complete. This is used as an interlock so that multiple on-demand requests can not be issuedsimultaneously.


8-16

8.10.2 On-demand Control Protocol

1 ) Control protocol programmable controller

2 ) Control protocol at computer

Transmission error check

On-demand data transmission

Set the word/byte data format

Set the on-demand data

Reset the on-demand error flag

Start on-demand

Transmission Complete

Set on/off special M8129.ON: byte units(8bits), OFF: word units(16bits)

Write the data to be transmitted into dataregisters.

Turn off on-demand error flag special M8128.(If special M8128 is ON, on-demand can notbe started.)

On-demand is started by writing the headdevice number where the data is stored intospecial M8127, and writing the data lengthinto special D8128.When the request is received, special M8127is turned on, and when transmission iscompleted, M8127 is turned off.

If the on-demand error flag special M8128 isON, the data was not transmitted due to atransmission error.

Error No error

……

……

……

……

……

On-demand Receive

Check that the received data ison-demand data.

Data processing

Completion of Receive

On-demand data has a PLC number of “FE”automatically attached. This can be used toidentify on-demand data.

……


8-17

8

3 ) On-demand request time chart. • When the computer is transmitting data

a ) When on-demand is requested, the on-demand execution signal (special M8127) isimmediately turned on.

b ) Transmission of on-demand data is forced to wait until completion of reception ofcommand data (ENQ-) from the computer.

c ) Transmission of response data (STX-) to command data (ENQ-) is forced to wait untilcompletion of transmission of on-demand data.

• When the computer is receiving data

a ) When on-demand is requested, the on-demand execution signal (special M8127) isimmediately turned on.

b ) Transmission of on-demand data is forced to wait until completion of transmission ofresponse data (STX-) to the command data (ENQ-) from the computer.

c ) Transmission of response data (ACK-) from the computer to the transmission of responsedata (STX-) from the programmable controller should be done after completion ofreception of on-demand data.

Computer


ENQ

STX

ACK

On-demandexecutionflag M8127

Start on-demand,writing of the on-

demand data length

b) On-demand data

a)

c)



ENQ

STX

ACK

On-demandexecutionflag M8127

Start on-demand,writing of the on-demand data length

On-demand data

a)

c)

b)



8-18

8.10.3 Specification and Example of On-demand

1 ) Command specificationProtocol format 1 is shown.


Special auxiliaryrelay M8127

Write processing

ON


S T

X

Station

No.

PLC

No.

Sum

checkcode

Transmissiondata

Added byprogrammablecontroller

E T

X

OFF

On-demand data is set, the head address iswritten to D8127 and the data length iswritten to D8128.

Notes• Specify the data length so as to satisfy the following condition.

Data length ≤ 40H (64 points)(13 points for FX0N)• The PLC number, “FE” is added by the programmable controller.• The station number, PLC number, number of devices, and sum check code are


Important• Don't use the on-demand function unless the system configuration is 1:1.• If the on-demand function is used in a multidrop system in which the computer and the

programmable controller are connected in 1:n configuration, normal communicationdata in control protocol formats 1 to 4, and on-demand data become confused, andnormal data transmission is not possible.


8-19

8

2 ) Specification Example 1To transmit the data stored in data registers D100 and D101 from the programmablecontroller (when the station number is 0, and data is specified in word units)

Program example


M8127

Write processing


Set ON if a transmissionerror occurs

STX

30H30H

0 0

45H46H

F E

32H31H

1 2 3 4

33H 35H34H02H

ETX

32H39H

9 2

03H

The PLC number "FE" is automatically added by the programmable controller.

36H37H38H

5 6 7 8

The 4 hexadecimal digits ofeach word are transmittedin ASCII, starting with themost significant digit.

D8127D8128

1002

On-demandcommand ➀

➁

M8128M8129

ON/OFFOFF

D100D101

1234H5678H

X000M8129

M8000

M8002PLS M0

M0 M8127H1234 D100FNC 12

MOV

H5678 D101

RST M8128

RST Y000

RST Y001

K100 D8127FNC 12MOV

K2 D8128FNC 12MOV

SET Y000

SET Y001

END

Data transmission set to word units.

Start command signals a pulse.

Transmission data is set.

On-demand error flag is reset(cannot start if M8128 is ON)

On-demand is started by specifying transmission dataarea head address and data length.

Confirming on-demand error, normal/abnormal externaloutput is set.

M8127 M8128

M8128

0

33

7

3

40

· · · · · · · · ·

· · · · · · · · ·

· · · · · · ·

· · · · · · · · ·

· · · · · · ·

· · · · · · ·

M8128 OFF : Normally transmitted.

ON : Data is not transmitted due to error.

FNC 12MOV


8-20

3 ) Specification Example 2To transmit the data stored in data registers D100 and D101 from the programmablecontroller (when the station number is 0, and data is specified in byte units)

Program example


M8127

Write processing


Set ON if a transmissionerror occurs

STX

30H30H

0 0

45H46H

F E

32H31H

3 4 1 2

33H 37H34H02H

ETX

32H39H

9 2

03H

The PC number "FE" is automatically added by theprogrammable controller

38H 35H 36H

7 8 5 6

The 2 hexadecimal digits ofeach byte are transmitted inASCII, starting with the mostsignificant digit.The lower byteof each word is transmitted first.

D8127D8128

1004

On-demandcommand ➀

➁

M8128M8129

ON/OFFON

D100D101

1234H5678H

X000M8129

M8000

M8002PLS M0

M0 M8127H1234 D100FNC 12

MOV

H5678 D101FNC 12MOV

RST M8128

RST Y000

RST Y001

K100 D8127FNC 12MOV

K4 D8128FNC 12MOV

SET Y000

SET Y001

END

Data transmission set to byte units.

Start command signals a pulse.

Transmission data is set.

On-demand error flag is reset(cannot start if M8128 is ON)

Confirming on-demand error, normal/abnormal external output is set.

Confirming on-demand error, normal/abnormal external output is set.

M8127 M8128

M8128

0

33

7

3

40

· · · · · · · · ·

· · · · · · · · ·

· · · · · · ·

· · · · · · · · ·

· · · · · · ·

· · · · · · ·

M8128 OFF : Normally transmitted.

ON : Data is not transmitted due to error.


8-21

8

8.11 Loopback TestThe loopback test is the function for testing if communication between the computer andprogrammable controller is operating as normal or not.

1 ) Command SpecificationProtocol format 1 is shown.

2 ) Specification exampleTo test the Loopback with data “ABCDE” at station No.0 (with message wait time set to 0 ms)


E N

Q

Station

No.

PLC

No.

T T

Message

wait tim

e

Sum

checkcode

Station

No.

S T

X

PLC

No.

Data(same dataas character

A area)

E T

X

Sum

checkcode

Character area B

Loopback test command

Data(designated

No.characters)

2 characters (hexadecimal)

Character area A

2 characters (hexadecimal)

No.

Character

No.

Characters

Notes• Specify the number of characters so as to satisfy the following condition.

- 1 ≤ No.characters ≤ 254 (25 for FX0N)• The station number, PC (PLC) number, number of devices, and sum check code are



ENQ


30H30H

0 0

46H46H

F F

54H54H

T T

30H

0

41H 45H44H43H42H 38H37H

A B C D E 7 8

05H

STX

30H30H

0 0

46H46H

F F

02H

ETX

33H41H

A 3

03H

35H30H

0 5

41H 45H44H43H42H

A B C D E

35H30H

0 5

Same data is transmitted.

The sum check is calculated overthis range


8-22

MEMO

FX communication RS instruction 9

9-1

9

9. RS instructionThis section refers to the RS instruction. For target devices, refer to the application instructionmanual of each programmable controller.

9.1 Function and Operation

9.1.1 Send and Receive Program

An RS instruction sends and receives serial data via the RS-232C port (optional equipment).

• The data transmission format can be set using the special data register D8120.Even if the setting of D8120 is modified while an RS instruction is driven, such modification are not accepted.

• In a system in which a send operation is not performed, set the number of send points to “K0”.In a system in which a receive operation is not performed, set the number of receive points to “K0”.

Supporting RS Instruction and Programming Protocol

When using the RS instruction in conjunction with a FX2N-232-BD or FX0N-232ADP, FX2NC-232ADP, the user can switch between no protocol communication and the programming tool(Programming Protocol) under the following conditions:

Accordingly, when data is received from the counterpart equipment while an RS instructionremains OFF, “NAK” will be sent back to the counterpart equipment.

Programmable Controller and Version

Supporting Version

FX2N V2.01 or more

FX2NC All products (V2.01 or more)

X010 FNC 80R S

D200

Read addressand number ofpoints of senddata

D 0 D500 D 1

Read addressand number ofpoints of receivedata


9-2

Operating Conditions and Format Set Content

The programmable controller can change from using no protocol communication to programmingprotocol (and back) by manipulating the RS instruction and Register D8120 and shown below.

1 ) With the RS instruction ON, move the data options shown below into the Register D8120 touse no protocol communication.

2 ) To use programming protocol, turn the RS instruction OFF and move the data H0000 into thecommunication format Register D8120. When the programmable controller is taken out ofRUN mode (by FX-PCS/WIN-E Software or the front panel switch), complete editing andprogram downloads can be accomplished. On line changes can be performed with theprogrammable controller in Run Mode.

Example of changing the communication format (D8120) between H0086 and H0000. Theprogrammable controller is first set for no protocol communication using the RS instruction.

Table: Set communication format (D8120)

ItemContent

H0086 H0186 H0286 H0386

Data length 7 Bit

Parity bit Even number (EVEN)

Stop bit 1 Bit

Baud rate (bps) 9600 bps

Header Off On Off On

Terminator Off On

X0 FNC 12 MOV

FNC 80RS

X0

P

D0 K1 D1 K1

H0086 D8120

FNC 12 MOV P H0000 D8120


9-3

9

9.1.2 Operation of RS Instruction

An RS instruction specifies the head address and the number of points of the send data sentfrom a programmable controller as well as the head address for receive data save destinationand the maximum acceptable number of points of receive data.The data send/receive sequence using an RS instruction is described below.

X010 FNC 80R S D200

Address andnumber of pointsof send data

D 0 D500 D 1

Address andnumber of pointsof receive dataPulse of Send

request Writes contents of senddata

SET M8122

M8123Moves receive data

RST M8123

Receive completion

Set send request

Reset receivecompletion flag

For operafion refer to section 9-2, 9-3

Writes the contents of D0 (number ofpoints of send data) and D200~.

This request is automatically resetwhen send is completed. Never resetthis request by a program.

Transfers the receive data to thededicated save area.

The receive completion flag M8123should not be reset in a program ofcontinuous operation.

Note:Though an RS instruction can be used in a program as many times as you want,make sure that only one RS instruction is driven at any one time (Two or more RSinstructions cannot be turned on at one time.). For changeover, assure the OFFtime is equivalent to or longer than one cycle time.In the FX0N, FX1S, FX1N, FX and FX2C, assure the OFF time is equivalent to orlonger than two scan times between completion of send and the start of receive orbetween completion of receive and the start of send. In the FX2N and FX2NC whoseversion is earlier than V 2.00, assure the OFF time is equivalent to or longer than100 µs between completion of send and start of receive or between completion ofreceive and start of send. (Refer to Paragraph 9.2.1.)This OFF time is not required in the FX2N, FX2NC whose version is V 2.00 or higherbecause full duplex communication is enabled.

While an RS instruction is driven, modification to D8120 is not accepted. Turn OFFthe RS instruction, then modify the setting.


9-4

9.1.3 Related Flags and Data Registers

1 ) Send request <M8122>When M8122 is set by a pulse instruction in the receive wait status or the receive completionstatus, data from D200 to D0 is sent. When send is completed, M8122 is automatically reset.When the RS instruction drive input X010 is turned on, the programmable controller is set tothe receive wait status.

2 ) Receive completion <M8123>• When the receive completion flag M8123 is turned ON, transfer the receive data to another

save destination, then reset M8123.• When M8123 is reset, the programmable controller is set to the receive wait status again.

To reset M8123, use a sequence as described on the previous page.When the RS instruction drive input X010 is turned on, the programmable controller is set to the receive wait status.

• When an RS instruction is executed while D1 is “0”, M8123 (execution completion flag) is not actuated and the programmable controller is not set to the receive wait status. If the programmable controller is set from this status to the receive wait status, set D1 to a value equivalent to or greater than “1”, then turn off M8123 (from the ON status).

3 ) Carrier detection <M8124>When the CD (DCD) signal (channel receive carrier detection) is received (from the modem tothe programmable controller) when the line of the modem is established, M8124 is turned on.While M8124 is turned off, the dial No. can be sent. While M8124 is turned on, data can besent and received.

Note:In the FX, FX2C, FX0N, FX1S, FX1N and earlier versions than V 2.00 of the FX2NC and FX2N, pay attention to the following points.While the programmable controller is receiving data, send is only performed after receive is completed. During this time, the send wait flag M8121 is actuated.After the head data is received and before the receive completion flag M8123 is turned on, it is regarded that a receive is being performed. If the send request is given while the head data is received, data may be confused.


9-5

9

4 ) Time-out evaluation <M8129> (Valid in the FX2N, FX2NC programmable controller earlier thanV2.00)If receive is not restarted within the time specified by D8129 after the receive data isinterrupted on the midway, it is regarded as time-out, M8129 is turned on, and receive iscompleted (Refer to the figure below.). M8129 is not automatically turned OFF. Reset it using a sequence program.When this function is used, data can be received without using a terminator even inequipment in which the number of send data may be changed.

5 ) Time-out evaluation time <D8129> (Valid in V 2.00 or later of the FX2N, FX2NC programmablecontroller)Set the time used for time-out evaluation described above. The value set here multiplied by“10 ms” is regarded as the evaluation time.When D8129 is set to “0”, the evaluation time equates to “100 ms”.

Example: When the time-out evaluation time is set to “50 ms”

Receive data isinterrupted

Reset by program

Receive

D8129 ×10ms

Data

ONTime-out evaluationM8129

ONReceive completionM8123

M8002FNC 12

MOVK 5 D8129


9-6

9.2 Hardware Hand Shake Operation

9.2.1 FX, FX2C, FX0N, FX1S, FX1N and FX2N (earlier than V 2.00)

In the FX, FX2C, FX0N, FX1S, FX1N and FX2N (earlier than V 2.00), half duplex communication isperformed. Accordingly, when the send flag is turned ON while data is received, the send wait flag M8121 isturned on. When the receive completion flag is changed from OFF to ON, send is started.

1 ) Do not use hardware hand shake ……D8120 ⟨(b12, b11, b10) = (0, 0, 0)⟩

Note:

* In FX1S, FX1N, FX0N, FX and FX2C series, the period should be longes 2 scan times or more.

Reset it using a program.When it is not trurned off, the nextdata cannot be received.

Data 1

RS instructiondriving

Send waitflag M8121

Send dataSD (TXD)

OFF ON

Data 4

Data 2 Data 3

OFFONSend requestM8122

Receive dataRD (RXD)

ReceivecompletionM8123

OFF ON ON

ONOFF* This period should be 100 µs or more

The receive waitstatus is started


9-7

9

2 ) Use terminal mode of control lineThis mode is available for send only or receive only.

a ) Send only

b ) Receive only

Data 1


Send dataSD (TXD)

OFF ON

Data 2

Send requestM8122

ONOFF

Data 1

ER(DTR) OFF

OFF

ON

ONDR(DSR)

Reset using a program. When it is not trurned off, the next data cannotbe received.

Data 1

OFF ON

OFF ON

ON

Data 2

OFF ONRS instructiondriving


ER(DTR)

ONReceivecompletionM8123


9-8

3 ) Use normal mode 1 of control line

Note:

* When using FX1S, FX1N, FX0N, FX, or FX2C, this period should be longer than 2 scan times ormore.

Reset using a program.When it is not trurned off, the nextdata cannot be received.

Data 1


Send waitflag M8121

Send data SD(TXD)

OFF ON

Data 3

Data 2

OFF ONSend requestM8122



OFF ON

ONOFF

ON

ON

OFF

OFF

This period should be 100 µs or more

ER(DTR)

DR(DSR)


9-9

9

4 ) Use normal mode 2 of control line (FX, FX2C only)

*1 Please turn OFF ER (DTR) of DR (DSR) later.

*2 When the data is sent, please turn OFF DR (DSR). When it is turned ON, the next data cannotbe communicated.

*3 When sending data to the programmable controller, please check to turn OFF the ER (DTR)signal.

*4 Reset using a program. When it is turned ON, the next data cannot be received.

*5 This period should be longer than 2 scan times or more.

Data 1


Send waitflag M8121

Send dataSD (TXD)

OFF ON

Data 3

Data 2




OFF ON

ON

ONOFF

OFF

ER(DTR)

DR(DSR)

*4

*5*1

*2

*3

*1CheckOFF

ON

Check OFF


9-10

9.2.2 FX2N, FX2NC (V 2.00 or later)

In the FX2N V 2.00 or later, full duplex communication is performed. When performing half duplexcommunication, pay rigid attention so that the send flag is not turned on while data is received. Ifit is turned on, send is started. As the result, the counterpart equipment may not be able toreceive data or the send/receive data may be damaged.In full duplex communication, the send wait flag M8121 is not turned on.In version V 2.00 or later, the programming protocol (Section 12) is supported while an RSinstruction remains OFF.

1 ) Do not use hardware hand shake

2 ) Use terminal mode of control lineThis mode is available for send only or receive only.The control line and the transmission sequence are equivalent to those in the FX2N serieswhose version is earlier than V 2.00. Refer to paragraph 9.2.1.

Reset using a program.When it is not trurned off, the nextdata cannot be received.

Data 1


Send dataSD (TXD)

OFF ON

Data 5



Data 3

Data 2 Data 4

OFF ON ON

The receive waitstatus is started



9-11

9

3 ) Use normal mode 1 of control line

Reset using a program.When it is not trurned off, the next datacannot be received.

Data 1

OFF

OFF ON

ON

Data 4

OFF ONRS instructiondriving

Send dataSD (TXD)

ER(DTR)

ONReceivecompletionM8123

OFF ON

Data 2 Data 3Receive dataRD (RXD)

OFF ON

Send requestM8122

DR(DSR)


9-12

4 ) Use interlink mode of control line

*1 While the counterpart equipment is ready to receive, turn ON the DR (DSR) signal.While both the DR (DSR) signal and the send request are turned on, the FX2N sends the data.

*2 In the interlink mode, the programmable controller turns OFF the ER (DTR) signal before the30th character receive buffer limit, and requests the counterpart equipment to stop send.After this send request, up to 30 characters can be received. The 31st and later characterscannot be received. Stop send temporarily, then send the remaining data after the ER (DTR)signal is turned ON again.When send is stopped, receive is completed after the time-out evaluation time is expired.When send is not stopped, receive is completed after the final character of the send data isreceived or the 30th character is received. Therefore, receive points need to set 30th or more.

*3 Reset using a sequence program.If it is turned ON, the next data cannot be received.

In the interlink mode, make sure to set the number of receive points to 30 characters or more.

Reset it using a program.When it is not trurned off,the next data cannot bereceived.

Data 2


Send dataSD (TXD)

OFF ON

Data 4

OFFONSend requestM8122


Data 4

Data 1 Data 3Receive dataRD (RXD)

OFF ON*1 *1 *1

Data 3

*3

Time-outevaluation timeD8129×10ms

OFF ON ON ON

Reset using a program.When it is not trurned off, thenext data cannot be received.

OFFON

DR(DSR)

Time-outevaluationflag M8129

Up to 30 characfers can bereceived *2

ER(DTR)


9-13

9

9.3 Number of Communication Data

9.3.1 Deal with 16 bits Data

When M8161 is set to OFF (M8161 is shared by an ASCII instruction, a HEX instruction and aCCD instruction.)

1 ) Send data and remaining number of send data

2 ) Receive data and number of receive data

Upper 8 bits Lower 8 bits

16-bit data

16-bit data is divided into thelower 8 bits and the upper 8bits, then sent or received.

STX D200 lower D200 upper D201 lower D201 upper ETX

STX D500 lower D500 upper D501 lower D501 upper D502 lower D502 upper ETX

Head address specified by

Send byte countspecified by "m"

S ·Terminator


It does not exceed the upper limit numberof receive data points (byte count)specified by "n".Receive is completed when the terminator(ETX) or "n" points are received.

TerminatorD·

Header

Header

Send data(Programmdblecontroller →Externalequipment)

Receive data(Externalequipment →Programmdblecontroller)

X010

M8000

FNC 80RS

D200 K 4 D500 K 10

S· m D· n

M8161 16-bit mode

OFF during RUNOFF

D20

0 lo

wer

D20

0 up

per

D20

1 lo

wer

D20

1 up

per

01

23

4

STX

ETX

Remaining numberof send data D8122

Send data SD (TXD)

D50

0 lo

wer

D50

0 up

per

D50

1 lo

wer

D50

1 up

per

D50

2 lo

wer

D50

2 up

per

The number of receivedata is also reset whenthe receive completionflag M8123 is reset.

65

43

21

0

STX

ETX

Receive data RD (RXD)

Number of receive dataD8123


9-14

9.3.2 Deal with 8 bits Data

When M8161 is set to ON (M8161 is shared by an ASCII instruction, a HEX instruction and aCCD instruction.)

1 ) Send data and remaining number of send data

2 ) Receive data and number of receive data

Ignored Lower 8 bits

The upper 8 bits are ignored,and the lower 8 bits exclusiuelyare regarcled as valid.

16-bit data

STX D200 lower D201 lower D202 lower D203 lower ETX

STX D500 lower D501 lower D502 lower D503 lower D504 lower D505 lower ETX

Head address specified bySend byte countspecified by "m"

S ·Terminator


It does not exceed the upper limit numberof receive data points (byte count)specified by "m".Receive is completed when the terminator(ETX) or "n" points are received.

TerminatorD·

Header

Header

Send data(Programmdblecontroller →Externalequipment)

Receive data(Externalequipment →Programmdblecontroller)

X010FNC 80

RSD200 K 4 D500 K 10

S· m D· n

8-bit modeM8000

M8161

D20

0 lo

wer

D20

1 lo

wer

D20

2 lo

wer

D20

3 lo

wer

01

23

4

STX

ETX

Remaining numberof send data D8122

Send data SD (TXD)

D50

0 lo

wer

D50

1 lo

wer

D50

2 lo

wer

D50

3 lo

wer

D50

4 lo

wer

D50

5 lo

wer

The number ofreceive data is alsoreset when thereceive completionflag M8123 reset.

65

43

21

0

STX

ETX

Receive data RD (RXD)

Number of receive dataD8123


9-15

9

9.4 Example Program

9.4.1 Personal Computer

When a programmable controller is connected to a personal computer, and data send/receive isperformed by the programmable controller

1 ) System configuration

Use a communication cable suitable to the arrangement of connector pins of the personalcomputer used. (For the representative wiring, refer to chapter 2.)

2 ) Communication formatIf the communication format of the commercial communication software used cannot realizethe following setting, set the programmable controller in accordance with the commercialcommunication software.

(The communication format in this example is set as follows.)

3 ) Operation

Data length 8 bit

Parity Even

Stop bit 2 bit

Baud rate 9,600 bps

Header None

Terminator None

Control line Normal mode 1


R ece ive

S end

FX 2N-232-B D FX 2N

Power ON

Receiving datafrom personal

computer

Sending data topersonal computer

PLC and personal computer are turned ON.When PLC is in RUN status, PLC can receive data frompersonal computer.

When operating program of personal computer, data is sent toD0 in PLC. This data value is A$ (40) in program. At this time,data (D0, D1) moves to D10, D11 in the PLC.

After moving data, PLC sends data (D10, D11) to the personalcomputer. When receiving data from the PLC, the personalcomputer displays the data.

*

$#

(

+)

,


9-16

4 ) Example program of programmable controller

5 ) Example program of computerThis is an example of a BASIC program for communication of RS instruction communication(no protocol communication). This BASIC program is written by not know overseas.

*1 This counter is used for waiting time of receiving data from PLC. Please change settingvalue of counter for personal computer CPU speed.

M8002

M8000

M8123FNC 15BMOV

D0 D10 K2

M20

END

SET M8122

RST M8123

PLF M20

FNC 80RS

D10 K4 D0 K4

FNC 12MOV

H 048F D8120

FNC 40ZRST

D0 D11Sending data and receiving datareset. #

Setting communication format.$

0000 0100 1000 11110 4 8 F

b15 b0

RS instruction drive. (

The receiving data (D0, D1)moves to sending data area(D10, D11). )

Receive completion reset ,

Send request *

+

102030405060708090100110120

C LO SE #1 :A$=”40”O PEN ”C O M 1:” AS #1PR IN T #1,A$C LO SE #1 :FO R I=J T O 2000:N EX T *1O PEN ”C O M 1:” AS #1FO R I=1 T O 100 *1IF LO C (1)>=4 G O T O 100N EX TC LO SE #1 :PR IN T ”T IM E O U T ER R O R ”:EN DB$=IN PU T $(LO C (1),#1)PR IN T B$EN D

T ext o f ASC II s tored.C O M 1 port is opened.D ata is sen t to PLC .

Length of rece ived data is checked.

R eceived data is d isp layed.


9-17

9

9.4.2 Printer

Connecting FX2N-232-BD and printer, and printing out the data send from the programmablecontroller.


Use a communication cable suitable to the arrangement of connector pins of the printerused. (For the representative wiring, refer to chapter 2.)

2 ) Communication formatLet the communication format of the programmable controller be in accordance with that ofthe printer used. (The communication format in this example is set as follows.)

3 ) Example program

Data length 8 bit

Parity Even

Stop bit 2 bit

Baud rate 2,400 bps

Header None

Terminator None

Control line No use


Send

FX 2N -232-BD FX 2N

M8000

M8002

X000

X001

M8161

END

M0

D8120H006FFNC 12MOV

K11D10FNC 80RS D50 K0

PLS M0

D10H0074FNC 12MOV

D11H0065FNC 12MOV

D17H006EFNC 12MOV

D18H0065FNC 12MOV

D19H000DFNC 12MOV

D20H000AFNC 12MOV

SET M8122

Handled by 8-bit data

Setting communication format

Writing send data

Send request

RS instruction driving b15 b00000 0000 0110 1111

0 0 6 F


9-18

4 ) Operation

Turn on the power of theprogrammable controller and printer,check the printer is on line and switchthe programmable controller to RUN.

Turn on X000, and drive RSinstruction.

Every time X001 is turned on, thecontents of D200 to D210 are sentto the printer, and "test line" isprinted.

Power on

RS instructiondrive

Data send

X000,ON

X001,ON

In this example,CR (H000D) andLF (H000A) are written at theend of the message. The printermoves down one line for eachmeessage.CR: Carriage ReturnLF: Line Feed

·

Note:lt may be necessary to setthe DIP switches of your printer.Check your printer manual forhow to configure the serialcommunications.

FX communication FX2N-232IF 10

10-1

10

10. FX2N-232IF

10.1 IntroductionThe RS-232C interface block FX2N-232IF (hereinafter referred to as “232IF”) is connectable withto the FX2N, FX2NC programmable controller to realize full duplex serial data communication withanother RS-232C interface such as a personal computer, bar code reader, printer, etc.

10.1.1 Outline of Product

1 ) Applicable programmable controllerThe 232IF can be connected as a special block of the FX2N, FX2NC programmable controller.

2 ) Control instructionsSend/receive data is received and sent and diversified control commands are manipulatedusing the FROM/TO instruction.

3 ) Number of I/O points and connection methodThe 232IF occupies 8 I/O points that can be allocated as either inputs or outputs. Howeverthe capacity of the 5 V power supplied from the programmable controller is limited.The current consumption of the 5 V power of the 232IF is 40 mA. Make sure that the totalcurrent consumption of the 5 V power including other special blocks is equivalent to or lessthan that available.

4 ) Communication methodFull duplex star t-stop synchronization and no protocol procedure are used. Thecommunication format can be specified using buffer memories (BFMs).

5 ) Send/receive bufferThe send/receive buffer can accommodate 512 bytes/256 words.When the RS-232C interlink connection mode is used, data exceeding 512 bytes/256 wordscan also be received.

6 ) ASCII/HEX conversion functionThe function to convert and send a hexadecimal numeric (0 to F) saved in the send databuffer as well as the function to convert a received ASCII code into a hexadecimal numeric (0to F) and save it to the receive buffer are provided.


10-2

10.2 Allocation of Buffer Memories (BFM’s)The RS-232C interface block FX2N-232IF(232IF) transmits data with the programmable controllervia buffer memories BFMs (16-bit RAM memories) in the 232IF.FNC78 (FROM) and FNC79 (TO) instructions are used to read and write the buffer memories.

10.2.1 BFM List

Note : “W : For write” can be used for read also. Undefined BFM Nos. are not allowed to be usedin program.

*1 : Spare buffers used in the interlink connection mode.

BFMNo. Name Setting range Initial value

R:For readW:For write

#0 Communication format 0087H W

#1 Command 0 W

#2 Receive upper limit byte count

1 to 512 (when data length is 16bits)1 to 256 (when data length is 8bits)“0” is treated as “512” or “256”.

0 W

#3 Receive time-out time 1 to 32,767 (X10 ms)“0” eliminates time-out time. 0 W

#4#5

Send header, lower 2 bytesSend header, upper 2 bytes 4 bytes max., zero suppression 0 (no header)

0 W

#6#7

Send terminator, lower 2 bytesSend terminator, upper 2 bytes 4 bytes max., zero suppression

0 (no terminator)

0W

#8#9

Receive header, lower 2 bytesReceive header, upper 2 bytes 4 bytes max., zero suppression 0 (no header)

0 W

#10#11

Receive terminator, lower 2bytesReceive terminator, upper 2bytes

4 bytes max., zero suppression0 (no

terminator)0

W

#12 Receive suspension waitingtime (in interlink connection) 0 to 32,327 (X10 ms) 0 W

#13 Number of remaining senddata

0 to 512 (when data length is 16bits)0 to 256 (when data length is 8bits)

0 R

#14 Number of receive buffers 0 to 256 + 15 *1 0 R

#15 Send sum result 0 R

#16 Receive sum result 0 R


10-3

10

Note : “W : For write” can be used for read also. Undefined BFM Nos. are not allowed to be usedin the program.

*1 : Spare buffers used in the interlink connection mode.

BFMNo. Name Setting range Initial

valueR:For readW:For write

#20 Time from CS ON to send start 0 to 32,327 (X 10 ms) 0 W

#21Time from completion of actual send to RS OFF (completion flag ON)

0 to 32,327 (X 10 ms) 0 W

#28 Status 0 R

#29 Error code 0 R

#30 Model code K7030 R

#1000 Send byte count 0 to 512 (when data length is 16 bits)0 to 256 (when data length is 8 bits) 0 W

#1001to

#1256Send buffers 0 W

#2000 Receive byte count 0 to 512 + 30 *10 to 256 + 15 *1 0 R

#2000to

#2256Receive buffers 0 R

#2257to

#2271

Spare receive buffers for interlink connection mode 0 R


10-4

10.2.2 Communication Format <BFM#0>

The communication format is determined on the rising edge of the send/receive enablecommand (BFM #1 b0).Accordingly, the communication format setting should be preliminary transferred using the TOinstruction before BFM #1 b0 is turned ON. Also, the send header and terminator are determinedby the rising edge of the send command (BFM #1 b1). The receive header and the receiveterminator are determined on the rising edge of BFM #1 b0 or on the rising edge of the receivecompletion reset command (BFM #1 b2). Accordingly, when only the header and the terminatorare exclusively changed it is not necessary to turn BFM #1 b0 OFF. The change becomes validform the next send/receive operation.

Bit Description 0 1 Initial valueb0 Data length 7 bit 8 bit 1 : 8 bit

b1b2 Parity

b1(00) : None(01) : Odd(11) : Even

(11) : Even

b3 Stop bit 1 bit 2 bit 0 : 1 bit

b4b5b6b7

Baud rate (bps)

b4(0011) : 300(0100) : 600(0101) : 1200(0110) : 2400(0111) : 4800(1000) : 9600(1001) : 19200

(1000) : 9600 bps

b8b9 Control line

b8(00) : Unused(01) : Standard RS-232C(11) : RS-232C interlink connection mode

(00) : Unused

b10b11 Addition of CR and LF

b10(00) : Not added(01) : CR only(11) : CR and LF

(00) : Not added

b12b13

Availability of check sum and ASCII/HEX conversion

b12(00) : Not available(01) : ASCII/HEX conversion available(10) : Check sum available(11) : Check sum available, ASCII/HEX conversion

available

(00) : Not available

b14 Send/receive buffer data length 16 bit 8 bit 0 : 16 bit

b15 Unused 0 : Unused


10-5

10

Note : Setting example (hexadecimal, constant specification)

1 ) Communication format

2 ) b0 to b7 (data length, parity, stop bit and baud rate)b0 to b7 should be aligned with the communication specification of the connectedcounterpart equipment.

M8002

Initialpulse

FNC 79TO

K 0 K 0 H4063 K 1

BlockNo.

BFM Setvalue

Number oftransferpoints

b15

4

0 1 0 0 0 0 0 0 0 1 1 0 0 0 1 1

b12 b11 b8 b7 b4 b3 b0

0 6 3(4063 H )

BFM #0

Data length 8 bits

Parity Odd

Stop bit 1 bit

Baud rate 2400 bps

Control line No used

CR, LF No added

Sum check No added

ASCII/HEX conversion No used

Buffer data length 8 bits

Data

Data

Data CR

Data CR LF

Data Sum

Data Sum CR

Data Sum CR

Data CR

Data CR LF

LF

Terminator

Header

Header

Header

Terminator

Terminator

Terminator

Terminator

Terminator

Select the communication format usedto send/receive data via the 232IFamong the 9 types shown on the left.

• The header can be specified in the

portion of the communication format.

• In the communication format type #, hexadecimal data (binary) and ASCII code can be sent and received.In the communication format types $ to -, the send/receive data should be any ASCII code except the header, terminator and CR.Communication can be performed using the ASCII/HEX conversion function by specifying the BFM #0 b13 and the BFM #0 b12.

• The ASCII codes available for the initial terminator are 01H to 1FH.

• In the RS-232C interlink connection mode, the communication formats $ to * are available.


10-6

3 ) b9 and b8 (control line)For examples of connecting the equipment corresponding to each setting, refer to section2.2.2. For operation of control line, refer to section 10.3.

• When bits b9=0 and b8=0 communication is performed using only the SD and RD signals without using the control line.

• When standard RS-232C mode is specified (b9=0, b8=1), a cross cable is required to connect the equipment of terminal specifications and a straight through cable is required to connect the equipment of modem specifications.

• When RS-232C interlink connection mode is specified (b9=1, b8=1), the request to send (RS) signal functions as the signal to enable receive in the 232IF. When receiving data exceeds the receive upper limit byte count (BFM #2), the 232IF sets the request to send (RS) signal to OFF and requests the counterpart equipment to suspend the send operation.At this time, when the data saved in the receive buffers is read to data registers in the programmable controller using the sequence program, the remaining data can be received.Make sure to perform the RS-232C interlink connection when specifying this mode.

4 ) b11 and b10 (addition of CR and LF)Set these bits as follows.

• Not added. (b11=0, b10=0)• CR only is added. (b11=0, b10=1)• CR and LF are added. (b11=1, b10=1)For the CR/LF addition format, refer to the communication format list shown above.

5 ) b13 and b12 (Availability of check sum and ASCII/HEX conversion)Set these bits as follows.

• Neither the check sum nor the ASCII/HEX conversion is available. ..... (b13=0, b12=0)• The ASCII/HEX conversion only is available. ....................................... (b13=0, b12=1)• The check sum only is available. .......................................................... (b13=1, b12=0)• Both the check sum and ASCII/HEX conversion are available. ............ (b13=1, b12=1)For the check sum addition format, refer to the communication format list shown above.


10-7

10

Note : ASCII/HEX conversionWhen execution of the ASCII/HEX conversion is specified, the hexadecimal numeric data (0 toF) inside the send buffers (BFMs #1001 to #1256) is converted into the ASCII code, then sent.The received ASCII code is converted into hexadecimal numeric data (0 to F), then saved tothe receive buffers (BFMs #2001 to #2256).At this time, the send/receive byte count indicates the number of hexadecimal data.

a ) Send format when hexadecimal data is converted into ASCII codeExample : When the send data “10ABH”, the header “STX” and the terminator “ETX” are

sent

b ) Receive format when ASCII code is converted into hexadecimal dataExample : When the receive data “10ABH”, the header “STX” and the terminator “ETX”

are received

6 ) b14 (send/receive buffer data length)

The data is treated as follows in accordance with the buffer data length.

• In the case of 16 bits (b14=0)

• In the case of 8 bits (b14=1)

b15

0 0 0 1 0 0 0 0 1 0 1 0 1 0 1 1

Send data buffer BFM #1001b0

The send byte count is "4".

STX

A B 1 0

ETX

02 H 41 H 42 H 31 H 30 H 03 H1 0 A B Converted into ASCIIcode before send

BFM #0

b15

1

0 0 0 1 0 0 0 0 1 0 1 0 1 0 1 1

b0

0 A B

STX

A B 1 0

ETX

02 H 41 H 42 H 31 H 30 H 03 H

The receive byte count is "2".1 byte 1 byte

Receive data bufferBFM #2001

STX

BFM#1001lower

BFM#1001upper

BFM#1002lower

BFM#1002upper

ETX

Upper 8 bits Lower 8 bits

Send/receive buffer

16-bit data is divided intoupper 8 bits and lower 8 bits,then sent and received.

Example of send buffers

STX

BFM#1001lower

BFM#1002lower

BFM#1003lower

BFM#1004lower

ETX

Ignored Lower 8 bits

Send/receive bufferUpper 8 bits are ignored, andlower 8 bits only are sent andreceived as valid data.

Example of send buffers


10-8

10.2.3 Command ⟨BFM #1⟩

BFM #1 gives the command for send/receive and the status information reset command to the232IF.

1 ) b0 (send/receive enable)While b0 is turned on, the 232IF can send and receive data.The contents of the following setting items are determined on the rising edge of b0. Makesure to set the contents using the TO instruction before setting b0 to “ON”.

• BFM #0 (communication format)• BFMs #9 and #8 (receive header)• BFMs #11 and #10 (receive terminator)On the rising edge of b0, the error occurrence (BFM #28 b3) and the error code (BFM #29)are cleared.

2 ) b1 (send command)On the rising edge of b1, the contents of the send buffers (BFMs # 1001 to #1256) are sent tothe counterpart equipment up to the send byte count (BFM #1000).When send is completed, the send completion status (BFM #28 b0) is set. BFM #28 b0 isautomatically reset when the next send command (b1) is given.When b1 is given, the contents of the following setting items are determined.

• BFMs #5 and #4 (send header)• BFMs #7 and #6 (send terminator)

3 ) b2 (receive completion reset command)When b2 is set to “ON”, the following items are cleared.

• BFM #28 b1 (receive completion)• BFM #2000 (receive byte count)• BFMs #2001 to #2256 (receive buffers)When receive is completed, b2 should be set to “ON” to clear the receive completion status(BFM #28 b1). If BFM #28 b1 is not reset, the next data cannot be received.When b2 is set to “ON”, the contents of the following setting items are determined.

• BFMs #9 and #8 (receive header)• BFMs #11 and #10 (receive terminator)In the RS-232C interlink connection mode (BFM #0 b9=1, b8=1), b2 functions as the receivecontinuation command to receive data exceeding the receive upper limit byte count (BFM#2), and clears the following items.

• BFM #28 b4 (receive suspended)• BFM #2000 (receive byte count)• BFMs #2001 to #2256 (receive buffers)• BFMs #2257 to #2271 (spare receive buffers)When b2 is set to “ON”, the request to send (RS) signal is automatically set to “ON” also.

4 ) b3 (error reset)When b3 is set to “ON”, the error occurrence status (BFM #28 b3) and error code (BFM #29)are cleared.

Bit Description

b0 Send/receive enable (ER ON)

b1 Send command

b2 Receive completion reset command

b3 Error reset


10-9

10

10.2.4 Receive Upper Limit Byte Count ⟨BFM #2⟩

Setting range: 1 to 512 (when buffer data length is 16 bits)1 to 256 (when buffer data length is 8 bits)“0” is regarded as “512” or “256”. The initial value is “0”.

BFM #2 specifies the maximum byte count received by the 232IF.When data is received up to the receive upper limit byte count, the receive completion status(BFM #28 b1) is set.When the receive terminator (BFMs #11 and #10) or the receive time-out time (BFM #3) is setand the set condition is satisfied, it is regarded that receive is completed even if the data receivedis within the receive upper limit byte count.

10.2.5 Receive Time-out Time <BFM #3>

Setting range: 1 to 32,767 (x 10ms)“0” eliminates time-out time. The initial value is “0”.

BFM #3 specifies the receive data waiting time limit.When the next data is not received within the receive time-out time starting from the receive edgeof each data, the receive time-out flag (BFM #28 b2) is set to “ON”, it is regarded that receive iscompleted, and the receive completion status (BFM #28 b1) is set.

10.2.6 Send Header <BFM #5 (upper), BFM #4 (lower)>

Setting range: 4 bytes maximum, zero suppressionThe initial value is “0” (No used).

For the send data of the 232IF, 4 headers maximum can be specified. When the number ofheaders is less than 4, the upper “0”s are ignored (zero suppression) and not transferred.

• The transmission order is fourth header, third header, second header, first header when 4 headers are specified.

10.2.7 Send Terminator <BFM #7 (upper), BFM #6 (lower)>


For the send data of the 232IF, 4 terminators maximum can be specified. When the number ofterminators is less than 4, the upper “0”s are ignored (zero suppression) and not transferred.As the first terminator, specify an ASCII code from 01H to 1FH. (As the second to fourthterminators, any ASCII code can be specified.)The register structure and the transmission order are equivalent to those of the send headerdescribed above.

b15

0

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

b0

0 0 0

BFM #5(upper 2 bytes)

4th 3rd

b15

0

0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0

b0

0 0 2

BFM #4(lower 2 bytes)

2nd 1stExample:02H (STX)


10-10

10.2.8 Receive Header <BFM #9 (upper), BFM #8 (lower)>


For the receive data of the 232IF, 4 headers maximum can be specified. When the number ofheaders is less than 4, the upper “0”s are ignored (zero suppression).The register structure and the transmission order are equivalent to those of the send headerdescribed above.

10.2.9 Receive Terminator <BFM #11 (upper), BFM #10 (lower)>


For the receive data of the 232IF, 4 terminators maximum can be specified. When the number ofterminators is less than 4, the upper “0”s are ignored (zero suppression).As the first terminator, specify an ASCII code from 01H to 1FH. (As the second to fourthterminators, any ASCII code can be specified.)The register structure and the transmission order are equivalent to those of the send headerdescribed above.

10.2.10 Receive Suspension Waiting Time <BFM #12>

Setting range: 0 to 32,767 (x 10ms)The initial value is 0 ms.

In the RS-232C interlink connection mode (BFM #0, b9=1, b8=1), when receiving data exceedingthe receive upper limit byte count (BFM #2), the 232IF sets the request to send (RS) signal to“OFF” and requests the counterpart equipment to suspend the send operation.BFM #12 specifies the time after the request to send (RS) signal is turned off until the receivesuspended status (BFM #28 b4) is turned on. The value set to the BFM #12 should be equivalentto or more than the time after the 232IF sets the request to send (RS) signal to “OFF” until thesend operation of the counterpart equipment is completely suspended.If the time times out and the receive suspended status (BFM #28 b4) is set to “ON” before thesend operation of the counterpart equipment is not suspended, the remaining data cannot bereceived.

Receive bytecountBFM#2000

Receive suspendedBFM#28 b4

Request to send (RS)

Suspension waiting time (BFM#12)0 to 32,767 (×10ms)

Data receive issuspended.

Spare receive buffers(BFM#2257 to #2271)

Receive upper limitbyte count (BFM#2) Set to the time in which

the send operation of thecounterpart equipment iscompletely suspended.

542

513512

0


10-11

10

10.2.11 Number of Remaining Send Data <BFM #13>

Saved value: 0 to 512 (when buffer data length is 16 bits)0 to 256 (when buffer data length is 8 bits)

The send byte count (BFM #1000) reduced by the number of data actually sent is duringtransmission.

10.2.12 Number of Receive Buffers <BFM #14>

Saved value: 0 to 256+15 (for spare receive buffers)

The number of buffers which have actually received data is saved in turn with regard to thereceive buffers BFM #2001 to #2256 and the spare receive buffers BFM #2257 to #2271 forinterlink connection mode.

10.2.13 Send Sum Result <BFM #15>

Initial value: 0

The check sum value added to the send data is saved.The sum check target range and the calculation method are shown below.

Note; Sum check target range and calculation method

Example:

The total value including the terminator and excluding the header (1st byte of the header only) iscalculated. Then, the lower 1 byte is converted into the ASCII code, and sent or received. Thedata converted into the ASCII code is placed in the order of upper digit and lower digit.

10.2.14 Receive Sum Result <BFM #16>

Initial value: 0

The sum check value of the receive data is saved.When the check sum added to the receive data is different from the receive sum result, “receivesum check error” occurs.The sum check target range and the calculation method are equivalent to those for the send sumresult described above.

STX

0 A 1 2 5

30 H 41 H 31 H 32 H 35 H

Header

Target range

F

ETX

5 2

46 H 03 H

Terminator Check sum

30 H +41 H +31 H +32 H +35 H +46 H +03 H =152 H

35 H 32 H02 H


10-12

10.2.15 Time from CS ON to Send Start <BFM #20>

Set value: 0 to 32,767 (x 10ms)The initial value is 0 ms.

The time after the clear to send (CS) signal is turned on until the 232IF starts the send operationcan be set.When “control line not used” is specified, the time after the send command is given until the sendoperation is started is specified.Set BFM #20 when it is required by a modem, etc.

10.2.16 Time from Completion of Actual Send to RS OFF (completion flag ON) <BFM #21>

Set value: 0 to 32,767 (x 10ms)The initial value is 0 ms.

The time after the 232IF sends the data until the RS signal is turned off and the send completionflag (BFM #28 b0) is turned on can be specified.Set BFM #21 when it is required by a modem, etc.


10-13

10

10.2.17 Status <BFM #28>

The 232IF status and the send/receive result are saved as status information. This informationcan be read from the programmable controller using the FROM instruction.

1 ) b0 (send completion)When send of data up to the send byte count (BFM #1000) is completed, the sendcompletion status (b0) is set. The send completion status (b0) is automatically reset whenthe next send command (BFM #1 b1) set to “ON”.

2 ) b1 (receive completion)When receive of data up to the receive upper limit byte count (BFM #2) is completed, thereceive completion status (b1) is set. If the receive terminator (BFMs #11 and #10) or thereceive time-out time (BFM #3) is set, it is regarded that receive is completed when the setcondition is satisfied, then the receive completion status (b1) is set in the same way.This status is required to be reset using the sequence program. If it is not reset, the next datacannot be received. This status can be reset using the receive completion reset command(BFM #1 b2).

3 ) b2 (receive time-out)When the receive time-out time (BFM #3) is reached while data is received, the receive time-out status (b2) is set. At the same time, the receive completion status (b1) is also set.This status is automatically reset when the receive completion reset command (BFM #1 b2)is executed.

4 ) b3 (error occurrence)When an error occurs while data is sent or received, b3 is set to “ON” and the error is savedto the error code (BFM #29).

5 ) b4 (receive suspended)When data exceeding the receive upper limit byte count (BFM #2) is received in the RS-232Cinterlink connection mode (BFM #0 b9=1, b8=1), the 232IF sets the request to send (RS)signal to “OFF”, requests the counterpart equipment to suspend the send operation, thensets b4 after the receive suspension waiting time (BFM #12) has expired.To receive the excess data in the interlink connection, the rising edge of the b4 is required tobe monitored using the sequence program. The data as much as the receive byte count(BFM #2000) in the receive buffers (BFMs #2001 to #2271) or the data as much as thenumber of receive buffers (BFM #14) should be read to data registers in the programmablecontroller and the receive completion command executed (BFM #1 b2).

6 ) b6 (being sent)b6 is turned on after the send command (BFM #1 b1) is given until the send completionstatus (BFM #28 b0) is set.

Bit Descriptionb0 Send completionb1 Receive completionb2 Receive time-out

b3 Error occurrenceb4 Receive suspendedb5 Undefined

b6 Being sentb7 Being received

Bit Descriptionb8 RS (RTS)b9 ER (DTR)

b10 Undefined

b11 Undefinedb12 DR (DSR)b13 CD (DCD)

b14 DS (CTS)b15 CI (RI)


10-14

7 ) b7 (being received)b7 is turned on after the head data is received until the receive completion status (BFM #28b1) is set.

8 ) b8 (RS), b9 (ER), b12 (DR), b13 (CD), b14 (CS), b15 (CI)These bits indicate the ON/OFF status of the control signals.

10.2.18 Error Code <BFM #29>

For error code, refer to chapter 12.

10.2.19 Model Code <BFM #30>

The model code of the 232IF is “K7030”.The model code is a fixed code assigned to each special extension equipment handled by theFROM/TO instruction. The programmable controller can distinguish the equipment type byreading this code.

10.2.20 Send Byte Count <BFM #1000>

Setting range: 0 to 512 (when buffer data length is 16 bits)0 to 256 (when buffer data length is 8 bits)

The BFM #1000 specifies how many bytes out of 512 bytes/256 words in the 16-bit send buffers(BFMs #1001 to #1256) are to be sent.

10.2.21 Send Buffers <BFMs #1001 to #1256>

Each of them is a 16-bit buffer to save the send data, and accommodates 512 bytes/256 words.

Note; Send/receive buffer structure

A numeric in the send/receive buffer is treated as hexadecimal (HEX).

b15

3

0 0 1 1 0 0 1 0 0 1 0 0 0 0 0 1

Example:#1001 (16-bit buffer)

b0

2 4 1

32 H =[2] 41 H =[A]

Upper bits Lower bits

1byte 1byte

1word


10-15

10

10.2.22 Receive Byte Count <BFM #2000>

Saved value: 0 to 512+30*1(when buffer data length is 16 bits)0 to 256+15*1(when buffer data length is 8 bits)

The byte count received from the counterpart equipment is saved.This value is cleared by the receive completion reset command (BFM #1 b2).*1 Spare buffers in the interlink connection mode

10.2.23 Receive Buffers <BFM #2001 to #2256>

Each of them is a 16-bit buffer to save the data received from the counterpart equipment, andaccommodates 512 bytes/256 words. The buffer structure is equivalent to that of the sendbuffers.The receive contents are cleared by the receive completion reset command (BFM #1 b2).

10.2.24 Spare Receive Buffers for Interlink Connection Mode <BFM #2257 to #2271>

Each of them is a spare buffer for the interlink connection in the case where the data exceeding512 bytes is received, and also used to receive data after the request to send (RS) signal isturned off until the send operation of the counterpart equipment is suspended.The receive contents are cleared by the receive completion reset command (BFM #1 b2).


10-16

10.3 Hardware Hand Shake Operation

10.3.1 No Hardware Hand Shake

Setting BFM#0 (b9, b8)=(0, 0)

*1 Turn off using a program. When it is turned ON, the next data cannot be sent.

*2 Time set by BFM#20 (x10ms).

*3 Turn it off using a program. When it is turned ON, the next data cannot be sent.

*4 After receive is completed and the data is read, turn off the receive completion flag (BFM #28b1) using a receive completion reset command (BFM #1 b2).

Send/receiveenable(BFM#1 b0)

Sendcommand(BFM#1 b1)

Send dataSD(TXD)

Sendcompletion(BFM#28 b0)

Receive dataRD(RXD)

Receivecompletion(BFM#28 b1)

Receivecompletion resetcommand(BFM#1 b2)

Data 1 Data 4

BFM#20X10ms

BFM#20X10ms

*1OFF

OFF

OFF

OFF

OFF

The receive waitstafus is started.

Data 2

ON

ON

Data 3

ON

ON

ON*1

*2 *2

*3

*4 *4 *3


10-17

10

10.3.2 Standard RS-232C Mode

Setting BFM #0 (b9, b8) = (0, 1)

*1 Turn off using a program. When it is turned ON, the next data cannot be sent

*2 Time set by BFM #21 (x10ms)


*4 Turn off using a program. When it is turned ON, the next data cannot be received.

*5 After receive is completed and the data is read, turn off the receive completion flag (BFM #28b1) using a completion reset command (BFM #1 b2)

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

ON

ON

ON

ON

ON


Sendcommand(BFM#1 b1)


Receive dataRD(RXD)

Receivecompletion(BFM#28 b1)Receivecompletion resetcommand(BFM#1 b2)

DR(DSR)

RS(RTS)

CS(CTS)

Send dataSD(TXD)

The receive waitstafus is started.

ON

Data 1

Data 4Data 2

Data 3

*2

BFM#21(X10ms) *2

BFM#20(X10ms) *3

BFM#20(X 10ms) *3

BFM#21(X10ms) *2

*1 *1

BFM#21(X10ms)

BFM#21(X10ms) *2

*4

*4*5 *5


10-18

10.3.3 Interlink Mode

Setting BFM #0 (b9, b8) = (1, 1)

*1 Turn off using a program. When it is turned ON, the next data cannot be sent.

*2 Make sure that the CS (CTS) in the FX2N-232IF is turned on while the counterpart equipmentis ready for receive.



*5 The RS (RTS) is turned off when the upper limit of receive byte count specified by the BFM #2is exceeded.When the send/receive buffer data length is 16 bits (BFM #0 b14=0), interrupt send from thecounterpart equipment within 30 bytes. When the send/receive buffer data a length is 8bits(BFM #0 b14=1), interrupt send from the counterpart equipment within 15 bits.If send is not interrupted, all the send data cannot be received.


*7 Turn off using a program. When it is turned ON, the next data cannot be received.

*8 After receive is completed and the data is read, turn off the receive completion flag (BFM #28b1) using a receive completion reset command (BFM #1 b2).

*9 Read the data as much as the receive byte count (BFM #14) in the receive buffer (BFM #2001to BFM #2271) to the data registers in the programmable controller, then turn it ON.

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF


Send command(BFM#1 b1)


Receive dataRD(RXD)

Receivecompletion(BFM#28 b1)Receivecompletion resetcommand(BFM#1 b2)

DR(DSR)

RS(RTS)

CS(CTS)

Send dataSD(TXD)

Receivesuspended(BFM#28 b4)

ON

ON

ON

ON

*2*2

ON

ON

Data 2

Data 1 Data 3

Data 4

ON

Data 3

BFM#20(X10ms) *3

BFM#20(X10ms) *4

*1*1

BFM#12(X10ms) *6

*8

*7

*9 *7 *7

*8

BFM#20(X10ms) *3

*5


10-19

10

10.4 Example Program

10.4.1 Example of 16 Bits Data Communication

This system configuration describes an example in which 16-bit buffer length data is sent andreceived between the equipment of the terminal specifications. In this example, the ASCII codesaved in the data registers D201 to D205 in the programmable controller sent to the counterpartequipment, and the data received from the counterpart equipment is saved to the data registersD301 to D304 in the programmable controller.


2 ) Example setting buffer memories The items not described here are set to the default respectively.

a ) Communication format <BFM #0>

FX 2N programmable contraller FX 2N -232IF

Personal computer

Cross cable

b15

0

0 0 0 0 0 0 0 0 1 0 0 1 1 1 1 1

b0

0 9 F (009F H)

b8 b7

Bit Description Settingb0 Data length (1): 8 bits

b1b2 Parity (1, 1): Even

b3 Stop bit (1): 2 bitsb4b5b6b7

Baud rate (1001): 19200 bps

b8b9 Control line (0, 0): Not used

b10b11 Addition of CR and LF (0, 0): Not added

b12b13

Availability of check sum and ASCII/HEX conversion (0, 0): Not available

b14 Send/receive buffer data length (0): 16 bits

b15 Undefined

. Specification item for16-bit length


10-20

b ) Command <BFM #1>M0→b0:Send/receive enable (ER ON)M1→b1:Send command M2→b2:Receive completion reset command M3→b3:Error reset

c ) Receive upper limit byte count <BFM #2> 8bytes

d ) Header and terminator <BFMs #4 to #11>BFMs #4 and #8 (send/receive header): 02H (STX)BFMs #6 and #10 (send/receive terminator):03H (ETX)

e ) Status <BFM #28> b0→M10:Send completion b8→M18:RS(RTS)b1→M11:Receive completion b9→M19:ER(DTR)b2→M12:Receive time-out b10→M20:Undefinedb3→M13:Error occurrence b11→M21:Undefinedb4→M14:Receive suspended b12→M22:DR(DSR)b5→M15:Undefined b13→M23:CD(DCD)b6→M16:Being sent b14→M24:CS(CTS)b7→M17:Being received b15→M25:CI(RI)

f ) Send byte count <BFM #1000>9 bytes

g ) Send buffers <BFMs #1001∼>9-byte send data “123456789” is prepared in ASCII code in accordance with the send bytecount specified above.

h ) Receive buffers <BFMs #2001∼>8-byte receive data specified in accordance with the receive upper limit byte count (BFM#2) is read to the data registers D301 to D304 in the programmable controller.

10th byte is not sent.

2 (32 H ) 1 (31 H )

4 (34 H ) 3 (33 H )

6 (36 H ) 5 (35 H )

8 (38 H ) 7 (37 H )

* * 9 (39 H )

2nd byte

4th byte

6th byte

8th byte

10th byte

1st byte

3rd byte

5th byte

7th byte

9th byte

Upper byte Lower byte

(BFM#1001)

(BFM#1002)

(BFM#1003)

(BFM#1004)

(BFM#1005)


10-21

10

3 ) Example program

Transfer of send byte count and send data D200(K 9)→BFM#1000 D201(2 1)→BFM#1001 D202(4 3)→BFM#1002 D203(6 5)→BFM#1003 D204(8 7)→BFM#1004 D205(_ 9)→BFM#1005

M8000

FNC 78FROM

K 0 K 28 K4M10 K 1

RUNmonitor Read of status

(BFM#28 b15 to b0→M25 to M10)

X001

Error reset inputError resetM 3

M8000 FNC 79TO

K 0 K 1 K1M0 K 1Transfer of command(M3 to M0→BFM#1 b3 to b0)

M11 FNC 78FROM

K 0 K2001 D301 K 4Receive

Read of receive buffers BFM#2001→D301 BFM#2002→D302 BFM#2003→D303 BFM#2004→D304

Receive completion resetcommandM 2

Y 1

Y 0Status monitor (upon necessity)

M 0 Send/receive enable

M10

M13Send completion

Error occurrence

FNC 79TO

K 0 K1000 D200 K 6

M8002 FNC 79TO

K 0 K 0 H009F K 1Initialpulse

Transfer of communication format(009FH→BFM#0)

FNC 79TO

K 0 K 2 K 8 K 1 Transfer of receive upper limit byte count(K 8→BFM#2)

Block No. BFM No. Transfersource

Number oftransfer points

X000

Send command inputPLS M 1

M 1 FNC 12MOV

K 9 D 200

FNC 12MOV

H3231 D 201

Send command

Send byte count(K9→D200)

( 2 1 )

FNC 12MOV

H3433 D 202 ( 4 3 )

FNC 12MOV

H3635 D 203 ( 6 5 )

FNC 12MOV

H3837 D 204 ( 8 7 )

FNC 12MOV

H0039 D 205 ( _ 9 )

Send data (as many as 9 bytes)[ 1 2 3 4 5 6 7 8 9 ]

FNC 79TO

K 0 K 4H02

(STX)K 1 Send header

(02H→BFM#4)

FNC 79TO

K 0 K 6H03

(ETX)K 1

Send terminator(03H→BFM#6)

FNC 79TO

K 0 K 8H02

(STX)K 1 Receive header

(02H→BFM#8)

FNC 79TO

K 0 K 10H03

(ETX)K 1 Receive terminator

(03H→BFM#10)

Unused

M8003

Block No. BFM No. Transferdestination


Initial pulse NC contact

completion


10-22

4 ) Operation chart

(M10)BFM#1000Send byte count

Send

(M1)

BFM#1 b0Send/receive enable

BFM#1001 to #1256Send buffers

Send completion status is also resetby next send command. ST

X

BFM#28 b0Send completion

BFM#13Number of remainingsend data

9 8 7

0

BFM#1 b1Send command

(M0)

6 5 4 3 2 1

(M2)

BFM#2Receive upperlimit byte count

BFM#14Number of receivebuffers

BFM#28 b1Receive completion

BFM#1 b2Receive completion resetcommand

BFM#2001 to #2256Receive buffers

BFM#2000Receive byte count

(M11)

ETX

When not resetContents of receive buffers are also cleared.

87

0

654321

STX

STX

#100

1 lo

wer

#100

1 up

per

#100

2 lo

wer

#100

2 up

per

#100

3 lo

wer

#100

3 up

per

#100

4 lo

wer

#100

4 up

per

#100

5 lo

wer

ETX

STX

#200

1 lo

wer

#200

1 up

per

#200

2 lo

wer

#200

2 up

per

#200

3 lo

wer

#200

3 up

per

#200

4 lo

wer

#200

4 up

per

ETX

10

23

4

Receive


10-23

10

10.4.2 Example of 8 Bits Data Communication

This system configuration describes an example in which 8-bit buffer length data is sent andreceived between the equipment of the terminal specifications. In this example, the ASCII codesaved in data registers D201 to D209 in the programmable controller is sent to the counterpartequipment, and the data received from the counterpart equipment is saved in data registersD301 to D308 in the programmable controller.


2 ) Example setting buffer memoriesThis items not described here are set to the default respectively.

a ) Communication format <BFM #0>

FX2N programmable controller FX2N-232IF

Personal computer

Cross cable

b15

4

0 1 0 0 0 0 0 0 1 0 0 1 1 1 1 1

b0

0 9 F (409F H )

b8 b7

Bit Description Settingb0 Data length (1): 8 bitsb1b2 Parity (1,1): Even

b3 Stop bit (1): 2 bitsb4b5b6b7

Baud rate (1001): 19200 bps

b8b9 Control line (0, 0): Not used

b10b11 Addition of CR and LF (0, 0): Not added

b12b13

Availability of check sum and ASCII/HEX conversion (0, 0): Not available

b14 Send/receive buffer data length (0): 8 bits

b15 Undefined

. Specification item for8-bit length


10-24

b ) Command <BFM #1>M0→b0:Send/receive enable (ER ON)M1→b1:Send commandM2→b2:Receive completion reset commandM3→b3:Error reset

c ) Receive upper limit byte count <BFM #2>8 bytes

d ) Header and terminator <BFMs #4 to #11>BFMs #4 and #8 (send/receive header): 02H (STX)BFMs #6 and #10 (send/receive terminator): 03H (ETX)

e ) Status <BFM #28>b0→M10:Send completion b8→M18:RS(RTS)b1→M11:Receive completion b9→M19:ER(DTR)b2→M12:Receive time-out b10→M20:Undefinedb3→M13:Error occurrence b11→M21:Undefinedb4→M14:Receive suspended b12→M22:DR(DSR)b5→M15:Undefined b13→M23:CD(DCD)b6→M16:Being sent b14→M24:CS(CTS)b7→M17:Being received b15→M25:CI(RI)

f ) Send byte count <BFM #1000>9bytes

g ) Send buffers <BFMs #1001∼>9-byte send data “123456789” is prepared in the ASCII code in accordance with the sendbyte count specified above.

h ) Receive buffers8-byte receive data specified in accordance with the receive upper limit byte count (BFM#2) is read to the data registers D301 to D308 in the programmable controller.

(BFM#1001)

(BFM#1002)

(BFM#1003)

(BFM#1004)

(BFM#1005)

lgnored 1 (31 H )

lgnored 2 (32 H )

lgnored 3 (33 H )

lgnored 4 (34 H )

lgnored 5 (35 H )

1 byte

2 byte

3 byte

4 byte

5 byte

Upper byte Lower byte

(BFM#1006)

(BFM#1007)

(BFM#1008)

(BFM#1009)

lgnored 6 (36 H )

lgnored 7 (37 H )

lgnored 8 (38 H )

lgnored 9 (39 H )

6 byte

7 byte

8 byte

9 byte


10-25

10

3 ) Example program M8002 FNC 79

TOK 0 K 0 H409F K 1

Initialpulse

Transfer of communication format(409FH→BFM#0)

FNC 79TO

K 0 K 2 K 8 K 1 Transfer of receive upper limit byte count(K 8→BFM#2)

Send command inputPLS M 1

FNC 12MOV

K 9 D 200

FNC 12MOV

H31 D 201

Send command

Send byte count(K9→D200)

( 2 )( 3 )( 4 )( 5 )( 6 )( 7 )( 8 )( 9 )

Send data (as many as 9 bytes)[ 1 2 3 4 5 6 7 8 9 ]

FNC 79TO

K 0 K 4H02

(STX)K 1 Send header

(02H→BFM#4)

FNC 79TO

K 0 K 6H03

(ETX)K 1 Send terminator

(03H→BFM#6)

FNC 79TO

K 0 K 8H02

(STX)K 1 Receive header

(02H→BFM#8)

FNC 79TO

K 0 K 10H03

(ETX)K 1 Receive terminator

(03H→BFM#10)

Program as followsin the same way.MOV H32 D202MOV H33 D203MOV H34 D204MOV H35 D205MOV H36 D206MOV H37 D207MOV H38 D208MOV H39 D209

( 1 )

M8000

FNC 78FROM

K 0 K 28 K4M10 K 1

RUNmonitor Read of status

(BFM#28 b15 to b0→M25 to M10)

X001

Error reset inputError resetM 3

M8000 FNC 79TO

K 0 K 1 K1M0 K 1 Transfer of command(M3 to M0→BFM#1 b3 to b0)

M11 FNC 78FROM

K 0 K2001 D301 K 8Receivecomple-tion

Read of receive buffers BFM#2001→D301 BFM#2005→D305 BFM#2002→D302 BFM#2006→D306 BFM#2003→D303 BFM#2007→D307 BFM#2004→D304 BFM#2008→D308

Receive completion reset commandM 2

Y 1

Y 0

Status monitor (upon necessity)

M 0 Send/receive enable

M10

M13Send completion

Error occurrence

FNC 79TO

K 0 K1000 D200 K 10Transfer of send byte count and send data D200(K9)→BFM#1000 D205( 5 )→BFM#1005 D201( 1 )→BFM#1001 D206( 6 )→BFM#1006 D202( 2 )→BFM#1002 D207( 7 )→BFM#1007 D203( 3 )→BFM#1003 D208( 8 )→BFM#1008 D204( 4 )→BFM#1004 D209( 9 )→BFM#1009

X000

M 1

M8003

Block No. BFM No. Transfersource


Block No. BFM No. Transferdestination


Initial pulse NC contact


10-26

4 ) Operation chart

(M10)BFM#1000Send byte count

Send

(M1)

BFM#1 b0Send/receive enable

BFM#1001 to #1256Send buffers

Send completion status is also resetby next send command. ST

X

BFM#28 b0Send completion

BFM#13Number of remainingsend data

9 8 7

0

BFM#1 b1Send command

(M0)

6 5 4 3 2 1

(M2)

BFM#2Receive upperlimit byte count

BFM#14Number of receivebuffers

BFM#28 b1Receive completion

BFM#1 b2Receive completion resetcommand

BFM#2001 to #2256Receive buffers

BFM#2000Receive byte count

(M11)

ETX

When not resetContents of receive buffers are also cleared.

87

0

654321

STX

STX

#100

1 lo

wer

#100

2 lo

wer

#100

3 lo

wer

#100

4 lo

wer

#100

5 lo

wer

#100

6 lo

wer

#100

7 lo

wer

#100

8 lo

wer

#100

9 lo

wer

ETX

STX

#200

1 lo

wer

#200

2 lo

wer

#200

3 lo

wer

#200

4 lo

wer

#200

5 lo

wer

#200

6 lo

wer

#200

7 lo

wer

#200

8 lo

wer

ETX

Receive

87

0

654321

FX communication Optional programming port 11

11-1

11

11. Optional Programming PortThis section describes connection to peripheral equipment (programming tool, data access unitand electronic operation terminal) using the FX2N-232-BD, FX1N-232-BD, FX0N-232ADP, FX2NC-232ADP, FX1N-422-BD, or FX2N-422-BD as well as cautions on communication. For the operatingprocedure of each peripheral equipment and installation of each interface, refer to thecorresponding manual.

11.1 FX2N-422-BD, FX1N-422-BDWhen an FX2N-422-BD is installed on the FX2N Series, or when an FX1N-422-BD is installed onFX1N or FX1S Series, the following peripheral equipment (programming tool, data access unit andelectronic operation terminal) can be connected.However, the FX2N-422-BD consumes 5V DC, 60 mA from the FX2N programmable controller,and the FX1N-422-BD consumes 5V DC, 60 mA from the FX1S or FX1N programmable controller. Make sure that the current consumption of 5V DC for special extensions and peripheralequipment does not exceed the capacity of the 5V DC power of the FX2N, FX1N or FX1S.

*1: When using other products or cables please check the product manual for required 5V DCsupply.

Note;These products cannot be connected via FX-2PIF to port of FX1N-422-BD or FX2N-422-BD. If connecting, power supply circuit in PLC will go down.

Product Connecting cable Required 5V DC

FX-20P-EFX-20P-CAB0 or FX-20P-CAB + FX-20P-CADP

180mA

FX-10P-E 120mA

Personal computer(For programming tool)

F2-232CAB-1 + FX-232AW(C) + (FX-422CAB0 orFX-422CAB + FX-20P-CADP) *1 220mA

FX-10DM FX-20P-CAB0 or FX-20P-CAB + FX-20P-CADP 220mA

FX-10DU-E FX-20P-CAB0 or FX-20P-CAB + FX-20P-CADP 220mA

FX-20DU-E FX-20DU-CAB0 or FX-20DU-CAB + FX-20P-CADP 180mA

FX-25DU-E, FX-30DU-E,FX-40DU-ES, FX-40DU-TK-ES,FX-50DU-TK(S)-E

FX-50DU-CAB0 (-1M, -10M, -20M, -30M, L)or FX-40DU-CAB (-10M, -20M, -30M) + FX-20P-CADP

0mA

F940GOT-SWD (LWD)-E, F930GOT-SBD FX-50DU-CAB0 (-1M, -10M, -20M, -30M, L) 0mA

F940GOT-SBD (LBD)-HF9GT-HCAB2-150 + F9GT-HCAB-3M (-10M)or FX-50DU-CAB0 (-1M) + F9GT-HCNB + F9GT-HCAB-3M (-10M)

0mA

GOT-A900 (Connecting directCPU port type) F9GT-CAB0 (-150, -10M) 0mA


11-2

11.2 FX2N-232-BD FX1N-232-BD FX0N-232ADP and FX2NC-232ADPWhen an FX2N-232-BD an FX0N-232ADP or an FX2NC-232ADP is installed on the FX2N, FX2NC

Series, or when an FX1N-232-BD is installed on FX1N or FX1S Series, a personal computer inwhich the following software is supported can be connected to each port.However, the FX2N-232-BD consumes 5V DC, 20 mA from the FX2N programmable controller, theFX1N-232-BD consumes 5V DC, 20 mA from the FX1N, FX1S programmable controller and theFX0N-232ADP, FX2NC-232ADP consumes 5V DC, 200mA from connected programmablecontroller. Make sure that the current consumption of 5V DC for special extensions does not exceed thecapacity of the 5V DC power of the FX2N, FX2NC, FX1S or FX1N.

• Programming software FX-PCS/AT-EE• Programming software FX-PCS/WIN-E

11.2.1 Connection cables

1 ) FX2N-232-BD, FX1N-232-BD, FX2NC-232ADP

2 ) FX0N-232ADP

RS-232C connector ofpersonal computer

FX2N-232-BD, FX1N-232-BD,FX2NC-232ADP side Personal computer side

D-SUB 9 pin

F2-232CAB-1 Gender changer

FX-232CAB-1

RS-232C cross cable (D-SUB 9 pin to D-SUB 9 pin) see the reference bellow

D-SUB 25 pinRS-232C cross cable (D-SUB 25 pin to D-SUB 9 pin) see the reference bellow

F2-232CAB-1

RS-232C connector ofpersonal computer Cable

D-SUB 25 pin F2-232CAB

D-SUB 9 pin F2-232CAB-1


11-3

11

Note: Reference

11.3 Cautions on Use

11.3.1 Cautions on Setting

Never set communication to the FX1S, FX1N, FX2N and FX2NC series using a peripheralequipment or program. If it is set in such a way, communication with peripheral equipment isdisabled.

11.3.2 Cautions on use

1

2

3

5

6

7

25pin

20

4

8

6

5

3

2

9pin

F2-232CAB-1

1

2

3

5

6

7

6

5

3

2

25pin 25pin

1

7

20 20

F2-232CAB

1

3

4

567

86

52

25pin 9pin

87

4

23

1

SHELL SHELL

20

RS232C crross cable(D-SUB 25pin→D-SUB 9pin)

1

3

456

7

8

6

28

7

423

1

Frame

5

Frame

9pin 9pin

RS232C crross cable(D-SUB 9pin→D-SUB 9pin)

2

3

4

5

6

8

9pin 5

8

6

3

2

9pin

FX-232CAB-1

4

Connect a programming tool (FX-10P, FX-20P, A7HGP/PHP, etc.) to either a connector built in aprogrammable controller or connector in optional unit (FX2N: FX2N-422-BD, FX2N-232-BD,FX2N-CNV-BD + FX0N-232ADP, FX2N-CNV-BD + FX2NC-232ADP, FX2NC: FX0N-232ADP, FX2NC-232ADP, FX1N, FX1S: FX1N-422-BD, FX1N-232-BD, FX1N-CNV-BD + FX0N-232ADP, FX1N-CNV-BD + FX2NC-232ADP).If the programming tool is connected to the both connectors, the following phenomena mayoccur.

1 ) A program in the programmable controller may be different from a program in theprogramming tool. If the program is modified or the set value of a timer, counter, etc. ismodified in this status, a part of the program may be damaged and the programmablecontroller may malfunction.

2 ) If the sampling trace function provided in the programmable controller is used in the bothports, correct sampling trace results cannot be obtained.


11-4

Memo

12

FX communication Diagnostics 12

12-1

12. Diagnostics

12.1 Common Items1 ) Check the connection with the communication unit of the programmable controller and the

optional equipment. When the connection is unstable, communication cannot be corrected. For the installation and connection method, refer to the manual of the communication unit ofthe optional equipment.

2 ) Check whether the VRRD or VRSC instruction is the program. If it is used, delete it, turn off the power of the programmable controller, then turn it on again.

3 ) Each setting of communication format (D8120), parameter of programmable controller byFX-PCS/WIN-E, N:N network (D8173 to D8180) and parallel link (M8070,M8071) is suitablefor the usage or it checks. The communication is not correctly done if setting is not suitablefor the usage.When each setting is changed, please turn off the power supply of the programmablecontroller, and turn it on again.

4 ) When using FX0N-485ADP and FX-485ADP, the power supply must be supplied correctly.


12-2

12.2 N:N Network

12.2.1 Error Code

When occurring the communication error, auxiliary relays (FX2N, FX2NC, FX1N, FX1S: M8183 toM8191, FX0N: M504 to M511) for error flag is turned ON in the station. And the error code isstored into the data registers (FX2N, FX2NC, FX1N, FX1S: D8211 to D8218, FX0N: D211 to D218).This error code is following the table.

M : Master station L : Slave station*1 Another slave station *2 Self station

12.2.2 Diagnostics

1 ) Check the status of the RD LED and the SD LED provided on each 485BD.• If both of them are lighted and extinguished, nothing is wrong.• If the RD LED is lighted/extinguished but the SD LED is not lighted/extinguished (not lighted

at all), check the setting of the station No., the transmission rate (baud rate) and the total number of slave stations.

• If the RD LED is not lighted/extinguished, check the wiring.2 ) Make sure that the communication error (FX2N: M8183 to M8190, FX0N: M504 to M511) in

each slave station is not turned on and that the data communication flag (FX2N: M8191,FX0N: M503) is not turned off. When one of the communication error flag is turned on or if thedata communication flag is turned off, check the error code of data registers (FX2N: D8211 toD8218, FX0N: D211 to D218). Please see the following section 12.2.1.

Errorcode Meaning Error

stationCheckstation Description Checking points

01H Commstime-out error L M

After master station send request to save station, no answer passing comms time-out.

Check wiring, power of programmable controller, RUN/STOP state (RUN is OK)

02H Station No.error L M

Station No. is not agreement between the master station and the slave station.

Check wiring

03H Commscounter error L M

Communication counter is not agreement between the master station and the slave station.

Check wiring

04H Commsformat error L M, L Communication format is not right

from slave station.

Check wiring, power of programmable controller, RUN/STOP state (RUN is OK), station No. setting

11H Commstime-out error M L

After slave station send answer to master station, master station do not send request to next slave station.


14H Commsformat error M L Communication format is not right

from master station.

Check wiring, power of programmable controller, RUN/STOP state (RUN is OK), station No. setting

21H No slave error L L *1 The station No. is not in this network. Check station No. setting.

22H Station No.error L L *1

Station No. is not agreement between the master station and the slave station.

Check wiring

23H Commscounter error L L *1

Communication counter is not agreement between the master station and the slave station.

Check wiring

31HNot receivecommsparameter error

L L *2When slave station receive request from master station before communication parameter.


12


12-3

12.3 Parallel Link

12.3.1 Diagnostics

1 ) Check the status of the RD(RXD) LED and the SD(TXD) LED provided on eachcommunication unit.

• If the RD(RXD) and the SD(TXD) LED are lighted and extinguished, nothing is wrong.• If the RD(RXD) LED is lighted/extinguished but the SD(TXD) LED is not lighted/extinguished

(not lighted at all), check the setting of the master station and the slave stations.• If the RD(RXD) LED is not lighted/extinguished, check the wiring.

2 ) Make sure that the master station and the slave stations are set correctly. If the setting isincorrect, correct it.

3 ) Make sure that the devices for the master station and the slave stations are handledcorrectly. If they are handled incorrectly, correct the program so that they are handledcorrectly.


12-4

12.4 Computer Link

12.4.1 NAK Error Code

The error code is sent following a NAK response to indicate the type of error that occurred. It istransmitted as two ASCII characters representing the hexadecimal codes ranging from 00H toFFH.If two or more errors occur simultaneously, the error code with the lowest number is transmitted.

12.4.2 Programmable Controller Error Code

With the FX series programmable controllers, the following errors are not transmitted using aNAK, but instead are shown at the programmable controller by switching on special auxiliaryrelay M8063, and storing the error code in special data register D8063.

Because these errors are not transmitted it must be programmed at the computer so as torecognize an error by using a watchdog timer or other monitor timer.

Error code(hexadecimal) Error description

00H, 01H 02H Sum error

03H Protocol error (the communication protocol does not conform to the format selected with D8120)

04H, 05H

06H Character area error (the character area is incorrectly defined, or the specified command is not available)

07H Character error (the data to be written to a device consists of ASCII codes other than hexadecimal codes)

08H, 09H 0AH PLC number error (the PLC number is not set to “FF” or not available from this station)

0BH to 0FH 10H PLC number error (the PLC number is not set to “FF” or not available from this station)

11H to 17H 18H Remote error (remote run/stop is disabled)

Error code(in D8063) Error description

6301 Parity, overrun, framing error

6305 Command failure receiving a command other than GW (global) when the station number is “FF”

6306 Monitor timer over (message to be received is insufficient)

12


12-5

12.4.3 Diagnostics

1 ) Check the status of the RD(RXD) LED and the SD(TXD) LED provided on eachcommunication unit.

• If both of them are lighted and extinguished, nothing is wrong.• If the RD(RXD) LED is lighted/extinguished but the SD(TXD) LED is not lighted/

extinguished (not lighted at all), check the setting of the station No. and the transmission rate (baud rate).

• If the RD(RXD) LED is not lighted/extinguished, check the wiring and confirm the connection with the programmable controller.

2 ) Make sure that the communication procedure is performed correctly. If it is not performedcorrectly, correct the setting in the computer.

3 ) Check the NAK error code and programmable controller error code.Please see the following section 12.4.1 and section 12.4.2.


12-6

12.5 RS Instruction

12.5.1 Diagnostics

1 ) Check the status of the RD (RXD) LED and the SD (TXD) LED provided on the optionalequipment.

• If the RD (RXD) LED is not lighted while data is received or the SD (TXD) LED is not lighted while data is sent, check the installation and the wiring.

• When the RD (RXD) LED is lighted while data is received or the SD (TXD) LED is lighted while data is sent, the installation and the wiring are correct.

2 ) Cheek the timing of data send/receive. For example, make sure that the counterpartequipment is ready for receive before starting to send data to it.

3 ) When the terminator is not used, check whether the send data capacity is equivalent to theacceptable data capacity. If the send data capacity may be changed, use the terminator.

4 ) Make sure that the external equipment is operating correctly.5 ) Check whether the type of send data and the type of receive data are equivalent. If they are

different, make them equivalent.6 ) When two or more RS instructions are used in the program, make sure that only one RS

instruction is actuated in one operation cycle. Never turn off the RS instruction while data is received or sent.

7 ) In the FX2N Series (V 2.00 or later), an RS instruction is not executed if the counterpartequipment receives “NAK”. Arrange the system so that the RS instruction is executed even if the counterpart equipmentreceives “NAK”.

12


12-7

12.6 FX2N-232IF

12.6.1 Error code

When an error occurs while data is sent or received, BFM #28 b3 is set to ON and the error codeis saved in BFM #29.

12.6.2 Diagnostics

1 ) Check the status of the POWER LED provided in the FX2N-232IF.• When it is Lit, the power source is correctly supplied.• If it is extinguished, supply from the power source correctly.

2 ) Check the status of the SD LED and the RD LED provided in the FX2N-232IF.• If the RD LED is not Lit while data is received or the SD LED is not Lit while data is sent,

check the installation and the wiring.• When the RD LED is Lit while data is received or the SD LED is Lit while data is sent, the

installation and the wiring are correct.3 ) Make sure that the communication setting (BFM #0) of the FX2N-232IF is equivalent to that of

the external equipment. If they are not equivalent each other, make them equivalent.4 ) Make sure the timing of data send/receive. For example, make sure that the counterpart

equipment is ready for receive before starting to send data to it.5 ) When the terminator is not used, check whether the send data capacity is equivalent to the

acceptable data capacity. If the send data capacity may be changed, use the terminator.6 ) Make sure that the external equipment is correctly operating.7 ) Check whether the type of send data and the type of receive data are equivalent. If they are

different, make them equivalent.

Code Description Causes and countermeasures

0 No error

1 Receive parity error, overrun error, framing error

Communication format such as baud rate is not matched.Control timing is not matched.

2 Undefined 3 Defective receive character Receive data is not ASCII code.

4 Receive sum check error Receive sum is not equal calculated sum result (BFM #16).

5 Receive buffer overflow (only in interlink connection mode)

Receive byte count exceeds 512+30 bytes.Decrease receive upper byte count (BFM #2), and increase spare receive buffer area.

6 Baud rate setting error Non-existing baud rate is specified.

7 Receive CR error CR is not placed in correct position.

8 Receive LF error LF is not placed in correct position.

9 Send/receive initial terminator setting error Initial terminator is other than 01H to 1FH.

10 Receive terminator error Receive terminator is not placed in correct position or not matched.

11 Undefined 12 Transmission sequence error Transmission sequence is not matched.


12-8

12.7 Using Optional Programming Port

12.7.1 FX1S, FX1N and FX2N(C) earlier V2.00

1 ) Make sure that the communication format is set to the initial status (D8120 = K0). Using a peripheral equipment, check the communication setting by parameters. If a non-procedure protocol (RS instruction) or dedicated protocol is selected in the setting, clear thesetting using the peripheral equipment.

2 ) When an RS instruction is used in the program, delete the RS instruction, turn off the powerof the programmable controller, then turn it on again.

12.7.2 FX2N, FX2NC whose version is V 2.00 or later

If an RS instruction is used in the program, make sure that it is not executed. If it is executed, theRS instruction has the priority.

A-1

A

Appendix A:ASCII code Lists

Table B-2: ASCII code ListsHex code

0 1 2 3 4 5 6 7

0 DLE SP 0 @ P ` p

1 SOH DC1 ! 1 A Q a q

2 STX DC2 ” 2 B R b r

3 ETX DC3 # 3 C S c s

4 EOT DC4 $ 4 D T d t

5 ENQ NAK % 5 E U e u

6 ACK SYN & 6 F V f v

7 BEL ETB ’ 7 G W g w

8 BS CAN ( 8 H X h x

9 HT EM ) 9 I Y i y

A LF SUB ∗ : J Z j z

B VT ESC + ; K [ k

C FF FS , < L \ l |

D CR GS - = M ] m

E SO RS . > N ^ n ~

F SI US / ? O _ o DEL

FX communication Appendix A

FX communication Appendix A

A-2

MEMO

HEADQUARTERS

MITSUBISHI ELECTRIC EUROPEEUROPE B.V.German BranchGothaer Straße 8D-40880 RatingenPhone: +49 (0) 2102 / 486-0Fax: +49 (0) 2102 / 486-1120e mail: [email protected] ELECTRIC FRANCEEUROPE B.V.French Branch25, Boulevard des BouvetsF-92741 Nanterre CedexPhone: +33 1 55 68 55 68Fax: +33 1 55 68 56 85e mail: [email protected] ELECTRIC IRELANDEUROPE B.V.Irish BranchWestgate Business Park, BallymountIRL-Dublin 24Phone: +353 (0) 1 / 419 88 00Fax: +353 (0) 1 / 419 88 90e mail: [email protected] ELECTRIC ITALYEUROPE B.V.Italian BranchVia Paracelso 12I-20041 Agrate Brianza (MI)Phone: +39 039 6053 1Fax: +39 039 6053 312e mail: [email protected] ELECTRIC SPAINEUROPE B.V.Spanish BranchCarretera de Rubí 76-80E-08190 Sant Cugat del VallésPhone: +34 9 3 / 565 3131Fax: +34 9 3 / 589 2948e mail: [email protected] ELECTRIC UKEUROPE B.V.UK BranchTravellers LaneGB-Hatfield Herts. AL10 8 XBPhone: +44 (0) 1707 / 27 61 00Fax: +44 (0) 1707 / 27 86 95e mail: [email protected] ELECTRIC JAPANCORPORATIONOffice Tower “Z” 14 F8-12,1 chome, Harumi Chuo-KuTokyo 104-6212Phone: +81 3 6221 6060Fax: +81 3 6221 6075MITSUBISHI ELECTRIC USAAUTOMATION500 Corporate Woods ParkwayVernon Hills, IL 60061Phone: +1 847 / 478 21 00Fax: +1 847 / 478 22 83

MIDDLE EAST REPRESENTATIVE

Ilan & Gavish Ltd. ISRAELAutomation Service24 Shenkar St., Kiryat ArieIL-49001 Petah-TiqvaPhone: +972 (0) 3 / 922 18 24Fax: +972 (0) 3 / 924 07 61e mail: [email protected] Electronics Ltd. ISRAELBox 6272IL-42160 NetanyaPhone: +972 (0) 9 / 863 08 91Fax: +972 (0) 9 / 885 24 30e mail: [email protected]

EUROPEAN REPRESENTATIVES

GEVA AUSTRIAWiener Straße 89AT-2500 BadenPhone: +43 (0) 2252 / 85 55 20Fax: +43 (0) 2252 / 488 60e mail: [email protected] BELARUSOktjabrskaya 16/5, Ap 704BY-220030 MinskPhone: +375 (0)17 / 22 75 704Fax: +375 (0)17 / 22 76 669e mail: [email protected] b.v. BELGIUMControl SystemsPontbeeklaan 43B-1731 Asse-ZellikPhone: +32 (0) 2 / 467 17 51Fax: +32 (0) 2 / 467 17 45e mail: [email protected] CO. BULGARIA4, A. Ljapchev Blvd.BG-1756 SofiaPhone: +359 (0) 2 / 97 44 05 8Fax: +359 (0) 2 / 97 44 06 1e mail: —INEA CR d.o.o. CROATIALosinjska 4 aHR-10000 ZagrebPhone: +385 (0) 1 / 36 940-01Fax: +385 (0) 1 / 36 940-03e mail: [email protected] CZECH REPUBLICControl Systems s.r.o.Nemocnicni 12CZ-702 00 Ostrava 2Phone: +420 59 / 6152 111Fax: +420 59 / 6152 562e mail: [email protected] poulsen DENMARKindustri & automationGeminivej 32DK-2670 GrevePhone: +45 (0) 70 / 10 15 35Fax: +45 (0) 43 / 95 95 91e mail: [email protected] Elektrotehnika AS ESTONIAPärnu mnt.160iEE-11317 TallinnPhone: +372 (0) 6 / 51 72 80Fax: +372 (0) 6 / 51 72 88e mail: [email protected] Electronics OY FINLANDAnsatie 6aFIN-01740 VantaaPhone: +358 (0) 9 / 886 77 500Fax: +358 (0) 9 / 886 77 555e mail: [email protected] A.B.E.E. GREECE5, Mavrogenous Str.GR-18542 PiraeusPhone: +302 (0) 10 / 42 10 050Fax: +302 (0) 10 / 42 12 033e mail: [email protected] Automatika Kft. HUNGARY55, Harmat St.HU-1105 BudapestPhone: +36 (0)1 / 2605 602Fax: +36 (0)1 / 2605 602e mail: [email protected] POWEL LATVIALienes iela 28LV-1009 RigaPhone: +371 784 / 22 80Fax: +371 784 / 22 81e mail: [email protected]

EUROPEAN REPRESENTATIVES

UAB UTU POWEL LITHUANIASavanoriu pr. 187LT-2053 VilniusPhone: +370 (0) 52323-101Fax: +370 (0) 52322-980e mail: [email protected] SRL MOLDOVACuza-Voda 36/1-81MD-2061 ChisinauPhone: +373 (0)2 / 562 263Fax: +373 (0)2 / 562 263e mail: [email protected] b.v. NETHERLANDSControl SystemsDonauweg 2 BNL-1043 AJ AmsterdamPhone: +31 (0) 20 / 587 67 00Fax: +31 (0) 20 / 587 68 39e mail: [email protected] Electronics AS NORWAYTeglverksveien 1N-3002 DrammenPhone: +47 (0) 32 / 24 30 00Fax: +47 (0) 32 / 84 85 77e mail: [email protected] Technology Sp. z o.o. POLANDul. Sliczna 36PL-31-444 KrakówPhone: +48 (0) 12 / 632 28 85Fax: +48 (0) 12 / 632 47 82e mail: [email protected] Trading & Services srl ROMANIAStr. Biharia No. 67-77RO-013981 Bucuresti 1Phone: +40 (0) 21 / 201 1146Fax: +40 (0) 21 / 201 1148e mail: [email protected] d.o.o. SLOVENIAStegne 11SI-1000 LjubljanaPhone: +386 (0) 1-513 8100Fax: +386 (0) 1-513 8170e mail: [email protected] Electronics AB SWEDENBox 426S-20124 MalmöPhone: +46 (0) 40 / 35 86 00Fax: +46 (0) 40 / 35 86 02e mail: [email protected] AG SWITZERLANDPostfach 282CH-8309 NürensdorfPhone: +41 (0) 1 / 838 48 11Fax: +41 (0) 1 / 838 48 12e mail: [email protected] TURKEYDarülaceze Cad. No. 43 Kat. 2TR-80270 Okmeydani-IstanbulPhone: +90 (0) 212 / 320 1640Fax: +90 (0) 212 / 320 1649e mail: [email protected] Automation Ltd. UKRAINE15, M. Raskova St., Fl. 10, Office 1010UA-02002 KievPhone: +380 (0) 44 / 238-83-16Fax: +380 (0) 44 / 238-83-17e mail: [email protected]

EURASIAN REPRESENTATIVES

Avtomatika Sever Ltd. RUSSIALva Tolstogo St. 7, Off. 311RU-197376 St PetersburgPhone: +7 812 / 11 83 238Fax: +7 812 / 11 83 239e mail: [email protected] RUSSIAPromyshlennaya St. 42RU-198099 St PetersburgPhone: +7 812 / 325 36 53Fax: +7 812 / 147 20 55e mail: [email protected] RUSSIASystems SiberiaPartizanskaya St. 27, Office 306RU-121355 MoscowPhone: +7 095/ 416-4321Fax: +7 095/ 416-4321e mail: [email protected] RUSSIASystems SiberiaShetinkina St. 33, Office 116RU-630088 NovosibirskPhone: +7 3832 / 22-03-05Fax: +7 3832 / 22-03-05e mail: [email protected] RUSSIAul. Garschina 11RU-140070 MoscowPhone: +7 095 / 514 9316Fax: +7 095 / 514 9317e mail: [email protected] RUSSIAKrasnij Prospekt 220-1Office No. 312RU-630049 NovosibirskPhone: +7 3832 / 10 66 18Fax: +7 3832 / 10 66 26e mail: [email protected] RUSSIAIndustrial Computer Systems ZaoRyazanskij Prospekt 8a, Office 100RU-109428 MoscowPhone: +7 095 / 232 - 0207Fax: +7 095 / 232 - 0327e mail: [email protected] Uralelektra RUSSIAul. Sverdlova 11aRU-620027 EkaterinburgPhone: +7 34 32 / 53 27 45Fax: +7 34 32 / 53 27 45e mail: [email protected] Rosgidromontazh Ltd. RUSSIA23, Lesoparkovaya Str.RU-344041 Rostov On DonPhone: +7 8632 / 36 00 22Fax: +7 8632 / 36 00 26e mail: —STC Drive Technique RUSSIAul. Bajkalskaja 239, Office 2 - 23RU-664075 IrkutskPhone: +7 3952 / 24 38 16Fax: +7 3952 / 23 02 98e mail: [email protected] Drive Technique RUSSIAPoslannikov Per. 9, str.1RU-107005 MoscowPhone: +7 095 / 790-72-10Fax: +7 095 / 790-72-12e mail: [email protected]

AFRICAN REPRESENTATIVE

CBI Ltd. SOUTH AFRICAPrivate Bag 2016ZA-1600 IsandoPhone: +27 (0) 11/ 928 2000Fax: +27 (0) 11/ 392 2354e mail: [email protected]

INDUSTRIAL AUTOMATION

Gothaer Strasse 8 Phone: +49 2102 486-0 Fax: +49 2102 486-7170 www.mitsubishi-automation.deD-40880 Ratingen Hotline: +49 1805 000-7650 [email protected] www.mitsubishi-automation.com

PLC1

1/04

-Prin

ted

inGe

rman

y

fx1 n s fx2n communicationusermanual jy992d69901 e

Documents

manual number

respective manual

manual presentation

manual layout

mitsubishi users

installation site

users manualbrand

explanations understandable