0% found this document useful (0 votes)
134 views186 pages

Communication Manual PDF

This document is a user manual for the FX communication facilities (RS-232C, RS-485). It provides guidelines for safely installing and operating the communication capabilities of FX series programmable controllers. The manual contains explanations, text, diagrams and safety symbols to ensure proper use. It is intended to be read by trained professionals qualified to local and national standards.

Uploaded by

Rafael Cortes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
134 views186 pages

Communication Manual PDF

This document is a user manual for the FX communication facilities (RS-232C, RS-485). It provides guidelines for safely installing and operating the communication capabilities of FX series programmable controllers. The manual contains explanations, text, diagrams and safety symbols to ensure proper use. It is intended to be read by trained professionals qualified to local and national standards.

Uploaded by

Rafael Cortes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 186

USERS MANUAL

FX COMMUNICATION (RS-232C, RS485)


FX communication

Foreword

This manual contains text, diagrams and explanations which will guide the reader in the cor-
rect installation and operation of the communication facilities of FX series. It should be read
and understood befre attempting to install or use the communication facilities of FX series.

Further infomation can be found in the manual of each programmable controller.

If in doubt at any stage of the installation of the communication facilities of FX series always
consult a professional electrical engineer who is qualified and trained to the local and
national standards which apply to the installation site.

If in doubt about the operation or use of the communication facilities of FX series please
consult the nearest Mitsubisi Electric distributor.

This manual is subject to change without notice.


FX communication

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

USERS MANUAL

Manual number : JY992D69901


Manual revision : C
Date : March 2000

Brand and product names describeed by/in this manual are trademarks or registered trade-
marks of the irrespective owners.

i
FX communication

ii
FX communication

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

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


Mitsubishi Electric.... .....................................................................
America (01) 847-478-2283 Your company ..............................................
Australia (02) 638 -7072 .....................................................................
Germany (0 21 02) 486-1 12 Your location:................................................
South Africa (0 27) 11 444-0223 .....................................................................
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 Un-friendly
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 Un-helpful
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,if possi-
ble 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 product
and this manual easy to use.

iii
FX communication

iv
FX communication

Guidelines for the Safety of the User and Protection of the programmable con-
trollers
This manual provides information for the use of the FX series communication unit. The manual
has been written to be used by trained and competent personnel. The definition of such a per-
son or persons is as follows;
a) Any engineer who is responsible for the planning, design and construction of automatic
equipment using the product associated with this manual should be of a competent
nature, trained and qualified to the local and national standards required to fulfill that
role. These engineers should be fully aware of all aspects of safety with regards to auto-
mated equipment.
b) Any commissioning or service engineer must be of a competent nature, trained and qual-
ified to the local and national standards required to fulfill that job. These engineers
should also be trained in the use and maintenance of the completed product. This
includes being completely familiar with all associated documentation for the said prod-
uct. All maintenance should be carried out in accordance with established safety prac-
tices.
c) All operators of the completed equipment should be trained to use that product in a safe
and coordinated manner in compliance to established safety practices. The operators
should also be familiar with documentation which is connected with the actual operation
of the completed equipment.
Note : Note: the term completed equipment refers to a third party constructed device which
contains or uses the product associated with this manual.
Notes on the Symbols Used in this Manual
At various times through out this manual certain symbols will be used to highlight points of
information which are intended to ensure the users personal safety and protect the integrity of
equipment. Whenever any of the following symbols are encountered its associated note must
be read and understood. Each of the symbols used will now be listed with a brief description of
its 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 property
damage.

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 should
be aware of.

6) Indicates a point of interest or further explanation.

v
FX communication

Under no circumstances will Mitsubishi Electric be liable responsible for any consequential
damage 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 to understand-
ing the text, not to guarantee operation. Mitsubishi Electric will accept no responsibility for
actual use of the product based on these illustrative examples.

Owing to the very great variety in possible application of this equipment, you must satisfy
yourself as to its suitability for your specific application.

vi
FX communication

Table of Contents

Guideline of Safety ..........................................................................................v

1. Introduction ............................................................................................. 1-1


1.1 Communication Types ...........................................................................................1-1
1.2 System Configuration ............................................................................................1-2
1.2.1 N:N Network.............................................................................................................................. 1-2
1.2.2 Parallel Link .............................................................................................................................. 1-2
1.2.3 Computer Link........................................................................................................................... 1-3
1.2.4 No Protocol Communication .................................................................................................... 1-4
1.3 Supporting Function and Version .........................................................................1-4

2. Wiring ...................................................................................................... 2-1


2.1 Caution ..................................................................................................................2-1
2.1.1 Common .................................................................................................................................. 2-1
2.1.2 FX2N-485-BD ........................................................................................................................... 2-1
2.1.3 FX0N-485ADP .......................................................................................................................... 2-2
2.1.4 FX2-40AW................................................................................................................................. 2-2
2.2 Using RS232C Interface ........................................................................................2-3
2.2.1 Using RS Instruction or Computer Link..................................................................................... 2-3
2.2.2 Using FX2N-232IF ..................................................................................................................... 2-4
2.3 Using RS485 Interface...........................................................................................2-6
2.3.1 Selection of Wiring .................................................................................................................... 2-6
2.3.2 Terminal Resistor...................................................................................................................... 2-6
2.3.3 One-pair Wiring ........................................................................................................................ 2-7
2.3.4 Two-pair Wiring ........................................................................................................................ 2-8
2.4 Parallel Link ...........................................................................................................2-9
2.4.1 FX2N(1N)-485-BD and FX0N-485ADP........................................................................................ 2-9
2.4.2 Only FX0N-485ADP................................................................................................................. 2-10
2.4.3 FX2N(1N)-485-BD and FX2N(1N)-485-BD ................................................................................. 2-11
2.4.4 Only FX2-40AW ..................................................................................................................... 2-12
2.4.5 FX2-40AP .............................................................................................................................. 2-12

3. Specifications .......................................................................................... 3-1


3.1 Specifications of Communication ..........................................................................3-1
3.2 Communication Time.............................................................................................3-2
3.2.1 N:N network ............................................................................................................................. 3-2
3.2.2 Parallel link ............................................................................................................................... 3-2
3.2.3 Computer link............................................................................................................................ 3-3

vii
FX communication

4. N:N Network............................................................................................ 4-1


4.1 Related Flags and Data Registers.........................................................................4-1
4.1.1 Auxiliary Relays ....................................................................................................................... 4-1
4.1.2 Data Registers ......................................................................................................................... 4-2
4.2 Setting....................................................................................................................4-3
4.2.1 Setting the Station No. (D8176) ................................................................................................ 4-3
4.2.2 Setting the Total Number of Slave Stations (D8177) ............................................................... 4-3
4.2.3 Setting the Refresh Range (D8178).......................................................................................... 4-4
4.2.4 Setting Retry Count (D8178)..................................................................................................... 4-5
4.2.5 Setting Comms Time-out (D8179) ............................................................................................ 4-5
4.2.6 Program Used for Setting ........................................................................................................ 4-6
4.3 Example Program ..................................................................................................4-7
4.3.1 System Configuration ............................................................................................................... 4-7
4.3.2 Operations ................................................................................................................................ 4-7
4.3.3 Example of Setting Program ..................................................................................................... 4-8
4.3.4 Example of Error Program ....................................................................................................... 4-8
4.3.5 Example of Operation Program ................................................................................................ 4-9

5. Parallel link.............................................................................................. 5-1


5.1 Related Flags and Data Registers ........................................................................5-1
5.2 Mode and Link Device ...........................................................................................5-2
5.2.1 Normal Mode (Special auxiliary relay M8162: OFF) ................................................................ 5-2
5.2.2 High Speed Mode (Special auxiliary relay M8162: ON) ........................................................... 5-3
5.3 Example Program ..................................................................................................5-4
5.3.1 Normal Mode ............................................................................................................................ 5-4
5.3.2 High Speed Mode ..................................................................................................................... 5-4

6. Communication format (D8120) .............................................................. 6-1


6.1 What Is Communication Format ? .........................................................................6-1
6.2 Related Flags and Data Registers.........................................................................6-1
6.2.1 Special Auxiliary Relays ........................................................................................................... 6-1
6.2.2 Special Data Registers ............................................................................................................ 6-1
6.3 Communication Format (D8120) ..........................................................................6-2
6.4 Example of setting program...................................................................................6-3

viii
FX communication

7. Computer Link......................................................................................... 7-1


7.1 Data Flow by Link ..................................................................................................7-1
7.2 Information Needed Before Programming .............................................................7-3
7.2.1 Programmable Controller Operation ......................................................................................... 7-3
7.2.2 Notes of Computer.................................................................................................................... 7-3
7.3 How to Read a Control Protocol Diagram..............................................................7-4
7.4 Basic Formats of Dedicated Protocol ....................................................................7-5
7.4.1 Control Protocol Format 1 ........................................................................................................ 7-6
7.4.2 Control Protocol Format 4......................................................................................................... 7-7
7.4.3 Control Protocol Parts Explained .............................................................................................. 7-8
7.4.4 Time- out Check Time............................................................................................................. 7-11
7.5 Communication Timing Chart ..............................................................................7-12
7.5.1 Reading Data from Programmable controller ......................................................................... 7-12
7.5.2 Writing Data to Programmable Controller ............................................................................... 7-12
7.5.3 Communication Time .............................................................................................................. 7-13
7.6 Character Area Data Transmission .....................................................................7-14
7.6.1 Bit Device Memory.................................................................................................................. 7-14
7.6.2 Word Device Memory ............................................................................................................. 7-15
7.7 Commands and Device Ranges ..........................................................................7-16
7.7.1 Commands.............................................................................................................................. 7-16
7.7.2 Device specification ranges .................................................................................................... 7-17
7.8 Example Computer Program for Loopback Test .................................................7-18

8. Commands.............................................................................................. 8-1
8.1 Batch Read of Bit Device (BR command)..............................................................8-2
8.2 Batch Read of Word Device (WR command) ........................................................8-3
8.3 Batch Write of Bit Device (BW command) .............................................................8-5
8.4 Batch Write of Word Device (WW command)........................................................8-6
8.5 Test of Bit Device (BT command)..........................................................................8-8
8.6 Test of Word Device (WT command) ....................................................................8-9
8.7 Remote RUN/STOP (RR, RS commands) ..........................................................8-10
8.7.1 Operation of Remote RUN/STOP ........................................................................................... 8-10
8.7.2 Conditions for Valid Execution of Remote RUN/STOP........................................................... 8-10
8.7.3 Control Specification and Examples of Remote RUN/STOP .................................................. 8-11
8.8 Reading The Programmable Controller Type (PC command).............................8-12
8.8.1 Type Codes ............................................................................................................................ 8-12
8.8.2 Control Specification and Example ......................................................................................... 8-13
8.9 Global Function (GW command) .........................................................................8-14
8.9.1 Control Specification and Example of Global Function........................................................... 8-14
8.10 On-demand Function .........................................................................................8-15
8.10.1 Special Devices Used in On-demand Function .................................................................... 8-15
8.10.2 On-demand Control Protocol ................................................................................................ 8-16
8.10.3 Specification and Example of On-demand............................................................................ 8-18
8.11 Loopback Test ...................................................................................................8-21

ix
FX communication

9. RS instruction.......................................................................................... 9-1
9.1 Function and Operation .........................................................................................9-1
9.1.1 Send and Receive Program...................................................................................................... 9-1
9.1.2 Operation of RS Instruction....................................................................................................... 9-2
9.1.3 Related Flags and Data Registers ............................................................................................ 9-3
9.2 Hardware Hand Shake Operation..........................................................................9-5
9.2.1 FX, FX2C, FX0N, FX1S, FX1N and FX2N (earlier than V 2.00).................................................... 9-5
9.2.2 FX2N, FX2NC (V 2.00 or later) ................................................................................................... 9-9
9.3 Number of Communication Data .........................................................................9-12
9.3.1 Deal with 16 bits Data ............................................................................................................. 9-12
9.3.2 Deal with 8 bits Data ............................................................................................................... 9-13
9.4 Example Program ................................................................................................9-14
9.4.1 Personal Computer ................................................................................................................. 9-14
9.4.2 Printer ..................................................................................................................................... 9-16
9.5 Supporting RS Instruction and Programming Protocol ........................................9-18
9.5.1 Programmable Controller and Version.................................................................................... 9-18
9.5.2 Operating Conditions and Format Set Content....................................................................... 9-18

10. FX2N-232IF ......................................................................................... 10-1


10.1 Introduction ........................................................................................................10-1
10.1.1 Outline of Product ................................................................................................................. 10-1
10.2 Allocation of Buffer Memories (BFMs) ..............................................................10-2
10.2.1 BFM List ............................................................................................................................... 10-2
10.2.2 Communication Format <BFM#0> ....................................................................................... 10-4
10.2.3 Command BFM #1 .................................................................................................. 108
10.2.4 Receive Upper Limit Byte Count BFM #2 ................................................................... 109
10.2.5 Receive Time-out Time <BFM #3> ....................................................................................... 10-9
10.2.6 Send Header <BFM #5 (upper), BFM #4 (lower)>................................................................ 10-9
10.2.7 Send Terminator <BFM #7 (upper), BFM #6 (lower)> .......................................................... 10-9
10.2.8 Receive Header <BFM #9 (upper), BFM #8 (lower)> ......................................................... 10-10
10.2.9 Receive Terminator <BFM #11 (upper), BFM #10 (lower)>................................................ 10-10
10.2.10 Receive Suspension Waiting Time <BFM #12> ............................................................... 10-10
10.2.11 Number of Remaining Send Data <BFM #13> ................................................................. 10-11
10.2.12 Number of Receive Buffers <BFM #14> ........................................................................... 10-11
10.2.13 Send Sum Result <BFM #15> .......................................................................................... 10-11
10.2.14 Receive Sum Result <BFM #16>...................................................................................... 10-11
10.2.15 Time from CS ON to Send Start <BFM #20>.................................................................... 10-12
10.2.16 Time from Completion of Actual Send to RS OFF (completion flag ON) <BFM #21> ...... 10-12
10.2.17 Status <BFM #28> ........................................................................................................... 10-13
10.2.18 Error Code <BFM #29>..................................................................................................... 10-14
10.2.19 Model Code <BFM #30>................................................................................................... 10-14
10.2.20 Send Byte Count <BFM #1000> ....................................................................................... 10-14
10.2.21 Send Buffers <BFMs #1001 to #1256>............................................................................. 10-14
10.2.22 Receive Byte Count <BFM #2000> .................................................................................. 10-15
10.2.23 Receive Buffers <BFM #2001 to #2256>.......................................................................... 10-15
10.2.24 Spare Receive Buffers for Interlink Connection Mode <BFM #2257 to #2271> ............... 10-15
10.3 Hardware Hand Shake Operation....................................................................10-16
10.3.1 No Hardware Hand Shake .................................................................................................. 10-16
10.3.2 Standard RS232C Mode..................................................................................................... 10-17
10.3.3 Interlink Mode ..................................................................................................................... 10-18
10.4 Example Program ............................................................................................10-19
10.4.1 Example of 16 Bits Data Communication ........................................................................... 10-19
10.4.2 Example of 8 Bits Data Communication ............................................................................. 10-23

x
FX communication

11. Optional Programming Port................................................................. 11-1


11.1 FX2N-422-BD, FX1N-422-BD...............................................................................11-1
11.2 FX2N-232-BD FX1N-232BD and FX0N-232ADP...................................................11-2
11.2.1 Connection cables ................................................................................................................ 11-2
11.3 Cautions on Use ................................................................................................11-3
11.3.1 Cautions on Setting............................................................................................................... 11-3
11.3.2 Cautions on use ................................................................................................................... 11-3

12. Diagnostics.......................................................................................... 12-1


12.1 Common Items ..................................................................................................12-1
12.2 N:N Network ......................................................................................................12-2
12.2.1 Error Code ............................................................................................................................ 12-2
12.2.2 Diagnostics ........................................................................................................................... 12-2
12.3 Parallel Link .......................................................................................................12-3
12.3.1 Diagnostics ........................................................................................................................... 12-3
12.4 Computer Link ...................................................................................................12-4
12.4.1 NAK Error Code .................................................................................................................... 12-4
12.4.2 Programmable Controller Error Code ................................................................................... 12-4
12.4.3 Diagnostics ........................................................................................................................... 12-5
12.5 RS Instruction ....................................................................................................12-6
12.5.1 Diagnostics ........................................................................................................................... 12-6
12.6 FX2N-232IF.........................................................................................................12-7
12.6.1 Error code ............................................................................................................................. 12-7
12.6.2 Diagnostics ........................................................................................................................... 12-7
12.7 Using Optional Programming Port .....................................................................12-8
12.7.1 FX1S, FX1N and FX2N(C) earlier V2.00 .................................................................................. 12-8
12.7.2 FX2N, FX2NC whose version is V 2.00 or later ...................................................................... 12-8

Appendix A:
Further Information Manual List ........................................................................... A-1

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

xi
FX communication

xii
FX Series Programmable Controllers Introduction 1

1 Introduction 1

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Introduction 1
FX communication Introduction 1

1. Introduction
1

1.1 Communication Types


The FX Series supports the fllowing 5 types of communication.
1 ) N:N network
Data transfer with FX2N, FX2NC, FX1N, FX 1S, FX0N programmable controllers can be per-
formed on the N:N basis. They can link data of a small-scale system if using this network.
For system configuration refer to subsection 1.2.1, specifications refer to chapter 3, wiring
refer to chapter 2, settings, the number of transferred data and example program refer to
chapter 4,diagnostics refer to chapter 12.
2 ) Parallel link
Data transfer with FX2N, FX2NC, FX1N, FX and FX2C programmable controllers can be per-
formed on a 1:1 basis for 100 auxiliary relays and 10 data registers. With FX1S and FX0N data
transfer is performed for 50 auxiliary relays and 10 data registers.
For a system configuration refer to Subsection 1.2.2, specifications refer to chapter 3, wiring
refer to chapter 2, the setting and example program refer to chapter 5, diagnostics refer to
chapter 12.
3 ) Computer link (Data transfer using dedicated protocol)
Data transfer with RS485 (422) units can be performed on a 1:n (16) basis using the dedi-
cated protocol.
For system configuration refer to subsection 1.2.3, specifications refer to chapter 3, wiring
refer to chapter 2, setting of communication format refer to chapter 6, dedicated protocol
refer to chapter 7 & 8, diagnostics refer to chapter 12.
4 ) No protocol communication (Data transfer using RS instruction)
Data communication with a diversified RS232C unit including personal computers, bar code
readers and printers can be performed using no protocol communications.
This communication uses RS instructions or an FX2N-232IF special function block.
For system configuration refer to subsection 1.2.3, specifications refer to chapter 3, wiring
refer to chapter 2, setting of communication format, RS instruction and example program
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, for
the 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 port
The port can support a programming protocol, if connected to an FX2N-232-BD, FX0N-32ADP,
FX1N-232-BD, FX2N-422-BD and FX1N-422-BD for FX2N, FX2NC, FX1N, FX1S Series program-
mable controller.
For notes on use, refer to chapter 11, diagnostics refer to chapter 12.

1-1
FX communication Introduction 1

1.2 System Configuration


For programming protocol refer to chapter 11.

1.2.1 N:N Network


FX2N-CNV-BD FX2N-485-BD FX1N-485-BD FX1N-CNV-BD

FX0N, FX1S, FX1S,


FX2N FX2N
FX2NC FX1N FX1N

FX0N-485ADP FX0N-485ADP FX0N-485ADP

When not using FX2N-485-BD or FX1N-485-BD in the system, total extension distance Max. 500m.
(Use : Max. 50m)
Total station of this network is Max. 8 stations.

1.2.2 Parallel Link

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

, Using interface Extension distance


FX2N-485-BD Max. 50 m
FX2N
FX2N-CNV-BD + FX0N-485ADP
Max. 500 m *1
FX2NC FX0N-485ADP
*1 When including FX2N-485-BD in system configuration, total extension distance max 50m.
2 ) FX1N (Shielded twisted-pair cable)

, Using interface Extension distance


FX1N-485-BD Max. 50 m
FX1N
FX1N-CNV-BD + FX0N-485ADP Max. 500 m *2

*2 When including FX1N-485-BD in system configuration, total extension distance max 50m.
3 ) FX1S (Shielded twisted-pair cable)

, Using interface Extension distance


FX1N-485-BD Max. 50 m
FX1s
FX1N-CNV-BD + FX0N-485ADP *3
Max. 500 m
*3 When including FX1N-485-BD in system configuration, total extension distance max 50m.
4 ) FX0N (Shielded twisted-pair cable)

, Using interface Extension distance


FX0N FX0N-485ADP Max. 500 m

1-2
FX communication Introduction 1

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

, Using interface Extension distance 1


FX2-40AW (Shielded twisted-pair cable) Max. 10 m
FX2, FX2C
FX2-40AP (Glassfiber cable) Max. 50 m

Note;
Parallel link is possible between the same series PLCs, or between other series in the
same group. However, parallel link between each group cannot be achieved.
Groups are separated as follows.
Group No. Series
Group 1 FX2N, FX2NC
Group 2 FX1N
Group 3 FX1S
Group 4 FX0N
Group 5 FX, FX2C

