Page 3 Fourth Edition, December 2006, SVE-1-101(E) (out of print) Fifth Edition, October 2008, SVE-1-101(F) All Rights Reserved, Copyright © 2003, 2008, 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 Be sure to read this manual and all other attached documents carefully before installing, operating inspecting or conducting maintenance on this unit. Always use this unit properly. Be sure to carefully read the information about the device, the safety information and precautions before using this unit.
Page 5 1. Installation Precautions DANGER If an emergency stop circuit, interlock circuit, or similar circuit is to be formulated, it must be positioned external to this module. If you do not observe this precaution, equipment damage or accident may occur when this module becomes defective.
Page 6 CAUTION The degree of temperature rise varies depending on how the module is mounted. The mounting intervals specified in the manual should be used as a guide only. While a test run is conducted after completion of mounting, measure the temperature near the module to check whether it is within the specified range.
Page 7 REQUIREMENT Fasten the mount base to a vertical surface. Fastening the mount base to a horizontal surface lessens the heat dissipation effects and allows the temperature to rise, thereby rendering the module defective or incurring component parts deterioration. Before installing the module, discharge any static buildup from your body because static electricity may render the module defective.
Page 8 2. Wiring Precautions DANGER Electric shock hazards exist so that you might suffer burns or become electrocuted. Further, the system might malfunction due to noise interference. Therefore, ground the line ground (LG), frame ground (FG), and shield wire (SHD). REQUIREMENT Insulate the mount base from the enclosure.
Page 9 REQUIREMENT To provide protection against short circuit, furnish the external power source with a fuse or circuit protector. Ensure that the employed circuit protector is rated as specified. Before supplying power to the equipment, thoroughly check the wiring connections. Before making power supply wiring connections, make sure that no voltage is applied to the power cable.
Page 10 3. Operating Precautions DANGER While the power is ON, do not touch any terminal, otherwise you may receive an electric shock. CAUTION Before changing the program, generating a forced output, or performing the RUN, STOP, or like procedure during an operation, thoroughly verify the safety because the use of an incorrect procedure may cause equipment damage or other accident.
Page 11 Hitachi cannot be responsible for accidents or losses resulting from a customer’s misuse. If the software supplied by Hitachi is modified for use, Hitachi cannot be responsible for accidents or losses resulting from such modification. Hitachi cannot be responsible for reliability if you use software other than supplied from Hitachi.
Page 12 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 13 This manual provides information for the following hardware and program products: <Hardware product> FL.NET (LQE500/LQE502) <Program products> S-7890-30 “FL.NET SYSTEM” 07-03 S-7895-30 “S10V FL.NET SYSTEM” 01-01 <Changes added to this manual> Description of added changes Page Subsection 6.1.1, “Replacing or adding on the module” is newly added. In addition to the above changes, all the unclear descriptions and typographical errors found are also corrected without prior notice.
Page 14 Revision record Revision No. Revision Record (revision details and reason for revision) Month, Year Remarks First Edition April 2003 Subsection 6.1.1, “Replacing or adding on the module” October 2008 is newly added.
Page 15 PREFACE Thank you for purchasing the FL.NET module, which is an option for use with the S10mini/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 16 The existing parameter setting software (FL.NET system) shown in the following table can be used for LQE500 and LQE502 regardless of the FL-net protocol version. Name Model Remarks FL.NET system for S10mini S-7890-30J For LQE500 and LQE502 FL.NET system for S10V S-7895-30J...
Page 17 <Trademarks> • Microsoft® Windows® operating system, Microsoft® Windows® 95 operating system, Microsoft® Windows® 98 operating system, Microsoft® Windows® 2000 operating system, Microsoft® Windows® XP operating system are registered trademarks of Microsoft Corporation in the United States and/or other countries. • Ethernet® is registered trademark of Xerox, Corp. <Note for storage capacity calculations>...
Page 18: Table Of Contents
CONTENTS 1 OVERVIEW ........................1-1 1.1 What is FL-net ....................... 1-2 1.2 FL-net Features ........................ 1-3 2 FL.NET MODULE ......................2-1 2.1 System Configuration ...................... 2-2 2.1.1 Functionality and performance specifications............2-3 2.1.2 Support tool specification ..................2-3 2.1.3 Link data specifications..................2-4 2.1.4 Link parameter setup area ..................
Page 19 5.2.4 Amount of data transmission................5-14 5.2.5 Transfer cycle and monitoring................5-15 5.2.6 Data area and memory..................5-16 5.2.7 Communication management tables..............5-17 5.2.8 Cyclic transmission and area ................5-19 5.2.9 Message transmission..................5-24 5.3 FL.NET Module Setup Procedures ................5-36 5.3.1 Startup procedure....................
Page 20 5.6.9 Sending setups....................5-144 5.6.10 Setup IP address ....................5-146 5.6.11 Entering operation function (S10mini only) ............5-148 5.6.12 Printing....................... 5-150 5.6.13 CSV output......................5-152 6 MAINTENANCE ........................ 6-1 6.1 Maintenance and Inspection..................... 6-2 6.1.1 Replacing or adding on the module ............... 6-3 7 TROUBLESHOOTING.......................
Page 21 8.3.5 Subnet mask ......................8-16 8.3.6 TCP/IP and UDP/IP communication protocols ........... 8-16 8.3.7 Port numbers......................8-16 8.3.8 FL-net data format ....................8-17 8.3.9 FL-net transaction codes..................8-19 8.3.10 Transaction code receive operation at the UDP port........... 8-21 8.4 FL-net Network Management ..................8-22 8.4.1 FL-net token management ...................
Page 22 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 2-2 FL.NET Module External Views............... 2-8 Figure 2-3 FL.NET Module Component Names..............2-9 Figure 3-1 Mounting the Option Module ................
Page 23 Figure 5-21 Cyclic Transmission Common Memory Area Example 1 ......5-21 Figure 5-22 Cyclic Transmission Common Memory Area Example 2 ......5-22 Figure 5-23 Common Memory Area 1 and 2..............5-22 Figure 5-24 Data Synchronicity Assurance ................ 5-23 Figure 5-25 Message Transmission Overview..............5-24 Figure 5-26 Byte Block Read....................
Page 24 Figure 5-55 The [Communication type] Window ............. 5-131 Figure 5-56 File Selection Dialog Box................5-131 Figure 5-57 The [Open] Window -- an Example .............. 5-133 Figure 5-58 The [Create confirmation] Dialog Box ............5-134 Figure 5-59 The Error Message Dialog Box Displayed in the Event of a Non-Existent or Invalid FL.NET Setup Info File Specified ......
Page 25 Figure 8-27 Ethernet Transceiver (Connector Type) ............8-38 Figure 8-28 Ethernet Multiport Transceiver ............... 8-39 Figure 8-29 Ethernet Repeater .................... 8-40 Figure 8-30 Ethernet Coaxial Cable ................... 8-41 Figure 8-31 Ethernet Coaxial Connector ................8-41 Figure 8-32 Ethernet Junction Connector ................8-42 Figure 8-33 Ethernet Terminator (Terminating Resistor)...........
Page 26 Figure 8-63 Transceiver and Transceiver Cable Wall-mounting Example 1 ...... 8-61 Figure 8-64 Transceiver and Transceiver Cable Wall-mounting Examples 2 ....8-62 Figure 8-65 Transceiver and Transceiver Cable Above-the-ceiling Mounting and Under-the-floor Mounting Example ............8-63 Figure 8-66 Mounting the Insertion Claw in the Ground Terminal Body......8-64 Figure 8-67 Installing the Ground Terminal................
Page 27 TABLES Table 2-1 General Specifications ..................Table 2-2 Functionality and Performance Specifications............ Table 2-3 Registers Available for Common Memory Area Allocation in CPU or LPU Memory ..................Table 2-4 Virtual Address Space and Physical Memory............. Table 2-5 Virtual Address Spaces and Symbol Names ............Table 2-6 Error Memory Area for Link Data ..............
Page 28 Table 7-6 Details of Error Freeze Information Table............7-10 Table 7-7 List of Detectable Codes..................7-12 Table 8-1 FL-net Communication Protocols..............8-14 Table 8-2 IP Address Classification................... 8-15 Table 8-3 FL-net Port Numbers ..................8-16 Table 8-4 List of Transaction Codes .................. 8-20 Table 8-5 Transaction Code Receives Processing at the UDP Port (LQE502)....
Page 29: Overview
1 OVERVIEW...
Page 30: 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 31: 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 32 When FL-net-compliant modules are interconnected, the performance varies with the connected devices. However, when the S10mini/S10V FL.NET modules (Ver. 1.00: Model LQE500) are interconnected, the response speed is as high as 64 ms/32 nodes (in 2k bit + 2k word mode).
Page 33: Fl.net Module
2 FL.NET MODULE...
Page 34: System Configuration
2 FL.NET MODULE 2.1 System Configuration The S10mini/S10V FL.NET module (LQE500, LQE502) 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 35: Functionality And Performance Specifications
Item Specifications Remarks Model LQE500, LQE502 Maximum number of mountable S10mini: 2 modules per CPU (Installing from the modules leftmost slot is required.) S10V: 2 modules per LPU (Installing from the leftmost slot is not required.) Transfer speed 10 Mbps Electrical interface IEEE 802.3-compliant (CSMA/CD-compliant)
Page 36: Link Data Specifications
LWW0000 to LWWFFFF (*2) Word work register LXW0000 to LXW3FFF (*2) Word work register (*1) Usable in the S10mini only. (*2) Usable in the S10V only. (2) Virtual address space and physical memory Table 2-4 Virtual Address Space and Physical Memory Item...
Page 37: Table 2-5 Virtual Address Spaces And Symbol Names
0x209000 to 0x209FFF Word work register LWW0000 to LWWFFFF (*2) 0x450000 to 0x46FFFE 0x228000 to 0x237FFF Word work register LXW0000 to LXW3FFF (*2) 0x4A0000 to 0x4A7FFE 0x250000 to 0x253FFF (*1) Usable in the S10mini only. (*2) Usable in the S10V only.
Page 38: Link Parameter Setup Area
2 FL.NET MODULE (3) Error memory area The FL.NET module offers tables for recording error information. Table 2-6 Error Memory Area for Link Data Item Specifications Error freeze information table Stores information about abnormal operations performed in the module. Error message data table Stores the error messages generated by the other nodes.
Page 39: Profile System Parameter Setup Area
Table 2-7 Profile System Parameter Setup Area (Description example of LQE500) Item Length Data Description Vendor name 10 bytes “HITACHI” Vendor name Maker form 10 bytes “LQE500” Maker form/device name ⎯⎯⎯⎯ Node name (equipment name)
Page 40: Fl.net Module Component Names And Functions
2 FL.NET MODULE 2.2 FL.NET Module Component Names and Functions 2.2.1 External views Figure 2-2 shows external views of the FL.NET module. LQE500 FL.NET LQE502 FL.NET MODU. MODU. 10BASE 10BASE 10BASE 10BASE Front view (LQE500) Front view (LQE502) Side view Figure 2-2 FL.NET Module External Views...
Page 41: Component Names And Functions
This switch performs main module/submodule setup or selects a switch communication port type. 10BASE5 interface Connect this connector to the S10mini and S10V or other controller. connector 10BASE-T interface Connect this connector to the S10mini and S10V or other controller.
Page 42: Fl.net Module Installation
3 FL.NET MODULE INSTALLATION...
Page 43: Mount Base
This module (LQE500, LQE502) can be mounted together with the LQE000 FL.NET module, which is specially designed for use with the S10mini. S10V Series There are no specific rules about the mounting position or unoccupied slots.
Page 44 3 FL.NET MODULE INSTALLATION CAUTION 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 45: Setting The Module Number Selector Switch
3 FL.NET MODULE INSTALLATION 3.3 Setting the Module Number Selector Switch When using the FL-net module, it is necessary to perform main module/submodule setup and communication port setup. Setup can be completed by pointing the arrow mark on the module number selector switch toward the desired module number.
Page 46: Fl.net Module Wiring Procedures
4 FL.NET MODULE WIRING PROCEDURES...
Page 47: Connecting The Communication Cable
4 FL.NET MODULE WIRING PROCEDURES 4.1 Connecting the Communication Cable (1) Connecting the 10BASE5 transceiver cable When the module number selector switch is set to 0 or 1, the module uses the 10BASE5 interface connector to establish communication with the other modules. Ensure that the 10BASE5 cable is connected as shown in Figure 4-1.
Page 48: Figure 4-2 Connecting The 10Base-T Cable To The Module
4 FL.NET MODULE WIRING PROCEDURES When the 10BASE5 connector is connected, make sure that the lock post is locked by the retainer. If the lock post is not properly locked, a malfunction may be caused by a poor contact or open circuit. Do not touch the 10BASE5 connector while the power supply is ON.
Page 49: Applicable Communication Cables
Table 4-1 Communication Cable (10BASE5 Transceiver Cable) Applicable to the Module Product name Model number Manufacturer Transceiver cable HBN-TC-100 Hitachi Cable, Ltd. (2) 10BASE-T cable Table 4-2 Communication Cable (10BASE-T Twisted-pair Cable) Applicable to the Module Product name Model number Manufacturer...
Page 50: Power Supply Wiring
4 FL.NET MODULE WIRING PROCEDURES 4.3 Power Supply Wiring For the use of 10BASE5, it is necessary to supply power from an external power source as indicated in Figure 4-3. LQE500 FL.NET LQE502 for MODU LQE502 10BASE 10BASE Connect to the FG terminal 12 VDC on the mount base.
Page 51: Ground Wiring
4 FL.NET MODULE WIRING PROCEDURES 4.4 Ground Wiring When using 10BASE5, make the ground wiring connection as shown in Figure 4-4. • Typical ground wiring for 10BASE5 10BASE Grounding point 10BASE or more 12 VDC Class D grounding* • Ground wiring for 10BASE-T (Do not make a ground wiring connection to the FG on the FL.NET module.) 10BASE Grounding point...
Page 52 4 FL.NET MODULE WIRING PROCEDURES * 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 seconds when shorting occurs in low tension lines.
Page 53: User Guide
5 USER GUIDE...
Page 54: Ethernet
5 USER GUIDE 5.1 Ethernet 5.1.1 10BASE5 system In the basic configuration, nodes are connected to a coaxial cable having a maximum length of 500 m as shown in Figure 5-1. Nodes are connected to the coaxial cable via transceiver cables (AUI cables) and transceivers.
Page 55: Figure 5-2 10Base5 System Basic Connection Method
5 USER GUIDE If the inter-node distance is longer than 500 m, you can increase the number of segments by making branches with repeaters as shown in Figure 5-2. In an example system shown in Figure 5-2, the maximum inter-node distance is not longer than 1500 m. Ensure that the number of repeaters does not exceed 2 in any path between arbitrarily selected two nodes.
Page 56: Figure 5-3 10Base5 System Basic Connection Method
5 USER GUIDE In the example shown in Figure 5-3, the maximum inter-node distance is 2500 m. A link cable (the maximum length is 500 m when the cable is coaxial) having repeaters on both ends is used to increase the transmission distance. A segment formed in this manner is called a link segment. No node is to be connected to a link segment.
Page 57: Table 5-1 General Specifications For Ethernet System Configuration
5 USER GUIDE The maximum link segment length is 500 m. Do not connect any node to a link segment. When a link segment is used, the portion enclosed by dotted lines in Figure 5-3, including the repeaters on both ends, is counted as one repeater. Ensure that the number of repeaters between nodes does not exceed 2.
Page 58 5 USER GUIDE Limitations on multiport transceiver installation location When a multiport transceiver is installed in the farthest coaxial segment in a system whose maximum coaxial cable length is 2500 m (5 segments), the multiport transceiver installation location is limited due to an increase in the data delay time.
Page 59: 10Base-T System
5 USER GUIDE When the H-7612-64/H-7612-68 multiport transceiver is used in network mode, cascade connections cannot be made due to the limitations on transmission characteristics. Coaxial cable H-7612-64 H-7612-68 H-7612-64 H-7612-68 H-7612-64 H-7612-68 H-7612-64 H-7612-68 Cascade connections impossible except for Cascade connections single-stage cascading impossible...
Page 60 5 USER GUIDE When the inter-node distance is short, you can connect nodes to a hub via twisted-pair cables as shown in Figure 5-5. These node connections can be made without a coaxial cable or transceiver. Figure 5-5 10BASE-T System Basic Connection Method 2 Limitations on hub use Hub cascading When using hubs (multiport repeaters) in cascade, ensure that no inter-node...
Page 61: Figure 5-6 Ethernet Ip Address Classification
5 USER GUIDE <IP address> UDP/IP uses a 32-bit logical address called an IP address. The IP address consists of a network address and host address. Class C is used in the field of FA (factory automation). Class C Network address (20-bit) Host address (8-bit) Figure 5-6 Ethernet IP Address Classification The IP address consists of 8-bit strings of decimal numbers joined by periods (.).
Page 62: Fl-Net
5 USER GUIDE 5.2 FL-net 5.2.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 63: Figure 5-9 Fa Link Protocol
5 USER GUIDE (2) FL-net protocol The FL-net consists of six protocol layers as shown in Figure 5-9. 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 Message transmission...
Page 64: 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 65: Supported Data Communications
5 USER GUIDE 5.2.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-12 Data Communication Types Supported by FL-net (1) Cyclic transmission Cyclic transmission provides periodic transmission of data.
Page 66: Figure 5-14 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 67: Figure 5-17 Typical Refresh Cycle Time Limit
5 USER GUIDE 5.2.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 68: Figure 5-18 Data Area And Memory
Message transmission message transmission buffer area FL-net management table area Physical memory FL-net parameter area * The CPU denotes the CPU module in the S10mini, or LPU module in the S10V. Figure 5-18 Data Area and Memory 5-16...
Page 69: Table 5-2 Self-Node Management Table
5 USER GUIDE 5.2.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-2 Self-node Management Table Name Length...
Page 70: Table 5-3 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-3 Participating Node Management Table Name Length Description/data range Node number 1 byte 1 to 254 Higher layer status 2 bytes...
Page 71 5 USER GUIDE 5.2.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 72 5 USER GUIDE Time Node #1 Node #2 Node #3 Node #N Token Node #1 Node #2 Node #3 Node #N Token Figure 5-19 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 73: Figure 5-21 Cyclic Transmission Common Memory Area Example 1
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 1024-byte transmission size limit per frame is exceeded by an area transmitted by one node.
Page 74: Figure 5-22 Cyclic Transmission Common Memory Area Example 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 (Transmission) (Reception) (Reception) (Reception) (Transmission) (Reception) Figure 5-22 Cyclic Transmission Common Memory Area Example 2 (3) Area 1 and 2 One node can allocate two data areas (Area 1 and 2) in the common memory.
Page 75: Figure 5-24 Data Synchronicity Assurance
5 USER GUIDE (4) 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 76: Figure 5-25 Message Transmission Overview
5 USER GUIDE 5.2.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 77: Table 5-5 List Of Supported Message Transmissions
5 USER GUIDE (2) List of supported messages Table 5-5 lists the types of messages that are supported by the FL.NET module. Table 5-5 List of Supported Message Transmissions Message Request Response Byte block read Byte block write √ √ Word block read √...
Page 78: Figure 5-26 Byte Block Read
5 USER GUIDE (3) Message function description 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 79: Figure 5-27 Byte Block Write
5 USER GUIDE 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 8 bits 0xFFFFFFFF...
Page 80: Figure 5-28 Word Block Read
5 USER GUIDE 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.4 Using the FL.NET Module.” Request message Response message 16 bits AAAA...
Page 81: Figure 5-29 Word Block Write
5 USER GUIDE 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.4 Using the FL.NET Module.” Request message Response message 16 bits AAAA...
Page 82: Figure 5-30 Network Parameter Read
5 USER GUIDE Network parameter read This function reads a remote node’s network parameter information from the network. The table 5-6 lists the items of information that this function reads. For use instructions, see “5.4 Using the FL.NET Module.” Table 5-6 Network Parameter Information Node number Vendor name Maker form...
Page 83: Figure 5-31 Network Parameter Write
5 USER GUIDE 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.4 Using the FL.NET Module.” • Node name (equipment name) •...
Page 84: Figure 5-32 Run/Stop Directive
5 USER GUIDE 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.4 Using the FL.NET Module.” Request message Response message Run directive...
Page 85: Figure 5-33 Profile Read
5 USER GUIDE 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: •...
Page 86: Figure 5-34 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.4 Using the FL.NET Module.” Request message Response message Communication log data Figure 5-34 Communication Log Data Read Communication log data clear This function clears a remote node’s log information from the network.
Page 87: Figure 5-36 Message Return Function
5 USER GUIDE Message return This function returns a received message. A message return automatically takes place within the FL.NET module. For use instructions, see “5.4 Using the FL.NET Module.” Request message Response message Figure 5-36 Message Return Function Transparent message transmission This function offers a transparent service to an FL-net higher layer.
Page 88 5 USER GUIDE 5.3 FL.NET Module Setup Procedures 5.3.1 Startup procedure The startup procedure for the FL.NET module is described below: ① Switch OFF the CPU unit or LPU unit and then install the FL.NET Start module. ② Set the module number selector switch on the FL.NET module, as Mount the module.
Page 89: Figure 5-38 Ip Address Setup Window
5 USER GUIDE (1) IP address/subnet setup precautions For the FL.NET module, you can freely set the IP address and subnet mask. However, you must comply with the FL-net protocol. It is therefore recommended that you use Class C for IP address setup and set the network address to 192.168.250.
Page 90 Note 5: If the IP address is not set or its setting is cleared, for instance, by clearing the memory at the time of OS loading, all the processes come to a stop except IP address setup, with the LER LED on the FL.NET module glowing and the S10mini CPU unit indicator showing the following error message: When the main module IP address is not set: “FLNMIPNG”...
Page 91: Figure 5-39 Link Parameter Setup Window
5 USER GUIDE 5.4 Using the FL.NET Module 5.4.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 [FL.NET For Windows®] to perform link parameter setup. The self- node setup screen is shown below.
Page 92 5 USER GUIDE The table below shows the acceptable input value range for each setting item. Input item Description Acceptable setting range Node number This number is used to identify the nodes for FL-net 1 to 254 communication purposes. Token surveillance This value represents the period of time (ms) during Fixed at 255 (cannot be timeout...
Page 93 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 94: Figure 5-40 Common Memory Data Transfer Image Of Fl.net Module
5 USER GUIDE 5.4.2 CPU or LPU memory allocation procedure The FL.NET module allocates the common memory area in the CPU or LPU memory. The data received by the FL.NET module is transferred to the resulting CPU or LPU memory. FL.NET module internal memory CPU or LPU memory Common memory area 1...
Page 95 /100000 to /4FFFFE (Extension memory) (*1) CPU module extension memory LBW0000 to LBWFFF0 (*2) Work register LWW0000 to LWWFFFF (*2) Word work register LXW0000 to LXW3FFF (*2) Word work register (*1) Usable in the S10mini only. (*2) Usable in the S10V only. 5-43...
Page 96: Figure 5-41 Self-Node Cpu Or Lpu Memory Allocation Window
5 USER GUIDE (1) Allocating the self-node CPU or LPU memory With the setup tool named [FL.NET For Windows®], open the [self-node information] window. In the “PCs allocment” section, enter the addresses for the PI/O or extension memory to be allocated as the self-node CPU or LPU memory area. After completion of input, click the button.
Page 97 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 CPU or LPU memory must not be a duplicate of any one of those for the other nodes.
Page 98: Figure 5-42 Common Memory Area Setup Window For Other Participating Nodes
5 USER GUIDE (2) Setting the CPU or LPU memory area for the other nodes Perform reception setup for the other nodes with the setup tool named [FL.NET For Windows®]. The data received from various nodes are transferred to the area allocated in the CPU or LPU memory.
Page 99 CPU or LPU memory area word count setting. If any node is left without being set, the FL.NET module cannot transfer to the S10mini or S10V the data received from that node into the common memory. 5-47...
Page 100: Figure 5-43 Setup Window For Setting Various Status Flag Areas For The Self-Node
[FL.NET For Windows®]. When various items of status information on the S10mini or S10V need to be referenced, the status of participating nodes and the like can be grasped by setting the transfer area for each flag.
Page 101 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 S10mini or S10V. 5-49...
Page 102 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 103: Figure 5-45 Bit Conversion Of Area 1 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 Bits Data received from another node 0x1234 Data transferred to S10mini or S10V 0x2C48 Data on S10mini or S10V 0x1234 Bits Data transmitted to another node...
Page 104 The FL.NET module does not perform bit conversion when transmitting or receiving the data of the common memory area 2. It transfers the data to the network without changing its arrangement on the S10mini or S10V, so the data received from the other nodes is transferred as it is. 5.4.5 Using message communications (1) Message communication (server side) When the FL.NET module receives a message request from another node, it processes the...
Page 105 5 USER GUIDE (3) C mode handler or mathematical/logical function (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 106: Table 5-8 C Mode Handler List
Issues a communication log clear request. mesret( ) /D74148 /D60120 /DF4148 /DE0120 Issues a message return request. Issues a specified-task control request (Hitachi’s unique reqmacro( ) /D74160 /D60140 /DF4160 /DE0140 transparent type of support). Issues a transparent message reception request (Hitachi’s toukaread( ) /D74178 /D60160 /DF4178 /DE0160 unique transparent type of support).
Page 107 The parameter specified at mathematical/logical function startup dictates the message processing to be requested. For the S10mini, it is necessary to register the mathematical/logical function for the main module/sub-module beforehand with the [FL.NET For Windows®] to use the mathematical/logical function in a ladder program.
Page 108: Table 5-9 Mathematical/Logical Function List
To check whether the requested processing is ended normally, note the code that is set at the error code storage address. Table 5-9 Mathematical/Logical Function List Mathematical/logical function Name registration address Functionality description Main Main S10mini S10V S10mini S10V FLCM FLCS /D74100 /D60000 /DF4100...
Page 109 Note 1: For bit allocation for the self-node status flag, see “5.4.6 Using the management tables.” Note 2: To make a request by using a mathematical/logical function in the S10mini, register the mathematical/logical function for the FL.NET module into the S10mini CPU by using the setup tool [FL.NET For Windows®].
Page 110 5 USER GUIDE <Transparent reception task> When a transparent message is received in situations where a transparent reception task is registered in the FL.NET module, task queuing takes place with the start factor (transparent reception task’s factor) that is set for the task number of the registered task. If the registered task is not released, however, it does not start.
Page 111 Description Acceptable setting range Transparent reception Task number of the task that is to start For the S10mini, the acceptable setting task upon receipt of a transparent message. ranges from 1 to 128. However, enter a setting between 2 and 100. For the S10V, the acceptable setting ranges from 1 to 255.
Page 112: Table 5-10 Transparent Receiving Flag Allocation
5 USER GUIDE Table 5-10 shows the bit allocation for the transparent receiving flag area. Table 5-10 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 113 = (long(*)( ))0xD60020 ;/* S10V */ wordrd = (long(*)( ))0xDE0020 ;/* S10V */ rtn = (*wordrd)(padr) ; rtn = (*wordrd)(padr) ; Note: For the S10mini, substitute 0xD74112, 0xDF4112 for 0xD60020, 0xDE0020. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (3)
Page 114 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 115 5 USER GUIDE [Function] • A word block read request using the specified virtual address and virtual size will be issued to a remote node. When a response code is received, the data is transferred to a read data storage address. •...
Page 116 = (long(*)( ))0xD60040 ;/* S10V */ wordwt = (long(*)( ))0xDE0040 ;/* S10V */ rtn = (*wordwt)(padr) ; rtn = (*wordwt)(padr) ; Note: For the S10mini, substitute 0xD74118, 0xDF4118 for 0xD60040, 0xDE0040. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (4)
Page 117 5 USER GUIDE Parameter Input range Message transmission service 4 (only when a mathematical/logical function is number used) Remote node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the CPU or LPU. (*) Write data storage address Virtual address 0 to 0xFFFFFFFF...
Page 118 = (long(*)( ))0xDE0060 ;/* S10V */ ～～ rtn = (*parard)(padr) ; rtn = (*parard)(padr) ; Note: For the S10mini, substitute 0xD7411E, 0xDF411E for 0xD60060, 0xDE0060. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (5) +0x0004 Remote node number (1 to 254)
Page 119 5 USER GUIDE Parameter Input range Message transmission service number 5 (only when a mathematical/logical function is used) Remote node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the CPU or 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 120 The data transfers to the read parameter data storage address in the format shown below. The node number does not transfer to the S10mini or S10V. Read parameter Node name (equipment name)
Page 121 = (long(*)( ))0xDE0080 ;/* S10V */ ～～ rtn = (*parawt)(padr) ; rtn = (*parawt)(padr) ; Note: For the S10mini, substitute 0xD74124, 0xDF4124 for 0xD60080, 0xDE0080. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (6) +0x0004 Remote node number (1 to 254)
Page 122 5 USER GUIDE Parameter Input range Message transmission service number 6 (only when a mathematical/logical function is used) Remote node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the CPU or 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 123 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 124 ReqStop = (long(*)( ))0xDE00A0 ;/* S10V */ ～～ rtn = (*ReqStop)(padr) ; rtn = (*ReqStop)(padr) ; Note: For the S10mini, substitute 0xD7412A, 0xDF412A for 0xD600A0, 0xDE00A0. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (7) +0x0004 Remote node number (1 to 254)
Page 125 5 USER GUIDE [Parameters] : Input parameter storage starting address padr Struct reqs_p { : Remote node number (1 to 254) long node ; : Error code storage address unsigned short *Erradr ; Be sure to specify an even-numbered address in padr. Parameter Input range Message transmission service...
Page 126 ReqRun = (long(*)( ))0xDE00C0 ;/* S10V */ ～～ rtn = (*ReqRun)(padr) ; rtn = (*ReqRun)(padr) ; Note: For the S10mini, substitute 0xD74130, 0xDF4130 for 0xD600C0, 0xDE00C0. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (8) +0x0004 Remote node number (1 to 254)
Page 127 5 USER GUIDE Parameter Input range Message transmission service 8 (only when a mathematical/logical function is number used) Remote node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the CPU or 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 0x02 0x01 “0x01” 0x13 0x07 “REVDATE” 0x30 0x0A 0x02 0x02 “0x07CF (1999) ” 0x02 0x01 “0x0B(11) ” 0x02 0x01 “0x0F(15) ” 0x13 0x0A “DVCATEGORY” 0x13 0x03 “PLC” 0x13 0x06 “VENDOR” 0x13 0x07 “HITACHI” 0x13 0x07 “DVMODEL” 0x13 0x06 “LQE500” 5-76...
Page 129 0x02 0x01 “0x01” 0x13 0x07 “REVDATE” 0x30 0x0A 0x02 0x02 “0x07D3 (2003) ” 0x02 0x01 “0x0C(12) ” 0x02 0x01 “0x12(18) ” 0x13 0x0A “DVCATEGORY” 0x13 0x03 “PLC” 0x13 0x06 “VENDOR” 0x13 0x07 “HITACHI” 0x13 0x07 “DVMODEL” 0x13 0x06 “LQE502” 5-77...
Page 130 Logrd = (long(*)( ))0xDE00E0 ;/* S10V */ ～～ rtn = (*Logrd)(padr) ; rtn = (*Logrd)(padr) ; Note: For the S10mini, substitute 0xD7413C, 0xDF413C for 0xD600E0, 0xDE00E0. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (10) +0x0004 Remote node number (1 to 254)
Page 131 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 132 Logclr = (long(*)( ))0xDE0100 ;/* S10V */ ～～ rtn = (*Logclr)(padr) ; rtn = (*Logclr)(padr) ; Note: For the S10mini, substitute 0xD74142, 0xDF4142 for 0xD60100, 0xDE0100. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (11) +0x0004 Remote node number (1 to 255)
Page 133 5 USER GUIDE Parameter Input range Message transmission service 11 (only when a mathematical/logical function is number used) Remote node number 1 to 255 Error code storage address Specify a real address (even-numbered address) on the CPU or 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 134 Mesret = (long(*)( ))0xDE0120 ;/* S10V */ ～～ rtn = (*Mesret)(padr) ; rtn = (*Mesret)(padr) ; Note: For the S10mini, substitute 0xD74148, 0xDF4148 for 0xD60120, 0xDE0120. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (12) +0x0004 Remote node number (1 to 254)
Page 135 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 1024) long Sendsiz ;...
Page 136 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 137 ReqMacro = (long(*)( ))0xDE0140 ;/* S10V */ ～～ rtn = (*ReqMacro)(padr) ; rtn = (*ReqMacro)(padr) ; Note: For the S10mini, substitute 0xD74160, 0xDF4160 for 0xD60140, 0xDE0140. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (13) +0x0004 Remote node number (1 to 254)
Page 138 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 139 <To execute a task abort> CPMS macro parameter count = 2 CPMS macro parameter [0] = 1 CPMS macro parameter [2] = task number (S10mini: 1 to 128, S10V: 1 to 255 (Note)) <To execute a task release> CPMS macro parameter count = 2...
Page 140 ToukaRead = (long(*)( ))0xDE0160 ;/* S10V*/ ～～ rtn = (*ToukaRead)(padr) ; rtn = (*ToukaRead)(padr) ; Note: For the S10mini, substitute 0xD74178, 0xDF4178 for 0xD60160, 0xDE0160. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (17) +0x0004 Reception destination node number (0 to 254)
Page 141 5 USER GUIDE Parameter Input range Message transmission service 17 (only when a mathematical/logical function is number used) Reception destination node 0 to 254 number Error code storage address Specify a real address (even-numbered address) on the CPU or LPU. (*) Reception data storage address Data word count 0 to 1024 (variable in 1-byte units)
Page 142 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 143 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 144 ToukaSend = (long(*)( ))0xDE0180 ;/* S10V */ ～～ rtn = (*ToukaSend)(padr) ; rtn = (*ToukaSend)(padr) ; Note: For the S10mini, substitute 0xD7417E, 0xDF417E for 0xD60180, 0xDE0180. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (18) +0x0004 Transmission destination node number (1 to 255)
Page 145 5 USER GUIDE Parameter Input range Message transmission service 18 (only when a mathematical/logical function is number used) Transmission destination node 1 to 255 number Error code storage address Specify a real address (even-numbered address) on the CPU or LPU. (*) Transmission data storage address Data word count 0 to 1024 (specified in bytes)
Page 146 5 USER GUIDE [Function] • As many data words as specified in bytes will be transferred from the area specified by a transmission data storage address to the remote node having a specified node number as a transparent message having the TCD number specified by a transmission message TCD. •...
Page 147 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 148 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 149 (long(*)( ))0xDE01A0 ;/* S10V */ ～～ rtn = (*comoffset)(padr) ; rtn = (*comoffset)(padr) ; Note: For the S10mini, substitute 0xD74184, 0xDF4184 for 0xD601A0, 0xDE01A0. [Parameters for mathematical/logical function] +0x0000 Message transmission service number (19) +0x0004 Specified node number (1 to 254)
Page 150 5 USER GUIDE Parameter Input range Message transmission service 19 (only when a mathematical/logical function is number used) Specified node number 1 to 254 Error code storage address Specify a real address (even-numbered address) on the CPU or LPU. (*) Common memory area 1 offset 0 to 0x1FF (variable in 1-word units) size...
Page 151 The above feature is designed for use in cases where the available memory space of the S10mini or S10V is insufficient. It is recommended that you do not use the feature when the memory space of the S10mini or S10V is adequate.
Page 152 LQP010 (LQP510 + LQP520) FL.NET LQE500/LQE502 Mount base HSC-1020, 1040, 1080, 1540, 1580 Select a model among those shown at left. Transceiver cable HBN-TC-100 Maker: Hitachi Cable, Ltd. Transceiver HLT-200TB Maker: Hitachi Cable, Ltd. Coaxial cable HBN-CX-100 Maker: Hitachi Cable, Ltd. Terminator HBN-T-NJ Maker: Hitachi Cable, Ltd.
Page 153 5 USER GUIDE [FL.NET module settings] The FL.NET module settings for CPU01 and CPU02 (or LPU/CMU01 and LPU/CMU02) are shown below: Self-node settings for the FL.NET modules Setup item CPU01 or LPU/CMU01 setting CPU02 or LPU/CMU02 setting Node number Area 1 address (setting) 0x000 0x004 Area 1 words...
Page 154 5 USER GUIDE [Program structure] The program structure is shown below. With the module having the node number 1 (FL.NET module for CPU01 or LPU/CMU01) and the module having the node number 2 (FL.NET module for CPU02 or LPU/CMU02) interconnected, cyclic transfer operations are performed between the FL-net modules.
Page 155 5 USER GUIDE [CPU01 or 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 156 /* Wait for message processing termination */ if( !( *nodeflg & 0x8000)){ break; Note: For the S10mini, change the #define TOUKA_SEND value from 0xD60180 into 0xD7417EL, the #define SBUFADR value from 0x450000L into 0x1E6000L, and the #define PARADDR value from 0x452000L into 0x1E5000L.
Page 157 5 USER GUIDE [CPU02 or 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 158 /* Wait for message processing termination */ if( !( *nodeflg & 0x8000)){ break; Note1: For the S10mini, change the #define TOUKA_READ value from 0xD60160 into 0xD74178L, the #define RBUFADR value from 0x450000L into 0x1E6000L, and the #define PARADDR value from 0x452000L into 0x1E5000L.
Page 159 LQP010 (LQP510) FL.NET LQE000 Mount base HSC-1020, 1040, 1080, 1540, 1580 Select a model among those shown at left. Transceiver cable HBN-TC-100 Manufacturer: Hitachi Cable, Ltd. Transceiver HLT-200TB Manufacturer: Hitachi Cable, Ltd. Coaxial cable HBN-CX-100 Manufacturer: Hitachi Cable, Ltd. Terminator HBN-T-NJ Manufacturer: Hitachi Cable, Ltd.
Page 160 5 USER GUIDE [FL.NET module settings] The FL.NET module settings for CPU01 and CPU02 (or LPU01 and LPU02) are shown below: Self-node settings for the FL.NET modules Setup item CPU01 or LPU01 setting CPU02 or LPU02 setting Node number Area 1 address (setting) 0x000 0x004 Area 1 words...
Page 161 The node 2 module receives the transparent message from node 1 module. This program example is a ladder program, which runs in this manner. When using this ladder program, be sure to place the S10mini or S10V in the RUN state. CPU01 or LPU01...
Page 162 5 USER GUIDE [CPU01 or LPU01 side ladder program] 18 = FL400 （MOV）DST V000 R080 R0A0 R088 （00001） 2 = FL402 （MOV）DST RW090 = FL404 FW000 = FL406 （MOV）DST 1024 = FL408 11000 = FL40A （MOV）DST FLCM HE2800（FW400） The description in parentheses is for the S10V. 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...
Page 163 5 USER GUIDE DST 11000 = FL40A (MOV 11000 = FL40A for the S10V) The TCD number (11000) is specified for the transparent message to be transmitted. FLCM HE2800 (FLCM FW400 for the S10V) The parameter storage address (HE2800 = FW400 real address) is specified for the mathematical/logical function (FLCM).
Page 164 5 USER GUIDE AST RW090 = FL404 The error code storage address (RW090 real address) is specified. AST FW000 = FL406 The reception buffer address (FW000 real address) is specified. DST 1024 = FL408 (MOV 1024 = FL408 for the S10V) The reception word count is specified.
Page 165: Figure 5-47 Participating Node Number List Window 1
5 USER GUIDE 5.4.6 Using the management tables The FL.NET module uses various management tables to manage the status of communications with remote nodes. You can determine the status of communications with the remote nodes by referencing these management tables. Note, however, that the setup tool named [FL.NET For Windows®] must be used to reference the management tables within the FL.NET module.
Page 166: Figure 5-48 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 167 =0: A request from the user is being awaited. =1: A request from the user is being processed. Note: The above self-node status represents the contents that are transferred to the S10mini or S10V. The self-node information dialog box of the setup tool [FL.NET For Windows®] allows you to reference the low-order byte (bits 2...
Page 168 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 Effective bit for Valid bit LQE502 only Participation status bit =0: The self-node has not participated in the network. =1: The self-node has participated in the network.
Page 169 When a higher-layer error occurs, the FL.NET module turns ON (sets) bits 2 and 2 Higher-layer operation status bit =0: The higher layer (S10mini or S10V) is halted (in the STOP state). =1: The higher layer (S10mini or S10V) is running (in the RUN state). 5-117...
Page 170: Figure 5-49 Participating Node Number List Window 2
5 USER GUIDE (2) Referencing the participating node management table When you display information about participating nodes with the setup tool [FL.NET For Windows®], you can view the [Other node information] dialog box, which lists the node numbers of the nodes that have participated in the network and the participating node management table contents concerning the participating node numbers.
Page 171: Figure 5-50 Participating Other Node Link Information Window
5 USER GUIDE Figure 5-50 Participating Other Node Link Information Window For the bit allocation for the higher layer status and FA link status about individual nodes, refer to the respective node manuals. (3) Referencing the network management table The network status window of the setup tool [FL.NET For Windows®] allows you to view the contents of the network management table.
Page 172 5 USER GUIDE The contents of the above window are explained below: On-screen item Description Token maintenance node number This is the node number of the node that currently holds the token. Minimum frame interval This value denotes the minimum frame interval that is allowed on the network.
Page 173 5 USER GUIDE Token hold time (ms): Token holding time of the self-node Token hold time = 1.6 + 0.0036 × S + 0.0029 × R + 2.47 × F + MFT ....[When 0 ≤ MFT < 2 and R ≤ 512] Token hold time = 1.6 + 0.0036 ×...
Page 174 5 USER GUIDE Word block read throughput (ms) Time from starting the operational function for word block reading to transmission of ACK to the opposite part from the self-node. Word block read throughput = 8 + 3RCT + Token holding time = 9.6 + 3RCT + 0.0036 ×...
Page 175 5 USER GUIDE Transparent message (ms) Message creating time (ms) = 0.02 + (0.0007 × MS)....[When message creating time > MFT] Message creating time (ms) = MFT ..........[When message creating time ≤ MFT] Message transmit processing time (ms) = (0.00096 × MS) Message receive processing time (ms) = (0.0013 ×...
Page 176 5 USER GUIDE (2) For FL-net protocol version Ver. 2.00 (Model: LQE502) 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. Accordingly, the worst case scenario is shown below on the supposition of communication performance between FL-NET modules.
Page 177 5 USER GUIDE Word block read throughput (ms) Time from starting the operational function for word block reading to transmission of ACK to the opposite part from the self-node. Word block read throughput = 8 + 3RCT + Token holding time = 10.7 + 3RCT + 0.0034 ×...
Page 178: Figure 5-52 [Ras Information] Dialog Box
5 USER GUIDE 5.4.8 Using the communication log With the setup tool [FL.NET For Windows®], you can view the RAS information (communication log) maintained in the FL.NET module. Figure 5-52 [RAS Information] Dialog Box 5-126...
Page 179 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 180 5.5.1 Installing (1) Installing the S10mini FL.NET system First check that the correct CD is on hand. The S10mini FL.NET system runs on the Microsoft® Windows® 95 operating system, Microsoft® Windows® 98 operating system, Microsoft® Windows® 2000 operating system and Microsoft® Windows® XP operating system.
Page 181 To start up the FL.NET system, perform the following procedure: S10mini FL.NET system startup procedure (1) If you want to start up the S10mini FL.NET system from the Windows® desk top, double- click the [FL.NET SYSTEM] icon. Alternatively, if you want to start it up from the Start button, choose [Programs] –...
Page 182: Figure 5-53 [Fl.net] Window
(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 the [Start] menu. To accomplish this, choose [Programs] – [Hitachi S10V] – [S10V FL.NET SYSTEM] – [S10V FL.NET SYSTEM] from the Start menu.
Page 183: Figure 5-55 The [Communication Type] Window
5 USER GUIDE (2) By choosing [Change connection] from the [Tool] menu, display the [Connection type] window (Figure 5-55) on-screen. When the [Connection type] window appears, specify the desired destination of connection and click the button (see “5.5.4 Changing connections” for details on the communication type). If you need not change the current connection destination setting, click the Cancel button instead.
Page 184 5 USER GUIDE 5.5.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 [FL.NET] window or [[S10V] FL.NET] window, click the Change connection button.
Page 185 5 USER GUIDE 5.5.5 Selecting an edition file Function: The function of this action is to choose a file you want to edit in offline mode. The files that you can choose for editing are those setup info files which have already been saved or prepared.
Page 186: Figure 5-58 The [Create Confirmation] Dialog Box
5 USER GUIDE Figure 5-58 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 187 5 USER GUIDE 5.6 Operating Method 5.6.1 Self-node information Function: Set the parameters required for the FL.NET module and set common memory allocation. And monitor the FL.NET module information. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [FL.NET] window or [[S10V] FL.NET] window.
Page 188 5 USER GUIDE (5) The [Self-node information] window is displayed. (6) Change the rewrite value and each item of PCs allocation. After completing the setup, click the button (or the Write button if the type of the controller used is S10V). To cancel the setup, click the Cancel button.
Page 189 5 USER GUIDE 5.6.2 Other nodes display Function: Display the contents of areas 1 and 2 of either the local node (self-node) or another distant node, whichever has been selected in the [Self-node information] or [Other node information] window. For using this function, it is a prerequisite that the PCs is connected to the PC by cable. Operation: The procedure is shown below.
Page 190 5 USER GUIDE 5.6.3 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 [FL.NET] window or [[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 191 5 USER GUIDE (6) The item whose setup has been changed is displayed in a different color. Self-node When the setup has been changed, its color changes. (7) If the node number to be displayed is not found on the window, click the ▲...
Page 192 5 USER GUIDE (4) Double-click the node No. icon (blue) to be set. (Double-clicking the red node No. icon displays the [Self-node information] window. (See “5.6.1 Self-node information.”) Double-click (5) The [Other node information] window of the specified number is displayed. (6) Change the each item setup of PCs allocation.
Page 193 5 USER GUIDE 5.6.5 Network status Function: Display the status when joining the network including the allowable refresh cycle time. For using this function, it is a prerequisite that the PCs is connected to the PC by cable. Operation: The procedure is shown below. (1) Select [Main] or [Sub] from the [Module] menu of the [FL.NET] window or [[S10V] FL.NET] window.
Page 194 5 USER GUIDE 5.6.6 Node setting list Function: Display the PCs allocation and current values of all nodes. For using this function, it is a prerequisite that the PCs is connected to the PC by cable. Operation: The procedure is shown below. (1) Click the Node setting list button on the [Network status] window.
Page 195 5 USER GUIDE (4) Click the Start monitoring button to monitor the RAS information. Click the Clear button to reset all the RAS information to 0. Click the Close button to exit the [RAS information] window. The RAS information is all reset to 0 by resetting or turning off and on the power supply. 5.6.8 Saving setups Function: Save the self-node setup of the PCs side, PCs allocation of all nodes, and IP address and subnet mask of the FL.NET module into the file on the PC.
Page 196: Sending Setups
5 USER GUIDE (3) The [Save As] window is displayed. Enter the file name. If a comment is required, enter it in the file comment field. (Maximum number of input characters: 128 characters) To change the PCs number, enter it in the PCs number field. (Maximum number of input characters: 4-digit number) (4) After completing the setup, click the Save...
Page 197 5 USER GUIDE (2) Select the [Send setups] menu. (3) The [Open] window is displayed. Enter the file name. (4) After completing the setup, click the Send button. To cancel the setup, click the Cancel button. (5) After completing the transmission, reset the PCs or display the power OFF/ON request message.
Page 198: Setup Ip Address
5 USER GUIDE 5.6.10 Setup IP address Online editing for the S10mini or S10V controller Function: Set the IP address of the FL.NET module. For using this function, it is a prerequisite that the PCs is connected to the PC by cable.
Page 199 5 USER GUIDE Offline editing for the S10V controller 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 [Setup IP address] window is displayed. Enter the IP address and subnet mask. (3) After completing the setup, click the Write button.
Page 200: Entering Operation Function (S10Mini Only)
5 USER GUIDE 5.6.11 Entering operation function (S10mini only) Function: Enter the operation function for the FL.NET module. For using this function, it is a prerequisite that the PCs is connected to the PC by cable. Operation: The procedure is shown below.
Page 201 5 USER GUIDE (6) The specified operation function is entered. To exit the [Enter operation function] window, click the Close button. 5-149...
Page 202: Printing
5 USER GUIDE 5.6.12 Printing Function: The function of commands used for this purpose is to print on the printer one of the following two pieces of information: 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 203 5 USER GUIDE <Sample printout> 5-151...
Page 204: Csv Output
5 USER GUIDE 5.6.13 CSV output Function: The function of this command is to output to a file in CSV format one of the following two pieces of information: 1) the setup information for a selected module from the actual target machine if the FL.NET system is running in online mode;...
Page 205 5 USER GUIDE <Sample CSV file output> 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 Area1 addr,FW100 Area1 words,8 Area2 addr,FW110...
Page 206: Maintenance
6 MAINTENANCE...
Page 207: Maintenance And Inspection
6 MAINTENANCE 6.1 Maintenance and Inspection To use the S10mini or S10V in an optimum condition, check the items listed below. Make this check at routine inspection or periodic inspection (twice or more per year). Module appearance Check that no fissure or crack exists in the module case. If the case has such a damage, there is a possibility that the internal circuit may also be damaged, resulting in a system malfunction.
Page 208: Replacing Or Adding On The Module
③ Connect the personal computer and the LPU module together with the RS-232C cable. ④ Start Hitachi’s S10V FL.NET System. Then, make a hand-written record of the currently used IP address and save the set values of all the existing parameters. (If the existing parameters are not accessible for some reason, use the copies of their set values [item ④]...
Page 209 6 MAINTENANCE ⑦ Replace the existing FL.NET module with the new one and set the new FL.NET module’s rotary switches in the same way as you wrote down in Step ①. ⑧ Turn on the power supply of the controller unit. Then, enter the same IP address as you recorded in Step ④...
Page 210: Troubleshooting
7 TROUBLESHOOTING...
Page 211: Trouble Detection And Solution
7 TROUBLESHOOTING 7.1 Trouble Detection and Solution When you wonder if a failure may have occurred, check the following items. • Check that the module is properly installed. • Check that the module switches are properly set. • Check that network IP address setup is properly completed. •...
Page 212: Network Problems And Repairing
7 TROUBLESHOOTING 7.2 Network Problems and Repairing (1) Network problems and remedies (concerning communication failures) Table 7-1 Network Problems and Repairing (Concerning Communication Failures) Inspection Problem Inspection procedure Remedy item Communica- Power supply Check whether the device main power Check for a faulty power supply, disconnected tion cannot lamp is illuminated.
Page 213: Table 7-2 Network Problems And Repairing (Concerning Unstable Communications)
7 TROUBLESHOOTING (2) Network problems and remedies (concerning unstable communications) Table 7-2 Network Problems and Repairing (Concerning Unstable Communications) Inspection Problem Inspection procedure Remedy item Establish the proper ground connection as Communi- Transmission Check whether the coaxial cable cation cannot path external conductor is grounded at one directed in “8.6 FL-net Network Installation...
Page 214 7 TROUBLESHOOTING (3) 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 215: 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 IEEE 802.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 216: Error Indications And Countermeasures
(2) Error indications to the CPU module In the S10mini, when an event or error occurs in the FL.NET module, a message is displayed with a distinction between main module and sub-module on the indicator of the CPU module as shown in Table 7-3.
Page 217: Table 7-4 Details Of Cpu Unit Module Indications Given Upon Fa Protocol
7 TROUBLESHOOTING [FA protocol errors] When an error stated in the FA protocol is detected during an FL.NET module operation, the CPU unit module indicator shows a message as explained in Table 7-4. The FL.NET module may stop running in compliance with the FA protocol, depending on the contents of the displayed message.
Page 218 Such a parameter as link parameter of the module may be incorrect (for example, the module containing the parameter data of the S10mini is installed in the S10V.). Set the parameter data. If the error cannot be recovered, the module may be faulty.
Page 219: Table 7-6 Details Of Error Freeze Information Table
S10mini, “FLNMROM3” or “FLNSROM3” is displayed on the indicator of the CPU module. Case 2: In the S10mini, when the FL.NET module in which parameters were set is installed in the S10V, “0x010B” is displayed on the error log of the tool (S10V BASE SYSTEM).
Page 220 7 TROUBLESHOOTING Figure 7-1 Shows the details of the stack frames in the error freeze information table. 7-11...
Page 221: Table 7-7 List Of Detectable Codes
7 TROUBLESHOOTING [Code table of errors that can be detected by C mode handler and mathematical/logical function] Table 7-7 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-7 List of Detectable Codes (1/2) Error...
Page 222 7 TROUBLESHOOTING Table 7-7 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 223 7 TROUBLESHOOTING [Error message data table] When a response message for a message request from the self-node is an abnormal response message, the message data is stored in the error message data table within the FL.NET module. The specification for the error message table is given below: Main module Submodule 0xD41380...
Page 224: Figure 7-2 Module Error Lamp
Therefore, the LER LED indication is not adequate for judging whether the module is abnormal. When the LER LED turns ON, note the CPU module indicator on the S10mini because it furnishes relevant detailed information. For details on indicator readouts, see “(2) Error indications to the CPU module.”...
Page 225: Appendixes
8 APPENDIXES...
Page 226: System Configuration Guide
8 APPENDIXES 8.1 System Configuration Guide 8.1.1 Ethernet overview Ethernet is a LAN (Local Area Network) standard for communications among personal computers, printers, and other devices. It defines communication data formats, cables, connectors, and communication-related items. The Ethernet standard is established by the Ethernet Working Group (IEEE 802.3).
Page 227: 10Base5 Specifications
8 APPENDIXES 8.1.2 10BASE5 specifications 10BASE5 is an Ethernet connection method that uses a coaxial cable about 10 mm in thickness (also referred to as a thick cable or yellow cable.) The number “10” of the designation “10BASE5” represents a transmission speed of 10 Mbps. The “BASE” portion indicates the use of a baseband transmission system.
Page 228: 10Base-T Specifications
8 APPENDIXES 8.1.3 10BASE-T specifications 10BASE-T is an Ethernet connection method that uses a twisted-pair cable. The number “10” of the designation “10BASE-T” represents an Ethernet transmission speed of 10 Mbps. The “BASE” portion indicates the use of a baseband transmission system. The suffix “T” indicates that a twisted-pair cable is used as a transmission medium.
Page 229: Other Ethernet Specifications
8 APPENDIXES 8.1.4 Other Ethernet specifications (1) 10BASE2 10BASE2 is an Ethernet connection method that uses a coaxial cable about 5 mm in thickness (also referred to as a thin cable). The number “10” of the designation “10BASE-2” represents a transmission speed of 10 Mbps. The “BASE” portion indicates the use of a baseband transmission system.
Page 230: Figure 8-6 Wireless Ethernet Configuration Example
8 APPENDIXES (3) Wireless Ethernet A wireless LAN uses radio waves or infrared rays as the transmission medium. It is used, for instance, to connect a mobile device to a LAN. Wireless LAN is being standardized by the IEEE Wireless LAN Working Group (IEEE 802.11). For the interconnection between a wireless LAN and an Ethernet network, the use of a bridge is required because they differ in MAC layer protocol.
Page 231: System Configuration Examples
8 APPENDIXES 8.2 System Configuration Examples 8.2.1 Small-scale configuration A network system consisting of several units of devices can be configured with one multiport transceiver or hub. Multiport transceiver AUI cable (maximum cable length: 50 m) (a) Use of a multiport transceiver Twisted-pair cable [UTP: Category 5] (maximum cable length: 100 m) (b) Use of a hub...
Page 232: Basic Configuration
8 APPENDIXES 8.2.2 Basic configuration A network system consisting of dozens of units of devices can be configured by connecting several multiport transceivers or hubs to one coaxial cable. Coaxial cable (maximum cable length: 500 m) Terminating Ground terminal resistor Single-port transceiver AUI cable...
Page 233: Large-Scale Configuration
8 APPENDIXES 8.2.3 Large-scale configuration A network system consisting of several hundred units of devices can be configured by connecting 10BASE5 network segments with repeaters. Coaxial cable (maximum cable length: 500 m) AUI cable (maximum cable length: 50 m) Multiport transceiver Repeater When a multiport transceiver is used,...
Page 234: Long-Distance Distributed Configuration
8 APPENDIXES 8.2.4 Long-distance distributed configuration If the distance between network segments in a large-scale network system exceeds the 10BASE5 transmission distance limit (500 m), you can connect network segments with optical repeaters to establish a network system whose inter-repeater distance is 2 km. Coaxial cable (maximum cable length: 500 m) AUI cable (maximum cable length: 50 m)
Page 235: Locally Concentrated Configuration
8 APPENDIXES 8.2.5 Locally concentrated configuration When dozens of units of devices are locally concentrated, a network system can be configured with stackable hubs. Stackable hub Twisted-pair cable [UTP: Category 5] (maximum cable length: 100 m) Figure 8-11 Locally Concentrated Configuration Example 8-11...
Page 236: Locally And Widely Distributed Configuration
8 APPENDIXES 8.2.6 Locally and widely distributed configuration When a certain controller in a network system having a basic configuration is positioned at a distance or there is a high-voltage power supply or noise source near a network, a long-haul network having an excellent noise immunity can be configured by dividing the network into two segments and interconnecting them with an optical repeater.
Page 237: Differences Between General-Purpose Ethernet And Fl-Net
8 APPENDIXES 8.2.8 Differences between general-purpose Ethernet and FL-net Since the FL-net is a network for FA (factory automation) fields, it cannot use all the general-purpose Ethernet devices. Some devices are inapplicable to the FL-net due to their noise immunity or environment resistance. The FL-net is required to offer a specified degree of real-time communication response capability for control purposes.
Page 238: Network System Definitions
8 APPENDIXES 8.3 Network System Definitions 8.3.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 239: Fl-Net Physical Layer
8 APPENDIXES 8.3.3 FL-net physical layer For a transmission speed of 10 Mbps, the Ethernet physical layer offers five different transmission methods: 10BASE5, 10BASE2, 10BASE-T, 10BASE-F, and 10BROAD36 (this last one is not commonly used). Note that 100 Mbps Ethernet also exists. The FL-net adopts 10BASE5 (recommended), 10BASE2, and 10BASE-T.
Page 240: Table 8-3 Fl-Net Port Numbers
8 APPENDIXES 8.3.5 Subnet mask In compliance with the FL-net protocol, the subnet mask is fixed at 255.255.255.0. The FL-net user must always use a subnet mask setting of 255.255.255.0. This value has the same network address section and host address section as for Class C. 8.3.6 TCP/IP and UDP/IP communication protocols TCP, UDP, and IP are important protocols that Ethernet uses.
Page 241: Figure 8-15 Fl-Net Data Format Overview
8 APPENDIXES 8.3.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: 1024 bytes maximum User data User data FL-net header UDP header FL-net data UDP segment IP header UDP header...
Page 242: Figure 8-16 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 HEX ASCII 0000 FF FF FF FF FF FF 00 ....E.
Page 243: Figure 8-17 Fl-Net Header
8 APPENDIXES (2) FL-net header format The FL-net header consists of 64 or 96 bytes. 64 to 96 bytes 1024 bytes maximum FL-net header Cyclic/message data Lower layer header FA link data 1500 bytes maximum Figure 8-17 FL-net Header The FL-net header is attached to the beginning of every frame related to the FL-net protocol. 8.3.9 FL-net transaction codes The FL-net offers the following message transmission services: •...
Page 244: 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 59999 Transparent message (LQE500) 0 to 9999 Reserve (LQE502) 10000 to 59999 Transparent message (LQE502)
Page 245: Table 8-5 Transaction Code Receives Processing At The Udp Port (Lqe502)
8 APPENDIXES 8.3.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 (LQE502) For token frame or cyclic For trigger frame or For message frame...
Page 246 8 APPENDIXES 8.4 FL-net Network Management 8.4.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 247: Figure 8-18 Token Flow
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 248: Table 8-6 Token And Data (Lqe500)
8 APPENDIXES (3) Token and data The following six different data patterns are used for token transmission: Table 8-6 Token and Data (LQE500) Pattern Description When no data is involved Only the token is transmitted. Token When only cyclic data is transmitted The cyclic data is transmitted with the token attached to it.
Page 249: Table 8-7 Token And Data (Lqe502)
8 APPENDIXES Table 8-7 Token and Data (LQE502) 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. Cyclic data Token When only cyclic data is transmitted Cyclic data is transmitted and, after the last frame, a token is after being divided into frames transmitted.
Page 250 8 APPENDIXES 8.4.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 251 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 252 8 APPENDIXES <Remarks> 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 253: Table 8-8 Node Status Management Table Overview
8 APPENDIXES 8.4.3 Node status management As outlined in Table 8-8, node status management is exercised with the self-node management table, entering node management table, and network management table. Table 8-8 Node Status Management Table Overview Name Description Self-node management table Manages the self-node settings.
Page 254: Table 8-10 Entering Node Management Table
8 APPENDIXES 8.4.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 255: Table 8-11 Network Management Table
8 APPENDIXES 8.4.6 FL-net status management (1) Basic feature Provides management of parameters related to network status. (2) Management data Table 8-11 Network Management Table Item Length Description Token maintenance node number 1 byte Node that currently holds the token. Variable in 100 µs units.
Page 256: Table 8-13 Reception Management Data For Message Sequence Number Management
8 APPENDIXES (3) Reception management data Table 8-13 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 257: Figure 8-21 Ethernet Components
8 APPENDIXES 8.5 Network Components 8.5.1 Ethernet component list Figure 8-21 shows Ethernet components. Transceiver cable Coaxial cable Ground terminal (AUI cable) Multiport transceiver Repeater Repeater Single-port transceiver Repeater 10BASE-T Transceiver cable (AUI cable) Ground terminal Single-port transceiver Multiport transceiver Figure 8-21 Ethernet Components 8-33...
Page 258: Table 8-14 Ethernet Component List
8 APPENDIXES Table 8-14 Ethernet Component List Product name Manufacturer Model number Remarks FL.NET module Hitachi, Ltd. LQE000 For both S10mini and S10V Transceiver Hitachi Cable, Ltd. HLT-200 Connector-type HLT-200TB Tap-type HBN200TZ HBN200TD Repeater Hitachi Cable, Ltd. HLR-200H Coaxial cable transmission distance extension Multiport transceiver Hitachi, Ltd.
Page 259: Figure 8-22 Transceiver Overview
8 APPENDIXES 8.5.2 10BASE5 components (1) Transceiver The transceiver converts a signal flowing along a coaxial cable (yellow cable) to a signal required for a node or vice versa. Transceivers to be attached to a coaxial cable must be positioned at spacing intervals of an integer multiple of 2.5 m.
Page 260: Figure 8-24 Tap And Coaxial Cable Installation
8 APPENDIXES M6 bolt 30L Backup probe Signal probe Tap cover Coaxial cable Tap body Figure 8-24 Tap and Coaxial Cable Installation Tap connector M6 bolt 14L Transceiver Figure 8-25 Tap and Transceiver Body Installation 8-36...
Page 261: Figure 8-26 Ethernet Transceiver (Tap Type)
8 APPENDIXES Transceiver (tap type) When connecting a tap-type transceiver, make a hole in a coaxial cable, insert a needle into the hole until it comes into contact with the inner conductor, and use a alligator-tooth claw to tear the insulation jacket and make a connection to the shield conductor. The use of special tools is required for transceiver connection.
Page 262: Figure 8-27 Ethernet Transceiver (Connector Type)
8 APPENDIXES Transceiver (connector type) For connector-type transceiver connection, attach a connector to a coaxial cable and then connect the connector to the transceiver. The connector-type transceiver can be connected without using special tools. They can easily be connected and disconnected. Transceiver power is supplied from a node via a transceiver cable.
Page 263: Figure 8-28 Ethernet Multiport Transceiver
8 APPENDIXES Multiport transceiver Unlike the tap-type and connector-type transceivers, which permit the connection of one terminal unit per transceiver, the multiport transceiver permits the connection of two or more terminal units. 4- and 8-port transceivers are frequently used. Coaxial cable Transceiver cable (AUI cable) Transceiver cable...
Page 264: Figure 8-29 Ethernet Repeater
8 APPENDIXES Repeater The repeater is a device that regenerates a transmission signal. It is used to interconnect differing media segments, extend the media segment distance, increase the number of terminal unit connections, or effect cable media conversion. The repeater receives a signal from one of interconnected segments, subjects it to waveform shaping, amplifies it to a predetermined level, and transmits (repeats) it to all the segments that are connected to the repeater.
Page 265: Figure 8-30 Ethernet Coaxial Cable
8 APPENDIXES (2) Coaxial cable The coaxial cable consists of an inner conductor and outer conductor. The outer conductor functions as a shield. The impedance of the coaxial cable used for Ethernet connections is 50 Ω. Typical coaxial cables are the RG58A/U for 10BASE2 and the so-called yellow cable for 10BASE5.
Page 266: Figure 8-32 Ethernet Junction Connector
8 APPENDIXES (4) Junction connector This connector provides a connection between coaxial cables to increase the overall coaxial cable length. In marked contrast to the repeater, which provides segment extension, the junction connector increases the overall cable length for a single segment. If two or more junction connectors are used at one time, the coaxial cable’s electrical resistance may change (it is recommended that you avoid simultaneously using two or more junction connectors).
Page 267: Figure 8-34 Ethernet Coaxial Cable Ground Terminal
8 APPENDIXES (6) Coaxial cable ground terminal This terminal is used to prevent a communication data error from being caused by noise contained in a coaxial cable. Ensure that the coaxial cable ground terminal is connected to a coaxial cable at one point. Provide Class D grounding. Figure 8-34 Ethernet Coaxial Cable Ground Terminal (7) Transceiver cable The transceiver cable is used to connect a node to a transceiver.
Page 268: Figure 8-36 Ethernet 10Base5/10Base-T Converter
8 APPENDIXES (8) 10BASE5/10BASE-T converter This converter is used to connect a cable having a 10BASE5 interface to 10BASE-T. 10BASE-T connectors 10BASE5 connectors (male) Figure 8-36 Ethernet 10BASE5/10BASE-T Converter Coaxial cable Transceiver cable Transceiver (AUI cable) 10BASE-T Figure 8-37 Ethernet 10BASE5/10BASE-T Converter Installation 8-44...
Page 269: Figure 8-38 Ethernet Coaxial/Optical Media Converter/Repeater
8 APPENDIXES (9) Coaxial/optical media converter/repeater The coaxial/optical media converter/repeater converts an electrical signal on a coaxial cable (10BASE5/10BASE2) to an optical signal. Typical examples are the FOIRL (Fiber-Optic Inter-Repeater Link) for inter-repeater connection and the 10BASE-FL for connection to a terminal.
Page 270: Figure 8-39 Ethernet Hub
8 APPENDIXES 8.5.3 10BASE-T components (1) Hub The hub is a line concentrator that has a repeater facility for accommodating twisted-pair cables for 10BASE-T. The hub is available in various types including the one having a 10BASE2 interface or an interface for cascading (making connections in cascade).
Page 271: Figure 8-40 Ethernet 10Base-T Cable
8 APPENDIXES (2) 10BASE-T cable The 10BASE-T cable contains several twisted-pair cables or pairs of stranded copper wires and is covered by an external protective jacket. This cable is divided into the following types: • Shielded STP cables and unshielded UTP cables •...
Page 272 8 APPENDIXES 8.6 FL-net Network Installation Procedures 8.6.1 10BASE5 coaxial cable wiring (1) Cable laying/wiring The cable can be laid and wired by various methods depending on the installation site. Typical methods are enumerated below: • Wall-surface exposed cable wiring •...
Page 273: Figure 8-42 Peeling Off The Coaxial Cable Covering (Pvc Sheath)
8 APPENDIXES (3) Main specifications for coaxial cable installation Table 8-15 shows the main specifications for coaxial cable installation. Table 8-15 Coaxial Cable Specifications Item Specifications Cable laying 100 mm or more in radius Cable clamping 100 mm or more in radius Tension 245 N maximum Cable weight...
Page 274: Figure 8-43 Coaxial Cable Aluminum Tape Removal 1
8 APPENDIXES ② Removing the aluminum tape Thoroughly remove the aluminum tape from this plane. Figure 8-43 Coaxial Cable Aluminum Tape Removal 1 Remove the aluminum tape completely as shown in the above figure. Figure 8-44 Coaxial Cable Aluminum Tape Removal 2 ③...
Page 275: Figure 8-47 Coaxial Cable Shield Treatment And Pin Contact Soldering
8 APPENDIXES ⑤ Soldering of pin contact Thread solder Pin contact Figure 8-47 Coaxial Cable Shield Treatment and Pin Contact Soldering ⑥ Connector attachment Allow a clearance of 1 mm or more between the pin contact and the insulating material. Take care not to cause the pin contact to bite into the insulating material.
Page 276: Figure 8-49 Transceiver Component Names
8 APPENDIXES (c) Installation procedure Marking Coaxial cable Shield pressure- connecting pin Cap screw Tap body Conductor probe Tighten screw Tap frame Transceiver (HLT-200TB) body Tap retaining screw Figure 8-49 Transceiver Component Names 8-52...
Page 277: Figure 8-50 Transceiver Shield Pressure-Connecting Pin Into Tap Body
8 APPENDIXES ① Insert the shield pressure-connecting pins into the tap body. Figure 8-50 Transceiver Shield Pressure-connecting Pin into Tap Body ② Loosen the cap screw to the extent that it does not come off. Figure 8-51 Loosing the Cap Screw of the Transceiver Tap Frame ③...
Page 278: Figure 8-53 Inserting The Transceiver Tap Frame And Coaxial Cable
8 APPENDIXES Insert the tap frame to ensure that the coaxial cable is positioned at the center of the shield pressure-connecting pin. If the cap screw is extremely tilted when tightened to a certain extent, loosen tighten the screw, center the cable, and tighten the screw. Figure 8-53 Inserting the Transceiver Tap Frame and Coaxial Cable ④...
Page 279: Figure 8-55 Mounting The Conductor Probe On A Coaxial Cable
8 APPENDIXES ⑤ Tighten the conductor probe with the dedicated mounting wrench. Figure 8-55 Mounting the Conductor Probe on a Coaxial Cable Tap connection installation is now completed. <Reference> A test method for making sure of a correct connection is described below. •...
Page 280: Figure 8-57 Securing The Transceiver Body And Tap
8 APPENDIXES ⑦ If the shield pressure-connecting pin and conductor probe seem to be improperly positioned, pull them out after their insertion. If they are not accurately inserted, their bends are visible. In such a situation, accomplish centering again, insert the tap retaining screw into the hole in the top of the transceiver body, and tighten it.
Page 281: Figure 8-58 Installing The Connector-Type Transceiver
8 APPENDIXES (7) Transceiver (connector type) installation Same as explained under “(6)-(a) Transceiver (tap type) installation.” (a) Applicable transceiver For the transceiver recommended for use with the FL.NET module, see “8.5.1 Ethernet component list.” (b) Installation procedure ① Finishing the coaxial cable For the procedure for mounting the coaxial connector on a coaxial cable, see item (5), “Installing the coaxial connector.”...
Page 282: Figure 8-59 Connecting The Repeater
Before connecting the transceiver cable, be sure to turn OFF the repeater. Transceiver To another transceiver Female Male Transceiver cable Male Male Female Female Repeater Figure 8-59 Connecting the Repeater ② Applicable repeater For the repeater recommended for use with the S10mini FL.NET module, see “8.5.1 Ethernet component list.” 8-58...
Page 283: Figure 8-60 Repeater Installation Space Requirements
8 APPENDIXES ③ Installation location and space requirements • When installing the repeater, select an appropriate site near a workstation (server) that provides an ease of maintenance (do not select a location above the ceiling or basement of an ordinary office room). Also, ensure that the front/rear, left/right, and upward clearance requirements indicated below are met.
Page 284: Figure 8-61 Junction Connector Insulation
8 APPENDIXES (9) Insulating the terminator and connector The connectors (junction connector and L-type connector) must be insulated as indicated in Figures 8-61 and 8-62. Insulation tape Linear sleeve Insulation sleeve cuttings Coaxial connector Insulation sleeve (N-type) Coaxial cable Figure 8-61 Junction Connector Insulation Insulation tape Coaxial connector (N-type) L-type connector...
Page 285 8 APPENDIXES (11) Transceiver cable installation Figure 8-63 shows a typical installation of the transceiver and transceiver cable. <Wall-mounting example (1)> Coaxial cable Wood board Transceiver Wiring duct cable (made of metal or polyvinyl chloride) Saddle Figure 8-63 Transceiver and Transceiver Cable Wall-mounting Example 1 8-61...
Page 286 8 APPENDIXES <Wall-mounting example (2)> Wood board <Wall-mounting example (3)> Wood board <Wall-mounting example (4)> Figure 8-64 Transceiver and Transceiver Cable Wall-mounting Examples 2 8-62...
Page 287: Figure 8-65 Transceiver And Transceiver Cable Above-The-Ceiling Mounting And Under-The-Floor Mounting Example
8 APPENDIXES <Above-the-ceiling mounting example> <Under-the-floor mounting example> Figure 8-65 Transceiver and Transceiver Cable Above-the-ceiling Mounting and Under-the-floor Mounting Example (a) Applicable transceiver cable For the cable recommended for use with the FL.NET module, see “8.5.1 Ethernet component list.” 8-63...
Page 288: Figure 8-66 Mounting The Insertion Claw In The Ground Terminal Body
8 APPENDIXES (12) Coaxial cable ground terminal installation (a) Applicable ground terminal For the ground terminal recommended for use with the FL.NET module, see “8.5.1 Ethernet component list.” (b) Installation procedure Installing the coaxial cable ground terminal Figure 8-67 shows how to install the coaxial cable ground terminal. For the coaxial cable, provide single-point grounding (Class D or higher) with a ground terminal (G-TM).
Page 289: Figure 8-68 Cutting The Insertion Claw
8 APPENDIXES ③ After tightening the M4 screw, cut off the excess length of the insertion claw. Cut off the excess length of the insertion claw. Figure 8-68 Cutting the Insertion Claw ④ Provide single-point grounding (Class D). Ground terminal (G-TM) Class D or higher grounding Figure 8-69 Mounting the Coaxial Cable Ground Terminal 8-65...
Page 290: Figure 8-70 Removing The Utp Cable Sheath
8 APPENDIXES 8.6.2 10BASE-T (UTP) cable (1) Preparing a 10BASE-T (UTP) able ① Removing the covering (sheath) from the 10BASE-T (UTP) cable Cut about 40 mm of sheath and then loosen the wire strands to rearrange them in proper order. Under normal conditions, a normal cable (straight cable) should be used.
Page 291: Figure 8-72 Inserting The Utp Cable Into The Connector
8 APPENDIXES ③ Inserting the UTP cable into the connector Attach the cable to the connector while retaining the proper arrangement of wires. View the front, top, and bottom surfaces of the cable to check whether the cable is inserted all the way into the connector.
Page 292 8 APPENDIXES 8.7 Grounding the FL-net System 8.7.1 Overview of FL-net system grounding Figures 8-74 and 8-75 show the methods of grounding the FL-net system’s controller control panel with a steel frame of a building. The control panel can be grounded with a building’s steel frame only when the following conditions are met.
Page 293 8 APPENDIXES Building’s steel frame Control High- panel voltage Steel frame circuit panel grounding point PLC, etc. Figure 8-75 Controller Control Panel Grounding Method 2 (Controller’s Dedicated Class D Grounding) 8.7.2 Power supply wiring and grounding For the explanation of the FL-net system’s power supply wiring and grounding, the example in Figure 8-76 indicates the power supply wiring and grounding of the distribution switchboard and controller panel.
Page 294: Figure 8-76 Typical Fl-Net System Power Supply Wiring And Grounding
8 APPENDIXES Distribution Controller control Control Pre- switchboard panel power operational Ry circuit supply PLC, etc. 100 VAC Panel ground Controller ground Panel ground (5.5 mm or more) (5.5 mm or more) Class D Class D Class D grounding grounding grounding Figure 8-76 Typical FL-net System Power Supply Wiring and Grounding 8.7.3 Power supply wiring and grounding for FL-net system network devices...
Page 295 8 APPENDIXES • If the transceiver (AUI) needs power supply from a DC power source (12 VDC, etc.), furnish the network with a dedicated regulated power supply and connect its DC output to the specified terminal on the FL.NET module. The required 100 VAC input power must be supplied from the same insulating transformer with a static shield as for the controller.
Page 296: Figure 8-78 Typical Wiring With Wiring Duct
8 APPENDIXES 8.7.4 Wiring duct/conduit wiring and grounding The examples in Figures 8-78 and 8-79 indicate the wiring duct/conduit wiring and grounding schemes for the FL-net system. As regards wiring work, observe the following instructions: • When using a wiring duct for wiring purposes, furnish a separator to separate the power and signal cables in accordance with their levels.
Page 297: Table 8-17 Fl-Net Installation Work Check Sheet
8 APPENDIXES 8.8 FL-net Installation Work Check Sheet Table 8-17 FL-net Installation Work Check Sheet FL-net Installation Work Check Sheet Communication line name: Area code: Inspection date: Inspector Company: Person in charge: Entry Setup switch Check column column Check that all the connectors are properly locked. Check that each cable bend radius is not smaller than specified.
Page 298: Figure 8-80 Device Communication Information Classification
8 APPENDIXES 8.9 FL-net Profile 8.9.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-80. Node A: Network parameters (setup (communication information for transmission) facility) B: System parameters •...
Page 299: Table 8-18 Details Of Common Parameters
8 APPENDIXES 8.9.2 Details of common parameters Table 8-18 shows the details of common parameters. Table 8-18 Details of Common Parameters Name character string Contents of Data type Parameter name [PrintableString type] parameter [type] (Length), (String) (Length), (Contents) Device profile common 6, “COMVER”...
Page 300: Table 8-19 Details Of Device-Specific Parameters
8 APPENDIXES 8.9.3 Details of device-specific parameters (when used) Table 8-19 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.9.4 System parameter examples (PLC examples) (1) PLC example of system parameter tabular document notation Table 8-20 System Parameter Tabular Document Notation (PLC Examples)
Page 301 8 APPENDIXES (2) Abstract syntax <Type definition> 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 302 8 APPENDIXES <Value definition> 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 303 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 304 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 305: Table 8-21 System Parameter Tabular Document Notation (Cnc Examples)
8 APPENDIXES 8.9.5 System parameter examples (CNC examples) Table 8-21 shows CNC system parameter examples. Table 8-21 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 306 8 APPENDIXES (1) Abstract syntax <Type definition> 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 307 8 APPENDIXES <Value definition> 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”,...

This manual is also suitable for:

S10v Fl.net Lqe500 Lqe502

Hitachi S10mini User Manual

1 Overview

2 Fl.net Module

3 Fl.net Module Installation

4 Fl.net Module Wiring Procedures

5 User Guide

Quick Links

Related Manuals for Hitachi S10mini

Summary of Contents for Hitachi S10mini