APPLICATION MANUAL for NETWORK

Transcription

1 HITACHI PROGRAMMABLE CONTROLLER APPLICATION MANUAL for NETWORK NJI-491A(X)

2 Revision History No. Description of Revision Date of Revision Manual number 1 The first edition Add explanation for EHV-CPU64 / 32 / Add explanation for Communication function. Revised chapter: Chapter NJI-491A(X)

3 Table of Contents Chapter 1 Network Configuration 1-1 to Communication port for CPU module Network configuration for Communication module Chapter to Features Ethernet communication port Task code communication port ASR communication port Reset function for Ethernet communication port NTP client function Factory setting Serial communication port Pin arrangement Dedicated port General-purpose port Modem connection function Connection between Serial communication port and Peripheral device Connection method for RS-422 / 485 communication USB communication port Appendix 1 Cable Connection Diagram A-1

4 MEMO

5 Chapter 1 Network Configuration EHV-CPU can configure various network systems depending on a combination of the communication port for CPU module and the communication module. Host Ethernet IEEE802.3 EH-150 EH-150 H series EH-150 FL-net PLC by other maker CPU link (Coaxial/Optical fiber) Positioning system DeviceNet ProfiBus Figure 1.1 Network configuration for EHV-CPU 1 1

6 Chapter 1 Network Configuration 1.1 Communication port for CPU module EHV-CPU is equipped with USB communication port, Serial communication port, and Ethernet communication port. The personal computer can be connected to every port, and you can create programs and monitor the system by using Control Editor which is a programming software. USB communication port It is a maintenance port for programming software. Programming software can be used, connecting a notebook which is not equipped with a RS-232C serial port. Serial communication port USB communication port Serial communication port Ethernet communication port RS-232C/422/485 can be switched like CPU currently in use. Supports a dedicated procedure and a general-purpose communication. Ethernet communication port It has functions equivalent to the Ethernet communication module (4 dedicated procedure connections and 6 message communications). Support to network can be realized by the CPU module by oneself. Figure 1.2 Communication ports for EHV-CPU! Caution Please pay attention the following points on the communication port. (1) If the Ethernet communication cable is connected to the serial communication port, the Ethernet communication port of the CPU module and external equipments connected to the Ethernet communication port may be damaged. (2) A link with a network HUB etc. may not be established on the high speed communication by 100BASE-TX connection (100Mbps) or the link may be easy to cut because communication error occurs under the influence of installation environment, cable length, and noise. In these cases, please construct the network system with the following solutions. (a) Increases the number of times to retry if necessary, using the TCP/IP communication for the protocol to communicate to other unit. (b) Change the Ethernet communication speed to 10Mbps. (3) If the programming tool and the USB communication port are used for connection, the programming tool may generate communication error under noise environment. If communication error is generated under noise environment, the serial port or the LAN port should be used for connection. And do not bring a communication cable close to other wiring and do not put the communication cable and the wiring into the same duct for the stable communication. Reference Since the Ethernet communication speed can be changed in Ver.x107 or newer, 5 types of communication speed (Auto-negotiation, 100M full-duplex/half-duplex, 10M full/duplex/half-duplex) can be set. The communication speed is set to 10M half-duplex at the shipment. (As for x in Ver.x107, it represents EHV-CPU128 when x is 0, it represents EHV-CPU64 when x is 1, it represents EHV-CPU32 when x is 2, and it represents EHV-CPU16 when x is 3. This version information is stored in the special internal output WRF050.) Control Editor (Ver.2.00 or newer) or IP address setting tool can change the communication speed. 1 2

7 Chapter 1 Network Configuration (1) Dedicated procedure communication (Task code communication) A dedicated procedure communication of Hitachi PLC is called a task code communication. CPU can be controlled from the host and I/O can be read and written. Each sales maker provides a driver for this task code communication such as a touch panel and HMI (Human Machine Interface) software. For compatible Hitachi PLCs, it is unnecessary to create a special program. Host Ethernet task code communication Serial task code communication Ethernet Touch pannel Serial communication HMI software EH-150 Application Hitachi PLC Communication driver Request task code Data memory Task code Response task code Figure 1.3 Task code communication (2) No procedure communication Serial communication port General-purpose communication Serial communication port can be used as a general-purpose port which can be controlled by a user program. Various setting for communication and processing for transmitting and receiving can be created with the user program, matching to external equipments. User program TRNS0 General-purpose communication d RECV0 Serial port External equipments Figure 1.4 General-purpose communication for Serial communication port 1 3

8 Chapter 1 Network Configuration Ethernet communication port ASR communication ASR communication function can be used for the event transmitting function which transmits data from the CPU to the host actively at the event occurrence, the cycle transmission which transmits data to the host at constant interval, and when receiving message data from the host at any timing. There are 6 connections and the communication method can be specified respectively. Communication with the host is possible by only minimum setting. [Optional procedure communication] TCP/IP application Ethernet [Active Open] Active Open Connection establish Passive Open Waiting for connection open Connection establish [Transmitting Broadcast] [Passive Open] Passive Open Connection establish Waiting for connection open [Cycle transmitting] Active Open Connection establish Ethernet Ethernet Figure 1.5 ASR communication for Ethernet communication port Serial communication port Modem connection function Serial communication port supports the modem connection function (only in setting RS-232C). If it is set so that the modem connection function can be used, necessary initial setting is performed to the modem automatically in connecting with the modem. If receiving from the modem is detected as an access from the host via commercial line, it becomes the status waiting for receiving task code. PC EHV-CPU Modem Commercial line Modem RS-232C (MAX 57.6 kbps) Figure 1.6 Modem connection function 1 4