1.2.3 Computer Link


1 ) Use RS485

Computer

RS232C
RS485(422)

FX-485PC-IF FX2,
FX2C
FX0N-485ADP
FX0N, FX2NC, FX-485ADP FX2N + FX2N-485-BD, A series PLC + A(1S)J71UC24
FX2N + FX2N-CNV-BD, FX1S + FX1N-485-BD,
FX1S + FX1N-CNV-BD, FX1N + FX1N-485-BD
FX1N + FX1N-CNV-BD

When not using FX2N-485-BD or FX1N-485-BD in the system, total extension distance is
Max. 500m. (Use : Max. 50m)
Total station of this network is Max. 16 stations.

2 ) Use RS232C

FX2N : FX2N-232-BD,
FX2N-CNV-BD + FX0N-232ADP
FX2NC, FX0N : FX0N-232ADP
Computer
FX1N, FX1S : FX1N-232-BD,
FX1N-CNV-BD + FX0N-232ADP
FX2, FX2C : FX-232ADP

Total extension distance is 15m.

1-3
FX communication Introduction 1

1.2.4 No Protocol Communication

RS232C
Personal computer *3 *3 *3
FX2N + FX2N +
FX2N-CNV-BD FX2N-232-BD FX2NC

FX0N-232ADP FX0N-232ADP
*4 FX0N *4 FX1N + *4
FX1N + FX1N-232-BD
FX, FX2C FX1N-CNV-BD FX1S +
Max 15m *1 FX1S + FX1N-232-BD
FX1N-CNV-BD
Bar code reader FX-232ADP FX0N-232ADP

FX2N, FX1N,
FX2NC + FX2NC-CNV-IF

FX2N-232IF

RS485(422)
*4 *3
FX2N + FX2N-CNV-BD
Printer FX1N + FX1N-CNV-BD FX2N + FX2N-485-BD
FX1S + FX1N-CNV-BD
FX0N, FX2NC

Max 500m *2 FX0N-485ADP


*4
FX1N + FX1N-485-BD
FX1S + FX1N-485-BD

*1 RS485/RS232C signal convertor becomes necessary for a case of RS485 interface for com-
puter connection.
*2 When using FX1N-485-BD, FX2N-485-BD in system, total extension distance max 50m.
But, RS485/RS232C signal convertor become necessary for a case of RS232C interface for
computer connection.
*3 This system configuration can achieve full-duplex communication or the half-duplex communi-
cation.
*4 This system configuration achieve only half-duplex communication.

1.3 Supporting Function and Version


Items FX2N, FX2NC FX1N, FX1S FX0N FX, FX2C
N:N network V2.00 or more No sport
Parallel link All versions All versions
All versions
Computer link All versions V1.20 or more V3.30 or more
No protocol Use RS instruction All versions V3.00 or more
communication Use FX2N-232IF Not supported.

1-4
FX Series Programmable Controllers Wiring 2

1 Introduction

2 Wiring 2

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Wiring 2
FX communication Wiring 2

2. Wiring
For the terminal layout when using a communication unit, refer to the individual units manual.

2
2.1 Caution
2.1.1 Common

1 ) This system is designed to read and write data (forced on/off) while the programmable con-
troller is running.
If abnormal data is written into the programmable controller, due to effects of noise, the pro-
grammable controller may malfunction and cause machine trouble or an accident. There-
fore, 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 dis-
tance of more than 100 mm 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 avoid
electric shock or damage of product.

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

2.1.2 FX2N-485-BD
To connect the RS485(422) unit, use a shielded twist-pair cable. The cable model must be
AWG 26 to 16, and the maximum tightening torque must be 0.6 Nm (6 kgfcm). If a cable other
than the AWG 26 to 16 is used, normal communication cannot be assured because the termi-
nal may be imperfectly contacted. It is recommended to insert a cable integrated by a crimping
tool into the terminal.

6mm

2-1
FX communication Wiring 2

2.1.3 FX0N-485ADP
1 ) The terminal screws of the FX(0N)-485ADP are M3 screws and therefore the crimp style ter-
minal (see drawing) suitable for use with these screws should be fitted to the cable for wir-
ing.
For M3 For M3
6.2mm 6.2mm
(0.24 inches) (0.24 inches)
or less or less
2 ) The terminal tightening torque is 0.5 to 0.8 Nm(5 to 8 kgfcm), tighten securely to avoid
malfunction.

2.1.4 FX2-40AW
1 ) The terminal screws for the terminal block of the FX2-40AW are M3.5 screws and therefore
the crimp style terminal (see drawing) suitable for use with these screws should be fitted to
the cable for wiring.
For M3.5 For M3.5
6.8mm 6.8mm
(0.27 inches) (0.27 inches)
or less or less
2 ) The terminal tightening torque is 0.5 to 0.8 Nm (5 to 8 kgfcm), tighten securely to avoid mal-
function.

2-2
FX communication Wiring 2

2.2 Using RS232C Interface


Below is a typical wiring example. Please wire similar to the following pin name, when a pin num-
ber on the side of a counterpart machine differs.

2.2.1 Using RS Instruction or Computer Link


2
1 ) Terminal specification device
P rogram m ab le C ontroller S ide R S -232C D e vice S ide
U ses C S , R S U ses D R , E R
S ignal F X 2N - 232-B D F X 0N - FX- S ignal S ignal
nam e F X 1N - 232-B D 232A D P 232A D P nam e 9-pin 25-pin nam e 9-pin 25-pin
D -S U B D -S U B D -S U B D -S U B
FG - 1 FG - 1 FG - 1
R D (R X D ) 2 3 R D (R X D ) 2 3 R D (R X D ) 2 3
S D (T X D ) 3 2 S D (T X D ) 3 2 S D (T X D ) 3 2
E R (D T R ) 4 20 RS RTS) 7 4 E R (D T R ) 4 20
S G (G N D ) 5 7 S G (G N D ) 5 7 S G (G N D ) 5 7
D R (D S R ) 6 6 C S (C T S ) 8 5 D R (D S R ) 6 6

Note;
When using ER and DR signals, please also check if RS and CS signals are needed according to
the RS232C device specifications.

2 ) Modem specification device


P rogram m ab le C ontroller S ide R S -232C D e vice S ide
U ses C S , R S U ses D R , E R
S ignal F X 2N - 232-B D F X 0N - FX- S ignal S ignal
nam e F X 1 N - 232-B D 232A D P 232A D P nam e 9-pin 25-pin nam e 9-pin 25-pin
D -S U B D -S U B D -S U B D -S U B
FG - 1 FG - 1 FG - 1
C D (D C D ) 1 - 8 C D (D C D ) 1 8 FG 1 8
R D (R X D ) 2 3 R D (R X D ) 2 3 R D (R X D ) 2 3
S D (T X D ) 3 2 S D (T X D ) 3 2 S D (T X D ) 3 2
E R (D T R ) 4 20 RS RTS) 7 4 E R (D T R ) 4 20
S G (G N D ) 5 7 S G (G N D ) 5 7 S G (G N D ) 5 7
D R (D S R ) 6 6 C S (C T S ) 8 5 D R (D S R ) 6 6

Note;
The FX0N-232ADP does not monitor the CD pin (pin8).
3 ) Computer link
Please refer to 2.2.1 1) for wiring.

2-3
FX communication Wiring 2

2.2.2 Using FX2N-232IF


The signal wiring of the RS232C equipment varies depending on the RS232C connection speci-
fications. Check the specifications of the RS232C equipment used, then connect the signals cor-
rectly. 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 in
P rogram m able C ontroller S id e R S -232C D evice S ide
accordance with the condition
S ignal S ignal 9-pin 25-pin
F X 2N -232IF determined by the software in
nam e nam e D -S U B D -S U B
S D (T X D ) 3 S D (T X D ) 3 2 the FX2N-232IF and the counter-
R D (R X D ) 2 R D (R X D ) 2 3 part equipment.
S G (G N D ) 5 S G (G N D ) 5 7

2 ) Terminal specification device (Use control line)


a ) Standard RS232C mode (Use cross cable)
Setting communication format (BFM #0); b9=0, b8=1
As the carrier to send (CS) sig-
P rogram m able C ontroller S ide R S -232C D evice S ide nal pin of the FX2N-232IF itself
S ignal S ignal 9-pin 25-pin
F X 2N -232IF receives the request to send
nam e nam e D -S U B D -S U B
S D (T X D ) 3 S D (T X D ) 3 2
(RS) signal, signal transfer is
performed as if the counterpart
R D (R X D ) 2 R D (R X D ) 2 3
equipment is functioning.
R S (R T S ) 7 R S (R T S ) 7 4
C S (C T S ) 8 C S (C T S ) 8 5 *1 When the CD signal is not
C D (D C D ) 1 C D (D C D ) 1 8 monitored, the CD signal pin
*1 *1 is not required to be con-
E R (D T R ) 4 E R (D T R ) 4 20
nected. With regard to the
D R (D T R ) 6 D R (D T R ) 6 6
*2 *2 CD signal, the FX2N-232IF
S G (G N D ) 5 S G (G N D ) 5 7
only indicates the status.
*2 The FX2N-232IF only indi-
cates the status.

2-4
FX communication Wiring 2

b ) Interlink connection mode (Use interlink serial cross cable)


Setting connection format (BFM #0); b9=1, b8=1
In the interlink connection
P rogram m able C ontroller S ide R S -232C D evice S ide mode, data exceeding 512
S ignal S ignal 9-pin 25-pin
F X 2N -232IF bytes (upper limit of the receive
nam e nam e D -S U B D -S U B
buffer in the FX2N-232IF) can
S D (T X D ) 3 S D (T X D ) 3 2
be received.
2
R D (R X D ) 2 R D (R X D ) 2 3
R S (R T S ) 7 R S (R T S ) 7 4 *1 The FX2N-232IF only indi-
C S (C T S ) 8 C S (C T S ) 8 5 cates the status.
*1 *1
E R (D T R ) 4 E R (D T R ) 4 20 *2 In this mode, the request to
D R (D T R ) 6 D R (D T R ) 6 6 send (RS) signal functions
*2 *2
S G (G N D ) 5 S G (G N D ) 5 7 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 RS232C mode (Using straight cable)
Setting communication format (BFM #0); b9=0, b8=1
*1 The FX2N-232IF indicates
P rogram m able C ontroller S ide R S -232C D evice S ide
S ignal S ignal 9-pin 25-pin
the status exclusively.
F X 2N -232IF
nam e nam e D -S U B D -S U B *2 When the CD signal is not
S D (T X D ) 3 S D (T X D ) 3 2 monitored, the CD signal pin
R D (R X D ) 2 R D (R X D ) 2 3 is not required to be con-
R S (R T S ) 7 R S (R T S ) 7 4 nected. With regard to the
C S (C T S ) 8 C S (C T S ) 8 5 CD signal, the FX2N-232IF
C D (D C D ) 1 *1 *1 C D (D C D ) 1 8 indicates the status exclu-
E R (D T R ) 4 E R (D T R ) 4 20 sively.
D R (D T R ) 6 *2 *2 D R (D T R ) 6 6 *3 When the CI signal is not
S G (G N D ) 5 S G (G N D ) 5 7 required, the CI signal pin is
C I (R I) 9 *3 *3 C I (R I) 9 22 not required to the con-
nected. With regard to the
CI signal, the FX2N-232IF
indicates the status exclu-
sively.

2-5
FX communication Wiring 2

2.3 Using RS485 Interface


2.3.1 Selection of Wiring
The wiring of RS485 can either be one-pair wiring or two-pair wiring. The wiring method is
decided according to the usage. Please select the wiring method from the table below.

Usage One-pair wiring Two-pair wiring

No protocol Half-duplex communication l*2


(Use RS instruction) *1 Full-duplex communication *3
It is necessary to set the
message wait in 70 ms or less.

Dedicated protocol It is not necessary to set the
(Use computer link)*1 massage wait in 70 ms or less.
l*2

Use on-demand function


Parallel link *4 l
N:N network
lRecommendation, OK, Can not use
*1 When this product is added to the system, please match the wiring to the existing method of
the system.
*2 When using FX2N-485-BD with this wiring method, remember to take account of/or ignore the
echo of the commands sent from the FX2N programmable controller.
*3 Please use FX2N programmable controller and FX2N-485-BD together.
Full-duplex the combination cannot be achieved in other configurations.
*4 For wiring of parallel link, see section 2.4.

2.3.2 Terminal Resistor


A terminal resistor must be used at both ends of the communication line as described in section
2.3.3 and 2.3.4.
1 ) In the case of two-pair wiring, connect the terminal resister Orange Orange Brown
(330, 1/4W) between terminals SDA and SDB as well between 330
terminals RDA and RDB. Use the resistors offered as accesso- 1/4 W
ries of the product.
Brown Brown Brown
2 ) In the case of one-pair wiring, connect the terminal resister
(110, 1/2W) between terminals RDA and RDB. Use the resis- 110
1/2 W
tors offered as accessories of the product.

2-6
FX communication Wiring 2

2.3.3 One-pair Wiring


FX1N-485-BD A series programmable
RS485/422 unit *4 FX2N-485-BD FX (0N)-485ADP controller's computer link unit

R*1 R*1
SDA SDA SDA SDA
2
SDB SDB SDB SDB
R*1 R*1
RDA RDA RDA RDA

RDB RDB RDB RDB


LINK
SG SG SG *3 SG *3
*2 FG FG

Grounding of registance 100 or less

*1 R is the terminating resistor. Connect the terminating resistor (110) between terminals SDA
and SDB.
*2 Connect the shield of the FX2N-485-BD, FX1N-485-BD using shielded twist-pair cable to
ground (100 or less).
Please adjust the grounding only to one side.
*3 Connect terminal FG to each terminal of the programmable controller body, grounded with
resistance of 100 or less. However, for the computer link unit of the A series programmable
controller, see the manual of the computer link unit.
*4 If an RS485/232 adapter is required, please use the FX-485-PC-IF. When using the FX-
485PC-IF with this wiring method, either take account for or ignore the echo of the com-
mands sent by the computer.

2-7
FX communication Wiring 2

2.3.4 Two-pair Wiring


FX1N-485-BD A series programmable
RS485/422 unit *4 FX2N-485-BD FX (0N)-485ADP controller's computer link unit

R*1 R*1
SDA SDA SDA SDA

SDB SDB SDB SDB


R*1 R*1
RDA RDA RDA RDA

RDB RDB RDB RDB


LINK
SG SG SG SG
*2 FG*3 FG*3

Grounding of registance 100 or less

*1 R is the terminating resistor. Connect the terminating resistor (330) between terminals SDA
and SDB, and terminals RDA and RDB.
*2 Connect the shield of FX2N-485-BD, FX1N-485-BD using shielded twist-pair cable to ground
(100 or less).
Please adjust the grounding only to one side.
*3 Connect terminal FG to each terminal of the programmable controller main body grounded
with resistance of 100 or less. However, as for the computer link unit of the A series pro-
grammable controller, see the manual of the computer link unit.
*4 When using RS232/485 or RS232/422 adapter, please the adapter use FX-485PC-IF.

2-8
FX communication Wiring 2

2.4 Parallel Link


2.4.1 FX2N(1N)-485-BD and FX0N-485ADP
1 ) One-pair Wiring
F X 2N -485-B D
F X 0N -485A D P
2
F X 1N -485-B D
SDA SDA

SDB SDB

RDA RDA
T erm inating T erm inating
resistance registance
110 RDB RDB 110
LIN K
SG
SG
F G *1

*1 Connect terminal FG to each terminal of the programmable controller main body,


grounded with resistance of 100 or less.

2 ) Two-pair Wiring
F X 2N -485-B D
F X 0N -485A D P
F X 1N -485-B D
SDA SDA

SDB SDB

RDA RDA
T erm inating T erm inating
resistance registance
330 RDB RDB 330
LIN K
SG
SG
F G *2

*2 Connect terminal FG to each terminal of the programmable controller main body,


grounded with resistance of 100 or less.

2-9
FX communication Wiring 2

2.4.2 Only FX0N-485ADP


1 ) One-pair Wiring

F X 0N -485A D P F X 0N -485A D P

SDA SDA

SDB SDB

RDA RDA
T erm inating T erm inating
resistance registance
110 RDB RDB 110
LIN K LIN K
SG SG
FG F G *1

*1 Connect terminal FG to each terminal of the programmable controller main body,


grounded with resistance of 100 or less.

2 ) Two-pair Wiring

F X 0N -485A D P F X 0N -485A D P

SDA SDA

SDB SDB

RDA RDA
T erm inating T erm inating
resistance registance
330 RDB RDB 330
LIN K LIN K
SG SG
FG F G *2

*2 Connect terminal FG to each terminal of the programmable controller main body,


grounded with resistance of 100 or less.

2-10
FX communication Wiring 2

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


1 ) One-pair Wiring
F X 2N -485-B D F X 2N -485-B D
F X 1N -485-B D F X 1N -485-B D
SDA SDA 2
SDB SDB

RDA RDA
T erm inating T erm inating
resistance registance
110 RDB RDB 110

SG SG

2 ) Two-pair Wiring
F X 2N -485-B D F X 2N -485-B D
F X 1N -485-B D F X 1N -485-B D
SDA SDA

SDB SDB

RDA RDA
T erm inating T erm inating
resistance registance
330 RDB RDB 330

SG SG

2-11
FX communication Wiring 2

2.4.4 Only FX2-40AW

FX2-40AW FX2-40AW *1 SG Terminal of FX2-40AW connect to


SG terminal of FX or FX2C main unit.
SA SA
*2 Please connect the shield of shielded
SB SB twist pair cable with terminal to
which the programmable controller main
SG*1 SG*1 unit is grounded. Please adjust the
grounding only to one side.
*2

FX, FX2C main unit

2.4.5 FX2-40AP
FX2-40AP FX2-40AP

T R

R T

Optical glassfiber
cable
Note;
Keep optical fibers away from wire cables carrying high loads.
Including where the cables are terminated.

2-12
FX Series Programmable Controllers Specifications 3

1 Introduction

2 Wiring

3 Specifications 3

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Specifications 3
FX communication Specifications 3

3. Specifications

3.1 Specifications of Communication


Computer
link
N:N network Parallel link No protocol communication
(dedicated
protocol)
Conforming to Conforming to RS485
3
Transmission standard Conforming to RS485 and RS422 or RS232C
RS485 and RS422
RS485(RS422): Max. 500m
Transmission distance Max. 500m
RS232C: Max. 15m
1:N RS232C:1:1
Total station is
Connected the number 1:1 (N is Max. 16
Max. 8 stations
stations RS485:1:N *1
FX, FX2C, FX0N, FX1N, FX1S :
half-duplex communication
Communication method Half-duplex communication
FX2N, FX2NC*2: full-duplex
communication
Data length 7 bit / 8 bit
Parity Fixation None / Odd / Even
Stop bit 1 bit / 2bit
Baud rate (bps) 38,400 19,200 300/600/1,200/2,400/4,800/9,600/19,200
Header character
Fixation
Terminator character None / effective
Control line
Format 1 /
Protocol Format 4
None
None /
Sum check Fixation
effective
Supported programmable FX2N, FX2NC,
FX2N, FX2NC, FX1N, FX1S, FX0N, FX FX2C
controller FX1N, FX1S, FX0N

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


*2 If using FX0N-485ADP, this system is half-duplex.

3-1
FX communication Specification 3

3.2 Communication Time


3.2.1 N:N network
Communication device
Pattern 0 Pattern 1 Pattern 2
Bit device: 0 point Bit device: 32 points Bit device: 64 points
Word device: 4 points Word device: 4 points Word device: 8 points
2 18 22 34
3 26 32 50
4 33 42 66
Total station number 5 41 52 83
6 49 62 99
7 57 72 115
8 65 82 131

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

3.2.2 Parallel link

Normal Mode 70 for reciprocation + Operation cycle of master station


+ Operation cycle of slave station (ms)

High speed mode 20 for reciprocation + Operation cycle of master station


+ Operation cycle of slave station (ms)

3-2
FX communication Specifications 3

3.2.3 Computer link


Calculations to determine the approximate time until communication is complete.
1 ) Programmable controller Computer
Communication time = Number of total characters based on dedicated protocol*1
Time to send or receive one character (ms)*2
+ Programmable controllers maximum scan time (ms) 3
+ Message wait (ms)
2 ) Computer Programmable controller 3
Communication time = Number of total characters based on dedicated protocol*1
Time to send or receive one character (ms)*2
+ Programmable controllers maximum scan time (ms)
+ Message wait (ms)
*1 Please count the number of characters referring to section 7.4.1 and 7.4.2 and chapter 8.
*2 Please refer to the following expression for the method of calculating this time.
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),
this time is as follows.
Baud rate (bps) Time to send or receive one character (ms)
300 33.34
600 16.67
1200 8.34
2400 4.17
4800 2.08
9600 1.04
19200 0.52

Note;
Please refer to following table for the relation between reading word points and communication
time.
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)
Reading word points
9,600 19,200
10 0.3 s 0.2 s
32 0.4 s 0.3 s
64 0.5 s 0.4 s

