Hitachi FL.NET User Manual
  1. Manuals
  2. Brands
  3. Hitachi Manuals
  4. Controller
  5. FL.NET
  6. User manual
Hitachi FL.NET User Manual

Hitachi FL.NET User Manual

Option for s10v
Hide thumbs Also See for FL.NET:
Table of Contents

Quick Links

Table of Contents

Troubleshooting

loading

Related Manuals for Hitachi FL.NET

Summary of Contents for Hitachi FL.NET

  • Page 3 Second Edition, July 2011, SVE-1-130(B) (out of print) Third Edition, January 2013, SVE-1-130(C) All Rights Reserved, Copyright © 2010, 2013, Hitachi, Ltd. The contents of this publication may be revised without prior notice. No part of this publication may be reproduced in any form or by any means without permission in writing from the publisher.
  • Page 4 SAFETY PRECAUTIONS Before installation, operation, maintenance, and/or inspection of this product, be sure to read through carefully this manual and other related manuals. Do not use this product until you are familiar with all the information concerning this product, safety information, and precautions provided in those manuals.
  • Page 5 Do not install, wire, handle, modify, or use maintenance parts in any manner not described in this manual. Such a practice may result in breakdown of this equipment or peripherals, injury or even death. Hitachi will not be responsible for any accident or failure resulting from such mishandling.
  • Page 6 During work For each procedure, follow the given sequence of steps. Use the special tools and instruments, specified for the work in the manual or commercially available tools and instruments which fit the purpose. Use measurement instruments and powered tools which are properly calibrated or periodically inspected.
  • Page 7 Prevention of electric shocks Before starting work, make sure that, unless otherwise specifically instructed, there is no potential electric hazard in the maintenance area such as insufficient grounding or a wet floor. Before starting work, note where the emergency power-off switches are located and make sure you know how to operate them.
  • Page 8 Procedures in an emergency For electric shock Do not panic. Do not become another victim through contact with the injured person. First, shut off the electric current passing through the victim. Use the emergency power-off switch, if there is one, or, otherwise, a normal power- off switch.
  • Page 9 NOTICE There are no specific rules about the mounting position or unoccupied slots. This model-LQE702 FL.NET module may not be mounted on the same mount base in conjunction with any other FL.NET module of models LQE500 or LQE502 and any EQ.LINK module of model LQE701.
  • Page 10 (chapter 3, page 3-3) NOTICE Dust or other foreign matter might accumulate on the connector, resulting in poor contact. Immediately after the module is unpacked, perform the mounting and wiring procedures. To prevent the module from being damaged, observe the following precautions when you mount or demount the module: •...
  • Page 11 LPU memory area word count setting. If any node is left without being set, the FL.NET module cannot transfer to the S10V the data received from that node into the common memory.
  • Page 12 If any node is omitted from the node settings given, the FL.NET module cannot transfer the higher layer status or FA link status of that node to the S10V.
  • Page 13 (chapter 5, page 5-49) NOTICE When issuing a request to the FL.NET module, do not simultaneously use the C mode handler and mathematical/logical function. You cannot specify an index in a parameter (PI/O address.) (chapter 5, page 5-55) NOTICE The server feature of the FL.NET module returns an abnormal response if, on reception of a word block read request, the virtual size is found exceeding 512 words.
  • Page 14 (chapter 5, page 5-65) NOTICE The FL.NET module does not support the server feature for a stop directive. If a stop request is issued to the FL.NET module, it returns a response to indicate that it does not support the stop directive.
  • Page 15 (chapter 5, page 5-115) NOTICE The S10V BASE SYSTEM is required for operating the S10V FL.NET. If it is not installed, you cannot install the S10V FL.NET. Before installing the S10V FL.NET, be sure to exit all the currently open Windows®-based programs.
  • Page 16 Hitachi Engineering & Services Co., Ltd. The malfunctioning part will be replaced or repaired free of charge. If the malfunctioning is shipped, however, the shipment charge and packaging expenses must be paid for by the customer.
  • Page 17 This Page Intentionally Left Blank...
  • Page 18 This manual provides information for the following hardware and program product: FL.NET (LQE702) S-7895-30, S10V FL.NET SYSTEM, 01-03...
  • Page 19 Revision record Revision record Revision No. Month, Year Remarks (revision details and reason for revision) First edition February 2010 Product safety labeling is revised to include July 2011 additional safety level information Windows® 7 (32-bit) operating system is newly January 2013 supported.
  • Page 20 Thank you for purchasing the FL.NET module, which is an option for use with the S10V. This manual, named “USER’S MANUAL OPTION FL.NET,” describes how to use the FL.NET module. For proper use of the CPU link module, it is requested that you thoroughly read this manual.
  • Page 21 Network [FL-net (OPCN-2)] - Protocol Specification JEM 1479 2002-revision issued by Japan Electrical Manufacturers’ Association (JEMA) The existing parameter setting software (FL.NET system) shown in the following table can be used for LQE702 regardless of the FL-net protocol version. Name...
  • Page 22 Memory capacities and requirements, file sizes and storage requirements, etc. must be calculated according to the formula 2 . The following examples show the results of such calculations by 2 (to the right of the equals signs). 1 KB (kilobyte) = 1,024 bytes 1 MB (megabyte) = 1,048,576 bytes 1 GB (gigabyte) = 1,073,741,824 bytes...

  • Page 23: Table Of Contents

    2.1.4 Link parameter setup area ................... 2-6 2.1.5 Profile system parameter setup area ................2-7 2.2 FL.NET Module Component Names and Functions ............3 FL.NET MODULE INSTALLATION ..................3-1 3.1 Mount Base ........................... 3-2 3.2 Mounting the Module ......................3-2 3.3 Setting the MAIN/SUB Selector Switch ................
  • Page 24 5.1.8 Cyclic transmission and area ..................5-11 5.1.9 Message transmission ....................5-16 5.2 FL.NET Module Setup Procedures ..................5-28 5.2.1 Startup procedure ...................... 5-28 5.2.2 Module installation and switch setup ............... 5-30 5.2.3 Tool connection procedure ..................5-30 5.2.4 Tool startup procedure ....................5-30 5.3 Using the FL.NET Module ....................
  • Page 25 6.1 Maintenance and Inspection ....................6-2 6.1.1 Replacing or adding on the module ................6-3 7 TROUBLESHOOTING ......................7-1 7.1 Troubleshooting ........................7-2 7.1.1 Procedure ........................7-2 7.1.2 Trouble detection and solution ................... 7-3 7.2 Network Problems and Repairing ..................7-4 7.3 Precautions for FL-net Use ....................
  • Page 26 FIGURES Figure 1-1 FA Control Network Configuration Example ............1-2 Figure 1-2 FL-net Protocol Basis Structure ................1-3 Figure 2-1 FA Control Network Configuration Example ............2-2 Figure 3-1 Mounting the Option Module ................. 3-2 Figure 3-2 Setting the MAIN/SUB Selector Switch ..............3-4 Figure 4-1 100BASE-TX Communication Cable Wiring ............
  • Page 27 Figure 5-31 IP Address Setup Window ................... 5-29 Figure 5-32 Link Parameter Setup Window ................5-31 Figure 5-33 Common Memory Data Transfer Image of FL.NET Module ......5-34 Figure 5-34 Self-node LPU Memory Allocation Window ............5-36 Figure 5-35 Common Memory Area Setup Window for Other Participating Nodes ....5-38 Figure 5-36 Setup Window for Setting Various Status Flag Areas for the Self-node .....
  • Page 28 Figure 8-6 Token Flow......................8-11 Figure 8-7 Startup Timing Diagram 1 ..................8-14 Figure 8-8 Startup Timing Diagram 2 ..................8-15 Figure 8-9 Device Communication Information Classification ..........8-20...
  • Page 29 Error Memory Area for Link Data ................2-6 Table 2-7 Profile System Parameter Setup Area (Description example) ......... 2-7 Table 3-1 Mount Bases Applicable to the FL.NET Module ............ Table 3-2 Details of MAIN/SUB Selector Switch ..............3-4 Table 4-1 Network Component List ..................
  • Page 30 Table 8-12 Reception Management Data for Message Sequence Number Management ..8-19 Table 8-13 Details of Common Parameters ................8-21 Table 8-14 Details of Device-Specific Parameters ..............8-22 Table 8-15 System Parameter Tabular Document Notation (PLC Examples) ......8-22 Table 8-16 System Parameter Tabular Document Notation (CNC Examples) ......8-27...
  • Page 31 This Page Intentionally Left Blank...

  • Page 32: Overview

    1 OVERVIEW...

  • Page 33: What Is Fl-Net

    1 OVERVIEW 1.1 What is FL-net FL-net is an open FA network that the FA Open Systems Promotion Group (FAOP) standardized in the Manufacturing Science and Technology Center (MSTC), which is an organization affiliated to the Ministry of International Trade and Industry. The Japan Electrical Manufacturers’ Association (JEMA) prepared the specification.

  • Page 34: Fl-Net Features

    1 OVERVIEW 1.2 FL-net Features FL-net has the following features: • An open system can be implemented. • A multivendor environment can be established. • Programmable controllers (PLCs), computer numerical control (CNC) devices, and various other factory automation controllers and personal computers of many different brands can be interconnected to exercise control and monitoring functions.
  • Page 35 When FL-net-compliant modules are interconnected, the performance varies with the connected devices. However, when the S10V FL.NET modules (Ver. 2.00: Model LQE702) are interconnected, the response speed is as high as 42 ms/32 nodes (in 2k bit + 2k word mode).

  • Page 36: System Software Specifications

    1.3 System Software Specifications 1.3.1 System overview To use the FL.NET module, you must register various items of module information in the module. This can be accomplished by using the system software (tools) listed below. The operating procedures for these tools are similar to those for general Windows® applications.
  • Page 37 This Page Intentionally Left Blank...

  • Page 38: Fl.net Module

    2 FL.NET MODULE...

  • Page 39: System Configuration

    2 FL.NET MODULE 2.1 System Configuration The S10V FL.NET module (LQE702) is Hitachi’s module that is compliant with the FL-net protocol. This is hereafter described as the FL.NET module. Figure 2-1 shows a typical system configuration for the use of FL-net communications.

  • Page 40: Functionality And Performance Specifications

    Twisted-pair cable: 100 m maximum/segment (category 5 or higher) 2.1.2 Support tool specification For the use of the FL.NET module, you must set the node numbers, common memory, and various other items with the setup tool named [S10V FL.NET SYSTEM].

  • Page 41: Link Data Specifications

    2.1.3 Link data specifications (1) Common memory area The FL.NET module allows you to set up a common memory area for each node. For the common memory area setup procedure, see “5.3.1 Link parameter setup procedure.” For the procedure for reserving a common memory area in the LPU’s memory, see “5.3.2 LPU memory allocation procedure.”...

  • Page 42: Table 2-5 Virtual Address Spaces And Symbol Names

    2 FL.NET MODULE Table 2-5 shows the relationships among virtual address spaces, memory addresses, and registers. Table 2-5 Virtual Address Spaces and Symbol Names Register name Symbol name Memory address Virtual address space External input X000 to XFFF 0x240000 to 0x241FFE...

  • Page 43: Link Parameter Setup Area

    For detailed information about the tables, see “7 TROUBLESHOOTING.” (4) Status memory area For the self-node status of the FL.NET module, FA link status, and Higher layer status you can refer to the setup tool [S10V FL.NET SYSTEM]. 2.1.4 Link parameter setup area The link parameters for the FL.NET module can be referenced with the setup tool named S10V...

  • Page 44: Profile System Parameter Setup Area

    2 FL.NET MODULE 2.1.5 Profile system parameter setup area The profile system parameters for the FL.NET module can be referenced with the setup tool named S10V FL.NET SYSTEM (for details, see “5.3 Using the FL.NET Module”). For the FL.NET module, the profile system parameters for the vendor name, manufacturer model, and protocol version are fixed data.

  • Page 45: Fl.net Module Component Names And Functions

    2 FL.NET MODULE 2.2 FL.NET Module Component Names and Functions Name Function LQE702 ① FL.NET RUN LED ① This LED indicates when the module is up and ② running normally. ③ LER LED This LED indicates when a unconnected FA link, or ②...

  • Page 46: Fl.net Module Installation

    3 FL.NET MODULE INSTALLATION...

  • Page 47: Mount Base

    3 FL.NET MODULE INSTALLATION 3.1 Mount Base The FL.NET module can be mounted in the mount bases shown in Table 3-1. Table 3-1 Mount Bases Applicable to the FL.NET Module Name Model Specification 4-slot mount base HSC-1540 Power supply + LPU + 4 slots (option, for I/O)
  • Page 48 3 FL.NET MODULE INSTALLATION NOTICE Dust or other foreign matter might accumulate on the connector, resulting in poor contact. Immediately after the module is unpacked, perform the mounting and wiring procedures. To prevent the module from being damaged, observe the following precautions when you mount or demount the module: •...

  • Page 49: Setting The Main/Sub Selector Switch

    The main module/submodule setup can be accomplished by setting the MAIN/SUB selector switch either in “0” position (main module) or “1” position (submodule). If only one FL.NET module is mounted in the mount base, set its MAIN/SUB selector switch in “0” position.

  • Page 50: Fl.net Module Wiring Procedures

    4 FL.NET MODULE WIRING PROCEDURES...

  • Page 51: Connecting The Communication Cable

    4 FL.NET MODULE WIRING PROCEDURES 4.1 Connecting the Communication Cable The module uses the 100BASE-TX interface connector to establish communication with the other modules. Ensure that the cable is connected as shown in Figure 4-1. LQE702 FL.NET 100MLINK MAIN /SUB Insert the communication cable into the RJ45 connector.

  • Page 52: Recommended Network Components

    4 FL.NET MODULE WIRING PROCEDURES 4.2 Recommended Network Components The LQE702 is a standard product conformed to the global standard of IEEE802.3. It may happen, however, that the LQE702 does not function successfully when used in conjunction with certain network components conforming to the same standard. To avoid this inconvenience, use network components of the make recommended by us to connect to the LQE702.

  • Page 53: System Configuration

    4 FL.NET MODULE WIRING PROCEDURES 4.3 System Configuration Data communication between Ethernet network devices becomes possible if you connect such devices to a hub, as shown in Figure 4-2. To connect Ethernet devices to the hub, use twisted- pair cables.

  • Page 54: Figure 4-4 A Sample Configuration Using 100-Mbps Hubs Of Class 2

    Figure 4-5 A Sample Configuration Using 100-Mbps Switching Hubs NOTICE The only port setting that is supported by the FL.NET module (model LQE702) is auto-negotiation. Do not use 100-Mbps full-duplex setting for the port of the switching hub. Disregarding this rule may result in a failure of data...

  • Page 55: Ground Wiring

    4 FL.NET MODULE WIRING PROCEDURES 4.4 Ground Wiring The FL.NET module requires no ground wiring. 2 mm or more Class D grounding (*) Figure 4-6 Unit Ground Wiring * Class D grounding is defined in the Technical Standard for Electrical Facilities of Japan. This standard states that the grounding resistance must be 100 ohms or less for equipment operating on 300 VAC or less, and 500 ohms or less for devices that shut down automatically within 0.5...

  • Page 56: User Guide

    5 USER GUIDE...

  • Page 57: Fl-Net

    5 USER GUIDE 5.1 FL-net 5.1.1 FL-net overview (1) FL-net concept The FL-net is an Ethernet-based factory-automation control network. It has a cyclic transmission function and message transmission function. The basic ideas incorporated in the FL-net are as follows: • Ethernet is used as the media (physical level, data link) of communication between FA (factory automation) controllers.

  • Page 58: Figure 5-2 Fa Link Protocol

    5 USER GUIDE (2) FL-net protocol The FL-net consists of six protocol layers as shown in Figure 5-2. The transport layer and network layer use UDP/IP, whereas the data link layer and physical layer use Ethernet. Application layer Controller interface Service function Cyclic transmission...

  • Page 59: Connection Capacity And Node Numbers

    5 USER GUIDE (4) FL-net IP address The IP address is an address that is used in IP(Internet Protocol)-based transmission to indicate a specific node (station). It is therefore necessary to set and manage IP addresses so as to avoid address duplication. For each FL-net node, an IP address needs to be set.

  • Page 60: Supported Data Communications

    5 USER GUIDE 5.1.3 Supported data communications Data communications supported by the FL-net are cyclic transmission and message transmission. Message Token-attached data cyclic data Cyclic transmission Cyclic transmission + message transmission Figure 5-5 Data Communication Types Supported by FL-net (1) Cyclic transmission Cyclic transmission provides periodic transmission of data.

  • Page 61: Figure 5-7 Typical Message Transmission

    5 USER GUIDE (2) Message transmission Message transmission provides nonperiodic transmission of data. Under normal conditions, communication is transmitted to a specific node upon request. Message transmission from node Message transmission from node 1 to node 3 6 to node 4 FL-net Node 1 Node 2...

  • Page 62: Transfer Cycle And Monitoring

    5 USER GUIDE 5.1.5 Transfer cycle and monitoring In cyclic data communication, the common memory is refreshed at virtually fixed intervals. Message transmission is controlled to prevent a single message communication from causing the time limit on the common memory refresh cycle to be exceeded. Each node constantly monitors message communication frames flowing within the network during the time interval between the reception of a token addressed to itself and the reception of the next token addressed to itself.

  • Page 63: Data Area And Memory

    5 USER GUIDE 5.1.6 Data area and memory FL-net FL.NET module LPU module Cyclic transmission LPU memory for area 1 Common memory area 1 LPU memory for area 2 Common memory area 2 Message transmission LPU memory for message transmission...

  • Page 64: Communication Management Tables

    5 USER GUIDE 5.1.7 Communication management tables Node status management is provided by means of the self-node management table, participating node management table, and network management table. (1) Self-node management table The self-node management table is used to manage the self-node setup. Table 5-1 Self-node Management Table Name Length...

  • Page 65: Table 5-2 Participating Node Management Table

    5 USER GUIDE (2) Participating node management table The participating node management table is used to manage the information about nodes that have participated in the network. Table 5-2 Participating Node Management Table Name Length Description/data range Node number 1 byte 1 to 254 Higher layer status 2 bytes...

  • Page 66: Cyclic Transmission And Area

    5 USER GUIDE 5.1.8 Cyclic transmission and area (1) Cyclic transmission overview The cyclic transmission function uses the common memory to periodically exchange data. • Transmits data when the node holds the token. • Recognizes nodes conducting no cyclic transmission as far as they participate in the network.
  • Page 67 5 USER GUIDE Time Node #1 Node #2 Node #3 Node #N Token Node #1 Node #2 Node #3 Node #N Token Figure 5-12 Token Rotation and Cyclic Transmission 1 Time Node #1 Node #2 Node #N-1 Node #N Token Node #1 Node #2 Node #N-1...
  • Page 68 5 USER GUIDE (2) Common memory The ideas of the common memory are described below. Furnishes the nodes conducting cyclic transmission with functions that can be handled as the functions of the common memory. Two areas (Area 1 and 2) can be allocated for one node. Two or more frames are used for data transmission when the 1,024-byte transmission size limit per frame is exceeded by an area transmitted by one node.

  • Page 69: Figure 5-16 Common Memory Area 1 And 2

    5 USER GUIDE It is also possible to use only a reception area of the common memory. Common memory Common memory Common memory for Node 01 for Node 02 for Node 05 (Reception) (Reception) (Transmission) (Reception) (Transmission) (Reception) ・ ・ ・...

  • Page 70: Figure 5-17 Data Synchronicity Assurance

    In cyclic transmission, the data to be transmitted is divided into frames depending its size. The following procedures are used to assure common memory (internal memory such as the FL.NET module) synchronicity on an individual node basis. Transmission timing When a data transmission is requested by a higher layer, the cyclic data of the self-node is copied to a buffer to prepare for transmission and then sequentially transmitted.

  • Page 71: Message Transmission

    5 USER GUIDE 5.1.9 Message transmission (1) Message transmission overview The message transmission function supports asynchronous data exchanges that are made between nodes. The fundamentals of the message transmission function are described below. When a node receives the token, it can transmit up to one frame of data before cyclic frame transmission.

  • Page 72: Table 5-4 List Of Supported Message Transmissions

    5 USER GUIDE (2) List of supported messages Table 5-4 lists the types of messages that are supported by the FL.NET module. Table 5-4 List of Supported Message Transmissions Message Request Response Byte block read Byte block write Word block read √...

  • Page 73: Figure 5-19 Byte Block Read

    Byte block read This message function reads a remote node’s virtual address space (32-bit address space) from the network byte by byte (in 1-address 8-bit units). This function is not supported by the FL.NET module. Request message Response message 8 bits...

  • Page 74: Figure 5-20 Byte Block Write

    Byte block write This message function writes into a remote node’s virtual address space (32-bit address space) from the network byte by byte (in 1-address 8-bit units). This function is not supported by the FL.NET module. Request message Response message...

  • Page 75: Figure 5-21 Word Block Read

    Word block read This message function reads a remote node’s virtual address space (32-bit address space) from the network word by word (in 1-address 16-bit units). For use instructions, see “5.3 Using the FL.NET Module.” Request message Response message 16 bits...

  • Page 76: Figure 5-22 Word Block Write

    Word Block Write This message function writes into a remote node’s virtual address space (32-bit address space) from the network word by word (in 1-address 16-bit units). For use instructions, see “5.3 Using the FL.NET Module.” Request message Response message...

  • Page 77: Figure 5-23 Network Parameter Read

    This function reads a remote node’s network parameter information from the network. The table 5-5 lists the items of information that this function reads. For use instructions, see “5.3 Using the FL.NET Module.” Table 5-5 Network Parameter Information Node number...

  • Page 78: Figure 5-24 Network Parameter Write

    This function edits a remote node’s network parameter information from the network. The following items of information can be edited. For use instructions, see “5.3 Using the FL.NET Module.” • Node name (equipment name) • Common memory area address and size If the starting address of area 1 or 2 is outside the common memory, an error occurs.

  • Page 79: Figure 5-25 Run/Stop Directive

    Run/stop directive This function allows the network to remotely run or stop the operation of a device connected to the FL-net. Only the associated request is supported by the FL.NET module. For use instructions, see “5.3 Using the FL.NET Module.”...

  • Page 80: Figure 5-26 Profile Read

    This function reads from the network the device profile system parameters that represent the information about a remote node. Only the associated response is supported by the FL.NET module. The system parameters represent the following items of information: • Common parameters (essential) •...

  • Page 81: Figure 5-27 Communication Log Data Read

    5 USER GUIDE Communication log data read This function reads a remote node’s log information from the network. For use instructions, see “5.3 Using the FL.NET Module.” Request message Response message Communication log data Figure 5-27 Communication Log Data Read Communication log data clear This function clears a remote node’s log information from the network.

  • Page 82: Figure 5-29 Message Return Function

    FL-net higher layer sends the same notification to the user interface level. When the notification is sent to the user interface level, it is necessary to create and return an associated response. For use instructions, see “5.3 Using the FL.NET Module.”...

  • Page 83: Fl.net Module Setup Procedures

    5 USER GUIDE 5.2 FL.NET Module Setup Procedures 5.2.1 Startup procedure The startup procedure for the FL.NET module is described below: ① Switch OFF the LPU unit and then install the FL.NET Start module. Mount the module. ② Set the MAIN/SUB selector switch on the FL.NET module (See “3.3 Setting the MAIN/SUB Selector...

  • Page 84: Figure 5-31 Ip Address Setup Window

    Note 1: If all the IP address entries are set to 0 or 255, an input error occurs. Note 2: If all the host number entries are set to /0 or /F, the FL.NET module performs the same process as in cases where IP address setup is not completed.

  • Page 85: Module Installation And Switch Setup

    5 USER GUIDE 5.2.2 Module installation and switch setup For the procedures for module installation and switch setup, see “3 FL.NET MODULE INSTALLATION.” 5.2.3 Tool connection procedure For the tool connection procedure, See “5.4 Installing and Starting Up the System.”...

  • Page 86: Using The Fl.net Module

    5.3 Using the FL.NET Module 5.3.1 Link parameter setup procedure The link parameters are used to set up the FL.NET module common memory area for each node. Use the setup tool named [S10V FL.NET SYSTEM] to perform link parameter setup. The self- node setup screen is shown below.
  • Page 87 For detailed procedure descriptions, See “5.5 Operating Method.” Note 1: If the minimum frame interval is set to “0”, it will be automatically changed to its minimum value used with each of the FL.NET module and other FL-net compliant modules connected to the FL-net network.
  • Page 88 5 USER GUIDE Example: When the following link parameter settings are employed, the FL-net module operates as indicated below: Node number Node number Area 1 address : 0x000 Area 1 address : 0x000 Area 1 words : 0x000 Area 1 words : 0x000 Area 2 address : 0x0000...

  • Page 89: Lpu Memory Allocation Procedure

    5 USER GUIDE 5.3.2 LPU memory allocation procedure The FL.NET module allocates the common memory area in the LPU memory. The data received by the FL.NET module is transferred to the resulting LPU memory. LPU memory FL.NET module internal memory...
  • Page 90 5 USER GUIDE Table 5-6 shows the addresses that are available for common memory area allocation in the LPU memory. Table 5-6 Address Ranges for Common Memory Area Allocation in LPU Memory Selectable register/address Remarks XW000 to XWFF0 External input YW000 to YWFF0 External output JW000 to JWFF0...

  • Page 91: Figure 5-34 Self-Node Lpu Memory Allocation Window

    5 USER GUIDE (1) Allocating the self-node LPU memory With the setup tool named [S10V FL.NET SYSTEM], open the [self-node information] window. In the “PCs allocment” section, enter the addresses for the PI/O to be allocated as the self-node LPU memory area. After completion of input, click the Write button.
  • Page 92 5 USER GUIDE Note 1: The area 1 word count (area 2 word count) for PCs allocation is the same as the link parameter area 1 word count (area 2 word count). Note 2: The allocation address setting for the self-node LPU memory must not be a duplicate of any one of those for the other nodes.

  • Page 93: Figure 5-35 Common Memory Area Setup Window For Other Participating Nodes

    5 USER GUIDE (2) Setting the LPU memory area for the other nodes Perform reception setup for the other nodes with the setup tool named [S10V FL.NET SYSTEM]. The data received from various nodes are transferred to the area allocated in the LPU memory.
  • Page 94 LPU memory area word count setting. If any node is left without being set, the FL.NET module cannot transfer to the S10V the data received from that node into the common memory.

  • Page 95: Figure 5-36 Setup Window For Setting Various Status Flag Areas For The Self-Node

    (3) Referencing the self-node status and FA link status The self-node status/FA link status of the FL.NET module, the FA link status of each node, and a higher layer status flag can be referenced with the setup tool named [S10V FL.NET SYSTEM].
  • Page 96 When the FA link status area is set up, the FA link status flag for the self-node is transferred to the low-order byte of the specified area. If the area for self-node status or FA link status information is not specified, the FL.NET module cannot transfer the status information to the S10V. 5-41...
  • Page 97 5 USER GUIDE To set up the FA link status/higher layer flag area, use the setup window for the other nodes reception setup. Shows the self-node number area setup. Make an entry specifying the FA link status transfer area for each node. Make an entry specifying the higher layer status transfer...

  • Page 98: Using Bit Data

    FA link status of that node to the S10V. 5.3.3 Using bit data The FL.NET module subjects the common memory area 1 data to bit conversion at the time of transmission/reception. Example: 1-word data of area 1...

  • Page 99: Using Word Data

    When a transparent message is received, use a C mode program or mathematical/logical function to fetch it from the FL.NET module. If the FL.NET module is filled with transparent messages, it may not be able to process any more request messages.
  • Page 100 (a) Message transmission request by C mode handler A C mode handler is called as a C function. It issues a message request to the FL.NET module to exchange data in place of a user program. Various C mode handlers are available for use with all message types.

  • Page 101: Table 5-7 C Mode Handler List

    /DE0100 Issues a communication log clear request. mesret( ) /D60120 /DE0120 Issues a message return request. Issues a specified-task control request (Hitachi’s unique reqmacro( ) /D60140 /DE0140 transparent type of support). Issues a transparent message reception request (Hitachi’s toukaread( ) /D60160 /DE0160 unique transparent type of support).
  • Page 102 FL.NET module and then terminates the processing. After receipt of a request, the FL.NET module sets the “user request processing in progress” bit in the self-node status flag, and resets it at the end of the processing.

  • Page 103: Table 5-8 Mathematical/Logical Function List

    Issues various message transmission requests. Create a ladder program with the mathematical/logical function for the FL.NET module. Write a request parameter at an address specified for the mathematical/logical function and then execute the mathematical/logical function.
  • Page 104 Note: For bit allocation for the self-node status flag, see “5.3.6 Using the management tables.” NOTICE When issuing a request to the FL.NET module, do not simultaneously use the C mode handler and mathematical/logical function. You cannot specify an index in a parameter (PI/O address.) (4) Transparent message reception The figure below outlines the operation performed for transparent messages.
  • Page 105 If the registered task is not released, however, it does not start. When a transparent receiving flag is set for the FL.NET module, a 16-word area beginning with the associated selected address is used as a transparent-type reception flag area.
  • Page 106 5 USER GUIDE Enter the settings for the transparent reception task and transparent reception task’s factor. Enter the starting address for the transparent receiving flag area. Figure 5-39 Transparent Receiving Flag Area and Transparent Reception Task Setup Window The table below shows the acceptable input ranges for the setup items. Input item Description Acceptable setting range...

  • Page 107: Table 5-9 Transparent Receiving Flag Allocation

    5 USER GUIDE Table 5-9 shows the bit allocation for the transparent receiving flag area. Table 5-9 Transparent Receiving Flag Allocation Bit number Address 0x0000 0x0002 0x0004 0x0006 0x0008 0x000A 0x000C 0x000E 0x0010 0x0012 0x0014 0x0016 0x0018 0x001A 208 0x001C 0x001E The numerical values in the above table represent transmission source node numbers for transparent messages.
  • Page 108 5 USER GUIDE (5) Parameters for various message requests The rest of this section describes the parameters that the C mode handler and mathematical/logical function use to issue various message requests. Word block read request: wordrd( ) [Linking procedure] C language Main Struct wordr_p { Struct wordr_p {...
  • Page 109 5 USER GUIDE [Parameters] : Input parameter storage starting address padr Struct wordr_p { : Remote node number (1 to 254) long node ; : Error code storage address unsigned short *Erradr ; : Read data storage address unsigned short *Setadr ; : Virtual address long Readadr ;...
  • Page 110 When a response code is received, the data is transferred to a read data storage address. • The virtual address varies from one FL.NET module to another. For the virtual address specifications for the FL.NET module, see “Table 2-4 Virtual Address Space and Physical Memory.”...
  • Page 111 5 USER GUIDE Word block write request: wordwt( ) [Linking procedure] C language Main Struct wordw_p { Struct wordw_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; unsigned short *Setadr ; unsigned short *Setadr ; long writeadr ;...
  • Page 112 • A word block write request using the specified virtual address, virtual size, and data at the write data storage address will be issued to a remote node. • The virtual address varies from one FL.NET module to another. For the virtual address specifications for the FL.NET module, see “Table 2-4 Virtual Address Space and Physical Memory.”...
  • Page 113 5 USER GUIDE Network parameter read request: parard( ) [Linking procedure] C language Main Struct parar_p { Struct parar_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; unsigned char *Setadr ; unsigned char *Setadr ; ～...
  • Page 114 5 USER GUIDE Parameter Input range Message transmission service 5 (only when a mathematical/logical function number is used) Remote node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the CMU. Read parameter data storage address (*) For the relationship between real address on LPU (memory address) and symbol name such as XW000, see “Table 2-5 Virtual Address Spare and Symbol Names.”...
  • Page 115 5 USER GUIDE [Function] A network parameter read request will be issued to a remote node. When a response code is received, the network parameter information about the specified node transfers to the read parameter data storage address. The data transfers to the read parameter data storage address in the format shown below. The node number does not transfer to the S10V.
  • Page 116 5 USER GUIDE Network parameter write request: parawt( ) [Linking procedure] C language Main Struct paraw_p { Struct paraw_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; unsigned char *Dataadr ; unsigned char *DataPadr ; ～...
  • Page 117 5 USER GUIDE Parameter Input range Message transmission service 6 (only when a mathematical/logical function number is used) Remote node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the LPU. (*) Write parameter data storage address (*) For the relationship between real address on LPU (memory address) and symbol name such as XW000, see “Table 2-5 Virtual Address Spare and Symbol Names.”...
  • Page 118 5 USER GUIDE [Write parameter data structure] (contiguous areas) Create the data as shown below in the area specified by the write parameter data storage address. 1. When rewriting the common memory address and common memory size only Write “1”. Parameter selection flag (2-byte) Common memory 1 address (2-byte) Common memory 1 size (2-byte)
  • Page 119 When rewriting the network parameters, take extreme care not to cause any setting duplication to the common memory. The server feature of the FL.NET module returns an abnormal response if, upon reception of a network parameter write request, the parameter selection flag is found to be not between 1 and 3.
  • Page 120 A stop request will be issued to a remote node. NOTICE The FL.NET module does not support the server feature for a stop directive. If a stop request is issued to the FL.NET module, it returns a response to indicate that it does not support the stop directive.
  • Page 121 5 USER GUIDE Run request: reqrun( ) [Linking procedure] C language Main Struct reqr_p { Struct reqr_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; ～ ～ long (*ReqRun)( ) ; long (*ReqRun)( ) ; long rtn ;...
  • Page 122 A run request will be issued to a remote node. NOTICE The FL.NET module does not support the server feature for a run directive. If a run request is issued to the FL.NET module, it returns a response to indicate that it does not support the run directive.
  • Page 123 5 USER GUIDE Profile read The FL.NET module does not support the client feature of profile read for another node. However, it responds to a request from another node. The FL.NET module’s response to a profile read request from another node is indicated...
  • Page 124 5 USER GUIDE Communication log data read request: logrd( ) [Linking procedure] C language Main Struct logr_p { Struct logr_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; unsigned char *logadr ; unsigned char *logadr ; ～...
  • Page 125 5 USER GUIDE [Parameters] : Input parameter storage starting address padr Struct logr_p { : Remote node number (1 to 254) long node ; : Error code storage address unsigned short *Erradr ; : Log data storage address unsigned char *logadr ; Be sure to specify an even-numbered address in padr.
  • Page 126 5 USER GUIDE Communication log data clear request: logclr( ) [Linking procedure] C language Main Struct logclr_p { Struct logclr_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; ～ ～ long (*Logclr)( ) ; long (*Logclr)( ) ;...
  • Page 127 5 USER GUIDE Parameter Input range Message transmission service 11 (only when a mathematical/logical function number is used) Remote node number 1 to 255 Error code storage address Specify a real address (even-numbered address) on the LPU. (*) (*) For the relationship between real address on LPU (memory address) and symbol name such as XW000, see “Table 2-5 Virtual Address Spare and Symbol Names.”...
  • Page 128 5 USER GUIDE Message return request: mesret( ) [Linking procedure] C language Main Struct mesreq_p { Struct mesreq_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; unsigned char *SendData ; unsigned char *SendData ; long Sendsiz ;...
  • Page 129 5 USER GUIDE [Parameters] : Input parameter storage starting address padr Struct mesreq_p { : Remote node number (1 to 254) long node ; : Error code storage address unsigned short *Erradr ; : Message data storage starting address unsigned char *SendData ; : Message data size (1 to 1,024) long Sendsiz ;...
  • Page 130 5 USER GUIDE [Function] • A message return request using the data at the message data storage starting address will be issued to a remote node. When a response message returns, the message data within the response code transfers to the return message storage address. •...
  • Page 131 5 USER GUIDE Specified task control request (Hitachi’s unique transparent type of support): reqmacro( ) [Operation performed] Exercises control (abort/release/queue) over a user-specified task number. [Linking procedure] C language Main Struct Reqmacro_p { Struct Reqmacro_p { long node long node unsigned short *Erradr ;...
  • Page 132 5 USER GUIDE [Parameters] : Input parameter storage starting address padr Struct Reqmacro_p { : Remote node number (1 to 254) long node ; : Error code storage address unsigned short *Erradr ; : CPMS macro execution result storage address unsigned long *Retdadr ;...
  • Page 133 5 USER GUIDE [Function] A task abort, release, or queue execution request can be issued to a remote node. When a response message is received, the task control execution result (log value) is written at the CPMS macro execution result storage address. Specify the parameters as indicated below: ...
  • Page 134 5 USER GUIDE Transparent message reception request (Hitachi’s unique transparent type of support): toukaread( ) [Linking procedure] C language Main Struct ToukaRead_p { Struct ToukaRead_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ;...
  • Page 135 5 USER GUIDE Parameter Input range Message transmission service 17 (only when a mathematical/logical function number is used) Reception destination node 0 to 254 number Error code storage address Specify a real address (even-numbered address) on the LPU. (*) Reception data storage address Data word count 0 to 1,024 (variable in 1-byte units) (*) For the relationship between real address on LPU (memory address) and symbol...
  • Page 136 5 USER GUIDE [Function] • Reception word count will be transferred to the area which is specified received transparent message by reception data storage address • If there is no transparent message from a reception destination node number, a parameter error occurs.
  • Page 137 5 USER GUIDE FL.NET module’s unique feature When the received transparent message TCD number is between 0 and 999, the reception message data is handled as word data in little-endian format. However, if the reception message data word count is expressed by an odd number of bytes, the data does not convert normally into little-endian format.
  • Page 138 5 USER GUIDE Transparent message transmission request (Hitachi’s unique transparent type of support): toukasend( ) [Linking procedure] C language Main Struct ToukaSend_p { Struct ToukaSend_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ;...
  • Page 139 5 USER GUIDE Parameter Input range Message transmission service 18 (only when a mathematical/logical function number is used) Transmission destination node 1 to 255 number Error code storage address Specify a real address (even-numbered Transmission data storage address) on the LPU. (*) address Data word count 0 to 1,024 (specified in bytes)
  • Page 140 1000, 1001, 1200, 1201 FL.NET module-unique feature When a TCD number between 0 and 999 is specified, the transmission data is sent as data in little-endian format. If the transmission word count is expressed by an odd number of bytes, the transmission data is converted into little-endian format with the 1-byte data “0x00”...
  • Page 141 5 USER GUIDE Common memory offset feature: comoffset( ) [Operation performed] When this handler is executed, the starting address for data transfer is set at a position that is shifted by a specified offset amount from the beginning of a specified node’s common memory area.
  • Page 142 5 USER GUIDE When an offset is specified Common memory area 2 address: 0x0020 Common memory area 2 word count: 0x0030 PCs memory address: FW000 PCs memory word count: 5 Offset size: 0x10 Common memory PCs memory area 2 0x0000 FW000 Offset FW005...
  • Page 143 5 USER GUIDE [Linking procedure] C language Main Struct CommonOffset_p { Struct CommonOffset_p { long node ; long node ; unsigned short *Erradr ; unsigned short *Erradr ; unsigned long com1offset ; unsigned long com1offset ; unsigned long com2offset ; unsigned long com2offset ;...
  • Page 144 5 USER GUIDE Parameter Input range Message transmission service 19 (only when a mathematical/logical function number is used) Specified node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the LPU. (*) Common memory area 1 offset 0 to 0x1FF (variable in 1-word units) size Common memory area 2 offset...
  • Page 145 When an offset size is specified for a specific node number, it is stored in memory until the FL.NET module is turned OFF or reset. Note, however, that the user cannot reference the offset setting within the FL.NET module after completion of offset setup.
  • Page 146 5 USER GUIDE (6) Program examples Program examples are shown below. These examples permit two units of the FL.NET module to transmit/receive transparent messages. (a) Transmission/reception by C mode handler [System configuration] Power supply Power supply LPU + CMU LPU + CMU FL.NET...
  • Page 147 5 USER GUIDE [FL.NET module settings] The FL.NET module settings for LPU/CMU01 and LPU/CMU02 are shown below: Self-node settings for the FL.NET modules Setup item LPU/CMU01 setting LPU/CMU02 setting Node number Area 1 address (setting) 0x000 0x004 Area 1 words...
  • Page 148 [Program structure] The program structure is shown below. With the module having the node number 1 (FL.NET module for LPU/CMU01) and the module having the node number 2 (FL.NET module for LPU/CMU02) interconnected, cyclic transfer operations are performed between the FL-net modules. (The FL.NET modules perform cyclic transfer operations.
  • Page 149 5 USER GUIDE [LPU/CMU01-side program flowchart] START ① Has node 1 participated in the network? Yes (cyclic transmission started) ② Transmission of a transparent message toukasend ③ Abnormal Return code? Normal ④ Self-node status check Transparent-message Transparent-message transmission in transmission ended progress ①...
  • Page 150 5 USER GUIDE [LPU/CMU01-side C program example] /* toukasend() starting address (main) */ #define TOUKA_SEND 0xD60180L #define SBUFADR 0x450000L /* Transmission buffer address */ /* Input parameter storage starting address */ #define PARADDR 0x452000L /* Self-node status transfer area (RW080) */ #define RW080 0x0E0C10L /* Transparent-message transmission error code area */...
  • Page 151 5 USER GUIDE [LPU/CMU02 side program flowchart] START ① No transparent message received Data received from node 1? Transparent message received ② Transparent-message reception toukaread ③ Abnormal Return code? Normal ④ Self-node status check Transparent-message Transparent-message reception in progress reception ended ①...
  • Page 152 5 USER GUIDE [LPU/CMU02-side C program example] /* toukaread() starting address (main) */ #define TOUKA_READ 0xD60160L /* Reception buffer address */ #define RBUFADR 0x450000L /* Input parameter storage starting address */ #define PARADDR 0x452000L /* Self-node status transfer area (RW080) */ #define RW080 0x0E0C10L /* Transparent-message transmission error code area */...
  • Page 153 IP address: 192.168.250.002 192.168.250.001 S10V (LPU01) S10V (LPU02) Twisted-pair Twisted-pair cable cable Ensure that the FL.NET module MAIN/SUB selector switches for LPU01 and LPU02 are set to 0. System component list Product name Model Quantity Remarks Power supply LQV000 LQP510 FL.NET...
  • Page 154 5 USER GUIDE [FL.NET module settings] The FL.NET module settings for LPU01 and LPU02 are shown below: Self-node settings for the FL.NET modules Setup item LPU01 setting LPU02 setting Node number Area 1 address (setting) 0x000 0x004 Area 1 words...
  • Page 155 [Program structure] The program structure is shown below. With the module having the node number 1 (FL.NET module for LPU01) and the module having the node number 2 (FL.NET module for LPU02) interconnected, cyclic transfer operations are performed between the FL.NET modules.
  • Page 156 5 USER GUIDE [LPU01 side ladder program] 18 = FL400 V000 R088 R080 R0A0 (00001) 2 = FL402 RW090 = FL404 FW000 = FL406 1024 = FL408 11000 = FL40A FLCM FW400 When the R0A0 turns ON, the program runs and checks the network participation status bit (R088) and user-requested-processing-in-progress bit (R080) in the self-node status flag (message processing can be performed when the network participation status bit is set with the user-requested-processing-in-progress bit reset.)
  • Page 157 The TCD number (11000) is specified for the transparent message to be transmitted. FLCM FW400 The parameter storage address (FW400 real address) is specified for the mathematical/logical function (FLCM). A message request (transparent-message transmission) is issued to the FL.NET module. [LPU02-side ladder program] 17 = FL400 R101...
  • Page 158 The parameter storage address (FW400 real address) is specified for the mathematical/logical function (FLCM). A message request (transparent-message transmission) is issued to the FL.NET module. Note: The ladder program examples presented here are created to facilitate understanding. In a practical program, it is necessary to check an error code that is written at an error code storage address after a “user request processing in progress”...

  • Page 159: Using The Management Tables

    You can determine the status of communications with the remote nodes by referencing these management tables. Note, however, that the setup tool named [S10V FL.NET SYSTEM] must be used to reference the management tables within the FL.NET module. For details on the procedures to be performed from various windows, See “5.5 Operating Method.”...

  • Page 160: Figure 5-41 Self-Node Information (Self-Node Management Table) Window

    5 USER GUIDE Flags enter in the specified areas A flag indicating the higher to indicate the FA link status and layer enters here. For the self-node status. For the contents of the flag, see the contents of the flags, see the next or a subsequent page.
  • Page 161 5 USER GUIDE [Contents of self-node status flag] In the FL.NET module, the bit allocation for the self-node status flag is as indicated below: Bits Valid bit Token hold timeout (Token monitoring time error flag) =0: A token hold timeout has not occurred.
  • Page 162 5 USER GUIDE [Contents of FA link status flag (FA link status)] The bit allocation for the FA link status flag is as indicated below: Bits Valid bit Participation status bit (Participation leaving flag) =0: The self-node has not participated in the network. =1: The self-node has participated in the network.
  • Page 163 (WARNING state). The cyclic data and message data are not guaranteed. When a higher-layer error occurs, the FL.NET module turns ON (sets) bits 2 and 2 Higher-layer operation status bit (RUN/STOP) =0: The higher layer (S10V) is halted (in the STOP state).
  • Page 164 Note, however, that the setup tool [S10V FL.NET SYSTEM] merely allows you to view the contents of the participating node management table concerning the nodes that have participated in the network.

  • Page 165: Figure 5-43 Participating Other Node Link Information Window

    (3) Referencing the network management table The network status window of the setup tool [S10V FL.NET SYSTEM] allows you to view the contents of the network management table. Figure 5-44 Network Status (Network Management Table) Window...

  • Page 166: Fl.net Module Communication Performance

    Refresh cycle measurement time (minimum) 5.3.7 FL.NET module communication performance The method of calculating the communication performance of the FL-NET module is shown below. However, the method varies depending on the destination of the connection and number of words.
  • Page 167 5 USER GUIDE Token hold time (ms): Token holding time of the self-node Token hold time = 1.1 + 0.001 × S + 0.001 × R + (MFT + 0.2) × F + MFT Refresh cycle time (ms): Sum of the token hold time values of all the nodes. Refresh cycle time = 1.1 ×...

  • Page 168: Using The Communication Log

    5 USER GUIDE 5.3.8 Using the communication log With the setup tool [S10V FL.NET SYSTEM], you can view the RAS information (communication log) maintained in the FL.NET module. Figure 5-45 [RAS Information] Dialog Box 5-113...
  • Page 169 5 USER GUIDE The table below describes the on-screen log information (RAS information). Item On-screen information description Log about Transmission Number of frames whose transmissions were requested transmission Transmitting error below socket Number of transmission errors in the socket section and reception Transmitting error of Ethernet Unused...

  • Page 170: Installing And Starting Up The System

    5.4 Installing and Starting Up the System 5.4.1 Installing To install the S10V FL.NET, you must execute the setup program that is stored in the S10V FL.NET DISK1 folder on the CD. Double-click “setup.exe” that is stored in the DISK1 folder on the S10V FL.NET system CD.
  • Page 171 Administrator account first created in the initial condition of your personal computer. When you have so logged on, you can then double-click “setup.exe” that is stored in the DISK 1 folder on the S10V FL.NET System CD. When “setup.exe” is started, the dialog box as shown below will appear. Click the button to continue the execution of the setup program.

  • Page 172: Uninstalling

    5 USER GUIDE 5.4.2 Uninstalling The existing FL.NET System needs to be uninstalled when, for instance, you want to upgrade it. The procedure required for uninstalling it is as follows: (1) Uninstalling from Windows® 2000 Click on Start button on your Windows desktop and choose [Settings] – [Control Panel].

  • Page 173: Starting Up The System

    S10V FL.NET system startup procedure to start it up in online mode (1) To start up the S10V FL.NET system from the Windows® desk top, double-click the “S10V FL.NET SYSTEM” icon. The S10V FL.NET system can also be started up from Start button.

  • Page 174: Figure 5-47 The [Communication Type] Window

    To send the setup information file prepared this way to the target machine, first put the FL.NET system into online mode and then send it by choosing [Main] – [Send setups], or [Sub] – [Send setups], from the [Module] menu.

  • Page 175: Changing Connections

    5.4.4 Changing connections Function: Set the communication type between the PCs and the PC. Operation: The procedure is shown below. (1) From the [Tool] menu of the [[S10V] FL.NET] window, click the Change connection button. (2) The [Communication type] window is displayed.

  • Page 176: Selecting An Edition File

    File Select] from the [Tool] menu. The [Open] window as shown below will then appear. Figure 5-49 The [Open] Window -- an Example (3) If you want to create an FL.NET setup information file and edit its content, enter a non- existing file name into the “File name” box and click the Open button.

  • Page 177: Closing The System

    5 USER GUIDE Figure 5-50 The [Create confirmation] Dialog Box (4) If you want to edit an already created FL.NET setup information file, choose it in the [Open] window. Then, the “PCs number” (in decimal), “PCs type” (in hexadecimal), and other information will be displayed.

  • Page 178: Operating Method

    And monitor the FL.NET module information. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [[S10V] FL.NET] window. (2) Select the [Setup] menu. (3) The [Setup self-node] icon (red) and [Other-node setup tran…] icon (blue) are displayed.
  • Page 179 Upon completion of the writing, the FL.NET module will automatically join the network again according to the written parameters. (7) If the FL.NET system is running in online mode, you can also take any of the following actions:...

  • Page 180: Other Nodes Display

    For using this function, it is a prerequisite that the PCs is connected with the PC by cable. Operation: The procedure is shown below. (1) When the FL.NET system is running in online mode, click the Display node data button in the [[Online] Self-node information] or [Other node information] window (see Subsection 5.5.4).

  • Page 181: Other Nodes Reception Setup

    Function: Set other nodes PCs allocation. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [[S10V] FL.NET] window. (2) Select the [Setup] menu. (3) The [Setup self-node] icon (red) and [Other-node Setup tran…] icon (blue) are displayed.

  • Page 182: Joining Other Nodes Information

    For using this function, it is a prerequisite that the PCs is connected with the PC by cable. Operation: The procedure is shown below. (1) When the FL.NET system is running in online mode, choose [Main] or [Sub] from the [Module] menu in the [[S10V] FL.NET] window.
  • Page 183 After completing the setup, click the button. To cancel the setup, click the Cancel button. Clicking the button causes the FL.NET module to automatically leave from the network to write the data. After writing the data, the FL.NET module joins the network automatically. 5-128...

  • Page 184: Network Status

    For using this function, it is a prerequisite that the PCs is connected with the PC by cable. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [[S10V] FL.NET] window. (2) Select the [Network] menu.

  • Page 185: Node Setting List

    For using this function, it is a prerequisite that the PCs is connected with the PC by cable. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [[S10V] FL.NET] window. (2) Select the [RAS information] menu.

  • Page 186: Saving Setups

    For using this function, it is a prerequisite that the PCs is connected with the PC by cable. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [[S10V] FL.NET] window. (2) Select the [Save setups] menu.

  • Page 187: Sending Setups

    5.5.9 Sending setups Function: Load the self-node setup, PCs allocation of all nodes, and IP address and subnet mask of the FL.NET module, which were saves on the PC by the saving function, onto the PCs. For using this function, it is a prerequisite that the PCs is connected with the PC by cable.
  • Page 188 5 USER GUIDE (2) Select the [Send setups] menu. (3) The [Open] window is displayed. Enter the file name. (4) When the file is specified, click the Send button to send it to the programmable controller. If you want to cancel this function, click the Cancel button.

  • Page 189: Setup Ip Address

    Function: Set the IP address of the FL.NET module. For using this function, it is a prerequisite that the PCs is connected with the PC by cable. Note: Setting the IP address or subnet mask for the FL.NET module resets the programmable controller automatically.
  • Page 190 Function: Set the IP address of the FL.NET module. Operation: The procedure is shown below. (1) Select [IP address] from the [Module] menu of the [[S10V] FL.NET] window. (2) The [[Offline] Setup IP address] window is displayed. Enter the IP address and subnet mask.

  • Page 191: Printing

    1) the setup information for a selected module from the actual target machine if the FL.NET system is running in online mode; or 2) the content (setup information) of a selected file if it is running in offline mode.
  • Page 192 5 USER GUIDE 5-137...

  • Page 193: Csv Output

    1) the setup information for a selected module from the actual target machine if the FL.NET system is running in online mode; or 2) the content (setup information) of a selected file if it is running in offline mode.
  • Page 194 5 USER GUIDE FL.NET 2006/10/19 20:28:50 File Name=C:\aaa\Settings\FL_main.pse Main Module IP address=101.102.103.104 Subnet mask=255.0.0.0 **Self-node information** Node No,2 Area1 addr,0x110 Area1 words,0x008 Area2 addr,0x1000 Area2 words,0x0008 Minimum frame interval ,0 Node name,node567890 PCs allocment Node No,FW010...
  • Page 195 This Page Intentionally Left Blank...

  • Page 196: Maintenance

    6 MAINTENANCE...

  • Page 197: Maintenance And Inspection

    6 MAINTENANCE 6.1 Maintenance and Inspection To keep the module running in optimal condition, it requires checks. Make checks daily or periodically (twice a year or more often). Table 6-1 Maintenance and Inspection Items Item Point to check Module appearance Check the module case for cracks, flaws and other defects.

  • Page 198: Replacing Or Adding On The Module

    ③ Connect the personal computer and the LPU module together with the RS-232C cable. ④ Start the S10V FL.NET SYSTEM and save the existing settings to a dedicated file, called an FL.NET setup information file (see “5.5.8 Saving setups” for details). If the existing settings are not accessible for some reason, skip this step and use item ④...
  • Page 199 Step ①. ⑧ Turn on the power supply of the controller unit and send to the new FL.NET module the FL.NET setup information file that you have saved in Step ④ (see “5.5.9 Sending setups”...

  • Page 200: Troubleshooting

    7 TROUBLESHOOTING...

  • Page 201: Procedure

    7 TROUBLESHOOTING 7.1 Troubleshooting 7.1.1 Procedure Trouble occurred. Check the trouble according to “7.1.2 Trouble detection and solution.” Is each item executed correctly? Correct if the item is not executed correctly. Returned normally? Verify it with the error LED and the Tool’s display, and take a necessary action.

  • Page 202: Trouble Detection And Solution

    7 TROUBLESHOOTING 7.1.2 Trouble detection and solution (1) Is the cabling correct? Check cables for disconnection or incorrect connection. (2) Are the modules mounted correctly? Check that no set screws loosen. Check if a model LQE702 module is intermixed with a model LQE500/LQE502/LQE701 module among the same series of similar modules installed.

  • Page 203: Network Problems And Repairing

    7 TROUBLESHOOTING 7.2 Network Problems and Repairing (1) Network problems and remedies (concerning unstable communications) Table 7-1 Network Problems and Repairing (Concerning Unstable Communications) Inspection Problem Inspection procedure Remedy item Communi- Transmission Check that all the stations properly Check the power supplies and cables of cation cannot path respond to the Ping command.
  • Page 204 7 TROUBLESHOOTING (2) Checking the IP address with the personal computer’s “ping feature” The connection and IP address setting for the target FL-net device can be checked without using the FL-net network analyzer or any other special tool. Such a check can also be conducted with the “Ping feature”...

  • Page 205: Precautions For Fl-Net Use

    7 TROUBLESHOOTING 7.3 Precautions for FL-net Use For the FL-net transmission path requirements, see the aforementioned section or IEEE802.3 standard. In addition to such requirements, you must observe the FL-net-specific precautions. • Ensure that no other Ethernet communication data flows along the FL-net communication cable. •...

  • Page 206: Error Indications And Countermeasures

    MODULES (manual number SVE-1-100).” [FA protocol errors] When an error stated in the FA protocol is detected during an FL.NET module operation, the LPU unit module shows a error code as recorded in Table 7-2. The FL.NET module may stop running in compliance with the FA protocol, depending on the contents of the displayed message.

  • Page 207: Table 7-2 Error Messages

    7 TROUBLESHOOTING Table 7-2 Error Messages (1/2) No. Error code Error message Meaning Required recovery action 3621 Program error (Invalid Data Access) Data access error – Turned on Hardware item replacement (Turned off) 3661 Program error (Data Access Protection) Data access protection error –...
  • Page 208 I/O error (IPADDR_DUPL) Duplicated-IP address error – Turned on Review the settings made. (*4) 0200 Network participation not completed. The FL.NET module currently not Turned on – Connect it to the network. participating in the network 0201 Duplicate common memory settings The local node’s common memory...
  • Page 209 100M LINK LED indicator, which indicates that a “link not established yet” condition exists. The LSI carrier loss also occurs when, after the startup of the LPU, a total of 32 send requests are issued by an FL.NET system program before the 100M LINK LED indicator comes on.

  • Page 210: Table 7-3 List Of Detectable Codes

    [Code table of errors that can be detected by C mode handler and mathematical/logical function] Table 7-3 shows error codes and remedies concerning the errors that may occur when the C mode handler or mathematical/logical function issues a request to the FL.NET module. Table 7-3 List of Detectable Codes (1/2) Error...
  • Page 211 7 TROUBLESHOOTING Table 7-3 List of Detectable Codes (2/2) Error Description Cause Remedy code 0xFE08 ACK reception An ACK response returned from a It is conceivable that the module may sequence number error specified node number reported a be defective. Replace the module. sequence number error.

  • Page 212: Figure 7-2 Module Error Lamp

    7 TROUBLESHOOTING (3) Module error indications When an error occurs in the FL.NET module, the LER LED or ERR LED on the module turns ON or blinking. LQE702 FL.NET LER LED ERR LED 100MLINK Figure 7-2 Module Error Lamp Note that the LER LED turns ON even when the module has not participated in the network.
  • Page 213 This Page Intentionally Left Blank...

  • Page 214: Appendixes

    8 APPENDIXES...

  • Page 215: Network System Definitions

    8 APPENDIXES 8.1 Network System Definitions 8.1.1 Standard compliance of communication protocol A communication protocol is a set of rules (communication regulations) to enable a system to exchange information with another system through a communications link. The communication protocols adopted by the FL-net comply with the following standards: Table 8-1 FL-net Communication Protocols FL-net communication protocol Standard complied with...

  • Page 216: Fl-Net Physical Layer

    8 APPENDIXES 8.1.3 FL-net physical layer For a transmission speed of 100 Mbps, the Ethernet physical layer offers five different transmission methods: 100BASE-TX, 100BASE-FX, 100BASE-T, 100BASE-T2, and 10BASE- The FL-net adopts 100BASE-TX. 8.1.4 IP address An address named “IP address (INET address)” is used to differentiate a specified communication device from many other communication devices connected to Ethernet.

  • Page 217: Subnet Mask

    The FL-net uses UDP. The reason is that TCP’s complicated data verification/retransmission procedure is redundant for the FL.NET. The FL-net provides an increased data exchange speed by skipping such a complicated procedure and having the FL-net protocol layer on a higher level perform token-based transmission right management, multiple-frame division/synthesis, and other relevant processes.

  • Page 218: Fl-Net Data Format

    8 APPENDIXES 8.1.8 FL-net data format (1) FL-net data format overview The data transmitted/received by the FL-net is capsuled in each communication protocol layer as indicated below: 1,024 bytes maximum User data User data FL-net header UDP header FL-net data UDP segment IP header UDP header...

  • Page 219: Figure 8-4 Fl-Net Data (One-Frame) Example

    8 APPENDIXES FL-net data (one-frame) observable over a communications line is indicated in the example below. In this example, 128-byte cyclic data is transferred. IP header Ethernet header FL-net header UDP header ADDR ASCII 0000 FF FF FF FF FF FF 08 00 19 10 00 07 08 00 45 00 ....E. 0010 00 E4 EB 59 00 00 80 11 D8 52 C0 A8 FA 0B C0 A8 ...Y..R..

  • Page 220: Fl-Net Transaction Codes

    8 APPENDIXES (2) FL-net header format The FL-net header consists of 64 or 96 bytes. 64 to 96 bytes 1,024 bytes maximum FL-net header Cyclic/message data Lower layer header FA link data 1,500 bytes maximum Figure 8-5 FL-net Header The FL-net header is attached to the beginning of every frame related to the FL-net protocol. 8.1.9 FL-net transaction codes The FL-net offers the following message transmission services: •...

  • Page 221: Table 8-4 List Of Transaction Codes

    8 APPENDIXES The header of each message contains a request transaction code or response transaction code (TCD) that provides message frame identification. Table 8-4 List of Transaction Codes Transaction code Description 0 to 9999 Reserve 10000 to 59999 Transparent message 60000 to 64999 Reserve 65000...

  • Page 222: Transaction Code Receive Operation At The Udp Port

    8 APPENDIXES 8.1.10 Transaction code receive operation at the UDP port The following table shows the operations matched to the transaction codes upon receipt of frames at the UDP port defined in FL-net. Table 8-5 Transaction Code Receives Processing at the UDP Port For token frame or cyclic For trigger frame or For message frame...

  • Page 223: Fl-Net Network Management

    8 APPENDIXES 8.2 FL-net Network Management 8.2.1 FL-net token management (1) Token Under normal conditions, a node can transmit data while it holds the token. A node without the token can transmit only two items: a token reissue request in the event of a token monitoring timeout and an enter request frame for situations where network enter is not completed.
  • Page 224 8 APPENDIXES (2) Flow of token Basically, only one token exists within the network. If two or more tokens should exist within the network, the one having the lowest destination node number takes precedence with the others discarded. A frame having a token (token frame) has a token’s destination node number and a token transmission node number.

  • Page 225: Table 8-6 Token And Data

    8 APPENDIXES (3) Token and data The following six different data patterns are used for token transmission: Table 8-6 Token and Data Pattern Description When no data is involved Only the token is transmitted. Token When only cyclic data is transmitted A token is transmitted after cyclic data is transmitted.

  • Page 226: Entering In/Leaving From Fl-Net

    8 APPENDIXES 8.2.2 Entering in/leaving from FL-net (1) Entering in FL-net When a node starts up, it monitors the line until an enter token detection timeout occurs. If it does not receive the token in this instance, it concludes that the network startup process is in progress, and then newly participates in the network.
  • Page 227 8 APPENDIXES Trigger Enter request Token Node monitoring started frame (when the power is turned ON or a reset is performed) Node 1 Enter token detection time (3 s) Node 2 Node 3 Enter request frame transmission wait time (node number × 4 ms) Node 254 Enter request frame reception wait time (1.2 s)
  • Page 228 8 APPENDIXES Enter token detection time: Period of time for checking whether the network is operating. Round: Rounds are determined with respect to the time at which the token addressed to the lowest node number is received. Enter request frame transmission wait time: A enter request frame transmission takes place after an elapse of [self-node number ×...

  • Page 229: Node Status Management

    8 APPENDIXES 8.2.3 Node status management As outlined in Table 8-7, node status management is exercised with the self-node management table, entering node management table, and network management table. Table 8-7 Node Status Management Table Overview Name Description Self-node management table Manages the self-node settings.

  • Page 230: Fl-Net Entering Node Management Table

    8 APPENDIXES 8.2.5 FL-net entering node management table (1) Basic features The status of nodes that have entered in the network is monitored with the management table that each node has. This table handles on an individual node basis the data about nodes that have entered in the network.

  • Page 231: Fl-Net Status Management

    8 APPENDIXES 8.2.6 FL-net status management (1) Basic feature Provides management of parameters related to network status. (2) Management data Table 8-10 Network Management Table Item Length Description Token maintenance node number 1 byte Node that currently holds the token. Minimum frame interval 1 byte Variable in 100 μs units.

  • Page 232: Table 8-12 Reception Management Data For Message Sequence Number Management

    8 APPENDIXES (3) Reception management data Table 8-12 Reception Management Data for Message Sequence Number Management Item Length Description Sequence number/version number 4 bytes 0x1 to 0xFFFFFFFF Sequence number (One-to-one reception) 4 bytes 0x1 to 0xFFFFFFFF Sequence number (One-to-N reception) 4 bytes 0x1 to 0xFFFFFFFF “0xFFFFFFFF”...

  • Page 233: Fl-Net Profile

    8 APPENDIXES 8.3 FL-net Profile 8.3.1 Device communication information classification In the FL-net, the communications-related information about networked devices is classified into three types as shown in Figure 8-9. Node A: Network parameters (setup (communication information for transmission) facility) B: System parameters •...

  • Page 234: Details Of Common Parameters

    8 APPENDIXES 8.3.2 Details of common parameters Table 8-13 shows the details of common parameters. Table 8-13 Details of Common Parameters Name character string Contents of Data type Parameter name [PrintableString type] parameter [type] (Length), (String) (Length), (Contents) 6, “COMVER” INTEGER Example: 1, 1 Device profile common...

  • Page 235: Details Of Device-Specific Parameters (When Used)

    8 APPENDIXES 8.3.3 Details of device-specific parameters (when used) Table 8-14 Details of Device-Specific Parameters Parameter name Name character string Data type Contents of parameter Device-specific parameter 2, “ID” PrintableString 7, “DEVPARA” identification string The vendor freely defines the contents for each device. 8.3.4 System parameter examples (PLC examples) (1) PLC example of system parameter tabular document notation Table 8-15 System Parameter Tabular Document Notation (PLC Examples)
  • Page 236 8 APPENDIXES (2) Abstract syntax PlcmRecord ::=SEQUENCE syspara SysparaType, plcmpara PlcmType SysparaType::=SEQUENCE nameCOMVER NameType, paraCOMVER INTEGER, nameID NameType, paraID NameType, nameREV NameType, paraREV INTEGER, nameREVDATE NameType, paraREVDATE DateType, nameDVCATEGORY NameType, paraDVCATEGORY NameType, nameVENDOR NameType, paraVENDOR NameType, nameDVMODEL NameType, paraDVMODEL NameType PlcmType::=...
  • Page 237 8 APPENDIXES syspara nameCOMVER “COMVER”, paraCOMVER nameID “ID”, paraID “SYSPARA”, nameREV “REV”, paraREV nameREVDATE “REVDATE”, paraREVDATE year 1998, month nameDVCATEGORY “DVCATEGORY”, paraDVCATEGORY “PLC”, nameVENDOR “VENDOR”, paraVENDOR “MSTC-JOP Electric Corporation”, nameDVMODEL “DVMODEL”, paraDVMODEL “PLC-M” plcmpara nameID “ID”, paraID “DEVPARA”, module nameMODULE “CPU1NAME”,...
  • Page 238 8 APPENDIXES (3) Transfer syntax data array (encoding) Identifier Length Contents $820133 “COMVER” “ID” “SYSPARA” “REV” “REVDATE” $07CE “DVCATEGORY” “PLC” “VENDOR” “MSTC-JOP Electric Corporation” “DVMODEL” “PLC-M” $81B1 “ID” “DEVPARA” “CPU1NAME” “PMSP35-5N” “CPU2NAME” “PMSP25-2N” “CPU3NAME” “PMSP25-2N” “CPU4NAME” “PMBP20-0N” “IO105NAME” “PMWD64-4N” “IO106NAME” “PMLD01-0N”...
  • Page 239 8 APPENDIXES (4) Data arrangement on circuit The sequence of data transmitted over a circuit is shown below. Data transmission begins with address (0) in the relative address 00 column shown below. Data is transmitted, byte by byte, in the order indicated by the horizontal arrow mark. Upon completion of the transmission of the data in the relative address 00 column, the data in the relative address 10 column begins to be transmitted.

  • Page 240: System Parameter Examples (Cnc Examples)

    8 APPENDIXES 8.3.5 System parameter examples (CNC examples) Table 8-16 shows CNC system parameter examples. Table 8-16 System Parameter Tabular Document Notation (CNC Examples) Name character string Contents of Data type Parameter name [PrintableString type] parameter [type] (Length), (String) (Length), (Contents) SysPara Device profile common 6, “COMVER”...
  • Page 241 8 APPENDIXES (1) Abstract syntax CncRecord ::= SEQUENCE SysPara SysParaType, CncPara CncParaType, SysParaType::= SEQUENCE nameCOMVER NameType, paraCOMVER INTEGER, nameID NameType, paraID NameType, nameREV NameType, paraREV INTEGER, nameREVDATE NameType, paraREVDATE DateType, nameDVCATEGORY NameType, paraDVCATEGORY NameType, nameVENDOR NameType, paraVENDOR NameType, nameDVMODEL NameType, paraDVMODEL...
  • Page 242 8 APPENDIXES SysPara nameCOMVER “COMVER”, paraCOMVER nameID “ID”, paraID “SYSPARA”, nameREV “REV”, paraREV nameREVDATE “REVDATE”, paraREVDATE year 1998, month nameDVCATEGORY “DVCATEGORY”, paraDVCATEGORY “CNC”, nameVENDOR “VENDOR”, paraVENDOR “MSTCJ LD”, nameDVMODEL “DVMODEL”, paraDVMODEL “MSTCJ Series 16a” CncPara nameID “ID”, paraID “DEVPARA”, nameMODEL “MODEL”,...
  • Page 243 8 APPENDIXES 8.4 Trouble Report Fill out this form and submit it to local source. Your company name Person in charge Data and time of occurrence (year / month / day / hour / minute) Address Where to make contact Telephone E-mail Model of defective module...

This manual is also suitable for:

Lqe702Lqe702-z

Table of Contents