9 Chapter 1 Network Configuration 1.2 Network configuration for Communication module An example of a network configuration using the communication module is shown below. Refer to each instruction for detailed specification of each module. (1) Ethernet module (EH-ETH) If industrial equipments are connected to the information system network, it is useful for performing production control, system operation monitor, facilities monitor, and maintenance smoothly. 1.EH-ETH is mounted in a basic base of EH-150 system and is a communication interface module to connect the EH-150 system to Ethernet conformed to IEEE EH-ETH connected to Ethernet functions as one station in the network. And data can be exchanged between a personal computer and a server on the network. PC Server Ethernet EHV system Figure 1.7 Example of Network configuration using Ethernet module (a) 10 connections for transmitting and receiving of data can be used. - There are 6 ASR connections for message communication and 4 connections for task code communication. - Data can be transmitted and received by only one connection. - One of TCP/IP and UDP/IP is selectable as a communication protocol which is used for each connection. - Data up to 1454 bytes can be transmitted and received between PLC or the host. (b) Simplifying a ladder program by Web server function for communication setting and ASR function. - Various settings for starting communication are performed using a general-purpose Web browser. Setting information is stored on a built-in FLASH memory in EH-ETH as a file named setup.dat. This file is a text file format. - Man-hour to create a ladder program can be reduced drastically by using ASR function. (c) Programming is possible from Control Editor. - Programming and I/O monitor via Ethernet of EH-ETH are possible by using the Control Editor. Maintenances of the program and the whole system improve by remote operation and monitor between PLC connected by Ethernet. 1 5

10 Chapter 1 Network Configuration (2) DeviceNet TM Mater module (EH-RMD) / Slave controller (EH-IOCD) Since DeviceNet TM master module / Slave controller conform to DeviceNet which is a open filed network, not only our master/slave device but also master/slave device made in other maker can be connected. EH-150 DeviceNet Master device Inverter L100DN/SJ100DN AC servo AD series NX-SDC (Dispersion controller) Device made in other maker EH-150 DeviceNet Slave controller Dispersion type I/O slave unit Figure 1.8 Example of Network configuration using DeviceNetTM Master module / Slave controller DeviceNet Features Device type Communication adaptor Master/Scanner Yes Explicit peer-to-peer message Yes I/O slave message I/O peer-to-peer message No Bit strobe Yes Configuration consistency value Yes Polling Yes Fault node recovery No Cyclic Yes Communication speed 125/250/500 kbps Change of state (COS) Yes 1. Supports Link mode / Remote mode of EH-RMD. Item Link mode Remote mode Communication protocol Conforms to DeviceNet release 2.0 Support connection Polling, Bit Strobe, Cyclic, COS, Explicit Message Number of installed units 2 units/cpu 4 units/cpu Input and output point 256-word input 256-word output 1,024-point input and output I/O assignment CPU link Remote 2 Configurator Need Need 2. Up to 16 modules can be mounted on EH-IOCD. EH-BS11A is not supported. Please use EH-BS3A/5A/8A. 3. EH-IOCD supports a digital I/O, an analog I/O module and a part of high-functional module. 4. Explicit message can be transmitted and received by a ladder program. 1 6

11 Chapter 1 Network Configuration (3) Serial interface module (EH-SIO) 1. Communication with Serial communication equipments (General-purpose communication) User program performs communication with external equipments. TRNS 9 which is a command for EH-SIO performs EH-SIO control by EHV-CPU and transmitting and receiving of data. Host RS-422 RS-232C Bar code reader Figure 1.9 System configuration at general-purpose communication 2. Communication with Modbus protocol support equipments EH-SIO can communicate by Modbus protocol. Modbus slave equipments can be controlled with communication by setting EH-SIO to a master. And I/O of EHV-CPU can be accessed from the host by Modbus protocol. Up to 32 units Inverter SJ-200 Inverter SJ-200 AC servo ADAX 4 -series RS-485 Figure 1.10 System configuration in controlling equipments supporting Modbus 1 7

12 Chapter 1 Network Configuration 3. Communication with Communication protocol (Hi-Protocol) support equipments for Hitachi H/EH series This can connect with HMI supporting Hi-Protocol. It can connect equipments supporting Hi-Protocol (HMI etc.), setting EH-SIO to Hi-Protocol mode. Figure 1.11 System configuration in connecting HMI 4. Simple data link function Simple data link is a function to exchange I/O information with a slave by communication, setting EH-SIO to a master. PLC which becomes a slave is EH-150* 1 and MICRO-EH* 1. If initial setting of EH-SIO which becomes a master is completed, the I/O area is updated by the system automatically. *1 Models supporting a transmission control procedure 2 (with station No.) are applied. St.No. 18 St.No. 01 St.No. 02 St.No. 31 RS-485 Up to 31 units Figure 1.12 System configuration in simple data link 1 8

13 Chapter 1 Network Configuration (4) CPU link module (Coaxial: EH-LNK, Optical: EH-OLNK) CPU link can be formed by using the CPU link module (coaxial and optical). And the entry into the existing H-series CPU link network is possible. Fig.1.13 shows an example of a system configuration using the CPU link module (coaxial and optical). ST0 EH-150 series ST61 ST1 Link system 2 ST62 ST0 ST63 ST : Station No. ST63 ST1 Link system 1 ST62 ST2 ST0 Link system 3 Large H-series ST0 ST3 Link system 4 Medium H-series ST1 ST1 Figure 1.13 Example of System configuration for CPU link Link data area WL Link data area WL Own station Figure 1.14 Other station Outline of Link data area 1 9