3-3
FX communication Specification 3

MEMO

3-4
FX Series Programmable Controllers N:N network 4

1 Introduction

2 Wiring

3 Specifications

4 N:N network 4

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers N:N network 4
FX communication N:N network 4

4. N:N Network
For diagnostics, please refer to chapter 12.

4.1 Related Flags and Data Registers


4.1.1 Auxiliary Relays

Auxiliary relays
Response
Attribute FX0N, FX1N, FX2N, Name Description
type
FX1S FX2NC 4
N:N network Used to set N:N network
R M8038 M, L
parameter setting parameters
Communication error of When communication error is
R M504 M8183 L
master station in master station, this is ON. *1
M505 to M8184 to Communication error of When communication error is
R M, L
M511 *2 M8190 *2 slave station in slave station, this is ON. *1
When communicate to other
R M503 M8191 Data communication M, L
station, this is ON.

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


*1 The number of communication errors that have occured in each station cannot be counted in
the CPU error status, the program error status or the stop status.
*2 No. in accordance with the slave station No.
Example: FX0N, FX1SSlave station No.1 is M505, Slave station No.2 is M506,
~ Slave station No.7 is M511.
FX2N, FX2N, FX1NSlave station No.1 is M8184, Slave station No.2 is M8185,
~ Slave station No.7 is M8190.

Note;
Devices M503 to M511 in the FX0N and FX1S cannot be applied for other usage in the
user program. These devices are used by the N:N network.

4-1
FX communication N:N network 4

4.1.2 Data Registers

Auxiliary relays
Response
Attribute FX0N, FX1N, FX2N, Name Description
type
FX1S FX2NC
R D8173 Station No. Saves its own station No. M, L
Total number of slave Saves total number of
R D8174 M, L
stations slave stations
R D8175 Refresh range Saves refresh range M, L
W D8176 Station number setting Sets its own station No. M, L
Total slave station number Sets total number of
W D8177 M
setting slave stations
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
Saves current network
R D201 D8201 Current network scan time M, L
scan time
Maximum network scan Saves maximum network
R D202 D8202 M, L
time scan time
Number of communica-
Number of communication
R D203 D8203 tion error at master sta- L
error at master station
tion *1
Number of communica-
D204 to D8204 to Number of communication
R tion error at slave station M, L
D210 *2 D8210 *3 error at slave station
*1
Code of communication Code of communication
R D211 D8211 L
error at master station error at master station *1
D212 to D8212 to Code of communication Code of communication
R M, L
D218 *2 D8218 *3 error at slave station error at slave station *1
D219 to
D255
Not used For internal processing

R : Ready 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 the
CPU error status, the program error status or the stop status.
*2 No. 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 No. 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.

Note;
Devices M503-M511 and D201-D255 in the FX0N and FX1S cannot be applied for other
usage in the user program. These devices are used by the N:N network.

4-2
FX communication N:N network 4

4.2 Setting
Each settings for the N:N network become valid when the program is run or when the power of
the programmable controller is turned on.

4.2.1 Setting the Station No. (D8176)


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

Set value Description


0 Master station
Slave station No.
1 to 7
Example: 1 is slave station No.1, 2 is slave station No.2
4
4.2.2 Setting the Total Number of Slave Stations (D8177)

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-3
FX communication N:N network 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.

Refresh range
Communication Pattern 0
device Pattern 1 Pattern 2
(FX0N, FX1S, FX1N,
(FX1N, FX2N, FX2NC) (FX1N, FX2N, FX2NC)
FX2N, FX2NC)
Bit device (M) 0 point 32 points 64 points
Word device (D) 4 points 4 points 8 points

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 long as the FX0N and FX1S communi-
cation error is occurring.

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

Device No.
Station 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

4-4
FX communication N:N network 4

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

Device No.
Station No. Bit device (M) Word device (D)
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 4
No.7 M1448 to M1479 D70 to D73

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

Device No.
Station No. Bit device (M) Word device (D)
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.2.4 Setting Retry Count (D8178)


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), com-
munication error occur in the station.

4.2.5 Setting Comms Time-out (D8179)


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.

4-5
FX communication N:N network 4

4.2.6 Program Used for Setting


M8038 Station No. setting:
FNC 12 K 0 D8176 Required for master
0
MOV station (Set range: 0 to 7)
Total number of slave
FNC 12 K 2 D8177 stations: 2
MOV (Setting range: 1 to 7)
Refresh range setting:
FNC 12 K 1 D8178 Pattern 1
MOV (Set range: 1 to 2) Not required for
slave station
FNC 12 Refry count setting:
K 3 D8179 3 (3times)
MOV

FNC 12 Comms time-out setting:


K 6 D8180 6 (60ms)
MOV

Make sure to write the program above from step 0 as the N:N network parameter setting program.
This program does not require to be executed, because it becomes effective automatically when it
is programmed in this position.
Note;
Setting of the parameters for the N:N network is started at step 0 (LD M8038), and fin-
ished when any instruction or device other than the program above is processed.

4-6
FX communication N:N network 4

4.3 Example Program


4.3.1 System Configuration

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

FX 2N FX 2N

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


4
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 the out-
put 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 output
points 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 output
points 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 in
the station No.1.
The contact (M1070) status of the counter C1 is reflected on the output point Y005 in the
master station.
5 ) The data register D2 in the master station is specified as the set value of the counter C2 in
the station No.2.
The contact (M1140) status of the counter C2 is reflected on the output point Y006 in the
master station.
6 ) The value of the data register D10 in the station No.1 and the value of the data register D20
in 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 register
D20 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 register
D10 in the station No.1 are added in the station No.2, and saved to the data register D21.

4-7
FX communication N:N network 4

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 program
below.

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)

M8038 Station No. setting:


FNC 12 K 0 D8176 Required for master
0
MOV station (Set range: 0 to 7)
Total number of slave
FNC 12 K 2 D8177 stations: 2
MOV (Setting range: 1 to 7)
Refresh range setting:
FNC 12 K 1 D8178 Pattern 1
MOV (Set range: 1 to 2) Not required for
slave station
FNC 12 Refry count setting:
K 3 D8179 3 (3times)
MOV

FNC 12 Comms time-out setting:


K 5 D8180 5 (50ms)
MOV

4.3.4 Example of Error Program

Master communication error


M8183 *
Y000
Slave 1 communication error
M8184 *
Y001

Slave 2 communication error


M8185 *
Y002

Data communication
M8191
Y003

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

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

4-8
FX communication N:N network 4

4.3.5 Example of Operation Program


a ) Program of master station

RUN monitor
M8000
MOV K1X000 K1M1000 Operation 1)
Slave 1
communication error
M8184
MOV K1M1064 K1Y014 Operation 2)

Slave 2
communication error
M8185
MOV K1M1128 K1Y020 Operation 3) 4
Slave 1
communication error
M8184
MOV K 10 D 1

Contact of slave 1 C1 Operation 4)


device
M1070
Y005

Slave 2
communication error
M8185
MOV K 10 D 2

Contact of slave 2 C2 Operation 5)


device
M1140
Y006
Slave 1 Slave 2
communication communication
error error
M8184 M8185
MOV K 10 D 3 Operation 6)

MOV K 10 D 0 Operation 7), 8)

END

4-9
FX communication N:N network 4

b ) Program of slave station No.1


Counter reset
X001
RST C 1
Master
communication
error
M8183
MOV K1M1000 K1Y010 Operation 1)

MOV K1X000 K1M1064 Operation 2)


Slave 2
communication
error
M8185
MOV K1M1128 K1Y020 Operation 3)

Counter input
X000
C1
D1

C1 Operation 4)
Y005

M1070
Slave 2 Contact of
communication slave 2 C2
error device
M8185 M1140
Y006 Operation 5)

MOV K 10 D 10 Operation 6), 8)

Slave 2
communication
error
M8185
ADD D 0 D 20 D 11 Operation 7)

END

4-10
FX communication N:N network 4

c ) Program of slave station No.2

Counter reset
X001
RST C 2
Master
communication
error
M8183
MOV K1M1000 K1Y010 Operation 1)
Slave 1
communication
error
M8184
MOV K1M1064 K1Y014 Operation 2)
4

MOV K1X000 K1M1128 Operation 3)


Slave 1 Contact of
communication slave 1 C1
error device
M8184 M1070
Y005 Operation 4)

Counter input
X000
C2
D2

C2
Y006 Operation 5)

M1140

MOV K 10 D 20 Operation 6), 7)


Slave 1
communication
error
M8184
ADD D 0 D 10 D 21

END

4-11
FX communication N:N network 4

MEMO

4-12
FX Series Programmable Controllers Parallel link 5

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link 5

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Parallel link 5
FX communication Parallel link 5

5. Parallel link
Data transfer with FX2N, FX2NC, FX1N, FX, FX2C programmable controllers can be performed on a
1:1 basis for 100 auxiliary relays and 10 data registers. Data transfer with FX 1S, FX0N program-
mable controller can be performed on a 1:1 basis for 50 auxiliary relays and 10 data registers.
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. 5
M8162 High speed mode for parallel link, 2 data words read/write only.
M8070 Parallel link watchdog time (Default: 500 ms).

5-1
FX communication Parallel link 5

5.2 Mode and Link Device


5.2.1 Normal Mode (Special auxiliary relay M8162: OFF)
Master Automatic Slave
communication
M -M M -M
M -M M -M
M8000 D -D D -D M8000
M8070 M8071
D-D D-D

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


Master M800 to M899 (100 points), M400 to M449 (50 points),
Communica- Slave D490 to D499 (10 points) D230 to D239 (10 points)
tion devices Slave M900 to M999 (100 points), M450 to M499 (50 points),
Master D500 to D509 (10 points) D240 to D249 (10 points)
Communication time 70 (ms) + Scan time of master (ms) + Scan time of slave (ms)
Note;
Parallel link is possible between PLCs 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.
Group No. Series
Group 1 FX2N, FX2NC
Group 2 FX1N
Group 3 FX1S
Group 4 FX0N
Group 5 FX, FX2C

5-2
FX communication Parallel link 5

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


Master Slave
Automatic
communication
M8000 M8000
M8070 M8071
D ,D
M8162 M8162
D ,D

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


Master
D490, D491 (2 points) D230, D231 (2 points)
Communica- Slave
tion devices Slave
D500, D501 (2 points) D240, D241 (2 points)
Master
Communication time 20 (ms) + Scan time of master (ms) + Scan time of slave (ms)

Note; 5
Parallel link is possible between PLCs 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.
Group No. Series
Group 1 FX2N, FX2NC
Group 2 FX1N
Group 3 FX1S
Group 4 FX0N
Group 5 FX, FX2C

5-3
FX communication Parallel link 5

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 in
the 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 is
output to Y000 to Y007 in the master station (). The value of D10 in the slave station is set to
the timer (T0) in the master station ().
Master station Slave station
M8000 M8000
M8070 M8071

MOV K2X000 K2M800 MOV K2M800 K2Y000


M8000
M8000 CMP D490 K100 M10
ADD D0 D2 D490
M10
M8000 Y010
MOV K2M900 K2Y000 M8000
X010 MOV K2M0 K2M900
T0 X010
D500 MOV D10 D500
END END

5.3.2 High Speed Mode


When the calculation result (D0+D2) in the master station is 100 or less, Y010 in the slave station
is turned on (). The value of D10 in the slave station is set to the timer (T0) in the master station
().
Master station Slave station
M8000 M8000
M8070 M8071

M8162 M8162
M8000
M8000 CMP D490 K100 M10
ADD D0 D2 D490 M10
X010 Y010
T0 X010
D500 MOV D10 D500
END END

Note;
In the normal mode, FNC 81 PRUN instruction can be used for .
However, This instruction is only supported FX, FX2C, FX2N, FX2NC.

5-4
FX Series Programmable Controllers Communication format (D8120) 6

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120) 6

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Communication format (D8120) 6
FX communication Communication format 6

6. Communication format (D8120)


This chapter explains setting the communication between no protocol communication (RS
instruction) and computer link. For the RS instruction, refer to Section 9. For computer link, refer
to 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 programmable
controller. Set D8120 in accordance with external equipment used.
After modifying the setting of the D8120, make sure to turn off the power of the programmable
controller, 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


6.2.1 Special Auxiliary Relays
Special auxiliary relays Description
M8121 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)
On-demand word/byte changeover (computer link)
M8129
Time out evaluation flag (RS instruction)
M8161 8 bits/16 bits changeover flag (RS instruction)

( ) indicates the use application.

6.2.2 Special Data Registers


Special data registers Description
D8120 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)

( ) indicates the use application.

6-1
FX communication Communication format 6

6.3 Communication Format (D8120)


Bit Description
Name
No. 0 (bit = OFF) 1 (bit = ON)
b0 Data length 7 bit 8 bit
(b2, b1)
b1 ( 0, 0) : None
Parity
b2 ( 0, 1) : Odd
( 1, 1) : Even
b3 Stop bit 1 bit 2 bit
(b7, b6, b5, b4) (b7, b6, b5, b4)
b4
( 0, 0, 1, 1) : 300 ( 0, 1, 1, 1) : 4,800
b5 Baud
( 0, 1, 0, 0) : 600 ( 1, 0, 0, 0) : 9,600
b6 rate(bps)
( 0, 1, 0, 1) : 1,200 ( 1, 0, 0, 1) : 19,200
b7
( 0, 1, 1, 0) : 2,400
b8*1 Header None Effective (D8124) Default : STX (02H)
b9*1 Terminator None Effective (D8125) Default : ETX (03H)
(b12, b11, b10)
( 0, 0, 0) : No use <RS232C interface>
( 0, 0, 1) : Terminal mode <RS232C interface>
No ( 0, 1, 0) : Interlink mode <RS232C interface > (FX2N V2.00 or
b10 protocol more)
Control ( 0, 1, 1) : Normal mode 1 <RS232C interface>,
b11
line <RS485 (422) interface>*3
b12
( 1, 0, 1) : Normal mode 2 <RS232C interface> (FX, FX2C only)
(b12, b11, b10)
Computer
( 0, 0, 0) : RS485 (422) interface
link
( 0, 1, 0) : RS232C interface
b13*2 Sum check Sum check code is not added Sum check code is added automatically
b14*2 Protocol No protocol Dedicated protocol
Transmission
b15*2 control Protocol format 1 Protocol format 4
protocol

*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 RS485 (422) interface, make setting controll line the same as this. But control line
of communication is the same as when not using control line operation.
This connection (RS485) is supported in the FX0N, FX1S, FX1N, FX2N, FX2NC series.

6-2
FX communication Communication format 6

6.4 Example of setting program


When setting the contents shown on the left, perform programming as follows.

M8002 Data length 7 bits


MOV H0C8E D8120
Parity Even
b15 b0
Stop bit 2 bits
D8120 = 0000 1100 1000 1110
0 C 8 E Baud rate 9600 bps
Protocol No protocol
Header No used
Terminator No used
Control line Normal mode 1

6-3
FX communication Communication format 6

MEMO

6-4
FX Series Programmable Controllers Computer link 7

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link 7

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Computer link 7
FX communication Computer link 7

7. Computer Link
This chapter explains the details and methods of specifying dedicated protocol used for linking of
the 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 computer
link unit of the A series programmable controller).
In this chapter FX2N-232-BD, FX1N-232-BD, FX 0N-232ADP and FX-232ADP refer to 232ADP,
FX2N-485-BD, FX1N-485-BD, FX0N -485ADP and FX-485ADP refer to 485ADP, FX-485PC-IF
refer to 485PC-IF.
When interface of programmable controller using RS232, please after read 232ADP instead of
485ADP.

7.1 Data Flow by Link


Shown below are drawings of data flow for reading, writing, and status control of the programma-
ble controller.
1 ) The computer reads data from programmable controller.
RS232C 485PC-IF RS485 485ADP Programmable controller
Computer
(2)Command (3) (4)
(9)Various data (8) (7)
OS* OS* Program
(12)Response (13) (14)
7
Request

Device memory Data(6) (5)Read


(10) (11) information (Read)
Signal Device
(1) Data Programmable
converting memory,etc.
Comn. controller CPU
interface
Prog. information (Read)

2 ) The computer sends data to programmable controller.


RS232C 485PC-IF RS485 485ADP
Computer (2)Command, Programmable controller
data,etc. (3) (4)
OS* OS* Program
(8)Response (7) (6)
Request

Device memory (5)Write


information (Write) Device
(1) Data Programmable memory,etc.
Comn. controller CPU
Prog. information (Write)

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

7-1
FX communication Computer link 7

3 ) Programmable controller sends data to the computer.

Computer RS232C 485PC-IF RS485 485ADP Programmable controller


(4)
(6) Data (5) Data
OS* OS* Program
On-demand data
( 7) Data (3) (2) Read (1) Send
Write request+
Data Device
memory,etc. data write
Comn.
Prog.

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

7-2
FX communication Computer link 7

7.2 Information Needed Before Programming


7.2.1 Programmable Controller Operation
The operation and scan time of programmable controller by the computer link are as follows.
While the programmable controller is running, access requests to the programmable controller
from the computer are processed on every END processing. The processing of Send or Receive
data is performed using interrupts.
Therefore, during the processing of Send or Receive, the scan time is extended; typically by
about 10 %. The scan time can be monitored using the special data registers D8010 to D8012 of
the programmable controller.
Note;
- These are in units of 0.1 ms

7.2.2 Notes of Computer


1 ) Conditions under which the transmission sequence is initialized.
The transmission sequence of the programmable controller is initialized during the following
conditions.
- 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)
7
2 ) Occurrence of framing error at the computer
When a commercial RS485 interface is used at the computer, if nothing is transmitted from
the programmable controller to the computer at the interface, a framing error may occur at
the computer.
Accordingly, read and skip the data at the computer until any one of STX, ACK, and NAK is
transmitted from the programmable controller.
3 ) NAK response from programmable controller
NAK response from the programmable controller to the computer is done when an error is
detected.
4 ) Command transmission from computer
When sending a command from the computer to the programmable controller using the ded-
icated protocol, only send the command after a gap of approximately two programmable
controller scans from the time the data communications required by the previous command
are completed.

Caution;
When using RS485 wiring (one pair, see section 2.3.3) remember to take account of/or
ignore the echo of the commands sent from the computer.

7-3
FX communication Computer link 7

7.3 How to Read a Control Protocol Diagram


1 ) When the computer reads data from the programmable controller
(computer programmable controller)

A C

E A
Computer N Data C Data
Q K
S
Programmable T Data
controller X

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, after
the ENQ.)
2 ) When writing data from the computer into the programmable controller
(computer programmable controller)

E
Computer N Data
Q
Programmable A
C Data
controller K

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, after
the ENQ.)

7-4
FX communication Computer link 7

7.4 Basic Formats of Dedicated Protocol


There are two formats for the dedicated protocol; which may be selected by setting special data
register D8120(see chapter 6).
The difference between the 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 for
A series programmable controller.)

Basic format of transmitted data.

Control code

Station No.

PC No.

Command

Message wait

Character 7

( Sum check code *1 )

( Control code CR/LF *2 )

*1 Whether or not to add sum check code can be selected using the communication format spe-
cial data register D8120.
*2 Whether or not to add terminating CR + LF codes is determined by the protocol selected.

7-5
FX communication Computer link 7

7.4.1 Control Protocol Format 1

Description Control protocol

PC No.
N A K

Station
No.
Transmission sequence

*
or

PC No.

Command

wait time
Message

PC No.
Character
E N Q

A C K
Station

Station
area A

check
code

Sum
No.

No.
To read data
Computer
from the pro-
grammable Programmable

PC No.

Character
Station
S T X

E T X
area B

check
code

Sum
controller to

No.
controller
the computer

or
*

PC No.
N A K

Station

Error
code
No.

*
No.
Station
PC No.

Command

wait time
Message

Character
E N Q

area C

check
code

Sum

To write data Computer


from the com- Programmable
No.
Station
PC No.

Transmission sequence
ACK

puter to the controller


programma-
ble controller
or
No.
Station
PC No.

Error code
NAK

1 ) Sum check code is used when the sum check flag is set Yes (b13=1 in special data register
D8120), 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 the aster-
Remarks isked area.
3 ) In the diagram, the contents of character area A, character area B, and character area C
depend 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.

7-6
FX communication Computer link 7

7.4.2 Control Protocol Format 4

Description Control protocol

L
PC No.
C
N A K

Station
No.
Transmission sequence

R
F
*
or

L
PC No.

Command

wait time
Message

PC No.
C
Character
E N Q

A C K
To read data
Station

Station
area A

check
code

Sum
No.

No.
from the pro-

R
F

F
grammable Computer
controller to Programmable

L
PC No.

C
Character
Station
S T X

E T X
area B

check
code

Sum
No.
the computer controller

R
F
or
*

L
PC No.

Error code

C
N A K

Station
No.

R
F
*
PC No.

Command

wait time
Message

code
check
Sum
C
L
Character
E N Q

Station

area C
No.

R
F

To write data Computer


from the com- Programmable 7
PC No.
C
L

Transmission sequence
Station
ACK

