2port-Efr Thu-6404
2port-Efr Thu-6404
2port-Efr Thu-6404
2PORT-EFR
2PORT-EFR THU-6404
Instruction Manual
2PORT-EFR THU-6404
Instruction
Manual
FOREWORD
Thank you very much for purchasing our 2PORT-EFR.
For safety use of this product, read carefully this manual and other related individual
instruction manuals. Furthermore, keep these manuals at an easily accessible place so as
to be ready for reading any time as necessary.
Distributor or dealer of this product is kindly requested to hand over this manual to end user
without fail.
The product specification, etc. are subject to change without prior notice due to better
modification.
Where a product applicable to the weapons and strategic materials (or services) stipulated
in the Foreign Exchange and Foreign Trade Control Act is exported to overseas from Japan,
it is necessary to get the export license from the Japanese Government.
In the event any defect due to our manufacture is found in our products during the warranty
period, we will repair or replace them at our discretion. We shall not be responsible for any
direct or indirect damages related to our products except as herein stated.
i
FOR SAFETY OPERATION
Before installing, operating, maintaining and checking, read carefully this Manual without fail
for proper and safety operation and work. Any operator and any maintenance man who
relate to this product (Programmable Controller) are requested to acquire the knowledge on
devices, safety information and cautions before being engaged in the operation and
maintenance. This Manual classifies the safety caution level into "WARNING" and
"CAUTION" using alert symbols as follows.
Don't overhaul the module and don't touch the module internals,
with the power switch kept ON.
Failure to observe this instruction could result in electric shock.
Don't touch the terminals with the power switch kept ON.
Failure to observe this instruction could result in electric shock.
Execute write during PC run (write during run) only when cyclic
operation of main equipment/machine is in shutdown.
Failure to observe this instruction could result in breakdown of
its device(s) and bodily injury from miss-operation, if any.
ii
Regarding safe-related signals and emergency stop circuit, etc.,
handle those signals in external units without through this
system.
iii
REVISION HISTORY OF OPERATION MANUAL
Operation manual revision No. is added as a part of Manual No. described on the cover sheet of
the manual.
T-756 * E
N: Japanese E: English
Series No. Revision symbol
Revision
Date of revision Content of revision
symbol
1 2007.5 The First edition printed
2 2011.4 The content of the description of the whole was reviewed.
3 2012.5 TOYODA brand logo added on the front cover
4 - -
5 - -
6 - -
7 - -
8 - -
9 - -
Added Reference 12
10 2019.4
Error correction
iv
Contents
・Introduction
・For safe use
・History of Revisions
・Related Manuals Formation
・Contents
Contents ............................................................................................................. 1
1 System configuration ......................................................................................................1-1
1.1 Outline......................................................................................................................1-1
1.2 Features ...................................................................................................................1-1
1.2.1 Feature of the FL-net function ...........................................................................1-1
1.2.2 Feature of the Ethernet function ........................................................................1-2
1.2.3 Feature of the FL Remote function ....................................................................1-3
1.3 Network configuration...............................................................................................1-4
1.4 System configuration................................................................................................1-7
1.5 Name and function of each part ...............................................................................1-8
1.6 Example of application ........................................................................................... 1-11
2 Functions of the 2PORT-EFR .........................................................................................2-1
2.1 Functions of the FL-net ............................................................................................2-1
2.1.1 Specifications for the FL-net ..............................................................................2-1
2.1.2 Specifications for Data Link ...............................................................................2-1
2.1.3 Data Link Method...............................................................................................2-2
2.1.4 Caution in Using I/O (X/Y) Area in Communication Area ...................................2-3
2.1.5 Message Server Function..................................................................................2-4
2.1.6 Message Client Function *1 ................................................................................2-4
2.1.7 Node Status Loading Function...........................................................................2-4
2.1.8 Monitor Function ................................................................................................2-5
2.1.9 Communication response time of FL-net ...........................................................2-6
2.1.10 Communication state confirmation function .....................................................2-7
2.1.11 Reading function of network management information ....................................2-9
2.2 Functions of the Ethernet .......................................................................................2-10
2.2.1 Specifications for the Ethernet .........................................................................2-10
2.2.2 Communication with Computer Link Method ...................................................2-10
2.2.3 Communication with File Memory Method....................................................... 2-11
2.2.4 PING Test Function..........................................................................................2-12
2.2.5 PING Test Procedure.......................................................................................2-12
2.2.6 Status Monitor Function ...................................................................................2-13
2.2.7 Communication state confirmation function .....................................................2-14
2.2.8 Communication using the general communication method .............................2-16
2.3. Functions of the FL Remote ..............................................................................2-17
2.3.1 Specifications for the FL Remote................................................................2-17
2.3.2 Network configuration.................................................................................2-21
2.3.3 Powering up sequence...............................................................................2-22
2.3.4 Communication reset .................................................................................2-23
2.3.5 Isolation function..............................................................................................2-24
2.3.6 Communication data response time ...........................................................2-26
3 Installation and Wiring.....................................................................................................3-1
3.1 Installation ................................................................................................................3-1
3.1.1 Environment for installation ...............................................................................3-1
3.1.2 Installation of the unit.........................................................................................3-1
3.2 FL-net/Ethernet/FL Remote wiring ...........................................................................3-2
3.3 LG Jumper ...............................................................................................................3-7
4 Initial Settings of the FL-net ............................................................................................4-1
4.1 Initial Setting Procedure ...........................................................................................4-1
4.2 Switch Settings.........................................................................................................4-2
4.3 I/O Module ID Code .................................................................................................4-4
4.4 Link Module Name ...................................................................................................4-5
4.5 Link Parameters .......................................................................................................4-5
4.5.1 Node No. ...........................................................................................................4-6
4.5.2 Node Name .......................................................................................................4-6
4.5.3 State of Output in Halt........................................................................................4-6
4.5.4 State of Input in Other Node Separation ............................................................4-6
4.5.5 Communication Methods ...................................................................................4-7
4.5.6 Data Link Parameters ........................................................................................4-8
4.5.7 Notes when CPU module is PC3J-CPU,PC3JNF,PC3JNM .............................4-19
4.6 Network Parameters...............................................................................................4-20
4.6.1 Network Address..............................................................................................4-20
4.6.2 Token Monitor Time-Out Time..........................................................................4-21
4.6.3 Minimum Permissible Frame Interval...............................................................4-22
5 Error Codes Used by the FL-net .....................................................................................5-1
5.1 Error Codes..............................................................................................................5-1
5.2 Error Messages Used by the CPU Module...............................................................5-4
5.2.1 Special Relays ...................................................................................................5-4
5.2.2 Special Registers ...............................................................................................5-5
5.3 Detection of abnormality by monitor function ...........................................................5-9
6 FL-net Message Functions .............................................................................................6-1
6.1 Message Server Function ........................................................................................6-1
6.1.1 Applicable TCD Codes and Contents of Response Data ...................................6-1
6.1.2 Remote programming / Remote monitor............................................................6-7
6.2 Message Client Function..........................................................................................6-8
6.2.1 Message Transmission Procedure.....................................................................6-8
6.2.2 Assembling the Sequence Program ...............................................................6-9
6.2.3 Examples of Sequence Programs ...................................................................6-14
6.3 Node Status Reading Function...............................................................................6-17
6.3.1 Node Status Data.............................................................................................6-17
6.3.2 Assembling the Sequence Program.................................................................6-19
7 Initial Settings of the Ethernet .........................................................................................7-1
7.1 Initial Setting Procedure ...........................................................................................7-1
7.2 I/O Module ID Code .................................................................................................7-1
7.3 Link Module Name ...................................................................................................7-2
7.4 I/O Parameters.........................................................................................................7-2
7.4.1 Description of I/O Parameters ...........................................................................7-2
7.4.2 Setting I/O Parameters ......................................................................................7-7
8 Opening/Closing the Ethernet Connections ....................................................................8-1
8.1 TCP Passive Opening/Closing .................................................................................8-1
8.2 TCP Active Opening/Closing ....................................................................................8-1
8.3 UDP Connection ......................................................................................................8-2
9 Ethernet Computer Linking Method ................................................................................9-1
9.1 Communication Format of Computer Link Method...................................................9-1
9.1.1 TOYOPUC Data Field Details ............................................................................9-1
9.2 Address List..............................................................................................................9-2
9.2.1 PC10 Standard mode, PC3 mode, PC2 Compatible mode................................9-2
9.2.2 PC10 mode........................................................................................................9-3
9.3 Command List ..........................................................................................................9-4
9.4 Limited Numbers of Read/Written Data Records and 2PORT-EFR Modules ...........9-6
9.5 Caution in Changing the CPU Module Parameters with Commands via Ethernet ...9-6
9.6 Ethernet Command/Response Data Format ............................................................9-7
10 Ethernet File Memory Method.....................................................................................10-1
10.1 Communication Format of File Memory Method ..................................................10-1
10.1.1 TOYOPUC Data Field Details ........................................................................10-1
10.2 File Memory Transmission ...................................................................................10-2
10.3 File Memory Reception ........................................................................................10-4
11 Ethernet and general communication method............................................................. 11-1
11.1 Communication format of the general communication method............................. 11-1
11.1.1 Sending data of the general communication method ..................................... 11-2
11.1.2 Receiving data of the general communication method .................................. 11-2
11.2 Switching to the general communication method ................................................. 11-3
11.3 General communication sending .......................................................................... 11-5
11.3.1 Sending procedures....................................................................................... 11-5
11.3.2 Operation upon sending error ........................................................................ 11-7
11.4 General communication receiving ........................................................................ 11-8
11.4.1 Receiving procedures .................................................................................... 11-8
11.4.2 Receiving separated data .............................................................................. 11-9
11.4.3 Receive data when the CPU has stopped running......................................... 11-9
11.4.4 Sequence program example ........................................................................ 11-10
11.4.5 Operation when file memory data reading is delayed .................................. 11-11
12 Warning by the Ethernet .............................................................................................12-1
12.1 Classification of Errors .........................................................................................12-1
12.2 Hardware Errors ...................................................................................................12-4
12.3 Link Parameter Error ............................................................................................12-4
12.4 Communication Errors..........................................................................................12-5
12.5 Connection Errors ................................................................................................12-8
12.5.1 Connection Anomaly Error Code Table..........................................................12-9
12.5.2 Error Response Data Error Code Table .......................................................12-13
13 Ethernet Communication Transaction Time ................................................................13-1
14 FL-Remote initialization ..............................................................................................14-1
14.1 Parameter settings ...............................................................................................14-1
14.2 I/O module setting example..................................................................................14-1
14.3 COLLECTION OF DIAGNOSIS DATA .................................................................14-6
14.3.1 Collection of Diagnosis Data by Link Parameter............................................14-7
14.3.2 General-purpose Status.................................................................................14-8
14.3.3 Error Record Reset / Arbitrary Reading Switch Format .................................14-9
14.3.4 Diagnosis Data Map ......................................................................................14-9
15. Warning by the FL-Remote........................................................................................15-1
15.1. Error information by CPU ....................................................................................15-2
15.2. Communication Status ........................................................................................15-7
15.3. Error Contents and Supposed Causes.............................................................. 15-11
16 Specifications..............................................................................................................16-1
Reference 1 Reading/Writing File Memory through SPR and SPW Commands
Reference 2 Ethernet File Memory Address Map
Reference 3 Transfer of Ethernet Control Output/Input Signals to Keep Relays
Reference 4 Ethernet Initial Sequence Program Sample
Reference 5 Ethernet IP Address, Gateway UP Address and Subnet Mask
Reference 6 Re-opening on Ethernet Function
Reference 7 Conducting PING Test via Windows-Installed PC
Reference 8 If an 2PORT-FER module that has replaced an older one does not
communicate with a personal computer:
Reference 9 Limitations on number of modules implemented due to power module
Reference 10 Andon controller link parameter settings
Reference 11 Ex number
1 System configuration
1.1 Outline
2PORT-EFR has two communication ports. By selecting with the switch on the front of the module, it is
possible to select either [Ethernet], [FL-net] or [FL remote] for each port.
1
If the FL-net function is selected, the TOYOPUC CPU can be connected with the FL-net (OPCN-2) 1
network.
Also, if the Ethernet function is selected, the TOYOPUC CPU can be connected with a PC, etc. via
2 2
Ethernet. Both TCP/IP and UDP/IP protocols are supported.
* 1. Based on the requirements of JEMA (Japan Electrical Manufacturers Associate), the MSTC (Manufacturing
Science and Technology Center) plays a central role so that any manufacturer can communicate via an FA
open network of specifications determined with the participation of major control device manufacturers.
FL-net (Ver 2.00 onwards) of this module corresponds with “Version 2” defined by JEMA.
* 2. TCP/IP is a highly reliable protocol that controls communication with other nodes.
UDP/IP acquires high speed through-put but there are cases where data being sent fails to reach its
destination due to signals colliding on the communication line. In such cases, the user themselves needs to
retry.
1.2 Features
1.2.1 Feature of the FL-net function
(1) Complies with FL-net (OPCN-2) protocol. Also corresponds with “Version 2” defined by JEMA.
(2) Able to communicate with a maximum of 254 stations. *1
(3) Uses a Master-free Token Ring method to perform communication between stations capable of
communicating at a specific point in time.
(4) Possible to have a data link with a maximum of 8192 link relay points*2 and 8192 link register words
*3
.
(5) As well as the N:N type, data link also supports 1:N type, making it possible to save link area and
standardize sequence programs.
(6) Supports a message server function, (a function that receives command messages sent from other
stations and responds), and allows reading/writing, etc. of data from areas other than data link.
(7) If PC3JL-CPU or later is used as the CPU module, a message client function that sends command
messages to other stations and reads responses is also available using sequence program
processing.
*1: As 250 to 254 are reserved for maintenance purposes, the node numbers which can be allocated to the
2PORT-EFR module are 1 to 249
*2: Maximum of 2048 points for everything other than CPU operation mode [PC3JG separation], [PC10
standard] and [PC10]. (Refer to 2.1.2 Specifications for Data Link)
*3: A maximum of 2048/6144 words are available for the link register using a selection switch. (Refer to 4.2
Switch Settings)
1 word = 2 bytes = 16 points
1-1
1.2.2 Feature of the Ethernet function
In Ethernet mode, data is exchanged between a computer and TOYOPUC using either [Computer
link method], [File memory method] or [General communication method]. A maximum of 8 ports are
available. Either TCP or UDP must be specified for each port.
If the CPU module is of the PC2J series, computer link method and file memory method can not be
used concurrently if the version is older than that shown in the table below. (An application
command error may occur if these methods are used concurrently)
PC2J V3.51
PC2 V4.90
PC2JC V4.10
PC2J16 V2.11
If both of the PORT-EFR communication ports are set to Ethernet, it cannot be used in PC3J-CPU.
The below table shows the number of Ethernet modules able to be set for each CPU.
CPU module
PC10G, PC10P, PC3JG,
PC3JG-P, PC3JP,
PC3JP-GP, PC3J-CPU
PC3JNM
PC3JD Ver 2.0 or later
Earlier than PC3JD Ver 1.10
PC3JM, PC3JL,MX,
PC2J series, PC2-CPU
Relay command 512 bytes or 256 words 512 bytes or 256 words
Other than relay command Max. data for each command 512 bytes or 256 words
No. of ethernet modules that
Multiple okay One only
can be set in parameters *1
■ Ethernet specifications
No. Item Specification
1 Physical layer 10BASE-T/100BASE-TX
2 Data transfer rate 10Mbps, 100Mbps*1
Maximum cable length Max. 100m(node to node(with a 1 to 1 connection),
3 node to HUB, HUB to HUB)
4 Communication function ① Computer link function
② File memory function
③ General communication function *2
5 No. of ports which can be Max. 8
opened
6 Computer link data capacity Max. 1K byte
7 File memory capacity Transmission 2K bytes
Receipt 2K bytes
*1 The designated HUB is auto negotiation. Transmission rate is 100Mbps if the devices using auto negotiation are connected.
1-2
1.2.3 Feature of the FL Remote function
FL Remote specifications
Item Specification
Physical layer 10BASE-T/100BASE-TX
Data transfer rate 10Mbps, 100Mbps*1
Maximum cable
length Max. 100m(Between master and HUB, master and slave(1 to 1 connection),
slave and HUB, HUB and HUB)
Total extension length: Max. 2100m(HUB:Max 20 units)
Max. no. of
64 units(1 master, 63 slaves)
connectable nodes
Node address Slave:01 to 63
No of I/O points Input: Max. 2048 points, output: Max. 2048 points
No. of I/O points for
Input: Max. 64 points, output: Max. 64 points
per slave
I/O allocation Max. unit of 8 points
Link area X・Y,M,L,EX・EY,EM,EL,GX/GY,GM
Communication
I/O communication
function
*1 The designated HUB is auto negotiation. Transmission rate is 100Mbps if the devices using auto negotiation are connected.
1-3
1.3 Network configuration
The below is one example of Ethernet network configuration.
2PORT-EFR module
LAN cable
HUB HUB
HUB
LAN cable
■ Description of devices
Name Explanation
Cable connecting the 2PORT-EFR module and HUB.
LAN cable
Maximum length of 100 meters.
1-4
The below is one example of FL-net network configuration.
2PORT-EFR module
Designated HUB
Designated HUB
Designated HUB
Designated
LAN cable Designated
LAN cable
■ Description of devices
Name Explanation
1-5
FL Remote network configuration is shown below.
2PORT-EFR
module
Switching HUB
・・・
Slave
Switch
Lamps
■ Description of devices
Name Explanation
Nodes have both a slave which connections input/output devices and a master
Node
which links the slaves together.
There is one master for every network.
The master and slave positions are not fixed and could be at either of the node
positions shown in the figure above.
FL Remote M is a master module.
1-6
1.4 System configuration
Below is an example of the configuration when a 2PORT-EFR module is connected to a PC10
system.
Basic rack
PC with
2PORT-EFR PC10G USB cable
Windows2000/XP
Extension rack
Program software
Base unit PCwin※3
I/O cable
LAN cable ※1
Base unit
LAN cable ※1
SW-HUB※2
FL-net system
1-7
1.5 Name and function of each part
110
105 35
2PORT-EFR
(1) TxD RxD
1 3 5 7
(2)
2 4 6 8 STATUS
(5)
(6)
(3)
(4)
130
(7)
1.00
(1) Sending and TxD illuminates when the module sends data and RxD illuminates when the
receiving LEDs module receives data
(2) Status LED In FL-net mode:
Node numbers (station numbers) are shown as 2 digit hexadecimal values
during normal communication. When an error occurs, an error code is
displayed. If no other station exists on the FL-net network and no
communication is being performed then --- is displayed.
In Ethernet mode:
Connections which are open are displayed as shown in the figure to the
right during normal communication. (The LED illuminates when open.)
When an error occurs, an error code is displayed. (See section 11).
For FL Remote
Master node numbers are shown as 2 digit hexadecimal values during
normal communication. When an error occurs, an error code is displayed.
1-8
(3) Module setting Changes the operation mode and communication speed of .
switch on the L1 ・Switch SW1-1/ SW1-2/ SW1-3
2PORT-EFR has 5 modes; FL-net mode (8K), FL-net mode (16K), FL-net
side
mode (32K), Ethernet mode and FL Remote.
321
1・2・3 off Relay link・・・・2048 pts(128 words)*1 C9 8K byte
Register link・・・2048 words
1 on
321
1・3 on
FL remote mode B8 4K byte
2 off
・Switches SW1-4
Set communication speed
Switch settings Transmission rate
OFF 10Mbps
ON Auto negotiation
Module setting
Same as (3) “Change between L1-side operation mode and communication
(4) switch on the L2
speed”.
side
2PORT-EFR can be implemented on any rack/slot however it also
exclusively occupies a quasi rack other than where it is implemented. This
Rack number exclusively occupied rack no. is set using switch 5. L1 is allocated to slot 0
(5)
switch of the selected rack no. and L2 to slot 1.
8 to E can be selected for the rack no. switch. (Please do not select other
numbers.)
Changes between status LED displays. By turning it to the L1 side, the L1
Display
(6) status is displayed, and by turning it to the L2 side, the L2 status is
changeover switch
displayed.
1-9
(7) Communication LED1. Displays hardware status
connector Green solid:Hardware normal
Red solid:Hardware error occurring
L1 Off:Program not operating
LED1
LED2. Displays communication status
・For Ethernet/FL-net
LED2
Green solid: 100 Mbps communication established
L2 Green flashing: 100 Mbps communicating
LED2
Orange solid: 10 Mbps communication established
Orange flashing: 10 Mbps communicating
LED1
Red solid: Link parameter error
Red flashing: Connection error/node overlap
Off: Cable not connected
・For FL remote
Green solid: Remote operating
Green flashing: FL participating
Red solid: Link parameter error
Red flashing: Communication error
Green/red alternating: Setting error
Off: Cable not connected
Jumper pin connecting the communication line shield and the FG of the
PC.
1-10
1.6 Example of application
This section explains about the parameter setting method (using PCwin Ver. 10 or later) in the case that
L1 is used as Ethernet and L2 as FL Remote. Rack no. will be virtually implemented.
1. Line the rotary switch up with the number of the rack that is to be virtually implemented.
2PORT-EFR
TxD RxD
1 3 5 7
2 4 6 8 STATUS
1. Start PCwin, select I/O module from the parameter settings and line the rack no. up with 8.
L1
L2
3. In link settings, set the link parameters as shown below. Please refer to “14.2 I/O module
settings” for detailed settings.
1-11
Precautions when using multiple 2PORT-EFR modules
If multiple 2PORT-EFR modules or 2PORT-LINK modules are used on one CPU module, please make
sure that the the same 2PORT-EFR or 2PORT-LINK number is not used twice. If it is, error no. 39 will
occur.
1-12
2 Functions of the 2PORT-EFR
connected.
*2 Values shown in parentheses include the number of nodes for maintenance.
If 20 FE-SWH08 units are used, the maximum node number is 122.
2-1
2.1.3 Data Link Method
The data link method supports N:N (N to N) and 1:N (1 to N) connections. With N:N
connections, the transmission area for a node (station) is the reception area for another node and
data is shared by different nodes as shown below.
With 1:N connections, communication is performed between a node designated as 1:N Master
and those as 1:N Satellites. No data link is established among 1:N Satellites.
Reception area
Reception area
Nodes with N:N connections and those with 1:N connections may coexist on a single network.
N:N or N:N or
1:N Master 1:N Master 1:N Satellite 1:N Satellite
Reception area Transmission area Reception area Reception area
Transmission area Reception area Transmission area Transmission area
2-2
2.1.4 Caution in Using I/O (X/Y) Area in Communication Area
(1) Take care not to overlap with I/O addresses of the I/O module connected with the CPU.
○
Acceptable
X/Y7FF X/Y7FF X/Y7FF
×
Not acceptable
X/Y7FF X/Y7FF X/Y7FF
(2) I/O refresh (RIO: FUN No. = 280), I refresh (RI: Fun No. = 281), and O refresh (RO:
Fun No. = 282) for instructions cannot be used in the communication area.
(3) The area used as transmission area is saved as input area in the CPU. Therefore, it
is indicated as X when the communication area is monitored with I/O monitor.
2-3
2.1.5 Message Server Function
With this function, a response is made to a command message sent from another node.
The command and response are automatically processed by the 2PORT-EFR module and CPU
module. Parameter settings and sequence program processes are not necessary for this function.
For detail, see section 6-1.
Command
Response
With this function, a command message is sent to another node and the response to that
message is received.
The sequence program generates the command data, gives instruction to send it to the
2PORT-EFR, and loads the response data from the 2PORT-EFR module to the register.
For detail, see section 6-2.
Command
Response
The status of another node participating in the FL-net communication may be loaded to the
register with the sequence program.
For detail, see section 6-3.
(*1: The message client and node status loading functions are available with CPU modules of
the following versions.)
CPU Module Version
PC10G 1.00 -
PC10P 1.00 -
PC3JG,PC3JG-P 1.30 -
PC3JP,PC3JP-GP 1.70 -
PC3JD 2.10 -
PC3JM 2.00 -
PC3JL 2.00 -
AF2K 2.00 -
MX 2.00 -
2-4
2.1.8 Monitor Function
The nodes (stations Nos. 1 to 254) participating in the FL-net communication can be
monitored with special registers S3*0 to S3*F. Correspondence between the station No.
(hexadecimal) and the bit address is shown below.
Moreover, when the version of FL-net is 1.4 or more, the own node number (hexadecimal)
is stored in special register S3xF.
MSB LSB
F E D C B A 9 8 7 6 5 4 3 2 1 0
S3*0 0F 0E 0D 0C 0B 0A 09 08 07 06 05 04 03 02 01
S3*1 1F 1E 1D 1C 1B 1A 19 18 17 16 15 14 13 12 11 10
S3*2 2F 2E 2D 2C 2B 2A 29 28 27 26 25 24 23 22 21 20
S3*3 3F 3E 3D 3C 3B 3A 39 38 37 36 35 34 33 32 31 30
S3*4 4F 4E 4D 4C 4B 4A 49 48 47 46 45 44 43 42 41 40
S3*5 5F 5E 5D 5C 5B 5A 59 58 57 56 55 54 53 52 51 50
S3*6 6F 6E 6D 6C 6B 6A 69 68 67 66 65 64 63 62 61 60
S3*7 7F 7E 7D 7C 7B 7A 79 78 77 76 75 74 73 72 71 70
S3*8 8F 8E 8D 8C 8B 8A 89 88 87 86 85 84 83 82 81 80
S3*9 9F 9E 9D 9C 9B 9A 99 98 97 96 95 94 93 92 91 90
S3*A AF AE AD AC AB AA A9 A8
S3*B BF BE BD BC BB BA B9 B8 B7 B6 B5 B4 B3 B2 B1 B0
S3*C CF CE CD CC CB CA C9 C8 C7 C6 C5 C4 C3 C2 C1 C0
S3*D DF DE DD DC DB DA D9 D8 D7 D6 D5 D4 D3 D2 D1 D0
S3*E EF EE ED EC EB EA E9 E8 E7 E6 E5 E4 E3 E2 E1 E0
S3*F FE FD FC FB FA F9 F8 F7 F6 F5 F4 F3 F2 F1 F0
・
・
・
S3xF Own node number(hexadecimal)
■ “*” and”x” in the special register No. is determined by the link No.
Link No. 1 2 3 4 5 6 7 8
* 0 2 4 6 8 A C E
x 1 3 5 7 9 B D F
If the link No. of the 2PORT-EFR module is 3, for example, the station with node No. 85 (55h)
may be monitored by checking the fifth bit of S355.
The above area is cleared with reset/start or the power supply switching off.
Moreover, 2PORT-EFR secedes from the communication line, and starts the communication
joining processing by reset again
2-5
2.1.9 Communication response time of FL-net
Response time is time from turning on the input by the transmission side PLC to the output by the
reception side PLC turns on..( when communicating by the module(TOYOPUC 2PORT-EFR))
2-6
2.1.10 Communication state confirmation function
This function confirms the state of the line. This function reads the following content among Log information on
the node.
(1)Reissued tokens
(2)Token retention time-outs
(3)Token monitor time-outs
Specifies the register recording the link No. with former 4 bits and the number
Link availability flag *1 of data bytes to be transmitted with latter 12 bits.
The register that sets the reading address (4000h fixation) from
Requisite for writing the FL/ET-T-V2H module is specified.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
2-7
Example of programming sequence that reads communication to register D0000-D0005
V006
Link No1, 12Bytes
WMOV 100C -> R103
Communication state
WMOV 4000 -> R104
read address(4000h
fixation)
The above-mentioned value cannot be called the state of the line excellence when the
count improvement is regularly done.
Please improve it referring to the following examples of measures.
2-8
2.1.11 Reading function of network management information
Specifies the register recording the link No. with former 4 bits and the number
Link availability flag *1 of data bytes to be transmitted with latter 12 bits.
The register that sets the reading address (8000h fixation) from
Requisite for writing the FL/ET-T-V2H module is specified.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
V006
Link No1, 8Bytes
WMOV 1008 -> R103
Communication state
WMOV 8000 -> R104
read address(8000h
fixation)
2-9
2.2 Functions of the Ethernet
Transmit a command from another node to read/write data in the CPU module. Since the
2PORT-EFR module is responsible for command analysis and communication with the CPU
module, no sequence program is required for data exchange.
Another node may be a personal computer or host and data exchange between TOYOPUCs is
not attainable.
For detail, see section 6.
2PORT-EFR module
CPU module (Ethernet)
Another node
Command Command
Analysis
Response Response
2-10
2.2.3 Communication with File Memory Method
Use instructions of the sequence program such as SPR (to read the file memory) and SPW (to
write the file memory) to read/write the file memory in the 2PORT-EFR module for
transmission/recepetion.
Another node may be any device other than a personal computer or host and data exchange
between 2PORT-EFR modules of a PLC is attainable. (No communication is possible with
Ethernet modules offered by other manufacturers.)
For detail, see section 10.
2PORT-EFR module
CPU module (Ethernet) Another node
2-11
2.2.4 PING Test Function
Conduct a PING Test to verify that the communication circuit is connected with a communicatee/
communicator and that communication is attainable normally.
If the module fails in the PING test, the following causes are suspected.
・ The cable is disconnected or poorly connected.
・ The transceiver power supply is disconnected from the terminal block on the 2PORT-EFR
module.
・ A communication device such as transceiver between the 2PORT-EFR module and the other
node is out of order.
・ The other mode has not been started.
・ Both nodes have the same IP address.
・ Both nodes have the same network ID in the IP address. (See Attachment 5.)
Set any of the following addresses as defined by the link No. to which the FL/NT-net-5 module
has been assigned, to the IP address of the other node by hexadecimal notation using peripheral
equipment or such.
If the 2PORT-EFR module has been assigned to link No. 1 and the IP address of the other node
is 172.16.93.133, for example, set S31C to '5D85' and S31D to 'AC10.'
After completion of the PING test, change these values back to 0000.
The PING test is performed every two seconds and results are expressed by the 3rd and 4th bits
at file memory address 106 (see Attachment 2). The 3rd bit turns on if the PING test is
successfully completed and the 4th bit turns on if not. Results of the PING test may also be
found from the status monitor area (see section 2-2-6).
A sequence program using an SPR command is required to load data from the file memory (see
Attachments 1 and 2).
2-12
2.2.6 Status Monitor Function
The module status may be monitored by checking special registers S300's of the CPU module.
The addresses to be monitored are determined by the link No. as shown below.
The status of the control flag in the file memory and connection error codes, if any, may be
monitored by checking this area using peripheral equipment.
F E D C B A 9 8 7 6 5 4 3 2 1 0
S3#0 CN8 Request for active open CN1 0 0 0 0 0 0 0 *1
S3#1 CN8 Request for file memory reception CN1 CN8 Request for file memory transmission CN1
S3#2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 *3 *2
S3#3 CN8 Open normal CN1 0 0 0 0 0 0 *5 *4
S3#4 CN8 File memory transmission complete CN1 CN8 Connection error CN1
S3#5 0 0 0 0 *9 *8 *7 *6 CN8 File memory reception complete CN1
S3#6 4th digit of own Ethernet address *10 5th digit of own Ethernet address *10
S3#7 6th digit of own Ethernet address *10 CN8 General communication CN1
S3#8 Connection 1: Connection error code
S3#9 Connection 2: Connection error code
S3#A Connection 3: Connection error code
S3#B Connection 4: Connection error code
S3#C Connection 5: Connection error code
S3#D Connection 6: Connection error code
S3#E Connection 7: Connection error code
S3#F Connection 8: Connection error code
*1: Request for initialization *2: Error log reception confirmed
*3: ICMP log reception confirmed *4: Normally initialized
*5: Abnormally initialized *6: Error log received
*7: ICMP log received *8: PING passed *9: PING failed
*10: Former 3 digits of Ethernet address are fixed to 00.60.53.
2-13
2.2.7 Communication state confirmation function
Sending and receiving packet information can be read to the register of CPU module by this function.
These information is read by the SPR command.
Specifies the register recording the link No. with former 4 bits and the number
Link availability flag *1 of data bytes to be transmitted with latter 12 bits.
The register that sets the reading address (0200h fixation) from
Requisite for writing the FL/ET-T-V2H module is specified.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
V006
Link No1, 24Bytes
WMOV 1018 -> R103
Communication state
WMOV 0200 -> R104
read address(0200h
fixation)
2-14
Response format of example of circuit
Address Data size Contents
+0 (D0201 D0200) 4 Byte Number of receiving packets
+4 (D0203 D0202) 4 Byte Number of receiving errors
+8 (D0205 D0204) 4 Byte Number of transmission packets
+C (D0207 D0206) 4 Byte Number of transmission errors
The numbers of counts other than A and B are excellent and when the count improvement is regularly
done, the state of the network is not excellent. Please improve it referring to the following examples of
measures.
1) The communications cable is separated from the power line and established.
2) LAN cable uses a specified cable.
3) Recommendation HUB is used.
4) When the other party node is grounded, the pin of the jumper in the module is
removed.
5) When the transmission rate is 100Mbps, it changes to 10Mbps fixation (SW1-4=OFF).
2-15
2.2.8 Communication using the general communication method
Sends and receives data using a sequence program application command SPR (file memory read),
SPW (file memory write) to read or write the file memories in the 2PORT-EFR module.
The general communication function differs from file memory communication in the sense that the
TCP/UDP data section is free formatted, meaning that Ethernet devices of a fixed communication
format can be connected.
However, there are no transfer control procedures, and checking for mistakes, etc is the
responsibility of the user.
Please see Chapter 11 for details. Other node
PC
TOYOPUC
2PORT-EFR module Other companies’
CPU module Ethernet devices
(Ethernet function)
Connection 1
SPR Data Recei Send
SPR
receiving
2-16
2.3. Functions of the FL Remote
are connected.
24VDC
Max. 100m
Master
▪ ▪ ▪ Max 100m
2PORT-EFR
Max 100m
・・・
Slave:Max. 63 units
2-17
(2)Link numbers and areas
The user can select link parameters at their discretion from links 1 to 8 of programs
1 to 3.
If internal relays (M) or link relays (L) are set in the link area, the program relay
for which link parameters were set becomes the link area. Input/output (X, Y) and
extension areas (EX and EY, EM, EL, GX and GY, GM) are common to all programs.
Extension input/output(EL)
2-18
(3)Precautions when using inputs and outputs (X, Y) in the communication area
1. Please be careful not to overlap the I/O addresses of the I/O module implemented on
the CPU and those of the communication area.
○
G
o
o
d
×
N
o
t
p
o
s
s
i
b
l
X/Y7FF X/Y7FF X/Y7FF e
2. The application commands, I/O refresh (RIO: FUN No. = 280), input refresh
(RI: Fun No. = 281) and output refresh (RO: Fun No. = 282), cannot be used in the
communication area.
3. If “Y” is used in communication area addresses, the CPU internal address display
will all be shown as “X”. Therefore, if the communication area is monitored on an I/O
monitor, the display will read “x”.
2-19
(4)Display
There are two FL Remote-M status display lamps, LED1 and LED2, which are
green and red respectively. These lamps illuminate solid, flash or go out in the
below situations.
2-20
2.3.2 Network configuration
The FL Remote network is configured as shown below.
Switching HUB:Max. 20
Master
24VDC
2PORT-EFR
TR
1
・・・ Max:100m
Slave:Max. 63 units
■Description of devices
Name Explanation
Nodes have both a slave which connections input/output devices and a master
Node
which links the slaves together.
There is one master for each network.
The master and slave positions are not fixed and could be in either of the node
positions shown in the figure above.
FL Remote M is a master module.
FL Remote
PC10G built-in link, 2PORT-EFR, etc are used as the FL Remote master.
master
Cable Please use JTEKT’s specified LAN cable. *1
Straight cable is used. However, cross cable is used for 1 to 1 connections.
Communication
If multiple slaves are connected, please use JTEKT’s designated switching HUB
method
(*2).
Power for communication is supplied to each node.
Communicaton For communication power, please apply 24V and 0V to terminal blocks with +, -
power on them.
II/O power For I/O power, please apply 24V and 0V to terminal blocks with +V, -V on them.
Please make the IO power and communication power separate systems.
* 1 Refer to 3.2 FL-net/Ethernet/FL Remote wiring.
*2 Please use FE-SWH05/08 (Jtekt) as the HUB.
2-21
2.3.3 Powering up sequence
When turning on power, either turn on the slaves first then the master or both at the same
time.
A communication error may occur if the master is turned on before the slaves.
Communication errors will also occur if slaves are turned off after communication has begun.
Powering up Result
sequence
Master → slave ×
Slave → master ○
Simultaneously ○
Even if the master receives no response form a slave that has been powered
up, it will not judge it as an error for the first 18 seconds.
During this time, the master performs a communication recovery operation. If
communication isn’t recovered after 18 seconds, the master alerts the CPU of
a communication error.
2-22
2.3.4 Communication reset
Communication reset is a function to reopen communication in the event that
communication has stopped due to a communication error.
By changing the communication reset special relay from [OFF] to [ON], it is possible to
reset communication.
The I/O addresses of the communication reset special relay per link number are as shown in
the table below.
Note 1: Communication reset is only enabled when the special relay is on.
Note 2: Communication reset is only enabled when a communication error is occurring. It is disabled when
communication is normal.
2-23
■ Example of a communication reset circuit
Reset circuit is not necessary for the first 18 seconds after power is turned on as the
communication recovery operation is performed.
The below diagram is an example of a circuit to recover communication in the event of errors.
Communication reset
Communication error
VAA
Note 2: The above circuit is not valid if [CPU RUN STOP] has been set for communication
errors.
2-24
slave is cleared. Once the error is cleared and a normal response is received, the exchange
of OFF data will begin. During this time I/O data will be communicated with other slaves as
normal.
In order to report that a communication error has occurred on the isolated slave the
master will display error code D9 (transfer error) and number of the faulty slave to the
7-segment display unit.
(4) Other
If a communication error occurs on a slave not designated as being isolated, the master will
report the error and cease communication with all slaves.
S3*C 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 -
S3*D 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
S3*E 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
S3*F 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
2-25
2.3.6 Communication data response time
(1)Configuration
Slaves are all FRMT (TCU-6405, TCU-6406, TCU-6407). (Communication speed = 100 Mbps)
Refresh Communication
CPU processing 2PORT-EFR processing
(Master)
Input X120
Output Y100
(2)Program
X120 Y100
The time taken from slave input to slave output is the communication data response time.
(3) Formula
Average response time = 20 + 2.7 x (No. of slaves) + (input response time + output response time)
+ (scan time) x 2 [ms]
Maximum response time = 30 + 3.7 × (No. of slaves) + (input response time + output response
time) + (scan time) ×2 [ms]
2-26
3 Installation and Wiring
3.1 Installation
If this module is used in the above environments, please install it in a place where favorable conditions can
be maintained, i.e. storing in a sealed control panel, etc. Please do not leave the control panel door open.
Furthermore, if a fan or the like is used in the control panel, please install the module so it is not directly
exposed to the wind. Please be aware that if the wind directly comes in contact with the module, a large
quantity of dust, etc. may adhere to the surface, preventing accurate measurement.
50mm or more
2PORT‐EFR
TXD RXD
1 3 5 7
2 4 6 8 STATUS
CPU/SEL.
POWER 0 RACK 1
NO.
8~E
SW2 SW1
L1
STATUS LED
L2
L1
L2
*.**
50mm or more
3-1
3.2 FL-net/Ethernet/FL Remote wiring
Connect the 2PORT-EFR(FL-net /Ethernet/ FL Remote) module and the other node using
a cross cable.
1 3 5 7
2 4 6 8 STATUS
RACK
NO.
8~E
Designated cross
SW2 SW1
L1
i bl
STATUS LED
L2
L1
L2 Designated straight
bl
*.**
3-2
When connecting through a HUB
Connect 2PORT-EFR (FL-net/Ethernet/FL Remote) and the hub using a straight cable.
Connect one hub to another hub using cross-cable or straight cable. However, do
not combine FL-net/Ethernet/FL Remote on the same system network.
DC
(FL Remote configuration)
24V
100m MAX
2PORT-EFR
100m MAX
DC
24V
FRMT
100m MAX
DC
24V
(Separate I/O power and unit power)
(FL-net /Ethernet configuration)
DC
24V
100m MAX
2PORT-EFR
100m MAX
100m MAX
3-3
Cable installation
Please be aware of the following points when installing the cable.
1. Make sure when laying the cable not to pull too tight.
×
Stretching due to excessive pulling
2. Make the turning radius of the fixed portion 4 times or more the OD of the cable.
4 times cable OD
2 times cable OD
3-4
3. When securing the cable, do not make the cable tie, etc too tight.
Crushed cable
Twisted cable
×
×
3-5
6. Keep cables away from noise generating sources.
Keep the communication cable and HUB as far away as possible from noise sources such as
welding equipment and motor drive circuits and high current power cables.
Noise Noise
generat generat
Communication cable
HUB
HUB storage box(metal)
Communication Duct(metal)
3-6
3.3 LG Jumper
(1) The role of the LG jumper
The LG jumper is a jumper pin which connects the shield of a communication line, and the PC
FG.
If LG jumper is set to "ON" (short), the noise guided to the LAN cable is dropped on FG, and
noise resistance can be improved. Normally, please use the LG jumper in an "ON" state.
LG jumper LG jumper
ON (short)
FG FG
ON (short)
3-7
4 Initial Settings of the FL-net
Start
4-1
4.2 Switch Settings
Set the link memory capacity using the switches at the front of the module.
The I/O module ID code changes as the switch positions change.
I/O module Link memory Data link capacity (maximum number of total
Switch positions
ID code capacity words in reception and transmission areas)
1 off
Relay link: 2048 points (128 words) (*2)
3 2 1
2 off C9 8 kbytes
Register link: 2048 words (*1)
3 off
1 off,
Relay link: 2048 points (128 words) (*2)
3 2 1
2 on D9 16 kbytes
Register link: 6144 words (*1)
3 off
1 on
Relay link: 2048 points (128 words) (*2)
3 2 1
2 on E9 32 kbytes
Register link: 8192 words (*1)
3 off
1 on,
3 2 1
If the link memory capacity is set to 16 or 32 kbytes for a CPU module of another version, the
module does not normally operate.
The module must be powered off before changing the switch positions.
Please refer to “Reference 12 Link memory capacity”.
4-2
4.3 I/O Module ID Code
Specify the I/O module ID code on the 'I/O module setup' window under 'Parameter' of
Hellowin. The ID code should correspond with the switch positions at the front of the module.
If the switch positions and parameter setting are inconsistent, error 48 'I/O Table Inconsistent'
appears on the CPU module.
4-3
4.4 Link Module Name
Select the link No. to be assigned to the 2PORT-EFR module and specify the rack No., slot No.
and link module name on the 'Link Parameter' window under 'Parameter' of Hellowin.
If the switch positions, I/O module ID code, capacity in the link module name (8KB, 16 KB, or
32 KB) are inconsistent, a link parameter error occurs.
Example of setting
These parameter values are usually specified by the network administrator at the end user.
4-4
4.5.1 Node No.
Specify the station No. of the 2PORT-EFR module between 1 and159, 168 and 249.
It should not be the same with another node (FL-net station).
If two or more nodes have the same No., the node that attempted later to participate in the
communication cannot do so. In this case, error code E7 (node No. duplicated) appears on the
LED display at the front of the module.
Enter the node name of the 2PORT-EFR module using up to 10 alphanumeric one-byte
characters. This field may be kept blank.
The specified node name is read as response data to the 'Request for Reading Network
Parameters' command from the host computer or such.
Specify the status of relay link and register link outputs with the CPU module not running. If
'Clear' is checked, the data sent through the data link to your module becomes all zeros when
the CPU module stops running. If 'Hold' is checked, the same data is continuously sent as
directly before the CPU module stops running.
Specify, for the relay link and register link, how to process the data received from another node
when that node is separated from the network.
If 'Clear' is checked, the data received from the separated node becomes all zeros. If 'Hold' is
checked, the data remains the same as directly before the node is separated.
Note:
The data sent from another node not participating in the communication is kept 00. If your
module participates in the communication after a participant node leaves the communication,
the data sent from that node is also kept 00.
If your module and another node participate in the communication at the same time and the
other node leaves after that, the data status depends on the setting of 'State of input in other
node separation.'
4-5
4.5.5 Communication Methods
Select the data link method from 'N:N or 1:N (Master),' '1:N (Satellite),' or 'No Datalink
(Message only).'
Reception area
Reception area
4-6
4.5.6 Data Link Parameters
If 'N:N or 1:N (Master)' or '1:N (Satellite)' has been selected, click the DataLink button and set
communication parameters.
For the data linkable area, see 2-2 'Data Link Specifications.'
On the FL-net network, data is transmitted and received via the 'common memory,' a virtual
memory space shared by all nodes participating in the communication.
As a node transmits data to the common memory, the data is received by other nodes and shared
by the respective nodes.
The destination address on the common memory and data size may be specified in units of word
(16 bits) for each node. Order of node No. does not coincide with that of destination address.
Example:
Common memory
Address 0000 →
Transmission area for node 1
Areas on the common memory to which data is to be transmitted from different nodes should be
not be overlapped. If they are overlapped, E8 (relay link area overlap) or E9 (register link
area overlap) appears on the LED display at the front of the node that participated in the
communication later.
Example:
Transmission
area for node 1
Transmissions areas
for nodes 2 and 3 are
Transmission overlapped.
area for node 10 Communication error
Transmission occurs with node 2.
Transmission area for node 3
area for node 2
4-7
In the 'N:N or 1:N (Master)' mode, it is necessary to specify the data range starting at the top of
the common memory, the corresponding top address on the CPU module register, and the top
address and size of the area to which data is transmitted from your module, using the following
four parameters.
Common memory address 0000 corresponds to the top address of the link area.
PLC internal register Common memory
(1) Address 0000
Reception
area
(3)
(2) Transmission
(4) area
Reception
area
Note:
The node No., the destination address on the common memory, and data size are usually
determined by the network administrator at the end user.
4-8
Example 1
①
②
③
Correspondence between the register data and the common memory with the above parameter
settings is shown below.
Address
PLC internal register Common memory
Address
L000 0000
Reception
area
L100 0010
16 Transmission
words area
64 words L1FF 001F
Reception
area
L3FF 003F
①
②
③
Correspondence between the register data and the common memory with the above parameter
settings is shown below.
Address
PLC internal register Common memory
Address
R000 0000
Reception
area
4-9
Example 2
Node No. 1
Node No. 2
If the above parameter settings are used for two nodes respectively, the data transmitted from
L100 to L1FF on node 1 is further transmitted to the same addresses on node 2 via the common
memory as shown below.
The data transmitted from L280 to L47F on node 2 is reflected on the common memory but
data from L400 to L47F is not accepted by the link area on node 1, L100 to L3FF, and
consequently not read by node 1. In this case, data from L280 to L3FF on node 2 is received
at the same addresses on node 1.
L5FF
4-10
The link area top address does not need to be the same for all nodes. If the following settings
are used for node 2, data is exchanged between nodes 1 and 2 as shown below.
M6FF
4-11
Example 3
Node No. 10
4-12
• Relay link parameters
Note: Relay link addresses may be specified in units of word (16 bits). X40W represents
X400 to X40F.
The transmission area defined by the 'transmission area top address' and 'transmission area
words' should be completely contained in the link area defined by the 'link area top address'
and 'link area words.'
For example, the following settings are not acceptable because the transmission area (L1300
to L47F) overflows the link area (L000 to L3FF). (An error message appears with such
settings.)
4-13
(2) 1:N (Satellite)
In the 1:N (Satellite) mode, data is only linked with a single station specified by the link
parameter. In this mode, it is necessary to specify the station (node) from which data is to
be received, the number of words to be received, the register at which data is to be stored, the
address on your module from which data is to be transmitted, the number of words to be
transmitted, and the top address on the common memory to which data is to be transmitted,
using the following parameters.
(*1): The common memory is a virtual memory space shared by all nodes participating in the
communication. The FL-net data is linked via the common memory.
Address 0000
(2)
Reception (3)
area
Transmission
area (4) (5)
4-14
Data is linked as shown below on the whole network.
Reception area
Reception area
Note: The node No., the destination address on the common memory, and data size are usually
determined by the network administrator at the end user.
Example 1
Address
L000 Master station transmission
area specified by station No.
Reception
32 words (32 words)
area
L200
Transmission
area 20 words 0100
Note: The data transmitted from the master station to any address on the common memory is
received from that address. Therefore, it is not necessary to specify the starting address
of the transmission area for the master station.
4-15
・ If the number of words specified by 'Recv. words' is smaller than the actual number
of transmission words from the master station:
→ Overflown part of the transmission data from the master station (last 8 words in the
following example) is not received.
Address
PLC internal register Common memory
0000
Address
L000 Master station transmission
Reception area specified by node No.
32 words
area (40 words)
Area not
L200 received
Transmission
area 20 words 0100
・ If the number of words specified by 'Recv. words' is larger than the actual number
of transmission words from the master station:
→ Part of the reception area not filled with the data transmitted from the master station
(last 16 words in the following example) is filled with 00.
Address
PLC internal register Common memory
0000
Note: If the hierarchical order of transmission areas on the common memory changes, the order
of reception and transmission areas at the PLC internal register remains unchanged.
PLC internal register Common memory
Reception
area
Transmission
area
Master station transmission
area specified by station
No. (32 words)
4-16
Node No. 100
Node No. 64
4-17
• Relay link parameters
Note: Relay link addresses may be specified in units of word (16 bits). X40W represents
X400 to X40F.
Transmission D580
D500
Reception area D67F
area for
node 150
D6FF
D780
Reception area
for node 64
D87F
4-18
4.6 Network Parameters
Network parameters do not need to be changed in usual cases. Do not change them unless
otherwise instructed by the network administrator.
Click the Network button and change the network parameters.
The FL-net communicates using the UDP/IP protocol. Specify the former 3 digits of the IP
address to be used for this protocol as network address. The forth digit of the IP address
represents the node No.
If the network address is 192.168.250 and the node No. is 100, for example, the IP address is
192.168.250.100. As PING is sent to this IP address from a personal computer or such, a
response is made by the 2PORT-EFR module.
The FL-net broadcasts data using the UDP/UP protocol. At this time, it sends the IP address
with the forth digit replaced by FFh as destination IP address. For the node with the IP
address of 192.168.250.100, for example, the destination IP address is 192.168.250.255.
All nodes on a single FL-net network should have the same network address.
Any node with a different network address cannot receive data from other nodes and the data
transmitted from that node is not received by other nodes. Care is required because all data
is monitored by the Ethernet analyzer.
The FL-net standards require the network address be defaulted as 192.168.250.
4-19
4.6.2 Token Monitor Time-Out Time
For the FL-net communication, each node rotates the token (right to transmit) among other
nodes in ascendent order of node No. The node that has received the token transmits data in
the data link transmission area and message data, if any, as divided into frames each
consisting of 1024 bytes or less and adds the token to the last frame to hand it over to the next
node.
The token monitor time-out time means the permissible longest time to be spent after the
token is transmitted by the prior node until it is transmitted to the next node. If the token is
not transmitted within this time, the next node reissues the token. If this occurs three times,
the node that fails to transmit the token is considered to have left and no longer given with
the token.
If 'Auto' has been checked, the token monitor time-out time is automatically determined from
the data size of the transmission area with the following formula.
Token monitor time-out time=(1+5)+(TBN+1+1)*(1+5) ms
Maximum value of frame intervals
Maximum data transmission time
Spare
Message frame
Total number of cyclic data blocks
Maximum value of frame intervals (*2)
Time taken by prior node
Maximum data transmission time (*1)
Token Token
(*1): The time required to put 1024-byte data on a 10 Mbps communication line.
(*2): The maximum value of minimum permissible frame intervals (for detail, see the
next section).
To manually preset the token monitor time-out time, remove the check mark in the check box
before 'Auto' and enter a desired value between 10 and 255.
If the token is not transmitted within the preset token monitor time-out time, error code EA
appears on the LED display at the front of the module. In this case, increase the token
monitor time-out time.
4-20
4.6.3 Minimum Permissible Frame Interval
The frame interval means the interval between two successive data frames where no data is
exchanged through the line.
For the FL-net communication, the minimum permissible frame interval has been preset for
each node and its value is always transmitted. Each node always monitors the minimum
permissible frame interval values of other nodes and the largest value of all nodes becomes
effective. The minimum permissible frame interval is changeable between 0 ms and 5 ms.
If nodes with three minimum permissible frame interval values of 1 ms, 3 ms and 5 ms
coexist, for example, 5 ms becomes effective and all data frames are transmitted through the
line at intervals of 5 ms.
This parameter is intended to adjust the data volume through the line per unit time so that
nodes even with a lower processing rate can participate in the communication.
With the TOYOPUC 2PORT-EFR module, the minimum permissible frame interval has been
preset to the default of 1 ms. Please note that the communication time of the entire network
is postponed when a big value is set by mistake though a value that is bigger than this can be
set.
4-21
5 Error Codes Used by the FL-net
If the 2PORT-EFR module finds an error, it indicates a two-digit error code on the LED display at
the front and warns the CPU module of the error.
The CPU module sets special relays, error information output registers, and link error information
output registers according to the content of the error.
Error
Content of error Cause and remedy 5
code
Preset link parameters if not preset. If all link parameters have been
preset, rack No. or slot No. as link parameter may not correspond with
the actual position.
5-1
Token monitor time-out occurs when all data cannot be transmitted
from your module within the token monitor time-out time specified as
link parameter on 'Network' window.
Check 'Auto' for token monitor time-out time or increase the preset
value.
This error occurs when a link area out of the data register area in the
CPU module is specified.
Ed Data register area overflow For example, the PC2J-CPU has data registers at D000 to D0FFF and,
if a link area out of this area is specified, error code Ed appears.
Check the link area address.
Upon power-up or reset/start-up, the 2PORT-EFR module
automatically checks that data can be normally transmitted and
received. This error code appears if the module fails in the test.
In this case, the test is automatically repeated until successfully
completed.
Communication starts after acceptable test results are obtained.
Check the following items in accordance with 3 'Installation and
Wiring.'
(1) Is the LAN cable connector firmly connected to the module and
locked with a fitting?
(2) Is the connector of LAN cable surely installed in HUB?
-- (3) Is LAN cable disconnected or it not short-circuited?
-- Failure in loop back test (4) Is the transceiver cable connector firmly connected to the HUB
-- and locked with a fitting?
(5) When HUB is stacked and used, is the connection between HUB
correct?
(6) Is the transceiver cable connector firmly connected to the
transceiver and locked with a fitting?
(7) Any cut wire or short circuit in the transceiver cable?
(8) Any problem about connection between transceiver and bus cable?
(9) Is a terminator connected with each end of the bus cable?
(10) Any cut wire or short circuit in the bus cable?
If this error occurs with all FL-net modules on the network, (9)
or (10) is suspected to be a cause.
This will be the display if there are no nodes which participate in the
network or when the module’s own nodes break away.
(1) Is not the power supply of HUB turned off?
-- Receive waiting (2) Is not the power supply of another node turned off?
(3) Is the connector of LAN cable surely installed in the module?
(4) Is the connector of LAN cable surely installed in HUB?
(5) Is LAN cable disconnected or it not short-circuited?
5-2
The following causes are suspected.
(1) CPU parameters have not been correctly set.
(2) 16-kbyte or 32-kbyte FL-net mode has been selected for the CPU
module that does not support these modes.
(3) A failure of 2PORT-EFR module, CPU module, or base
H5 NAK from CPU module
Remedy:
(1) -> Check CPU module parameter settings.
(2) -> Change switch settings.
(3) -> Replace 2PORT-EFR module, CPU module, or base.
5-3
5.2 Error Messages Used by the CPU Module
Address Content
5-4
5.2.2 Special Registers
S200
| CPU error information output registers
S24F
Participation of nodes in FL-net network communication
S3*0
Indicates the communication status of each node (1 =
|
participating or 0 = not participating).
S3*F
See 2-8 'Monitor Function.'
S3x0
| Link error information output registers
S3xB
♦ “*” and “x” in the above addresses are determined by the link No. as shown in the
following table.
Link No. 1 2 3 4 5 6 7 8
* 0 2 4 6 8 A C E
x 1 3 5 7 9 B D F
Example) If the link No. is 1, for example, the communication status of each node is
recorded at S300 to S30F and the link error information at S310 to S31B.
Note: The information recorded at a special register is not cleared after error recovery.
If it is to be cleared, enter '0000' at the register using the I/O monitor, programmer or
such.
5-5
(1) CPU Error Information Output Registers
When an error is detected, an error code, error related information, and error detection time
are recorded at registers specially designed for recording error information. Up to 8 errors
are recorded at these 8-level shift registers. As the 9th and subsequent errors occur, error
records are deleted from the oldest one.
The error information recorded at these registers can be loaded with peripheral equipment or
such.
Communication module
FUNC. I/O
81 memory overflow - - - - VC8 ON
OVER 2
Critical errors
Link
86 LINK ERROR A communication error - - -
No.
A wrong rack No., slot
FUNC. I/O Rack Slot
89 No. or module name as - - VF2 ON
ALARM No. No.
link parameter
Note: These codes are different from the ones indicated on the LED display at the front of
the 2PORT-EFR module.
5-6
(2) Link Error Information Output Registers
If the 2PORT-EFR module finds an error, it warns the CPU module of the error. The CPU
module records content of the error at link error information output registers. Up to 8
errors can be recorded at these 8-level shift registers. As the 9th and subsequent errors
occur, error records are deleted from the oldest one.
The error information recorded at these registers can be loaded with peripheral equipment or
such.
*1: The same with the error codes indicated at the front of the module. (See 5-1 'Error Codes
Used by the 2PORT-EFR Module.')
*2: For link parameter errors only (error code = E6). Fixed to 0000 for other errors.
*3: 0123h for version 1.23.
5-7
♦ Link Parameter Error Codes
If a link parameter has been set to a wrong value, E6 appears on the LED display at the front
of the module with error code E6 recorded at link error information output register S3x0 and
a link parameter error code at S3x1.
Check link parameters in accordance with the following table.
Before checking link parameters, load them from the CPU module to the peripheral equipment.
Parameters in the peripheral equipment may not coincide with those in the CPU module.
If parameters are set with the peripheral equipment such as PCwin, preset values are checked
by the peripheral equipment and wrong ones are rejected. If a link parameter error still
occurs, link parameters in the CPU module may have been modified by a computer link
command except for 0024 (a switch setting error).
5-8
5.3 Detection of abnormality by monitor function
The participation secession of the FL-net node can be confirmed by the special register from
S3*0 to S3*F.
The node of the corresponding exchange number participates in the network when the flag
has been turned on. The node of the corresponding exchange number has seceded the
network when the flag is turned off.
The node that secedes the network by observing this flag by the sequence program can be
detected.
The flag turned off once by some interference joins the network again as soon as
interference recovers and turns on the flag. Please maintain the flag that corresponds to the
node that secedes by the sequence program in another address to detect momentary
secession.
Please refer to the following for specific in an abnormal location where it causes secession.
<Procedure>
1) The network system chart of equipment is prepared.
2) It marks it to the node that the flag is turned off.
3) It confirms it according to the following patterns.
100
1 4 3 5 2 6
It is thought that the abnormal cause is chiefly in the module or the cable of node 3.
5-9
Pattern B: Secession of same HUB all nodes
Example: Abnormal cause when secession of node 2 and 6 is detected by node 100
100
1 4 3 5 2 6
Note) There might uncommonly when consecutive node No is abnormality be a cause on the node in front of
minimum, abnormal node No. (Refer to example 2 of pattern C. )
5-10
Pattern C: All nodes secede or when the secession node is different
Example 1:Abnormal cause when all node secession is detected by node 100
100
1 4 3 5 2 6
It is thought that the abnormal cause is chiefly in trunk line or node 100.
Probable cause Measures
There is no power supply of HUB1. Please turn on power.
Neither node 100 nor HUB1 are connected. Please connect the cable surely.
Defective cable between HUB1 and node 100 (disconnection, Please exchange cables of node 100.
short-circuit, unspecified cable)
Defective cable between HUB and HUB (disconnection, Please exchange cables.
short-circuit, unspecified cable)
Breakdown of HUB (Either or all from HUB1 to HUB3) Please exchange HUB
Breakdown of node 100 Please exchange nodes 100.
Defective cable of node 6 (disconnection, short-circuit, Please exchange cables of node 6.
unspecified cable) *1
Breakdown of node 6 *1 Please exchange nodes 6.
Node 100 might become abnormal by intermittent interference of the node of the exchange number in front of
an abnormal node (node 6).
Example 2: Abnormal cause when two or more node secession is detected by node 100
100
1 4 3 5 2 6
5-11
6 FL-net Message Functions
The message functions include the message server function for receiving a command from
another node and making a response and the message client function for receiving a response.
With the message client function, commands are transmitted and response data is read by the
sequence program. With the message server function, no special sequence program is required
for such processes.
The message server function for making a response to the command transmitted from another
node by the FL-net message function is described below.
Command
Response 6
6.1.1 Applicable TCD Codes and Contents of Response Data
The following TCD codes (command codes) as specified by the FL-net standard are applicable.
6-1
(1) Read/Write Byte/Word Block Data
For these commands, specify the address of the data to be read or written with four bytes.
Specify the CPU module mode and program No. with the former two bytes and the indirect
byte or word address with the latter two bytes.
Indirect byte
No. ID Designation Word address Indirect word address
address
1 Input
X
X, Y00W - 7FW 200 - 2FF 100 - 17F
2 Output
Y
3 Internal relay
M M00W - 7FW 300 - 3FF 180 - 1FF
4 Keep relay
K K00W - 2FW 40 - 9F 20 - 4F
5 Special relay
V V00W - 0FW A0 - BF 50 - 5F
6 Timer
T
T, C00W - 1FW C0 - FF 60 - 7F
7 Counter
C
8 Link relay
L L00W - 7FW 100 - 1FF 80 - FF
9 Data register
D D0000 - 2FFF 2000 - 7FFF 1000 - 3FFF
10 Link register
R R0000 - 07FF 1000 - 1FFF 800 - FFF
11 Current value register
N N0000 - 01FF C00 - FFF 600 - 7FF
12 Special register
S S0000 - 03FF 400 - BFF 200 - 5FF
13 Expansion input
EX
EX, EY00W - 7FW B00 - BFF 580 - 5FF
14 Expansion output
EY
15 Expansion internal relay
EM EM00W - 1FFW C00 - FFF 600 - 7FF
16 Expansion keep relay
EK EK00W - FFW 200 - 3FF 100 - 1FF
17 Expansion special relay
EV EV00W - FFW 400 - 5FF 200 - 2FF
18 Expansion timer
ET
ET, EC00W - 7FW 600 - 6FF 300 - 37F
19 Expansion counter
EC
20 Expansion link relay
EL EL00W - 1FFW 700 - AFF 380 - 57F
21 Expansion data register
U U0000 - 7FFF 0000 - FFFF 0000 - 7FFF
Expansion current value
22 EN EN0000 - 07FF 2000 - 2FFF 1000 - 17FF
register
Expansion preset value
23 H H0000 - 07FF 3000 - 3FFF 1800 - 1FFF
register
24 ES Expansion special register ES0000 - 07FF 1000 - 1FFF 800 - FFF
25 GX Expansion input
GX, GY00W - FFFW 0000 – 1FFF 0000 – 0FFF
26 GY Expansion output
27 GM Expansion internal relay GM00W - FFFW 2000 – 3FFF 1000 – 1FFF
6-2
(2) Read Network Parameters
The response data to the Read Network Parameter command uses the format specified by
the FL-net protocol standard as shown below.
15 87 0
offset+0 Node name (equipment name)
+4
+5 Vender name
+9
+10 Manufacturer's model name
+14
+15 Top address of area 1
+16 Size of area 1
+17 Top address of area 2
+18 Size of area 2
+19 Not used Token monitor time-out time
+20 Not used Minimum permissible frame interval
+21 Not used Link status
+22 Not used Protocol version
+23 Upper layer status
+24 RCT setting of permissible refresh cycle time
+25 Measured refresh cycle time (current)
+26 Measured refresh cycle time (max)
+27 Measured refresh cycle time (min)
For the TOYOPUC 2PORT-EFR module (THU-6289), the response consists of the
following data.
6-3
(3) Run/Stop
Used to start the CPU module to scan (run) or stops it from scanning.
With the TOYOPUC 2PORT-EFR module (THU-6404), the profile data as shown below is
sent back.
Seq:179:
Seq:139
Str:6:COMVER
Int:1:1
Str:2:ID
Str:7:SYSPARA
Str:3:REV
Int:1:0
Str:7:REVDATE
Seq:10:
Int:2:2007
Int:1:7
Int:1:7
Str:10:DVCATEGORY
Str:2:PC
Str:6:VENDOR
Str:17:JTEKT CORPORATION.
Str:7:DVMODEL
Str:32:PC3J/PC2J 2PORT-EFR THU-6404
Seq:31:
Str:2:ID
Str:7:DEVPARA
Str:12:SOFT VERSION
Int:2:112h (for version 1.12)
6-4
(5) Read Log
The log data format is specified by the FL-net protocol standard as shown below. The
counter is reset when the module is powered on/off or reset. Each data record consists of
4 bytes.
6-5
57
58
59
60 Token Recognized token multiplications Number of tokens recognized to be multiplied ones
61 Discarded tokens Number of times token was discarded
62 Reissued tokens Number of times token was reissued
63
64
65
66 Token retention time-outs Number of times token retention time ran out.
67 Token monitor time-outs Number of times token monitor time ran out.
68
69
70
71
72 Status 1 Cumulative operation time Operation time after start-up
73 Frame waiting times Number of times module waited for frames with no other node on
network
74 Participations
75 Self separations Number of nodes that were separated due to three retention
time-outs or absence of nodes on network
76 Separations due to skipping Number of nodes that were not given token and consequently
skipped and separated
77 Recognized node separations Number of other nodes recognized as separated
78
79
80
81
82
83
84 Status 2 A list of participant nodes (1 to 31) Nodes recognized as participant are represented in units of bit.
85 A list of participant nodes (32 to 63) Example) 31 4 3 2 1 0
86 A list of participant nodes (64 to 95)
87 A list of participant nodes (96 to 127)
88 A list of participant nodes (128 to 159)
89 A list of participant nodes (160 to 191) Node No. 1
90 A list of participant nodes (192 to 223) Node No. 31
91 A list of participant nodes (224 to 254) (1 for participating or 0 for not participating)
6-6
6.1.2 Remote programming / Remote monitor
Because FL-net corresponds to the relay command, it is possible to monitor from the
communication modules such as Ethernet and HPC-LINK remotely and the programming
remotely via FL-net.
Response A C B
Response
FL-net communication network
Note 1) Please refer to the manual of each communication module for details of the relay command.
Note 2)When you issue "Reset" command to CPU (above figure C ) where FL-net is mounted by using
the function of remote programming from the peripheral equipment, an abnormal response returns
to the peripheral equipment so that the communication of FL-net of B may interrupt by reset. In
this case, "Reset" command to CPU C is normally executed.
6-7
6.2 Message Client Function
This function is used to transmit a command message to another node and receive a response.
It is available with CPU modules of the following versions.
Command
Response
The message transmission process is performed by the sequence program with the following
procedure.
Data to be transmitted is
recorded at register.
Response data is read from 2PORT-EFR For Read Byte/Word Block Data
module with SPR command. commands requiring response data
Note: The next command can only be transmitted after response data is completely read.
6-8
6.2.2 Assembling the Sequence Program
The data to be transmitted should be recorded in the following format (in units of byte).
・ ・
0 - FF
・ ・
1033(max) Written data (end)
(*1: When data exceeding 1024 bytes is recorded, only 1024 bytes are transmitted.)
■ If a command for writing 2-word data at R100 and R101 of the CPU module connected
with a 2PORT-EFR module with node No. 2 is to be transmitted:
6-9
(2) Writing the data to be transmitted in the 2PORT-EFR module
An SPW command is used to write the data to be transmitted in the 2PORT-EFR module.
Specifies the register recording the link No. with former 4 bits and the
Link availability flag *1 number of data bytes to be transmitted with latter 12 bits.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
■ An example of sequence program for writing the data shown in the previous page in the
2PORT-EFR module with link No. 1
V006
WMOV 100E → R103 Link No. 1 (14 bytes)
(14 = Eh)
Transmission data
WMOV 2000 → R105 destination address on
2PORT-EFR module
6-10
(3) Reading the control signal from the 2PORT-EFR module and confirming the
completion of transmission process
It is determined from the control signal read from the 2PORT-EFR module whether the data
is normally transmitted and the process completed.
The control signal is read with an SPR command.
The control signal consists of a word (2 bytes).
Specifies the register recording the link No. with former 4 bits and
Link availability flag *1 the number of data bytes to be transmitted with latter 12 bits.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
■ An example of sequence program for reading the control signal from the 2PORT-EFR
module with link No. 1 into R109
V006
WMOV 1002 → R106 Link No. 1 (2 bytes)
Address on
2PORT-EFR module
WMOV 0 → R107 from which control
signal
is to be read
R109 indirect byte
WMOV 1212 → R108 address
6-11
The control signal remains '0000' during the transmission process and changes to '0001'
upon the normal completion of the process.
In case of failure, one of the following error codes is sent back.
The control signal should be continuously read by the sequence program until the
transmission process is normally or abnormally completed.
As a command requesting response data from the other node (Read Byte/Word Block, etc.) is
transmitted, the response data is read upon the normal completion of transmission process.
This process is performed with an SPR command.
Specifies the register recording the link No. with former 4 bits and
Link availability flag *1 the number of data bytes to be transmitted with latter 12 bits.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
6-12
The response data uses the following format (data in units of byte).
■ An example of sequence program for reading 8-byte response data from the
2PORT-EFR module with link No. 1 into R220 and subsequent
V006
WMOV 1008 → R111 Link No. 1 (8 bytes)
Address on
2PORT-EFR module
WMOV 3000 → R112 from which response
data
is to be read
R220 indirect byte
WMOV 1440 → R113 address
Notes
If SPW, SPR commands are used, not only will scan time be longer, but part of the processing on the
2PORT-EFR module side will be made to wait. If these commands are executed excessively,
communication processing will be effected so please program to minimize the frequency of these
commands.
6-13
6.2.3 Examples of Sequence Programs
Node No. 2
2 words
Link 1, 14 bytes
R200 address
6-14
Link 1, 2 bytes
Message transmission
abnormally completed
Written data incremented
6-15
Keep relay cleared
2 words
Link 1, 10 bytes
R210 address
Link 1, 2 bytes
Message transmission
abnormally completed
Link 1, 8 bytes
6-16
6.3 Node Status Reading Function
This function reads the status of another node into the I/O register.
It is available with CPU modules of the following versions.
The following data can be read for other nodes participating in the communication.
The status of any node not participating in the communication is expressed by 0000 if read.
Relative address
Contents
of read data
0000 Fixed to 00 FA link status (*1)
0001 Upper layer status (H) (*1) Upper layer status (L) (*1)
0002 Address of common memory area 1 (H) Address of common memory area 1 (L)
0003 Size of common memory area 1 (H) Size of common memory area 1 (L)
0004 Address of common memory area 2 (H) Address of common memory area 2 (L)
0005 Size of common memory area 2 (H) Size of common memory area 2 (L)
0006 Permissible refresh cycle time (H) Permissible refresh cycle time (L)
0007 Fixed to 00 Token monitor time-out time
0008 Fixed to 00 Minimum permissible frame interval
0009 … Vender name (L) (*2)
000A … …
000B … …
000C … …
000D Vender name (H) (*2) …
000E … Manufacturer's model name (L) (*2)
000F … …
0010 … …
0011 … …
0012 Manufacturer's model name (H) (*2) …
0013 … Node name (L) (*2)
0014 … …
0015 … …
0016 … …
0017 Node name (H) (*2) …
(*1): For the FA link status and upper layer status, see the next page.
(*2): Data might not enter when the node participates in the network on the way.
The vender name, manufacturer's model name, and node name are expressed by ASCII codes.
6-17
■ FA link status
0 1 2 3 4 5 6 7
Reserved
Upper layer operation signal
error
0: Any error
1: No error
Common memory data
Communication validity notice
invalidity detection 0: Invalid
0: No detection 1: Valid
1: Detection Common memory (address
size) definition
Participation secession 0: Not completed
of node 1: Completed
0: Secession
1: Participation Address duplication notice
0: Not duplicated
1: Duplicated
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
U_ERR_CODE
Defined by upper layer
reserved
U_ERR
00:NORMAL
01:WARNING
10:ALARM
RUN/STOP
0:STOP
1:RUN
6-18
6.3.2 Assembling the Sequence Program
Specifies the register recording the link No. with former 4 bits and the
Link availability flag *1 number of data bytes to be transmitted with latter 12 bits.
*1: The link availability flag is V90 for the 2PORT-EFR module with link No. 1, V92 with
link No. 2, or V9E with link No. 8.
■ An example of sequence program for reading the status of node No. 2 from the
2PORT-EFR module with link No. 1 into 30h bytes from D0000
Link 1, 2 h bytes
Note: The node status reading process cannot be executed at the same time with the
message data transmission or response data reading process.
If they are executed at the same time, an instruction error occurs.
6-19
7 Initial Settings of the Ethernet
Start
Setting of transmission rate See 1-5 '.Name and Function of Each Unit '
Specify the I/O module ID code on the 'I/O module setup' window under 'Parameter' of the
peripheral equipment. When the Ethernet mode is selected, the ID code of the 2PORT-EFR
module is B3.
7-1
7.3 Link Module Name
Select the rack No. and slot No. to which the 2PORT-EFR module is to be assigned by the settings
on 'Link Parameter' window under 'Parameter' of the peripheral equipment. Set the link module
name to 'Ethernet.'
When a PC3J series CPU has been used in the program divided mode, also select the program No.
correctly.
7-2
With the TCP/IP, it is necessary to open the line before the start of communication and close or
reset it at the end of communication. With the UDP/IP, communication can be started or
interrupted without opening or closing the line. With the TCP/IP, it is confirmed from the
ACK (acknowledge) response whether data has reached the other node or not and, if it cannot
be confirmed, data is re-transmitted. With the UDP/IP, it is not confirmed whether data has
reached and, therefore, transmitted data may disappear due to data collision on the line or for
another reason before reaching the other node.
(iv) UDP
Communication is performed with the UDP/IP protocol. The line is not opened or closed. It
is not confirmed whether data has reached the destination and, therefore, data may be lost
before reaching.
7-3
(7) Other Node IP Address
For the Other Node Tables for which the 'Used' boxes have been checked, it is necessary to
specify the IP address of the other node with four numbers between 0 and 255.
■ Ref.
Specify an unique IP address for each node (each device equipped with Ethernet
communication function such as personal computer or FL/ET-nete-5 module). Do
not specify the same IP address for two or more nodes as doing so prevents normal
communication.
More than one port No. may be specified for each node. Do not specify the same
port No. more than once for a single node.
Communication may be independently performed for each node.
When the TCP protocol is to be used, determine which ports open connections.
Specify the ports that opens them as 'active' and others as 'passive.' The ports
communicating with each other do not need to have the same port No.
Example of settings
Opens Opened
IP address 192.168.1.0
Port No.2001
IP address 192.168.1.1 Port No.1025
Port No.6000 Port No.1020
Port No.6001
Port No.6002 IP address 192.168.1.2
Port No.2000
Port No.3000
Port No.4000
Port No.4500
7-4
Timer settings used for communication are described below.
They do not need to be changed in usual cases.
7-5
(15) Close Timer
When a connection is to be closed by your module, it is necessary to transmit FIN from your
module and receive FIN from the other node. If FIN is not received from the other node
within the specified time after FIN is transmitted from your module, the connection is reset.
(Programmable between 2 and 60 seconds, defaulted as 10 sec.)
7-6
7.4.2 Setting I/O Parameters
Parameters can be set in either of two ways as described below.
(1) Set from the 'Link parameter setup' window of the peripheral equipment.
PCwin or Hellowin (Ver2.2 Rev00 or more) is required to set I/O parameters in this way.
They cannot be set from the link parameter setup window of Hellowin(Less than Ver2.2
Rev00), GH3, GL1, GP1, or HP3.
(2) Set with the sequence program.
If I/O parameters have been set from link parameters and with the sequence program, the settings
from link parameters usually take precedence. If 'Initialized based on Initial Sequence Program'
has been selected on the link parameter setup window, however, the settings with the sequence
program take precedence over those from link parameters.
Select 'Ethernet' on the 'Link parameter setup' window and click the 'Detail (D)' button to open the
'Ethernet P1 L1 R0 S0' window.
Click the 'Other Node Table ...' button to open the Other Node Table window.
7-7
On this window, specify:
・Table 1 to 16 Used
・Other Node IP Addresses
・Other Node Port Nos.
7-8
Click the 'Sub-net Mask and Gateway IP Address ...' button to open the Sub-net Mask and
Gateway IP Address window. All values are initially defaulted as zero.
Click the 'Change' button when parameters are to be changed.
Click the 'Default' button to reset parameters to default values.
● Caution
If the CPU module parameters are to be set from the link
parameter settings of the 2PORT-EFR module by
reading to the peripheral equipment parameters from the
CPU module with which the 2PORT-EFR module has
been initialized with the sequence program, default
values are usually changed to zeros. In this case, return
to the Program 1 Link <1> window, clear the Ethernet
settings, click the 'OK' button, and set the Ethernet
parameters again. Moreover, please delete the initial
sequence program (material 4). The application
instruction error occurs in CPU module if the SPW
instruction initial programming it with "Initialization
based on link parameter" selected is executed.
(2) Setting I/O parameters with the Sequence Program
I/O parameters may be set with the sequence program with the following procedure.
7-9
■ Recording I/O parameters at registers
I/O parameters are written in the 2PORT-EFR module with an SPW command after recorded at
registers.
The following example shows I/O parameters and a sequence program that write them into File
Memory:
Caution) Since CPU Module register data are 16-bit word data, File Memory by 2 bytes is
represented by one register datum.
7-10
■ An example of sequence program for transferring I/O parameters to 2PORT-EFR module and
turning initialization request flag on
A function instruction, SPW, is used to transfer the I/O parameters recorded at registers to the
2PORT-EFR module. For the SPW command, see Reference 1 at the end of this manual.
An example is given below where the I/O parameters as shown in the previous page are written in
the file memory of the 2PORT-EFR module and the initialization request flag turned on.
As I/O parameters are normally set and the initialization request flag turned on, the 2PORT-EFR
module becomes capable of normally communicating and all LEDs at the front of the module go off.
Any I/O parameter has been set to a wrong value, 'E6' appears on the LED display at the front of the
module and the CPU module has a communication error. Check I/O parameters in accordance
with 7-4 'Communication Errors.'
If I/O parameters are not normally written or the Initialization request flag not turned on due to a
sequence program error or the CPU module does not run due to a failure or setting error, the LED
display at the front of the module remains showing .
Note: When a PC3J series CPU has been used in a mode other than PC2 compatible, programs 2 and 3 do not
run unless the program execution mode is selected to be 'effective' with CPU operation mode parameter.
7-11
■ File memory communication parameter setting address
bit7 bit0
0000 8 (00 fixed) 1 1:Initialization Request 8:Parameter area read-only(1:Release 0: read-only)
0001 8 7 6 5 4 3 2 1 1-8:Connections 1-8 Active Open Request (1:Request)
0002 8 7 6 5 4 3 2 1 1-8:Connections 1-8 Transmission Request (1:Request)
0003 8 7 6 5 4 3 2 1 1-8:Connections 1-8 Reception Request (1:Confirmation)
0004 (00 fixed) 2 1 1:Error Log Reception Confirmation, 2:ICMP Log Reception Confirmation
0005 (00 fixed)
0006 (00 fixed)
0007 (00 fixed)
0008 (Lower)
0009
Own Node IP Address
000A 00000001 - FFFFFFE
000B (Higher)
000C 8 7 6 5 4 3 2 1 1-8:Connection Used (1:Use)
000D 8 7 6 5 4 3 2 1
1-16:Table Used (1:Use)
000E 16 15 14 13 12 11 10 9
000F (00 fixed)
0010 TCP Active Open: 0000h, TCP Destination-Specified Passive Open: 0100h,
Connection opening method
Connection No.1
7-12
0038 TCP Active Open: 0000h, TCP Destination-Specified Passive Open: 0100h,
Connection opening method
Connection No.6
0039 TCP Destination Non-Specified Passive Open: 0200h, UDP:0001h
003A Own Node Port No. (Lower)
003B 0401h - FFFEh (Higher)
003C Other Node Table No.. (Lower)
003D 0001h - 0010h (Higher)
003E General communication setting 00h or FFh
003F (00 fixed)
0040 TCP Active Open: 0000h, TCP Destination-Specified Passive Open: 0100h,
Connection opening method
Connection No.7
006B (Higher)
006C Other Node Port No. (Lower)
006D 0401h - FFFEh (Higher)
006E
(00 fixed)
006F
7-13
0070 (Lower)
0071
Table No.5 Other Node IP Address
0072 00000001 - FFFFFFE
0073 (Higher)
0074 Other Node Port No. (Lower)
0075 0401h - FFFEh (Higher)
0076
(00 fixed)
0077
0078 (Lower)
0079
Other Node IP Address
Table No.6
00000001 - FFFFFFE
00A3 (Higher)
00A4 Other Node Port No. (Lower)
00A5 0401h - FFFEh (Higher)
00A6
(00 fixed)
00A7
7-14
00A8 (Lower)
00A9
Table No.12 Other Node IP Address
00AA 00000001 - FFFFFFE
00AB (Higher)
00AC Other Node Port No. (Lower)
00AD 0401h - FFFEh (Higher)
00AE
(00 fixed)
00AF
00B0 (Lower)
00B1
Other Node IP Address
Table No.13
00DF
7-15
00E0 (Lower) ●Response time
Response Timer
00E1 (Higher) Set in units of second.
00E2 (Lower) (0006h for 6 seconds)
Non-Reception Timer
00E3 (Higher)
00E4 (Lower) ●Non-reception timer
Resending Timer (Data)
00E5 (Higher) Set in units of second or minute. If set in units of second, the
00E6 (Lower) most significant digit of hexadecimal notation should be 1.
Re-transmitted Data (SYN/FIN)
00E7 (Higher) Set to 0 if the timer is not to be used.
00E8 (Lower) (101Eh for 30 seconds, 0002h for 2 minutes, 0000h for
Close Timer
00E9 (Higher) permanent waiting)
00EA (Lower)
Packet alive Time
00EB (Higher) ●Resending Timer (Data)/Re-transmitted Data (SYN/FIN)
00EC (Lower) Set in units of second or 100 ms. If set in units of 100 ms, the
IP Assembly Timer
00ED (Higher) most significant digit of hexadecimal notation should be 1.
00EE (Lower) (1005h for 500 ms, 0002h for 2 seconds)
Reset wait resending times
00EF (Higher)
●Close Timer
00F0
Set in units of second.
00F1 (0005h for 5 seconds)
00F2
00F3 ●Packet alive Time
00F4 Set in units of time.
00F5
(000Ah for 10 times)
00F6 ●IP Assembly Timer
00F7 Set in units of time.
(00 fixed)
00F8 (000Ah for 10 times)
00F9
●Reset wait resending times
00FA
Set in units of time.
00FB (000Ah for 10 times)
00FC
00FD
00FE
00FF
7-16
8 Opening/Closing the Ethernet Connections
With the TCP protocol, a connection should be opened before the start of communication. The
opening methods include 'passive open' where a connection is opened upon the request from
another node and 'active open' where your module requests another node to open the connection.
In the specified passive open mode, the connection is only opened when requested by a specified
node and, in the non-specified passive open mode, it is opened when requested by any node.
At the end of communication, the connection is closed by the node that opened it.
With the UDP protocol, command/response data can be transmitted and received at any time
without opening or closing a connection. The protocol and opening method may be specified by
link parameters or with the initialization sequence for each connection.
If the CPU module is reset, TCP connections are reset. Note that, if the CPU module is reset by a
command via the 2PORT-EFR module, communication is continued without resetting the
connections.
The instant the connection that are set up as TCP Passive with I/O parameters has been
initialized, it enters the wait state for an opening request from other nodes.
Then, the connection is opened as the opening request is received from another node and the
Normal-Opening flag of the file memory (see Reference 2) and the corresponding LED at the
front of the module turn on at the same time.
The connection open status may also be monitored by the status monitor (see 2-2-6). If
control input signals to the file memory have been assigned to K30 to K68 as shown in the
example of sequence program in Reference 3, the connection open status can be confirmed
from the on-status of contacts K38 (connection 1) to K3F (connection 8).
File Memory
Normal-Opening Flag
(1) (2)
(1) When an opening request from another node is received, the connection is opened to hoist the normal
opening flag.
(2) When a closing request from another node is received, the connection is closed to lower the
normal opening flag.
After an initialization is completed, an opening request signal is sent toward Other Node
designated by Other Node Table No. of I/O parameters, through hoisting Active-Opening
Request Flag of File Memory (see Reference 2). Data is written in the file memory with an
SPW command. If control input signals to the file memory have been assigned to K30 to K68
8-1
as shown in the example of sequence program in Reference 3, the opening request flag turns on
as contacts K38 (connection 1) to K3F (connection 8) turn on.
As a connection is normally opened, the Normal-Opening connection flag of the file memory
and the corresponding LED at the front of the module turn on at the same time.
The connection open status may also be monitored by the status monitor (see 2-2-6). If any
connection cannot be normally opened because the other node does not exist on the line or for
another reason, connection error code 4001 appears.
File Memory
Opening-Request Flag
File Memory
Normal-Opening Flag
(1) The sequence program turns the opening request flag of the file memory on.
(2) The 2PORT-EFR module opens a connection to the other node and turns the
Normal-Opening signal on if the connection is normally opened.
(3) The sequence program turns the opening request flag of the file memory off to close the
connection.
(4) The 2PORT-EFR module closes a connection with the other node and turns the
Normal-Opening signal off.
With the UDP protocol, connections are not opened/closed and, directly after the completion of
initialization, the 'Normal-Opening' connection flag of the file memory and the corresponding
LED at the front of the module turn on at the same time to enable the communication.
Note that, with the UDP protocol, the 'Normal-Opening' flag turns on even if the
communication line with the other node is not normally connected.
8-2
9 Ethernet Computer Linking Method
In this method, a PC or workstation, etc. sends a computer-link command for 2PORT-EFR
Module to return a response to it in order to carry out a communication.
Any particular sequence program to process computer-link commands is not required, because
2PORT-EFR Module is responsible for analysing the computer-link commands and for reading &
writing the I/O of CPU Module.
Analysis
(3) Response (4) Response
Ethernet Header, IP Header, TCP/UDP Header, and Ethernet FCS are generally annexed by
communication software automatically.
0 0 L L C Command-Field Data
0 0 L H M
(FT) D
8 R L L C Response Data
0 C L H M
(FT) D
9-1
9.2 Address List
9.2.1 PC10 Standard mode, PC3 mode, PC2 Compatible mode
Use the following addresses within the Command-Field Data of computer link, according to each
instruction by the word, byte, and bit:
Program No.
ID Designation Address Word address Byte address Bit address
(*1)
K Keeping Relay K000-2FF 0020-004F 0040-009F 0200-04FF
V Specific Relay V000-0FF 0050-005F 00A0-00BF 0500-05FF
Bit area
07
Exp
bit
For example, if you access Register D0100 via a command that reads/writes the I/O register word,
specify the address as "1000H (word address of Register D0000) + 100H = 1100H (lower
address:00H, higher address:11H)." Likewise, if you read/write the I/O register byte from/into the
same Register D0100, designate the address as "2000H (byte address of Register D0000) + 200H
(100H*2) = 2200H (lower address:00H, higher address:22H)."
(Multiplying an address by 2 is necessary because D register has a 16-bit word unit.)
9-2
9.2.2 PC10 mode
Please use the address used in the command data of the computer link by the unit (unit of the wor
d, unit of the byte, and unit of the bit) specified by each instruction. (A long unit becomes the sa
me to unit of the word specification. )
Unit of bit
Example) P1-M1000
1) Reference)The bit address is acquired from the address table. (0x61800 is stored in 0bit to 18bit.)
2) Reference)Ex No. (*) is acquired from the address table. (0x0D is stored in 19bit to 26bit. )
3) The bit address is calculated from 32 bit data (0x006E1800).
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
00固定
fix Ex No.(0x0D) Bit Address
ビットアドレス(0x61800)
0 0 0 0 0 0 0 0 0 1 1 0 1 1 1 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0
0 0 6 E 1 8 0 0
Upper WORD
上位WORD Upper WORD
上位WORD Lower WORD
下位WORD Lower WORD
下位WORD
アドレス上位
Upper Address アドレス下位
Lower Address アドレス上位
Upper Address アドレス下位
Lower Address
Unit of byte
Example) P2-D2000
1) Reference)Byte address is acquired from the address table. (Even the 15th bit from the 0th bit stores
0x6000. )
2) Reference)Ex No. (*) is acquired from the address table. (Even the 23rd bit from the 16th bit sto
res 0x0E. )
3) The bit address is calculated from 32 bit data (0x000E6000)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0固定
fix Ex No.(0x0E) Byte Address
バイトアドレス(0x6000)
0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 E 6 0 0 0
Upper WORD
上位WORD Upper WORD
上位WORD Lower WORD
下位WORD Lower WORD
下位WORD
アドレス上位
Upper Address アドレス下位
Lower Address アドレス上位
Upper Address アドレス下位
Lower Address
9-3
9.3 Command List
If you use PC2J-Series CPU Module or PC2-Interchangeable PC3J-CPU, commands only No.1
to 31 are available.
If you use PC3-Mode PC3J-CPU Module with the commands No.1-31 issued; the program that
has program No. where 2PORT-EFR Module is allocated, I/O, and register are processed. To
read/write the expansion field data or the program parameters that have different parameter
Nos., use the expansion commands No.32 - 42.
Command Code
No. Function Sub-command
(HEX)
1 Reading Sequence Program Word 18 NO
2 Writing Sequence Program Word 19 NO
3 Reading I/O Register Word 1C NO
4 Writing I/O Register Word 1D NO
5 Reading I/O Register Byte 1E NO
6 Writing I/O Register Byte 1F NO
7 Reading I/O Register Bit 20 NO
8 Writing I/O Register Bit 21 NO
9 Reading I/O Register Multi-Point Word 22 NO
10 Writing I/O Register Multi-Point Word 32 NO
11 Reading I/O Register Multi-Point Byte 24 NO
12 Writing I/O Register Multi-Point Byte 25 NO
13 Reading I/O Register Multi-Point Bit 26 NO
14 Writing I/O Register Multi-Point Bit 27 NO
15 Reading Parameter 30 NO
16 Writing Parameter 31 NO
17 Reset 32 00, 00
18 Scan Resumption 32 01, 00
19 Scan Stop, Stop Break 32 02, 00
Function 20 Pseudo-Scan Stop, Break 32 03, 00
Call
21 Reading CPU Status 32 11, 00
22 Reading Execution Priority Steady State 32 21, 00
23 Execution Priority Restricting Configuration 32 22, 00
9-4
Command Code Sub-comma
No. Function
(HEX) nd
24 Fill 32 32, 00
25 Reading Set Values & Recent Values of Timer 32 40, 00
& Counter
26 Writing Set Values & Recent Values of Timer 32 41, 00
Function & Counter
Call
27 Writing Set Values of Timer & Counter 32 42, 00
28 Writing Recent Values of Timer & Counter 32 43, 00
29 Reading Clock Time 32 70, 00
30 Setting Clock Time 32 71, 00
31 Relay Command 60 NO
32 Reading Program Expansion Word *1 90 NO
33 Writing Program Expansion Word *1 91 NO
34 Reading Parameter Expansion *1 92 NO
35 Writing Parameter Expansion *1 93 NO
36 Reading Data Expansion Word *1 94 NO
37 Writing Data Expansion Word *1 95 NO
38 Reading Data Expansion Byte *1 96 NO
39 Writing Data Expansion Byte *1 97 NO
40 Reading Data Expansion Multi-Point *1 98 NO
41 Writing Data Expansion Multi-Point *1 99 NO
42 Expansion Function Call *1 A0 *3
9-5
9.4 Limited Numbers of Read/Written Data Records and 2PORT-EFR Modules
The number of data records that can be read/written with commands and that of 2PORT-EFR
modules (in Ethernet mode) that can be mounted are limited according to the CPU module type.
They should not exceed the numbers shown below.
CPU module
PC3JG, PC3JG-P
PC3JP, PC3JP-GP PC3J-CPU
PC3JD ver 2.0 or subsequent PC3JNM
PC3JM, PC3JL PC3JD ver 1.10 or earlier
Mx, PC2J series
Relay commands 512 bytes or 256 words 512 bytes or 256 words
Maximum data size
Other than relay commands 512 bytes or 256 words
for each command
Number of Ethernet modules
Up to 8 Only one
that can be mounted *1
(As of January, '06)
*1 The number of mounting of EN-I/F T and FL/ET(-net5,-T-V2) used in the “Ethernet mode”
is contained.
9.5 Caution in Changing the CPU Module Parameters with Commands via Ethernet
Do not change the program or link No. to which the 2PORT-EFR itself has been assigned, using
the Write Parameter command via the 2PORT-EFR module.
If you do so, the 2PORT-EFR module and CPU module cannot communicate with each other
and an error may occur.
In this case, shut the module off once.
9-6
9.6 Ethernet Command/Response Data Format
(1) Function
Reading the program memory by the word block
0 0 L L C
Word No.
Word No.
Address
Address
Higher
Higher
Lower
Lower
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data n
0 C L H M
D
n ≤ 200H
(Example)
A command to read out sequence program at the 0th operand by one word
00. 00. 05. 00. 18. 00. 00. 01. 00
The response to the 0th operand read as NOP
80. 00. 03. 00. 18. 00. 00
(1) Function
Writing the program memory by the word block
(2)Message format
・Command Transfer Number
0 0 L L C
Address
Address
Data 1
Data 2
Data n
Higher
Lower
0 0 L H M
D
n ≤ 200H
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write NOP (code:0000) into sequence program at the 1st operand
00. 00. 05. 00. 19. 01. 00. 00. 00
Response
80. 00. 01. 00. 19
9-7
3. Reading I/O Register Word (CMD = 1CH)
(1) Function
Reading out the data memory by the word block
0 0 L L C
Word No.
Word No.
Address
Address
Higher
Higher
Lower
Lower
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data n
0 C L H M
D
n ≤ 200H
(Example)
A command to read out data registers D0100-D0102
00. 00. 05. 00. 1C. 00. 11. 03. 00
Command Code Data 1
Word Address of D0100
(1) Function
Writing the data memory by word block
(2)Message format
・Command Transfer Number
0 0 L L C
Address
Address
Data 1
Data 2
Data n
Higher
Lower
0 0 L H M
D
n ≤ 200H
・Response
8 R L L C
0 C L H M
D
9-8
(Example)
A command to write the data, 0001, 0203, and 0405, into data registers D0100-D0102
00. 00. 09. 00. 1D. 00. 11. 01. 00. 03. 02. 05. 04
Command Code Data 1 Data 2 Data 3
Word Address of D0100
Response
80. 00. 01. 00. 1D
(1) Function
Reading out the data memory by the byte block
0 0 L L C
Word No.
Word No.
Address
Address
Higher
Higher
Lower
Lower
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data 3
Data 4
Data n
0 C L H M
D
n ≤ 400H
(Example)
A command to read out data registers D0100L-D0102L
00. 00. 05. 00. 1E. 00. 22. 05. 00
5 Bytes
Byte Address of D0100
9-9
6. Writing I/O Register Byte (CMD = 1FH)
(1) Function
Writing the data memory by the byte block
0 0 L L C
Data 1
Data 2
Data 3
Data 4
Data n
Address
Address
Higher
Lower
0 0 L H M
D
n ≤ 400H
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write data, 01,02,03,04,and 05, into data registers D0100L-D0102L
0 0 . 0 0 . 0 8 . 0 0 . 1 F. 0 0 . 2 2 . 0 1 . 0 2 . 0 3 . 0 4 . 0 5
Response
80. 00. 01. 00. 1F
(1) Function
Reading out the data memory at its bit area by one bit
Reading out image memory data for external I/O
0 0 L L C
Address
Address
Higher
Lower
0 0 L H M
D
・Response Transfer
Number
Data
8 R L L C
0 C L H M
D
1: ON, 0: OFF
9-10
(Example)
A command to read out the state of internal relay M0201
00. 00. 03. 00. 20. 01. 1A
Command Code Bit Access Relative Address
The response to M0201 at ON
80. 00. 02. 00. 20. 01
(1) Function
Writing the data memory at its bit area by one bit
Writing an image and an output card for external I/O
0 0 L L C
Address
Address
Higher
Lower
0 0 L H M
D
1: ON, 0: OFF
・Response
8 R L L C
0 C L H M
D
(Example)
A command to turn on internal relay M0201
00. 00. 04. 00. 21. 01. 1A. 01
Command Code ON Signal
Bit Address of M0201
Response
80. 00. 01. 00. 21
(1) Function
Reading out data memory at multiple points by the word
9-11
(2) Message format
・Command Transfer Number
0 0 L L C
Address
Address
Address
Address
Address
Address
Address
Address
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data 3
Data n
0 C L H M
D
n ≤ 80H
(Example)
A command to read out the data of data registers D0100,D0200,and D0210
00. 00. 07. 00. 22. 00. 11. 00. 12. 10. 12
Word Access Address of Each Data
(1) Function
Writing the data memory at multiple points by the word
0 0 L L C
Address
Address
Address
Address
Address
Address
Address
Address
Data 1
Data 2
Data 3
Data n
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M
D
n ≤ 80H
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write 1234 into data register D0100, 5678 into D0210, and 9ABC into D0210
00. 00. 0D. 00. 23. 00. 11. 34. 12. 00. 12. 78. 56.
10. 12. BC. 9A
Response
80. 00. 01. 00. 23
9-12
11. Reading I/O Register Multi-Point Byte (CMD = 24H)
(1) Function
Reading out the data memory at multiple points by the byte
(2) Message format
・Command Transfer Number
0 0 L L C
Address
Address
Address
Address
Address
Address
Address
Address
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data 3
Data n
0 C L H M
D
n ≤ 80H
(Example)
A command to read out D800L & D802L
00. 00. 05. 00. 24. 00. 30. 04. 30
(1) Function
Writing the data memory by the byte
(2) Message format
・Command Transfer Number
0 0 L L C
Data 1
Data 2
Data 3
Data n
Address
Address
Address
Address
Address
Address
Address
Address
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M
D
n ≤ 80H
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write 56h into D800L and 12h into D802L
00. 00. 07. 00. 25. 00. 30. 56. 04. 30. 12
Response
80. 00. 01. 00. 25
9-13
13. Reading I/O Register Multi-Point Bit (CMD = 26H)
(1) Function
Reading out the data memory at its multiple points by the bit
(2) Message format
・Command Transfer Number
0 0 L L C
Address
Address
Address
Address
Address
Address
Address
Address
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data 3
Data n
0 C L H M
D
n ≤ 80H
(Example)
A command to read out M400 & M402
00. 00. 05. 00. 26. 00. 1C. 02. 1C
(1) Function
Writing the data memory by the bit
(2) Message format
・Command Transfer Number
0 0 L L C
Data 1
Data 2
Data 3
Data n
Address
Address
Address
Address
Address
Address
Address
Address
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M
D
n ≤ 80H
・Response
8 R L L C
0 C L H M
D
(Example)
A command to turn on M400 and off M402
00. 00. 07. 00. 27. 00. 1C. 01. 02. 1C. 00
Response
80. 00. 01. 00. 27
9-14
15. Reading Parameter (CMD = 30H)
(1) Function
Reading out the parameter field
(2) Message format
・Command Transfer Number
0 0 L L C
Block
No.
0 0 L H M
D
8 R L L C
Data 1
Data 2
Data n
Byte No.
Byte No.
Higher
Lower
0 C L H M
D
0 0 L L C
Data 1
Data 2
Data n
Block
No.
0 0 L H M
D
256 bytes/block
Parameter No.
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write 8 (kilobytes) into parameter No.3 at block No.0
00. 00. 04. 00. 31. 03. 00. 08
Response
80. 00. 01. 00. 31
9-15
17. Reset (CMD = 32)
(1) Function
Resetting the CPU Module
(2) Message format
・Command
0 0 L L C 0 0 (Example) Command
0 0 L H M 0 0
D 00. 00. 03. 00. 32. 00. 00
・Response
8 R L L C 0 0 (Example) Response
0 C L H M 0 0
D 80. 00. 03. 00. 32. 00. 00
After issuing this command, release a scan resumption command to resume scanning.
Caution:
Though issue of this command via Ethernet resets CPU Module, it won't reset the
2PORT-EFR module itself. So care should be taken to the following:
・All the connections the 2PORT-EFR module was communicating with proceed to their
communication without being closed/reset after a reset command execution.
・Since the process of a computer link command is aborted temporarily during the reset
process of CPU Module, the response can delay up to 200 ms.
・If the scan is resumed via a scan resumption command after a reset command has been
executed, the initial sequence program (a sequence program preceding the START
Command) runs likewise as an ordinary reset/start in order for V06 (a specific relay to
activate only the first scan) to activate the first scan only.
・If any sequence program to initialize and configure 2PORT-EFR Module runs after a scan
resumption, the program is ignored by the 2PORT-EFR Module. Accordingly, even if the
initial parameters of the 2PORT-EFR Module are modified, the configuration of the
2PORT-EFR Module won't be refreshed. (By turning off then on the power or by
resetting/raising the CPU Module via a peripheral device or through the reset/start switch,
you can validate the modified initial parameters.)
・If the communication was accompanied by File Memory Method where the sequence
program is responsible for the communication, faulty communication may result because
of initialized sequence scan.
Warning
Make sure that safety is secured through ascertaining whether there are no people within or
around the equipment and whether the equipment is free from any possible event ― if you
are at a site apart form the equipment ― prior to module reset, scan stopping, or scan
resumption via Ethernet.
9-16
18. Scan Resumption (CMD = 32)
(1) Function
Resuming a CPU scan.
・Response
8 R L L C 0 0 (Example) Response
0 C L H M 1 0
D 80. 00. 03. 00. 01. 00
(1) Function
Stopping a CPU scan or breaking the stop
OP1 Operation
00 Scan-Stop Break
Caution) To resume scanning, issue a Scan Resumption
01 Scan Stop command after a Scan-Stop Break.
・Response
8 R L L C 0 0
0 C L H M 2 0
D
(Example)
A command to stop scanning
00. 00. 04. 00. 32. 02. 00. 01
Response
80. 00. 03. 00. 32. 02. 00
9-17
20. Pseudo-Scan Stop, Break (CMD = 32)
(1) Function
Aborting a CPU scan (with RUN output ON) or breaking the abort
OP1 Operation
00 Break of Abort
01 Abort Caution) Break an abort to resume scanning.
・Response
8 R L L C 0 0
0 C L H M 3 0
D
(Example)
A command to abort
00. 00. 04. 00. 32. 03. 00. 01
Response
80. 00. 03. 00. 32. 03. 00
(1) Function
Reading out the status information of CPU operation
・Response
8 R L L C 1 0
Data 1
Data 2
Data 8
0 C L H M 1 0
D
9-18
bit Description bit Description
7 RUN 7 Trace
6 Under a stop 6 Scan sampling trace
5 Under stop-request continuity 5 Periodic sampling trace
Data 1
Data 5
4 Under a pseudo-stop 4 "Enable" detected
3 Debug mod 3 Trigger detected
2 I/O monitor user mode 2 One scan step
1 PC3 mode 1 One block step
0 0 One instruction step
7 Fatal failure 7 I/O off-line
6 Faint failure 6 Remote RUN setting
5 Alarm 5 Status latch setting
Data 2
Data 6
4 4
3 I/O allocation parameter altered 3
2 With a memory card 2
1 1
0 0
7 Memory card operation 7
6 Write-protected program and supplementary 6 Write-priority limited program and
information supplementary information
5 5
Data 3
Data 7
4 4
3 3
2 2
1 1 Abnormal write during RUN *
0 0 Under writing during RUN *
7 Read-protected system memory 7
6 Write-protected system memory 6
5 Read-protected system I/O 5
Data 4
Data 8
9-19
22. Reading Execution Priority Steady State (CMD = 32)
(1) Function
Reading out the source that requests for a execution-priority limitation
・Response
8 R L L C 2 0 Data 1
Data 2
Data 6
Data 7
Data 8
0 C L H M 1 0
D
Caution)
If any Error Code 35 is returned to the Host in attempting to write a program and its
complementary information into CPU via a computer link command:
(A) Read out the peripheral device that restricts the execution priority and read out its Link
No. with the link command and
(B) Reset the Execution Priority Restricting Configuration with the device that is responsible
for Configuring the Execution Priority Restriction so as to
(C) Write such program, etc.
For instance:
In case an Error Code 35 is resend in attempting to write a program through 2PORT-EFR
Module at Link No.1 and then "02" (Link No.2) is discovered in response to Reading
Execution Priority Restriction, you can accomplish such writing after Resetting Execution
Priority Restricting Configuration with the module at Link No.2.
(Example)
A command
00. 00. 03. 00. 32. 21. 00
The response to the module at Link No.2 that set up Execution Priority Restriction
8 0 . 0 0 . 0 B . 0 0 . 3 2 . 2 1 . 0 0 . F F. F F. F F. F F. F F. F F. 0 2 . F F
9-20
23. Execution Priority Restricting Configuration (CMD = 32)
(1) Function
Limiting a execution priority to the source requesting for execution priority restriction, or
cancelling the priority
A priority cancelling is available on the source that requested for execution priority
restriction only.
CAUTION)
Execution Priority Restriction is a function for prohibiting or permitting other communication
module and peripheral device to write a program and supplementary information (a set for
prohibition and a reset for permission).
For example, if you set Execution Priority Configuration through computer link, the
peripheral device (graphic programmer GP1) will be disabled from writing. This protection
is for prohibiting any overlapped writing by more than one devices.
To privilege other device to write:
(A) Set Execution Priority Configuration,
(B) Complete the setting, and
(C) Reset the Execution Priority Configuration.
OP1 Operation
00 Execution priority reset
01 Execution priority set
・Response
8 R L L C 2 0
0 C L H M 2 0
D
(Example)
A command to limit an execution priority to the connected 2PORT-EFR module only
00. 00. 05. 00. 32. 22. 00. 01. 40
Response
80. 00. 03. 00. 32. 22. 00
9-21
24. Fill (CMD = 32)
(1) Function
Writing the designated data by the word into data memory at desirable field
Word No.
Word No.
0 0 L L C 3 0 O
Address
Address
Higher
Higher
Higher
Lower
Lower
Lower
Data
Data
0 0 L H M 2 0 P
D 1
OP1 Operation
01 Program Memory
02 Data Memory
・Response
8 R L L C 3 0
0 C L H M 2 0
D
(Example)
A command to fill D0800-D08FF with 1234h
00. 00. 0A. 00. 32. 32. 00. 02. 00. 18. 00. 01. 34. 12
Response
80. 00. 03. 00. 32. 32. 00
25. Reading Set Values & Recent Values of Timer & Counter (CMD = 32)
(1) Function
Reading out the set values and recent values of timer and counter
Address
Higher
Lower
0 0 L H M 0 0 P
D 1
・Response
8 R L L C 4 0
Recent Value
Recent Value
Set Value
Set Value
Higher
Lower
Higher
0 C L H M 0 0
Lower
9-22
(Example)
A command to read out the set value and the recent value of T000
00. 00. 05. 00. 32. 40. 00. 00. 06
The response to T000 Set Value = 10 and Recent Value = 08
80. 00. 07. 00. 32. 40. 00. 0A. 00. 08. 00
Caution) The set and recent values are read out in HEX.
26. Writing Set Values & Recent Values of Timer & Counter (CMD = 32)
(1) Function
Simultaneously amending the set values and recent values of timer and counter
Recent Value
Recent Value
0 0 L L C 4 0
Set Value
Set Value
Address
Address
Higher
Higher
Lower
Lower
Higher
Lower
0 0 L H M 1 0
D
・Response
8 R L L C 4 0
0 C L H M 1 0
D
(Example)
A command to write 10 into the set value of T000 and 08 into the recent value
00. 00. 09. 00. 32. 41. 00. 00. 06. 0A. 00. 08. 00
Response
80. 00. 03. 00. 32. 41. 00
Caution) Specify the set and recent values in HEX.
9-23
27. Writing Set Values of Timer & Counter (CMD = 32)
(1) Function
Mending the set values only of timer and counter
Set Value
Set Value
Address
Address
Higher
Higher
Lower
Lower
0 0 L H M 2 0
D
・Response
8 R L L C 4 0
0 C L H M 2 0
D
(Example)
A command to set 10 in T010
00. 07. 00. 32. 42. 00. 10. 06. 0A. 00
Response
80. 00. 03. 00. 32. 42. 00
(1) Function
Amending the recent values only of timer and counter
Recent Value
0 0 L L C 4 0
Address
Address
Higher
Lower
Higher
Lower
0 0 L H M 3 0
D
・Response
8 R L L C 4 0
0 C L H M 3 0
D
(Example)
A command to set 05 in T010
00. 00. 07. 00. 32. 43. 00. 10. 06. 05. 00
Response
80. 00. 03. 00. 32. 43. 00
9-24
29. Reading Clock Time (CMD = 32)
(1) Function
Reading out the time of clock incorporated in CPU
(2) Message format
・Command
0 0 L L C 7 0
0 0 L H M 0 0
D
・Response
Day of the
8 R L L C 7 0
Second
Minute
Month
Hour
Week
Year
Day
0 C L H M 0 0
D
0 0 L L C 7 0
Second
Minute
Month
Hour
Week
Year
Day
0 0 L H M 1 0
D
9-25
31. Relay Command (CMD = 60)
(1) Function
Issuing a command toward HPC Link installed on the CPU Module on which the
2PORT-EFR Module is also installed or toward other CPU Module connected via ME-NET
Command
Response A C B
Command
Response
Caution) If you use relay command, command data length and response data length should be
less than 550 bytes.
Command Code
Exchange No.
Exchange No.
0 0 L L C 0 L L 0
0 0 L H M 5 L H 0
Higher
Lower
Data
D
・Response
Link No. of Link Module A on the above Fig. Fixed data (ACK) representing a command
Link No.
Command Code
×
Exchange No.
Exchange No.
8 R L L C 0 L L Response
0 C L H M 6 L H Data
Higher
×
Lower
Caution) Specify a program No. to the higher digits of Link No. for divided-mode PC3J.
For link No.4 of program No.2, for instance, specify 24H as link No. data for command
and response data.
If the former 4 bits of the link No. (program No.) have been zero to zeros, the command
is sent through the link module with the program No. to which the 2PORT-EFR module
has been assigned.
9-26
(Example)
A sample to read out data registers D0100-D0102 of CPU Module on which HPC Link with
exchange No.3 to which HPC link with link No.2 is connected is installed.
・Command
00. 00. 0D. 00. 60. 02. 03. 00. 05. 05. 00. 1C. 00. 11. 03. 00. 00
80. 00. 0F. 00. 60. 02. 03. 00. 06. 07. 00. 1C. 00. 01. 02. 03. 04. 05. XX
(XX Undefined)
Transfer Byte Data Contents of
No. at 2 D0100 D0101 D0102
Relay Command Code Command Code for Reading I/O Register Word
Transfer Byte No. at 1
Fixed Data (ACK)
Exchange No. of Relay Destination Link Module
Link No. of Relay Destination Link Module
If any error reply arises on CPU Module at link destination, the following response appears:
2
80. 00. . . 60. 02. 03. 00. 15. . . EC ( E r r o r code). ##・ ・ ・ ##. XX
(XX Undefined)
Transfer Byte No. Error Response Data
at 2 See 5.5.2 Response Data Error Code Table.
Relay Command Code Transfer Byte No. at 1
Fixed Data (NAK)
Exchange No. of Relay Destination Link Module
Link No. of Relay Destination Link Module
9-27
Up to 4 stages of relay commands are executable by hierarchized relay command.
Caution)
If you transfer a command from child node to parent node (exchange No.00) with HPC or
ME-NET, specify 40H as exchange No. of the parent node in command data.
9-28
A sample for issuing a command to read out I/O register word into III CPU Module
・Command 3
2
1
00. 00. 15. 00. 60. 02. 01. 00. 05. 0D. 00. 60. 02. 01. 00. 05. 05. 00. 1C. 00. 11. 03. 00. 00. 00
80. 00. 17. 00. 60. 02. 01. 00. 06. 0F. 00. 60. 02. 01. 00. 06. 07. 00. 1C. 06. 07. 08. 09. 0A. 0B. XX. XX
9-29
A sample for issuing a command to read out I/O register word into IV CPU Module
4
3
2
1
00. 00. 1D. 00. 60. 02. 01. 00. 05. 15. 00. 60. 02. 01. 00. 05. 0D. 00. 60. 02. 01. 00. 05. 05. 00. 1C. 00. 11. 03. 00. 00. 00. 00
3
2
1
80. 00. 1F. 00. 60. 02. 01. 00. 06. 17. 00. 60. 02. 01. 00. 06. 0F. 00. 60. 02. 01. 00. 06. 07. 00. 1C. 0C. 0D. 0E. 0F. 12. 34. XX. XX. XX
9-30
32. Reading Program Expansion Word (CMD = 90H)
(1) Function
Reading out the program memory by the word block
0 0 L L C
Word No.
Word No.
PRG. No.
Address
Address
Higher
Higher
Lower
Lower
0 0 L H M
D
PRG1 = 01
Program No. PRG2 = 02
PRG3 = 03
8 R L L C
Data 1
Data 2
Data n
0 C L H M
D
n ≤ 200H
(Example)
A command to read out 2 words from sequence program No.2 located at the 0th operand
00. 00. 06. 00. 90. 02. 00. 00. 02. 00
9-31
33. Writing Program Expansion Word (CMD = 91H)
(1) Function
Writing the program memory by the word block
0 0 L L C
PRG. No.
Data 1
Data 2
Address
Address
Data n
Higher
Lower
0 0 L H M
D
n ≤ 200H
Program No.
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write NOP (code:0000) into sequence program No.2 at the 4th operand
00. 00. 08. 00. 91. 02. 04. 00. 00. 00. 00. 00
Response
80. 00. 01. 00. 91
(1) Function
Reading out the parameter field
0 0 L L C
PAR. No.
PRG. No.
Block
0 0 L H M
D
8 R L L C
Byte No.
Byte No.
Data 1
Data 2
Data n
Higher
Lower
0 C L H M
D
9-32
(Example)
A command to read out block No.0, parameter No.9, program No.1 (program name
parameter)
00. 00. 04. 00. 92. 01. 09. 00
(1) Function
Writing the parameter field
0 0 L L C
Data 1
Data 2
Data n
Block
0 0 L H M
D
(Example)
A command to write PROGRAM 1 into block No.0, parameter No.9, program No.1 (program
name parameter)
0 0 . 0 0 . 0 C . 0 0 . 9 3 . 0 1 . 0 9 . 0 0 . 5 0 . 5 2 . 4 F. 4 7 . 5 2 . 4 1 . 4 D . 3 1
Response
80. 00. 01. 00. 93
(1) Function
Reading out the data memory (including expansion area) by the word block
01 PRG. 1
0 0 L L C
Word No.
Word No.
Address
Address
02 PRG. 2
Higher
Higher
Lower
Lower
0 0 L H M
No.
03 PRG. 3
D
:
:
08 Expansion Register Area (U)
9-33
・Response Transfer Number
8 R L L C
Data 1
Data 2
Data n
0 C L H M
D
n ≤ 200H
(Example)
A command to read out expansion data register U0000 by one word
00. 00. 06. 00. 94. 08. 00. 00. 01 .00
(1) Function
Writing the data memory (including expansion area) by the word block
0 0 L L C
Data 1
Data 2
Address
Address
Data n
Higher
Lower
No.
0 0 L H M
D
n ≤ 200H
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write Data 1234H into expansion data register U0000
00. 00. 06. 00. 95. 08. 00. 00. 34. 12
Response
80. 00. 01. 00. 95
9-34
38. Reading Data Expansion Byte (CMD = 96H)
(1) Function
Reading out the data memory (including expansion area) by the byte block
(2) Message format
・Command Transfer Number
0 0 L L C
Byte No.
Byte No.
Address
Address
Higher
Higher
Lower
Lower
0 0 L H M
No.
D
8 R L L C
Data 1
Data 2
Data 3
Data 4
Data n
0 C L H M
D
n ≤ 400H
(Example)
A command to read out expansion recent-value register EN0000 by 2 bytes
00. 00. 06. 00. 96. 00. 00. 20. 02. 00
The response to EN0000 = 1234
80. 00. 03. 00. 96. 34. 12
(1) Function
Writing the data memory (including expansion area) by the byte block
(2) Message format
・Command Transfer Number
PRG. No.
0 0 L L C
Address
Address
Data 1
Data 2
Data 3
Data 4
Data n
Higher
Lower
0 0 L H M
D
n ≤ 400H
Program No.
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write 2 bytes, 12H and 34H, into expansion recent-value registers EN0000L
and EN0000H
00. 00. 06. 00. 97. 00. 00. 20. 12. 34
Response
80. 00. 01. 00. 97
9-35
40. Reading Data Expansion Multi-Point (CMD = 98H)
(1) Function
Reading out the data memory (including expansion area) at multiple points by each unit of bit,
byte, and word.
(2) Message format
b7 b6 b5 b4 b3 b2 b1 b0
・Command Bit Position PRG. No.
0-7
Address 1-0
Address 1-1
0 0 L L C
Address M
Address N
PRG No.
No. Bit
No. Bit
Higher
Higher
Higher
Higher
Lower
Lower
Lower
Lower
0 0 L H M Byte
Byte
Byte
Byte
No.
D
Data N
Data N
Higher
Data 1
Data 2
Data 3
Lower
0 C L H M
D
Max.128 Bytes
(Example)
A command to read out data from bit 7 of expansion internal register EM000, from expansion
recent-value register EN0000L, and from expansion data register U0000 respectively by one point
00. 00. 0D. 00. 98. 01. 01. 01. 70. 00. 0C. 00. 00. 20. 08. 00. 00
The response to EN000 with its bit 7 ON, to EN0000L=12H, and to U0000=3456H
80. 00. 05. 00. 98. 01. 12. 56. 34
Higher Data N
Lower Data N
Address 2
PRGNo. Bit
Bit Point No.
Address 1
Address M
Address N
PRG No.
PRG No.
0 0 L H M
Data M
No. Bit
Byte
Higher
Data 1
Data 2
Lower
Higher
Lower
Byte
Byte
Byte
↑
"bit 0" is effective as bit data
Address Total=Bit Point No.+Byte Point No.+Word Point No. ≤ 176 Points
Data Total=Bit Point No./8+Byte Point No.+Word Point No. × 2 ≤ 128 (bytes)
9-36
・Response
8 R L L C
0 C L H M
D
(Example)
A command to write the data of expansion internal register EM000 with its bit 7 ON, of
expansion recent-value register EN0000L=12H, and of expansion data register
U0000=3456H respectively by one point
00. 00. 11. 00. 99. 01. 01. 01. 70. 00. 0C. 01. 00.
00. 20. 12. 08. 00. 00. 56. 34
Response
80. 00. 01. 00. 99
(1) Function
Controlling the PC3J operation, reading and writing the state and each information. Use the
same format as function call (CMD = 32H) except that PRG. No. is inserted next to the
command code. Note that PRG. No. is fixed at "00" in resetting, reading and setting the
clock time, and that, if any reset command is executed, all programs are reset.
0 0 L L C O O O
PRG. No.
Higher
Lower
0 0 L H M P P P
D 1 2 n
0 0 L L C O O O
PRG. No.
Higher
Lower
0 0 L H M P P P
D 1 2 n
(Example)
A command to reset PC3J CPU Module
00. 00. 04. 00. A0. 00. 00. 00
Response
80. 00. 04. 00. A0. 00. 00. 00
9-37
43. PC10 data byte reading (CMD=C2H)
(1) Function
Data memory (PC10 whole area) is read in byte unit block.
下位WOR
Low D 上位WORD
High
order order
high
order
order
low
order
order
Address
Address
Address
Address
C
バイト数
バイト数
アドレス
アドレス
アドレス
アドレス
下位
上位
0 0 L L
Byte
Byte
low下位
上位
low下位
上位
M
count
count
0 0 L H
high
high
D
Response
Data quantity
データ数
C
n
データ11
データ22
データ33
データ44
データn
8 R L L
n<=3F0H
Data
Data
Data
Data
Data
M
0 C L H
D
(1) Function
Data memory (PC10 whole area) is read in byte unit block.
下位WOR
Low D 上High
位WORD
order order
n<=3F0H
order
order
Address
Address
Address
Address
C
n
1
4
アドレス
アドレス
アドレス
アドレス
データ1
データ2
データ3
データ4
データn
0 0 L L
high
high
low下位
上位
low下位
上位
Data
Data
Data
Data
Data
M
0 0 L H
D
Response
C
8 R L L
M
0 C L H
D
9-38
45. PC10 multi-point reading (CMD=C4H)
(1) Function
Data memory (PC10 whole area) is read in each unit of bit, byte, word, and long at multipoint.
下位WORD
Low order 上位WORD
High order 下位WORD
Low order 上位WORD
High order 下位WORD
Low order 上位WORD
High order 下位WORD
Low order 上位WORD
High order
word word word word word word word word
Word point
Byte point
ビット点数
バイト点数
ワード点数
ロング点数
Long point
order
order
order
order
order
order
order
order
order
order
order
order
order
order
order
order
C
Bit point
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
Address
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
アドレス
count
0 0 L L count
count
count
low下位
上位
low下位
上位
low下位
上位
low下位
上位
low下位
上位
low下位
上位
下位
上位
下位
上位
M
0 0 L H
high
high
high
high
high
high
high
high
low
low
D
Bitビットアドレス部
address count Byte address count
バイトアドレス部 Word address count
ワードアドレス部 Long address
ロングアドレス
(bit address) (byte address) (byte address) (byte address)
(ビットアドレス) (バイトアドレス) (バイトアドレス) (バイトアドレス)
Address total = Bit point count + Byte point count + Word point count +
アドレス合計=ビット点数+バイト点数+ワード点数+ロング点数<=127点
Long point count <= 127 points
Response Low D
下位WOR 上High
位WOR D
order order
点数
点数
ワード 点数
点数
order
order
order
ビットpoint
C
M
データ11
データ22
データ33
データLL
データLL
データLL
データLL
データM
データN
データN
point
Word
Long
point
count
point
8 R L L
Byte
low下位
上位
low下位
上位
low下位
上位
high
high
high
Data
Data
Data
Data
Data
Data
Data
Data
Data
M Data
バイト
ロング
0 C L H
Bit
Address total = Bit point count + Byte point count + Word point count +
データ合計=ビット点数/8+バイト点数+ワード点数*2+ロング点数*4<=506(バイト)
Long point count <= 506 (bytes)
(1) Function
Data memory (PC10 whole area) is read in each unit of bit, byte, word, and long at multipoint.
下位WORD
Low order 上位WORD
High order 下位WORD 上位WORD
Low order High order 下位WORD
Low order 上位WORD
High order
word word word word word word
N low
点数
バイト 点数
ワード 点数
ロング 点数
order
order
Word point
order
order
order
order
Byte point
Long point
Bit point
order
C
order
order
order
order
Address
Address
Address
Address
Address
order
order
Address
M
Address
N
Address
アドレス
アドレス
アドレス
アドレス
データ1
アドレス
アドレス
アドレス
アドレス
データM
アドレス
アドレス
アドレス
アドレス
データN
データN
Address
Address
1
Address
Address
count
0 0 L L
order
low下位
high上位
low下位
上位
low下位
上位
low下位
上位
low下位
上位
low下位
上位
下位
上位
count
count
count
Data
Data
M
Data
ビット
0 0 L H
high
Data
high
high
high
high
high
Low order
下位WORD High order
上位WORD Low order
下位WORD High order
上位WORD
word word word word
order
order
order
order
order
order
order
order
Address
Address
Address
Address
Address
Address
Address
Address
アドレス
アドレス
アドレス
アドレス
データL
データL
データL
データL
下位
上位
下位
上位
下位
上位
下位
上位
high
high
high
high
low
low
low
low
Long address
ロングアト ゙レス
(byte address)
゙レス)
(バイトアト
Response
C
8 R L L
M
0 C L H
D
9-39
47. FR register registration (CMD=CAH)
(1) Function
Data of flash register is written to corresponding flash memory.
When only the block is written without issuing flash register registration command, the flash
memory recovers the original content by resetting or power-on.
M
0 0 L H
D
Response
C
8 R L L
M
0 C L H
D
7) Completion
9-40
10 Ethernet File Memory Method
Use the transmission/reception data area of File Memory to transfer data between another node
with this method. You can communicate with another 2PORT-EFR Module as well as a
computer workstation.
Ethernet Header, IP Header, TCP/UDP Header, and Ethernet FCS are generally annexed by
communication software automatically. Also, they are added by 2PORT-EFR Module
automatically.
TOYOPUC Data Field is depicted hereinafter.
6 0 L L
0 0 L H Transmission Data
(FT)
・Response
E R
0 C
(FT)
FT ― Frame Type
RC ― Response code (Normally set to 00. If a response code other than 00 is sent
back, see 12-5-1 'Connection Anomaly Error Code Table' or 12-5-2 'Error
Response Data Error Code Table')
LL ― Lower Transfer Number
LH ― Higher Transfer Number
10-1
10.2 File Memory Transmission
Follow the steps below in transmitting the File Memory from your 2PORT-EFRModule through
a sequence program. For file memory addresses, see Reference 2 'File Memory Address Map.'
(6)
Transmission
Request Flag (1) (2)
CPU to Ethernet
Transmission
Completion Flag
Ethernet to CPU (3) (4)
Condition:
Transmitting 2044 bytes, D0100-D04FD.
Setting transmission number data to D04FE (D04FE=07FCh).
Connection No.= 1
Link No.= 1
Like the sequence program example in Reference 3; control input/output signals are
allocated to K00-K68.
10-2
[ WMOV 13FE → R027 ]
(Link No.1, 1023-byte transfer)
R Connection 1
K48 P005 K10 Transmission Request
Lowered
Connection 1
Transmission
Completed
Caution) Since the upper-limit capacity the SPW command can process simultaneously is 1023
(3FFH) bytes, if you read the data exceeding this limitation, divide it into two parts to
execute the SPW command.
If you use this sequence program to transmit data, D0100-D04FE, the following data
are conveyed:
D0100=0100 D0101=0302
D0102=0504 D0103=0706
D0104=0908 D0105=0B0A
Transmission Data
D0106=0D0C D0107=0F0E
D0108=1110 ································
···························· D04FD=FBFA
60. 00. FC. 07. 00. 01. 02. 03 ············································ 0F. 10. 11···········FA. FB
10-3
10.3 File Memory Reception
Follow the steps below in receiving the File Memory from your 2PORT-EFR Module through a
sequence program. For file memory addresses, see Reference 2 'File Memory Address Map'.
Reception
Confirmation Flag
CPU to 2PORT-EFR (3) (4) (6)
Reception
Completion Flag
2PORT-EFR to CPU (7)
(2) (5)
(1)
Another Node
Condition:
Reading out reception data to Data Registers, D500-D8FE.
Setting transfer number data to D04FE (D04FE=07FCh).
Connection No.= 1
Link No.= 1
Like the sequence program example in Reference 3; control input/output signals are
allocated to K00-K68.
10-4
[ WMOV 2DFD → R036 ]
(D6FE(H) Indirect Address)
R Connection 1 Reception
K58 P005 K18 Completion Lowered
Caution) Since the upper-limit capacity the SPR command can process simultaneously is 1023
(3FFH) bytes, if you read the data exceeding this limitation, divide it into two parts to
execute the SPR command.
If you transmit the following data toward connection 1 under the said sequence execution:
60. 00. FC. 07. 00. 11. 22. 33. 44. 55. 66. 77. 88. 99. AA. BB. CC. DD. EE. FF. 00. 11···················AA. BB
D0500=1100 D0501=3322
D0502=5544 D0503=7766
D0504=9988 D0505=BBAA
Transmission Data
D0506=DDCC D0507=FFEE
D0508=1110 ································
···························· D08FE=BBAA
10-5
11 Ethernet and general communication method
A method that sends and receives data to and from other nodes using file memory sending/receiving data areas.
The general communication method does not have set procedures for sending and receiving, and the TOYOPUC
data section can communicate entirely with arbitrary data, therefore not only hosts such as PCs, etc., connection
with various Ethernet devices made by other manufacturers is possible.
This function uses 2PORT-EFR Ver1.20 and later.
Normally, communication software or the like automatically adds Ethernet headers, IP headers, TCP/UDP
headers or Ethernet FCS. For 2PORT-EFR modules. 2PORT-EFR module also automatically adds these.
The sending and receiving area used is one which uses the file memory method.
TOYOPUC data content and file memory data content is the same. LL, LH are added to the
frame.
Transfer control is nonprocedural, and the user has the responsibility of checking for mistakes, etc. We re
commend adding transfer number, data types, etc. to the frame, enabling data reliability to be confirmed
11-1
11.1.1 Sending data of the general communication method
17FD
NOTE)Data is sent separately
1800 LL (Transfer no. lower) at 1024 or less for TCP or
1801 Conne LH (Transfer no. upper)
1472 or less for UDP.
1802 ction 1 Receiving data (Max. 2044 bytes)
receiv
e
1FFD
header FCS
Sending frame
header FCS
Receiving frame
Stores valid receiving data size Note 1) The MSS (Maximum Segment Size)
of the 2PORT-EFR TCP is 1024bytes.
File memory area If another node sends data that
bit7 bit0 exceeds 1024 bytes, the data will be
1000 LL(Transfer no. lower) separated on the other side.
1001 LH(Transfer no. higher) Note 2)Data separated in the IP layer will
Conne Sending data
1002 ction 1 be automatically associated in
send (Max. 2044 bytes) 2PORT-EFR.
17FD
1FFD
11-2
11.2 Switching to the general communication method
It is possible to switch to general communication method by writing a pre-determined setting value in the file
memory designation area. However, switchover procedures differ depending on communication parameters.
① When setting using link parameters
When setting using link parameters, writing limitations have been put in place in the communication
parameter area to prevent the wrong settings from being written. To enable this function, set the
designated area (general communication setting) after releasing the parameter area writing limitations.
By turning bit 7 of file memory 0000 on, writing limitations to all communication parameters are released.
bit7 bit0
0000 8 (00 fixed) 1 1:Initial request 8: Parameter area writing prohibited(1:Release)
0001 8 7 6 5 4 3 2 1 1 to 8:Connection 1 – 8 Active open request
0002 8 7 6 5 4 3 2 1 1 to 8:Connection 1 – 8 Send request
0003 8 7 6 5 4 3 2 1 1 to 8:Connection 1 – 8 Receipt check
0004 (00 fixed) 3 2 1 1: Error log receiving check 2:ICMP log receiving confirmation
0005 (00 fixed)
0006 (00 fixed)
0007 (00 fixed)
0008 (lower)
0009
Own node IP address
000A 00000001 to FFFFFFFE
000B (upper)
000C 8 7 6 5 4 3 2 1 1 to 8: Connection use
000D 8 7 6 5 4 3 2 1
000E 16 15 14 13 12 11 10 9 1 to 16:Table use
000F (00 fixed)
0010 TCP active open:0000h,TCP mate specific passive open:0100h
Connection open method
0011 TCP mate non-specific passive open:0200h, UDP:0001h
0012 Conn Own node port no. (lower)
0013 ection 0401h to FFFEh (upper)
0014 No. Own node port no. (lower)
1 0001h to 0010h (upper)
0015
0016 General communication setting General communication disabled: 00h, general communication enabled: FFh
0017 (00 fixed)
0018 TCP active open:0000h, TCP mate specific passive open:0100h
Connection open method
0019 TCP mate non-specific passive open:0200h, UDP:0001h
001A Conn Own node port no. (lower)
001B ection 0401h~FFFEh (upper)
001C No. Other node table no. (lower)
2 0001h to 0010h (upper)
001D
001E General communication setting General communication disabled: 00h, general communication enabled: FFh
001F (00 fixed)
General communication settings can be performed for each connection. Settings are performed in SPW
command.If values are written to somewhere other than the general communication setting area, the
communication parameters will change and there is a chance that communication will not be possible, so
be careful not to mistake the writing destination address.
If general communication settings are enabled (FF), computer link method or file memory method cannot
be used for that connection.
Please do not set general communication settings to anything other than 00 or FF. (If 01 to FE is set, then
operation will be as per 00)
If settings are changed during communication, communication may not be performed correctly. Please do
not to change after setting.
11-3
The switchover status of the general communication method can be confirmed in the below areas.
1) File memory
When the applicable bit for each connection of file memory address 0107 is on, the general
communication method is enabled. When the applicable bit is off, the file memory method and
computer link method is enabled.
bit7 bit0
0100 1 1:Initial normal
0101 8 7 6 5 4 3 2 1 1 to 8:Connection 1 - 8 Open normal
0102 8 7 6 5 4 3 2 1 1 to 8:Connection 1 - 8 Connection error
0103 8 7 6 5 4 3 2 1 1 to 8:Connection 1 - 8 Sending complete
0104
0105 8 7 6 5 4 3 2 1 1 to 8:Connection 1 - 8 Receiving complete
0106 4 3 2 1 1: Error log receipt 2:ICMP log receipt 3:PING normal 4:PINGerror
0107 8 7 6 5 4 3 2 1 1 to 8:Connection 1 – 8 General communication method enabled
0108 (lower) A specific Ethernet address value is set for each of the Ethernet devices
0109
010A
010B Own Ethernet address
010C
010D
(upper)
MSB LSB
F E D C B A 9 8 7 6 5 4 3 2 1 0
S3#0 CN8 Active open request CN1 0 0 0 0 0 0 0 *1
S3#1 CN8 File memory sending request CN1 CN8 File memory sending request CN1
S3#2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 *3 *2
S3#3 CN8 Open normal 0 CN1
0 00 0 0 *5 *4
S3#4 CN8 File memory sending complete CN1 CN8
Connection error CN1
S3#5 0 0 0 0 *9 *8 *7 *6 CN8
File memory sending complete CN1
th *10
S3#6 4 digit of own Ethernet address 5 digit of own Ethernet address *10
th
S3#7 6th digit of own Ethernet address *10 CN8 General communication enabled CN1
S3#8 Connection 1:Connection error code
S3#9 Connection 2:Connection error code
S3#A Connection 3:Connection error code
S3#B Connection 4:Connection error code
S3#C Connection 5:Connection error code
S3#D Connection 6:Connection error code
S3#E Connection 7:Connection error code
S3#F Connection 8:Connection error code
*1:Initial request *2:Error log receive confirmation *3:ICMP log receive confirmation
*4:Initial normal *5:Initial error *6:Error log receive
*7:ICMP log receive *8:PING normal *9:PING error
*10:The upper 3 digits of the Ethernet address are 00.60.53 (fixed value).
“#” changes depending on the link number.
11-4
11.3 General communication sending
11.3.1 Sending procedures
If data is sent from the 2PORT-EFR module by the sequence program using the general
communication method, it is done so according to the below procedures. For file memory
addresses, please see the 2PORT-EFR instruction manual [Reference 2 File memory addr
ess map].
⑤
③ ④ ⑥
Other node
① In the sequence program, send data and transfer number is written to the file memory.
② Send request is turned on in the sequence program.
③ Send data is transferred to the sending processing section and “send complete” comes on.
④ The 2PORT-EFR module performs sending.
⑤ Once send complete has been confirmed in the sequence program, send request turns off.
⑥ Send complete will turn off on the 2PORT-EFR module when the send request turns off.
11-5
[ WMOV 1002 → R021 ]
V006 (Link №1, 2 byte transfer)
(1st scan only turns on
special relay) [ WMOV 29FC → R022 ]
(D04FE indirect address 29FCh=2000h+4FEh×2)
R Connection 1
K48 P005 K10 Send request off
Connection 1
Send complete
Note) On CPUs other than PC10G, the maximum amount of data that can be transferred in
one go with the SPW command is 1023 (3FFH) bytes therefore if the data amount
exceeds this, please execute the SPW command in two separate goes.
If data from DO100 to DO4FE is sent to this sequence program, data will be sent as
shown in the below example.
11-6
D0100=0100 D0101=0302
D0102=0504 D0103=0706
D0104=0908 D0105=0B0A
Send data
D0106=0D0C D0107=0F0E
D0108=1110
D04FD=FBFA
D04FE=07FC Transfer no. data
The send complete signal turns on when send data is handed to the communication module.
Therefore, at this stage send data is not sent out to the network (it does not equate to receiving
ACK from another node).
For TCP/IP, if the next data is requested while TCP is being sent, send data is held in the send
buffer. Furthermore, if the next send request is made, that data is joined with the previous data in
the send buffer and stored. If the first data is sent due to re-sending, the send data that was made
to wait during TCP re-sending will be joined and sent within the maximum segment size limitations.
If data is sent continuously, the above operation will be performed therefore we recommend
creating a communication program where, after data is sent once, response data from other nodes
is received (alternating with send).
Data 1
Data 1
Send complete ON
ACK
Data 2
Data 2
Send complete ON Fail
Data 2
Data 3 Fail
Data 2
Send complete ON Fail TCP re-sending
Data 2
Data 4 Fail
Data 2
Send complete ON Fail
Data 2
Data 5
ACK
Send complete ON
ACK
11-7
11.4 General communication receiving
If data is received from the 2PORT-EFR module by the sequence program using the gene
ral communication method (mode 1), it is done so according to the below procedures. For
file memory addresses, please see the 2PORT-EFR instruction manual [Reference 2 File
memory address map].
Other nodes
11-8
11.4.2 Receiving separated data
If the data is separated on the sending side, (when other nodes have tried sending data
exceeding the maximum segment size, etc) the separate batches of receive data arrive at
different times and are not stored in the file memory simultaneously.
In such cases the receive complete flag turns on at the point where the first data batch is
stored in the file memory. Receive complete does not necessarily mean that all data that
the other node has separated and sent has arrived. Please look at the receive data size
and data portion header information, etc. to judge whether all data has been received or
not.
SPR
Receive data 1 Receive data 1
Data received when the CPU has stopped running will remain saved in the file memory.
If the CPU is restarted as is, file memory content will be retained. If the CPU is reset then
restarted, 2PORT-EFR will be initialized and data received until then will be destroyed.
11-9
11.4.4 Sequence program example
Below is an example of a sequence program for file memory receiving.
Note) On the PC2J, PC3J series, the data size that can be read with SPR command is limited
to 1023 bytes.
To read more than 1023 bytes worth of data, divide the data into two halves.
11-10
11.4.5 Operation when file memory data reading is delayed
When new data is received before reading out data in the file memory, the new data is
joined with the old data and stored in the file memory as long as there is space.
If the file memory is full (2044 bytes), new data will not be destroyed, but will be temporarily
held in the receive buffer until space is made.
If multiple new data is received in that time, it will be joined with the data still stored in the
buffer.
If the receive buffer becomes empty without data being read from the file memory, flow
control will be performed on other nodes.
For TCP, the window size will become 0 and the sending of data from other nodes will be
stopped. For UDP, ICMP Source Quench response will be sent and data will be destroyed.
Receive buffer Data 1 Data 2 Data 3 Data 3,4 Data 3,4,5 Data 6
Receive complete
Receive confirmation
11-11
b) If receive buffer becomes empty(TCP)
Receive buffer Data 1 Data 2 Data 23 Data 234 Data 2345 Data 3b45 Data 3b456
Receive complete
Receive data loaded
Receive confirmation
Data 1 Data 2, 3a
Destroy
Receive Data 1 Data 2 Data 23 Data 234 Data 2345 Data 3b 45 Data 3b457
Receive
Receive data loaded
Receive
Data 1 Data 2, 3a
Note)If data is received when the CPU has stopped running the receive buffer will empty and
b), c) operations will be performed.
If the CPU is reset then restarted, the Ethernet module will be initialized causing receive d
ata to be lost.
If the CPU is simply restarted, the file memory and receive buffer will still contain valid dat
a so to receive new data, please discard this remaining data.
For TCP, it is possible to destroy data by reopening connection.
11-12
12 Warning by the Ethernet
(1) Hardware errorsFailures of the 2PORT-EFR module or communication errors with the CPU
module
'H*' (* = 0 to F) appears on the LED display of the 2PORT-EFR
module and error code 84 (a special module error) on the CPU
module.
See 11-2 'Hardware Errors.'
(2) Link parameter errorThe link module name as link parameter has been set to a wrong value
on the CPU module. Error code 89 (a link module
(3) Communication errorsA wrong I/O parameter setting (see section 11) or a failure of the
sequence program.
If an I/O parameter has been set to a wrong value,
appears on the LED display of the 2PORT-EFR module.
12-1
(4) Connection errorsA communication error with another node.
If a connection error occurs, the connection error code is stored in
the file memory and the connection error flag turns on.
Connection error codes for each connection may also be read from
the monitor area (see 2-2-6).
The connection No. of the connection with which an error
occurred and the error code are alternately indicated every second.
If connection 1 is reset after the specified number of TCP
re-transmissions (error code 4013), for example:
(5) Line errorsIf the line does not become available before the power-up or reset/start-up, the
LED display becomes as shown below.
Note: 10 Base-T cables for Ethernet are divided into two types;
straight and cross ones.
Use a straight one to connect the hub or a cross one to
make a direct 1:1 connection with another device.
12-2
(6) No initial dataIf initial data such as IP address is not received from the CPU module upon
the power-up or reset/start-up, the LED display becomes as shown
below.
12-3
12.2 Hardware Errors
When the 2PORT-EFR module does not normally operate due to a failure of the module or
peripheral equipment, it is considered as a hardware error.
Error code 84 (a special module error) appears on the CPU module.
An error code appears on the LED display at the front of the 2PORT-EFR module. Take
corrective action in accordance with the following table.
Error code on
Ethernet module Error content Cause and remedy
LED
H0 RAM error
H1 Flash memory error
H2 EEPROM error The Ethernet module is considered to be faulty.
H3 Ethernet error Replace it with a new one.
Application loading
HF error
Command Malfunctions of the Ethernet module, CPU module, base and I/O cable will prevent
H5 disagreement the normal sending and receiving of data between the Ethernet and CPU modules.
INTL clearness check If an error other than error code 84 is occurring on the CPU module, please perform
H6 error trouble-shooting on the CPU module.
If error code 84 is occurring on the CPU module, should this error also be occurring
Communication port on other communication modules, please perform trouble-shooting on the other
H7 hardware error modules first.
If the error cannot be cleared, please replace the Ethernet module, CPU module, I/O
System Abnormal
Hd execution cable and base one by one.
Malfunctions of the Ethernet module, CPU module, base and I/O cable will prevent
the normal sending and receiving of data between the Ethernet and CPU modules.
If an error other than error code 84 is occurring on the CPU module, please perform
trouble-shooting on the CPU module.
If error code 84 is occurring on the CPU module, should this error also be occurring
on other communication modules, please perform trouble-shooting on the other
There is no command
H9 response from CPU.
modules first.
If the error cannot be cleared, please replace the Ethernet module, CPU module, I/O
cable and base one by one.
Occurs if communication is being performed via the network from the Ethernet
module to a PC on another hierarchy when communication with connected devices
has not been normal for an extended period of time due to equipment power supply
being shut off, etc. When this error occurs, please reset or restart the CPU module in a
state where the network communicating with the other hierarchy is communicating
normally.
The link module name as a link parameter has been set to a wrong value. Select 'Ethernet' as
link module name.
For the peripheral equipment of an older type that does not have 'Ethernet' in its menu, select
'Computer link.'
12-4
12.4 Communication Errors
When an I/O parameter has been set to a wrong value with the 2PORT-EFR module or the
number of bytes to be transmitted with the file memory method is out of the specified range, it
is considered as an I/O error.
Error code 86 appears on the CPU module.
Error detailed data codes are recorded at the CPU module's special registers at the following
addresses determined by the link No. of the 2PORT-EFR module.
12-5
■ Communication Anomaly Error Code Table
Detailed Detailed Detailed
Error Code Description How to Dispose
Data 1 Data 2 Data 3
Ascertain whether your own IP address is correctly specified.
Note that the following IP addresses are not available:
・All bits of network ID are 0 or 1 solidly.
0113 Your own node IP address on the initialization command may be erroneous. 0000 0000 0000 ・All bits of host ID are 0 or 1 solidly.
・All bits of subnet ID are 0 or 1 solidly.
・The highest byte is 127 (7Fh).
(See Reference 5.)
0114 Gateway IP address on the initialization command may be erroneous. 0000 0000 0000 Ascertain whether the gateway IP address is correctly specified.
Ascertain whether the other node IP address is correctly specified.
・All bits of network ID are 0 or 1 solidly.
・All bits of host ID are 0 or 1 solidly.
0115 Other node IP address on the initialization command may be erroneous. 0000 0000 0000
・All bits of subnet ID are 0 or 1 solidly.
・The highest byte is 127 (7Fh).
(See Reference 5.)
Ascertain whether the other node port No. is correctly specified.
0116 Other node port No. (TCP) on the initialization command may be erroneous. 0000 0000 0000
The port No. should be between 0401h and FFFEh (1025 and 65534).
0117 Protocol on the initialization command may be erroneous. 0000 0000 0000 Ascertain whether the protocol (TCP:00 or UDP:01) is correctly specified.
Ascertain whether the mode (Active:00, Destination-Specified Passive:01, or
0118 Mode on the initialization command may be erroneous. 0000 0000 0000 Destination Non-Specified Passive:02) is properly written in File Memory
when you use TCP as the protocol.
Your own node port No. (TCP) on the initialization command may be Ascertain whether the other node port No. is correctly specified.
0119 0000 0000 0000
erroneous. The port No. should be between 0401h and FFFEh (1025 and 65534).
Ascertain whether the other node port No. is correctly specified and whether
011A Other node table No. on the initialization command may be erroneous. 0000 0000 0000
the specified table is set as "used" in the Using Table of initial parameter.
Your own node port No. (TCP) on the initialization command may be
011B 0000 0000 0000 Ascertain whether your own node port No. is not duplicated.
duplicated.
Your own node port No. (UDP) on the initialization command may be
011C 0000 0000 0000 Ascertain whether your own node port No. is not duplicated.
duplicated.
Resending-timer (data) value on the initialization command may be
011D 0000 0000 0000 Ascertain whether the timer value is within the specification.
erroneous.
Resending-timer (SYN,FIN) value on the initialization command may be
011E 0000 0000 0000 Ascertain whether the timer value is within the specification.
erroneous.
011F Closing-timer value on the initialization command may be erroneous. 0000 0000 0000 Ascertain whether the timer value is within the specification.
0120 Packet alive time on the initialization command may be erroneous. 0000 0000 0000 Ascertain whether the timer value is within the specification.
0121 IP assembly timer value on the initialization command may be erroneous. 0000 0000 0000 Ascertain whether the timer value is within the specification.
Limit the altering points between 0 and 1 of the subnet mask to one point only.
0125 Subnet mask on the initialization command may be erroneous. 0000 0000 0000
(See Reference 5.)
Configure the gateway address or ascertain whether there is not any error on
0126 Gateway IP address on the initialization command is not configured. 0000 0000 0000 your own node IP address and other node IP addresses.
(See Reference 5.)
12-6
0127 The initial command indicates an invalid number of re-transmissions. 0000 0000 0000 Ascertain whether the number of retransmissions is within the specified range.
This anomaly shows that Other Node Table No. is not specified for the
0134 Other node table No. on the active opening command may be invalid. Connection No. 0000 0000 connection designated as TCP Active. Ascertain whether the Other Node
Table No. is correct and whether the specified table is set as 'used.'
2080 Faulty response timer value of the initial data 0000 0000 0000 Ascertain whether the timer value is within the specification.
2081 Faulty non-reception timer value of the initial data 0000 0000 0000 Ascertain whether the timer value is within the specification.
Check whether the transfer data size at the head of transmission data area is
Transfer
2082 Faulty transmission data transfer number Connection No. 0000 between 0 and 2044 (7FCh) and whether the transfer data size is properly
number
written in the file memory.
Reception confirmation flag has been already hoisted when the fail reception
2085 Connection No. 0000 0000 Ascertain whether the reception confirmation flag is not kept hoisted.
is completed.
12-7
12.5 Connection Errors
When the data received from another node has an error, it is considered as a connection error.
In this case, the error is indicated by the following devices.
If a connection error occurs, an error response may be transmitted to the other node.
12-8
12.5.1 Connection Anomaly Error Code Table
12-9
This arises if the second datum (RC:response code) of received data is one besides "00"
Faulty reception data frame format (Abnormal RC) (1)(2)(3) 4005 **.02 Opening from other node when file memory data or computer link command is received. Verify your transmission
data.
Occurs if the transfer number data (LL, LH) of the received data is 0000 but exceeds 1274
Faulty reception data frame format (Abnormal
(1)(2)(3) 4005 **.03 Opening from other node bytes (computer link command) or 2044 bytes, (file memory sending, general-purpose
transfer number)
communication sending). Confirm the sent data.
This arises if the next computer link command is received before resending the response to
Though a computer link command has not processed
(1)(2)(3) 4006 80.06 Opening from other node a received computer link command. Verify the computer link command transmission
yet, the next computer link command is received.
timing.
Though a file memory transmission has not This arises if the next file memory data is received before resending the response to
(1)(2)(3) 4007 E0.07 Opening from other node
processed yet, the next file memory data is received. received file memory data. Verify the file memory data transmission timing.
Relay command has a wrong transfer data size or ENG code. Check the content of relay
Faulty relay command format (1)(2)(3) 4008 80.04 Opening from other node
command.
Connection reset or closed during file memory In Lowering Transmission
(1) 4009 - A connection was reset or closed during file memory transmission process.
transmission process. Request Flag
Data from another node cannot be received for a time longer than specified by
Non-reception timer is time up (1)(2) 4010 - Opening from other node Non-Reception Timer as initial parameter (defaulted 00: undefined). Check the setting of
Non-Reception Timer.
Reception confirmation (ACK) signal was not received from the other node after the
Connection reset after specified number of TCP number of communication retries specified by 'reset wait resending times' as initial
(1)(2) 4013 - Opening from other node
re-transmissions parameter. This occurs when the other node is powered off or the cable has a cut wire.
(See 7-4.)
The connection designated as TCP non-specified passive open is reset if opening request is
Connection reset by multiple connection opening
(1)(2) 4014 - Opening from other node sent to the same port from another node when the connection is open. As opening request
request from another port with the same IP address
is sent from another node later, the connection with that node opens. (See 7-4.)
Error Response Reception to file memory
In Lowering Transmission This arises if the response code (RC) received from other node is not "00" after a file
transmission from other node (1)(2) 30++ -
Request Flag memory data transmission. Verify the response data.
[++=response code: RC]
NAK response from J-CPU during computer link Received computer link command has an error and could not be normally processed.
(3) - (4) -
command process Check the content of computer link command.
Occur if an improper open/close request is received from another mode. Please check the
Connection errors other than the above (1)(2) 013+ - Opening from other node
communication program of the other node.
12-10
In lowering transmission The number of transmission bytes in the file memory is wrong. Check transfer data size at
Wrong number of file memory transmission bytes (1) 4003 -
request flag the head of the file memory transmission data area.
This arises if file memory data or computer link command is received or if the
In hoisting opening request transfer-number data (LL,LH) exceeds data number to be actually transmitted or the data is
Inability to receive data by the transfer number (1)(2)(3) 4004 **.05
flag discontinued in the middle. Ascertain whether the transfer-number data is appropriate and
whether all one-frame data are transmitted.
This arises if the head data (FT:frame type) of reception data is abnormal.
In hoisting opening request
Faulty reception data frame format (Abnormal FT) (1)(2)(3) 4005 ***.01 FT must be one of the following: FT=00(computer link command),FT=60(file memory
flag
transmission), FT=E0(the corresponding response to transmitted file memory)
This arises if the second datum (RC:response code) of received data is one besides "00"
In hoisting opening request
Faulty reception data frame format (Abnormal RC) (1)(2)(3) 4005 **.02 when file memory data or computer link command is received. Verify your transmission
flag
data.
This arises if the transfer-number data (LL,LH) of received data is "0000," exceeds 1274
Faulty reception data frame format (Abnormal In hoisting opening request
(1)(2)(3) 4005 **.03 bytes (computer link command), or exceeds 2044 bytes (file memory transmission). Verify
transfer number) flag
your transmission data.
Though a computer link command has not processed This arises if the next computer link command has been received before resending the
In hoisting opening request
yet, the next computer link command has been (1)(2)(3) 4006 80.06 response to a received computer link command. Verify the computer link command
flag
received. transmission timing.
Though a file memory transmission has not
In hoisting opening request This arises if the next file memory data has been received before resending the response to
processed yet, the next file memory data has been (1)(2)(3) 4007 E0.07
flag received file memory data. Verify the file memory data transmission timing.
received.
In hoisting opening request Relay command has a wrong transfer data size or ENG code. Check the content of relay
Faulty relay command format (1)(2)(3) 4008 80.04
flag command.
Connection reset or closed during file memory In lowering transmission
(1) 4009 - A connection was reset or closed during file memory transmission process.
transmission process. request flag
This arises if data from other node cannot be received for the period or more that is set by
In hoisting opening request
Non-reception timer is time up (1)(2) 4010 - Non-Reception Timer (default 00:undefined) of file memory. Check the setting of
flag
Non-Reception Timer.
In hoisting opening request This arises if the other node has closed the connection after your own node opened a
Other node has closed the connection. (1) 4011 -
flag connection through an active opening.
In hoisting opening request This arises if the other node has reset the connection after your own node opened a
Other node has reset the connection. (1) 4012 -
flag connection through an active opening.
Reception confirmation (ACK) signal was not received from the other node after the number
Connection reset after specified number of TCP In hoisting opening request
(1) 4013 - of communication retries specified by 'reset wait resending times' as initial parameter. This
re-transmissions flag
occurs when the other node is powered off or the cable has a cut wire. (See 7-4.)
Error Response Reception to file memory
In hoisting transmission This arises if the response code (RC) received from other node is not "00" after a file
transmission from other node (1)(2) 30++ -
request flag memory data transmission. Verify the response data.
[++=response code: RC]
NAK response from J-CPU during computer link Received computer link command has an error and could not be normally processed.
(3) - (4) -
command process Check the content of computer link command.
Occurs if the send complete flag turns off while data is being sent, and sending is performed
In hoisting opening request
Continuous open (1)(2) 0132 - again. If it occurs, please reset the CPU module. Please modify the program so that the send
flag
request flag turns off after data sending is complete or a connection error has occurred.
12-11
(iii) In case of UDP connection
Find & Error response
Connection
Description Correct data to the other Clear Timing of Anomaly Occurrence Cause of Anomaly and Corrective Action
Anomaly Code
Trouble node
No response is sent from the other node for the time specified by Response Timer as initial
File Memory transmission response data reception In hoisting transmission
(1) 4002 - parameter (defaulted 6 secs) after file memory data is transmitted from 2PORT-EFR
time is up. request flag
module. Check that file memory is normally processed by the other node.
In hoisting transmission The number of transmission bytes in the file memory is wrong. Check transfer data size at
Wrong number of file memory transmission bytes (1) 4003 -
request flag the head of the file memory transmission data area.
This arises if file memory data or computer link command is received or if the
transfer-number data (LL,LH) exceeds data number to be actually transmitted or the data is
Inability to receive data by the transfer number (3) **.05 -
discontinued in the middle. Ascertain whether the transfer-number data is appropriate and
whether all one-frame data are transmitted.
This arises if the head data (FT:frame type) of reception data is abnormal.
Faulty reception data frame format (Abnormal FT) (3) ***.01 - FT must be one of the following: FT=00(computer link command),FT=60(file memory
transmission), FT=E0(the corresponding response to transmitted file memory)
This arises if the second datum (RC:response code) of received data is one besides "00"
Faulty reception data frame format (Abnormal RC) (3) **.02 - when file memory data or computer link command is received. Verify your transmission
data.
This arises if the transfer-number data (LL,LH) of received data is "0000," exceeds 1274
Faulty reception data frame format (Abnormal
(3) **.03 - bytes (computer link command), or exceeds 2044 bytes (file memory transmission). Verify
transfer number)
your transmission data.
Though a computer link command has not processed This arises if the next computer link command has been received before resending the
yet, the next computer link command has been (3) 80.06 - response to a received computer link command. Verify the computer link command
received. transmission timing.
Though a file memory transmission has not
This arises if the next file memory data has been received before resending the response to
processed yet, the next file memory data has been (3) E0.07 -
received file memory data. Verify the file memory data transmission timing.
received.
Relay command has a wrong transfer data size or ENG code. Check the content of relay
Faulty relay command format (3) 80.04 -
command.
Error Response Reception to file memory
In hoisting transmission This arises if the response code (RC) received from other node is not "00" after a file
transmission from other node (1) 30++ -
request flag memory data transmission. Verify the response data.
[++ = response code: RC]
NAK response from J-CPU during computer link This arises if received computer link command has any fault resulting in abnormal
(3) - (4) -
command process transaction. Verify the computer link command contents.
12-12
12.5.2 Error Response Data Error Code Table
If any NAK (anomaly) reply is returned as the computer link command error response
"80.10.01.00. " ( :Error Code) or as the relay command response, refer to the
following table for reviewing your command data:
: Error Code Error Description
11 Inability to process data because of faulty CPU Module Hardware
20 Fixed Data (ENQ) within relay command is not "05."
21 Faulty transfer number (there is erroneous transfer byte number within the relay command.)
23 Erroneous command code
24 Erroneous subcommand code
25 Erroneous command-format data byte
26 Erroneous function-call operand number
Attempting to write data into the field where any writing is prohibited during a sequence
31 operation or to use the function call which is protected from any execution during a sequence
operation.
32 A command that is defeated during a stop continuity is activated during a stop continuity.
33 Attempting to execute a debug function call despite non-debug mode
34 Access prohibited owing to access-prohibited configuration
35 Non-executable owing to execution-priority limiting configuration (*)
36 Non-executable owing to execution-priority limiting configuration by another device (*)
Attempting to start scanning without any reset after writing I/O point-number parameters or I/O
39
allocation point-number parameters
3C During a fatal failure, a command has issued that is not executable during a fatal failure
3D Non-executable due to competing process while a different-factor command is executed.
3E Non-executable command due to reset existence
3F Non-executable command due to stop duration
Address of a reading/writing command or of "address + data number" of a command is out of
40
range.
41 Word/byte number is out of range.
42 Non-designated data is sent.
43 Erroneous function-call operand
Though any timer or counter is employed, a command for reading/writing the set/recent values is
52
issued.
No reply is sent from link module with the link exchange No. specified by a relay command
66
(Owing to no existence of specified link module, power OFF, or faulty circuit, etc.)
Non-executable module with the link exchange No. specified by a relay command (Owing to
70
erroneous link No. designation or faulty link module)
No reply is sent from link module with the link exchange No. specified by a relay command
72
(Owing to no existence of specified link module, power OFF, or faulty circuit, etc.)
Multiple relay commands were issued to the same link module from the CPU module and the
73
link module could not process the commands. (Send commands again.)
*: See command (22), reading execution priority limitation state or (23), setting execution
priority limitation.
If any error code other than the above is returned, review the entire command data.
12-13
13 Ethernet Communication Transaction Time
Use the following equality to figure out Transfer Delay Time for Computer Link Method
Communication or File Memory Method Communication.
Note that the Transfer Delay Time can be extended further depending upon network active ratio and
system formation.
Consider the value calculated from the equity below as an aim of minimum transfer delay time.
If any data is not transmitted due to heavy congestion on the circuit on data collision occurs on the
line, the 2PORT-EFR module waits for the period specified by Resending Timer as an I/O
parameter before attempting to re-transmit.
(*1: If the sequence scan time exceeds 25 ms, use 25 ms for calculation.)
Caution) The said Command Byte Number and Response Byte Number is identical to
TOYOPUC data-unit byte number specified in Chapter 6. Computer Link Method.
13-1
(2) File Memory Method
The time to be spent by the communicatee, after the communicator hoists the transmission
request flag, to read the reception data into registers, hoist the reception confirmation flag, and
send a response back to the communicator before the transmission completion flag at the
communicator turns on under a communication between TOYOPUC 2PORT-EFR modules.
Caution) Transmission Data Byte Number above is the byte number (value of LL, LH) of file
memory data to be transmitted.
13-2
(3) General communication method
Below is the time taken from the point where the send request flag turns on on the sending
side and the data is read to the register on the receiving side when two TOYOPUC 2POR
T-EFR modules communicate with each other.
Send →
■ Common to TCP/UDP
Transmit delay time=13+(4 + 0.003X send data byte no. )×Used connection no. +
Sending-side sequence scan time + receiving-side sequence scan time ×3
(Note:Send data byte no. is the byte no. of the file memory data sent (LL,LH values).
13-3
14 FL-Remote initialization
The following explains about the parameter setting method for the below configuration.
Connect LS with i4 Connect valve with 02
2PORT-EFR
2TRO
21436587S
R
N
8 Slave
L S S
LLST
L
2PORT-EFR
TxD RxD
1 3 5 7
2 4 6 8 STATUS
2. After starting PCwin and setting parameters, select I/O module and align the rack number with 8.
14-1
3. In settings, designate Ethernet for slot 0 and FL Remote-M for slot 1.
14-2
[Setting detailed setup]
(1) (9)
(2) (8)
(3)
(7)
(4) (6)
(5)
14-3
(3) [Slave setup]
Slave No. at Slave setup list is clicked, [Slave setup] is clicked, and detailed parameter of Slave
is set up. Please refer to "Setting detailed parameter of Slaves" for details.
(9) [Network]
It is not necessary to set it for this item.
14-4
[Setting the detailed parameter of slaves]
(4)
(1)
(2)
(3)
(1)
(2)
14-5
14.3 COLLECTION OF DIAGNOSIS DATA
In FL-remote, there are diagnosis data as ‘general-purpose status’, ‘short circuit data’, ‘disconnection
data’, and ‘validity/invalidity of the disconnection detecting function’ besides the I/O data.
I/O allocation by the link parameter of FL-remote (Refer to “14.3.1 Collection of Diagnosis Data by
Link Parameter” about details)
1. I/O data: the top address is set to ‘link area’.
2. General-purpose status and error record reset / arbitrary reading switch: the top address is set to
‘General-purpose status area’ in the extended setting.
3. Validity/invalidity of the disconnection detecting function: ‘validity/invalidity of the disconnection
detecting function’ is set for the I/O address of the each slave. This data is kept during turning off
the slave's power supply.
4. Short-circuit data: the top address is set to ‘ Short-circuit state area’ in the extended setting.
5. Disconnection data: the top address is set to ‘ Unconnected state area’ in the extended setting.
(Note 1) In general-purpose status, error record reset / arbitrary reading switch, validity/invalidity of the
disconnection detecting function, short-circuit data and disconnection data, the target slave is
FRMT series and these are effective when set by the link parameter, diagnosis function
"Enable".
(Note 2) If the diagnosis functions of all slaves are ‘Disable’, ‘General-purpose status area’ of the node
01-63 must be set to the unused area because these are always I/Orefreshed.
14-6
14.3.1 Collection of Diagnosis Data by Link Parameter
I/O allocation to CPU for ‘general-purpose status’, ‘short-circuit data’ and ‘disconnection data’, and the
setting of ‘validity/invalidity of the disconnection detecting function’ are set to the link parameter of
FL-remote with PCwin (Ver8 or later).
Please refer to “14.1 Parameter Setting” for the method of setting the link parameter.
Initial setting is "general-purpose status area" D000L-D003FH, "short-circuit information area"
D0040L-D007FH", and "Un-connect information area" D0080L-D00BFH.
‘validity/invalidity of the
disconnection detecting function’
are set.
‘ ’ is checked to the I/O address
‘ ’ : validity, ‘ ‘ : invalidity
14-7
14.3.2 General-purpose Status
If the general-purpose status is allocated to CPU by the link parameter, ‘general-purpose status’ is
allocated to the top address to set [+00L] – [+1FH], and ‘error record reset / arbitrary reading switch’ is
allocated to [+20L] – [+3FH] in CPU. (Refer to “14.3.2 Error Record Reset / Arbitrary Reading Switch”
about details)
The general-purpose status and the error record reset / arbitrary reading switches are allocated in 1byte
per 1node.
(Note) Even if the diagnosis functions of all slaves are set to ‘Disable’ in the link parameter of FRMT, the
general-purpose status and the error record reset / arbitrary reading switch of the node 01-63 are
allocated.
Allocation of the general-purpose status and error record reset / arbitrary reading switch
relative byte data
address
+00L
+00H node 01 : general-purpose status
| |
| | General-purpose status area
| |
+1FL node 62 : general-purpose status
+1FH node 63 : general-purpose status
+20L
+20H node 01 : error record reset /
arbitrary reading switch
| | Error record reset / arbitrary reading switch
| |
| |
+3FL node 62 : error record reset /
arbitrary reading switch
+3FH node 63 : error record reset /
arbitrary reading switch
14-8
14.3.3 Error Record Reset / Arbitrary Reading Switch Format
In DRMT series, after detecting ‘short-circuit’ and ‘disconnection’, if the factor is removed, I/O control is
returned automatically but the short-circuit data and the disconnection data are kept and I/O LED is
maintained in the red flicker.
Setting various bits of the error record reset switch can reset these kept data.
The error record and the error are loaded to the diagnosis data map (Refer to “14.3.3 Diagnosis Data
Map” about details) by setting various bits of the arbitrary reading switch.
14-9
(1) Format of short-circuit data area (U7040L ~ U707FH)
Relative
Data Content Data format
address
+00L Get/Set flag Bit0=0 : Get, Bit0=1 : Set, Bit1 – 7=0 fixed
+00H (Unused) 00h fixed
+01L Node address (Hex) 00h – 3Fh (0 – 63)
+01H (Unused) 00h fixed
+02L Response code Lo 69h
Short-
circuit +02H Response code Hi 00h fixed
+03L Error code Lo error code (Lo) of message response (Normal : 00h)
Record +03H Error code Hi error code (Hi) of message response(Normal : 00h)
data0 +04L MSB LSB
+04H 07 06 05 04 03 02 01 00
newest
data +05L 0F 0E 0D 0C 0B 0A 09 08
+05H Short-circuit record data | | | | | | | |
+06L I/O 0 – 63 | | | | | | | |
3F 3E 3D 3C 3B 3A 39 38
+06H
Numerical value : I/O Address
+07L
Bit data=0 : Normal , Bit data=1: Short-circuit
+07H
+08L Get/Set flag Bit0=0 : Get, Bit0=1 : Set, Bit1 – 7=0 fixed
+08H (Unused) 00h fixed
+09L Node address (Hex) 01h – 3Fh (1 – 63)
+09H (Unused) 00h fixed
+0AL Response code Lo 67h
Short-
+0AH Response code Hi 00h fixed
circuit
+0BL Error code Lo error code (Lo) of message response(Normal : 00h)
Current +0BH Error code Hi error code (Hi) of message response(Normal : 00h)
data0 +0CL MSB LSB
+0CH 07 06 05 04 03 02 01 00
newest
data +0DL 0F 0E 0D 0C 0B 0A 09 08
+0DH Short-circuit current data | | | | | | | |
+0EL I/O 0 – 63 | | | | | | | |
3F 3E 3D 3C 3B 3A 39 38
+0EH
Numerical value : I/O Address
+0FL
Bit data=0 : Normal , Bit data=1: Short-circuit
+0FH
Short- Same as record data0 Same as record data0
+10L
circuit
|
Record
+17H
data1
Short- +18L Same as current data0 Same as current data0
circuit
Current
|
data1 +1FH
Short- +20L Same as record data0 Same as record data0
circuit
Record
|
data2 +27H
Short- +28L Same as current data0 Same as current data0
circuit
Current
|
data2 +2FH
Short- +30L Same as record data0 Same as record data0
circuit
Record
|
data3 +37H
Short- Same as current data0 Same as current data0
+38L
circuit
|
Current
+3FH
data3
14-10
(2) Format of disconnection data area (U7080L ~ U70BFH)
Relative
Data Content Data format
address
+00L Get/Set flag Bit0=0 : Get, Bit0=1 : Set, Bit1 – 7=0 fixed
+00H (Unused) 00h fixed
+01L Node address (Hex) 01h – 3Fh (1 – 63)
+01H (Unused) 00h
+02L Response code Lo 6A
Disco-
+02H Response code Hi 00h
nnection
+03L Error code Lo error code (Lo) of message response(Normal : 00h)
Record +03H Error code Hi error code (H) of message response(Normal : 00h)
data0 +04L MSB LSB
+04H 07 06 05 04 03 02 01 00
newest
data
+05L 0F 0E 0D 0C 0B 0A 09 08
+05H Disconnection record data | | | | | | | |
+06L I/O 0 – 63 | | | | | | | |
3F 3E 3D 3C 3B 3A 39 38
+06H
Numerical value : I/O Address
+07L
Bit data=0 : Normal , Bit data=1: Disconnection
+07H
+08L Get/Set flag Bit0=0 : Get, Bit0=1 : Set, Bit1 – 7=0 fixed
+08H (Unused) 00h fixed
+09L Node address (Hex) 01h – 3Fh (1 – 63)
+09H (Unused) 00h fixed
+0AL Response code Lo 68h
Disco- +0AH Response code Hi 00h fixed
nnection
+0BL Error code Lo error code (Lo) of message response(Normal : 00h)
Current +0BH Error code Hi error code (Hi) of message response(Normal : 00h)
data0 +0CL MSB LSB
+0CH 07 06 05 04 03 02 01 00
newest
data +0DL 0F 0E 0D 0C 0B 0A 09 08
+0DH Disconnection current data | | | | | | | |
+0EL I/O 0 – 63 | | | | | | | |
3F 3E 3D 3C 3B 3A 39 38
+0EH
Numerical value : I/O Address
+0FL
Bit data=0 : Normal , Bit data=1: Disconnection
+0FH
Disco- Same as record data0 Same as record data0
+10L
nnection
|
Record
+17H
data1
Disco- +18L Same as current data0 Same as current data0
nnection |
Current
data1 +1FH
Disco- +20L Same as record data0 Same as record data0
nnection |
Record
data2 +27H
Disco- +28L Same as current data0 Same as current data0
nnection |
Current
data2 +2FH
Disco- +30L Same as record data0 Same as record data0
nnection |
Record
data3 +37H
Disco- Same as current data0 Same as current data0
+38L
nnection
|
Current
+3FH
data3
14-11
Example of handling short circuits and disconnection information
Configuration example Example of outputting the short circuit and disconnection information of station
no. 41(DRMT-16/16P) to the direct monitor (panel computer).
General status storage area:D0380L to D03BFH
Short circuit information storage area: D0300L to D033FH
Disconnection information storage area: D0340L to D037FH
Sequence program example
Short circuit information arbitrary read switch D3B4-C
Input short info read
Short Station 41
exists FUN 577 FUN 111
Short info → Output to monitor
[ =D D0301L = 41d ] [ DMOVE D0304 → EM104W ]
FUN 101
[ WMOV 0h → D0300 ] Clear “get short history” flag
Short fault
FUN 752 M010
Short occurrence
[ D >H EM104W > 0h ]
(Maintenance call buzzer, etc)
*1 M020
Disconnect info read *1
Disconnect
Station 41 Disconnect info read *1
exists M020 Disconnect info → Output to monitor
FUN 577 FUN 111
M001
[ =D D0341L = 41d ] [ DMOVE D0344 → EM106W ]
FUN 101
[ WMOV 0h → D0340 ] Clear “get disconnect history” flag
M011
Disconnect fault FUN 752
Disconnect occurrence
[ D >H EM106W > 0h ]
(Maintenance call buzzer, etc)
Terminal block 1_I/O power EM1060
D394-8
I/O power 1 → Output to monitor
14-12
15. Warning by the FL-Remote
If an error is detected in FL Remote, these errors will be reported to FL Remote and the CPU.
For FL Remote, error alerts are performed using LED1 and LED2 lamps and a message display.
For CPU, error alerts are performed using special relays, special registers (register for error information
output, register for link error information output) and a message display.
It is also possible to check the status of FL Remote communication on the special register.
15-1
15.1. 1B Error information by CPU
(1) Special Relay
All station in communicating flag turn ON at normal, and other flags are turned ON at error.
Contents At At
Address
normal error
VA0 Link No.1 All station in communicating
VA4 Link No.2 All station in communicating
VA8 Link No.3 All station in communicating
VAC Link No.4 All station in communicating Note) When the unlinking
1 0
VB0 Link No.5 All station in communicating function is set, it becomes 0.
VB4 Link No.6 All station in communicating
VB8 Link No.7 All station in communicating
VBC Link No.8 All station in communicating
VA1 Link No.1 Link parameter error
VA5 Link No.2 Link parameter error
VA9 Link No.3 Link parameter error
VAD Link No.4 Link parameter error
0 1
VB1 Link No.5 Link parameter error
VB5 Link No.6 Link parameter error
VB9 Link No.7 Link parameter error
VBD Link No.8 Link parameter error
VA2 Link No.1 Communication error
VA6 Link No.2 Communication error
VAA Link No.3 Communication error
VAE Link No.4 Communication error
0 1
VB2 Link No.5 Communication error
VB6 Link No.6 Communication error
VBA Link No.7 Communication error
VBE Link No.8 Communication error
VC4 Error with special module(Communication module failure) 0 1
I/O configuration error
VC8 (Communication modules are mounted more than the regulated 0 1
number.)
Special module allocated error
VF2 (Rack No., Slot No., Link module name in link parameter different from 0 1
state of mounting.)
(Note) The address of the special relays are the case of the PC2 compatible mode and the data
memory separate mode (the PC3 mode).
ON:1
OFF:0
15-2
(2) Special Register
FL-remote stores the data of error condition and communication condition into the following address
of PLC.
Address Contents
S200
| CPU error output register
S24F
S3#0
Normal slave data area
S3#1
This displays the communication conditions
S3#2
(normal / error) of each slave.
S3#3
The master status area
S3#4
Indicating master and network status. *1
S3#5 Software version (BCD)
S3#6 The number of times of re-issuing token
S3#7 The number of times of token retention timeout
S3#8 The number of times of token monitor timeout
S3#C
| Connection office connection state
S3#F
S3*0
| Link error output register
S3*B
S3*C
S3*D
Unlinking register
S3*E
S3*F
The # and * portion of the above address are determined by link No.
Link No. 1 2 3 4 5 6 7 8
# 0 2 4 6 8 A C E
* 1 3 5 7 9 B D F
(Note) Information stored in the register S200 to S24F and S3#0 to S3*B is not cleared after
restoration from error.
When information must be cleared, write "0000" to the register with PCwin, etc.
The address of the special resisters are the case of the PC2 compatible mode and the data
memory separate mode (the PC3 mode).
* * * * * * * *
Node address
duplication E7
Transfer error D9
Checking error D6
Master communication speed [0: 10M, 1:100M]
Setting up for communication 1: Setting up for communication
(since power is turned on until communication is established)
Common memory sending area duplication, Error E8 and E9
15-3
(3) Special Register for CPU Error Information Output
When any error is detected, error code, error related information, and error detection time are stored
in the special register for error information. This register is a 8-step shift register and can store up to
8 errors.
When error are detected more than 8 times, the oldest error information is lost.
Error information stored in the register can be displayed by the peripheral device.
Contents of register
Adress
S200
Error 0 Information Error code
S20A
Error 1 Information Error related information 1,2
S214
Error 2 Information Error related information 3,4
S21E
Error 3 Information Error detection time(Second)
S228
Error 4 Information Error detection time(Minute)
S232
Error 5 Information Error detection time(Hour)
S23C
Error 6 Information Error detection time(Day)
S246
Error 7 Information Error detection time(Month)
S24F
Error detection time(Year)
Error detection time
Lost (Day of the week) 0~6:Sun-Sat
Link parameter
rack
FUNC. I/O Rack Slot
89 No. slot No. - - VF2 ON
ALARM No. No.
module
name error
(Note) This differs from error code of FL-remote.
Error information saved in S200- is also stored in S1000- for Ver.3.00 and thereafter.
(See the item 5.1.4 Error information output special resister)
15-4
(4) Link Error Data Output Special Register
At detection of error in FL-remote, error message is carried out to CPU, and the error code of
FL-remote is stored into the link error data output special register.
This register has an 8-step shift register structure, and can memorize up to 8 errors.
At errors over 8 errors, the first stored error data is deleted.
Note 2) When “Collation error (I/O bytes discrepancy)“, the number of I/O bytes is stored in the
S3*1 – S3*4.
S3*1 : The number of I/O bytes of the real slave. (low byte)
S3*2 : The number of I/O bytes in the link parameters. (low byte)
15-5
Error Code Details and FL-remote Error Display
Error
Display S03*0 S03*1 Detail
code
89 E5 --- --- Link parameter is not set yet.
85 E7 00F0 00F2 Own node number duplication error
85 ED 00ED 0000 Area overflow
85 E6 0021 0000 Total byte count has exceeded the limit.
85 E6 0022 0000 Station number with byte count 0 is found.
E6 Input or output byte count of 1 slave has
85 0023 0000
exceeded the limit.
85 E6 0025 0000 Communication area overflow
E6 I/O of CPU and communication area are
85 0026 0000
duplicated.
85 E6 0027 0000 Module sub-code error
85 E6 0028 0000 Module No. error
85 E6 0029 0000 Minimum permissible frame interval error
85 E6 002A 0000 Own node number error
85 E6 002B 0000 Network address error
86 E8 00E8 0000 Common memory 1 duplication error
86 E9 00E9 0000 Common memory 2 duplication error
86 EA 00EA 0000 Token monitor timeout error
86 EB 00EB 0000 Cyclic data reading error
86 EC 00EC 0000 Cyclic data writing error
FL- *3Checking error
remote S03*1H actual input byte count (HEX)
##D6 *3 S03*1L actual output byte count (HEX)
S03*2H input byte count (HEX)
86 D6 S03*2L output byte count (HEX)
86 D9 ##D9 0000 Transfer error
84 H5 --- --- Some other trouble of hardware
Hd Special module allocation exceeded or
84 --- ---
2PORT-EFR hardware error
84 H0 --- ---
84 H1 --- ---
84 H2 --- ---
84 H3 --- --- 2PORT-EFR module hardware error
84 HE --- ---
84 HF --- ---
84 HL --- ---
84 HU --- ---
84 H4 --- --- 2PORT-EFR module and CPU module interface
84 H6 --- --- hardware error
84 H7 --- ---
84 H8 --- ---
84 H9 --- ---
84 HA --- ---
84 HC --- ---
84 DL --- --- Maintenance mode
15-6
15.2. 2B Communication Status
FL-remote outputs the communication status in the special register.
(1) Normal Slave Data Area
Each bit of normal slave data area shows communication status of each slave.
The state flags of each slave are output to special register S3#0 - S3#3.
Each bit No. represents node address.
MSB LSB
S3#0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
S3#1 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
S3#2 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
S3#3 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
1: Communication normal state
0: Communication error state (or node not to use)
(Either communications error or verification errors have occurred.)
15-7
(2) Communication state confirmation function
This function is the standard of the stability of the communication line. The communication
error does not necessarily occur, even if error occurs. It is possible that the communication
error occurs when error occurs frequently.
15-8
Saving circuit of the number of errors
The total number of CAN errors (CAN error data area) is cleared by power off or CPU reset at
the communication error. But it is not cleared by the communication reset. So, please design the
following sequence circuit to save the total number of CAN errors.
Example)
The following circuit is saving the slave state, master status, number of CAN error and time of
error occurrence
Communication error flag
(Link No. 1)
Txxx
VA2
TMR K=1.0 1sec timer
Txxx P***
Slave state
WBMOV S3#0 → D0FF0= 0012D Master status
Number of CAN
error transmission
D0FF0
1 Normal slave data area
2
3
4 Master status area
5
6
7
8 Number of CAN error
9
A
B time minute, sec (BCD)
C time day, hour (BCD)
D time year, month (BCD)
E
15-9
(3) Connected slave setting area
It is an area where the connection of the slave set in the link parameter of the CPU is shown. The
state flag of each slave is output to special register S3#C-3#F.
0 shows the master, and each bit number shows the node address (station number).
MSB LSB
S3#C 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
S3#D 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
S3#E 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
S3#F 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
15-10
15.3. Error Contents and Supposed Causes
Specialr
egister Master7
content segement
Error description Main probable causes How to reset
display
note)
(1) CPU parameters not set (1) Revise CPU module
correctly parameter settings
(2) Setting was made in a
CPU module NAK CPU module not supporting (2) Modify switch settings
- H5 response FL-net 16KB or 32KB mode (3) Replace 2PORT-EFR
(3) Malfunction of the module, CPU module or
2PORT-EFR module, CPU base
module or base
The 2PORT-EFR module is Refering to [4.2 Switch
Special module malfunctioning or error code Settings], check that the total
allocation exceeded or 81 [Special module link memory capacity does
- Hd
2PORT-EFR module allocation exceeded] is not exceed 60K. (excluding
hardware error occurring on the CPU PC10) Replace the module if
module. the error cannot be cleared.
- H0
- H1
- H2
- H3 2PORT-EFR module 2PORT-EFR module
Replace module
- HE hardware error malfunction
- HF
- HL
- HU
- H4
Due to a malfunction on the
- H6
2PORT-EFR module, CPU
- H7 module, I/O cable or base, Replace the
2PORT-EFR module and data is not being properly 2PORT-EFR2PORT-EFR
- H8 CPU module interface passed between the module, CPU module, I/O
hardware error 2PORT-EFR module and
- H9 cable, or base.
CPU module.
- HA
- HC
15-11
Specialr
egister Master7
content segemen Error contents Main supposed cause Recovery method
t display
note)
Total number of bytes
0021 E6
exceeding limitation value
Station with 0 byte
0022 E6 Link parameter error
present Rewrite normal parameter,
and reset or supply power
Number of bytes for input Error with CPU main body
once again.
0023 E6 / output per one slave or memory
exceeding limitation value Disappearance of memory
Please refer to the manual
Input / output designation
data by a battery voltage of each CPU for details.
0024 E6 drop of CPU main body.
error
0025 E6 Range over
CPU input / output and
0026 E6
range in duplication
0027 E6 Sub code error
64F0 E7 Master duplication
Common memory Two or more master Separate any other master
sending area modules are connected to module from the network,
00E8 E8
Address duplication the network. and turn on power again.
(relay link)
Common memory FL-net module is Separate FL-net module
sending area connected to the same from the network, and turn
00E9 E9 Address network. on power again.
communication
(register link)
15-12
Special
Master 7
register
segment Error contents Main supposed cause Recovery method
contents
indicator
*
15-13
16 Specifications
16-1
Reference 1 Reading/Writing FileMemory through SPR and SPW Commands
If the read-out instruction as the above example is executed, data are transferred as follows:
The number of bytes specified by OP1 are read from the file memory head address specified
by OP2 into the CPU module address specified by OP3.
Reference 1 - 1
■ Reading File Memory (SPW: Specific-Module Byte-Data Reading Instruction)
Executing
Condition V** FUN 306
[ SPW OP1 OP2 → OP3 ]
Mnemonic coded SPR command
If the read-out instruction as the above example is executed, data are transferred as follows:
The number of bytes specified by OP1 are transfered from the CPU module address
specified by OP2 into the file memory destination address specified by OP3.
Reference 1 - 2
Reference 2 Ethernet File Memory Address Map
■ Control signal output and I/O parameter areas (Addresses 0000 to 0FFF) [write only]
bit7 bit0
0000 8 (00 fixed) 1 1:Initialization Request 8: Parameter area writing prohibited(1:Release)
0001 8 7 6 5 4 3 2 1 1-8:Connections 1-8 Active Open Request
0002 8 7 6 5 4 3 2 1 1-8:Connections 1-8 Transmission Request
0003 8 7 6 5 4 3 2 1 1-8:Connections 1-8 Reception Request
0004 (00 fixed) 2 1 1:Error Log Reception Confirmation, 2:ICMP Log Reception Confirmation
0005 (00 fixed)
0006 (00 fixed)
0007 (00 fixed)
0008 (Lower)
0009
Own Node IP Address
000A 00000001 - FFFFFFE
000B (Higher)
000C 8 7 6 5 4 3 2 1 1-8:Connection Used (1:Use)
000D 8 7 6 5 4 3 2 1
1-16:Table Used (1:Use)
000E 16 15 14 13 12 11 10 9
000F (00 fixed)
0010 TCP Active Open: 0000h, TCP Destination-Specified Passive Open: 0100h,
Connection opening method
Connection No.1
Reference 2 - 1
0038 TCP Active Open: 0000h, TCP Destination-Specified Passive Open: 0100h,
Connection opening method
Connection No.6
0039 TCP Destination Non-Specified Passive Open: 0200h, UDP:0001h
003A Own Node Port No. (Lower)
003B 0401h - FFFEh (Higher)
003C Other Node Table No.. (Lower)
003D 0001h - 0010h (Higher)
003E General communication setting 00h or FFh
003F (00 fixed)
0040 TCP Active Open: 0000h, TCP Destination-Specified Passive Open: 0100h,
Connection opening method
Connection No.7
Reference 2 - 2
0070 (Lower)
0071
Other Node IP Address
0072 Table No.5 00000001 - FFFFFFE
0073 (Higher)
0074 Other Node Port No. (Lower)
0075 0401h - FFFEh (Higher)
0076
(00 fixed)
0077
0078 (Lower)
0079
Other Node IP Address
Table No.6
Reference 2 - 3
00A8 (Lower)
00A9
Other Node IP Address
00AA Table No.12 00000001 - FFFFFFE
00AB (Higher)
00AC Other Node Port No. (Lower)
00AD 0401h - FFFEh (Higher)
00AE
(00 fixed)
00AF
00B0 (Lower)
00B1
Other Node IP Address
Table No.13
Reference 2 - 4
00E0 (Lower)
Response Timer
00E1 (Higher)
00E2 (Lower)
Non-Reception Timer
00E3 (Higher)
00E4 (Lower)
Resending Timer (Data)
00E5 (Higher)
00E6 (Lower)
Re-transmitted Data (SYN/FIN)
00E7 (Higher)
00E8 (Lower)
Close Timer
00E9 (Higher)
00EA (Lower)
Packet alive Time
00EB (Higher)
00EC (Lower)
IP Assembly Timer
00ED (Higher)
00EE (Lower)
Reset wait resending times
00EF (Higher)
00F0
00F1
00F2
00F3
00F4
00F5
00F6
00F7
(00 fixed)
00F8
00F9
00FA
00FB
00FC
00FD
00FE
00FF
Reference 2 - 5
■ Control signal input and connection error areas (Addresses 0100 to 013F) [read only]
bit7 bit0
0101 1 1:Initialization Request
0101 8 7 6 5 4 3 2 1 1-8:Connections 1-8 normally opened
0102 8 7 6 5 4 3 2 1 1-8:Connections 1-8 connection error
0103 8 7 6 5 4 3 2 1 1-8:Connections 1-8 transmission completed
0104
0105 8 7 6 5 4 3 2 1 1-8: Connections 1-8 reception completed
0106 4 3 2 1 1: Error log received 2: ICMP log received 3: PING OK 4: PING NG
0107 Reserve
0108 (Lower) Each Ethernet device has an unique Ethernet address.
0109
010A
010B Own Ethernet Address
010C
010D (Higher)
0120 Connection error codes can also be monitored with special registers
Connection No.1 Connection error code
0121 of CPU module.
0122 See 2-2-6 'Status Monitor Function.'
0123
0124
Connection No.2 Connection error code
0125
0126
0127
0128
Connection No.3 Connection error code
0129
012A
012B
012C
Connection No.4 Connection error code
012D
012E
012F
0130
Connection No.5 Connection error code
0131
0132
0133
0134
Connection No.6 Connection error code
0135
0136
0137
0138
Connection No.7 Connection error code
0139
013A
013B
013C
Connection No.8 Connection error code
013D
013E
013F
Reference 2 - 6
■ File Memory Transmission/Reception Data Areas (Addresses 1000 to 8FFD)
bit7 bit0
1000 LL (Lower Transfer Number)
Connection No.1
Transmission
1802
Reception data
(up to 2044 bytes)
1FFD
2802
Reception data
(up to 2044 bytes)
2FFD
3802
Reception data
(up to 2044 bytes)
3FFD
4802
Reception data
(up to 2044 bytes)
4FFD
Reference 2 - 7
5000 LL (Lower Transfer Number)
Connection No.5
5001 Transmission LH (Higher Transfer Number)
5002
Transmission data
(up to 2044 bytes)
57FD
5802
Reception data
(up to 2044 bytes)
5FFD
6802
Reception data
(up to 2044 bytes)
6FFD
7802
Reception data
(up to 2044 bytes)
7FFD
8802
Reception data
(up to 2044 bytes)
8FFD
Reference 2 - 8
Reference 3 Transfer of Ethernet Control Output/Input Signals to
Keep Relays
Addresses 0000-0004h of File Memory are for control-output signals toward 2PORT-EFR
Module and 0100-0106h are for control-input signals from 2PORT-EFR Module.
It is recommendable to allocate these fields to keeper relays so as to facilitate a sequence
program creation.
The following sequence program turns on/off keeper relays (K**) in order to turn set/reset each
control-output signal and to relate a control-input signal with the status of a keeper-relay contact
point.
Ensure to clear keeper relays by the first scan after Power ON, because they won't be reset
through a CPU-Module reset or Power ON/OFF.
Reference 3 - 1
This sequence program assigns control I/O signals as follows:
Reference 3 - 2
Reference 4 Ethernet Initial Sequence Program Sample
In the following example, the sequence program is used to set I/O parameters.
Condition of setting
・ 2PORT-EFR Module link No. is 3.
・ Your own node IP address is 192.168.1.1 (C0.A8.01.01)h
・ Your own node port No. is 4096 (1000h)
・ The file memory 0th operand corresponds with data register D0000.
・ Data registers D100-D105 are used for writing file memory.
IP address:
2PORT-
PC2J /
PC3J
192. 168. 1. 1
EFR
Link No.3
V006
[ FIL1 00 → D0000L → D0009H ] Data clear
Reference 4 - 1
Reference 5 Ethernet IP Address, Gateway IP Address and Subnet Mask
IP Address is notated in 4 bytes to determine up to what bytes from the highest byte of the
4 are considered as network ID based on the higher 1 to 3 bits of the first byte.
In case the Network ID of destination differs from IP Address Network ID specified by your own
node IP address, a command is sent toward the gateway located at the address configured by
Gateway IP Address. (Even in this case, Destination IP is kept intact at the original IP and the
Gateway's Ethernet Address is used.)
Example)
Host 1 Host 2
IP Address 80. 01. 01. 01 IP Address 80. 01. 01. 02
Network ID 80. 01
Network ID 80. 11
Host 3
IP Address 80. 11. 01. 02
(Note: Each IP address is expressed by hexadecimal notation)
In case any transmission command from host 1 to host 3 is issued; as network ID differs, Ethernet
Module transmits it toward Gateway 1.
Gateway 1 sends data to the host 3.
Reference 5 - 1
Subnet mask considers the certain higher bits of host ID as a part of network ID, and conduct
configuration if data conveyance is required via gateway.
In the following figure, if the subnet mask is set as FF.FF.FF.00 (255.255.255.0), host 1 considers
that host 3 is on the different network from one of host 1 for data to be transferred via gateway 1.
Example)
Host 2 Host 23
IP Address 81. 00. 01. 02 IP Address 81. 00. 41. 03
Limit the altering points of bit data of the subnet mask to one point only.
(Example) 1111 1111 . 1111 1111 . 1111 1111 . 0000 0000 (FF.FF.FF.00)h
For instance, if class B IP address and this subnet mask are combined, each bit of IP address
represents the following three ID sections:
IP address where all bits of each ID section are 0 or 1 evenly is not configureable.
For example, if IP address is 81.00.FF.01 (129.0.256.1) and subnet mask is FF.FF.FF.00
(255.255.255.0); since all subnet ID sections are 1, so they cannot be configured.
If subnet mask and gateway IP address are set as 00.00.00.00, they are assumed to be undefined.
In this case, all components are considered as Network ID unit and Host ID only.
Reference 5 - 2
Reference 6 Re-opening on Ethernet Function
With this function, the personal computer if accidentally shut down or rest can re-open a
connection after a retry.
* Because the error is released at once as for connection error 4014 when the data interval from
A to B is short, abnormality might not be able to be confirmed.
Reference 6 - 1
Reference 7 Conducting PING Test via Windows-Installed PC
The PING test is to check that the line is correctly connected and the IP address and other
parameters correctly specified to enable the communication.
■ Test method
(1) Click the start button [Start], and click [Program] then [MS-DOS prompt].
Reference 7 - 1
Reference 8 If an 2PORT-EFR module that has replaced an older one
does not communicate with a personal computer:
If an 2PORT-EFR module communicating with a personal computer is replaced with a new one,
the new one may not communicate with the PC for a while.
This is because the Ethernet communication requires an unique Ethernet address (also called
MAC address) as well as an IP address and port No. and the personal computer stores an ARP
table showing the correspondence between Ethernet addresses and IP addresses. If an
2PORT-EFR module is replaced with another one with the same IP address but a different
Ethernet address stored in the hardware, communication cannot be started as far as previous
settings remain in the ARP table.
After communication is suspended for a few minutes, the ARP table is usually cleared to permit
the restart of communication. The table may also be cleared with the following procedure.
(1) Click the Start button [Start] on the personal computer. Select 'Programs' and 'MS-DOS
Prompt.'
(2) Enter 'arp-d' and the IP address of the 2PORT-EFR module after C:¥WINDOWS>.
Press the Enter key.
(Example) If the IP address of the 2PORT-EFR module is 192.168.1.1, for example:
C:¥WINDOWS>arp -d 192.168.1.1
Then, it becomes possible to restart the communication. The ARP table may also be cleared
when the personal computer is shut down or restarted.
Reference 8 - 1
Reference 9 Limitations on number of modules implemented due to power
module
Please be careful that the combined consumption current of individual modules does not exceed the
maximum output current of the power module.
The maximum output current of each power source module is as follows.
If POWER1 and PC10G (consumption current = 1A) is implemented, a maximum of two can be
implemented on 2PORT-EFR.
POWER 1 PC10G-CPU 2P O R T ‐
E FR 2P O R T ‐
E FR 2P O R T ‐
E FR
POWER RUN E/A TXD RXD TXD RXD TXD RXD
W
P2 P3
1 3 5 7 1 3 5 7 1 3 5 7
L1 L2
L3 2 4 6 8 STATUS 2 4 6 8 STATUS 2 4 6 8 STATUS
INPUT AC85~264V
CPU/SEL. CPU/SEL.
POWER BATTERY POWER
1st./
MODE 0 RACK
NO.
0
1 RACK
NO.
2
1 RACK
NO.
2nd./ 8~E 8~E 8~E
FL L1 L1 L1
L1 ET STATUS LED STATUS LED STATUS LED
RMT L2 L2 L2
FL
L2 ET
RMT L1 L1 L1
L1 Auto 10M
L2 Auto 10M
L1 SEL. DM
L3 T-ON T-OFF
*.** L2 L2 L2
START
RESET
L1 L3
TERM.
L3
0V
L-
L2
L+
If POWER2H and PC10G (consumption current = 1A) is implemented, a maximum of three can be
implemented on 2PORT-EFR.
current (1A) current (1.1A) current (1.1A) current (1.1A) current (1.1A)
POWER2H
Reference 9-1
It is possible to use it up to seven (rack no. 8 to E) by making the load to each power source module
below the maximum output current by using the increase base to increase the number of sheets of the
module. (The number of 2PORT-EFR that can be mounted on the increase base is four or less in
POWER2H in POWER1 for three or less.)
FL L1 L1
L1 ET STATUS LED STATUS LED
RMT L2 L2
FL
L2 ET
RMT L1 L1
L1 Auto 10M
L2 Auto 10M
L1 SEL. DM
L3 T-ON T-OFF
*.** L2 L2
START
RESET
L1 L3
TERM.
L3
0V
L-
L2
L+
1 3 5 7 1 3 5 7 1 3 5 7
SW1 SW2
NO.
8~E
SW1 SW2
NO.
8~E
SW1
L1 L1 L1
STATUS LED STATUS LED STATUS LED
L2 L2 L2
L1 L1 L1
L2 L2 L2
TERM.
Total 3.3A
The next page shows consumption currents (Typ.) for various modules as reference.
Reference 9-2
Consumption current of individual modules (Typ.)
Module name Consumption current (mA) Module name Consumption current (mA)
SELECTOR 31 SIO 310
IN-11,12 60*1 260(5VDC)
DLNK-M2
1N-22D 63*1 40(24VDC)
IN-32F 77*1 180(5VDC)
DLNK-S2
IN-22H 100*1 60(24VDC)
IN-SW 126*1 PC1-I/O-I/F 200
OUT-1,4 174*1 MPLX-TR-I/F 700
OUT-3 356*1 AD 140
OUT-11 336*1 DA 670
OUT-12 380*1 COUNTER 300
OUT-15,16 310*1 PULSE OUT 250
OUT-18,19 136*1 SUB-CPU 380
OUT-28D,29D 210*1 B7A-I/F 100
I/O-329G 330*1 S-LINK 100
FL/ET-T-V2H 600 2PORT-EFR 1100(5VDC)
PC/CMP-LINK CT10 200
170
PC/CMP2-LINK EF10 1100(5VDC)
RMT-I/O M AD10 300
210
RMT-I/O S ML10 150
HPC-LINK 250 SC10 240
ME-NET 600 TOYOPUC-MCML 150(5VDC)
2PORT-LINK 330 Program name Consumption current(mA)
2PORT-M-NET 150 HP3 200*2
EN-I/F 600 I/O monitor 300*2
*1 Input and output modules consumption current is the (Typ.) value when all points are on.
*2 If peripheral devices which have power supplied from the PC unit such as HP3 and the like are used,
please include their consumption current in calculations.
Reference 9 - 3
Reference 10 Andon controller link parameter settings
When multiple connections are open on TCP passive, if a [Connection Resend Over] (error code 4013)
occurs on multiple ports simultaneously due to cable disconnections, etc, there may be cases where
connection cannot be established if the other node requests an open.
If this problem occurs frequently, activate the no-receipt timer, and adjust the timer setting value to
prevent a connection resend over error from occurring.
When connecting the Mitsubishi Electric Andon controller (EPC010, EPC020) and 2PORT-EFR, please
set each of the timer values for the link parameter as shown below.
Click
Change the sections circled in red. Default settings used for everywhere other than these four places.
Reference 10-1
Reference 11 Ex number
In PC10 mode, the overall data area is expressed as [8 digits (HEX) byte address].
There are cases where [8 digit byte address] and [Ex number] use [Index function] and [Flash
register].
E.g.
P1-D0000 000D2000
EB01234 00102468h
EM0L 00010C00h
Reference 11-1
Reference) Address table
Ex No.
Name Address Byte address
(HEX)
Edge P000 - P1FF 0000 - 003F
Keep relay K000 - K2FF 0040 - 009F
Special relay V000 - V0FF 00A0 - 00BF
Timer/counter TC000 - TC1FF 00C0 - 00FF
P1PC3JG Link relay L000 - L7FF 0100 - 01FF
compatible Input/output XY000 - XY7FF 0200 - 02FF
※2 Internal relay M000 - M7FF 0300 - 03FF
Special register S0000 - S03FF 0400 - 0BFF
Current value register N0000 - N01FF 0C00 - 0FFF
Link register 0D R0000 - R07FF 1000 - 1FFF
Data register 1 D0000 - D0FFF 2000 - 3FFF
Data register 2 D1000 - D2FFF 4000 - 7FFF
Edge P1000 - P17FF C000 - C0FF
P1 Special relay V1000 - V17FF C100 - C1FF
Timer/counter TC1000 - TC17FF C200 - C2FF
PC10 Internal relay M1000 - M17FF C300 - C3FF
extension Link relay L1000 - L2FFF C400 - C7FF
Special register S1000 - S13FF C800 - CFFF
Current value register N1000 - N17FF D000 - DFFF
Edge P000 - P1FF 0000 - 003F
Keep relay K000 - K2FF 0040 - 009F
Special relay V000 - V0FF 00A0 - 00BF
P2 Timer/counter TC000 - TC1FF 00C0 - 00FF
Link relay L000 - L7FF 0100 - 01FF
PC3JG
compatible Input/output XY000 - XY7FF 0200 - 02FF
Internal relay M000 - M7FF 0300 - 03FF
※2 Special register S0000 - S03FF 0400 - 0BFF
Current value register N0000 - N01FF 0C00 - 0FFF
Basic
Link register 0E R0000 - R07FF 1000 - 1FFF
area 2
Data register 1 D0000 - D0FFF 2000 - 3FFF
Data register 2 D1000 - D2FFF 4000 - 7FFF
Edge P1000 - P17FF C000 - C0FF
P2 Special relay V1000 - V17FF C100 - C1FF
Timer/counter TC1000 - TC17FF C200 - C2FF
PC10 Internal relay M1000 - M17FF C300 - C3FF
extension Link relay L1000 - L2FFF C400 - C7FF
Special register S1000 - S13FF C800 - CFFF
Current value register N1000 - N17FF D000 - DFFF
Edge P000 - P1FF 0000 - 003F
Keep relay K000 - K2FF 0040 - 009F
Special relay V000 - V0FF 00A0 - 00BF
P3 Timer/counter TC000 - TC1FF 00C0 - 00FF
Link relay L000 - L7FF 0100 - 01FF
PC3JG
compatible Input/output XY000 - XY7FF 0200 - 02FF
Internal relay M000 - M7FF 0300 - 03FF
※2 Special register S0000 - S03FF 0400 - 0BFF
Current value register N0000 - N01FF 0C00 - 0FFF
Link register 0F R0000 - R07FF 1000 - 1FFF
Data register 1 D0000 - D0FFF 2000 - 3FFF
Data register 2 D1000 - D2FFF 4000 - 7FFF
Edge P1000 - P17FF C000 - C0FF
P3 Special relay V1000 - V17FF C100 - C1FF
Timer/counter TC1000 - TC17FF C200 - C2FF
PC10 Internal relay M1000 - M17FF C300 - C3FF
extension Link relay L1000 - L2FFF C400 - C7FF
Special register S1000 - S13FF C800 - CFFF
Current value register N1000 - N17FF D000 - DFFF
Reference 11-2
Ex No.
Name Address Byte address
(HEX)
Extension edge EP000 - EPFFF 0000 - 01FF
Extension keep relay EK000 - EKFFF 0200 - 03FF
Extension special relay EV000 - EVFFF 0400 - 05FF
Extension timer/counter ETC000 - ETC7FF 0600 - 06FF
Extension PC3JG Extension link relay EL0000 - EL1FFF 0700 - 0AFF
01
area 1 compatible Extension input/output EXY000 - EXY7FF 0B00 - 0BFF
Extension internal relay EM0000 - EM1FFF 0C00 - 0FFF
Extension special register ES0000 - ES07FF 1000 - 1FFF
Extension current value register EN0000 - EN07FF 2000 - 2FFF
Extension setting value register H0000 - H07FF 3000 - 3FFF
Extension PC3JG Extension input/output GXY0000 - GXYFFFF C000 - DFFF
02
area 2 compatible Extension internal relay GM0000 - GMFFFF E000 - FFFF
PC3JG
03 U00000 - U07FFF 0000 - FFFF
compatible
Extension
Extension data register 04 U08000 - U0FFFF 0000 - FFFF
area 3 PC10
extension 05 U10000 - U17FFF 0000 - FFFF
06 U18000 - U1FFFF 0000 - FFFF
10 EB00000 - EB07FFF 0000 - FFFF
PC3JG 11 EB08000 - EB0FFFF 0000 - FFFF
compatible 12 EB10000 - EB17FFF 0000 - FFFF
Extension 13 EB18000 - EB1FFFF 0000 - FFFF
Extension buffer register
area 4 14 EB20000 - EB27FFF 0000 - FFFF
15 EB28000 - EB2FFFF 0000 - FFFF
PC10Extension
16 EB30000 - EB37FFF 0000 - FFFF
17 EB38000 - EB3FFFF 0000 - FFFF
Reference 11-3
Ex No.
Name Address Byte address
(HEX)
40 FR000000 - FR007FFF 0000 - FFFF
41 FR008000 - FR00FFFF 0000 - FFFF
42 FR010000 - FR017FFF 0000 - FFFF
43 FR018000 - FR01FFFF 0000 - FFFF
44 FR020000 - FR027FFF 0000 - FFFF
45 FR028000 - FR02FFFF 0000 - FFFF
46 FR030000 - FR037FFF 0000 - FFFF
47 FR038000 - FR03FFFF 0000 - FFFF
48 FR040000 - FR047FFF 0000 - FFFF
49 FR048000 - FR04FFFF 0000 - FFFF
4A FR050000 - FR057FFF 0000 - FFFF
4B FR058000 - FR05FFFF 0000 - FFFF
4C FR060000 - FR067FFF 0000 - FFFF
4D FR068000 - FR06FFFF 0000 - FFFF
4E FR070000 - FR077FFF 0000 - FFFF
4F FR078000 - FR07FFFF 0000 - FFFF
50 FR080000 - FR087FFF 0000 - FFFF
51 FR088000 - FR08FFFF 0000 - FFFF
52 FR090000 - FR097FFF 0000 - FFFF
53 FR098000 - FR09FFFF 0000 - FFFF
54 FR0A0000 - FR0A7FFF 0000 - FFFF
55 FR0A8000 - FR0AFFFF 0000 - FFFF
56 FR0B0000 - FR0B7FFF 0000 - FFFF
57 FR0B8000 - FR0BFFFF 0000 - FFFF
58 FR0C0000 - FR0C7FFF 0000 - FFFF
59 FR0C8000 - FR0CFFFF 0000 - FFFF
5A FR0D0000 - FR0D7FFF 0000 - FFFF
5B FR0D8000 - FR0DFFFF 0000 - FFFF
5C FR0E0000 - FR0E7FFF 0000 - FFFF
5D FR0E8000 - FR0EFFFF 0000 - FFFF
5E FR0F0000 - FR0F7FFF 0000 - FFFF
Extension PC10 5F FR0F8000 - FR0FFFFF 0000 - FFFF
Flash register
area 5 extension 60 FR100000 - FR107FFF 0000 - FFFF
61 FR108000 - FR10FFFF 0000 - FFFF
62 FR110000 - FR117FFF 0000 - FFFF
63 FR118000 - FR11FFFF 0000 - FFFF
64 FR120000 - FR127FFF 0000 - FFFF
65 FR128000 - FR12FFFF 0000 - FFFF
66 FR130000 - FR137FFF 0000 - FFFF
67 FR138000 - FR13FFFF 0000 - FFFF
68 FR140000 - FR147FFF 0000 - FFFF
69 FR148000 - FR14FFFF 0000 - FFFF
6A FR150000 - FR157FFF 0000 - FFFF
6B FR158000 - FR15FFFF 0000 - FFFF
6C FR160000 - FR167FFF 0000 - FFFF
6D FR168000 - FR16FFFF 0000 - FFFF
6E FR170000 - FR177FFF 0000 - FFFF
6F FR178000 - FR17FFFF 0000 - FFFF
70 FR180000 - FR187FFF 0000 - FFFF
71 FR188000 - FR18FFFF 0000 - FFFF
72 FR190000 - FR197FFF 0000 - FFFF
73 FR198000 - FR19FFFF 0000 - FFFF
74 FR1A0000 - FR1A7FFF 0000 - FFFF
75 FR1A8000 - FR1AFFFF 0000 - FFFF
76 FR1B0000 - FR1B7FFF 0000 - FFFF
77 FR1B8000 - FR1BFFFF 0000 - FFFF
78 FR1C0000 - FR1C7FFF 0000 - FFFF
79 FR1C8000 - FR1CFFFF 0000 - FFFF
7A FR1D0000 - FR1D7FFF 0000 - FFFF
7B FR1D8000 - FR1DFFFF 0000 - FFFF
7C FR1E0000 - FR1E7FFF 0000 - FFFF
7D FR1E8000 - FR1EFFFF 0000 - FFFF
7E FR1F0000 - FR1F7FFF 0000 - FFFF
7F FR1F8000 - FR1FFFFF 0000 - FFFF
Reference 11-4
Reference 12 Link memory capacity
The total link memory capacity of all link modules mounted on a single CPU module
should be 60 kbytes or less. The link memory capacity should be as small as possible
to reserve a necessary data link capacity.
The 16-kbyte and 32-kbyte modes of the FL-net are available with CPU modules of the
following versions.
If the link memory capacity is set to 16 or 32 kbytes for a CPU module of another
version, the module does not normally operate.
Reference12 -1
Link memory capacities of different modules
FL-net 8K 8K bytes
FL/ET-T-V2H
2PORT-EFR FL-net 16K 16K bytes
FL-net 32K 32K bytes
FL/ET-T-V2H Ethernet 4K bytes
2PORT-EFR
EF10
2PORT-EFR FLRemote-M 4K bytes
PC/CMP-LINK 4K bytes
2PORT-LINK 8K bytes
2PORT M-NET 4K bytes
HPC-LINK 4K bytes
SIO 4K bytes
Memory Card I/F 4K bytes
EN-I/F 4K bytes
SUB-CPU 4K bytes
RMT-I/O M 4K bytes
DLNK-M 4K bytes
DLNK-M2 4K bytes
DLNK-S2 4K bytes
PROFI-S2 4K bytes
ID I/F 4K bytes
MPLX-TR-I/F 4K bytes
PC1-I/O-I/F 4K bytes
AF1K-C 4K bytes
MC1K-C 4K bytes
ME-NET 8K bytes
PULSE OUTPUT 8K bytes
Reference12 -2
Note:
・ For PC2J or PC3J series CPUs, it is not necessary to add the internal or optional link
memory capacity except for the DLNK-M contained in the PC3JD etc., which
consumes 4 kbytes' link memory space. However, when CPU module is PC10 series,
the link memory capacity is not limited.
Example 1
8K 4K 4K 8K 4K 4K ←Link memory capacity
2PORT-LINK
PC3JL-CPU
FL-net(8K)
CMP LINK
HPC-LINK
HPC-LINK
POWER1
PC-LINK
OUT-18
OUT-18
FL-net(8K)
POWER1
Ethernet
net
Example 2
4K 8K 4K 4K ←Link memory capacity
2PORT-LINK
HPC-LINKI
HPC-LINK
POWER1
OUT-18
OUT-18
PC3JD-CPU
IN-12
IN-12
FL-net(8K)
POWER1
FL‐net
Ethernet
Reference12 -3
• This document is subject to modification without notice.
• Your comments or advice concerning ambiguous descriptions,
errors and/or omissions would be much appreciated.
• Unauthorized duplication of any information contained in this
document is prohibited.
Manual No.
T-75610E
©
JTEKT CORPORATION 2007-2019
* Specification in this manual are subject to change without notice.
* Products herein may be strategic commodities under the Foreign Exchange and
Foreign Trade Control Law of Japan.
An approval under the law may be required exportation of the products.