14 MEMO

15 Specification of Communication port for CPU module 2.1 Features EHV-CPU has three communication ports as follows. (1) Ethernet communication port (2) Serial communication port (3) USB communication port USB communication port Serial communication port Ethernet communication port Figure 2.1 Communication port (1) Ethernet communication port EHV-CPU has 4 ports as a task code dedicated port for communicating by the dedicated protocol of H series. Programming and monitoring are possible by connecting the Control Editor. This port can also connect with a monitor available on the market corresponding to the H series dedicated protocol. And since the ASR communication function is supported, transmitting and receiving message data are possible by the simple setting. Message data are transmitted at the event occurrence or periodically, and received automatically. Therefore, the network configuration matching to the system can be constructed. In addition, since the SNTP client function is supported, the time information can be taken from the NTP server and the SNTP server on the network, and the time can be revised automatically. (Refer to NTP client function in this chapter for the SNTP client function.) (2) Serial communication port EHV-CPU supports RS-232C, RS-422, and RS-485 as a communication interface of the serial communication port. And also it supports a dedicated port for communicating by the H series dedicated protocol as the communication port and a general-purpose port which can control communication by a user program. In the dedicated port, programming and monitoring are possible by connecting the Control Editor. This port can also connect with a monitor available on the market corresponding to the H series dedicated protocol. In addition, since the model connecting function is supported (only RS-232C), communication of the programming software via the model can be realized. In the general-purpose port, since communication can be controlled by the user program, communication with external devices with the serial communication port is possible. 2 1

16 (3) USB communication port USB communication port is a dedicated port to connect the Control Editor. Programming and monitoring are possible. Programming software Control Editor Creation of program Monitoring EHV-CPU Fig.2.2 Programming software connection diagram HMI software Application Touch pannel EHV-CPU Figure 2.3 Example of Network configuration using dedicated protocol Reference Since the Ethernet communication speed can be changed in Ver.x107 or newer, 5 types of communication speed (Auto-negotiation, 100M full-duplex/half-duplex, 10M full-duplex/half-duplex) can be set. The communication speed is set to 10M half-duplex at the shipment. (As for x in Ver.x107, it represents EHV-CPU128 when x is 0, it represents EHV-CPU64 when x is 1, it represents EHV-CPU32 when x is 2, and it represents EHV-CPU16 when x is 3. This version information is stored in the special internal output WRF050.) Control Editor (Ver.2.00 or newer) or IP address setting tool can change the Ethernet communication speed. And set the Ethernet communication speed according to the following table. Device to be communicated Table 2.1 Task code communication specifications EHV-CPU Auto-negotiation 100M 10M Full-duplex Half-duplex Full-duplex Half-duplex Auto-negotiation M Full-duplex Half-duplex M Full-duplex Half-duplex

17 2.2 Ethernet communication port Task code communication port Task code communication can achieve the following functions by combining individual communication command on a host program. (1) CPU control (occupy / release, CPU status read, etc.) (2) I/O control (all kinds of monitors) (3) Memory write (all clear, batch transfer, etc.) (4) Memory read (read of program, etc.) (5) Response (all kinds of response from CPU) This function can establish a system using the HMI software (SCADA, etc.) supporting HITACH H/EH series PLC Ethernet communication and a touch panel. HMI software TCP/IP application HMI software EHV-CPU Application Data memory Ethernet EHV-CPU HITACH PLC Communication driver Request task code Task code processing Touch pannel Response task code Figure 2.4 Composition of Task code communication equipment Table 2.1 Specifications for task code communication Item Specifications 1 Command system HITACHI H/EH series PLC Ethernet task code (Server function) 2 Communication TCP/IP, UDP/IP protocol 3 Logical port Up to 4 (A port not to be used can be set up to the Not-Use.) 4 Logical port No. Select any from 1,024 to 65,535 5 Timeout time Invalid or Valid (Time between 1 to 65,535 sec. can be set up optionally.) 2 3

18 2.2.2 ASR communication port ASR communication function can be used when message data is transmitted from this unit to the host actively at the event occurrence, and message data is received from the host at any time. And communication procedures can be established according to the system. [Event transmitting] TCP/IP application [Cyclic transmitting] Ethernet Ethernet Event occurrence!! [Receiving] [Transmitting and receiving] Application TCP/IP application Ethernet Ethernet Figure 2.5 ASR communication port Table 2.2 Communication specifications for ASR communication Item 1 Communication protocol TCP/IP, UDP/IP Specifications 2 Logical port Up to 6 (A port not to be used can be set up to the Invalid.) 3 Maximum length of message UP to 730 words 4 Transmitting area Specifying from WX, WY, and internal output 5 Receiving area Specifying from WY and internal output 6 Transmitting system Event transmitting, Cyclic transmitting 7 Receiving system Auto receiving 2 4