puter to the
No.

controller
programma-
R
F

ble controller
or
PC No.

C
L
Station
NAK

Error
code
No.

R
F

1 ) Sum check code is used when the sum check flag is set Yes (b13=1 in special data register
D8120), 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 the aster-
Remarks isked area.
3 ) In the diagram, the contents of character area A, character area B, and character area C
depend 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.

7-7
FX communication Computer link 7

7.4.3 Control Protocol Parts Explained


This is to explain the content of data set in each control procedure.
1 ) Control codes
The control codes are listed below.

Code Code
Signal Description Signal Description
(Hexadecimal) (Hexadecimal)
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

a ) The programmable controller initializes the transmission sequence when receiving any
one of ENQ, ACK, NAK, and starts.
b ) When EOT, or CL code is received as follows, the programmable controller initializes the
transmission sequence. At this time, no response is made from the programmable con-
troller.

Format 1 Format 4

E E C L
O O
T T R F
or or
C C C L

Computer L
Computer L R F
Programmable Programmable
controller controller

7-8
FX communication Computer link 7

2 ) Station number
The station number is the number provided at the programmable controller in order to deter-
mine which programmable controller the computer accesses. In the FX series programmable
controller, the station number is set by the special data register D8121(special D8121 herein-
after). The setting range is 00H to 0FH. In the case of FX0N series turn on M8120 when using
the special D8121. For the setting method of an A series programmable controller, see the A
series manual.

Computer

FX FX FX FX
series series series series

485PC-IF 485ADP 485ADP 485ADP 485ADP


Station No.0 Station No.1 Station No.2 Station No.15

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

M8002
MOV H0 D8121

Notes
7
1 ) 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 spec-
ified range(00H to 0FH). For example, setting in a random order or skipping numbers is
acceptable.
3 ) PC number
The PC number is the number identifying the programmable controller CPU on the A
series MELSECNET(II) or MELSECNET/B.
Accordingly, the PC number for an FX series programmable controller is FFH, and is rep-
resented as two ASCII characters; i.e. FF. When using the on-demand function the PC
number is automatically converted to FFH by the programmable controller.
For the PC number of programmable controller CPU on the MELSECNET(II), MELSEC-
NET/B see the computer link manual for A series programmable controllers.
4 ) Command
Used to specify the operation required, e.g. read, write, etc. Commands are defined using
two ASCII characters.
For a description of the available commands, see section 7.7.1.

7-9
FX communication Computer link 7

5 ) Message wait
This 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 controller
sends data after receiving a message from the computer. Set the wait time according to the
computer specifications.
The message wait time may be set between 0 to 150 ms in 10 ms increments. The value is
set 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 (7
or more). If scan time of programmable controller is 70 ms or more on the network, message
wait time need to set maximum scan time or more.
Example: Setting the message wait time
Message wait (100 ms)

"A"
Computer
Programmable
controller

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

6 ) Sum check code


The sum check code is used to verify that the data in a message has not been corrupted. It is
calculated by adding (summing) the hexadecimal values of the ASCII character codes in the
sum 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 the mes-
sage. (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 sum
check 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, PC number FF, command BR (device memory
batch read), message wait time 30 ms, and data ABCD in format 1, the sum check code is calcu-
lated as follows.

E Station PC No. Command Message Character area Sum


N No. wait time check
Q B R code
0 0 F F 3 A B C D B D
Computer
05H 30H 30H 46H 46H 42H 52H 33H 41H 42H 43H 44H 42H 44H
Programmable E Station PC No.
controller N No.
Q
0 0 F F
30H+30H+46H+46H+42H+52H+33H+41H+42H 02H 30H 30H 46H 46H
+43H+44H=2BDH 30ms
(Message wait time)

7-10
FX communication Computer link 7

7.4.4 Time- out Check Time


The time out check time refers to the duration after termination of receive (final character
received) of a failed transmission from the computer to the programmable controller, until the
send sequence is initialized.
This check time is specified as follows depending on the model and version of the programmable
controller.
To set the time-out check time as 60 ms:
M8002
MOV K6 D8129

Other function information:


In the case of FX0N series, turn on M8120 when using the special D8129.

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.

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 the 7
baud rate (transmission speed) in use. When 1 character = 12 bits, the minimum setting of time-
out check time is as follows.

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)

7-11
FX communication Computer link 7

7.5 Communication Timing Chart


7.5.1 Reading Data from Programmable controller

ENQ

ACK
Computer

Wait(TW) T3 T4 T5

Interface

STX
More than two-scan
Read process delay is needed.

This time becomes 0 when the message wait time is not set or
when the wait time is less than the processing time needed by
Programmable the programmable controller.
controller T0 T1 T2

Programmable
controller program
END Step 0 END Step 0 END Step 0 END

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

7.5.2 Writing Data to Programmable Controller


ENQ

Computer

Wait(TW) T3

Interface

Writing data
Write process

This time becomes 0 when the message wait time is not set or
when the wait time is less than the processing time needed by
Programmable the programmable controller.
controller T0 T1 T2

Programmable
controller program
END Step 0 END Step 0 END Step 0 END

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

7-12
FX communication Computer link 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
T0, T3, T5 = 1/baud rate number of bits in 1 character (1 + 7(8) + 0(1) + 1(2))
number of characters

Start bit Stop bit (1 or 2)


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

T1 = max. 1 scan time (during RUN, message processing is done at END processing, a
maximum 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:N
system configuration, this time need to set Time-out timer value (D8129) + 1 scan
time or more.
TW = set time when message wait is set.
7
2 ) When writing data from the computer to the programmable controller
Communication time = T0 + (T1 + T2 or TW, whichever is longer) + T3
T0, T3 = 1/baud rate number of bits in 1 character (1 + 7(8) + 0(1) + 1(2))
number of characters

Start bit Stop bit (1 or 2)


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

T1 = max. 1 scan time (during RUN, message processing is done at END processing, a
maximum 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.

7-13
FX communication Computer link 7

7.6 Character Area Data Transmission


The data shown in the following examples are samples of the data used in character area B
when reading 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 an increas-
ing 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

Head device No.of Data


device
M 0 0 1 6 points
0 5 1 0 1 0 1

05H 30H 30H 46H 46H 42H 52H 05H 30H 30H 46H 46H

Indicating M14 is ON
Indicating M13 is OFF
Indicating M12 is ON

Indicating M11 is OFF


Indicating M10 is ON

2 ) Word units (units of 16 points)


When handling bit device memory in word units, each word (16 bits, highest bit being first) is
expressed as 4 hexadecimal digits (each of 4 bits) starting with the higher digit. Each digit
being represented by the appropriate ASCII character.
Example: When transmitting the on/off status of 32 points from M16
The number of devices is "02" because word units are used.

Head device No.of Data Data


device
points
M 0 0 6 0 2 A B 1 2 3 4 C D
4DH 30H 30H 31H 36H 30H 32H 41H 42H 31H 32H 33H 34H 43H 44H

A B 1 2 3 4 C D

B15 B14 B13 B12 B11 B10 B9 B8 B7 B6 B5 B4 B3 B2 B1 B0 B15 B14 B13 B12 B11 B10 B9 B8 B7 B6 B5 B4 B3 B2 B1 B0
1 0 1 0 1 0 1 1 0 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0 1 1 0 0 1 1 0 1

M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32

Lowest bit
Head device:
of 2nd word
Lowest bit of 1st word
1:Represents ON
0:Represents OFF

7-14
FX communication Computer link 7

7.6.2 Word Device Memory


When handling word device memory, each word is expressed as 4 hexadecimal digits (each of 4
bits) starting with the higher digit. Each digit being represented by the appropriate ASCII charac-
ter.
Example 1) When showing the contents of data registers D350, D351

Head device No.of Data Data


device
points
D 0 3 5 0 0 2 5 6 A B 1 7 0 F
44H 30H 33H 35H 30H 30H 32H 35H 36H 41H 42H 31H 37H 30H 46H

5 6 A B 1 7 0 F

B15 B14 B13 B12 B11 B10 B9 B8 B7 B6 B5 B4 B3 B2 B1 B0 B15 B14 B13 B12 B11 B10 B9 B8 B7 B6 B5 B4 B3 B2 B1 B0
0 1 0 1 0 1 1 0 1 0 1 0 1 0 1 1 0 0 0 1 0 1 1 1 0 0 0 0 1 1 1 1

Contents of D350 is 56ABH Contents of D350 is 56ABH


(22187 in decimal). (22187 in decimal).

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

No.of
Head device
device
Data Data
7
points
C N 2 0 0 0 1 1 2 3 4 5 6 7 8
44H 30H 33H 35H 30H 30H 31H 31H 32H 33H 34H 35H 36H 37H 38H

1 2 3 4 5 6 7 8

B15 B14 B13 B12 B11 B10 B9 B8 B7 B6 B5 B4 B3 B2 B1 B0 B15 B14 B13 B12 B11 B10 B9 B8 B7 B6 B5 B4 B3 B2 B1 B0

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

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

* The device code of C200 is CN200.

7-15
FX communication Computer link 7

7.7 Commands and Device Ranges


7.7.1 Commands

Maximum No. of units


Command
per communication
Description FX, FX2C
ASCII FX0N,
Symbol , FX1N, FX2N,
code FX1S
FX2NC
Bit Reads a group of bit devices (X, Y, M,
BR 42H, 52H 54 points 256 points
unit S, T, C), result is in units of 1 device.
Batch Reads a group of bit devices (X, Y, M, 13 words, 32 words,
read Word S), result is in units of 16 devices. 208 points 512 points
WR 57H, 52H
unit Reads a group of word devices (D, T,
13 points 64 points
C), result is in units of 1 device.
Bit Writes a group of bit devices (X, Y, M,
BW 42H, 57H 46 points 160 points
Device memory

unit S, T, C), data is in units of 1 device.


Batch Writes a group of bit devices (X, Y, M, 10 words, 10 words
write Word S), data is in units of 16 devices. 160 points 160 points
WW 57H, 57H
unit Writes a group of word devices (D, T,
11 points 64 points
C), data is in units of 1 device.
Set/reset individual bit devices (X, Y,
Bit
BT 42H, 54H M, S, T, C) selectively in units of 1 10 points 20 points
unit
device.
Test
(select Set/reset bit devices (X, Y, M, S) 6 words, 10 words,
write) Word selectively in units of 16 devices. 96 points 160 points
WT 57H, 54H
unit Write word devices (D, T, C*)
6 points 10 points
selectively in units of 1 device.
Remote run RR 52H, 52H Remote run/stop request to
PC Remote stop RS 52H, 53H programmable controller.
PC type read PC 50H, 43H PC type name(code) is read.
Set/reset the global flag (M8126 for
Global GW 47H, 57H FX series) to all connected 1 point 1 point
programmable controllers.
Send request from programmable
Maximum Maximum
On-demand controller. Possible, however, only in
13 words 64 words
1:1 system configuration.
Characters received from the
25 254
Loopback test TT 54H, 54H computer are directly sent back to the
characters characters
computer.

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

7-16
FX communication Computer link 7

7.7.2 Device specification ranges


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

Device specification characters Usable


command
Device Decimal/octal
FX2N, expression BR, WR,
FX0N FX1S FX, FX2C FX1N BW, WW,
FX2NC BT WT
X0000 X0000 X0000 X0000 X0000
Inputs (X)
X0177 X0017 X0337 X0177 X0267
Octal
Y0000 Y0000 Y0000 Y0000 Y0000
Outputs (Y)
Y0177 Y0015 Y0337 Y0177 Y0267
M0000

Auxiliary relays (M) M0000M0511 M0000M1535
M3071

States (S) S0000S0127 S0000S0999
Special auxiliary relays (M) M8000M8254 M8000M8255 Decimal
Timer contacts (T) TS000TS063 TS000TS255
CS000CS031
Counter contacts (C) CS000CS255
CS235CS254
In FX series, the timer coil (TC) and counter coil (CC) are not supported.
7
2 ) Word devices
Usable
Device specification characters command
Decimal/
Device octal BR,
FX1N, FX2N, expression BW, WR, WT
FX0N FX1S FX, FX2C
FX2NC BT WW
Timer current value (T) TN000TN063 TN000TN255
CN000CN031
Counter current value(C) CN000CN255 *
CN235CN254
Data registers (D) D0000D0255 D0000D0999 D0000D7999 Decimal
File registers (D) D1000D2499 D1000D2999

RAM file registers (D) D6000D7999
Special data registers (D) D8000D8255 D8000D8255
* Only CN000 to CN199 can be used.
(C200 to C255 of 32 bit counter or high speed counter cannot be used.)

Notes
1 ) 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 in
the programmable controller. Accordingly, for details of special auxiliary relays and
special data registers, see the programmable controller manual.

7-17
FX communication Computer link 7

7.8 Example Computer Program for Loopback Test


This is an example of a BASIC program for communication of the computer link using a com-
puter, programmable controller 485PC-IF, and 485ADP. (N88BASIC of Nippon Electric Corpora-
tion is used.)
Pleas see loopback test command see section 8.11.
1 ) Setting of transmission specification

Item Description
Communication Half-duplex communication
method method
Synchronizing Start-stop synchronization
method method
Baud rate 9600 bps
4
Start bit 1 bit
Data format

8
Data length 7 bit FX series
Personal 485 5
programmabl
Parity bit None computer PC-IF A
e controller
D
Stop bit 1 bit
P
Sum check Sum check is used
Station No. Station No.0
Exclusive protocol
Format 1
format

According to the above transmission specification, the transmission specification and trans-
mission procedure of the programmable controller are set as follows.
D8120 = H6080
D8121 = H0000 For setting and details, see chapter 6, and section 7.4.
D8129 = K0

2 ) Program example
10 T0 = 3000 : Reception wait counter (adjusted depending on computer speed)
20 STCNT = 14 : Normal data length
30 NACNT = 7 : Data length of error code (NAK statement)
40 ERFLG = 0
50 ENQ$ = CHR$(5) Transmission data
60 STX$ = CHR$(2)
70 ETX$ = CHR$(3) 00 FF TT 2 04 ABCD 34
80 NAK$ = CHR$(&H15)
: Data transmission
Station No.
PC No.
Command
Data wait
Number of characters

Character

Sum check code

90 *DATASEND
100 CLOSE #1
110 OPENCOM1:AS#1
120 SENDDATA$ = 00FFTT204ABCD34 : Transmission data
130 PRINT #1, ENQ$; SENDDATA$;
140 *REC0: Reception of first character
150 RVCNT = 1
160 GOSUB *RECWAIT
170 IF ERFLG = 99 THEN GOTO ERRORFIN1
180 BUF$ = RCV$

7-18
FX communication Computer link 7

190 HED$ = LEFT$(BUF$.1)


200 IF HED$ = STX$ OR HED$ = NAK$ THEN GOTO *REC1 ELSE GOTO *REC0
210 *REC1 : Reception of remaining data
220 IF HED$ = STX$ THEN RVCNT = STCNT-1
230 IF HED$ = NAK$ THEN RVCNT = NACNT-1
240 GOSUB *RECWAIT
250 IF ERFLG = 99 THEN GOTO *ERRORFIN1
260 BUF$ = BUF$ + RCV$
270 *PRINTRDATA : Display of received data
280 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 370
340 IF PRT2$ = 3 THEN PRINT ;03;ETX :GOTO 370
350 IF PRT2$ = 15 THEN PRINT ;15;NAK :GOTO 370
360 PRINT ;PRT2$; CHR$(&H22);PRT1$;CHR$(&H22)
370 NEXT I
380 IF HED$ = NAK$ THEN GOTO *ERROROFIN2
390 *DATACHECK : Check of received data
400 DDATA$ = STX$ + 00FF04ABCD + ETX$ + 5D : Normal data
410 FOR J=1 TO LEN(BUF$)
420 RDATA$ = MID$(BUF$,J,1)
430 ODATA$ = MID$(DDTA$,J,1) 7
440 IF RDATA$ <> ODATA$ THEN GOTO *ERRORFIN3
450 NEXT J
460 PRINT Received data is normal
470 PRINT Loopback test complete :GOTO *FIN
480 *ERRORFIN1
490 PRINT Data is not received at all or data content is insufficient.
500 GOTO *FIN
510 *ERRORFIN2
520 ERRORCODE$ = MID$(BUF$,6,2)
530 PRINT Error code ;ERRORCODE$; H is received.
540 GOTO *FIN
550 *ERRORFIN3
560 PRINT Received data is abnormal.(;J;-th character)
570 *FIN
580 CLOSE #1
590 END
600 *RECWAIT : Wait for receive
610 FOR I=1 TO T0
620 RCV$ =
630 IF LOC(1) => RVCNT THEN GOTO *BUFIN
640 NEXT
650 IF RCV$ = THEN ERFLG=99
660 RETURN
670 *BUFIN : Reading of received data
680 RCV$ = INPUT$(RVCNT,#1)
690 RETURN

7-19
FX communication Computer link 7

3 ) Operation
a ) 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 com-
puter.
d ) The computer compares the data received from the programmable controller and the orig-
inal 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 is Check again the writing, station No., transmission
insufficient. specification, and transmission protocol.
Error code 00H is received. Refer to error code list in chapter 12.
Received character is abnormal.
Check for faulty writing, observing writing cautions.
(0-th character)

7-20
FX Series Programmable Controllers Commands 8

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link) 8

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Commands 8
FX communication Commands 8

8. Commands
This chapter describes the structure and gives examples for each command of the dedicate pro-
tocol.
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
Bit devices specified in units of 16 points, and set/reset (forced on/off), or word
WT 8.6
devices specified in units of 1 point, and data written.
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-1
FX communication Commands 8

8.1 Batch Read of Bit Device (BR command)


1 ) Command specification
Protocol format 1 is shown.

Betch read command (bits)


No. Character area A
Station

PC No.

wait time
Message

code
Sum check

No.
Station

PC No.
Head device Number of
"0" (30H) indicates OFF.
E N Q

A C K
devices

B R
"1" (31H) indicates ON.
(5 characters) (2 characters,
Computer hexadecimal)

Programmable

No.
Station

PC No.

code
Sum check
Data of

S T X

E T X
controller Specifies the range of the
specified
devices to be read. devices

Character area B

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 number, number of devices, and sum check code are
expressed in hexadecimal.

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

E A
N 0 5 F F B R A X 0 0 4 0 0 5 4 7 The sum check is calculated C 0 5 F F
Q over this range K
Computer 05H 30H 35H 46H 46H 42H 52H 41H 58H 30H 30H 34H 30H 30H 35H 34H 37H 06H 30H 35H 46H 46H

Programmable The sum check is calculated S E


controller T 0 5 F F 0 1 1 0 1 T 0 5
over this range X X
02H 30H 35H 46H 46H 30H 31H 31H 30H 31H 03H 30H 35H

Indicating X044 is ON
Indicating X043 is OFF
Indicating X042 is ON
Indicating X041 is ON
Indicating X040 is OFF
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-2
FX communication Commands 8

8.2 Batch Read of Word Device (WR command)


1 ) Command specification
Protocol format 1 is shown.
One word device requires
Betch read command (words) Character area A
four hexadecimal digits.
Therefore,one word is
No.
Station

PC No.

code
Sum check

No.
Station

PC No.
Head device Number of

Message
wait time

A C K
E N Q

devices

W R
expressed using four
(5 characters) (2 characters, characters.
Computer hexadecimal)

Programmable

No.
Station

PC No.

code
Sum check
Data of

S T X

E T X
controller Specifies the range of the
specified
devices to be read. devices

Character area B
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 number, number of devices, and sum check code are
expressed in hexadecimal.

2 ) Command examples
a ) Example 1
8
To read 32 points of data from X040 to X077 at station No.5 (with message wait time set
to 100 ms).

E A
N 0 5 F F W R 0 X 0 0 4 0 0 2 4 8 The sum check is calculated C 0 5 F F
Q over this range K
Computer 05H 30H 35H 46H 46H 57H 52H 30H 58H 30H 30H 34H 30H 30H 32H 34H 38H 06H 30H 35H 46H 46H
Programmable S E
controller The sum check is calculated T 0 5 F F 1 2 3 4 A B C D T 0 8
over this range X X
02H 30H 35H 46H 46H 31H 32H 33H 34H 41H 42H 43H 44H 03H 30H 38H

1 2 3 4 A B C D

0 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0 1 0 1 0 1 0 1 1 1 1 0 0 1 1 0 1
X X X X X X X X X X X X X X X X X X
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
5 5 5 5 4 4 4 4 4 7 7 7 7 6 6 6 6 6
7 2 1 0 7 3 2 1 0 7 2 1 0 7 3 2 1 0
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-3
FX communication Commands 8

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

E A
N 0 5 F F W R 0 T N 1 2 3 0 2 6 4 The sum check is calculated over C 0 5 F F
Q this range K
Computer 05H 30H 35H 46H 46H 57H 52H 30H 54H 4EH 31H 32H 33H 30H 32H 36H 34H 06H 30H 35H 46H 46H
Programmable S E
The sum check is calculated
controller T 0 5 F F 7 B C 9 1 2 3 4 T B 3
over this range X X
02H 30H 35H 46H 46H 37H 42H 43H 39H 31H 32H 33H 34H 03H 42H 33H

