Mitsubishi Electronics fx3u manuals

284 pages6.46 Mb

3SAFETY PRECAUTIONS
- DANGER
- CAUTION
- [Design Precautions] DANGER
- 4[Design Precautions]
- [Installation Precautions]
- CAUTION
- 5[Wiring Instructions] DANGER
- CAUTION
  - 11A - 9 A - 9
  - 14How to use this manual
  - (1) Features and utility lists
  - (2) Processing required prior to starting the operation of the Ethernet module
  - 15(3) Connection between the Ethernet module and external devices
  - (4) Details on the data communication functions
  - (5) Data communication functions and programming
  - (6) Checking for error occurrences and taking corrective actions
  - FX Configurator-EN-L (FX3U-ENET-L Configuration tool)
    - 16A - 14 A - 14
  - 171
  - 1OVERVIEW
    - 1.1 Overview of the Ethernet Module
    - 20(3) Sending by e-mail (Details are explained in Chapter 10)
    - 231.3 Software Configuration
    - (1) TCP (Transmission Control Protocol)
  - 262
  - 2 SYSTEM CONFIGURATIONS
    - 27SYSTEM CONFIGURATIONS2
    - 2.2 Devices Required for Network Configuration
    - (1) Connection using the 100BASE-TX
    - 28SYSTEM CONFIGURATIONS2
    - (2) Connection using the 10BASE-T
  - 293
  - 3 SPECIFICATIONS
    - 3.1 Performance Specifications
      - 303 - 2
      - The following explains each of the transmission specification items.
      - 3 - 2
      - [Connecting using the 10BASE-T] [Connecting using the 100BASE-TX]
    - 313.2 Data Codes for Communication
    - 33(1) Communicability with external devices using various functions
    - (2) Relationship with additional functions
      - 3 - 6
    - 343.4 Ethernet Module Function List
      - Checks that the Ethernet module is working and can communicate normally.
      - This section shows a list of Ethernet module functions.
    - (1) Basic functions of the Ethernet module
    - (2) Additional functions of the Ethernet module
      - The following table lists the additional functions of the Ethernet module that can be used.
    - (3) Status check of the Ethernet module
      - 3 - 7
    - 353.5 List of Setting Items for Ethernet Modules
      - The following table lists the parameter setting items that are set using Ethernet Module.
      - Parameters set in FX Configurator-EN-L are saved in the Ethernet module's flash ROM.
    - 363.6 List of Applications and Assignments of the Buffer Memory
    - (1) Configuration of the buffer memory
      - 3 - 9
    - 37(2) Assignments of the buffer memory
      - b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
      - 383 - 10
      - 393 - 11
      - (b) Communication parameter setting area (BFM #32 to 102)
      - 403 - 12
      - 413 - 13
      - (c) Communication status storage area (BFM #103 to 226)
      - 423 - 14
      - 433 - 15
      - (d) Error log partition area (BFM #227 to 511)
      - 443 - 16
      - 453 - 17
      - (e) Router relay parameter setting area (BFM #512 to 1599)
      - 463 - 18
      - (f) Open/close control (BFM #1600 to 1663)
      - 473 - 19
      - 483 - 20
      - (g) Fixed buffer area (BFM #1664 to 9855)
      - 493 - 21
      - (h) Mail send parameter settings (BFM #9856 to 20479)
      - 503 - 22
      - *1 (example)192. 168. 0. 10 C0 A8 00 0A 4) 3) 2) 1) SMTP : BFM#9922 POP3 : BFM#9955
      - H L 2) 1) SMTP : BFM#9923 POP3 : BFM#9956 4) 3)
      - 513 - 23
      - (i) Connection status storage area (BFM #20480 to 22639)
      - 523 - 24
      - (j) E-mail status storage area (BFM #22640 to 31999)
        to b7 b0
        Day of the week (0 to 6)
        
        Month (01 to 12
        b7 b0
        Hour (00 to 23HDate (01 to 31H) Second (00 to 59HMinutes (00 to 59 H)
        
        to
        to SUN:0 to SAT:6
      - 533 - 25
  - 544
  - 4 SETTINGS AND PROCEDURES PRIOR TO OPERATION
    - 4.1 Loading and Installation
    - 4.1.1 Handling precautions
  - DANGER
  - 554
    - 4.1.2 Installation environment
  - CAUTION
    - 564.2 Settings and Procedures Prior to Starting the Operation
      - 4 - 5
    - 584.3 Components of the Ethernet Module
      - This section shows the components of the Ethernet module.
    - 59(1) LED display contents
    - 4.4 Connecting to the Network
  - 60CAUTION
    - 614.4.1 Connecting to the 10BASE-T/100BASE-TX network
      - 4 - 10
    - 634.6 Operational Settings
      - This section explains how to set the operations parameters.
    - (1) Communication data code (BFM#24 b1)
    - 65(4) Initial Timing (BFM#24 b8)
    - 66(5) IP Address settings - IP address (BFM #0 to 1)
    - 674.7 Self-Diagnostic Tests
    - 4.7.1 Self loopback test
    - 684.7.2 Hardware test (H/W Test)
    - 4.8 Maintenance and Inspection
    - 4.8.1 Maintenance and inspection
  - 69DANGER
  - CAUTION
    - 704.8.2 Installing and uninstalling the module
  - 715
  - 5 COMMUNICATION PROCEDURE
    - 5.1 Overview of the Communication Procedure
      - 725 - 2
    - 735.2 Initial Processing
    - 5.2.1 Initial processing
    - (1) Parameters required for initial processing
    - (2) Confirmation of initial processing result
      - 5 - 4
    - 745.2.2 Initial settings
      - *1 Details are explained in Section 10.6.
      - This section explains the initial settings.
    - 75(1) Timer setting - TCP ULP timer (BFM#4)
    - (2) Timer setting - TCP zero window timer (BFM#5)
    - (3) Timer setting - TCP resend timer (BFM#6)
    - (4) Timer setting - TCP end timer (BFM#7)
    - 805.2.3 Re-initialization
    - (1) Purposes of performing re-initialization
      - 5 - 11
    - 81(2) Programming and timing for re-initialization
    - 82(3) Operation for re-initialization
    - 835.3 Router Relay Parameter
    - (1) Router relay function (BFM#2 b4,b5)
    - 84(2) Subnet mask pattern (BFM#512, 513)
    - (3) Router IP address (BFM#514, 515)
    - 855.4 Confirming the Completion of the Initial Processing
    - 865.4.1 PING command (Personal computer Ethernet module)
    - 875.4.2 Loop back test (Communication using MC protocol)
    - 885.5 Open Settings
    - 5.5.1 Fixed buffer connection (connection No. 1 and connection No. 2)
    - (1) Protocol (connection numbers 1, 2; BFM#32, 33 b8)
      - 5 - 19
    - 89(2) Open system (connection numbers 1, 2; BFM#32, 33 b15, b14)
      - PLC main unit PLC main unit
    - (3) Fixed buffer (connection numbers 1, 2; BFM#32, 33 b0)
      - Ethernet module Ethernet module
    - 90(4) Fixed buffer communication (connection numbers 1, 2; BFM#32, 33 b9 to b10)
    - (5) Pairing open (connection numbers 1 only; BFM#32 b7)
    - 91(6) Existence confirmation (connection numbers 1, 2; BFM#32, 33 b1)
    - (7) Local station Port No. (connection numbers 1, 2; BFM#40, 47)
    - (8) Destination IP address (connection numbers 1, 2; BFM#41 to 42, 48 to 49)
    - 92(9) Destination Port No. (connection numbers 1, 2; BFM#43, 50)
    - 945.5.2 MELSOFT/MC protocol connections (connection No. 3 and connection No. 4)
    - (1) Local station Port No. (connection numbers 3, 4; BFM#54, 61)
    - (2) Destination IP address (connection numbers 3, 4; BFM#55 to 56, 62 to 63)
    - (3) Destination Port No. (connection numbers 3, 4; BFM#57, 64)
    - 955.6 Open Processing/Close Processing of the Connection
    - (1) Open processing
    - 96(2) Close processing
      - 5 - 27
    - 975.6.1 Active open processing/close processing
      - <<Open processing for connection No.1>>
    - 101Program example
      - 1025 - 32
    - 1035.6.2 Passive open processing/close processing
    - (1) When "Always wait for OPEN" is selected in the operational setting
    - 104(2) When "Do not wait for OPEN" is selected in the operational setting
      - 1055 - 35
    - 108Program example
      - 1095 - 39
      - 1115 - 41
        <<Open processing for connection No.1>>
        <<Close processing for connection No.1>>
    - 1135.7 Pairing Open
    - 5.7.1 Pairing open
    - 1165.8 Hub Connection Status Monitor Function
    - (1) Hub connection status area (BFM#201)
    - (2) Disconnection detection count storage area (BFM#20995)
    - FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
  - 1176
  - 6 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)
    - 6.1 Control Method
      - 6 - 3
    - 119FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
      - 6 - 3
    - 6.2 Sending Control Method
      - 6 - 6
    - 122FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
      - Data receiving
      - Response
      - 6 - 6
    - 6.3 Receiving Control Method
    - 6.3.1 Receive processing with the main program
      - ACK (only TCP) 5)
      - ACK (only TCP) 2)
      - 1) 3) 4) 6)
    - 124FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
    - 6.4 Data Format
    - 6.4.1 Header
      - 6 - 9
    - 125FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
      - (b) Communication using ASCII code
      - 6 - 9
    - 6.4.2 Application data
    - (1) Format
      - (a) Communication using binary code
      - 6 - 10
    - 126FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
      - 6 - 10
    - (2) Subheader
    - 127FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
    - (3) Data length setting
    - (4) Text (command)
      - 6 - 12
    - 128FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
      - 6 - 12
      - (b) Communication using ASCII code
    - (5) End codes
    - 129FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
    - 6.5 Programming
    - 6.5.1 Precautions when creating programs
    - 130FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST
    - 6.5.2 Fixed buffer communication program example (with the procedure exist control method)
      - 6 - 17
      - (Send program) (See Subsection 5.6.1)
      - 133Open processing program
        1346 - 18
        (Receive program)
    - FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
  - 1357
  - 7 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)
    - 7.1 Control Method
      - 7 - 4
    - 138FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
      - 7 - 4
    - 7.2 Sending Control Method
      - 7 - 6
    - 140FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
      - 7 - 6
    - 7.3 Receiving Control Method
    - 7.3.1 Receive processing with the main program
    - 142FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
    - 7.4 Data Format
    - (1) Header
    - (2) Application Data
    - 143FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
    - 7.5 Programming
    - 7.5.1 Precautions when creating programs
    - 144FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE
    - 7.5.2 Fixed buffer communication program example (with the no procedure control method)
      - 1477 - 13
      - (Send program)
      - 1487 - 14
      - (Receive program)
      - Program example for the unit No. 0
  - 1498
  - 8 COMMUNICATION USING MC PROTOCOL
    - 8.1 Data Communication Function
    - 8.1.1 Accessing the PLC using MC protocol
    - (1) Data read/write
    - 150(2) Remote control of the PLC
    - 8.1.2 How to Read the Control Procedures of the MC Protocol
    - (1) Transmission of command messages
    - (2) When a normal completion response message to a command message cannot be received
    - 1518.1.3 Access Timing on the PLC Side
    - 1528.1.4 PLC setting for performing data communication
    - 8.1.5 Precautions on Data Communication
    - (1) Precautions that should be observed when performing data communication via the Ethernet module
  - 1549
  - 9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL
    - 9.1 Message Formats and Control Procedures
    - 9.1.1 How to read the command reference section
    - (1) When an external device reads data from the PLC
    - 155(2) When an external device writes data to the PLC
    - 1569.1.2 Message format and control procedure
    - (1) Message format
      - 9 - 4
    - 157(2) Control procedure
      - Exists only when the complete code is "5B."
      - Abnormal code
      - PLC side
      - Text (Command)
      - External device side (Response message) (Normal completion)
        Text (Response)
      - (Abnormal completion)
        Text (Response)
        When complete code 5B
      - 1589 - 5
      - 2) When writing data to the local station PLC from the external device side
      - External device side PLC side (Command message)
      - PLC side External device side (Response message) (Normal completion)
      - (Abnormal completion)
      - PLC side External device side (Response message) (Normal completion) (Abnormal completion)
      - 1599 - 6
      - 2) When writing data to the local station PLC from the external device side
        PLC side External device side (Response message) (Normal completion) (Abnormal completion)
    - 1609.1.3 Contents of data designation items
    - (1) Header
    - (2) Subheader
    - (3) PC number
    - (4) Monitoring timer
    - (5) Character field (command)
    - 161(6) Character field (response)
    - (7) Complete code
    - (8) Abnormal code
      - 9 - 9
      - (b) The order when receiving a response (external device Ethernet module)
    - 162(1) Format when communicating in binary code
      - (a) The order when sending a command (external device Ethernet module)
      - 9 - 10
    - 163(2) Format when communicating in ASCII code
      - (b) The order when receiving a response (external device Ethernet module)
      - (a) The order when sending a command (external device Ethernet module)
      - 9 - 11
    - 1649.1.4 Character area transmission data
      - MMMMMM MM MM MM MM MM MMMMMMMM MM MM MM MM
      - 010011001101
      - 10101011000100100011
      - Indicating the ON/OFF status of 32 points from M16
    - (1) Data communication using ASCII code
      - AB123 4CD
        3130 29 28 27 26 25 24 23 22 21 20 19 18 17 16 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
        The device point is "02" in 16-point units.
        1: Indicates ON 0: Indicates OFF
      - 1659 - 12
      - Indicating the storage contents of data registers D350 and D351
    - 166(2) Data communication using binary code
      - 9 - 15
    - 1689.2 List of Commands and Functions for The MC protocol
      - *1 When the double word data is read using the user program, etc., read out the 32bit data at once.
      - The following table lists the commands and functions when an external device accesses the PLC.
      - 9 - 16
    - 1699.3 Device Memory Read/Write
    - 9.3.1 Commands and device range (1) Commands used for reading from and writing to the device memory
      - 9 - 17
    - 170(2) Designation method and accessible range of devices.
      - (b) The following table outlines the device codes and numbers.
    - Device list
      - B15 B0 B31 B0 to to Device code Device number (Set in hexadecimal)
        [Example] In case of D100 D100 = 4420 00000064 Device number (hexadecimal) Device code
      - 9 - 19
    - 1729.3.2 Batch read in bit units (command: 00)
      - Use the designation "00H" when the number of device points is 256 points.
      - Reading the on/off status of M100 to M111 of the PLC on which the FX3U-ENET-L is loaded.
      - 1739 - 20
      - 9 - 21
    - 1749.3.3 Batch write in bit units (command: 02)
      - Writing the on/off status of M50 to M61 of the PLC on which the Ethernet module is loaded.
      - 1759 - 22
      - 9 - 23
    - 1769.3.4 Test in bit units (random write) (command: 04)
      - Specifying Y45 to ON, M60 to OFF, and S38 to ON at the PLC on which the Ethernet module is loaded.
      - 1779 - 24
      - 9 - 25
    - 1789.3.5 Batch read in word units (command: 01)
      - 1799 - 26
      - 9 - 27
      - 32 points x 2 = 64 word
      - 4 bytes x 32=128 bytes
        L - - - - H
        L - H L - H L - H L - H
    - 180(1) When communicating in binary code
      - 12345678=00BC614E
      - 45678912=02B90140
        CN220
        External device side
        Head device
        Number of device points
        Head data
        Last data
      - 9 - 28
    - 181(2) When communicating in ASCII code
      - Low 16bit High 16bit Low 16bit High 16bit
      - code
      - Complete
      - PC No.
      - (4 bytes x 2) x 32=256bytes
      - Last data
      - H - - L H - - L
      - C
      - D
      - 0 0
      - 0
      - 4 E 0 0 0
      - 3
      - 4
      - 4 0
      - 12345678=00BC614E
      - 45678912=02B90140
      - H L
      - 0 0
      - H - - - - - - - - - - L 6 1 4 E 0 0 B C
      - H - - L H - - L 0 1 4 0 0 2 B 9
        External device side
        PLC side
        Monitoring timer
        Head device Number of device
        points
        Head data
      - 9 - 29
    - 1829.3.6 Batch write in word units (command: 03)
      - Writing data to D100 to D102 of the PLC on which the Ethernet module is loaded.
      - 1839 - 30
      - 9 - 31
      - 32 points x 2 = 64word
        L - - - - H
        L - H L - H L - H L - H
      - CN220
      - 45678912=02B90140
      - 12345678=00BC614E
    - 184(1) When communicating in binary code
      - L
      - H
      - (2 bytes x 2) x 32 = 128 bytes
      - External device side
        Head device
        Number of device points
        Head data Last data
      - 9 - 32
    - 185(2) When communicating in ASCII code
      - x 2)
      - (4 bytes
      - points
      - PC No.
      - code
      - Complete
      - 32 points x 2 = 64word
      - H - - L H - - L H - - L H - - L
      - 45678912=02B90140
      - 12345678=00BC614E
      - H L 4 0
      - 0 0
      - H - - - - - - - - - - L 4 3 4 E 0 0 0 0 0 0 D C 6 1 4 E 0 0 B C 0 1 4 0 0 2 B 9
        High16bitLow16bitHigh16bitLow16bit
        External device side
        PLC side
        Monitoring timer Head device Number of device
        x 32 = 256 bytes Head data Last data
      - 9 - 33
    - 1869.3.7 Test in word units (random write) (command: 05)
      - 1879 - 34
      - 9 - 36
    - 1899.4.2 Remote RUN (command: 13) / Remote STOP(Command: 14)
      - Monitoring
      - PLC side
      - For remote RUN 93
      - For remote STOP 94
      - For remote RUN 13
      - For remote STOP 14
        Monitoring
      - PLC side
        /94
    - (2) Executing remote RUN while communicating in ASCII code
    - (1) Executing remote RUN while communicating in binary code
      - (Data name)
        93
        FF
        0A
        00
        LH
        13
        /14
        00
      - External device side (Example) (Data name) (Example)
      - *
        External device side
        For remote RUN
      - 9 - 38
    - 1919.4.3 PLC model name read (command: 15)
    - (1) Data communication in binary code
    - (2) Data communication in ASCII code
      - Distinguish the PLC model name by the model name code. "F3
    - 1929.5 Loopback Test
    - 9.5.1 Loopback test (command: 16)
    - (1) Performing a loopback test while communicating in binary code
      - 9 - 40
    - 193(2) Performing a loopback test while communicating in ASCII code
  - 19410
  - 10 USING THE E-MAIL FUNCTION
    - 10.1 E-mail Function
    - 10.1.1E-mail send by the PLC
    - 19610.2 Configuration and Environment of the Applicable System
    - 19710.3 Precautions for Using the E-mail Function
      - 10 - 5
    - 19810.4 E-mail Specifications
      - The following table lists the specifications of the e-mail function.
      - 10 - 6
    - 19910.5 Processing Procedure of the E-mail Function
      - The following flowchart illustrates the procedure that is required before sending e-mails:
    - 20010.6 E-mail Settings
    - 202(3) Send mail address setting
    - 20310.7 Sending E-mail (Attached Files) by the PLC
    - 10.7.1When sending data as an attached file
      - 20410 - 11
      - The table below shows the buffer memory to be used for sending mail.
      - 20510 - 12
      - Program example for the unit No. 1
      - 20610 - 13
    - 20910.7.2Contents of the attached files
    - 21010.8 Sending E-mail (Main Text) by the PLC
    - 10.8.1When sending data as main text of e-mail
      - 21110 - 18
      - The table below shows the buffer memory to be used for sending mail.
  - 21311
  - 11 TROUBLESHOOTING
    - 11 - 2
    - 21411.1 How to Check Errors Using LED Displays
    - 11.1.1Checking error display
      - 21511 - 3
    - 21611.1.2How to turn off COM.ERR LED and to read/clear error information
    - (1) How to turn off [COM.ERR] LED using buffer memory
      - COM.ERR off
    - (3) Reading buffer memory to read error information
      - 11 - 5
    - 217(4) How to clear error information by writing to buffer memory
      - Writing to BFM#31800 to 31802 allows clearing the error information and turning off COM.ERR.
    - 21811.2 How to Check an Error Through FX Configurator-EN-L
    - (1) Ethernet diagnostics (See Section 11.2.2.)
    - (2) Buffer memory batch monitor (See Section 11.3.)
      - 11 - 7
    - 21911.2.1Buffer memory that can be monitored with the FX Configurator-EN-L diagnostic function
      - 22011 - 8
    - 22111.2.2Ethernet diagnostics
      - Diagnostics Diagnostics
    - 22211.3 Checking the error information by the buffer memory batch monitoring function
      - Start Monitor
        11 - 11
    - 22311.4 Err or Co de Li st
    - 11.4.1Type of error incident
      - The details of errors and error handling procedures are described.
    - 225(5) Error log area (BFM#227 to 372)
    - 227(6) E-mail status storage area (BFM#22640 to 24575)
      - 11 - 17
    - 22911.4.2End codes (Complete codes) returned to an external device during data communication
    - 23011.4.3Abnormal codes returned during communication using MC protocol
    - 23111.4.4Error codes stored in the buffer memory
      - 23211 - 20
      - 23311 - 21
      - 23411 - 22
      - *1 When this error occurs, the COM.ERR light turns on, but turns off again about one second later.
      - 11 - 22
      - 23511 - 23
      - 23611 - 24
      - 23711 - 25
      - 23811 - 26
      - 23911 - 27
      - 24011 - 28
      - 11 - 32
    - 24411.5 Troubleshooting Flowchart
      - 24511 - 33
      - [example] When communication is performed using a fixed buffer.
      - 24711 - 35
    - 24811 - 36
    - 24911 - 37
    - 1)
    - Perform error code reading while the connection is open.
    - 25011 - 38
    - 11 - 40
    - 25211.5.3Errors in communication using MC protocol
      - 11 - 42
    - 25411.5.4Sending errors during e-mail communication
  - 255 App
  - APPENDIX
    - Appendix 1 Processing Time
  - 256App
    - (2) Minimum processing time of communication using MC protocol (batch read and batch write)
    - 258Appendix 2 ASCII Code List
    - Appendix 3 References
    - 259Appendix 4 Program Examples
    - (1) Receive processing of target device
    - Background
    - 260Appendix 4.1 Program example for communication using MC protocol -1
    - (1) Execution environment of the program example
    - 261(3) FX Configurator-EN-L settings
    - 262(4) Program on the external device side
    - (2) Outline of the procedure for calling the socket routine
    - REMARK
    - 269(4) Window example (Form 1)
    - (5) Sample program (Form 1)
      - App - 19
    - 273Appendix 5 Differences between the Ethernet and the IEEE802.3
      - Destination address Source address Length Data (46 to 1500 bytes) FCS
      - The following shows the Ethernet header in the data link layer supported by the Ethernet module.
    - (1) Ethernet
    - (2) IEEE802.3
    - Appendix 6 ICMP Protocol Supported by the Ethernet Module
      - Destination address Source address Type Data (46 to 1500 bytes) FCS
      - App - 20
    - 274Appendix 7 Setting Value Recording Sheets
      - Recording sheet 1
      - 275App - 21
      - Recording sheet 2
      - 276App - 22
      - Recording Sheet 3
      - 278App - 24
      - Recording sheet 5
    - 281Warranty
      - 1. Gratis Warranty Term and Gratis Warranty Range
      - [Gratis Warranty Term]
      - [Gratis Warranty Range]
      - 2. Onerous repair term after discontinuation of production
      - 3. Overseas service
      - 4. Exclusion of loss in opportunity and secondary loss from warranty liability
      - 5. Changes in product specifications
      - 6. Product application