19 Communication type You can specify the following 4 communication types. Table 2.3 Communication type for ASR communication Type Description 1 Not used Not perform the transmitting and receiving 2 Transmitting and receiving Performs the transmitting and receiving to the other station. 3 Only transmitting Performs the transmitting to the other station only. 4 Only receiving Performs the receiving only. Connection type You can specify the following 5 connection types. Table 2.4 Connection type for ASR communication Connection method 1 TCP/IP-Active open 2 TCP/IP-Passive open Specifies for the other station 3 TCP/IP-Passive open Optional for the other station 4 UDP/IP Specified for the other station 5 UDP/IP Optional for the other station TCP/IP-Active open and TCP/IP-Passive open When performing the ASR communication using TCP/IP, the logical transmission path for the connection with an open request should be established between EHV-CPU and the other station in advance. There are two methods to establish connection, the active open and the passive open. Table 2.5 Connection method for ASR communication No Connection method Description 1 Active Open A method to establish connection by transmitting the open request later to the other station waiting for the connection open. Active open Connection established Passive open Waiting for the connection open Connection established 2 Passive Open A method to establish connection by receiving the open request from the other station, waiting for the connection open earlier. Passive open Connection established Waiting for the connection open Active open Connection established 2 5

20 Specified and Optional for the other station Message communication can be achieved with any station if TCP/IP-Active open is specified or UDP/IP-receiving is specified. Transmitting Broadcast When Transmitting and receiving, or Transmitting only is specified using UDP/IP, message data can be exchanged between the logical ports which satisfy the following requirements. (1) Nodes with the same network address (Multiple other stations) (2) Nodes with the same logical port No., which can perform the UDP/IP communication (Multiple other stations) (3) Nodes in status which can receive message (Multiple other stations) This is called Simultaneous transmission or Transmitting Broadcast. Transmitting Broadcast Application Ethernet Figure 2.6 Transmitting Broadcast Transmitting type There are the following 2 transmitting types. Table 2.6 Transmitting type for ASR communication Transmitting type Description 1 Event transmitting When the transmitting trigger bit specified is turned from OFF to ON, data in I/O memory specified as the transmitting area is transmitted To transmit data, the event transmission request flag should be ON for 120ms or longer and OFF for 120ms or more. Event transmitting request flag ON OFF TON TOFF: Trigger bit OFF time (Min) TON: Trigger bit ON time (Min) TOFF, TON 120ms 2 Cyclic transmitting Data in I/O memory specified as the transmitting area is transmitted at the interval (1 65,535 1sec, 1 65, ms) specified with the cyclic transmitting timer in a constant cycle. TOFF 2 6

21 Setup item Items need to be set up depending on the combination of the communication type, the connection type, and the transmitting type. Required items are shown below. is marked to the item which should be set the parameter specifying in the following table for the communication. * The Control Editor is used in setting up. When the port supply is turned on at next, the set information becomes effective. Table 2.7 Setup items for ASR communication Communicatin Items which shoeld be setup Connection type Transmitting type type A B C D E F G H I J K L 1 Transmitting TCP/IP-Active Event transmitting and receiving Cyclic transmitting TCP/IP-Passive Specified Event transmitting Cyclic transmitting TCP/IP-Passive Optional Event transmitting Cyclic transmitting UDP/IP Specified Event transmitting Cyclic transmitting UDP/IP Optional Event transmitting Cyclic transmitting 2 Only TCP/IP active open Event transmitting transmitting Cyclic transmitting TCP/IP-Passice Specified Event transmitting Cyclic transmitting TCP/IP-Passice Optional Event transmitting Cyclic transmitting UDP/IP Specified Event transmitting Cyclic transmitting UDP/IP Optional Event transmitting Cyclic transmitting 3 Only TCP/IP-Active - receiving TCP/IP-Passice Specified - TCP/IP-Passice Optional - UDP/IP Specified - UDP/IP Optional - [A] Master station port No. [B] Other station IP address [C] Other station port No. [D] Transmitting cycle timer [E] Transmitting area I/O type [F] Head I/O address in transmitting area [G] Transmitting area size [H] Receiving area I/O type [I] Head I/O address in receiving area [J] Receiving area size [K] Number of retry times [L] Retry interval 2 7

22 Transmitting area and receiving are information In ASR communication, areas for the I/O memory which store message data to transmit and which store message data received need to be specifies. Both the size which can be transmitted and received are 1 to 730 words. Table 2.8 Transmitting and receiving are information for ASR communication Type 1 Transmitting area information 2 Receiving area information *1: Depends on the I/O assignment. I/O memory area which can be specified EHV-CPU128 EHV-CPU64 / 32 / 16 WX (*1) WY (*1) WEX (*1) WEY (*1) WR 0 to FFFF WL 0 to 3FF 1000 to 13FF 2000 to 23FF 3000 to 33FF 4000 to 43FF 5000 to 53FF 6000 to 63FF 7000 to 73FF WM 0 to 7FFF WN 0 to 1FFFF 0 to 7FFF WY (*1) WEY (*1) WR 0 to FFFF WL 0 to 3FF 1000 to 13FF 2000 to 23FF 3000 to 33FF 4000 to 43FF 5000 to 53FF 6000 to 63FF 7000 to 73FF WM 0 to 7FFF WN 0 to 1FFFF 0 to 7FFF Number of areas which can be specified 10 areas (*2) 1 area *2: The size which can be transmitted is up to 730 words totally regardless the number of setting areas 2 8

23 Number of retry times and Retry interval for Connection open When TCP/IP-active is specified, the number of retry times and the retry interval for the connection open when failing can be specified. When there is no response to the packet including the SYN flag* 1 transmitted from the EHV-CPU, the retry is performed three times. And this process is repeated for the number of retry times. The internal between cycles which consist of three retries is specified as the retry interval. The following is an example in case where the number of retry times is set to 3 and the retry interval is set to 10 seconds. *1: SYN flag is a connection open request flag. EHV-CPU SYN First retry cycle Second retry cycle Third retry cycle SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN 1.5s 3s 6s 10s 1.5s 3s 6s 10s 1.5s 3s 6s 10s 1.5s 3s 6s Fixed by the system (Unchangeable by user) Retry interval Figure 2.7 Connection open retry sequence 2 9