Present value of T123: 7BC9H(hexadecimal): indicates 31689 in decimal.


Present value of T124: 1234H(hexadecimal): indicates 4660 in decimal.

8-4
FX communication Commands 8

8.3 Batch Write of Bit Device (BW command)


1 ) Command specification
Protocol format 1 is shown
Betch write command (bits) Character area A
No.
Station

PC No.

code
Sum check
Head device Number of

Message
wait time
Data of
E N Q

devices

B W
the
(5 characters) (2 characters, specified
Computer hexadecimal) devices

Programmable

No.
Station

PC No.
S T X
controller 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 number, number of devices, and sum check code are
expressed in hexadecimal.

2 ) Command example
To write data into five points from M903 to M907 at station No.0 (with message wait time set
to 0 ms).
The sum check is calculated over this range

E
N 0 0
Q
F F B W 0 M 0 9 0 3 0 5 0 1 1 0 1 2 6 8
Computer 05H 30H 30H 46H 46H 42H 57H 30H 4DH 30H 39H 30H 33H 30H 35H 30H 31H 31H 30H 31H 32H 36H

Programmable A
Specifies to turn OFF M903
contoroller C 0 0 F F
Specifies to turn ON M904 K
Specifies to turn ON M905 06H 30H 30H 46H 46H
Specifies to turn OFF M906
Specifies to turn ON M907

8-5
FX communication Commands 8

8.4 Batch Write of Word Device (WW command)


1 ) Command specification
Protocol format 1 is shown

Betch write Command (words) Character area C


No.
Station

PC No.

code
Sum check
Head device Number of

Message
wait time
Data of
E N Q

devices

B R
the
specified
(5 characters) (2 characters, devices
Computer hexadecimal)

Programmable

No.
Station

PC No.
S T X
controller Specifies the range of devices to be read.
One word device requires four hexadecimal digits.
Therefore,one word is expressed using four
characters.
Notes
Specify the range and number of devices (16 bit words) so as to satisfy the following
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.
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.
2 ) Specification examples
a ) 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 0 0 F F WW 0 M 0 6 4 0 0 2 2 3 4 7 A B 9 6 0 5
Q
Computer 05H 30H 30H 46H 46H 57H 57H 30H 4DH 30H 36H 34H 30H 30H 32H 32H 33H 34H 37H 41H 42H 39H 36H 30H 35H
Programmable The sum check is calculated A
controller over this range C 0 5 F F
K
06H 30H 30H 46H 46H
1 2 3 7 A B 9 6

0 0 1 0 0 0 1 1 0 1 0 0 0 1 1 1 1 0 1 0 1 0 1 1 1 0 0 1 0 1 1 0
M M M M M M M M M M M M M M
6 6 6 6 6 6 6 6 6 6 6 6 6 6
5 5 5 4 4 4 4 7 7 6 5 5 5 5
5 4 3 3 2 1 0 1 0 9 9 8 7 6

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-6
FX communication Commands 8

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

E
N 0 0 F F WW 0 D 0 0 0 0 0 2 1 2 3 4 A C D 7 F 9
Q
Computer 05H 30H 30H 46H 46H 57H 57H 30H 44H 30H 30H 30H 30H 30H 32H 31H 32H 33H 34H 41H 43H 44H 37H 46H 39H
Programmable A
controller C 0 5 F F
The sum check is calculated over this range K
06H 30H 30H 46H 46H
1234H(hexadecimal) to D0: indicates to write 4660 in decimal.
ACD7H(hexadecimal) to D1: indicates to write -21289 in decimal.

8-7
FX communication Commands 8

8.5 Test of Bit Device (BT command)


1 ) Command specification
Protocol format 1 is shown
Test command
(selective write,bits) Character area C

code
Sum check
No.
Station

PC No.

Set/reset

Set/reset
Number of Device Device

Message
wait time
E N Q

devices

B T
(2 characters, (5 characters) (5 characters)
Computer hexadecimal)

Programmable

No.
Station

PC No.
A C K
1 character
controller "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 number, number of devices, and sum check code are
expressed in hexadecimal.

2 ) Specification example
To set ON M50, OFF S100, and ON Y001 at station No.5 (with message wait time set to 0
ms).
The sum check is calculated over this range

E
N 0 5 F F B T 0 0 3 M 0 0 5 0 1 S 0 1 0 0 0 Y 0 0 0 1 1 E C
Q
Computer 05H 30H 35H 46H 46H 42H 54H 30H 30H 33H 4DH 30H 30H 35H 30H 31H 53H 30H 31H 30H 30H 30H 59H 30H 30H 30H 31H 31H 45H 43H
Programmable A
controller C 0 5 F F
Set (ON) Reset (OFF) Set (ON) K
06H 30H 35H 46H 46H

8-8
FX communication Commands 8

8.6 Test of Word Device (WT command)


1 ) Command specification
Protocol format 1 is shown.
Test command
(selective write,word) Character area C

code
Sum check
No.
Station

PC No.

Number of Device Device Device Device

Message
wait time
E N Q

devices
W T

(2 characters, (5 characters) (4 characters) (5 characters) (4 characters)


Computer hexadecimal)

Programmable

No.
Station

PC No.
A C K
controller When specifying bit One word device requires four
devices,specify the hexadecimal digits.
Head device. Therefore,one word is expressed using
four characters.

Notes
Specify the range and number of devices (16 bit words) so as to satisfy the following
conditions.
- 1 number of devices 10 (6 for FX0N)(one unit is 16 points for bit devices)
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.
C200 to C255 (CN200 to CN255) which are 32-bit devices cannot be handled in this
command.

2 ) Specification example
To changing the present value of D500 to 1234H, bits Y100 to Y117 to BCA9H, and the
present value of C100 to 100 at station No.5 (with message wait time set to 0 ms). 8
The sum check is calculated over this range

E
N 0 5 F F WT 0 0 3 D 0 5 0 0 1 2 3 4 Y 0 1 0 0 B C A 9 C N 1 0 0 0 0 6 4 0 7
Q
Computer 05H 30H 35H 46H 46H 57H 54H 30H 30H 33H 44H 30H 35H 30H 30H 31H 32H 33H 34H 59H 30H 31H 30H 30H 42H 43H 41H 39H 43H 4EH 31H 30H 30H 30H 30H 36H 34H 30H 37H
Programmable A
controller C 0 5 F F
B C A 9 K
06H 30H 30H 46H 46H

Indicates to change the 1 0 1 1 1 1 0 0 1 0 1 0 1 0 0 1 Indicates to change the


contents of D500 to present value of C100 to
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 64H or 100 in decimal.
1234H or 4660 in
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
decimal.
1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Each bit 0/1 indicates reset (OFF) or set (ON) respectivly.

8-9
FX communication Commands 8

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 forced
run mode, and the special auxiliary relays M8035, M8036, M8037 are controlled as follows.
Remote RUN
When remote RUN (RR command) is requested, M8035 and M8036 are set ON at the pro-
grammable controller, and forced RUN mode becomes active; the programmable controller
switching to RUN.
However, when remote run is executed while the programmable controller is running (forced
or otherwise), the state is not changed, and the remote error code (18H) is returned to the
computer.
Remote STOP
When remote STOP (RS command) is requested, M8037 is set ON at the programmable
controller. This in turn resets M8035, M8036 and M8037 to OFF and forced RUN mode is
disabled; the programmable controller switching to STOP.
However, when remote STOP is executes while the programmable controller is not in forced
RUN mode, the state is not changed, and the remote error code (18H) is returned to the
computer.

Remote stop

NO
Forced run mode

YES
Special auxiliary relay Remote error code (18H) is returned to
M8037 is ON computer, and the state of programmable
controller is not changed.

Special auxiliary relays


M8035, M8036, M8037
are OFF

Programmable
controller is stopped.

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 at
STOP.
Remote RUN
The programmable controller should be stopped.
Remote STOP
The programmable controller should be in forced run mode.
Notes
Forced RUN mode is not restored after a power failure. When the programmable con-
troller is in forced RUN mode, if the power source is turned off and on, the special aux-
iliary relays M8035, M8036, M8037 are all reset to OFF, and the programmable
controller remains in STOP.

8-10
FX communication Commands 8

8.7.3 Control Specification and Examples of Remote RUN/STOP


1 ) Control specification
Protocol format 1 is shown.
Programmable controller remote run command: "RR"
Programmable controller remote stop command: "RS"

No.
Station

PC No.

wait time
Message

code
Sum check
E N Q
RR
or
RS
Computer
Programmable

No.
Station

PC No.
A C K
controller

Notes
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.

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

The sum check is


calculated over
this range

E
N 0 5 F F R R 0 C 5
Q
Computer
Programmable
05H 30H 35H 46H 46H 52H 52H 30H 43H 35H
8
A
controller C 0 5 F F
K
06H 30H 35H 46H 46H

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

The sum check is


calculated over
this range

E
N 0 0 F F R S 0 C 1
Q
Computer 05H 30H 30H 46H 46H 52H 53H 30H 43H 31H
Programmable A
controller C 0 0 F F
K
06H 30H 30H 46H 46H

8-11
FX communication Commands 8

8.8 Reading The Programmable Controller Type


(PC command)
8.8.1 Type Codes
Type code Type code
Programmable controller type Programmable controller type
(hex.) (hex.)
FX1S F2H A2USCPU 82H
FX0N 8EH A2CPU-A1, A2USCPU-S1 83H
FX, FX2C 8DH A3CPU, A3NCPU A3H
FX1N 9EH A3ACPU 94H
FX2N, FX2NC 9DH A3HCPU, A3MCPU A4H
A0J2HCPU 98H A3UCPU 84H
A1CPU, A1NCPU A1H A4UCPU 85H
A1SCPU, A1SJCPU 98H A52GCPU 9AH
A2CPU(-S1), A2NCPU(-S1), A2SCPU A2H A73CPU A3H
A2ACPU 92H A7LMS-F A3H
A2ACPU-S1 93H AJ72P25/R25 ABH
A2CCPU 9AH AJ72LP25/BR15 8BH

8-12
FX communication Commands 8

8.8.2 Control Specification and Example


1 ) Control specification
Protocol format 1 is shown.

Programmable controller type name


read command

No.
Station

PC No.

code
Sum check

No.
Station

PC No.
Message
wait time
E N Q

A C K
P C
Character area B
Computer
Programmable

No.
Station

PC No.

code
Sum check
PC type

S T X

E T X
controller name

(2 characters)

Notes
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.

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

The sum check is


calculated over
this range

The sum check is


E calculated over A
N 0 F F F P C 0 C 5 C 0 F F F
Q this range K
Computer 05H 30H 46H 46H 46H 50H 43H 30H 43H 35H 06H 30H 46H 46H 46H
Programmable
controller
S
T 0 F F F 8 D
E
T 8 1
8
X X
Indicates station No. 15
02H 30H 46H 46H 46H 38H 44H 03H 38H 31H
("0F" in hexadecimal).
Indicates the type name of the Programmable controller is FX, FX 2C series.

8-13
FX communication Commands 8

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 series pro-
grammable controller, it is Xn2 of the computer link unit.
This function can be used for initialization, resetting or simultaneous start/stop of all programma-
ble 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) at
all stations in the multidrop link.
The station number specified in the control protocol must indicate all stations, and is hence
specified as FFH (FF). If other than FFH is specified as the station number, the special aux-
iliary 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
turned off, and the global function operation is cleared.
1 ) Control specification
Protocol format 1 is shown.
Global function command Character area A
No.
Station

PC No.

code
Sum check
Message
wait time
E N Q

Control flag
G W

(1 characters)
Computer
Programmable When data value is "1" (31H), global operation flag is tumed on.
controller When data value is "0" (30H), global operation flag is tumed off.
Notes
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.

2 ) Specification example
To turn on the global operation flag at all programmable controller stations in the computer link;
auxiliary relay M8126 in an FX series PC station, and Xn2 in an A series programmable controller
station.
The sum check is
calculated over
this range

E
N F F F F G W 0 1 1 7
Q
Computer 05H 46H 46H 46H 46H 47H 57H 30H 31H 31H 37H
Prpgrammable
controller Indicates that the global operation flag is turned ON.

"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).

8-14
FX communication Commands 8

8.10 On-demand Function


Data transmission between the computer and programmable controller is usually initiated by the
computer only. The on-demand function is used if there is a need to transmit data from the pro-
grammable controller to the computer. The range of data registers containing the data to be sent
is specified in special data registers.
Programmable controller
D8127 Head address
D8128 Data length
Program D(n) Computer

D(n+m-1)

Notes
This function can only be used when the configuration of the computer and program-
mable controller is 1:1.

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 in
the following table.

Device Name Description


On during execution of on-demand
On-demand handshake
M8127 ON: on-demand data being transmitted
signal
OFF: on-demand data transmission complete
On if there is error in specified value for data transmission in on-
demand
M8128 On-demand error flag
ON: error
OFF: no error
8
Word/byte data format for on-demand data.
Flag for specifying word
M8129 ON: byte units (8-bits per data register)
or byte data format
OFF: word units (16-bits per data register)
On-demand head The head device number of the data area in which the data to be
D8127
device number register transmitted is stored. Set by programmable controllers program.
On-demand data length The data length to be transmitted by on-demand. Set by pro-
D8128
register grammable controllers program.

Notes
The on-demand handshake signal is a signal which is turned on when data transmis-
sion to the computer is started from the programmable controller, and is turned off
when transmission of the specified data is complete.
This is used as an interlock so that multiple on-demand requests can not be issued
simultaneously.

8-15
FX communication Commands 8

8.10.2 On-demand Control Protocol


1 ) Control protocol programmable controller

On-demand data transmission

Set the word/byte data format Set on/off special M8129.


ON: byte units(8bits), OFF: word units(16bits)

Set the on-demand data Write the data to be transmitted into data reg-
isters.

Reset the on-demand error flag Turn off on-demand error flag special M8128.
(If special M8128 is ON, on-demand can not
be started.)
Start on-demand On-demand is started by writing the head
device number where the data is stored into
special M8127, and writing the data length
into special D8128.
When the request is received, special M8127
is turned on, and when transmission is com-
pleted, the M8127 is turned off.

Transmission error check If the on-demand error flag special M8128 is


ON, the data was not transmitted due to a
transmission error.
Error No error

Transmission Complete

2 ) Control protocol at computer

On-demand Receive

Check that the received data is On-demand data has a PC number of FE auto-
on-demand data. matically attached. This can be used to identify
on-demand data.

Data processing

Completion of Receive

8-16
FX communication Commands 8

3 ) On-demand request time chart.


When the computer is transmitting data

E A
N b) On-demand data C
Q K
Computer c)
Programmable S
controller T
X

On-demand a)
execution
flag M8127
Start on-demand,
Programmable writing of the on-
controller demand data length

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


immediately turned on.
b ) Transmission of on-demand data is forced to wait until completion of reception of com-
mand data (ENQ-) from the computer.
c ) Transmission of response data (STX-) to command data (ENQ-) is forced to wait until
completion of transmission of on-demand data.

When the computer is receiving data

c)
E A
N On-demand data C
Computer
Q K 8
Programmable S
controller T
X

On-demand
execution b)
flag M8127 a)
Start on-demand,
Programmable writing of the on-
controller demand data length

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


immediately turned on.
b ) Transmission of on-demand data is forced to wait until completion of transmission of
response data (STX-) to the command data (ENQ-) from the computer.
c ) Transmission of response data (ACK-) from the computer to the transmission of response
data (STX-) from the programmable controller should be done after completion of recep-
tion of on-demand data.

8-17
FX communication Commands 8

8.10.3 Specification and Example of On-demand


1 ) Command specification
Protocol format 1 is shown.
Added by
programmable
controller

Computer
Programmable

No.
Station

PC No.

code
Sum check
S T X

E T X
controller Transmission
data

ON
Special auxiliary OFF
relay M8127
On-demand data is set, the head address
Programmable Write processing is written to D8127 and the data length is
controller written to D8128.

Notes
Specify the data length so as to satisfy the following condition.
Data length 40H (64 points)(13 points for FX0N)
The PC number, FE is added by the programmable controller.
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.

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 communication
data in control protocol formats 1 to 4, and on-demand data become confused, and
normal data transmission is not possible.

8-18
FX communication Commands 8

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

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


Programmable S A
controller T 0 0 F E 1 2 3 4 5 6 7 8 C 9 2
X K
02H 30H 30H 46H 45H 31H 32H 33H 34H 35H 36H 37H 38H 03H 39H 32H

M8127

Programmable
Write processing
controller Set ON if a transmission error
occurs
On-demand D8127 100 M8128 ON/OFF
command D8128 2 M8129 OFF
D100 1234H
The 4 hexadecimal digits of
D101 5678H each word are transmitted in
ASCII, starting with the most
significant digit.

Program example

M8000
M8129 Data transmission set to word units.
X000 M8002
0 PLS M0 Start command signals a pulse.
M0 M8127
3 MOV H1234 D100
Transmission data is set.
7 MOV H5678 D101 8
On-demand error flag is reset
RST M8128
(cannot start if M8128 is ON)
RST Y000

RST Y001

MOV K100 D8127 On-demand is started by specifying transmission



data area head address and data length.
MOV K2 D8128
M8127 M8128
33 SET Y000 Confirming on-demand error, normal/abnormal
M8128
external output is set.
SET Y001

40 END

M8128 OFF : Normally transmitted.

ON : Data is not transmitted due to error.

8-19
FX communication Commands 8

3 ) Specification Example 2
To transmit the data stored in data registers D100 and D101 from the programmable control-
ler (when the station number is 0, and data is specified in byte units)
The PC number "FE" is automatically added by the
programmable controller
Computer
Programmable S E
controller T 0 0 F E 3 4 1 2 7 8 5 6 T 9 2
X X
02H 30H 30H 46H 45H 31H 32H 33H 34H 37H 38H 35H 36H 03H 39H 32H

M8127

Programmable
controller Write processing
Set ON if a transmission
error occurs
On-demand D8127 100 M8128 ON/OFF
command D8128 4 M8129 ON
D100 1234H The 2 hexadecimal digits of
D101 5678H each byte are transmitted in
ASCII, starting with the most
significant digit.The lower byte
of each word is transmitted first.

Program example
M8000
M8129 Data transmission set to byte units.
X000 M8002
0 PLS M0 Start command signals a pulse.
M0 M8127
3 MOV H1234 D100
Transmission data is set.
7 MOV H5678 D101
On-demand error flag is reset
RST M8128
(cannot start if M8128 is ON)
RST Y000

RST Y001

MOV K100 D8127 Confirming on-demand error, normal/



abnormal external output is set.
MOV K4 D8128
M8127 M8128
33 SET Y000 Confirming on-demand error, normal/
M8128
abnormal external output is set.
SET Y001

40 END

M8128 OFF : Normally transmitted.

ON : Data is not transmitted due to error.

8-20
FX communication Commands 8

8.11 Loopback Test


The loopback test is the function for testing if communication between the computer and pro-
grammable controller is operating as normal or not.
1 ) Command Specification
Protocol format 1 is shown.
Loopback test command Character area A
No.
Station

PC No.

Characters
No.

code
Sum check
Message
wait time
Data
E N Q

T T (designated
No.
characters) 2 characters (hexadecimal)
Computer
Programmable

No.
Station

PC No.

Character
No.

code
Sum check
Data

A C K

E T X
controller 2 characters (hexadecimal) (same data
as character
A area)

Character area B
Notes
Specify the number of characters so as to satisfy the following condition.
- 1 No.characters 254 (25 for FX0N)
The station number, PC number, number of devices, and sum check code are
expressed in hexadecimal.

2 ) Specification example
To test the Loopback with data ABCDE at station No.0 (with message wait time set to 0 ms)
The sum check is calculated over
this range 8
E
N 0 0 F F T T 0 0 5 A B C D E 7 8 The sum check is calculated
Q over this range
Computer 05H 30H 30H 46H 46H 54H 54H 30H 30H 35H 41H 42H 43H 44H 45H 37H 38H
Programmable S E
controller T 0 0 F F 0 5 A B C D E T A 3
X X
02H 30H 30H 46H 46H 30H 35H 41H 42H 43H 44H 45H 03H 41H 33H

Same data is transmitted.

8-21
FX communication Commands 8

MEMO

8-22
FX Series Programmable Controllers RS instruction 9

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction 9

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers RS instruction 9
FX communication RS instruction 9

9. RS instruction
This section describes RS instructions. For the target devices, refer to the application instruction
manual of each programmable controller.

9.1 Function and Operation


9.1.1 Send and Receive Program
An RS instruction sends and receives serial data using the RS232C port (optional equipment).
X010
RS D200 D 0 D500 D 1

Address and Address and


number of points number of points
of send data of receive data

The data transmission format can be set using a special data register D8120.
Even if the setting of D8120 is modified while an RS instruction is driven, such modification is
not accepted.
In a system in which send is not performed, set the number of send points to K0.
In a system in which receive is not performed, set the number of receive points to K0.

9-1
FX communication RS instruction 9

9.1.2 Operation of RS Instruction


An RS instruction specifies the head address and the number of points of the send data sent
from a programmable controller as well as the head address for receive data save destination
and the maximum number of acceptable number of points of receive data.
The data send/receive sequence using an RS instruction is described below.
X010
RS D200 D 0 D500 D 1 For operafion refer to section 9-2, 9-3

Address and Address and


number of points number of points
Pulse of Send of send data of receive data
request Writes conferts of send Writes the contents of D0 (number of
data points of send data) and D200~.

This request is automatically reset


SET M8122 when send is complefed.Never reset
this request by a program.
Set send request
Receive completion
M8123 Transfers the receive data to the
Moves receive data dedicated save area.

The receive completion flag M8123


RST M8123 should not be reset in a program of
confinuous operation.
Reset receive
completion flag

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 a time (Two or more RS instruc-
tions cannot be turned on at one time.). For changeover, assure the OFF time is
equivalent to or longer than one cycle time.
In the FX0N , FX 1S, FX1N, FX and FX 2C, assure the OFF time is equivalent to or
longer than two scan times between completion of send and start of receive or
between completion of receive and start of send. In the FX2N and FX2NC whose ver-
sion is earlier than V 2.00, assure the OFF time is equivalent to or longer than 100
s between completion of send and start of receive or between completion of
receive 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 later
because full duplex communication is enabled.

While an RS instruction is driven, modification of the setting of the D8120 is not


accepted. Turn off the RS instruction, then modify the setting.

9-2
FX communication RS instruction 9

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 completion
status, 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 to
the receive wait status.

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.

2 ) Receive completion <M8123>


When the receive completion flag M8123 is turned on, transfer the receive data to an other
save destination, then reset the 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 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 program-
mable controller is set from this status to the receive wait status, set D1 to a value equivalent
to or smaller 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 to
the programmable controller) when the line of the modem is established, M8124 is turned on.
9
While M8124 is turned off, the dial No. can be sent. While M8124 is turned on, data can be
sent and received.

9-3
FX communication RS instruction 9

4 ) Time-out evaluation <M8129> (Valid in the FX2N, FX2NC programmable controller earlier
than V2.00)
If receive is not restarted within the time specified by D8129 after the receive data is inter-
rupted on the midway, it is regarded as time-out, M8129 is turned on, and receive is com-
pleted (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 in equip-
ment in which the number of send data may be changed.
Receive data is
interrupted
Receive Data
Reset by program
Time-out evaluation D8129 10ms
M8129 ON
Receive completion
M8123 ON

5 ) Time-out evaluation time <D8129> (Valid in V 2.00 or later of the FX2N, FX2NC programmable
controller)
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 0 is set to D8129, the evaluation time is regarded as 100 ms.
Example: When the time-out evaluation time is set to 50 ms

M8002
MOV K5 D8129

9-4
FX communication RS instruction 9

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 is
performed.
Accordingly, when the send flag is turned on while data is received, the send wait flag M8121 is
turned 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)
RS instruction
driving OFF ON

Send data
SD (TXD) Data 1 Data 4

Send request ON OFF


M8122

Send wait OFF ON


flag M8121 * This period should be
100 s or more

Receive data
RD (RXD) Data 2 Data 3

Receive
completion OFF ON ON
M8123 The receive wait
status is started Reset it using a program.
When it is not trurned off, the next
data cannot be received.

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

9-5
FX communication RS instruction 9

2 ) Use terminal mode of control line


This mode is available for send only or receive only.
a ) Send only
RS instruction
driving OFF ON

Send data
SD (TXD) Data 1 Data 1 Data 2

Send request OFF ON


M8122

ER(DTR) OFF ON

DR(DSR) OFF ON

b ) Receive only

RS instruction
driving OFF ON

Receive data
RD (RXD) Data 1 Data 2

ER(DTR) OFF ON

Receive
completion OFF ON ON ON
M8123
Reset using a program. When it is not trurned off, the next data cannot
be received.

9-6
FX communication RS instruction 9

3 ) Use normal mode 1 of control line

RS instruction
driving OFF ON

Send data SD
(TXD) Data 1 Data 3

Send request OFF ON


M8122

Send wait OFF ON


flag M8121

ER(DTR) OFF ON

Receive data
RD (RXD) Data 2

Receive
completion OFF ON
M8123
Reset using a program.
When it is not trurned off, the next
data cannot be received.

DR(DSR) OFF ON

This period should be 100 s or more

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

9-7
FX communication RS instruction 9

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


RS instruction
driving OFF ON

Send data
SD (TXD) Data 1 Data 3

Send request OFF ON


M8122

Send wait ON
flag M8121
Check OFF
ER(DTR) OFF ON
*2
DR(DSR) OFF ON *1 *1
Check *5
OFF
Receive data *3
RD (RXD) Data 2

Receive
completion OFF ON *4
M8123

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


*2 When finished to send data, please turn off DR (DSR). When it is not turned off, the next data
cannot be 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 not turned off, the next data cannot be received.
*5 This period should be 2 scan times or more.

9-8
FX communication RS instruction 9

9.2.2 FX2N, FX2NC (V 2.00 or later)


In the FX2N of V 2.00 or later, full duplex communication is performed. When performing half
duplex communication, pay rigid attention so that the send flag is not turned on while data is
received. If it is turned on, send is started. As the result, the counterpart equipment may not be
able to receive data or the send/receive data may be damaged.
In the full duplex communication, the send wait flag M8121 is not turned on.
In the version V 2.00 or later, the programming protocol (Section 12) is supported while an RS
instruction remains OFF.
1 ) Do not use hardware hand shake
RS instruction
driving OFF ON

Send data
SD (TXD) Data 1 Data 3 Data 5

Send request OFF ON


M8122

Receive data Data 4


RD (RXD) Data 2

Receive
completion OFF ON ON
M8123
The receive wait Reset using a program.
status is started When it is not trurned off, the next
data cannot be received.

2 ) Use terminal mode of control line


This mode is available for send only or receive only.
The control line and the transmission sequence are equivalent to those in the FX2N series
whose version is earlier than V 2.00. Refer to paragraph 9.2.1.

9-9
FX communication RS instruction 9

3 ) Use normal mode 1 of control line


RS instruction
driving OFF ON

Send data
SD (TXD) Data 1 Data 4

Send request OFF ON


M8122

ER(DTR) OFF ON

Receive data
RD (RXD) Data 2 Data 3

Receive
completion OFF ON ON
M8123
DR(DSR) OFF ON

Reset using a program.


When it is not trurned off, the next data
cannot be received.

9-10
FX communication RS instruction 9

4 ) Use interlink mode of control line


RS instruction
driving OFF ON

Send data
SD (TXD) Data 2 Data 4 Data 4

Send request ON OFF


M8122

DR(DSR) OFF *1 ON *1 *1
Up to 30 characfers can be
received *2

Receive data
RD (RXD) Data 1 Data 3 Time-out Data 3
evaluation time
D812910ms
Time-out
evaluation *3
flag M8129 Reset it using a program.
When it is not trurned off,
the next data cannot be
received.
Receive
completion OFF ON ON ON
M8123
ER(DTR) ON OFF

Reset using a program.


When it is not trurned off, the
next data cannot be received.

*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 the
30th character receive buffer limit, and requests the counterpart equipment to stop send.
9
After this send request, up to 30 characters can be received. The 31st and later characters
cannot 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 is
received or the 30th character is received. Therefore, receive points need to set 30th or more.
*3 Reset using a sequence program.
If it is not turned off, the next data cannot be received.

9-11
FX communication RS instruction 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 a
CCD instruction.)

OFF during RUN 16-bit data


OFF
Upper 8 bits Lower 8 bits
M8000
M8161 16-bit mode 16-bit data is divided into the
lower 8 bits and the upper 8
bits, then sent or received.
S m D n
X010
RS D200 K 4 D500 K 10

Send data STX D200 lower D200 upper D201 lower D201 upper ETX
(Programmdble
controller Header Terminator
External Head address specified by S
equipment) Send byte count
specified by "m"

Receive data STX D500 lower D500 upper D501 lower D501 upper D502 lower D502 upper ETX
(External
equipment Header Terminator
Programmdble Head address specified by D
controller) It does not exceed the upper limit number
of receive data points (byte count)
specified by "n".
Receive is completed when the terminator
(ETX) or "n" points are received.

1 ) Send data and remaining number of send data


D200 upper

D201 upper
D200 lower

D201 lower
STX

ETX

Send data SD (TXD)

4
3
Remaining number 2
1
of send data D8122 0

2 ) Receive data and number of receive data


D500 upper

D501 upper

D502 upper
D500 lower

D501 lower

D502 lower
STX

ETX

Receive data RD (RXD)

6 The number of receive


5
4 data is also reset when
3 the receive completion
Number of receive data 2
D8123 1 flag M8123 is reset.
0

9-12
FX communication RS instruction 9

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 a
CCD instruction.)
M8000 16-bit data
M8161 8-bit mode
Ignored Lower 8 bits
S m D n The upper 8 bits are ignored,
X010 and the lower 8 bits exclusiuely
RS D200 K 4 D500 K 10 are regarcled as valid.

Send data STX D200 lower D201 lower D202 lower D203 lower ETX
(Programmdble
controller Header Terminator
External Head address specified by S
equipment) Send byte count
specified by "m"

Receive data STX D500 lower D501 lower D502 lower D503 lower D504 lower D505 lower ETX
(External
equipment Header Terminator
Programmdble Head address specified by D
controller)
It does not exceed the upper limit number
of receive data points (byte count)
specified by "m".
Receive is completed when the terminator
(ETX) or "n" points are received.

1 ) Send data and remaining number of send data


D200 lower
D201 lower
D202 lower
D203 lower
STX

ETX

Send data SD (TXD)

4
3 9
Remaining number 2
1
of send data D8122 0

2 ) Receive data and number of receive data


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

ETX

Receive data RD (RXD)

6 The number of
5 receive data is also
4 reset when the
3
Number of receive data 2 receive completion
D8123 1 flag M8123 reset.
0

9-13
FX communication RS instruction 9

9.4 Example Program


9.4.1 Personal Computer
When a programmable controller is connected to a personal computer, and data send/receive is
performed by the programmable controller
1 ) System configuration

R e ce ive

Send

F X 2 N -2 3 2 -B D F X 2N

Use a communication cable suitable to the arrangement of connector pins of the personal
computer used. (For the representative wiring, refer to chapter 2.)
2 ) Communication format
If the communication format of the commercial communication software used cannot realize
the following setting, set the programmable controller in accordance with the commercial
communication software.
(The communication format in this example is set as follows.)
Data length 8 bit
Parity Even
Stop bit 2 bit
Baud rate 9,600 bps
Header None
Terminator None
Control line Normal mode 1
Protocol No protocol

3 ) Operation
PLC and personal computer are turned ON.
Power ON When PLC is in RUN status, PLC already can receive data
from personal computer.

Receiving data When operating program of personal computer, data is sent to


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

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

9-14
FX communication RS instruction 9

4 ) Example program of programmable controller

M8002 Sending data and receiving data


FNC 40 D0 D11
ZRST reset.

FNC 12 Setting communication format.


H 048F D8120 b15 b0
MOV
0000 0100 1000 1111
M8000 0 4 8 F
FNC 80 D10 K4 D0 K4 RS instruction drive.
RS

M8123
FNC 15 D0 D10 K2 The receiving data (D0, D1)
BMOV moves to sending data area
(D10, D11).

PLF M20

RST M8123 Receive completion reset

M20
SET M8122 Send request

END

5 ) Example program of cumputer


This is an example of a BASIC program for communication of RS instruction communication
(no protocol communication). This BASIC program is written by N88BASIC of Nippon Electric
Corporation.
9
10 C LO S E #1 :A $=40 T ext of A S C II stored.
20 O P E N C O M 1: A S #1 C O M 1 port is opened.
30 P R IN T #1,A $ D ata is sen t to P LC .
40 C LO S E #1 :F O R I=J T O 2000:N E X T *1
50 O P E N C O M 1: A S #1
60 F O R I=1 T O 100 *1
70 IF LO C (1)>=4 G O T O 10 0 Length of received data is check ed.
80 NEXT
90 C LO S E #1 :P R IN T T IM E O U T E R R O R :E N D
100 B $=IN P U T $(LO C (1),#1)
110 P R IN T B $ R eceived d ata is displayed.
120 END

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

9-15
FX communication RS instruction 9

9.4.2 Printer
Connecting FX2N-232-BD and printer, and printing out the data send from the programmable
controller.
1 ) System configuration

Send

FX 2N -232-BD FX 2N

Use a communication cable suitable to the arrangement of connector pins of the printer
used. (For the representative wiring, refer to chapter 2.)
2 ) Communication format
Let the communication format of the programmable controller be in accordance with that of
the printer used. (The communication format in this example is set as follows.)
Data length 8 bit
Parity Even
Stop bit 2 bit
Baud rate 2,400 bps
Header None
Terminator None
Control line No use
Protocol No protocol

3 ) Operation

Turn on the power of the In this example,CR (H000D) and


programmable controller and printer, LF (H000A) are written at the
Power on
check the printer is on line and switch end of the message. The printer
the programmable controller to RUN. moves down one line for each
X000,ON meessage.
CR: Carriage Return
RS instruction Turn on X000, and drive RS
LF: Line Feed
drive instruction.

X001,ON Note:lt may be necessary to set


Every time X001 is turned on, the the DIP switches of your printer.
contents of D200 to D210 are sent Check your printer manual for
Data send
to the printer, and "test line" is how to configure the serial
printed. communications.

9-16
FX communication RS instruction 9

4 ) Example program

M8000
M8161 Handled by 8-bit data
M8002
MOV H006F D8120 Setting communication format
X000 b15 b0
RS D10 K11 D50 K0 RS instruction driving
X001 0000 0000 0110 1111
PLS M0 0 0 6 F
M0
MOV H0074 D10
MOV H0065 D11

Writing send data


MOV H006E D17
MOV H0065 D18
MOV H000D D19
MOV H000A D20
SET M8122 Send request
END

9-17
FX communication RS instruction 9

9.5 Supporting RS Instruction and Programming Protocol


When using RS instruction in conjunction with the FX 2N-232-BD or FX0N-232ADP, the user can
switch between using no protocol communication and the programming tool (programming proto-
col) under the following conditions:
Accordingly, when data is received from counterpart equipment while an RS instruction remains
OFF, NAK will be sent back to the counterpart equipment.

9.5.1 Programmable Controller and Version

Supporting Version
FX2N V2.01 or more

FX2NC All products (V2.01 or more)

9.5.2 Operating Conditions and Format Set Content


The programmable controller can change from using no protocol communication to programming
protocol (and back) by manipulating the RS instruction and Register D8120 and shown below.
1 ) With the RS instruction On, move the data choices shown below into the Register D8120 to
use no protocol communication.
Table: Set communication format (D8120)
Content
Item
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
2 ) To use programming protocol, turn the RS instruction Off and move the data H0000 into the
communication format Register D8120. When the programmable controller is taken out of
RUN mode (by FX-PCS/WIN-E Software or the front panel switch), complete editing and pro-
gram downloads can be accomplished. On line changes can be performed with the program-
mable controller in Run Mode.
Example of changing the communication format (D8120) between H0086 and H0000. The pro-
grammable controller is first set for no protocol communication using RS instruction.
X0
MOV P H0086 D8120

RS D0 K1 D1 K1
X0
MOV P H0000 D8120

9-18
FX Series Programmable Controllers FX2N-232IF 10

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF 10

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers FX2N-232IF 10
FX communication FX2N-232IF 10

10. FX2N-232IF

10.1 Introduction
The RS232C interface block FX2N-232IF (hereinafter referred to as 232IF) is connected to the
FX1N, FX2N, FX2NC programmable controller to realize full duplex serial data communication with
another RS232C interface such as a personal computer, bar code reader, printer, etc.

10.1.1 Outline of Product


1 ) Applicable programmable controller
The 232IF can be connected as a special block of the FX1N, FX2N, FX2NC programmable
controller.
2 ) Control instructions
Send/receive data is received and sent and diversified control commands are manipulated
using the FROM/TO instruction.
3 ) Number of I/O points and connection method
The number of I/O points occupied is 8 in all (either input or output). However the 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 total
current consumption of the 5 V power including other special blocks is equivalent to or less
than that available.
4 ) Communication method
Full duplex start-stop synchronization and no protocol procedure are used. The communica-
tion format can be specified using the buffer memories (BFMs).
5 ) Send/receive buffer
The send/receive buffer can accommodate 512 bytes/256 words.
When the RS232C interlink connection mode is used, data exceeding 512 bytes/256 words
can also be received.
6 ) ASCII/HEX conversion function
The function to convert and send a hexadecimal numeric (0 to F) saved in the send data 10
buffer as well as the function to convert a received ASCII code into a hexadecimal numeric (0
to F) and save it to the receive buffer are provided.

10-1
FX communication FX2N-232IF 10

10.2 Allocation of Buffer Memories (BFMs)


The RS232C interface block FX2N-232IF(232IF) transmits data with the programmable controller
via the 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

R:For read
BFM
Name Setting range Initial value W:For
No.
write
#0 Communication format 0087H W
#1 Command 0 W
1 to 512 (when data length is 16
bits)
#2 Receive upper limit byte count 1 to 256 (when data length is 8 0 W
bits)
0 is treated as 512 or 256.
1 to 32,767 (X10 ms)
#3 Receive time-out time 0 W
0 eliminates time-out time.
#4 Send header, lower 2 bytes 0 (no header)
4 bytes max., zero suppression W
#5 Send header, upper 2 bytes 0
#6 Send terminator, lower 2 bytes 0 (no terminator)
4 bytes max., zero suppression W
#7 Send terminator, upper 2 bytes 0
#8 Receive header, lower 2 bytes 0 (no header)
#9 4 bytes max., zero suppression W
Receive header, upper 2 bytes 0
Receive terminator, lower 2
#10 bytes 0 (no terminator)
4 bytes max., zero suppression W
#11 Receive terminator, upper 2 0
bytes
Receive suspension waiting
#12 0 to 32,327 (X10 ms) 0 W
time (in interlink connection)
0 to 512 (when data length is 16
Number of remaining send bits)
#13 0 R
data 0 to 256 (when data length is 8
bits)
#14 Number of receive buffers 0 to 256 + 15 *1 0 R
#15 Send sum result 0 R
#16 Receive sum result 0 R

Note : W : For write can be used for read also. Undefined BFM Nos. are not allowed to be used
in program.
*1 : Spare buffers used in the interlink connection mode.

10-2
FX communication FX2N-232IF 10

BFM Initial R:For read


Name Setting range
No. value W:For write
#20 Time from CS ON to send start 0 to 32,327 (X 10 ms) 0 W
Time from completion of actual
#21 send to RS OFF 0 to 32,327 (X 10 ms) 0 W
(completion flag ON)
#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

#1001
to Send buffers 0 W
#1256

#2000 Receive byte count


0 to 512 + 30 *1
0 to 256 + 15 *1 0 R

#2000
to Receive buffers 0 R
#2256
#2257 Spare receive buffers for interlink
to 0 R
#2271 connection mode

Note : W : For write can be used for read also. Undefined BFM Nos. are not allowed to be used
in the program.
*1 : Spare buffers used in the interlink connection mode.

10

10-3
FX communication FX2N-232IF 10

10.2.2 Communication Format <BFM#0>


Bit Description 0 1 Initial value
b0 Data length 7 bit 8 bit 1 : 8 bit
b1
b1 (00) : None
Parity (11) : Even
b2 (01) : Odd
(11) : Even
b3 Stop bit 1 bit 2 bit 0 : 1 bit
b4
(0011) : 300
b4 (0100) : 600
b5 (0101) : 1200
Baud rate (bps) (1000) : 9600 bps
b6 (0110) : 2400
b7 (0111) : 4800
(1000) : 9600
(1001) : 19200
b8
b8 (00) : No used
Control line (00) : No used
b9 (01) : Standard RS232C
(11) : RS232C interlink connection mode
b10
b10 (00) : No added
Addition of CR and LF (00) : No added
b11 (01) : CR only
(11) : CR and LF
b12
(00) : No available
Availability of check
b12 (01) : ASCII/HEX conversion available
sum and ASCII/HEX (00) : No available
b13 (10) : Check sum available
conversion
(11) : Check sum available, ASCII/HEX conversion
available
Send/receive buffer
b14 16 bit 8 bit 0 : 16 bit
data length
b15 No used 0 : No used