24 Status Register, Control register, Transmitting counter, Receiving counter The status register, the control register, the transmitting counter, and the receiving counter for ASR communication are assigned to the special internal output WRF600 or later. Table 2.9 Special internal output for ASR function No. Name Set condition Reset condition WRF600 ASR port 1 Status register Set by system Clear system or user WRF601 Control register Set by user Clear by user WRF602 Transmitting counter Set by system Clear by user WRF603 Receiving counter Set by system Clear by user WRF604 ASR port 2 Status register Set by system Clear by system or user WRF605 Control register Set by user Clear by user WRF606 Transmitting counter Set by system Clear by user WRF607 Receiving counter Set by system Clear by user WRF608 ASR port 3 Status register Set by system Clear by system or user WRF609 Control register Set by user Clear by user WRF60A Transmitting counter Set by system Clear by user WRF60B Receiving counter Set by system Clear by user WRF60C ASR port 4 Status register Set by system Clear by system or user WRF60D Control register Set by user Clear by user WRF60E Transmitting counter Set by system Clear by user WRF60F Receiving counter Set by system Clear by user WRF610 ASR port 5 Status register Set by system Clear by system or user WRF611 Control register Set by user Clear by user WRF612 Transmitting counter Set by system Clear by user WRF613 Receiving counter Set by system Clear by user WRF614 ASR port 6 Status register Set by system Clear by system or user WRF615 Control register Set by user Clear by user WRF616 Transmitting counter Set by system Clear by user WRF617 Receiving counter Set by system Clear by user 2 10

25 Details of the status register, the control register, the transmitting counter, and the receiving counter are described below. b15 b8 b7 b0 Status register [5] [4] [3] [2] [1] +00 Control register [B] [A] +01 Transmitting counter +02 Receiving counter +03 Figure 2.8 Status register, Control register, Transmitting counter, and Receiving counter [ Status register ] [1] ASR port status flag 1: Under open, 0: Under close [2] Event transmitting completion flag 1: Transmitting completion [3] Receiving completion flag 1: Receiving completion [4] Error flag 1: Error occurrence [5] Error code 0x01: Event transmitting request flag [B] is turned ON while ASR port status flag [A] is closed. 0x02: Event transmitting request flag is turned ON again in status which the transmitting of message is not completed. [ Control register ] [A] ASR port open request flag 1: Open request, 0: Close request [B] Event transmitting request flag 1: Transmitting start [ Transmitting counter ] Stores the number of transmitting of message data. [ Receiving counter ] Stores the number of receiving of message data. 2 11

26 (1) ASR port status flag [1] and ASR port open request flag [A] [TCP/IP Active] If user turns on the ASR port open request flag [A], the system will open the connection with the communication other stations. If the other station is waiting for the connection open, the connection will be open normally and the ASR port status flag [1] will turn ON and it will be indicated that the connection is opening. If the other station is not waiting for the connection open and is not found, the connection will not be open normally and the ASR port status flag [1] is still OFF and it will be indicated that the connection is closing. If user turns off the ASR port open request flag [A] while the connection is opened, the connection will be closed and the connection status request flag [A] will turn OFF. And if the other station closes the connection, user must turn off the ASR port open request flag [A] because it does not turn OFF. Opens the connection. Closes the connection. Failure of the connection open [A] [1] Connection is opened at the rising of the open request. The other station closes the connection. Connection is closed at the falling of the open request. Continues closing. the : Operation by user : Operation by system Figure 2.9 TCP/IP Active open for ASR port status flag and ASR port open request flag [TCP/IP Passive] If user turns on the ASR port open request flag [A], the connection open will become the waiting status. In this case, if the other station transmits the connection open request, the connection with the other station will be opened and the ASR port status flag [1] will turn ON and it is indicated that the connection is opening. The connection open does not become the waiting status when the ASR port open request flag [A] is OFF. In this case, if the other station transmits the connection open request, the connection with the other station will not be opened. Makes the connection open the waiting status. Closes the connection. Makes the connection open the waiting status. [A] [1] Connection is open by the open request from the other station. Connection is closed at the falling of the open request. The other station closes the connection. : Operation by user : Operation by system Figure 2.10 TCP/IP Passive open for ASR port status flag and ASR port open request flag 2 12

27 (*) In case where the connection is not closed normally. When the connection is not closed normally for reasons that the cable came off, etc., the process mentioned above is not performed. When the set of the transmitting and receiving is specified to Transmitting or Transmitting and receiving, it is detected by the transmitting timeout that the connection is not opened normally and the ASR port status flag [1] is turned ON. Opens the connection. [A] [1] Connection is opened at the rising of the open request. Cable came off. Connection close is detected by the transmitting timeout. : Operation by user : Operation by system : Event Figure 2.11 TCP/IP Transmitting and Transmitting and receiving side for ASR port status flag and ASR port open request flag When the set of transmitting and receiving is specified to Receiving, it is not detected that the connection is closed because of waiting for message data from the other station. When the connection open request is transmitted from the other station again, it is detected that the connection is closed and the ASR port status flag [1] is turned OFF. Makes the connection open the waiting status. Closes connection. the [A] [1] Cable came off. Cable came off. Connection is opened by the open request from the other station. Connection close is detected by the open request from the other station. Connection is closed at the falling of the open request. : Operation by user : Operation by system : Event Figure 2.12 TCP/IP Receiving side for ASR port status flag and ASR port open request flag 2 13

28 [UDP/IP] If user turns on the ASR port open request flag [A], the ASR port is opened and it is that the ASR port is opening because the ASR port status flag [1] is turned off. In this status, message data can be transmitted and received. When UDP/IP other station is fixed, ARP packet is transmitted to communication destination when message data is transmitted for the first time. If there is no response to this ARP packet, ASR port is closed and the ASR port status flag [1] is turned off. In case of only receiving or when message data is transmitted after second time, the system does not close the ASR port because ARP packet is not transmitted to communication destination. If user turns off the ASR port open request flag [A], the ASR port is closed and it is indicated that the ASR port is closing. In this status, message data cannot be transmitted and received. Open ASR port Close ASR port Open ASR port [A] [1] Open ASR port at the rising of open request : Operation by user : Operation by system Close ASR port at the falling of open request Close ASR port when there is no response to ARP in sending message data (*) (*) Only when UDP/IP other station is fixed, or receiving (sending and receiving) is chosen. Fig UDP/IP for ASR port status flag and ASR port open request flag 2 14

29 (2) Event transmitting completion flag [2] and Event transmitting request flag [B] If user turns on the event transmitting request flag [B] when message data can be transmitted and received (the connection is established in TCP/IP, and ASR port is opened in UDP/IP), the system will transmit message data. If the transmitting of message data is completed, the system will turn on the event transmitting completion flag [2]. If user performs the event transmitting again, user must turn on the event transmitting request flag [B] after turning OFF. And when monitoring whether the transmitting to the event transmitting request has been completed or not, user needs t turn off the event transmitting completion flag before turning on the event transmitting request flag. If the event transmitting request flag [B] is turned ON when message data cannot be transmitted and received (the connection is not established in TCP/IP, and ASR port is not opened in UDP/IP), the error flag and the error code are set because of error. [B] Turn off the flag by user if necessary. (System does not turn off the flag.) [2] Transmitting completion Transmitting starts if the rising of the event transmitting is detected. : Operation by user : Operation by system Figure 2.14 Event transmitting completion flag and Event transmitting request flag (3) Receiving completion flag [3] If the receiving of message data is completed, the receiving completion flag [3] will turn ON. Since the system turns on this flag whenever the receiving is completed, user needs to turn off this flag when monitoring the receiving using this flag. Turn off the flag by user if necessary. (System does not turn off the flag.) [3] Receiving completion : Operation by user : Operation by system Figure 2.15 Receiving completion flag 2 15

30 (4) Error flag [4] and Error code [5] The system will turn on the error flag [4] and store the error code [5] if factors of the error are found in the system. User must clear this flag and area if necessary because the system does not clear them. [B] Turn OFF the flag by user if necessary. (System does not turn OFF the flag.) [4] Detection of error [5] Error code set Error code reset : Operation by user : Operation by system Clear the code by user if necessary. (System does not clear the code.) Figure 2.16 Error flag and Error code (5) Transmitting counter and Receiving counter The increment of the transmitting counter is performed when message data is transmitted. The increment of the receiving counter is performed when message data is received. User must clear the transmitting counter and the receiving counter if necessary because the system does not clear them. Transmitting of message data Transmitting of message data Transmitting counter Increment Increment Clear the counter by user if necessary. (System does not clear the counter.) Receiving of message data Receiving of message data Receiving counter : Event Increment Increment Clear the counter by user if necessary. (System does not clear the counter.) Figure 2.17 Transmitting counter and Receiving counter 2 16

31 TCP/IP protocols When using TCP/IP to communicate, it is necessary to establish the connection between communication stations. Otherwise, message data cannot be sent and received. In order to establish the connection, set one side to the TCP/IP connection active open, and set the other side to the TCP/IP connection passive open. Open a port of the TCP/IP connection passive open side, and then open a port of the TCP/IP connection active open after the connection open stood by to open. After the connection established, data can be sent and received. And in order to close the connection, close the port you want to close first. Active open side Passive open side EHV-CPU Server Active open Connection open error (Because the passive open side is opened but it is not the stand by status.) Passive open Active open Connection establishment Data sending and receiving Connection close Figure 2.18 Example of TCP/IP protocols Reference In order to open the port on the ASR communication port, turn on the ASR port open request flag of the control register. Ex.) In case of ASR communication port 1: WRF601 = H0001 In order to close the port on the ASR communication port, turn off the ASR port open request flag of the control register. Ex.) In case of ASR communication port 1: WRF601 = H

32 UDP/IP protocols In the ASR communication port, when using UDP/IP to communication, it is necessary to open the ASR port. Message data can be sent and received after the ASR port is opened. Message data cannot be sent and received if the ASR port is closed. When receiving messages while the ASR port is closed, the receiving data is cancelled. In the ASR communication port, close the port to terminal the communication. Active open side Passive open side EHV-CPU Server ASR port open Port open (*) (*) The ready to send and receive data is called Port open in this manual. Data sending and receiving ASR port close Port close (*) (*) The termination to send and receive is called Port close in this manual. Figure 2.19 Example of UDP/IP protocols Reference In order to open the port on the ASR communication port, turn on the ASR port open request flag of the control register. Ex.) In case of ASR communication port 1: WRF601 = H0001 In order to close the port on the ASR communication port, turn off the ASR port open request flag of the control register. Ex.) In case of ASR communication port 1: WRF601 = H