The communication format is determined on the rising edge of the send/receive enable com-
mand (BFM #1 b0).
Accordingly, the setting of the communication format should be preliminary transferred using the
TO instruction before BFM #1 b0 is turned on. Also, the send header and the send terminator are
determined in the rising edge of the send command (BFM #1 b1). The receive header and the
receive terminator are determined on the rising edge of BFM #1 b0 or on the rising edge of the
receive completion reset command (BFM #1 b2). Accordingly, when only the header and the ter-
minator exclusively are changed it is not necessary to turn BFM #1 b0 off. The change becomes
valid form the next send/receive operation.

10-4
FX communication FX2N-232IF 10

Note : Setting example (hexadecimal, constant specification)

Data length 8 bits


Parity Odd b15 b12 b11 b8 b7 b4 b3 b0
Stop bit 1 bit BFM #0 0 1 0 0 0 0 0 0 0 1 1 0 0 0 1 1
Baud rate 2400 bps 4 0 6 3
Control line No used (4063 H )
CR, LF No added M8002
FNC 79 K0 K0 H4063 K1
Sum check No added TO
Initial
ASCII/HEX conversion No used pulse Block BFM Set Number of
No. value transfer
Buffer data length 8 bits points

1 ) Communication format
Select the communication format used
Data
to send/receive data in the 232IF
among 9 types shown on the left.
Data Termi
nator
The header can be specified in the
portion in the communication Data Termi CR
format. nator

In the communication format type Termi


Data CR LF
, hexadecimal data (binary) and nator

ASCII code can be send and


Header Data Termi Sum
received. nator
In the communication format types
to , the send/receive data Header Data Termi
nator
Sum CR
should be any ASCII code except
the header, the terminator and CR. Header Data Termi Sum CR LF
nator
Communication can be performed
using the ASCII/HEX conversion
Data CR
function by specifying the BFM #0
b13 and the BFM #0 b12.
Data CR LF
The ASCII codes available for the 10
initial terminator are 01H to 1FH.
In the RS232C interlink connection
mode, the communication formats
to are available.

2 ) b0 to b7 (data length, parity, stop bit and baud rate)


b0 to b7 should be aligned with the communication specification of the connected counter-
part equipment.

10-5
FX communication FX2N-232IF 10

3 ) b9 and b8 (control line)


For examples of connecting the equipment corresponding to each setting, refer to section
2.2.2. For operation of control line, refer to section 10.3.
When not used (b9=0, b8=0) is specified, communication is performed using only the SD
and RD signals without using the control line.
When standard RS232C mode (b9=0, b8=1) is specified, a cross cable is required to con-
nect the equipment of terminal specifications and a straight through cable is required to
connect the equipment of modem specifications.
When RS232C interlink connection mode (b9=1, b8=1) is specified, the request to send
(RS) signal functions as the signal to enable receive in the 232IF. When receiving data
exceeding 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 opera-
tion.
At this time, when the data saved in the receive buffers is read to data registers in the pro-
grammable controller using the sequence program, the remaining data can be received.
Make sure to perform the RS232C interlink connection when specifying this mode.
4 ) b11 and b10 (addition of CR and LF)
Set these bits as follows.
No 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-6
FX communication FX2N-232IF 10

Note : ASCII/HEX conversion


When execution of the ASCII/HEX conversion is specified, the hexadecimal numeric data (0
to F) 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 to the 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 code
Example : When the send data 10ABH, the header STX and the terminator ETX are
sent
Send data buffer BFM #1001
b15 b0 S E
0 0 0 1 0 0 0 0 1 0 1 0 1 0 1 1 T T
BFM #0 A B 1 0
X X
1 0 A B Converted into ASCII 02 H 41 H 42 H 31 H 30 H 03 H
code before send
The send byte count is "4".

b ) Receive format when ASCII code is converted into hexadecimal data


Example : When the receive data 10ABH, the header STX and the terminator ETX
are received
b15 b0
S E 0 0 0 1 0 0 0 0 1 0 1 0 1 0 1 1
T T
A B 1 0 1 0 A B
X X
Receive data buffer
02 H 41 H 42 H 31 H 30 H 03 H BFM #2001 1 byte 1 byte
The receive byte count is "2".

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)
Send/receive buffer
16-bit data is divided into
upper 8 bits and lower 8 bits,
Upper 8 bits Lower 8 bits then sent and received.
10
Example of send buffers
S BFM BFM BFM BFM E
T #1001 #1001 #1002 #1002 T
X lower upper lower upper X

In the case of 8 bits (b14=1)


Send/receive buffer
Upper 8 bits are ignored, and
lower 8 bits only are sent and
Ignored Lower 8 bits received as valid data.

Example of send buffers


S BFM BFM BFM BFM E
T #1001 #1002 #1003 #1004 T
X lower lower lower lower X

10-7
FX communication FX2N-232IF 10

10.2.3 Command BFM #1

Bit Description
b0 Send/receive enable (ER ON)
b1 Send command
b2 Receive completion reset command
b3 Error reset

BFM #1 gives the command for send/receive and the status information reset command to the
232IF.
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. Make
sure 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 to
the 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 is
automatically 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 receive
continuation 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.