33 Sample program [Sample 1] Network consists of two EHV-CPUs as follows, and the Control Editor sets the ASR communication. The setting information for two EHV-CPUs is as follows. EHV-CPU1 (Active, Send) EHV-CPU2 (Passive, Receive) Data sending Figure 2.20 Connection diagram of Sample 1 Table 2.10 Setting information of Sample 1 Setting EHV-CPU1 EHV-CPU2 1 IP address Port No Protocol TCP/IP-Active, Specified TCP/IP-Passive, Specified 4 Send / Receive Send Receive 5 Access Point IP address Access Point Port No Send Timing Cyclic sending: 1 second - 8 Transmission area WR0 to WRF - 9 Receiving area - WN0 to WNF [Description of Sample program] The connection is opened and the transmitting starts when R0 of EHV-CPU1 is turned ON. [Sample program of EHV-CPU1] R0 DIF WRF601 = H0001 While the connection of ASR port a is not established, ASR port a is opened at the rising edge of user turns on R0. After the connection is established, ASR communication is started according to the setting and data is transmitted at one second interval. WRF600.0 DFN WRF601 = H0000 When the connection of ASR port 1 is cut by other station and the cable is cut, the ASR port open request flag falls when the connection is closed. 2 19

34 [Sample program of EHV-CPU2] R7E3 WRF601.0 DFN WRF601 = H0001 Opens the connection just after the RUN start, or at the falling of OFF of the ASR open request flag after the connection of ASR port 1 is closed. WRF600.0 DFN WRF601 = H0000 When the connection of ASR port 1 is cut by other station and the cable is cut, the ASR port open request flag falls when the connection is closed. [Sample 2] Network consists of one EHV-CPU and one server as follows, and the Control Editor set the ASR communication of EHV-CPU. The setting information for EHV-CPU3 and the server is as follows. When the even occurs, 5-word data from WRF00B to WRF00F of EHV-CPU3 is transmitted from EHV-Cpu3 to the server. EHV-CPU3 (Active, Send) Server (Passive, Receive) Data sending at event occurrence Figure 2.21 Connection diagram of Sample 2 Table 2.11 Setting information of Sample 2 Setting EHV-CPU3 Server 1 IP address Port No Protocol TCP/IP-Active, Specified TCP/IP-Passive, Optional 4 Send / Receive Send Receive 5 Access Point IP address Access Point Port No Send Timing Event sending - 8 Transmission area WRF00B to WRF00F - 9 Receiving area - - [Description of sample program] The connection is opened when R0 of EHV-CPU3 is turned ON, and the event transmitting is performed by turning ON R1 at the event occurrence. 2 20

35 [Sample program of EHV-CPU3] R0 DIF WRF601 = H0001 Opens the ASR port 1 at the rising edge of R0. WRF600.0 DFN WRF601 = H0000 The ASR port open request flag falls when the ASR port 1 is closed. R1 DIF WRF601.1 S Performs the event transmitting at the rising edge of R1. WRF600.1 DIF WRF601.1 R WRF600.1 The event transmitting completion flag, the event transmitting request flag, and R1 fall when the event transmitting is completed. R R1 R [Sample 3] Network consists of EHV-CPU and Web controller as follows, and the Control Editor sets the ASR communication of EHV-CPU. ASR communication of Web controller is set using the Web browser. The setting information of EHV-CPU4 and Web controller is as follows. The connection is established between EHV-CPU4 and Web controller in two seconds later after RUN of EHV-CPU4, 16-word data from WR0 to WRF of EHV-CPU4 is transmitted from EHV-CPU to Web controller at one second interval. In Web controller, the received data is stored in WR0 to WRF. And 16-word data from WR10 to WR1F of Web controller is transmitted from Web controller to EHV-CPU4, and the received data is stored in WR10 to WR1F in EHV-CPU4. EHV-CPU4 (Active, Send / Receive) Web controller (Passive, Send / Receive) Data sending and receiving Figure 2.22 Connection diagram of Sample

36 Tale 2.12 Setting information of Sample 3 Setting EHV-CPU4 Web controller 1 IP address Port No Protocol TCP/IP-active, Specified TCP/IP-passive, Specified 4 Send / Receive Send / Receive Send / Receive 5 Access point IP address Access point Port No Send Timing Cyclic sending: 1 second Cyclic sending: 1 second 8 Transmission area WR0 to WRF WR10 to WR1F 9 Receiving area WR10 to WR1F WR0 to WRF [Description of sample program] The connection is established between EHV-CPU4 and Web controller in two seconds after RUN of EHV-CPU4, and the sending and receiving are started. (If the connection is established before RUN of EHV-CPU4, the connection is closed immediately after RUN and the connection is established again.) [Sample program of EHV-CPU4] R7E3 WRF600.0 DFN WRF601 = H0000 R0 = 1 ASR port is closed immediately after RUN or in falling which ASR port status flag turned off after ASR port 1 was closed. R0 TD0 TC 1ms 2000 TD0 turns on in 2 seconds later from ASR port close. TD0 WRF601 = H0000 ASR port open request bit is turned on in 2 seconds from ASR port close, and then ASR port is opened. [Sample program of Web controller] When Web controller is set to TCP/IP passive station, the connection stands by to open when the power supply is turned on or immediately after the connection is cut. Therefore a program to control the connection is unnecessary. 2 22

37 [Sample 4] Network consists of two EHV-CPUs as follows, and the Control Editor sets the ASR communication. The setting information of two EHV-CPUs is as follows. 16-word data from WR0 to WRF of EHV-CPU5 is transmitted from EHV-CPU5 to EHV-CPU6. In EHV-CPU6, the received data is stored in WR0 to WRF. EHV-CPU5 (Active, Send) EHV-CPU6 (Passive, Receive) Data sending Figure 2.23 Connection diagram of Sample 4 Table 2.13 Setting information of Sample 4 Setting EHV-CPU5 EHV-CPU6 1 IP address Port No Protocol UDP/IP, Specified UDP/IP, Specified 4 Send / Receive Send Receive 5 Access points IP address Access points Port No Send Timing Cyclic sending: 40ms - 8 Transmission area WR0 to WRF - 9 Receiving area - WR0 to WRF [Description of sample program] ASR port is opened in two seconds later after RUN of EHV-CPU5. If there is a communication target is on the network (there is a response to ARP packet), the transmission is executed automatically. And similarly, EHV-CPU6 executes the receiving if the ASR port is opened in EHV-CPU6 because the ASR port is opened also in two seconds after RUN of EHV-CPU

38 [Sample program of EHV-CPU5 and 6] R7E3 WRF600.0 DFN WRF601 = H0000 R0 = 1 ASR port is closed immediately after RUN or in falling which ASR port status flag turns off after ASR port 1 is closed. R0 TD0 TC 1ms 2000 TD0 turns on in two seconds later after ASR port close. TD0 WRF601 = H0000 ASR port open request bit is turned on in two seconds later after ASR port close, and ASR port is opened. In case of UDP/IP, it can be sent and received in this status. 2 24

39 Cautionary note In communication (Task code processing and ASR communication) of EHV-CPU series, the response may delay if CPU is loaded. We would explain a load of CPU below. Please utilize this as a standard in considering the responsibility of communications. [About Communication processing time in CPU module] CPU module executes processing by two processors, one is an operation processor to execute user programs and the other is a main processor to execute a system program processing, and END processing and a communication processing. While the operation processor executes the user program, the main processor executes the communication processing. Therefore, a total of scan time and system processing time is communication processing time. Taking 40ms which is a minimum transmission interval of ASR communication for instance, a rate of time for each processing executed by the main processor is shown below. In this case, response delay and transmission delay occur at least unless task code communication and ASR communication are completed within approx. 28ms for communication processing. Processing time 40ms System program processing 6.4 [ms] (Fixed) *1 Communication processing (Task code communication, ASR communication) Scan time + System processing time 28.7 [ms] (Fluctuation) I/O refresh processing 2.2ms (Fluctuation) *3 END processing 2.7ms (Fluctuation) *2 *1. 1ms cyclic processing. In this case, it is executed 40 times. *2. Processing time when the number of program steps is 0 *3. Processing time when the number of I/O mounted is 66 words (1056 points, that is 66 modules equipped 16-point I/O each are mounted.) Figure 2.24 An example of ratio of each processing by main processor within 40ms Communication processing time is not fixed but fluctuates under the influence of the following factors. (a) Scan time of user program While the operation processor executes the user program, the main processor can execute the system processing and the communication processing. The longer scan time becomes, the more communication processing time increases. And since the number of times that END processing occurs within a same time also decreases if scan time get longer, END processing decreases and communication processing time increases in above figure. (b) I/O configuration I/O refresh processing time increases and communication processing time increases in proportion to the number of modules mounted. It takes 1µs per word as processing time depending on the external I/O points and the number of link data. (c) System processing time (Setting by Control Editor) This is a setable time, using operation parameter of Control Editor. This System processing means the communication time. 2 25

40 [Calculation method of communication processing time] Communication processing time can calculate using the following methods, and is calculated on the basis of the transmission interval of ASR. (Example) - Whole processing time (ASR transmission interval) 40ms = 40,000µs - System program processing time (1ms cyclic processing) 160µs - Scan time (Displayed value of CPU status current value) (*) 2ms = 2,000µs - END processing time (Fixed) (*) 80µs - I/O refresh processing time (In mounting 66 module with 16-point I/O) (*) 66µs - System processing time (Setting by Control Editor) 1ms = 1,000µs (*) Operation time for one scan (a) System program processing time: 160 [µs/time] 40 [time] (Execution times in 40ms) = 6,400[µs] (b) Number of scan times of user program: (Whole processing time - (a)) / (Scan time + END processing time + I/O refresh time + System processing time) = ( 40,000[µs] - 6,400[µs] ) / ( 2,000[µs] + 80[µs] + 66[µs] + 1,000[µs] ) 10.7 [time] (c) Scan time: 2,000 [µs/time] (b) = 2,000 [µs/time] 10.7 [time] = 21,400 [µs] (d) System processing time: 1,000 [µs/time] (b) = 1,000 [µs/time] 10.7 [time] = 10,700 [µs] Communication processing time = (c) + (d) = 21,400 [µs] + 10,700 [µs] = 32,100 [µs] = 32.1ms In this example, the communication processing time is 32.1ms. If processing of task code communication and ASR communication is 32.1ms or less, delay of communication response does not occur. Whole processing time 40ms System program processing time 6.4 [ms] (a) Communication processing (Task code communication and ASR communication) Scan time + System processing time 32.1 [ms] (c) + (d) I/O refresh processing time: 66[µs] 10.7[time] 0.7[ms] END processing time: 80[µs] 10.7[time] 0.9[ms] Figure 2.25 Calculation of communication processing time 2 26