10-8
FX communication FX2N-232IF 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 set
and the set condition is satisfied, it is regarded that receive is completed even if the data received
is 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 edge
of each data, the receive time-out flag (BFM #28 b2) is set to ON, it is regarded that receive is
completed, 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 suppression
The initial value is 0 (No used).
For the send data of the 232IF, 4 headers maximum can be specified. When the number of head-
ers is less than 4, the upper 0s are ignored (zero suppression) and not transferred.
BFM #5 BFM #4
(upper 2 bytes) (lower 2 bytes)
b15 b0 b15 b0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
0 0 0 0 0 0 0 2
4th 3rd 2nd 1st
Example:02H (STX)

The transmission order is fourth header, third header, second header, first header when 4
headers are specified. 10
10.2.7 Send Terminator <BFM #7 (upper), BFM #6 (lower)>
Setting range: 4 bytes maximum, zero suppression
The initial value is 0 (No used).
For the send data of the 232IF, 4 terminators maximum can be specified. When the number of
terminators is less than 4, the upper 0s are ignored (zero suppression) and not transferred.
As the first terminator, specify an ASCII code from 01H to 1FH. (As the second to fourth termina-
tors, any ASCII code can be specified.)
The register structure and the transmission order are equivalent to those of the send header
described above.

10-9
FX communication FX2N-232IF 10

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


Setting range: 4 bytes maximum, zero suppression
The initial value is 0 (No used).
For the receive data of the 232IF, 4 headers maximum can be specified. When the number of
headers is less than 4, the upper 0s are ignored (zero suppression).
The register structure and the transmission order are equivalent to those of the send header
described above.

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


Setting range: 4 bytes maximum, zero suppression
The initial value is 0 (No used).
For the receive data of the 232IF, 4 terminators maximum can be specified. When the number of
terminators is less than 4, the upper 0s are ignored (zero suppression).
As the first terminator, specify an ASCII code from 01H to 1FH. (As the second to fourth termina-
tors, any ASCII code can be specified.)
The register structure and the transmission order are equivalent to those of the send header
described 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 exceeding
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.
BFM #12 specifies the time after the request to send (RS) signal is turned off until the receive
suspended status (BFM #28 b4) is turned on. The value set to the BFM #12 should be equivalent
to or more than the time after the 232IF sets the request to send (RS) signal to OFF until the
send 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 the
send operation of the counterpart equipment is not suspended, the remaining data cannot be
received.

542 Spare receive buffers


(BFM#2257 to #2271)
513
512
Receive byte
count Receive upper limit
0 byte count (BFM#2) Set to the time in which
BFM#2000 the send operation of the
Data receive is counterpart equipment is
suspended. completely suspended.
Request to send (RS)

Receive suspended
BFM#28 b4

Suspension waiting time (BFM#12)


0 to 32,767 (10ms)

10-10
FX communication FX2N-232IF 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 during trans-
mission.

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 the
receive buffers BFM #2001 to #2256 and the spare receive buffers BFM #2257 to #2271 for
interlink 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:
Header Terminator Check sum

S E
T T
0 A 1 2 5 F 5 2
X X
02 H 30 H 41 H 31 H 32 H 35 H 46 H 03 H 35 H 32 H

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

The total value including the terminator and excluding the header (1st byte of the header only) is
calculated. Then, the lower 1 byte is converted into the ASCII code, and sent or received. The
data converted into the ASCII code is placed in the order of upper digit and lower digit. 10
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, receive
sum check error occurs.
The sum check target range and the calculation method are equivalent to those for the send sum
result described above.

10-11
FX communication FX2N-232IF 10

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 operation
can be set.
When control line not used is specified, the time after the send command is given until the send
operation 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 completion
flag (BFM #28 b0) is turned on can be specified.
Set BFM #21 when it is required by a modem, etc.

10-12
FX communication FX2N-232IF 10

10.2.17 Status <BFM #28>

Bit Description Bit Description


b0 Send completion b8 RS (RTS)
b1 Receive completion b9 ER (DTR)
b2 Receive time-out b10 Undefined
b3 Error occurrence b11 Undefined
b4 Receive suspended b12 DR (DSR)
b5 Undefined b13 CD (DCD)
b6 Being sent b14 DS (CTS)
b7 Being received b15 CI (RI)

The 232IF status and the send/receive result are saved as status information. This information
can be read from the programmable controller using the FROM instruction, then utilized.
1 ) b0 (send completion)
When send of data up to the send byte count (BFM #1000) is completed, the send comple-
tion status (b0) is set. The send completion status (b0) is automatically reset when the 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, the
receive completion status (b1) is set. If the receive terminator (BFMs #11 and #10) or the
receive time-out time (BFM #3) is set, it is regarded that receive is completed when the set
condition 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 data
cannot 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 saved
to the error code (BFM #29). 10
5 ) b4 (receive suspended)
When data exceeding the receive upper limit byte count (BFM #2) is received in the RS232C
interlink connection mode (BFM #0 b9=1, b8=1), the 232IF sets the request to send (RS) sig-
nal to OFF, requests the counterpart equipment to suspend the send operation, then sets
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 to
be 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 the num-
ber of receive buffers (BFM #14) should be read to data registers in the programmable con-
troller 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 completion sta-
tus (BFM #28 b0) is set.

10-13
FX communication FX2N-232IF 10

7 ) b7 (being received)
b7 is turned on after the head data is received until the receive completion status (BFM #28
b1) 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 the
FROM/TO instruction. The programmable controller can distinguish the equipment type by read-
ing 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
Example:#1001 (16-bit buffer)

Upper bits Lower bits


b15 b0
0 0 1 1 0 0 1 0 0 1 0 0 0 0 0 1
3 2 4 1
32 H =[2] 41 H = [A]

1byte 1byte
1word

A numeric in the send/receive buffer is treated as hexadecimal (HEX).

10-14
FX communication FX2N-232IF 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, and
accommodates 512 bytes/256 words. The buffer structure is equivalent to that of the send buff-
ers.
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 exceeding
512 bytes is received, and is used to receive the data after the request to send (RS) signal is
turned 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

10-15
FX communication FX2N-232IF 10

10.3 Hardware Hand Shake Operation


10.3.1 No Hardware Hand Shake
Setting BFM#0 (b9, b8)=(0, 0)

Send/receive OFF ON
enable *1 *1
(BFM#1 b0)
Send OFF ON
command
(BFM#1 b1)
Send data Data 1 Data 4
SD(TXD)
BFM#20 BFM#20
Send OFF X10ms *2 ON X10ms *2
completion
(BFM#28 b0)
Receive data Data 2 Data 3
RD(RXD)

Receive OFF ON
completion
(BFM#28 b1)
*3
Receive OFF ON
completion reset
command The receive wait
(BFM#1 b2) stafus is started. *4 *4 *3

*1 Turn off using a program. When it is not turned off, the next data cannot be sent.
*2 Time set by BFM#20 (x10ms).
*3 Turn it off using a program. When it is not turned off, the next data cannot be sent.
*4 After receive is completed and the receive data is read, turn off the receive completion flag
(BFM #28 b1) using a receive completion reset command (BFM #1 b2).

10-16
FX communication FX2N-232IF 10

10.3.2 Standard RS232C Mode


Setting BFM #0 (b9, b8) = (0, 1)
Send/receive OFF ON
enable
(BFM#1 b0)
DR(DSR) OFF ON

*1 *1 BFM#21(X10ms) *2
Send OFF ON
command BFM#21 *2
(BFM#1 b1) (X10ms)
RS(RTS) OFF ON

CS(CTS) OFF ON

Send data OFF


SD(TXD) Data 2 Data 4
BFM#20 BFM#20
Send OFF (X10ms) *3 (X 10ms) *3
completion
(BFM#28 b0) BFM#21 BFM#21
Receive data (X10ms) *2 (X10ms) *2
Data 1 Data 3
RD(RXD)
Receive OFF ON
completion
(BFM#28 b1) *4
Receive OFF
completion reset *5 *5
command The receive wait *4
(BFM#1 b2) stafus is started.

*1 Turn off using a program. When it is not turned off, the next data cannot be sent
*2 Time set by BFM #21 (x10ms)
*3 Time set by BFM #22 (x10ms)
*4 Turn off using a program. When it is not turned off, the next data cannot be received.
*5 After receive is completed and the receive data is read, turn off the receive completion flag
(BFM #28 b1) using a receive completion reset command (BFM #1 b2)
10

10-17
FX communication FX2N-232IF 10

10.3.3 Interlink Mode


Setting BFM #0 (b9, b8) = (1, 1)
Send/receive OFF ON
enable
(BFM#1 b0)
OFF ON
DR(DSR)
*1
*1
Send command OFF ON
(BFM#1 b1)
*2
CS(CTS) OFF *2
BFM#20(X10ms) *3 BFM#20(X10ms) *3

Send data Data 2 Data 4


SD(TXD)

Send OFF ON
completion BFM#20
(BFM#28 b0) (X10ms) *4
OFF ON
RS(RTS)
*5
Receive data Data 1 Data 3 Data 3
RD(RXD)
ON
Receive OFF
suspended
(BFM#28 b4) BFM#12
Receive OFF ON (X10ms) *6
completion *7
(BFM#28 b1) *8
Receive OFF
completion reset
command *9 *7 *7
*8
(BFM#1 b2)

*1 Turn off using a program. When it is not turned off, the next data cannot be sent.
*2 Make sure that the CS (CTS) in the FX2N-232IF is turned on while the counterpart equipment
is ready for receive.
*3 Time set by BFM #20 (x10ms)
*4 Time set by BFM #21 (x10ms)
*5 The RS (RTS) is turned off when the upper limit of receive byte count specified by the BFM #2
is exceeded.
When the send/receive buffer data length is 16 bits (BFM #0 b14=0), interrupt send from the
counterpart 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.
*6 Time set by BFM #12 (x10ms)
*7 Turn off using a program. When it is not turned off, the next data cannot be received.
*8 After receive is completed and the receive data is read, turn off the receive completion flag
(BFM #28 b1) 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 #2001
to BFM #2271) to the data registers in the programmable controller, then turn it ON.

10-18
FX communication FX2N-232IF 10

10.4 Example Program


10.4.1 Example of 16 Bits Data Communication
This system configuration describes an example in which data of 16-bit buffer length is sent and
received between the equipment of the terminal specifications. In this example, the ASCII code
saved in the data registers D201 to D205 in the programmable controller sent to the counterpart
equipment, and the data received from the counterpart equipment is saved to the data registers
D301 to D304 in the programmable controller.
1 ) System configuration

FX 2N programmable contraller FX 2N -232IF

Cross cable

Personal computer

2 ) Example setting buffer memories


The items not described here are set to the default respectively.
a ) Communication format <BFM #0>
Bit Description Setting
b0 Data length (1): 8 bits
b1
b2
Parity (1, 1): Even 10
b3 Stop bit (1): 2 bits
b4
b5
b6 Baud rate (1001): 19200 bps
b7
b8 Control line (0, 0): Not used
b9
b10
b11 Addition of CR and LF (0, 0): Not added
b12 Availability of check sum and
(0, 0): Not available Specification item for
b13 ASCII/HEX conversion
16-bit length
b14 Send/receive buffer data length (0): 16 bits
b15 Undefined

b15 b8 b7 b0
0 0 0 0 0 0 0 0 1 0 0 1 1 1 1 1
0 0 9 F (009F H)

10-19
FX communication FX2N-232IF 10

b ) Command <BFM #1>


M0b0:Send/receive enable (ER ON)
M1b1:Send command
M2b2:Receive completion reset command
M3b3: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>
b0M10:Send completion b8M18:RS(RTS)
b1M11:Receive completion b9M19:ER(DTR)
b2M12:Receive time-out b10M20:Undefined
b3M13:Error occurrence b11M21:Undefined
b4M14:Receive suspended b12M22:DR(DSR)
b5M15:Undefined b13M23:CD(DCD)
b6M16:Being sent b14M24:CS(CTS)
b7M17:Being received b15M25: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
byte count specified above.
Upper byte Lower byte
2nd byte 1st byte
(BFM#1001) 2 (32 H ) 1 (31 H )
4th byte 3rd byte
(BFM#1002) 4 (34 H ) 3 (33 H )
6th byte 5th byte
(BFM#1003) 6 (36 H ) 5 (35 H )
8th byte 7th byte
(BFM#1004) 8 (38 H ) 7 (37 H )
10th byte is not sent. 10th byte 9th byte
(BFM#1005) * * 9 (39 H )

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.

10-20
FX communication FX2N-232IF 10

3 ) Example program

M8002 FNC 79 Transfer of communication format


K0 K0 H009F K1
TO (009F H BFM#0)
Initial
pulse Block No. BFM No. Transfer
source
Number of
transfer points
FNC 79 Transfer of receive upper limit byte count
K0 K2 K8 K1 (K 8 BFM#2)
TO
FNC 79 H02 Send header
K0 K4 K1 (02 H BFM#4)
TO (STX)
FNC 79 H03 Send terminator
K0 K6 K1 (03 H BFM#6)
TO (ETX)
FNC 79 H02 Receive header
K0 K8 K1 (02 H BFM#8)
TO (STX)
FNC 79 H03 Receive terminator
K0 K 10 K1 (03 H BFM#10)
TO (ETX)
X000
PLS M1 Send command
Send command input
M1 FNC 12 Send byte count
K9 D 200 (K9 D200)
MOV
FNC 12 H3231 D 201 (21)
MOV
FNC 12 H3433 D 202 (43)
MOV
FNC 12 Send data (as many as 9 bytes)
H3635 D 203 (65)
MOV [123456789]

FNC 12 H3837 D 204 (87)


MOV
FNC 12 H0039 D 205 (_9)
MOV
Unused
Transfer of send byte count and send data
FNC 79 K0 K1000 D200 K6 D200(K 9) BFM#1000
TO 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 M8003
M0 Send/receive enable
RUN Initial pulse NC contact
monitor FNC 78 K0 K 28 K4M10 K1
Read of status 10
FROM (BFM#28 b15 to b0 M25 to M10)
Block No. BFM No. Transfer Number of
destination transfer points
M10
Y0
Send completion Status monitor (upon necessity)
M13
Y1
Error occurrence
X001
M3 Error reset
Error reset input
M11 FNC 78 Read of receive buffers
FROM
K0 K2001 D301 K4 BFM#2001 D301
Receive BFM#2002 D302
comple- BFM#2003 D303
tion BFM#2004 D304
Receive completion reset
M2 command
M8000 FNC 79 Transfer of command
K0 K1 K1M0 K1 (M3 to M0 BFM#1 b3 to b0)
TO

10-21
FX communication FX2N-232IF 10

4 ) Operation chart

(M0) BFM#1 b0
Send/receive enable

(M1) BFM#1 b1
Send command
9 8
7 6
BFM#13 5 4
Number of remaining 3 2
1 0
Send send data

#1001 upper

#1002 upper

#1003 upper

#1004 upper
#1002 lower

#1003 lower

#1004 lower

#1005 lower
#1001 lower
Send completion status is also reset
STX

STX
ETX
BFM#1001 to #1256 by next send command.
Send buffers

BFM#1000
(M10) BFM#28 b0 Send byte count
Send completion

4
3
BFM#14 2
Number of receive 1
buffers 0
7 8
4 5 6
BFM#2000 2 3
Receive byte count 0 1
Contents of receive buffers are also cleared. When not reset
Receive
#2001 upper

#2003 upper

#2004 upper
#2002 upper
#2002 lower
#2001 lower

#2003 lower

#2004 lower
STX

ETX

STX

ETX
BFM#2001 to #2256
Receive buffers

BFM#2
(M11) BFM#28 b1 Receive upper
Receive completion limit byte count

BFM#1 b2
(M2) Receive completion reset
command

10-22
FX communication FX2N-232IF 10

10.4.2 Example of 8 Bits Data Communication


This system configuration describes an example in which data of 8-bit buffer length is sent and
received between the equipment of the terminal specifications. In this example, the ASCII code
saved in the data registers D201 to D209 in the programmable controller is sent to the counter-
part equipment, and the data received from the counterpart equipment is saved to the data regis-
ters D301 to D308 in the programmable controller.
1 ) System configuration

FX 2N programmable contraller FX 2N -232IF

Cross cable

Personal computer

2 ) Example setting buffer memories


This items not described here are set to the default respectively.
a ) Communication format <BFM #0>
Bit Description Setting
b0 Data length (1): 8 bits
b1
b2 Parity (1,1): Even
b3 Stop bit (1): 2 bits
b4 10
b5
b6 Baud rate (1001): 19200 bps
b7
b8 Control line (0, 0): Not used
b9
b10 Addition of CR and LF (0, 0): Not added
b11
b12 Availability of check sum and
(0, 0): Not available Specification item for
b13 ASCII/HEX conversion
8-bit length
b14 Send/receive buffer data length (0): 8 bits
b15 Undefined

b15 b8 b7 b0
0 1 0 0 0 0 0 0 1 0 0 1 1 1 1 1
4 0 9 F (409F H )

10-23
FX communication FX2N-232IF 10

b ) Command <BFM #1>


M0b0:Send/receive enable (ER ON)
M1b1:Send command
M2b2:Receive completion reset command
M3b3: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>
b0M10:Send completion b8M18:RS(RTS)
b1M11:Receive completion b9M19:ER(DTR)
b2M12:Receive time-out b10M20:Undefined
b3M13:Error occurrence b11M21:Undefined
b4M14:Receive suspended b12M22:DR(DSR)
b5M15:Undefined b13M23:CD(DCD)
b6M16:Being sent b14M24:CS(CTS)
b7M17:Being received b15M25: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 send
byte count specified above.
Upper byte Lower byte
1 byte
(BFM#1001) lgnored 1 (31 H )
2 byte
(BFM#1002) lgnored 2 (32 H )
3 byte
(BFM#1003) lgnored 3 (33 H )
4 byte
(BFM#1004) lgnored 4 (34 H )
5 byte
(BFM#1005) lgnored 5 (35 H )
6 byte
(BFM#1006) lgnored 6 (36 H )
7 byte
(BFM#1007) lgnored 7 (37 H )
8 byte
(BFM#1008) lgnored 8 (38 H )
9 byte
(BFM#1009) lgnored 9 (39 H )

h ) Receive buffers
8-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.

10-24
FX communication FX2N-232IF 10

3 ) Example program
M8002 FNC 79 Transfer of communication format
K0 K0 H409F K1 (409F H BFM#0)
Initial TO
pulse Block No. BFM No. Transfer Number of
source transfer points
FNC 79 Transfer of receive upper limit byte count
K0 K2 K8 K1 (K 8 BFM#2)
TO
FNC 79 H02 Send header
K0 K4 K1 (02 H BFM#4)
TO (STX)

FNC 79 H03 Send terminator


K0 K6 K1 (03 H BFM#6)
TO (ETX)

FNC 79 H02 Receive header


K0 K8 K1 (02 H BFM#8)
TO (STX)

FNC 79 H03 Receive terminator


K0 K 10 K1 (03 H BFM#10)
TO (ETX)
X000
PLS M1 Send command
Send command input
M1 FNC 12 Send byte count
K9 D 200 (K9 D200)
MOV
FNC 12 HCA D 201 (1)
MOV
Program as follows
in the same way.
MOV HDF D202 ( 2 )
MOV HBF D203 ( 3 ) Send data (as many as 9 bytes)
MOV HBA D204 ( 4 )
MOV HDD D205 ( 5 ) [123456789]
MOV H20 D206 ( 6 )
MOV HC3 D207 ( 7 )
MOV HBD D208 ( 8 )
MOV HC4 D209 ( 9 )

Transfer of send byte count and send data


FNC 79 K0 K1000 D200 K 10 D200(K9) BFM#1000 D205( 5 ) BFM#1005
TO 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
M8000 M8003
M0 Send/receive enable
RUN Initial pulse NC contact
monitor
FNC 78
FROM
K0 K 28 K4M10 K1
Read of status
(BFM#28 b15 to b0 M25 to M10)
10
Block No. BFM No. Transfer Number of
destination transfer points
M10
Y0
Send completion Status monitor (upon necessity)
M13
Y1
Error occurrence
X001
M3 Error reset
Error reset input
M11 FNC 78 Read of receive buffers
K0 K2001 D301 K8 BFM#2001 D301 BFM#2005 D305
Receive FROM BFM#2002 D302 BFM#2006 D306
comple- BFM#2003 D303 BFM#2007 D307
tion BFM#2004 D304 BFM#2008 D308

M2 Receive completion reset command

M8000 FNC 79 Transfer of command


K0 K1 K1M0 K1 (M3 to M0 BFM#1 b3 to b0)
TO

10-25
FX communication FX2N-232IF 10

4 ) Operation chart

(M0) BFM#1 b0
Send/receive enable

(M1) BFM#1 b1
Send command
9 8
7 6 5
BFM#13 4 3
Number of remaining 2 1
send data 0
Send
Send completion status is also reset

#1002 lower
#1003 lower
#1004 lower
#1005 lower
#1006 lower
#1007 lower
#1008 lower
#1009 lower
#1001 lower
STX

STX
ETX
BFM#1001 to #1256 by next send command.
Send buffers

BFM#1000
(M10) BFM#28 b0 Send byte count
Send completion

7 8
BFM#14 4 5 6
Number of receive 2 3
buffers 0 1
8
6 7
3 4 5
BFM#2000 2
Receive byte count 0 1
Contents of receive buffers are also cleared. When not reset
Receive
#2002 lower
#2003 lower

#2006 lower

#2008 lower
#2001 lower

#2004 lower
#2005 lower

#2007 lower
STX

ETX

STX

ETX
BFM#2001 to #2256
Receive buffers
BFM#2
Receive upper
(M11) BFM#28 b1 limit byte count
Receive completion

BFM#1 b2
(M2) Receive completion reset
command

10-26
FX Series Programmable Controllers Optional programming port 11

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port 11

12 Diagnostics

A Further Information Manual List

B ASCII code Lists


FX Series Programmable Controllers Optional programming port 11
FX communication Optional programming port 11

11. Optional Programming Port


This section describes connection to peripheral equipment (programming tool, data access unit
and electronic operation terminal) using the FX2N-232-BD, FX1N-232-BD, FX0N-232ADP, FX1N-
422-BD, or FX2N-422-BD as well as cautions on communication. For the operating procedure of
each peripheral equipment and installation of each interface, refer to the corresponding manual.

11.1 FX2N-422-BD, FX1N-422-BD


When an FX2N-422-BD is installed on the FX2N Series, or when an FX1N-422-BD is installed on
FX1N or FX1S Series, the following peripheral equipment (programming tool, data access unit and
electronic 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 peripheral equip-
ment does not exceed the capacity of the 5V DC power of the FX2N, FX1N or FX1S.

Product Connecting cable Required 5V DC


FX-20P-E 180mA
FX-20P-CAB0 or FX-20P-CAB + FX-20P-CADP
FX-10P-E 120mA
Personal computer F2-232CAB-1 + FX-232AW(C) + (FX-422CAB0 or
220mA
(For programming tool) FX-422CAB + FX-20P-CADP) *1
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-50DU-CAB0 (-1M, -10M, -20M, -30M, L)
FX-40DU-ES, FX-40DU-TK-ES, or FX-40DU-CAB (-10M, -20M, -30M) + FX-20P- 0mA
FX-50DU-TK(S)-E CADP
F940GOT-SWD (LWD)-E,
FX-50DU-CAB0 (-1M, -10M, -20M, -30M, L) 0mA
F930GOT-SBD
F9GT-HCAB2-150 + F9GT-HCAB-3M (-10M)
F940GOT-SBD (LBD)-H or FX-50DU-CAB0 (-1M) + F9GT-HCNB + F9GT- 0mA
HCAB-3M (-10M)
GOT-A900 (Connecting direct
F9GT-CAB0 (-150, -10M) 0mA
CPU port type)

*1: When using other products or cables please check the product manual for required 5V DC 11
supply.

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.

11-1
FX communication Optional programming port 11

11.2 FX2N-232-BD FX1N-232BD and FX0N-232ADP


When an FX2N-232-BD or an FX0N-232ADP is installed on the FX2N, FX2NC Series, or when an
FX1N-232-BD is installed on FX1N or FX1S Series, a personal computer in which the following soft-
ware is supported can be connected to each port.
However, the FX2N-232-BD consumes 5V DC, 20 mA from the FX2N programmable controller, the
FX1N -232-BD consumes 5V DC, 20 mA from the FX1N, FX1S programmable controller and the
FX0N-232ADP consumes 5V DC, 200 mA from connected programmable controller.
Make sure that the current consumption of 5V DC for special extensions does not exceed the
capacity 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

RS232C connector of
FX2N-232-BD side Personal computer side
personal computer
F2-232CAB-1 Gender changer
FX-232CAB-1
D-SUB 9 pin
RS232C cross cable (D-SUB 9 pin to D-SUB 9 pin) see the reference
bellow
RS232C cross cable (D-SUB 25 pin to D-SUB 9 pin) see the reference
D-SUB 25 pin bellow
F2-232CAB-1
2 ) FX0N-232ADP
RS232C connector of
personal computer Cable

D-SUB 25 pin F2-232CAB


D-SUB 9 pin F2-232CAB-1

11-2
FX communication Optional programming port 11

Note: Reference
F2-232CAB-1 F2-232CAB RS232C crross cable RS232C crross cable
(D-SUB 25pinD-SUB 9pin) (D-SUB 9pinD-SUB 9pin)

1 1 1 4 1 1 7
2 2 2 2 5 8
2 2 2 3
3 3 3 3
3 3 3 2
25pin 5 9pin 5 5 25pin 4 9pin
25pin 25pin 6 9pin 4 6 9pin
6 4 6 6 7 5 5 5
7 5 7 7 20 6 6 4
20 8 7 7 1
20 6 20
1 8 8
8 SHELL SHELL Frame Frame

FX-232CAB-1

2 2
3 3
4 4
9pin 5 5 9pin
6 6
8 8

11.3 Cautions on Use


11.3.1 Cautions on Setting
Never set communication to the FX2N series using peripheral equipment or program. If communi-
cation is set in such a way, communication between peripheral equipment is disabled.

11.3.2 Cautions on use


Connect a programming tool (FX-10P, FX-20P, A7HGP/PHP, etc.) to either a connector built in
to the programmable controller, the connector of the FX2N-422-BD, the connector of the FX2N-
232-BD or the connector of the FX0N-232-ADP. If the programming tool is connected to both
connectors, the following phenomena may occur.
1 ) A program in the programmable controller may be different from a program in the program-
ming tool. If the program is modified or the set value of the timer, the counter, etc. is modi-
fied in this status, a part of the program may be damaged and the programmable controller 11
may malfunction.
2 ) If the sampling trace function provided in the programmable controller is used in both ports,
correct sampling trace results cannot be obtained.

11-3
FX communication Optional programming port 11

Memo

11-4
FX communication Diagnostics 12

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics 12

A Further Information Manual List

B ASCII code Lists


FX communication Diagnostics 12
FX communication Diagnostics 12

12. Diagnostics

12.1 Common Items


1 ) Check the connection with the communication unit of the programmable controller and the
option. When the connection is unstable, the communication cannot be corrected.
For the installation and the connection method, refer to the manual of the communication unit
of the option.
2 ) Check whether the VRRD or VRSC instruction is used in used in 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 by
FX-PCS/WIN-E, N:N network (D8173 to D8180) and parallel link (M8070,M8071) is suitable
for the usage or it checks. The communication is not correctly done if setting is not suitable
for the usage.
When each setting is changed, please turn off the power supply of the programmable con-
troller, and turn it on again.
4 ) When you use FX0N-485ADP and FX-485ADP, please the power supply for the drive must
be supplied correctly or check.

12

12-1
FX communication Diagnostics 12

12.2 N:N Network


12.2.1 Error Code
When station occur communication error, auxiliary relays (FX 2N: M8183 to M8191, FX0N: M504
to M511) of communication error is ON in the station. And the error code put into data registers
FX2N: D8211 to D8218, FX0N: D211 to D218). This is error code is following the table.
Error Error Check
code Meaning station station Description Checking points
After master station send request Check wiring, power of program-
01H Comms L M to save station, no answer passing mable controller, RUN/STOP state
time-out error comms time-out. (RUN is OK)
Station No. Station No. is not agreement
02H error L M between the master station and Check wiring
the slave station.
Communication counter is not
03H Comms L M agreement between the master Check wiring
counter error station and the slave station.
Check wiring, power of program-
04H Comms L M, L Communication format is not right mable controller, RUN/STOP state
format error from slave station. (RUN is OK), station No. setting
After slave station send answer to Check wiring, power of program-
11H Comms M L master station, master station do mable controller, RUN/STOP state
time-out error not send request to next slave sta- (RUN is OK)
tion.
Check wiring, power of program-
14H Comms M L Communication format is not right mable controller, RUN/STOP state
format error from master station. (RUN is OK), station No. setting
The station No. is not in this net-
21H No slave error L L *1 work. Check station No. setting.

Station No. Station No. is not agreement


22H error L L *1 between the master station and Check wiring
the slave station.
Communication counter is not
23H Comms L L *1 agreement between the master Check wiring
counter error station and the slave station.
Not receive When slave station receive Check wiring, power of program-
31H comms L L *2 request from master station before mable controller, RUN/STOP state
parameter error communication parameter. (RUN is OK)

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 (FX 2N: M8191,
FX0N: M503) is not turned off. When one of the communication error flag is turned on or if the
data communication flag is turned off, check the error code of data registers (FX2N: D8211 to
D8218, FX0N: D211 to D218).
Please see the following section 12.2.1.

12-2
FX communication Diagnostics 12

12.3 Parallel Link


12.3.1 Diagnostics
1 ) Check the status of the RD(RXD) LED and the SD(TXD) LED provided on each communica-
tion 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/extin-
guished (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 is
incorrect, correct it.
3 ) Make sure that the devices for the master station and the slave stations are handled cor-
rectly. If they are handled incorrectly, correct the program so that they are handled correctly.

12

12-3
FX communication Diagnostics 12

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 is
transmitted as two ASCII characters representing the hexadecimal codes ranging from 00H to
FFH.
If two or more errors occur simultaneously, the error code with the lowest number is transmitted.

Error code
Error description
(hexadecimal)
00H, 01H
02H Sum error
Protocol error (the communication protocol does not conform to the format selected
03H
with D8120)
04H, 05H
Character area error (the character area is incorrectly defined, or the specified com-
06H
mand is not available)
Character error (the data to be written to a device consists of ASCII codes other than
07H
hexadecimal codes)
08H09H
10H PC number error (the PC number is not set to FF or not available from this station)
11H17H
18H Remote error (remote run/stop is disabled)

12.4.2 Programmable Controller Error Code


With the FX series programmable controllers, the following errors are not transmitted using a
NAK, but instead are shown at the programmable controller by switching on special auxiliary
relay M8063, and storing the error code in special data register D8063.

Error code
Error description
(in D8063)
6301 Parity, overrun, framing error
Command failure receiving a command other than GW (global) when the station num-
6305
ber is FF
6306 Monitor timer over (message to be received is insufficient)

Because these errors are not transmitted it must be programmed at the computer so as to recog-
nize an error by using a watchdog timer or other monitor timer.

12-4
FX communication Diagnostics 12

12.4.3 Diagnostics
1 ) Check the status of the RD(RXD) LED and the SD(TXD) LED provided on each communica-
tion 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/extin-
guished (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 connec-
tion with the programmable controller.
2 ) Make sure that the communication procedure is performed correctly. If it is not performed
correctly, 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

12-5
FX communication Diagnostics 12

12.5 RS Instruction
12.5.1 Diagnostics
1 ) Check the status of the RD (RXD) LED and the SD (TXD) LED provided in an optional equip-
ment.
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 ) 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.
3 ) 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.
4 ) Make sure that the external equipment is correctly operating.
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 counterpart
equipment receives NAK.
Arrange the system so that the RS instruction is executed even if the counterpart equipment
receives NAK.

12-6
FX communication Diagnostics 12

12.6 FX2N-232IF
12.6.1 Error code
When an error occurs while data is sent or received, the BFM #28 b3 is set to ON and the error
code is saved in the BFM #29.

Code Description Causes and countermeasures


0 No error
Communication format such as baud rate is not
Receive parity error, overrun error, framing
1 matched.
error
Control timing is not matched.
2 Undefined
3 Defective receive character Receive data is not ASCII code.
Receive sum is not equal calculated sum result
4 Receive sum check error
(BFM #16).
Receive byte count exceeds 512+30 bytes.
Receive buffer overflow (only in interlink
5 Decrease receive upper byte count (BFM #2),
connection mode)
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.
Receive terminator is not placed in correct posi-
10 Receive terminator error
tion or not matched.
11 Undefined
12 Transmission sequence error Transmission sequence is not matched.

12.6.2 Diagnostics
1 ) Check the status of the POWER LED provided in the FX2N-232IF.
When it is lighted, the drive power is correctly supplied.
If it is extinguished, supply the drive power correctly.
2 ) Check the status of the SD LED and the RD LED provided in the FX2N-232IF.
If the RD LED is not lighted while data is received or the SD LED is not lighted while data is
sent, check the installation and the wiring.
When the RD LED is lighted while data is received or the SD LED is lighted 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 12
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.

12-7
FX communication Diagnostics 12

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-pro-
cedure protocol (RS instruction) or dedicated protocol is selected in the setting, clear the set-
ting using the peripheral equipment.
2 ) When an RS instruction is used in the program, delete the RS instruction, turn off the power
of 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, the
RS instruction has the priority.

12-8
FX communication Appebdix A

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List A

B ASCII code Lists


FX Series Programmable Controllers Appebdix A
FX communication Appendix A

Appendix A:
Further Information Manual List

Table A-1: Further Information Manual List


Manual name Manual No. Discription
This manual contains written hardware explanation of
FX1S Hardware Manual JY992D83901 wiring, installation and specification, etc. regarding the
FX1S Series programmable controller.
This manual contains written hardware explanation of
FX0 / FX0N Hardware Manual JY992D47501 wiring, installation and specification, etc. regarding the
FX1S and FX1N Series programmable controllers.
This manual contains written hardware explanation of
FX Hardware Manual JY992D47401 wiring, installation and specification, etc. regarding the
FX Series programmable controller.
This manual contains supplimentary data regarding
FX2C Supplementary Manual JY992D50201 the FX Series programmable controller Hardware
Manual
This manual contains written hardware explanation of
FX1N Hardware Manual JY992D88201 wiring, installation and specification, etc. regarding the
FX1N Series programmable controller.
This manual contains written hardware explanation of
FX2N Hardware Manual JY992D66301 wiring, installation and specification, etc. regarding the
FX2N Series programmable controller.
This manual contains written hardware explanation of
FX2NC Hardware Manual JY992D76401 wiring, installation and specification, etc. regarding the
FX2NC Series programmable controller.
This manual contens written instructions regarding the
FX Programming Manual JY992D48301 FX0, FX0S, FX0N, FX, FX2C, FX2N and FX2NC Series
programmable controllers.
This manual contens written instructions regarding the
FX Programming Manual JY992D88101 FX1S, FX1N, FX2N and FX2NC Series programmable
controllers.
This manual contains written hardware explanation of
FX / FX0N-485ADP Users
JY992D53201 installation and specification regarding the
Guidel
FX-485ADP and FX0N-485ADP.
This manual contains written hardware explanation of
FX-232ADP Users Guide JY992D48801 installation and specification regarding the
FX-232ADP.
This manual contains written hardware explanation of
FX0N-232ADP Users Guide JY992D51301 installation and specification regarding the
FX0N-232ADP.
This manual contains written hardware explanation of
FX2N-232-BD Users Guide JY992D66001 installation and specification regarding the
FX2N-232-BD.
This manual contains written hardware explanation of
FX2N-485-BD Hardware
JY992D73401 installation and specification regarding the
A
Manual
FX2N-485-BD.
This manual contains written hardware explanation of
FX2N-422-BD Users Guide JY992D66101 installation and specification regarding the
FX2N-422-BD.

A-1
FX communication Appendix A

Table A-1: Further Information Manual List


Manual name Manual No. Discription
This manual contains written hardware explanation of
FX1N-232-BD Hardware
JY992D84501 installation and specification regarding the
Manual
FX1N-232-BD.
This manual contains written hardware explanation of
FX1N-485-BD Hardware
JY992D84301 installation and specification regarding the FX1N-485-
Manual
BD.
This manual contains written hardware explanation of
FX1N-422-BD Users Guide JY992D84101 installation and specification regarding the
FX1N-422-BD.
This manual contains written hardware explanation of
FX-485-IF Hardware Manual JY992D81801
installation and specification regarding the FX-485-IF.

A-2
FX communication Appebdix B

1 Introduction

2 Wiring

3 Specifications

4 N:N network

5 Parallel link

6 Communication format (D8120)

7 Computer link

8 Commands (for computer link)

9 RS instruction

10 FX2N-232IF

11 Optional programming port

12 Diagnostics

A Further Information Manual List

B ASCII code Lists B


FX Series Programmable Controllers Appebdix B

B
FX communication Appendix B

Appendix B:
ASCII code Lists

Table B-1: ASCII code Lists


Hex
0 1 2 3 4 5 6 7
code
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

B-1
FX communication Appendix B

MEMO

B-2
USERS MANUAL
FX COMMUNICATION (RS-232C, RS-485)

HEAD OFFICE: MITSUBISHI DENKI BLDG MARUNOUCHI TOKYO 100-8310 TELEX: J24532 CABLE MELCO TOKYO
HIMEJI WORKS: 840, CHIYODA CHO, HIMEJI, JAPAN

Effective Mar. 2000


JY992D69901C Specification are subject
(MEE0003) to change without notice.

You might also like