https://www.truck-manuals.
https://www.truck-manuals.
First Edition, November 2005, SVE-3-001(B) All Rights Reserved, Copyright © 2005, 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. Printed in Japan. BI-SN-YS (FL-MW20, AI8.0) https://www.truck-manuals.
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. Be sure that the person(s) responsible for maintenance receives and understands this manual completely. This manual divides the safety precautions into DANGERs and CAUTIONs.
1. Installation Precautions 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. Properly tighten the screws.
CAUTION The module may become defective due to a high temperature, which may result from heat dissipation failure. It may also malfunction due to electromagnetic interference from nearby equipment. For heat dissipation and electromagnetic radiation minimization, provide the specified clearances among the module, its enclosure, and neighboring equipment. 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.
PROHIBITION Do not take the insulation sheets off the mount base. These insulation sheets electrically insulate the modules from the mount base. PROHIBITION Do not disassemble or modify the module. Failure to observe this precaution may result in a fire or cause the module to become defective or malfunction. https://www.truck-manuals.
2. Wiring Precautions 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. Surge voltage may cause malfunction or damage to this product. When you connect coils, such as relays, to the PCsOK output circuit, be sure to add surge-absorbing diodes or the equivalent to that circuit.
REQUIREMENT Insulate the mount base from the enclosure. To keep the mount base insulated, avoid removing the insulation sheets that are supplied with the mount base. The LG is a ground terminal for power supply noise. The FG and SHD are ground terminals for the noise in the remote I/O, communication module and other external interface lines. To avoid interference between the ground terminals, separately ground the LG and FG.
3. Operating Precautions REQUIREMENT Before terminating this product (by shutting down or resetting), check that all the peripheral equipment is already stopped or will not be affected by the termination. Failure of an installed module may damage the contents of memory spaces. Be sure to make a backup copy of any important data in memory. Overheating may cause a fire or unit failure.
CAUTION Do not use a transceiver, cellular phone, or similar device near the unit because unit malfunction or system failure may occur due to noise. The parts, which used gallium arsenic (GaAs) for a photo coupler and LED, are included in this product. GaAs is specified as a harmful object by law. Take special care when handling the product, in particular, scrapping it. Before scrapping the product, ask a professional waste disposal dealer in charge of scrapping work.
This manual provides troubleshooting information for the following hardware and program products: (SVE-3-001(B)) LPU (LQP510) CMU (LQP520) Power supplies (LQV000/LQV100/LQV020) ET.NET (LQE520/LQE720) SD.LINK (LQP530) OD.RING (LQE510/515) FL.NET (LQE500/502) CPU LINK (LQE550) RS-232C (LQE560) RS-422 (LQE565) J.NET J.NET-INT IR.LINK D.NET SV.LINK EQ.LINK RI/O J.Station IR.Station D.
Description of added changes Page New information is added to Section 3.4, “Backing Up and Restoring.” 64 Section 3.16, “ET.NET (LQE720) Error Information,” is newly added. 165 Section 3.17, “Error Freeze Information,” is newly added. 168 Section 3.18, “Memory Dump Procedure,” is newly added. 173 Section 3.19, “Network Information,” is newly added. 177 Section 3.20, “Network Maintenance Commands,” is newly added.
Revision record Revision No. B Revision Record (revision details and reason for revision) First Edition Month, Year November 2005 https://www.truck-manuals.
PREFACE Thank you for purchasing Hitachi’s programmable controller (S10V). This manual provides information on how to perform troubleshooting correctly when a problem arises with the product. Please read this manual carefully when troubleshooting the product, and use the product properly. The S10V product is available in two types: standard model and environmentally resistant model. The environmentally resistant model has thicker platings and coatings than those for the standard model.
CONTENTS 1 PRELIMINARY CHECKING.............................................................................................. 1 2 TROUBLESHOOTING........................................................................................................ 2.1 Troubleshooting Procedure ............................................................................................... 2.2 Troubleshooting Maps ......................................................................................................
J.NET, J.NET-INT The TX and RX indicators (LEDs) do not come on normally.......................................... 22 The ERR indicator (LED) is lit. ........................................................................................ 23 Other problems.................................................................................................................. 23 IR.LINK The TX and RX indicators (LEDs) do not come on normally..........................................
D.Station The MNS indicators (LEDs) do not come on normally.................................................... Other problems ................................................................................................................. A.INPUT Analog input 37 37 Input data cannot be input normally. ................................................................................ 38 A.INPUT Scan-type analog input Input data cannot be input normally. ...................................................
3.5 Performance....................................................................................................................... 3.6 Address Space Maps ......................................................................................................... 3.7 Registers ............................................................................................................................ 3.7.1 Ladder instructions and usable registers...............................................................
4 ERROR LOG INFORMATION ........................................................................................... 4.1 Displaying Error Log Information .................................................................................... 4.2 Error Log Information and Required Actions ................................................................... 4.2.1 LPU (model LQP510) error log info and required actions ....................................... 4.2.
(9) System down -- kernel trap........................................................................................ (10) System down -- built-in subroutine error .................................................................. (11) System down -- built-in subroutine stoppage............................................................ (12) ADT error .................................................................................................................. (13) Memory error........................
FIGURES Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 4-1 Figure 4-2 Address Space Map of the LPU Unit.................................................................. Address Space Map to the PIO-RAM Bit Area .................................................. Address Space Map to the PIO-RAM Word Area (1) ........................................ Address Space Map to the PIO-RAM Word Area (2) ........................................
TABLES Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 3-8 Table 3-9 Table 3-10 Table 3-11 Table 3-12 Table 3-13 Table 3-14 Table 3-15 Table 3-16 Table 3-17 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table 4-7 Table 4-8 Table 4-9 Table 4-10 Table 4-11 Table 4-12 Memory Areas Subjected to Backing up and Restoring ....................................... Backup Areas Used by Optional-Module Setting Tools ....................................... Backup Areas ........
Table 4-16 Table 4-17 Table 4-18 Table 4-19 Table 4-20 Table 4-21 Table 4-22 Table 4-23 Table 4-24 Table 4-25 Table 4-26 Table 4-27 Table 4-28 Table 4-29 Table 4-30 Table 4-31 Table 4-32 Table 4-33 Table 4-34 Table 4-35 Table 4-36 Table 4-37 Table 4-38 I/O Error Message Format .................................................................................... Error Codes, Subtitles, and Their Meanings (for I/O Errors) ............................... Error Detail Data for ROM Board Errors .................
1 PRELIMINARY CHECKING https://www.truck-manuals.
1 PRELIMINARY CHECKING Perform the following preliminary checks to eliminate obvious problems before troubleshooting the product: Check that terminating resistors are connected to both ends of the inter-LPU links chain established. Both ends of the inter-LPU link line must be terminated with terminating resistors. Terminating resistor LPU LPU LPU Terminating resistor Check that terminating resistors are connected to both ends of the remote I/O line.
1 Is the cabling correct? Check the cables for disconnection or incorrect connection. Are the modules mounted correctly? Check that no set screws are loosened. -3- https://www.truck-manuals.
1 PRELIMINARY CHECKING Is grounding correct? • Do not ground the D.NET module in the same place where high-voltage equipment is grounded. They must be grounded in separate places. • Perform grounding work conforming to Class D* or higher grounding standard. Are the LG and FG separated? • Be sure to separate the LG from the FG or vice versa because power noise enters the FG via the LG. Failure to observe this rule may result in an equipment malfunction. • Ground the LG at the power supply side.
2 TROUBLESHOOTING https://www.truck-manuals.
2 TROUBLESHOOTING 2.1 Troubleshooting Procedure A problem occurs. Check out indications on the individual modules’ LEDs, error log, and the ON/OFF status of the load. Is an abnormal module found? NO YES Perform all necessary checking and take appropriate remedial action, as described in Section 2.2, “Troubleshooting Map.” Is the problem solved? NO YES Fill out a trouble report form exemplified in Section 5.2, “Trouble Report.” End of troubleshooting Contact your local source of supply.
2 TROUBLESHOOTING 2.2 Troubleshooting Maps The troubleshooting maps provided in this section serve as a guide to help users troubleshoot their systems as quickly as possible in the event of a problem. Each troubleshooting map has the following general format: Problematic symptom or condition Module name LPU Module model LQP510 None of the LED indicators comes on. Check if: What to do The power supply module is operating abnormally.
2 TROUBLESHOOTING LPU LQP510 None of the LED indicators comes on. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The LPU and/or the power supply module is installed incorrectly. If true, install them correctly. The supply voltage from the power supply module is abnormal. If true, replace the power supply module. The ERR indicator (LED) is lit.
2 TROUBLESHOOTING The remote I/O process produces outputs but does not accept inputs. Check if: What to do A terminating resistor(s) are installed between the following terminals for the LPU: If not, install them. RI/O1→ 100 Ω : Terminals A6 and A7 150 Ω : Terminals A5 and A7 RI/O2→ 100 Ω : Terminals B5 and B6 150 Ω : Terminals B4 and B6 The PCs OK output is OFF. Check if: What to do The LADDER switch is set in STOP position. If true, set it in RUN position.
2 TROUBLESHOOTING The sequence program does not run. Check if: What to do The LADDER switch is set in STOP position. If true, set it in RUN position. The LPU module’s ERR indicator (LED) is lit. If true, check the error log to see if an LPU error is recorded. If so, troubleshoot according to the instructions given under “4 ERROR LOG INFORMATION.” The SIMU indicator (LED) is lit. If true, change the LADDER MODE to “NORM” in the S10V BASE SYSTEM. External STOP input is in process.
2 TROUBLESHOOTING CMU LQP520 Data communication is not possible with the Tool (personal computer or PC). Check if: What to do In cases where data communications are carried out by using the CMU module whose IP address is set to a fixed value of “192.192.192.1”: The ST.No. U and L switches are both set in Fposition. If not, set both in F-position. The IP address of the Tool is set to a value of “192.192.192.***”, where *** is a number in the range 002 to 254. If not, set it to a value of “192.192.
2 TROUBLESHOOTING PS Power supply LQV000 LQV020 LQV100 The POWER ON indicator (LED) does not come on. Check if: What to do The power cable is connected properly. If not, connect it properly. (For details, refer to the “S10V USER’S MANUAL BASIC MODULES (manual number SVE-1-100)).” The power cable is broken. If true, replace the cable. The external power supply is normal (in terms of voltage and wave form). If not, make it normal. - 12 - https://www.truck-manuals.
2 TROUBLESHOOTING FL.NET LQE500 LQE502 The TX and RX indicators (LEDs) do not come on normally. Check if: What to do The MODU number is set correctly. If not, set it correctly. The set IP address of a remote node is duplicated with that of another node. If true, set unique IP addresses for both nodes. The IP address of the local node is set correctly. Set the same network address for both the local and remote nodes. The recommended network address is “192.168.250”. The FL.
2 TROUBLESHOOTING Common network problems and troubleshooting (1) Network-related problems (communication not possible) and troubleshooting Symptom Communication not possible Item to be checked Power supply Connection of communication cable and transceiver Connection of transceiver cable and transceiver Connection of transceiver cable and other device Check if: What to do Some equipment’s main power indicator(s) are not lit. The power indicator of the AUI’s power supply unit is lit.
2 TROUBLESHOOTING (2) Network-related problems (communication unstable) and troubleshooting Symptom Communication not possible at all, or possible but unstable Item to be checked Communication path Check if: What to do The external conductor of the coaxial cable is grounded at one place. The shield wire of the AUI cable is grounded properly. There is any station not responding correctly to a given ping command. The collision indicator is lit frequently.
2 TROUBLESHOOTING (3) IP address checking using a PC’s Ping function Whether a given FL.NET module is networked properly or its IP address is set correctly can be checked by using a special function of a Windows® machine (PC), commonly known as Ping, rather than by using a special tool, such as the FL.NET network analyzer. The description below gives an outline of check operations using the Ping function. If an IP connection is used with the FL.
2 TROUBLESHOOTING FL.NET usage precautions There are some precautions that must be observed when using the FL.NET module. These precautions are listed below along with the restrictions in the table below. For information on the standard related to FL.NET communication paths, refer to the FL.NET (manual number SVE-1-101) or IEEE802.3 standard. Do not carry data traffic from other Ethernet networks on the FL.NET communication cable. Do not connect the FL.NET module to any router.
2 TROUBLESHOOTING OD.RING, SD.LINK LQE510 LQE515 LQE530 The TX and RX indicators (LEDs) do not come on normally. Check if: What to do The MODU No. and CPL No. switches are set correctly. If not, set them correctly. The OD.RING/SD.LINK parameters are set correctly by using the S10V OD.RING/SD.LINK system. If not, set them correctly. The cable is connected properly. (For example, check if a cable line is broken or the cable is connected to the wrong destination.) If not, connect it properly.
2 TROUBLESHOOTING ET.NET LQE520 Communication is initially not possible. Check if: What to do An error message is recorded in the error log. If true, troubleshoot according to the instructions given under “4 Error Log Information.” The module number is set correctly. If not, set the rotary switch (MODU No.) at the front of the module housing correctly according to the instructions given under “2 NAMES AND FUNCTIONS OF EACH PART” in the “ET.NET (manual number SVE-1-103).” The cable is disconnected.
2 TROUBLESHOOTING Communication is not possible with the Tool (PC) Check if: What to do Where the Tool and ET.NET module are directly connected together by using a cross cable: The ET.NET module’s module no. setting switch (MODU No.) is set either in 4- or 5-position. If not, and you are using 10BASE-T, then set it in 4-position if the ET.NET module is the main module, and in 5-position if it is a submodule. The IP address of the Tool is set to a value of “192.192.192.
2 TROUBLESHOOTING SV.LINK LQE521 The TX and RX indicators (LEDs) do not come on normally. Check if: What to do The MODU No. switch is set correctly. If not, set it correctly. The IP address of the SV.LINK module is duplicated with the IP address of some other module. If true, set a unique IP address for the module. The IP address is set correctly. If not, set it correctly. The SV.LINK module’s parameters are set correctly. If not, correct them. In cases where the SV.
2 TROUBLESHOOTING J.NET, J.NET-INT LQE540 LQE545 The TX and RX indicators (LEDs) do not come on normally. Symptom Both TX and RX are OFF. TX is flickering, but RX is OFF. Both TX and RX are flickering. Check if: What to do The system or NET information is set correctly. If not, set it correctly. The MODU No. and BIT RATE switches are set correctly. If not, set them correctly. The RI/O STOP terminal on the LPU’s terminal block is shorted. If true, open-circuit the terminal. A J.
2 TROUBLESHOOTING The ERR indicator (LED) is lit. Check if: What to do The MODU No. or BIT RATE switch is set correctly. If not, set them correctly. The J.NET or J.NET-INT module mounted in this S10V controller is one whose parameters are previously set for use in an S10mini controller. If true, open the parameter-setting window in the tool (J.NET or J.NETINT SYSTEM) and add changes to the parameter settings for the mounted J.NET or J.NET-INT module.
2 TROUBLESHOOTING IR.LINK LQE546 The TX and RX indicators (LEDs) do not come on normally. Symptom Both TX and RX are OFF. TX is flickering, but RX is OFF. Both TX and RX are flickering. Check if: What to do The system or NET information is set correctly. If not, set it correctly. The MODU No. and BIT RATE switches are set correctly. If not, set them correctly. The RI/O STOP terminal on the LPU’s terminal block is shorted. If true, open-circuit the terminal. An IR.
2 TROUBLESHOOTING The ERR indicator (LED) is lit. Check if: What to do The MODU No. or BIT RATE switch is set correctly. If not, set them correctly. The IR.LINK module mounted in this S10V controller is one whose parameters are previously set for use in an S10mini controller. If true, open the parameter-setting window in the tool (IR.LINK SYSTEM) and add changes to the parameter settings for the mounted IR.LINK module.
2 TROUBLESHOOTING CPU LINK Inter-CPU link LQE550 The LINK indicator (LED) does not come on. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The MAIN/SUB setting switch is set correctly. If not, set it correctly. For details, refer to the description under “4 OPERATION” in the “CPU LINK (manual number SVE-1-109).
2 TROUBLESHOOTING RS-232C, RS-422 LQE560 LQE565 The TX and RX indicators (LEDs) do not come on normally. Check if: What to do The MODU No. switch is set correctly. If not, set it correctly. The RS-232C or RS-422 module’s parameters are set correctly. If not, set them correctly. The cable is connected correctly. Check the cable connections and, if a connection error is found, correct it.
2 TROUBLESHOOTING D.NET LQE570 LQE575 The MNS indicators (LEDs) do not come on normally. Symptom The green LED is flickering, but the red LED is OFF. Check if: What to do The cable is connected properly or free from breakage. If not, connect it properly. Terminating resistors are connected properly. If not, connect them properly. The slave is registered properly. If not, register it properly. The slave is started up normally. If not, start it up normally. The D.
2 TROUBLESHOOTING EQ.LINK LQE701 The TX and RX indicators (LEDs) do not come on normally. Check if: What to do The MODU No. switch is set correctly. If not, set it correctly. The IP address of the EQ.LINK module is duplicated with some other node’s. If true, set them uniquely. The IP address is set correctly. Set the same network address for both the local and remote nodes. The recommended network address is “192.168.250”. The EQ.LINK module’s parameters are set correctly.
2 TROUBLESHOOTING Common network problems and troubleshooting (1) Network-related problems (communication not possible) and troubleshooting Symptom Item to be checked Communi- Power cation not supply possible Check if: What to do Some equipment’s main power indicator(s) are not lit. If true, check the power supply and its voltage, and also check the power cables for any loose connections.
2 TROUBLESHOOTING EQ.LINK usage precautions There are some precautions that must be observed when using the EQ.LINK module. These precautions are listed below. For information on the standard related to EQ.LINK communication paths, refer to the EQ.LINK (manual number SVE-1-124) or IEEE802.3 standard. Do not carry data traffic from other Ethernet networks on the EQ.LINK communication cable. Do not connect the EQ.LINK module to any router. Use of a switching hub for the EQ.
2 TROUBLESHOOTING ET.NET LQE720 Communication is initially not possible. Check if: What to do An error message is recorded in the error log. If true, troubleshoot according to the instructions given under “4 ERROR LOG INFORMATION.” The module number is set correctly. If not, set the rotary switch (MODU No.) at the front of the module housing correctly according to the instructions given under “2 NAMES AND FUNCTIONS OF EACH PART” in the ET.NET (manual number SVE-1-103). The cable is disconnected.
2 TROUBLESHOOTING Communication is not possible with the Tool (PC) Check if: What to do Where the Tool and ET.NET module are directly connected together by using a cross cable: The ET.NET module’s ST No. setting switches are set to a value of /FF. The IP address of the Tool is set to a value of “192.192.192.***”, where *** is a number in the range 002 to 254. Where communication is performed via a hub: The ET.NET module has its IP address set. If not, set it. The IP addresses of the Tool and ET.
2 TROUBLESHOOTING RI/O Remote I/O station LQS000 The RI/O indicator (LED) does not come on. Check if: What to do The LPU module’s SIMU indicator (LED) is lit. If true, change the LADDER MODE to “NORM” in the S10V BASE SYSTEM. The LPU module is operating abnormally. If true, follow the troubleshooting map for the LPU module in order to check out the said module. The station number is set correctly. If not, set it correctly.
2 TROUBLESHOOTING J.Station LQS020 The J-NET indicator (LED) does not come on normally. Check if: What to do The BIT RATE and ST No. switches are set correctly. If not, set them correctly. The J.Station module’s terminal block has its terminals wired correctly. If not, wire the terminals correctly. The master side is started up normally. If not, start it up normally. If the master is a J.NET module, see the error freeze information for the J.NET module.
2 TROUBLESHOOTING IR.Station LQS021 The TX/RX indicator does not come on normally. Check if: What to do The BIT RATE and ST No. switches are set correctly. If not, set them correctly. The IR.Station module’s terminal block has its terminals wired correctly. If not, wire the terminals correctly. The IR.LINK module is started up normally. If not, start it up normally. If an IR.LINK error is reported, see the error freeze information for the IR.LINK module. The IR.
2 TROUBLESHOOTING D.Station LQS070 The MNS indicators (LEDs) do not come on normally. Symptom The green LED is flickering, but the red LED is OFF. The green LED is OFF but the red LED is lit. The green LED is OFF, but the red LED is flickering. Both the green and red LEDs are OFF. Check if: What to do The cable is connected properly (or free from wire breakage). If not, connect it properly. Terminating resistors are connected properly. If not, connect them properly. A registration of the D.
2 TROUBLESHOOTING A.INPUT Analog input LQA0** LQA1** LQA2** Input data cannot be input normally. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The station in which the A.INPUT module is installed is operating abnormally. If true, follow the troubleshooting map for the station module in order to check out the said module. The analog input module is mounted properly.
2 TROUBLESHOOTING A.INPUT Scan-type analog input LQA3** LQA8** Input data cannot be input normally. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The station in which the A.INPUT module is installed is operating abnormally. If true, follow the troubleshooting map for the station module in order to check out the said module.
2 TROUBLESHOOTING A.OUTPUT Analog output LQA5** LQA6** The output voltage and current are abnormal. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The station in which the A.OUTPUT module is installed is operating abnormally. If true, follow the troubleshooting map for the station module in order to check out the said module. The analog output module is mounted properly.
2 TROUBLESHOOTING D.INPUT Digital input LQX*** None of the input points is turned on. Check if: The operation status indicators (LEDs) are all ON or OFF. OFF ON What to do The right terminal block is attached to the D.INPUT module. If not, attach the right one to it. The fixing screws of the digital input module are loose. If true, apply additional tightening to the fixing screws. An external input power source is connected to the digital input module. If not, connect one to it.
2 TROUBLESHOOTING None of the input points is turned off. Check if: What to do The operation status indicator (LED) is OFF. If true, replace the module. The operation status indicator (LED) is ON. If true, check if the external wiring is correct. If it is correct, replace the module. The input is turned on of off irregularly. Check if: What to do The external input power voltage is too low. If true, raise it. Adequate noise reduction measures are taken. If not: • Use surge absorbers.
2 TROUBLESHOOTING D.OUTPUT Digital output LQY*** None of the load points is turned on. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The digital output module is mounted properly. If not, mount it properly. The operation status indicator (LED) is ON or OFF. The station module is malfunctioning.
2 TROUBLESHOOTING None of the load points is turned off. Check if: What to do The station module is operating abnormally. If true, follow the troubleshooting map for the station module in order to check out the said module. The LPU module is operating abnormally. If true, follow the troubleshooting map for the LPU module in order to check out the said module. Only a particular load point is not turned off. Check if: The operation status indicator (LED) is ON or OFF.
2 TROUBLESHOOTING The load is turned on of off irregularly. Check if: What to do The external load power voltage is too low. If true, raise it. Adequate noise reduction measures are taken. • Use surge absorbers. • Take measures to protect the laid cables from any noise source. For more information, refer to the description under “4 HANDLING” in the “S10mini HARDWARE MANUAL, I/O MODULES (manual number SME-1-114).” The remote I/O cable is abnormal.
2 TROUBLESHOOTING D.IN/OUT Digital input/output LQZ*** Input or output is malfunctioning. Check if: What to do The allocation address setting switch (SW3) is set correctly. If not, set it correctly. Input is malfunctioning. If true, follow the troubleshooting map for the digital input (D.INPUT) module in order to check out the said module. Output is malfunctioning. If true, follow the troubleshooting map for the digital output (D.OUTPUT) module in order to check out the said module.
2 TROUBLESHOOTING COUNTER Pulse counter LQC000 The counter does not count pulses. Check if: What to do The power supply module is operating abnormally. If true, follow the troubleshooting map for the power supply module in order to check out the said module. The station is operating abnormally. If true, follow the troubleshooting map for the station module in order to check out the said module. The pulse counter module is mounted properly. If not, mount it properly.
2 TROUBLESHOOTING The count value is not correct. Check if: What to do The input pulses received exceeds 20K PPS. If true, reduce them to 20K PPS or less. Extra pulses are received due to noise. If true, take a noise reduction measure. Relay-generated pulses are received. If true, receive only pulses generated by transistor or other semiconductor devices. No external comparison output is produced. Check if: What to do An external power source is connected to the counter module.
2 TROUBLESHOOTING Tool (personal computer) connection No connection can be established with the PCs (via RS-232C) Check if: What to do The cable connector is screwed tightly. If not, screw it tightly. Any connector pins are bent. If true, replace the cable. The connection between the cable and connector is loose. A cable not conforming to the standard cable specifications is used. No connection can be established with the PCs (via Ethernet [ET.
THIS PAGE INTENTIONALLY LEFT BLANK. https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION 3.1 Remote I/O Troubleshooting If the data read from or written to the X or Y area is not input or output normally, troubleshoot as described below. Checking if terminating resistors are connected As exemplified below, terminating resistors need to be connected to both ends of a communication line on the LPU or the I/O unit. : A place where a terminating resistor needs to be connected.
3 TECHNICAL SUPPORT INFORMATION Connecting terminating resistors When you want to use a conforming cable, terminate it with a built-in resistor of either 100 or 150 Ω. To use these resistors, short the terminal pairs shown below. If a non-conforming cable is selected and you want to terminate it with a termination value other than 100 and 150 Ω, then connect an appropriate resistor between the signal input terminals (A and B in the figures below).
3 TECHNICAL SUPPORT INFORMATION Checking if the I/O address is duplicated or is another station’s Check the address switch settings of the station module in the I/O unit. Checking if the remote I/O cable used is conforming to the standard cable spec Use as the remote I/O cable a communication cable that conforms to the specifications shown below. Also, as the power and grounding cables, use those specified below.
3 TECHNICAL SUPPORT INFORMATION Checking if extra X and Y numbers are registered In some cases, an old I/O unit in which a station module of model PST350 or PST360 is installed in the left-end slot is connected to the LPU module. In such a case, if the number of remote I/O transfer points for the LPU module is set to 1024 or greater, decrease the number.
3 TECHNICAL SUPPORT INFORMATION Remote I/O and inter-CPU link line waveforms (1) Transmission and reception waveforms -- examples (2) Enlarged view of normal waveform -- example 1.0 V/div 20 µs/div Transmission 1.0 V/div 0.5 µs/div Reception (3) Normal waveform on remote I/O line * The transmitted waveform has its crest value of approximately 3 V. * The received waveform has its crest value of approximately 2 V. No disturbance must appear in this portion of the waveform. 1.0 V + 0.4 V 0V -0.
3 TECHNICAL SUPPORT INFORMATION (4) Normal waveform on inter-CPU link line * The transmitted waveform has its crest value of approximately 3 V. * The received waveform has its crest value of approximately 2 V. No disturbance must appear in this portion of the waveform. 1.0 V + 0.4 V 0V -0.5 V 900 ns or more The voltage must not go down below 1.0 V in this time period. -1.0 V 500 ns or more The voltage must not go up above 0.4 V in this time period.
3 TECHNICAL SUPPORT INFORMATION 3.2 LPU Error Information Detail Table If an error occurs in any of the installed LPU modules, detail error information is stored in a special table in the LPU module’s internal RAM. By accessing this table, called the LPU error information detail table, you can obtain more comprehensive error information than the error information supplied by the basic tool (S10V BASE SYSTEM). This table can be accessed with the MCS function of the basic tool.
3 TECHNICAL SUPPORT INFORMATION (3) Detail information • Detail info for error codes 0x1101 and 0x1102 Offset from the beginning of case 231 20 +/0000 0010 0x0000 0000 (detail word count) +/0000 0014 0x0000 0000 • Detail info for error code 0x1105 • Detail info for error code 0x1103 Offset from the beginning of case 231 20 +/0000 0010 0x0000 000C (detail word count) +/0000 0014 Address at which error is detected +/0000 0018 Write data +/0000 001C Read data • Detail info for error code 0x1106 Offset fr
3 TECHNICAL SUPPORT INFORMATION Note 2: The table below is a list of I/F register addresses and the corresponding optional modules in which errors of this type are detected. I/F register address Corresponding optional module /41F800, F810 CPU link (/41F800: Main module, /41F810: Submodule) /41F820, F830 OD.RING (/41F820: Main module, /41F830: Submodule) /41F920, F930 J.NET/J.NET-INT/IR.
3 TECHNICAL SUPPORT INFORMATION • Detail info for error codes other than the above Offset from the beginning of case 231 20 +/0000 0010 0x000001EC (detail word count) +/0000 0014 N-coil number +/0000 0018 Ladder program counter (SPC) +/0000 001C HI-FLOW executed process No.
3 TECHNICAL SUPPORT INFORMATION (Continued from preceding page) Offset from the beginning of case 231 216 215 20 +/0000 0178 MCW0 +/0000 017C MCW1 +/0000 0180 MCW3 +/0000 0184 MCW4 +/0000 0188 IRW0 +/0000 018C IRW1 +/0000 0190 IRW2 +/0000 0194 IRW3 LPU’s +/0000 0198 IRW4 internal +/0000 019C RERRLOG registers +/0000 01A0 RSBACR +/0000 01A4 RERRSTATSLV RERRENSLV +/0000 01A8 RERRSTATCP RERRENCP +/0000 01AC RLERRSTAT RLERREN +/0000 01B0 RBUSMNT RBRQTMR +/0000 01B4 RTRANSTMR RACYCTMER +/0000 01B8 RACKBUSYTMR
3 3.3 TECHNICAL SUPPORT INFORMATION Clearing the Entire Memory Clearing the LPU module’s memory The entire memory of any LPU module can be cleared (to a condition at shipment) by performing the following procedure: ① Turn off the power to the LPU unit. ② Set the LPU module’s operational setting switch (T/M) in E-position. ③ Turn on the power to the LPU unit and wait about three seconds. ④ Turn off the power to the LPU unit. ⑤ Set the LPU module’s operational setting switch (T/M) in F-position.
3 TECHNICAL SUPPORT INFORMATION 3.4 Backing Up and Restoring Replacement of an existing module may sometimes requires prior backing up and subsequent replacement of the entire software system. In these cases, use the S10V BACKUP RESTORE SYSTEM (also called the batch saving/loading system). Backup/restore areas The BACKUP RESTORE SYSTEM backs up all the memory areas listed in the table below at one time. Table 3-1 Memory Areas Subjected to Backing up and Restoring (1/3) No.
3 Table 3-1 TECHNICAL SUPPORT INFORMATION Memory Areas Subjected to Backing Up and Restoring (2/3) No.
3 TECHNICAL SUPPORT INFORMATION Table 3-1 No. 10 11 12 13 14 Memory Areas Subjected to Backing Up and Restoring (3/3) User area name D.NET Inter-CPU link RS-232C/RS-422 EQ.
3 TECHNICAL SUPPORT INFORMATION Backing up procedure Choose [Start] – [Programs] – [Hitachi S10V] – [S10V Backup Restore System] on the personal computer (PC) connected with the S10V system. The Backup Restore System then starts. As described in detail below, click on the Backup button in the [BACKUP RESTORE SYSTEM] window, and then the [Backup] window appears on the screen. Now the BACKUP RESTORE SYSTEM is ready for backing up the S10V system.
3 TECHNICAL SUPPORT INFORMATION (2) Enter the name and position finder of the folder to which to save the contents of the memory areas, and the desired PCs number, along with a comment, if necessary. The following information describes the input items and buttons displayed in the aforementioned [Backup] window. Name: Is the name of the folder in which to place the files backed up. This folder name is defaulted to none; the box is displayed blank.
3 TECHNICAL SUPPORT INFORMATION Select the desired folder and click the OK button. Then, the [Reference] window disappears and the [Backup] window appears again. The folder you have just selected in the [Reference] window is displayed with its full path name in the Position (I) text box.
3 TECHNICAL SUPPORT INFORMATION If the entire plant equipment under control can be stopped, abort all the active tasks in your system. When the tasks are aborted, they are automatically post-processed properly, so that the files can be backed up safely. If the backup process is started without aborting the tasks, the files will be backed up in a condition in which the memory areas being accessed by the tasks are dynamically changing in their contents.
3 TECHNICAL SUPPORT INFORMATION Clicking the OK button starts the PCs resetting process. The same confirmation message as above is also displayed at the end of the backup process. When it is displayed, do the same as you have done to the above confirmation message. If the entire plant equipment under control can be stopped, stop the operating system (OS).
3 TECHNICAL SUPPORT INFORMATION The size of save area cannot be changed for each individual module. If the backup process in progress is canceled and ends up with an error, the OS may remain in a stop state. Therefore, be sure to check if the OS is in RUN state by using an appropriate utility command. If it is not, put it back into RUN state by using the same utility command.
3 TECHNICAL SUPPORT INFORMATION Restoring procedure As is done in file backup, start the S10V BACKUP RESTORE SYSTEM on the personal computer (PC) connected with the S10V system. Then, as described in detail below, click on the Restore button in the [BACKUP RESTORE SYSTEM] window. The [Select Restore File] window then appears on the screen. Now the BACKUP RESTORE SYSTEM is ready for restoring the S10V system’s backed up files. (1) Click the Restore button in the [BACKUP RESTORE SYSTEM] window.
3 TECHNICAL SUPPORT INFORMATION At the same time, if a CMU module is installed, and there is data backed up for that CMU module, and a connection is established by using the RS-232C or ET.NET (LQE520) module, then the following warning message appears: In this case, data restoring is not performed for the CMU module. If you want to perform data restoring for the CMU module, re-establish a connection by using the Ethernet support provided by that CMU module or an ET.NET (model LQE720) module.
3 TECHNICAL SUPPORT INFORMATION The [Restoration Information] window provides, in a list form, information as to whether each predefined type of module is actually installed in the system and whether the corresponding data is backed up. However, this window provides no such information on any predefined type of module for which no data is backed up. Take a look at the displayed list and, if you want to restore all the backup data in the list, click the OK button.
3 TECHNICAL SUPPORT INFORMATION Restore.It rewrites by PCsNo of the wsvl file header.: Is an option to carry out a restore operation while overwriting the PCs number in the restoration destination with the PCs number in the backup file’s header. The PCs number in the backup file’s header is one that is specified at the time of backup. Restore.It rewrites by PCsNo of the wsvl file main part.
3 TECHNICAL SUPPORT INFORMATION Restore.It rewrites by IP address of the wsvl file.: Is an option to carry out a restore operation while overwriting the IP address in the restoration destination with the IP address in the backup file. In this case, the IP address-related information (subnet mask, broadcast address, and routing information) is also subjected to overwriting. Restore.IP adrress is not rewritten.
3 TECHNICAL SUPPORT INFORMATION (5) When a restore operation is started, a message to ask permission to reset the PCs is presented. Click the OK button in the dialog. The PCs is then reset. (6) Upon completion of the PCs resetting, the following confirmation message is presented: If you click the Yes button in the above dialog, the keep-coil and counter-count backup information is restored. If you click the No button instead, it is not restored.
3 TECHNICAL SUPPORT INFORMATION When the PCs resetting is completed, click the OK button. Then, the [Restore] window disappears and the [Select Restore File] window appears again. (8) Finish your restore operation by clicking the window. Cancel button in the [Select Restore File] If the restoration process in progress is canceled and ends up with an error, the OS may remain in a stop state. Therefore, be sure to check if the OS is in RUN state by using an appropriate utility command.
3 TECHNICAL SUPPORT INFORMATION Backup and restoration using optional-module setting tools It is a common practice to carry out a backup and a restore operation using the BACKUP RESTORE SYSTEM when a module(s) need to be replaced and when they are replaced, respectively. However, if the number of optional modules to be replaced is only one, you can carry out a backup and a restore operation using the optional-module setting tool for that module.
3 Table 3-2 No. Backup Areas Used by Optional-Module Setting Tools (2/2) Header storage location (address) Setting tool /00E3 0000 to /00E3 5AFE ch0 /00E3 6000 to /00E3 608E /00E7 0000 to /00E7 5AFE ch1 5 /00E7 6000 to /00E7 608E D.
3 TECHNICAL SUPPORT INFORMATION Backup areas The table below shows the memory addresses for modules that are subjected to backup operations. Table 3-3 No. 1 Backup Areas (1/2) Module (backup file name) Backup address LPU /0010 0000 to (changeable) (backup1.
3 Table 3-3 5 Backup Areas (2/2) Module (backup file name) No. FL.NET TECHNICAL SUPPORT INFORMATION Backup address Main module (backup5.wsvl) /00D4 1A00 to /00D4 1A32 /00D7 0050 to /00D7 1E4E /00D7 0020 to /00D7 0048 Submodule /00DC 1A00 to /00DC 1A32 /00DF 0050 to /00DF 1E4E /00DF 0020 to /00DF 0048 6 D.NET Channel 0 (backup6.
3 TECHNICAL SUPPORT INFORMATION Note 1: As this backup area, only the range of addresses actually used to store a ladder program’s body, comment data, and user (arithmetic) functions’ bodies is subjected to backup. The end address of this area is changeable in the range: /0010 4406 to /0016 7FFE Note 2: These backup areas are defined only when HI-FLOW is stored in place.
3 3.5 TECHNICAL SUPPORT INFORMATION Performance Performance information for the S10V controller can be viewed on screen. To accomplish this, start up the S10V BASE SYSTEM by choosing [Start] – [Programs] – [Hitachi S10V] – [S10V BASE SYSTEM] on the personal computer connected with the S10V controller, and click the Performance button. Then, the [Performance] window appears which present the performance information.
3 TECHNICAL SUPPORT INFORMATION • Clear button (for sequence cycle): Used to clear the current value, maximum value, and minimum value of sequence cycle and restart measurement. When the three values are cleared, they are displayed as zero (0). • Clear button (for CMU load percentage): Used to clear the current value, maximum value, and minimum value of CMU load percentage and restart measurement. When the three values are cleared, they are displayed as zero (0).
3 TECHNICAL SUPPORT INFORMATION (2) [Change Measurement Time] window The [Change Measurement Time] window allows you to change the current value of CMU load percentage measurement time. • [Measurement time] box: Allows you to enter a new value of CMU load percentage measurement time expressed in seconds in the range 1 to 60. This measurement time is defaulted to 1. The entered value appears as a new default value when this window is displayed next time.
3 TECHNICAL SUPPORT INFORMATION 3.6 Address Space Maps Address space map of the LPU unit /000000 System area /060000 SEQ-RAM (first 128 KB) (Note) /080000 System area /0A0000 /0C0000 /0E0000 Note: Of the addresses /060000 through /07FFFF (SEQ-RAM), the following addresses are allocated to the items shown right below.
3 TECHNICAL SUPPORT INFORMATION Address space map to PIO-RAM bit area /200000 Remote I/O communication area (input) /202000 Transfer registers, J000 to FFF /204000 Remote I/O communication area (output) /206000 Receive registers, Q000 to FFF /208000 Global link registers, G000 to FFF /20A000 Extension internal registers, A000 to FFF /216200 /20C000 Internal registers, R000 to FFF /216800 /20E000 Extension internal registers, M000 to FFF /216A00 /210000 Keep-relays, K000 to FFF /0A0000
3 TECHNICAL SUPPORT INFORMATION Address space map to PIO-RAM word area /061000 DW000 to FFF (Note) Same data values as of /4700000 DW000 thru FFF /063000 Set values of Ts Remote I/O /400000 /063400 Set values of Us communication area /063600 Set values of Cs (input) /400200 /063800 Transfer registers, /0E0000 JW000 to FF0 First 16k words Remote I/O /0E8000 /400400 communication area /0F0000 Counts of Ts (output) /0F0400 /400600 Counts of Us Receive registers, /0F0600 Counts of Cs (Note) QW000 to FF0 /0F08
3 TECHNICAL SUPPORT INFORMATION Address space map to PIO-RAM word area (continued from preceding page): /400000 First 16k words /408000 Set values/counts /409000 (Reserved) /412000 /412000 Work registers, LB0000 to FFFF (LBW0000 to FFF0; LBL0000 to FFE0) External inputs, XW000 to FF0 /414000 Extension area (120k words) /414200 External outputs, YW000 to FF0 /414400 NX user buffer area /42D400 (Reserved) /430000 Long-word registers, LLL0000 to 1FFF /438000 Floating-point registers, LF000
3 TECHNICAL SUPPORT INFORMATION Address space map of the CMU unit /0000 0000 LPU address space (same as the address space map of the LPU unit) /0100 0000 /0110 0000 /0300 0000 /0400 0000 /0C00 0000 /1800 0000 /1C00 0000 /2000 0000 /2800 0000 /3000 0000 NX user buffer area (Reserved) HI-FLOW address space (Reserved) High-speed system bus address space PCI address space CMU address space (not accessible from the LPU) (Reserved) MAP address space CPMS address space Task address space /4000 0000 GLBR addr
3 3.7 TECHNICAL SUPPORT INFORMATION Registers 3.7.1 Ladder instructions and usable registers The table below shows all registers usable in ladder instructions.
3 TECHNICAL SUPPORT INFORMATION Table 3-5 Usable Registers (2/2) Ladder symbols Function name S R Comparison F Status after reset or power recovery E V Z S J Q HH √ cu √ √ √ √ cu cu √ cu cu cu cu cu √ cu √ cu cu √ cu cu cu cu cu cu cu cu √ √ √ √ √ √ cu √ √ √ √ √ √ cu Cleared Cleared Cleared Initialized Cleared Cleared Cleared LB LR √ √ cu cu √ √ cu cu √ √ √ √ Cleared Cleared LV cu √ cu cu √ √ Cleared IW cu cu cu cu √ √ Cleared OW cu cu cu cu √ √ Cleared BD c
3 TECHNICAL SUPPORT INFORMATION 3.7.2 Register numbers The table below is a list of all register numbers that can be used in ladder programs. As shown, the range of usable register numbers depends on the types of registers accessed by their generic register names. Table 3-6 No.
3 TECHNICAL SUPPORT INFORMATION Table 3-6 No.
3 TECHNICAL SUPPORT INFORMATION 3.7.3 System registers Range of numbers 000 to BFF System registers are read-only registers reflecting the system’s operation performed or other things relating to the system. The table below is a list of all available system registers. Table 3-7 No.
3 TECHNICAL SUPPORT INFORMATION (1) Arithmetic-function flag registers Arithmetic-function flag registers indicate the set/reset statuses of predefined flags that occur upon the execution of system arithmetic-function instructions. These registers cannot be referenced from the ladder circuit monitor and MCS functions (if an attempt is made to do so, the registers are always displayed as “OFF”).
3 TECHNICAL SUPPORT INFORMATION (3) HI-FLOW application-instruction execution-result flag registers HI-FLOW application-instruction execution-result flag registers indicate the statuses of predefined flags that occur upon the execution of HI-FLOW application instructions.
3 TECHNICAL SUPPORT INFORMATION (6) Time setting registers Time setting registers are used to store values indicating the year, month, day of month, hours, minutes, seconds, and day of week. When you make time settings in the LPU, store time information in these registers. Data stored in these registers must be in binary format.
3 TECHNICAL SUPPORT INFORMATION (7) Remote I/O status registers Remote I/O status registers present remote I/O station information, such as station registered or not, timeout error detected or not, and fuse blown or not. Registered stations • All stations that are currently connected to the communication line and that have thus far responded normally at least once have their associated registers set to 1.
3 TECHNICAL SUPPORT INFORMATION (8) Optional-module status registers Optional-module status registers are used to store error information for inter-CPU links, external-equipment links, etc. As shown below, these registers are organized into four groups according to the module types used. Data is set in each group of registers by a system program provided for its associated module type.
3 TECHNICAL SUPPORT INFORMATION (9) Sequence-cycle scan-time registers Sequence-cycle scan-time registers are used to store the result of measurements of sequence cycles. (MSB) (LSB) 15 0 2 SW900 SW910 SW920 SW930 2 Latest measurement value (ms) Maximum measurement value (ms) Zero-cleared when the status of the LPU module is switched from STOP to RUN.
3 TECHNICAL SUPPORT INFORMATION (12) Optional-module status registers (J.NET/IR.LINK) These optional-module status registers are used to store error information on errors detected in each J.NET or IR.LINK module (main or submodule). For details, refer to the “J.NET (manual number SVE-1-104)” and “J.NET-INT (manual number SVE-1-107),” or the “IR.LINK (manual number SVE-1-117).
3 TECHNICAL SUPPORT INFORMATION (14) LPU status registers LPU status registers indicates the current state of the LPU. LPU status bit configuration (MSB) (LSB) 15 14 13 2 2 2 SWBF0 1/0 1/0 * Bit No. 0 1 2 12 11 10 2 2 2 1/0 1/0 * 3 4 5 9 8 2 2 1/0 * 6 7 7 6 5 4 3 2 2 2 2 2 1/0 1/0 1/0 1/0 * 8 9 A B C 2 1 0 2 2 2 1/0 1/0 0 D E F * Each of these bits is reserved for future extension. Bit No. Meanings of bits Bit register No. ON (=1) OFF (=0) 0 SBF0 Currently in STOP state.
3 TECHNICAL SUPPORT INFORMATION (15) Ethernet communication result flag registers Ethernet communication result flag registers are used to store special flags for indicating the result of execution of Ethernet communication instructions. Execution results are flagged in the system registers S9C0 through S9FF according to the management numbers, which are predefined in one-to-one correspondence with all available sockets.
3 3.8 TECHNICAL SUPPORT INFORMATION Memory Maps for Optional Modules As shown below, optional modules are mapped into memory, starting from the address /800000. Address /000000 ～ ～ ～ ～ /800000 ET.NET/SV.LINK (main module) /880000 ET.NET/SV.LINK (submodule) /900000 OD.RING/SD.LINK (main module) /980000 OD.RING/SD.LINK (submodule) /A00000 J.NET/J.NET-INT/IR.LINK (main module) /A80000 J.NET/J.NET-INT/IR.
TECHNICAL SUPPORT INFORMATION Memory map for the ET.
3 TECHNICAL SUPPORT INFORMATION Memory map for the SV.
TECHNICAL SUPPORT INFORMATION Memory map for the OD.RING (model LQE510/515)/SD.
3 TECHNICAL SUPPORT INFORMATION Memory map for the J.NET (model LQE540), J.NET-INT (model LQE545), and IR.
TECHNICAL SUPPORT INFORMATION Memory map for the FL.NET (model LQE500 or LQE502) module Submodule /D80000 μprogram /D40000 /DC0000 /D40400 /DC0400 /D40500 /DC0500 /D40800 /DC0800 /D40C00 /DC0C00 Module info table Error freeze table (Reserved for system use) System work area FA protocol work area /D70000 /DE0000 (Reserved for system use) /D80000 Flash ROM Main module /D00000 /E00000 - 112 - https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION Memory map for the EQ.LINK (model LQE701) module μprogram /D40000 /DC0000 /D40400 /DC0400 /D40500 /DC0500 /D40800 /DC0800 /D40C00 /DC0C00 Module info table Error freeze table (Reserved for system use) System work area μprogram work area /D70000 /DE0000 (Reserved for system use) /D80000 Flash ROM Submodule /D80000 /E00000 - 113 - https://www.truck-manuals.
TECHNICAL SUPPORT INFORMATION Memory map for the D.
3 TECHNICAL SUPPORT INFORMATION Memory map for the RS-232C/422 (model LQE560/565) module Channel 0 Channel 1 Channel 2 Channel 3 /F40000 /F50000 /F60000 /F70000 μprogram /F48000 /F58000 /F68000 Flash ROM /F78000 (Reserved for system use) /F48800 /F58800 /F68800 /F78800 Error freeze /F48900 /F58900 /F68900 /F78900 /F48920 /F58920 /F68920 /F78920 Error counter H-7338 error trace /F48B00 /F58B00 /F68B00 /F78B00 RAM (shared memory) (Reserved for system use) /F4D000 /F5D000 /F
3 TECHNICAL SUPPORT INFORMATION 3.9 FL.NET (Model LQE500/LQE502) Error Information Error message data table The error message table is a data table provided in the FL.NET module and used as follows: If a message is received as a response to a message request issued by the local node and is found abnormal, its message data is stored in the error message table. The information given below is the detailed specification of the error message table.
3 TECHNICAL SUPPORT INFORMATION Error codes for C-mode handler- and arithmetic function-detected errors The table below enumerates all error codes that are returned when errors are detected in requests issued from C-mode handlers and arithmetic functions to the FL.NET module. In addition to these error codes, the table also provides information on the error causes and the user actions required to solve the problems.
3 TECHNICAL SUPPORT INFORMATION (2/2) Error code 0xFE08 Brief description Cause Required action ACK reception An ACK response containing a Module failure is conceivable. sequence-number error sequence-number error is received Replace the module. from the specified node. 0xFE09 0xFE12 0xFE13 ACK reception An ACK response containing a sequence-number sequence-number version error is version error received from the specified node.
3 3.10 TECHNICAL SUPPORT INFORMATION OD.RING (Model LQE510/515) and SD.LINK (Model LQE530) Communication Traces The OD.RING and SD.LINK modules are capable of tracing communications and their details. By using this capability, you can generate trace data and use it for troubleshooting. (1) Trace buffer structure The trace buffer used consists of an 8-word trace control table and 256 cases (32 words per case) of trace data, as shown below.
3 TECHNICAL SUPPORT INFORMATION (2) Trace control table The trace control table consists of eight words, as shown below. Main module Submodule /940FF0 /9C0FF0 Perform/Stop /940FF2 /9C0FF2 (Unused) /940FF4 /9C0FF4 Trace target address /940FF8 /9C0FF8 Mask data /940FFA /9C0FFA Comparison data /940FFC /9C0FFC Pointer /940FFE /9C0FFE (Unused) ① Perform/Stop This table entry is used to set one of the following directives to the tracing capability: 0: Stop tracing.
3 TECHNICAL SUPPORT INFORMATION Assume that G002 must always be equal to 1, and that, if it is set equal to 0, tracing needs to be stopped. Then, set the following entries in the trace control table. /0002 /000E /0800 GW000 (Address=0E0800) G 0 0 1 G 0 0 2 G 0 0 F 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 /2000 /2000 G 0 0 0 Mask data Assume that FW000 must always be equal to 1234, and that, if FW000 is set equal to 1111, tracing needs to be stopped.
3 TECHNICAL SUPPORT INFORMATION (3) Trace data The trace data for each case of tracing consists of 32 words, as shown below. /00 Trace factor /02 Error status /04 Header portion (10 words) from frame /18 Frame information 32 words long Bit data (first 8 words) from frame /28 Word data (first 8 words) from frame /38 Event data (first 4 words) from frame 15 8 7 0 /04 Destination CPL No. Source CPL No.
3 TECHNICAL SUPPORT INFORMATION (4) Trace events and processes performed on their occurrence The table below shows the relationships between events causing the generation of trace data and processes performed on the occurrence of the events.
3 TECHNICAL SUPPORT INFORMATION Termination on error If the “perform/stop” entry in the table is set equal to 2, communication tracing is terminated on the occurrence of an error. Trace factor The “trace factor” entry in the table consists of flags to indicate a variety of causes of trace data generation: 15 2 (MSB) 12 11 2 2 8 7 2 2 4 3 2 2 0 2 (LSB) /0 Condition not satisfied. /1 Condition satisfied. Reserved for future extension. /0 Started. /1 Terminated normally.
3 TECHNICAL SUPPORT INFORMATION 15 2 (MSB) 7 5 2 2 D E L G 0 2 (LSB) N A O B C O R V Overrun CRC-detected error Abort sequence Non-octet frame Frame length violation DPLL error NOTE The error status is set to “FFFF” when a reception time-out error is detected. The table below sets forth the details of the error status.
3 TECHNICAL SUPPORT INFORMATION 3.11 3.11.1 ET.NET (Model LQE520) Error Information Error codes from the socket handler The table below enumerates all error codes that are returned from the socket handler to report on the occurrence of errors. In addition to these error codes, the table also provides information on the error causes and the user actions required to solve the problems.
3 Table 3-8 Error code Brief description TECHNICAL SUPPORT INFORMATION Error Codes from the Socket Handler (LQE520) (2/3) Cause Required action Check the user program (to see if all the send data lengths specified are within the stated limits). Check the user program (to see if all the receive data lengths specified are within the stated limits).
3 TECHNICAL SUPPORT INFORMATION Table 3-8 Error code Brief description Error Codes from the Socket Handler (LQE520) (3/3) Cause Required action FFFD Duplicate socket The same socket (using the remote station’s IP address or port number, or the local station’s port number) is already existent. Check the user program. FFFE Illegal control block The maximum permitted number of usable sockets has been exceeded.
3 3.11.
3 TECHNICAL SUPPORT INFORMATION 3.12 SV.LINK (Model LQE521) Error Information Parameter setting and communication errors, if detected, are reported by setting error codes in the status register area (BD000). These error codes are listed in the table below. No.
3 TECHNICAL SUPPORT INFORMATION The error code (BD000) in the status register area described above is cleared to zero (0) when an error recovery is made by, for instance, communication retries. Any error(s) that occurred in the past can be identified by referencing the error code trace area shown below. This trace area can contain information on up to 16 past error codes reported.
3 TECHNICAL SUPPORT INFORMATION 3.13 3.13.1 J.NET (Model LQE541), J.NET-INT (Model LQE547), and IR.LINK (Model LQE548) Trace Information Command and response buffers Command buffer In the information given below, the “Main module [N1]” stands for the IR.LINK module.
3 TECHNICAL SUPPORT INFORMATION Response buffer In the information given below, the “Main module [N1]” stands for the IR.LINK module.
3 TECHNICAL SUPPORT INFORMATION 3.13.2 Data send and data receive buffers Data send buffer In the information given below, the “Main module [N1]” stands for the IR.LINK module.
3 TECHNICAL SUPPORT INFORMATION Data receive buffer In the information given below, the “Main module [N1]” stands for the IR.LINK module.
3 TECHNICAL SUPPORT INFORMATION 3.13.3 Error counters Communication errors in the J.NET, J.NET-INT, and IR.LINK modules (master stations) and stations (slave stations) are counted in the counters shown below. These error counters are initialized when the controller is reset. In the information given below, the “Main module [N1]” stands for the IR.LINK module.
3 3.13.4 TECHNICAL SUPPORT INFORMATION Trace The J.NET, J.NET-INT, and IR.LINK modules are capable of tracing the status of communication in respect to each network (N1 or N2). Tracing begins on the occurrence of an LPU reset or error stop mode (due to an error or tracing stop) following power-on and performs recording for transmissions and receptions in each service. Main module Submodule /AE8000 Trace pointer /A68002 /AE8002 Enforce the stoppage of tracing or not.
3 TECHNICAL SUPPORT INFORMATION Trace data area +00 Type +02 Error code +04 (Unused) All possible types and what they indicate are as follows: Type +06 +08 First 20 bytes of data from the send /receive buffer in physical layer +1A +1C +1E Timer count (elapsed time after CPU resetting) What it indicates 1010 I/O service transmission done normally 1030 Initialization service transmission done normally 2010 I/O service reception done normally 2030 Initialization service reception done norm
3 TECHNICAL SUPPORT INFORMATION Trace data area +00 Type +02 Error code Type +04 (Unused) 3010 I/O service transmission error 3030 Initialization service transmission error 4010 I/O service reception error 4030 Initialization service reception error All possible types and what they indicate are as follows: +06 +08 First 20 bytes of data from the send /receive buffer in physical layer What it indicates +1A +1C +1E Timer count (elapsed time after CPU resetting) For details, see the info
3 TECHNICAL SUPPORT INFORMATION 3.14 3.14.1 RS-232C (Model LQE560) and RS-422 (Model LQE565) Trace Information Communication tracing The RS-232C and RS-422 modules are capable of tracing communications and their details. By using this capability, you can generate trace data and use it for troubleshooting.
3 Table 3-10 TECHNICAL SUPPORT INFORMATION Trace Data Area Details (for Communication Tracing) Address Format /00 Type /02 Control signal statuses /04 Send/receive data | (24 bytes) /1A /1C Elapsed time (ms) after resetting /1E ① Type This item indicates one of the following occurrences: /1000: Transmission has been performed normally. /2000: Reception has been performed normally. /30**: Transmission has ended up with an error. /40**: Reception has ended up with an error.
3 TECHNICAL SUPPORT INFORMATION 3.14.2 Handler tracing The RS-232C and RS-422 modules are capable of tracing the activation of handlers from applications and the response from the handlers thereafter.
3 Table 3-12 TECHNICAL SUPPORT INFORMATION Trace Data Area Details (for Handler Tracing) Address Format /00 Type /02 Error code /04 Parameter 1 /06 /08 Parameter 2 /0A /0C Elapsed time (ms) after resetting /0E ① Type This item indicates one of the following occurrences: /8000: Transmission handler has been activated normally. /9000: Reception handler has been activated normally. /8800: Transmission handler has ended up with an error. /9800: Reception handler has ended up with an error.
3 TECHNICAL SUPPORT INFORMATION 3.14.3 H-7338 error tracing The RS-232C and RS-422 modules are capable of tracing H-7338 communication errors and the communication data involved in H-7338 communications.
3 Table 3-14 TECHNICAL SUPPORT INFORMATION Trace Data Area Details (for H-7338 Error Tracing) Address Format /00 Error code /04 Command code /08 Parameter 1 /0C Parameter 2 /10 Parameter 3 /14 Parameter 4 /18 Elapsed time (ms) after resetting /1C (Unused) ① Error code This item identifies a reported command or communication line error.
3 TECHNICAL SUPPORT INFORMATION 3.14.4 Error counters The RS-232C and RS-422 modules are provided with error counters to count communication errors. These error counters are initialized when the controller is reset.
3 TECHNICAL SUPPORT INFORMATION 3.15 D.NET (Model LQE570/575) Statistical and Error Information Statistical information Each unit of statistical information is 2 bytes long, and each counter takes values in the range 0 to 0xFFFF cyclically, i.e., when it exceeds the value 0xFFFF, it is reset to 0 and goes on counting.
3 TECHNICAL SUPPORT INFORMATION (3) CAN control counts 0xE*7240 Stack error detection count 0xE*7242 Form error detection count 0xE*7244 Ack.
3 TECHNICAL SUPPORT INFORMATION (5) User error 1 counts 0xE*7280 Unsuccessful I/O data read count 0xE*7282 Unsuccessful I/O data write count (unused) 0xE*7284 Effective data length error detection count 0xE*7286 Service double-start detection count 0xE*7288 Open double-start detection count 0xE*728A Open issuance destination error detection count 0xE*728C Close issuance destination error detection count 0xE*728E MACID error detection count 0xE*7290 Service issuance status error detection
3 TECHNICAL SUPPORT INFORMATION (7) System error counts 0xE*72C0 Service double-start detection count (TI wait) 0xE*72C0 Service acceptance completion buffer-busy detection count 0xE*72C0 Service response queue-busy detection count 0xE*72C0 Service response report wait detection count 0xE*72C0 System message queue-busy detection count 0xE*72C0 System message buffer-busy detection count 0xE*72C0 AI queue-busy detection count 0xE*72C0 AI buffer-busy detection count 0xE*72D0 Exclusive alloca
3 TECHNICAL SUPPORT INFORMATION Trace information (1) Normal trace table structure CPU address Table structure 0xE*2000 Trace header +0x00 0xE*2010 Case #1 (16 bytes) +0x02 15 0 Trace stop flag: 0x00000000: Tracing in progress. 0x00000000: Tracing stopped. Trace stop flag +0x04 Trace pointer Trace pointer. A pointer to the area to which trace data is to be written next. The pointer’s lower word is the lower word of the address.
Error response transmission buffer acquisition was not successful. 3 - 152 - https://www.truck-manuals.net/ The connection establishment process was ended normally. A response was received in the connection establishment process. The connection establishment process was ended abnormal (service code improper). The connection establishment process was ended abnormally (connection size mismatch). The connection establishment process was abnormal (data length improper).
A command double-start was attempted. Command response report. AI report The AI report queue table was full. An AI report was awaited (AI report buffer full or TI not reported yet). 3 4 5 6 7 Error stop Type: 0 = Normal trace. 1 = Special trace. 1 No. Trace name Command TI report 2 μOS link function A command was received. Trace name 1 No.
√ 16 - 154 - https://www.truck-manuals.net/ √ √ √ S: Server. √: Applicable. C: Client. 25 √ 24 23 √ 22 21 √ 20 19 √ 18 √ √ 15 17 √ √ √ 14 13 √ 12 11 √ 10 √ (*) A byte-swapped value is set. 0x420F 0x420E 0x420D 0x420C 0x420B 0x420A 0x4209 0x4208 0x4207 0x4206 0x4205 0x4204 0x4203 0x4202 0x4201 0x4108 0x4107 8 Transmission was unachievable (a transmission double-start was attempted [starting source: IFO]).
Trace name - 155 - https://www.truck-manuals.net/ √ A reception was canceled (InstanceType was I/O). 43 0x4402 0x4403 √ An Ack reception was canceled (the received Ack data length was abnormal). An Ack reception was canceled (the received Ack sequence number did not agree with the Ack sequence number whose reception was awaited).
0x4502 √ Transmission was unachievable (the received Ack status was abnormal). √ 58 - 156 - https://www.truck-manuals.net/ – – – – – – – 69 70 71 72 73 74 75 0x4907 0x4908 I/O transmission was unachievable (an InitialCommCharacteristics mismatch occurred). 0x4906 0x4905 0x4904 0x4903 0x4902 I/O transmission was unachievable (an Instance Type mismatch occurred). An I/O reception was canceled (the connection status was other than “Established”).
– 77 0 0 0 Trace data [2] Received data[2] 0 0 0 Received data[3] Trace data [3] AI report Log name co_send A CAN transmission was started (error response transmission to a short √ request). 84 - 157 - https://www.truck-manuals.net/ – – – – – – – – – – 89 90 91 92 93 94 95 96 97 98 0x4B0A 0x4B0B An I/O reception was canceled (an Instance Type mismatch occurred).
Trace name - 158 - https://www.truck-manuals.net/ A response reception was canceled (CloseResponse was improperly timed). A response reception was canceled (the CloseResponse data length was illegal). A response reception was canceled (the heartbeat data length was illegal). A response reception was canceled (an illegal response other than Error Response was received). A response reception was canceled (the Shutdown data length was illegal). (*) A byte-swapped value is set.
A request reception was canceled (the State was the Configuring state). A request reception was canceled (Fragment [Frag = 1] or Response [R/R = 1]). A request reception was canceled (the received data did not contain data before the service code). A request reception was canceled (the OpenRequest received data length was illegal). A request reception was canceled (the CloseRequest received data length was illegal). A DupMAC reception was canceled (the received data length was illegal).
A response was reported with the queue table full. 9 0x7031 0x7030 (*) A byte-swapped value is set. 0x7042 A response was reported. 8 0x7021 13 The buffer for system message reception was full. Service request acceptance was completed with the buffer full. 7 0x7020 0x7041 A service TI was reported. 6 0x7011 12 A system message was reported with the queue table full. A service was called before the report of a previous service TI. 5 0x7040 “Explicit” was accepted.
0x9040 0x9050 0x9060 0x9070 A CAN transmission timeout detection trace was performed. An explicit message cancel trace was performed due to a CAN transmission timeout. A CAN chip error trace was performed. A trace was performed on the completion of a transmission message write into the CAN chip (other than I/O). 6 7 8 9 - 161 - https://www.truck-manuals.net/ 0xB010 Internal Start call trace was performed. A “recovery from ‘bus-OFF retry limit exceeded’ condition” trace was performed.
- 162 - https://www.truck-manuals.net/ – – – – – – – – – – – 14 15 16 17 18 19 20 21 22 23 24 0xaB12 0xaB13 0xaB14 (IoSequence:) An I/O reception was canceled (fragmented data whose type was other than the beginning or end to which FragCnt is set equal, was received in a wait for the beginning)). (IoSequence:) An I/O reception was canceled (the cumulative length of received fragmented data exceeded the maximum permissible received data length).
– – 26 27 Trace name (Proxy:) Explicit transmission semaphore flag acquisition failed (G2OnliClient). (Proxy:) Explicit transmission semaphore flag acquisition failed (G2OnliClient). (Proxy:) Proxy non-fragmented data delivery was unachievable (slave-totool delivery transmission buffer acquisition failed). (Proxy:) Proxy non-fragmented data delivery was unachievable (tool-to√ slave delivery transmission buffer acquisition failed).
An I/O reception was accepted. The I/O reception report queue table was full. 3 4 I/O reception reporting was completed. 8 - 164 - https://www.truck-manuals.net/ A CAN invalid interrupt was generated. A remote frame reception was performed. 4 5 (*) A byte-swapped value is set. A CAN chip error trace was performed. An I/O sequence control frame cancel trace was performed due to a CAN transmission timeout.
3 3.16 3.16.1 TECHNICAL SUPPORT INFORMATION ET.NET (Model LQE720) Error Information Error codes from the socket handler The table below enumerates all error codes that are returned from the socket handler to report on the occurrence of errors. In addition to these error codes, the table also provides information on the error causes and the user actions required to solve the problems.
3 TECHNICAL SUPPORT INFORMATION Table 3-17 Error code Brief description Error Codes from the Socket Handler (2/2) Cause Required action • A port has been released (due to an RST reception) when the handler was called (this error is related to tcp_open()); or • A port was already released when the handler was called (this error is related to tcp_send() or tcp_receive()).
3 TECHNICAL SUPPORT INFORMATION (*) A “duplicate socket” error occurs in the following way: If a socket is opened by calling tcp_open() or tcp_popen() with a specification of the local station’s port number, and an attempt is made to close that socket by calling tcp_close in the same local station, then the socket will immediately enter the TIMEWAIT state (see the connection state transitions diagram under “3.19.
3 TECHNICAL SUPPORT INFORMATION 3.17 Error Freeze Information On detection of a hardware error, the modules listed below light the error LED indicator, save the error freeze information in a predetermined area, and then stop their operation. ET.NET, SV.LINK, OD.RING, SD.LINK, J.NET, J.NET-INT, IR.LINK, FL.NET, EQ.LINK, RS232C, RS-422 For the address at which the error freeze is saved, see the information under “3.8 Memory Maps for Optional Modules.
3 TECHNICAL SUPPORT INFORMATION The table below lists the error codes stored as error freeze information. Meaning No.
3 TECHNICAL SUPPORT INFORMATION Meaning No.
2 2 15 Vector offset program counter Next-instruction Status register 2 C 15 Vector offset counter Return program Status register DBUF 2 0 2 Vector offset counter Return program Status register Status register before exception occurrence has occurred. Address at which a fault C 15 2 - 171 - https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION RS-232C (LQE560), RS-422 (LQE565) Stack frame for errors other than bus/address errors 15 /**0450 /**0452 /**0454 0 Stack frame for bus/address errors 15 Status register 4 3 2 1 0 R/W I/N FC Program counter Access address /**0456 Instruction register /**0458 Status register /**045A Program counter /**045C R/W (Read/Write): = 0: Write; = 1: Read. I/N (Instruction/Non-instruction): = 0: Instruction; = 1: Non-instruction.
3 3.18 TECHNICAL SUPPORT INFORMATION Memory Dump Procedure To dump the S10V controller’s memory, start the S10V BASE SYSTEM by choosing [Start] – [Programs] – [Hitachi S10V] – [S10V BASE SYSTEM] on the personal computer connected with the S10V controller. Then, click the Memory Dump button. The [Memory Dump] window shown below then appears, which enables you to dump the S10V controller’s memory. For details on the S10V BASE SYSTEM, refer to the “BASIC MODULES (manual number SVE-1-100).
3 TECHNICAL SUPPORT INFORMATION (4) Choose either the “Whole memory” or the “Specifies a range” option in the “Preserving range” group. If you have chosen the latter option, you can enter values in both the “Top address” and “Save size” boxes. In these boxes, specify the starting address of the memory area you want to dump and the size of that area. (5) Choose either the “ASCII form” or the “Binary form” option in the “Dump file format” group.
3 TECHNICAL SUPPORT INFORMATION (6) If you want to carry out a memory dump at high speed, check the “High speed save mode” checkbox. If not (i.e., you are carrying it out at standard speed), make sure that the said checkbox is deselected. (7) If you want to save the content of the optional-modules area (/0080 0000 to /00FF FFFF), check the “Save option module area” checkbox. In this case, only the information on the installed optional modules will be saved.
3 TECHNICAL SUPPORT INFORMATION Dumpable memory ranges The figure below shows all memory ranges that can be subjected to memory dumps. If you dump the entire memory, only all the dumpable memory ranges are dumped. If you dump a specified memory range, it is dumped as long as its starting address is not within any nondumpable range. In addition, if a specified memory range includes a non-dumpable range(s), only the dumpable portion is dumped. If an RS-232C or ET.
3 3.19 3.19.1 TECHNICAL SUPPORT INFORMATION Network Information Displaying network information To display system-maintained network information on screen, start the S10V BASE SYSTEM by choosing [Start] – [Programs] – [Hitachi S10V] – [S10V BASE SYSTEM] on the personal computer connected with the S10V controller. Then, click the Display Status of Network button. The network information functions list window then appears. In this window, click the Display Status of Network button.
3 TECHNICAL SUPPORT INFORMATION (2) From the “Module name” pulldown menu in the “Selection of Display module” box, choose the module for which you want to display network information. Then, by clicking the desired tab in the window, choose the type of network information you want to display on screen.
3 3.19.2 TECHNICAL SUPPORT INFORMATION Network information details (1) Socket information The socket information displayed as shown below is a list of the currently existing network connections. where: • Proto The name of the protocol used over the connection. • Local Address The IP address of the local host (source of connection). If the IP address is not bound with a socket, an asterisk (“*”) is displayed instead. • Port The port number of the local host (source of connection).
3 TECHNICAL SUPPORT INFORMATION • Port The port number of the remote host (destination of connection). If the IP address is not bound with a socket, an asterisk (“*”) is displayed instead. • State The connection status of the TCP protocol. The connection state is one of the following 11 states: Displayed symbol Meaning CLOSED Currently not in use. LISTEN Waiting for a port to become available.
3 TECHNICAL SUPPORT INFORMATION All possible state transitions between the connection states are as follows: Processing (reception/transmission flag): ACK: Positive acknowledgement flag SYN: Connection check flag FIN: End-of-connection flag x: (no flag provided) CLOSED Passive open Close Active open (x/SYN) LISTEN Transmission (x/SYN) (SYN/SYN+ACK) (SYN/SYN+ACK) SYN_RECEIVED (ACK/x) SYN_SENT (SYN+ACK/ACK) Close (x/FIN) ESTABLISHED Close (x/FIN) (FIN/ACK) FINWAIT1 (ACK/x) CLOSEWAIT Close (x/FIN)
3 TECHNICAL SUPPORT INFORMATION (2) Interface information The interface information displayed as shown below is concerning the network interfaces currently in operation and includes input/output packet count information. where: ① slot The slot number of the slot in which a module subjected to this display process is mounted. ② kind Always the string “EPORT” is displayed as this item.
3 TECHNICAL SUPPORT INFORMATION ⑦ output request count A count of the number of send requests that were accepted for message transmission. ⑧ output count(success) A count of the number of message transmissions that were done successfully. ⑨ output discard error count A count of the number of message transmissions that failed due to memory shortage.
3 TECHNICAL SUPPORT INFORMATION (3) Memory information The memory information displayed as shown below is the statistics maintained by the memory management routine. where: • CURRENT: The current state of mbuf. • MAX: The status of mbuf at its maximum utilization. • HIGH: Peak value for each item. • DROP: The status of mbuf in the event of an overflow. ① Cluster top address The starting address of the cluster memory. - 184 - https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION ② mbufs in use The number of mbufs currently in use, and the total number of allocated mbufs. following table shows details of the mbufs currently in use. Item The Description data The number of mbufs in which communication data is stored. packet headers The number of mbufs in which a packet header is stored. socket structures The number of mbufs in which a socket structure is stored.
3 TECHNICAL SUPPORT INFORMATION (4) Routing information The routing information displayed as shown below is concerning the routes registered in the CMU and ET.NET modules. where: ① Destination The network address of the destination. In the case of virtual network addresses, an asterisk (“*”) is appended to the end of the address value. ② Gateway The IP address of the gateway associated with the destination. ③ Flags Information indicating the status of the route.
3 TECHNICAL SUPPORT INFORMATION ④ Refcnt A count of the number of users who are using the route. ⑤ Metric A hop count of the number of gateways that are present in the route to the destination. ⑥ Interface Always the string “EPORT” is displayed as this item. - 187 - https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION (5) IP statistical information The IP statistical information displayed as shown below is a set of statistics concerning the IP protocol. where: ① IP forwarding Since forwarding is not supported, the string “host” is displayed as this item. If it was supported, an indication would be displayed which indicates whether it is operating as a forwarding gateway. ② default TTL The default value of TTL (Time To Live) that determines the maximum hop count.
3 TECHNICAL SUPPORT INFORMATION ⑥ packets forwarded The total number of IP packets that were forwarded (or routed to another interface). ⑦ unknown (or unsupported) protocol The total number of IP packets whose IP header contained a specification of an undefined upper protocol. ⑧ input packets discarded The total number of IP packets that were received but discarded without being delivered to an upper protocol because of a buffer area shortage, or that the upper protocol refused to receive.
3 TECHNICAL SUPPORT INFORMATION (6) ICMP statistical information The ICMP statistical information displayed as shown below is a set of statistics concerning the ICMP protocol. where: ① Messages The total number of ICMP messages that were processed. ② Errors The total number of ICMP error messages that were processed. ③ Destination Unreachable The total number of ICMP messages that could not be transmitted to the destination.
3 TECHNICAL SUPPORT INFORMATION ⑥ Source Quenches The total number of ICMP messages that requested the control of transmissions because of a resource shortage on the receiving side. ⑦ Redirects The total number of ICMP messages that reported on the existence of a more suitable route to the destination. ⑧ Echos The total number of ICMP messages that were transmitted from the sending side of ping. ⑨ Echo Replies The total number of ICMP messages that were returned from the receiving side of ping.
3 TECHNICAL SUPPORT INFORMATION (7) TCP statistical information The TCP statistical information displayed as shown below is a set of statistics concerning the TCP protocol. where: ① retransmitting algorithm Name of the retransmission timeout (RTO) algorithm used. ② minimum value of retransmission timeout(milliseconds) The minimum value of retransmission timeout period expressed in milliseconds.
3 TECHNICAL SUPPORT INFORMATION ⑦ attempt fails The number of connection requests whose attempt to connect failed. ⑧ establish resets The number of connection requests that were rejected during their processing. ⑨ current establish The total number of TCP connections currently active. ⑩ segments received The total number of segments (units of data each transmitted by TCP at a time) that were received. ⑪ segments sent The total number of segments that were transmitted.
3 TECHNICAL SUPPORT INFORMATION (8) UDP statistical information The UDP statistical information displayed as shown below is a set of statistics concerning the UDP protocol. where: ① packets received The total number of UDP packets that were received. ② no application at the destination port The number of UDP packets for which no receiving application (port number) could be found at the destination.
3 TECHNICAL SUPPORT INFORMATION (9) Cumulative information The cumulative information displayed as shown below is a variety of counts maintained in the existing interface modules. The following is a description of the log numbers 001 through 129 displayed as cumulative information. All log numbers other than listed are used as internal information for maintenance purposes. Log number 001: Receiving frame (success) The number of frames that were received normally.
3 TECHNICAL SUPPORT INFORMATION Log number 006: Total byte of the receiving frame to LAN The total number of bytes of the frames that were received from the communication line. Log number 007: (LSI) Receiving data of unusual size The number of frames whose frame length was abnormal. Log number 008: CMU: (LSI) Bubble errors Unused ET.NET: (LSI) The number of times which failed in sending since 3.2msec was exceeded The number of transmissions that failed due to a transmission delay (i.e.
3 TECHNICAL SUPPORT INFORMATION Log number 016: (LSI) Retry errors The number of retry errors (i.e., attempts to do more retries than permitted) that occurred during transmission. Log number 017: (LSI) Framing errors The number of framing errors that occurred during reception. Log number 018: (LSI) Received overflow The number of receive-buffer overflows that occurred during reception. Log number 019: (LSI) CRC errors The number of frame CRC errors that occurred during reception.
3 TECHNICAL SUPPORT INFORMATION (10) ARP table information The ARP table information displayed as shown below is the contents of the translation table that is used by the ARP (Address Resolution Protocol) for translation of IP addresses to physical addresses. where: ARP information ① uno A value of 1 is always displayed as this item. ② kind The string “EPORT” is always displayed as this item. Interface Information ARP entries that are registered.
3 TECHNICAL SUPPORT INFORMATION ② IP Address The IP address of the destination registered in the ARP table. ③ Physical Address The physical address(es) of the destination(s) registered in the ARP table. If an ARP entry is found invalid, the string “(incomplete)” is displayed instead. ④ State The current state(s) of the ARP entry (entries). The possible states are as follows: State name displayed Meaning permanent Fixed entry published Proxy ARP entry - 199 - https://www.truck-manuals.
3 TECHNICAL SUPPORT INFORMATION 3.20 Network Maintenance Commands Command Function CMU ET.NET NCP-F LANCP svarp Displays or modifies the address translation table. √ √ √ √ svnetstat Displays the network status. √ √ √ √ nu nu √ nu nu nu √ nu √ √ nu √ svfrstat svfrtest svnetlog Displays the ring map, the station configuration, and operation information. Instructs configuration modification for the specified machine on the ring, or performs a loopback test.
3 3.20.1 TECHNICAL SUPPORT INFORMATION Usage To use network management commands, specify the following storage location and enter each command in the general command form shown below. C:\Hitachi\S10V\S10BASE\bin The above pathname assumes that the S10V BASE SYSTEM is installed in the folder identified by the pathname “C:\Hitachi\S10V\S10BASE”.
3 TECHNICAL SUPPORT INFORMATION svarp svarp -- display or modify ARP information (correspondence between internet addresses and MAC addresses). svarp target_ctlr interface host svarp target_ctlr interface -a svarp target_ctlr interface -d host svarp target_ctlr interface -s host etaddr The svarp command displays or modifies the table that translates Internet addresses used by the address resolution protocol (ARP) to MAC addresses.
3 TECHNICAL SUPPORT INFORMATION svnetstat svnetstat -- display the network status. svnetstat target_ctlr interface [ -a | -i | -m | -r | -s | -rs ] svnetstat target_ctlr interface -fm sn The svnetstat command displays the data structures related to various networks. target_ctlr: Specifies the host name or dot internet address of the controller in need of maintenance. interface: Specifies the unit number of the interface in need of maintenance.
3 TECHNICAL SUPPORT INFORMATION The following examples of displays show the display formats used by the svnetstat command, which vary depending on the type of option used. (1) Socket status display format (when no option or the -a option is used) Proto Local Address Foreign Address (state) tcp 158.212.107.198.1105 158.212.109.150.1122 SYN_SENT Proto: The name of the protocol used. Local Address: The IP address and port number of the local host.
3 TECHNICAL SUPPORT INFORMATION (3) Interface information display format (when the -i option is used) UNIT NO. 5: slot = 5 kind = LANCP MTU = 1500 IP address = 160.160.0.1 Netmask = 255.255.0.0 broadcast address = 160.160.255.
3 TECHNICAL SUPPORT INFORMATION (4) Statistical information display format (when the -s option is used) ip: ip forwarding:host ... (a) 0 default TTL ... (b) 0 total packets received ... (c) 0 errors in IP headers ... (d) 0 invalid IP address ... (e) 0 packets forwarded ... (f) 0 unknown (or unsupported) protocol ... (g) 0 input packets discarded ... (h) 0 in delivered ... (i) 0 out requests ... (j) 0 output packets discarded ... (k) 0 packets discarded because no route ...
3 TECHNICAL SUPPORT INFORMATION icmp: 0 messages recieved 0 error messages 0 destination unreachable 0 time exceeded 0 parameter problem 0 source quench 0 redirect 0 echo 0 echo reply 0 timestamp 0 timestamp reply 0 address mask request 0 address mask reply 0 messages sent 0 error massages 0 destination unreachable 0 time exceeded 0 parameter problem 0 source quench 0 redirect 0 echo 0 echo reply 0 timestamp 0 timestamp reply 0 address mask request 0 address mask reply ... (A) ... (B) ... (C) ... (D) ...
3 TECHNICAL SUPPORT INFORMATION (a) Indicates whether it is operating as an IP gateway. (“gateway”: Operating as a gateway; host: Not operating as a gateway) (b) Default value of Time-to-Live for IP packets. (c) Total number of received IP packets. (d) The number of packets discarded due to IP header errors. (e) The number of packets discarded due to destination address errors. (f) The number of forwarded packets.
3 TECHNICAL SUPPORT INFORMATION The accumulated values Except for (A), (B), (N), and (0), all counts are displayed only when they indicate packets were actually sent or received. (A) The number of received ICMP messages -- this number includes (B). (B) The number of ICMP messages resulting in reception errors. (C) The number of received ICMP Destination Unreachable messages.
3 TECHNICAL SUPPORT INFORMATION ① Retransmission algorithm type. ② Minimum retransmission time-out value (milliseconds). ③ Maximum retransmission time-out value (milliseconds). ④ Maximum number of TCP connections that can be opened concurrently. ⑤ The number of active opens made. ⑥ The number of passive opens made. ⑦ The number of state transitions made from SYN-SENT or SYN-RCVD to CLOSE. ⑧ The number of state transitions made from ESTABLISHED or CLOSE-WAIT to CLOSE.
3 TECHNICAL SUPPORT INFORMATION (5) Memory statistical info display format (when the -m option is used) Format used when an NCP-F interface is specified: Top Free Aline addr addr addr 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX Total Use Wait Peack Overflow buff cnt cnt cnt 0 0 0 cnt cnt 0 0 Page Refcnt Aline 0 0 0 0 0 0 Page Block Use Aline Addr CBIX 0 0 0 0 0xXXXXXXXX 0xXXXXXXXX 0 0 0 0 0xXXXXXXXX 0xXXXXXXXX 0 0 0
3 TECHNICAL SUPPORT INFORMATION Format used when a built-in LANCE or LANCP interface is specified: CURRENT: XXX/XXX mbufs in use: XXX mbufs allocated to data XXX mbufs allocated to packet headres XXX mbufs allocated to socket structures XXX mbufs allocated to protocol control blocks XXX mbufs allocated to routing table entries XXX mbufs allocated to fragment reassemble queue headers XXX mbufs allocated to socket names and addresses XXX mbufs allocated to socket options XXX mbufs allocated to interface add
3 TECHNICAL SUPPORT INFORMATION DROP: XXX/XXX mbufs in use: XXX mbufs allocated to data XXX mbufs allocated to packet headres XXX mbufs allocated to socket structures XXX mbufs allocated to protocol control blocks XXX mbufs allocated to routing table entries XXX mbufs allocated to fragment reassemble queue headers XXX mbufs allocated to socket names and addresses XXX mbufs allocated to socket options XXX mbufs allocated to interface addresses XXX/XXX Kbytes allocated: XXX Kbytes allocated to mbufs XXX Kby
3 TECHNICAL SUPPORT INFORMATION (6) Routing statistical info display format (when the -rs option is used) -- IP Routing Statistics -IP Addr(uno) *160.10.0.10(3) 170.10.0.20(5) 170.20.0.20(6) 160.20.0.160(4) Ipkts 50 25 20 0 Ierrs D_uno 10 5 0 0 Routing Opkts Oerrs 5 20 10 1 6 20 10 0 3 20 10 0 4 0 0 0 3 20 10 0 4 0 0 0 5 0 0 0 6 0 0 0 IP Addr: IP address of the NCP-F interface that reported packet reception to the routing feature.
3 TECHNICAL SUPPORT INFORMATION svnetlog svnetlog -- display count information. svnetlog target_ctlr interface The svnetlog command displays count information for a specified interface. target_ctlr: Specifies the host name or Internet address in dot-separated format of a controller in need of maintenance. interface: Specifies the unit number of an interface in need of maintenance.
THIS PAGE INTENTIONALLY LEFT BLANK. https://www.truck-manuals.
4 ERROR LOG INFORMATION https://www.truck-manuals.
4 ERROR LOG INFORMATION 4.1 Displaying Error Log Information To display error log information on screen, start the S10V Base System by choosing [Start] – [Programs] – [Hitachi S10V] – [S10V BASE SYSTEM] on the Windows® personal computer connected with the LPU unit. Then, the [S10BASE] window appears. In this window, click the Error Log button. The [Error log information] window then appears, which enables you to view the information on errors that occurred in individual modules.
4 4.2 ERROR LOG INFORMATION Error Log Information and Required Actions 4.2.1 LPU (model LQP510) error log info and required actions (1/3) Error code Meaning Required action At startup, the self-diagnosis capability detected an error. Reset the LPU module and then check if the same error recurs. If so, replace the LPU module.
4 ERROR LOG INFORMATION (2/3) Error code Meaning Required action 0x120A User arithmetic function registration address A registration address for a user arithmetic function is set error outside SEQ-RAM. Review the setting. 0x120B RAM parity error (detected when an access was made to it from the system bus) Reset the LPU module. Then, if the same error recurs, replace the module.
4 ERROR LOG INFORMATION (3/3) Error code Meaning Required action 0x2301 LPU battery low The backup battery is low. Replace the battery. For details, refer to the information provided under “10.2 Replacing the Backup Battery” in the “BASIC MODULES (manual number SVE-1-100).” 0x2401 Optional-module startup check error One of the mounted optional modules is not up and running. View the error log on the optional module and remove the cause of the error. - 221 - https://www.truck-manuals.
4 ERROR LOG INFORMATION 4.2.2 CMU (model LQP520) error log info and required actions CMU-related errors are reported by presenting error messages in one of the formats shown under “4.3 CMU Error Message Formats.” (1/4) No.
4 ERROR LOG INFORMATION (2/4) No.
4 ERROR LOG INFORMATION (3/4) No.
4 ERROR LOG INFORMATION (4/4) No.
4 ERROR LOG INFORMATION 4.2.3 FL.NET (model LQE500/502) error log info and required actions (1/2) Error code Meaning Required action 0x0010 Bus error 0x0011 Address error 0x0012 Illegal instruction 0x0013 Division by zero 0x0014 Privileged-instruction violation 0x0016 Format error 0x0017 Spurious interrupt 0x0018 Unsupported exception 0x0019 Parity error 0x0100 Module no. setting error The module no. setting switch is set incorrectly. Correct the module no.
4 ERROR LOG INFORMATION (2/2) Error code Meaning Required action 0x0202 Node number duplicated The set node number of the FL.NET module is duplicated with another node’s in the same network. Check the node number of the other node and correct the duplicated node number. (If this type of error occurs, the node for which the duplicated node number is set is blocked from participating in the network, as is prescribed in the FA link protocol’s rules.
4 ERROR LOG INFORMATION 4.2.4 OD.RING (model LQE510/515) error log info and required actions Error code Meaning Required action 0x0010 Bus error Reset the LPU module. Then, if the same error recurs, the OD.RING module may be in a failure condition. Replace the module.
4 ERROR LOG INFORMATION 4.2.5 ET.NET (model LQE520) error log info and required actions Error code Meaning Required action 0x0010 Bus error 0x0011 Address error 0x0012 Illegal instruction 0x0013 Division by zero 0x0014 Privileged-instruction violation 0x0016 Format error 0x0017 Spurious interrupt 0x0018 Unsupported exception 0x0019 Parity error 0x0100 Module no. setting error The module no. setting switch is set incorrectly. Correct the module no.
4 ERROR LOG INFORMATION 4.2.6 SV.LINK (model LQE521) error log info and required actions Error code Meaning Required action 0x0010 Bus error 0x0011 Address error 0x0012 Illegal instruction 0x0013 Division by zero 0x0014 Privileged-instruction violation 0x0016 Format error 0x0017 Spurious interrupt 0x0018 Unsupported exception 0x0019 Parity error 0x0100 Module no. setting error The module no. setting switch is set incorrectly. Correct the module no.
4 ERROR LOG INFORMATION 4.2.7 SD.LINK (model LQE530) error log info and required actions Error code Meaning Required action 0x0010 Bus error Reset the LPU module. Then, if the same error recurs, the SD.LINK module may be in a failure condition. Replace the module.
4 ERROR LOG INFORMATION 4.2.8 J.NET (model LQE541) / J.NET-INT (model LQE547) error log info and required actions (1/3) Error code Meaning Required action Reset the LPU module. Then, if the same error recurs, the J.NET/J.NET-INT module may be in a failure condition. Replace the module.
4 ERROR LOG INFORMATION (2/3) Error code Meaning Required action 0x0112 Non-matching parameter type detected (e.g., a parameter specified for use in an S10mini controller), or parameter error (incorrect SUM value) A parameter previously set for use in an S10mini controller, or a parameter error is detected. Correct the parameters by referring to the information provided under “4.2 Commands” in the “J.NET (manual number SVE-1-132)” or “J.NET-INT (manual number SVE-1-133).
4 ERROR LOG INFORMATION (3/3) Error code Meaning Required action 0x7110 Undefined service requested 0x7120 Data length error 0x7130 Packet structure error 0x8020 SVPT error -- an initialization request is rejected. 0x8081 SVPT error -- in AUTO mode, the defined number of transfer bytes does not match the response I/O size from the remote station. 0x8082 SVPT error -- with a specified slot, the defined number of transfer bytes does not match the response I/O size from the remote station.
4 ERROR LOG INFORMATION 4.2.9 IR.LINK (model LQE548) error log info and required actions (1/3) Error code Meaning Required action 0x0010 Bus error Reset the LPU module. Then, if the same error recurs, the IR.LINK module may be in a failure condition. Replace the module.
4 ERROR LOG INFORMATION (2/3) Error code Meaning Required action • Check if the communication line is functioning properly. • Check if there is any mismatch between the parameter settings and remote-station settings. • After the above checks and troubleshooting, if the same error recurs, replace the IR.LINK module.
4 ERROR LOG INFORMATION (3/3) Error code Meaning 0x8020 SVPT error -- an initialization request is rejected. 0x8081 SVPT error -- in AUTO mode, the defined number of transfer bytes does not match the response I/O size from the remote station. 0x8082 SVPT error -- with a specified slot, the defined number of transfer bytes does not match the response I/O size from the remote station.
4 ERROR LOG INFORMATION 4.2.10 Error code CPU LINK (model LQE550) error log info and required actions Meaning Required action 0x0002 WDT timeout error Reset the LPU module. Then, if the same error recurs, the interCPU link module may be in a failure condition. Replace the module. 0x0004 ROM checksum error -- an error is detected in the ROM. 0x0008 RAM check error -- an error is detected in the system program. 0x0010 RAM parity error -- a parity error is detected in the RAM.
4 4.2.11 ERROR LOG INFORMATION RS-232C (model LQE560) / RS-422 (model LQE565) error log info and required actions (1/3) Error code Meaning Required action 0x0010 Bus error 0x0011 Address error 0x0012 Illegal instruction 0x0013 Division by zero 0x0014 Privileged-instruction violation 0x0015 WDT timeout error 0x0018 Unsupported exception 0x0019 RAM parity error 0x0100 Module no. setting error The module no. setting switch is set incorrectly. Correct the module no.
4 ERROR LOG INFORMATION (2/3) Error code Meaning Required action 0x1083 • Check the destination device settings and communication Transmission suspension timed out -program. after a transmission in progress was suspended by a suspend code, it has not • Check the LGB settings. been resumed by a resume code within a specified transmission suspension monitoring time period. 0x1084 • Check if there is any incorrect control signal setting in the Send request (CS) timed out -- after a destination device.
4 ERROR LOG INFORMATION (3/3) Error code Meaning Required action Review the application running on the destination device. 0x2084 ASCII conversion error -- in a requested ASCII conversion, data outside the ranges “0” to “9” and “A” to “F” is received. 0x2085 End code error -- in a requested ASCII conversion, data outside the ranges “0” to “9” and “A” to “F”, or a non-end code is received. 0x2086 BCC error -- in a BCC reception, a BCC mismatch is detected by a specified BCC check.
4 ERROR LOG INFORMATION 4.2.12 Error code D.NET (model LQE570/575) error log info and required actions Meaning Required action 0x1401 MPU register compare error 0x1402 MPU operation check error 0x1403 CAN register compare error 0x1405 ROM compare error 0x1406 ROM checksum error, program-related 0x1407 RAM compare error 0x1409 MPU built-in timer diagnosis error 0x140A Module no. setting error The module no. setting switch is set incorrectly. Correct the module no.
4 ERROR LOG INFORMATION D.NET (model LQE770/775) error log info and required actions Error code 0x1401 0x1402 0x1403 0x1405 0x1406 0x1407 0x1409 0x140A 0x518C 0x140D 0x2404 0x34XX 0x4281 0x5188 0x5189 0x7381 0x8181 Meaning MPU register compare error MPU operation check error CAN register compare check error FROM compare check error FROM checksum error, microprogramrelated SRAM compare check error MPU built-in timer diagnosis error Module no. setting error Required action Reset the LPU module.
4 ERROR LOG INFORMATION 4.2.13 EQ.LINK (model LQE701) error log info and required actions (1/2) Error code Meaning Required action 0x0010 Bus error 0x0011 Address error 0x0012 Illegal instruction 0x0013 Division by zero 0x0014 Privileged-instruction violation 0x0016 Format error 0x0017 Spurious interrupt 0x0018 Unsupported exception 0x0019 Parity error 0x0100 Module no. setting error The module no. setting switch is set incorrectly. Correct the module no.
4 ERROR LOG INFORMATION (2/2) Error code Meaning Required action 0x0201 Common memory settings duplicated In the common memory division setup given, the local node’s common memory area is duplicated with the remote node’s. By referring to the information provided under “5.2.4 Setup common memory division” in the “EQ.LINK (manual number SVE-1-124),” correct the setup so that the common memory offset value may not be duplicated between the local and the remote node.
4 ERROR LOG INFORMATION 4.2.14 ET.NET (model LQE720) error log info and required actions ET.NET-related errors are reported by presenting error messages in one of the formats shown under “4.3 CMU Error Message Formats.” (1/3) No.
4 ERROR LOG INFORMATION (2/3) ALARM LED ERR LED LQE720 and LQE520 combination mounting error – ON EC=07D00018 Module error (TASK-ROM CHECKSUM ERROR) 42 %CPMS-W-HARD-0006 EC=07D01003 Module error (THE VERSION OF CMU MODULE IS OLD) ROM checksum error, communication task-related Model LQE720 module is mounted along with the CMU module not supporting it.
4 ERROR LOG INFORMATION (3/3) No.
4 4.2.15 ERROR LOG INFORMATION NCP-F (model LQE780-Z) error log info and required actions NCP-F-related errors are reported by presenting error messages in one of the formats shown under “4.3 CMU Error Message Formats.” (1/5) No.
4 ERROR LOG INFORMATION (2/5) No.
4 ERROR LOG INFORMATION (3/5) No.
4 ERROR LOG INFORMATION (4/5) No.
4 ERROR LOG INFORMATION (5/5) No. Error log title Error code Error message Brief description Error Error location classification Error handling in Re-issue it after Transmission unachievable due to the Network ring in Ring_Non_op condition configuration communication the node’s line (including ISOLATE condition) change participation in the ring. (*1) I/O error (SEND_ABORT) Transmission aborted due to MAC FDDI control Restart the system.
4 ERROR LOG INFORMATION 4.2.16 LANCP (model LQE790-Z/795-Z) error log info and required actions LANCP-related errors are reported by presenting error messages in one of the formats shown under “4.3 CMU Error Message Formats.” No.
4 4.3 ERROR LOG INFORMATION CMU Error Message Formats CMU-related errors are reported in the following formats. 4.3.
4 ERROR LOG INFORMATION 4.3.
4 Table 4-4 ERROR LOG INFORMATION Non-Panic Log Default Error Messages Format type Error message Program error Program error Macro parameter check error Macro parameter error I/O error I/O error WDT timeout error WDT timeout error Module error Module Error Kernel warning Kernel Warning Kernel information Kernel Information System down -- kernel trap System down System down -- built-in subroutine stoppage System down ADT error Program error Memory error Memory error System-bus err
4 ERROR LOG INFORMATION Possible format elements -- form 2: Non-panic log error messages of form 2 are displayed in the following format: %****-*-****-**** ① ② ③ ④ ① ID name of a system in which the error is detected CPMS: CPMS (basic OS) LNET: RCTLNET (network driver) NX: NXACP (autonomous distributed platform) MSxx: Middleware numbered xx, where xx is a 2-digit number in the range 01 to 16. USxx: Application software numbered xx, where xx is a 2-digit number in the range 01 to 16.
4 4.4 ERROR LOG INFORMATION RPDP Error Log Display Guide 4.4.1 Reading the error log This section serves as a short guide on how to read the content of the “Error Log Detail” window displayed by the svelog command of RPDP or by the S10V BASE SYSTEM. The following is an example of the “Error Log Detail” window displayed.
4 ERROR LOG INFORMATION System ID name in which the error was detected CPMS: CPMS (basic OS) LNET: RCTLNET (network driver) NX: NXACP (autonomous distributed platform) MSxx: Middleware numbered xx, where xx is a 2-digit number in the range 01 to 16. USxx: Application software numbered xx, where xx is a 2-digit number in the range 01 to 16. Error message (listed under “4.2 Error Log Information and Required Actions”) Program error: An error that affects the normal execution of the program.
4 ERROR LOG INFORMATION 4.4.2 Types of error logs (1) Types of OS error logs The error logs maintained by the OS can be classified as shown below. For information on the error messages in these error logs, see the error message lists provided under “4.2 Error Log Information and Required Actions.
4 ERROR LOG INFORMATION (2) Types of NXACP error logs The table below is a list of all predefined types of NXACP error logs.
4 ERROR LOG INFORMATION 4.4.3 Error log details and analysis (1) Program error This type of error is reported when a fault in a program causes the program to access an abnormal address in memory or execute an illegal instruction. When analyzing this type of error, use the following two-step preliminary procedure: Determine the nature of the error from the error name and other information in the displayed error message.
4 ERROR LOG INFORMATION Table 4-7 Program Error Message Format %CPMS-E-SOFT-0001 SITE=xxxxxxxxxxxxxx RC=xxxxxxxx yyyy/mm/dd hh:mm:ss LOG=xxx EC=xxxxxxxx Program error (subtitle) TN =xxxxxxxx PC =xxxxxxxx EXPEV=xxxxxxxx FADR =xxxxxxxx SR =xxxxxxxx PR =xxxxxxxx SP =xxxxxxxx GBR =xxxxxxxx MACH =xxxxxxxx MACL =xxxxxxxx R0 =xxxxxxxx R1 =xxxxxxxx R2 =xxxxxxxx R3 =xxxxxxxx R4 =xxxxxxxx R5 =xxxxxxxx R6 =xxxxxxxx R7 =xxxxxxxx R8 =xxxxxxxx R9 =xxxxxxxx R10 =xxxxxxxx R11 =xxxxxxxx R12 =xxxxxxxx R13 =xxxxxxxx R14 =
4 ERROR LOG INFORMATION (2/2) Item XFxx DRxx XDxx INST PC FADR PR Meaning The content of the 32-bit floating-point extension register numbered xx. When FPSCR.PR (19th bit of the bits 31 thru 0) = 0, these registers contain values of FPRxx_BANK1. When FPSCR.PR = 1, they contain values of FPRxx_BANK0. The content of the 64-bit floating-point register numbered xx. When FPSCR.PR (19th bit of the bits 31 thru 0) = 0, these registers contain values of FPRxx_BANK0. When FPSCR.
4 ERROR LOG INFORMATION Make sure that the displayed error message has the form “Program error (...)”. Check if the error message contains one of the following subtitles in parentheses: Data Page Fault Data Access Protection Invalid Data Access Invalid Inst. Access Inst.Alignment Error Data Alignment Error No Continued on next page. Yes Then, the error was caused by an attempt to access an abnormal address.
4 ERROR LOG INFORMATION Continued from preceding page Check if the displayed message subtitle is “FP Program error”. No Yes Then, the error was caused by something in a floating-point arithmetic operation. Determine the type of the error from the displayed FPSCR value. Then, the instruction that was executed is incorrect. Check whether or not the address pointed to by the PC in the displayed error log, i.e. the address at which the error occurred, is inside the text area of the task or IRSUB.
4 ERROR LOG INFORMATION The following is an example of a program error analysis based on an actually displayed error message.
4 ERROR LOG INFORMATION The displayed INST information reports on the failed instruction plus the preceding and succeeding instructions. From this information piece, you can determine the failed instruction from the code 0x2d22e3bc, which represents the following machine instructions: MOV.L R2,@R13 MOV #-68,R3 Of these, the first instruction stores the content of general register 2 in the location indicated by the content of general register 13.
4 ERROR LOG INFORMATION (2) Macro parameter check error This type of error is reported when an erroneous parameter is detected in a macro instruction issued in a program to the CPMS. When such a parameter is detected, the issuing task is aborted. Find the erroneous parameter by referring to the displayed error message. The table below shows the general format of error messages for macro parameter check errors and describes each format element.
4 Table 4-10 ERROR LOG INFORMATION Predefined Supervisory Macro Codes and Macro Names Identified by Them SVC i 0000000i 0000001i 0000002i 0000003i 0000004i 0 – prsrv usrel 1 queue pfree elset gtkmem prog_start 2 rleas gfact (cpms_ginfo) wrtmem prog_switch 3 sfact gtime (chml) chkbmem prog_exit 4 abort exit (taskenv) chktaer prog_call 5 susp asusp (printf) getsysinfo 6 rsum arsum gettaskinfo 7 ctime open save_env 8 wait close 9 post read gettimebase A
4 ERROR LOG INFORMATION (3) I/O error Network I/O error This type of error is reported when an abnormality occurs in the network’s hardware or transmission path during accessing the network in a program using network access macros and libraries. The table below shows the general format of error messages for network I/O errors and describes each format element.
4 Item EC UNO DEV DVA IOEC TN DATn ERROR LOG INFORMATION Description Error Code: Identifies the type of the error detected. For details, see the information under “4.2.15 NCP-F error log info and required actions.” I/O Unit number: Is the unit number of the I/O unit used. Device number Identifies the type and mounting slot of the I/O device in which the error occurred.
4 ERROR LOG INFORMATION Table 4-12 DATn DAT0 Error Detail Data for Built-in LANCE-/LANCE-Detected I/O Errors (EC=0x078013XX) (1/2) Data name PCISTATUS info Detail data 30 30 29 28 27 26 25 DEVSEL timing 24 23 22 21 20 19 18 17 16 15 to 0 (Reserved) Command FastBackToBackCapable dataPerr sigTargetAbort recTargetAbort recMasterAbort sigSerr detectPerr Bit(s) 31 Name detectPerr Set value and its meaning 1: An A-/D-parity error was detected. 0: No A-/D-parity error was detected.
4 Table 4-12 DATn DAT1 ERROR LOG INFORMATION Error Detail Data for Built-in LANCE-/LANCE-Detected I/O Errors (EC=0x078013XX) (2/2) Data name CSR0 register Detail data Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 CSR0 ERR RES CERR MISS MERR RINT TINT IDON INTR IENA RXON TXON TDMD STOP STRT INIT (Bits 31 thru 16 are reserved.) ERR : An error occurred.
4 ERROR LOG INFORMATION Table 4-13 DATn DAT0 DAT1 Data name PCISTATUS info BUERRSTAT info Error Detail Data for Built-in LANCE PCI Bus I/O Errors (EC=0x078014XX) (1/5) Detail data See the description of DAT0 in Table 4-12.
4 Table 4-13 DATn DAT2 Error Detail Data for Built-in LANCE PCI Bus I/O Errors (EC=0x078014XX) (2/5) Data name BUERRINTENB info ERROR LOG INFORMATION Detail data 31 11 10 9 8 7 6 5 4 3 2 1 0 (Reserved) (Reserved) enbEINTO enbBRQTO enbBUSBUSY enbRDPE enbWDPE enbAPE enbSERR enbMA enbTA enbTRDYTO Bit(s) Name Set value and its meaning 31 to 11 (Reserved) 0x0000 00 10 enbBUSBUSY 1: An interrupt was generated due to an attempted bus access in a bus deadlock condition.
4 ERROR LOG INFORMATION Table 4-13 DATn DAT3 Data name BUERRADR info Error Detail Data for Built-in LANCE PCI Bus I/O Errors (EC=0x078014XX) (3/5) Detail data 31 0 errADR Bits Name 31 to 0 errADR DAT4 BUERRPTR info Set value and its meaning PCI address: Set when the PCI bus master has encountered the error. Processor address: Set when a “bus busy” condition or bus request timeout error is detected.
4 Table 4-13 DATn Data name DAT4 BUERRPTR info Error Detail Data for Built-in LANCE PCI Bus I/O Errors (EC=0x078014XX) (4/5) Detail data Bit(s) DAT5 BUERRINTMST info ERROR LOG INFORMATION 4 Name pntMA 3 2 (Reserved) pntAPE 1 pntWDPE 0 pntRDPE 31 Set value and its meaning 1: A master abort was observed. 0: A master abort was not observed. 0 1: An address parity error was detected. 0: An address parity error was not detected. 1: A write-data parity error was detected.
4 ERROR LOG INFORMATION Table 4-13 DATn Data name DAT5 BUERRINTMST info DAT6 BUERRCMD info Error Detail Data for Built-in LANCE PCI Bus I/O Errors (EC=0x078014XX) (5/5) Detail data 2 Bit(s) Name errMSTBU 1 errMSTNU 0 errMSTPU Set value and its meaning 1: The CALINK caused an error when it was master. 0: The CALINK did not cause any error. 1: The NPU caused an error when it was master. 0: The NPU did not cause any error. 1: The CPU caused an error when it was master.
4 Table 4-14 DATn DAT0 DAT4 to 6 Data name LANCP MSW6 LANCP MSW3 to 5 (Meaningful only when EC=0x07801601) Error Detail Data for LANCP I/O Errors (EC=0x078016XX) Detail data Register name MSW3 Bit(s) Name 31 ADDRVAL 30 DATAVAL 29 28 (Unused) PTYINFO 27 to 24 (Unused) 23 to 20 COMMD 19 to 16 BYTE MSW4 DAT1 DAT2 DAT3 DAT7 LANCP MSW0 LANCP MSW1 LANCP MSW2 (Meaningful only when EC=0x07801601) LANCP ICW2 ERROR LOG INFORMATION 15 to 0 (Unused) 31 to 16 Bus error 15 to 0 address MSW5 31 to 16
4 ERROR LOG INFORMATION Table 4-15 DATn Error Detail Data for Driver-Detected I/O Errors (EC=0x078015XX) Data name Detail data DAT0 (Unused) DAT1 LANCP MSW0 MSW0 when the error is related to the LANCP. For details, see the LANCP-related information under “(5) Module error.” DAT2 LANCP MSW1 MSW1 when the error is related to the LANCP. For details, see the LANCP-related information under “(5) Module error.
4 ERROR LOG INFORMATION I/O error This type of error is reported when a problem is detected during input or output with devices. The error detail data varies with devices in which an I/O error is detected.
4 ERROR LOG INFORMATION Table 4-17 Error Codes, Subtitles, and Their Meanings (for I/O Errors) No. Error code Subtitle Meaning Content of DATn 1 EC=07395010 ROM Board Error A hardware abnormality was detected during accessing the ROM (CF) board. For details on DATn, see Table 4-18.
4 Table 4-18 DATn DAT6 Error Detail Data for ROM Board Errors (2/2) Data name Detail data Status register Is a value read in from the Status register among the task file registers. value 0 23 24 25 26 27 28 0 DAT8 Logical block address Error register value 29 0 BUSY RDY DWF DSC DRQ CORR Bit no. Bit name Read-in value 0 to 23 － Always 0. 24 BUSY 0: Cause found. 1: Cause not found. 25 RDY 0: Cause found. 1: Cause not found. 26 DWF 0: Cause found. 1: Cause not found. 27 DSC 0: Cause found.
4 ERROR LOG INFORMATION (4) Watchdog timer timeout error This type of error is reported when a timeout is generated by the watchdog timer (WDT). A generated timeout indicates that, because a user task periodically executed to update the watchdog timer was not executed for some reason, the set time value could not be updated within the set timeout period. If this type of error occurs, a link is automatically made to the built-in subroutine called WDTES.
4 ERROR LOG INFORMATION (5) Module error This type of error is reported when a hardware abnormality is detected in a module. The table below shows the general format of error messages for module errors and describes each format element.
4 ERROR LOG INFORMATION Table 4-21 Error Codes, Subtitles, and Their Meanings (for Module Errors) (1/3) No. Error code Subtitle Meaning 1 EC=05000000 Invalid Interrupt An invalid interrupt was detected. The contents of MSW0, MSW1, and DAT0 are insignificant. 2 EC=05000001 Undefined Interrupt An interrupt code for which an interrupt-handling process is undefined was detected. DAT0: Is the interrupt code (INTEVT) of the generated interrupt.
4 Table 4-21 No. Error code 10 EC=0500C001 11 12 13 14 15 EC=05005001 EC=0D010000 EC=0d320000 EC=0d330000 EC=0d340000 ERROR LOG INFORMATION Error Codes, Subtitles, and Their Meanings (for Module Errors) (2/3) Subtitle NINTR Invalid Interrupt Meaning The module that reported on the occurrence of a communication interrupt could not be found. RINTR Invalid Interrupt The module that reported on the occurrence of an I/O interrupt could not be found.
4 ERROR LOG INFORMATION Table 4-21 No. Error code 16 EC=0d350000 Error Codes, Subtitles, and Their Meanings (for Module Errors) (3/3) Subtitle Meaning RAM Sum A RAM checksum error was Check Error detected. Content of MSW0, MSW1, and DATn DAT0: Is the MSW2 information for the module in which the error occurred. For information on the contents of MSW0, MSW1, and MSW2, see the information for that module in Table 4-22. 17 EC=0d360000 ROM Sum A ROM checksum error was Check Error detected.
4 Table 4-22 Module name CPU MSW Detail Data for Modules (1/6) MSW MSW0 0 Interface ID Bit no. 0 to 7 Bit name Interface ID 8 to 15 Module ID 16 to 23 － 24 BIST Cpbl 25 to 29 － 30 BIST MSW1 Detail data 15 16 23 7 8 31 ERROR LOG INFORMATION MHI Module ID 0 24 25 BIST 0 0 Cpbl 29 30 31 0 BIST MHI Read-in value Interface ID Meaning Module ID code provided for use in software Module ID Module ID code provided for use in hardware Always 0. 0: Not supported. 1: Supported. Always 0.
4 ERROR LOG INFORMATION Table 4-22 Module name MSW CPU MSW1 (continued from preceding page) MSW2 MSW Detail Data for Modules (2/6) Detail data Bit no. 6 Read-in value 1: RUN was flickering. 7 ERRF 1: ERR was flickering. 8 STBYF 1: STBY was flickering. 9 MERRF 1: MERR was flickering. 10 － Always 0. 11 ETH1LINK 1: Transmission was in normal progress. 12 ETH1ACTV Reception was in normal progress. 13 ETH2LINK Reception was in normal progress. 14 ETH2ACTV Reception was in normal progress. 15 Always 0.
4 Table 4-22 Module name CPU (continued from preceding page) MSW Detail Data for Modules (3/6) MSW MSW2 ERROR LOG INFORMATION Detail data Bit no. Bit name Read-in value Meaning 4 HWDT 1: Error detected. A hardware watchdog timer timeout was generated. 0: Error not detected. (For the CPU, this type of error is included in the category of EXE errors.) 5 SWDT 1: Error detected. A software watchdog timer timeout was generated. 0: Error not detected. 6 RAMS 1: Error detected.
4 ERROR LOG INFORMATION Table 4-22 MSW Detail Data for Modules (4/6) Module name NCP-F MSW Detail data MSW0 0 1 2 5 MHI BIST 0 0 6 RMVBL Cpbl 7 8 BIST 0 Cpbl Bit no. Bit name Read-in value 0 MHI 1: Initialization in progress. 0: Initialization ended. 1 BIST Always 0.
4 Table 4-22 Module name NCP-F (continued from preceding page) LANCP ERROR LOG INFORMATION MSW Detail Data for Modules (5/6) MSW Detail data MSW1 Bit no. Bit name Read-in value Meaning 12 to 21 － Always 0. － 22 WRAPB 1: Lit. 0: Not lit. WRAPB LED status 23 WRAPA 1: Lit. 0: Not lit. WRAPA LED status 24 NETONLN 1: Lit. 0: Not lit. NETONLN LED status 25 WDTO 1: Lit. 0: Not lit. WDTO LED status 26 MEME 1: Lit. 0: Not lit. MEME LED status 27 BTO 1: Lit. 0: Not lit.
4 ERROR LOG INFORMATION Table 4-22 Module name LANCP MSW Detail Data for Modules (6/6) MSW Detail data MSW1 0 1 2 MINT RINT 0 29 30 3 4 5 6 7 8 0 R6TO R6MA R6TA R6WP R6RP 9 0 10 11 12 R7DPE R7BE 0 28 0 31 ERR RUN RMVBLREQ Bit no. 0 Bit name MINT Read-in value 1: Interrupt not generated. Meaning Indicates whether or not a network-related interrupt was generated. 0: Interrupt generated. 1 RINT Always 0.
4 ERROR LOG INFORMATION (6) Kernel warning Although this type of message is not an error message, it indicates that an abnormality affecting the execution of the user program was detected. The table below shows the general format of kernel warning messages and describes each format element.
4 ERROR LOG INFORMATION (7) Kernel information This type of error is reported when a transient abnormality not affecting the execution of the user program at all is detected in the CPMS. The table below shows the general format of kernel information messages, followed by a short description.
4 ERROR LOG INFORMATION (8) System down -- system error This type of error is reported when an abnormality making further processing impossible is detected by the CPMS. The table below shows the general format of error messages for system errors and describes each format element.
4 ERROR LOG INFORMATION Table 4-27 Error Codes, Subtitles, and Their Meanings (for System Errors) No.
4 ERROR LOG INFORMATION (9) System down -- kernel trap This type of error is reported when an internal irrationality in the CPMS is detected during the execution of the CPMS. The table below shows the general format of error messages for kernel traps and describes each format element.
4 ERROR LOG INFORMATION (10) System down -- built-in subroutine error This type of error is reported when an error making further processing impossible is detected by the CPMS during the execution of a built-in subroutine. The table below shows the general format of error messages for built-in subroutine errors and describes each format element.
4 Table 4-30 ERROR LOG INFORMATION Error Codes, Subtitles, and Their Meanings (for Built-in Subroutine Errors) No. Error code 1 EC=03030000 Subtitle Alignment Error Brief description Alignment error Meaning An instruction’s operand was not aligned on word boundaries. 2 EC=03040000 Illegal Instruction Illegal-instruction error An attempt was made to execute an illegal instruction.
4 ERROR LOG INFORMATION (11) System down -- built-in subroutine stoppage This type of error is reported when a return value for a CPU stop request is returned from a built-in subroutine at the end of its execution. The table below shows the general format of error messages for built-in subroutine stoppages and describes each format element.
4 ERROR LOG INFORMATION (12) ADT error This type of error is reported when a specified access (R/W) is made to an address (trap) set by the user using the debugger. The table below shows the general format of error messages for ADT errors and describes each format element.
4 ERROR LOG INFORMATION Item TN PC SR PR SP GBR MACH MACL Rxx FPSCR FPUL FRxx XFxx DRxx XDxx BARA Description The task number of the task in which the error occurred. The content of the program counter. The content of the status register. The content of the procedure register, which is used in calling a subroutine and stores the return address to the calling routine. The content of the stack pointer -- the register R15 is used as the stack pointer.
4 Item BBRA ERROR LOG INFORMATION Description 25 26 27 28 29 30 31 0 24 0 0 SZA2 IDA1 IDA0 RWA1 RWA0 SZA1 SZA0 Bit no. 0 to 24 25, 30, 31 26, 27 28, 29 Bit name － SZA2, SZA1, SZA0 IDA1, IDA0 RWA1, RWA0 Read-in value Always 0. Specified value Specified value Specified value Meaning － Used in combination, specify an operand size for the bus cycle used as a break condition for channel A: 0, 0, 0: Do not use an operand size as part of the break condition. 0, 0, 1: Use byte access.
4 ERROR LOG INFORMATION Item BAMRB Description 0 0 27 0 Bit no. 0 to 27 29 Bit name － BASMB 28, 30, 31 BAMB2, BAMB1, BAMB0 28 BAMB2 Read-in value Always 0. 0: Included. 1: Not included. Specified value 29 BASMB 30 BAMB1 31 BAMB0 Meaning － Indicates whether or not all bits in BASRB are included in the break condition. Used in combination, specify the bits to be included in the break address (break condition) for channel B: 0, 0, 0: Do not mask in or out all the bits of BARB.
4 Item BASRB ERROR LOG INFORMATION Description 0 23 24 0 0 Bit no. 0 to 23 24 to 31 Bit name － BASRB Read-in value Always 0. Specified value 31 BASRB Meaning － Is the ASID used as a break condition for channel B. 0 0 16 15 0 17 18 0 19 0 20 0 21 22 0 23 0 24 25 26 0 27 0 28 29 0 30 0 31 CMFA CMFB UBDE SEQ PCBB DBEB PCBA INST PC PR Bit no.
4 ERROR LOG INFORMATION (13) Memory error This type of error is reported when a serious error (2-bit error by memory ECC) is detected in relation to memory. The table below shows the general format of error messages for memory-related serious errors and describes each format element.
4 Item TN PC EXPEV SR PR SP GBR MACH MACL Rxx FPSCR FPUL FRxx XFxx INST HERST ERROR LOG INFORMATION Description The task number of the task in which the error occurred. The content of the program counter. The content of the exception code register. The content of the status register. The content of the procedure register, which is used in calling a subroutine and stores the return address to the calling routine. The content of the stack pointer -- the register R15 is used as the stack pointer.
4 ERROR LOG INFORMATION Item MERRADR Description 0 3 4 0 0 29 30 31 ERROR_ADR Reserve Bit no. Bit name Read-in value Meaning 0 to3 － Always 0. － 4 to 29 ERROR_ Specified value Is the access address at which the ADR memory-related serious error was detected. 30 to 31 MERRDAT － － Always 0. 0 31 ERROR_DAT Bit no. 0 to 31 Bit name ERROR_ Read-in value Specified value DAT MSYNDR Meaning Is the data piece that encountered the above-mentioned error. 0 24 25 0 Bit no.
4 Item MHPMCLG ERROR LOG INFORMATION Description 0 0 10 11 12 13 14 15 16 17 20 21 22 23 24 25 28 29 30 31 0 ECC_2BIT HPMC_CHK CLK_CHK MLT ECC_2BIT_LG HPMC_CHK_LG CLK_CHK_LG BU_ERROR MU_ERROR Reserve PU_ERROR BRST_ACS MLT_LG Bit no. 0 to 10 11 Bit name － BU_ ERROR Read-in value Always 0. 0: Not any I/O. 1: I/O. 12 MU_ ERROR － NU_ ERROR Always 0. Always 0. 0: Not CMU. 1: CMU. 15 BRST_ ACS 0: Not burst. 1: Burst. 16 MLT_LG 0: Not a log. 1: A log.
4 ERROR LOG INFORMATION Item MLPMCLG Description 0 10 0 0 11 12 13 14 15 BRST_ACS PU_ERROR Reserve MU_ERROR BU_ERROR 16 17 18 19 20 21 22 23 24 25 26 27 28 29 MLT_LG Reserve RCNFG_LG CPY_PE_LG Reserve CPU_WR_ERR_LG WR_ECC2_LG ECC_1BIT_LG Bit no. 30 31 ECC_1BIT WR_BYT_ECC CPU_WR_ERR Reserve SRAM_WERR RCNFG Reserve MLT Bit name Read-in value Meaning 0 to 10 Reserve Always 0. － 11 BU_ ERROR 0: Not any I/O. 1: I/O.
4 Item ERROR LOG INFORMATION Description MLPMCLG (continued Bit no. from 24 Bit name MLT preceding Read-in value Meaning 0: Did not occur. Indicates whether or not multiple 1: Occurred. unserious errors of the same type page) occurred. 25 Reserve Always 0. － 26 RCNFG Always 0. (Reserved for functional enhancement) 27 SRAM_ 0: Request not Indicates whether or not a write failed WERR issued. due to an SRAM byte write request 1: Write failed. issued in SRAM ECC mode.
4 ERROR LOG INFORMATION Item MSW2 Description 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 VAL VBC IVRT MEME HWDT SWDT RAMS ROMS 16 Reserve Reserve Reserve Reserve Reserve OSCLR CLKSTP EXE 17 18 19 20 21 22 23 24 25 26 27 28 RAPE AAPE RDPE ADPE ATE TTE BBTE MSAW 29 30 31 Reserve Reserve Reserve BRTOE AERTR RERTR WPAW UDTW Bit no. 0 Bit name VAL Read-in value 0: Not significant. 1: Significant. 0: Battery normal. 1: Battery abnormal.
4 Item MSW2 (continued from preceding page) ERROR LOG INFORMATION Description Bit no. Bit name Read-in value Meaning 11 to 15 Reserve Always 0. － 16 RAPE 0: Error not detected. 1: Error detected. Indicates whether or not a receivedaddress parity error was detected (when the CMU was master). 17 AAPE 0: Error not detected. 1: Error detected. Indicates whether or not an assertedaddress parity error was detected (when the CMU was target). 18 RDPE 0: Error not detected. 1: Error detected.
4 ERROR LOG INFORMATION Item STATNP STATCP Description Unused 0 24 25 26 27 28 29 30 31 0 0 MWDPE RTA TRNSTO Bit no. Bit name BRQTO MA MRDPE MAPE Read-in value Meaning 0 to 24 － Always 0. － 25 MWDPE 0: Not received. Indicates whether or not, when the CMU 1: Received. was bus master, a write-data parity error was detected and an error notification was received from the target. 26 RTA 0: Not received. Indicates whether or not, when the CMU 1: Received.
4 Item STATSLV ERROR LOG INFORMATION Description 0 0 20 21 22 23 24 25 26 27 28 29 30 31 0 MAAE PIOME Reserve ACKBUSYTO RSERR Bit no. Bit name NODTACK ME TDPE TAPE STA INVCMD Read-in value Meaning 0 to 20 － Always 0. － 21 MAAE 0: Not detected. Indicates whether or not, when the target 1: Detected was in operation, an illegal byte-enable was detected in a write. 22 PIOME 0: Not detected.
4 ERROR LOG INFORMATION Item RERRLOG Description 0 12 13 0 14 15 0 NOACKTO Reserve MAAE 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ACK BUSYTO RSERR INVCMD STA TAPE TDPE ME NODTACK BRQTO MA MRDPE MAPE TRNSTO RTA MWDPE Reserve Bit no. 0 to 12 13 Bit name Reserve MAAE Read-in value Always 0. 0: Not detected. 1: Detected 14 15 Reserve NOACK TO Always 0. 0: Not detected. 1: Detected 16 17 ACK BUSYTO RSERR 18 INVCMD 0: Not detected. 1: Detected 0: Not received.
4 Item RERRLOG (continued from preceding page) Description Bit no. Bit name Read-in value Meaning 26 RTA 0: Not received. 1: Received. Indicates whether or not, when the CMU was bus master, an error transaction was received (and the bus operation was ended). 27 TRNSTO 0: Not detected. 1: Detected. Indicates whether or not, when the CMU was bus master, a transaction timeout was detected (and the bus operation was ended). 28 MAPE 0: Not received. 1: Received.
4 ERROR LOG INFORMATION Item RERRMST Description 0 18 19 20 0 0 23 24 25 26 27 28 29 30 31 0 0 CP SLOT7 SLOT6 SLOT5 Bit no. RERRCMD SLOT0 SLOT1 SLOT2 SLOT3 SLOT4 0 to 18 Bit name － Always 0. － 19 CP 0: Other than CMU. 1: CMU. 20 to 23 Reserve Always 0. Indicates whether or not the master that encountered the error was the CMU. － 24 SLOT7 0: Other than slot #7. 1: Slot #7. Indicates whether or not the master that encountered the error was the module mounted in slot #7.
4 Table 4-34 Set value of MST_TYPE The Set Values of MST_TYPE and MST_INFO Type of master Set value of MST_INFO 0x1 CMU 0x00000055: Denotes CMU master. 0xFFFFFFFF: Master unidentifiable. 0x2 I/O device under PCI bus 0x00000001: Denotes LANCE(CH1) master. 0x00000002: Denotes LANCE(CH2) master. 0xFFFFFFFF: Master unidentifiable. 0x3 I/O module under R700 (S10) bus Master slot number (8 for the CPU) Item PC ERROR LOG INFORMATION Description The content of the program counter.
4 ERROR LOG INFORMATION (14) System bus error This type of error is reported when a serious error is detected on the system bus. The table below shows the general format of error messages for system bus errors and describes each format element.
4 Item ERROR LOG INFORMATION Description MSW1 0 1 2 3 0 4 0 15 Module-specific information (LED) ERROR RUN 16 17 18 19 20 0 0 27 28 29 0 0 Module status 30 31 MASTER NINT MRDY RINT Bit no. Bit name Read-in value Meaning 0 Reserve Always 0. － 1 RUN 0: Not in RUN state. Is the module status. (The RUN LED is either lit or blinking.) 1: In RUN state. 2 ERROR 0: Error not detected. Is the error status. (The ERR LED is either lit or blinking.) 1: Error detected.
4 ERROR LOG INFORMATION Item MSW0 Description 0 27 28 29 30 31 0 Bit no. 0 Bit name BU_HER MU_HER EU_HER SU_HER Read-in value Meaning 0 to 26 － Always 0. － 27 Reserve Always 0. (Reserved for future extension) 28 BU_HER 0: Not generated. Indicates whether or not a serious-error 1: Generated. interrupt was generated in relation to the PCI bus. 29 EU_HER 0: Not generated. Indicates whether or not a serious-error 1: Generated.
4 Item STATCP Description 24 25 0 0 ENCP ERROR LOG INFORMATION 26 27 28 29 30 31 0 MWDPE RTA TRNSTO BRQTO MA MRDPE MAPE Meaning － Indicates whether or not, when the CMU was bus master, a write-data parity error was detected and an error notification was received from the target. Indicates whether or not, when the CMU was bus master, an error transaction was received (and the bus operation was ended).
4 ERROR LOG INFORMATION Item Description LOG 0 12 13 0 0 14 15 NOACKTO Reserve MAAE 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ACK BUSYTO BRQTO RSERR MRDPE INVCMD MAPE STA TRNSTO TAPE RTA TDPE MWDPE ME Reserve MA NODTACK Bit no. Bit name Read-in value Meaning 0 to 12 Reserve Always 0. － 13 MAAE 0: Not detected. 1: Detected Indicates whether or not, when the target was in operation, an illegal byte-enable was detected in a write.
4 Item LOG (continued from preceding page) ADR Description Bit no. Bit name Read-in value Meaning 25 MWDPE 0: Not received. 1: Received. Indicates whether or not, when the CMU was bus master, a write-data parity error notification was received from the target. 26 RTA 0: Not received. 1: Received. Indicates whether or not, when the CMU was bus master, an error transaction was received (and the bus operation was ended). 27 TRNSTO 0: Not detected. 1: Detected.
4 ERROR LOG INFORMATION Item MST Description 0 18 19 20 23 24 25 26 27 28 29 30 31 0 0 0 0 CP SLOT7 SLOT6 SLOT0 SLOT1 SLOT2 SLOT5 SLOT3 SLOT4 Bit no. CMD Bit name Read-in value Meaning 0 to 18 － Always 0. － 19 CP 0: Other than CMU. 1: CMU. Indicates whether or not the master that encountered the error was the CMU. 20 to 23 Reserve Always 0. － 24 SLOT7 0: Other than slot #7. 1: Slot #7.
4 Item MST ERROR LOG INFORMATION Description 0 20 21 22 23 24 25 26 27 28 29 30 31 0 0 0 0 MAAE NODTACK ACKBUSYTO ME RSERR TDPE INVCMD TAPE STA Bit no. Bit name Read-in value Meaning 0 to 20 － Always 0. 21 MAAE 0: Not detected. Indicates whether or not, when the 1: Detected target was in operation, an illegal byte-enable was detected in a write. 22 to 23 Reserve Always 0. 24 ACKBUSYTO 0: Not detected. Indicates whether or not a “BGACK 1: Detected.
4 ERROR LOG INFORMATION Item ENSLV Description 0 20 21 22 23 24 25 26 27 28 29 30 31 0 0 0 0 MAAE NODTACK ACKBUSYTO ME RSERR TDPE INVCMD TAPE STA Bit no. Bit name Read-in value Meaning 0 to 20 － Always 0. － 21 MAAE 0: Not reported. 1: Reported. Indicates whether or not a misalignment error was detected during target operation and reported as a serious error. (Related only to the CMU.) 22 to 23 Reserve Always 0. － 24 ACK BUSYTO 0: Not reported. 1: Reported.
4 Item ERROR LOG INFORMATION Description RBUSMNT 0 18 19 20 23 24 25 26 27 28 29 30 31 0 0 0 0 CP SLOT0 SLOT7 SLOT1 SLOT6 SLOT2 SLOT5 SLOT3 SLOT4 Bit no. Bit name Read-in value － Always 0. － 19 CP 0: Other than CMU. 1: CMU. Indicates whether or not the current master executing a bus transaction was the CMU. 20 to 23 Reserve Always 0. － 24 SLOT7 0: Other than slot #7. 1: Slot #7.
4 ERROR LOG INFORMATION (15) Other error This type of error is one that is output by the user. The ECs and their meanings for other errors are defined by the user.
4 ERROR LOG INFORMATION 4.4.4 Reading the DHP trace information DHP trace information is displayed in the following format: The DHP facility displays trace information in reverse chronological order. DHP trace information is classified into three categories of task, idle, and OS, based on DISPATCH_E events. For each DISPATCH_E event, DATA1 values in the range 0x00000001 to 0x0000012C are the task numbers of tasks executed.
TRACE_ON TRACE_OFF TRACE_TBU DHP display name DISPATCH_E RUNQ IDLE TASK_PRI 0x020083 0x020004 0x020005 0x020006 WAKEUP processing SLEEP event Before thread_invoke processing After thread_invoke processing RUNQ connection IDLE processing Priority level control Trace point - 336 - https://www.truck-manuals.
FREE PRSERV PFREE GFACT GTIME EXIT ASUSP ARSUM DHPCTL DHPREAD CHML CFREAD CFWRITE 0x10000f 0x100010 0x100011 0x100012 0x100013 0x100014 0x100015 0x100016 0x10001e 0x10001f 0x100023 0x100056 0x100057 Before or after the issuance of gfact macro gtime macro issued exit macro issued asusp macro issued arsum macro issued dhpctl macro issued dhpread macro issued chml macro issued Flash-memory read Flash-memory write pfree macro issued prserv macro issued free macro issued rserv macro issued Undefin
Trace point SENDTO RECV RECVFROM SETSOCKOPT SETSOCKOPT macro issued GETSOCKOPT macro GETSOCKOPT issued SHUTDOWN SHUTDOWN macro issued NET_END Macro abend NET_CTLR IOCTL macro issued Remote CPU control NET_CTLR accepted 0x300007 0x300008 0x300009 0x30000a NET_START NET_START NET_TERM NET_TERM NET_ATEN NET_ATEN NET_STO NET_SUB 0x300011 0x300012 0x300012 0x300013 0x300013 0x300014 0x300015 Built-in LANCE/LANCP transmission NCP-F termination interrupt Built-in LANCE/LANCE termination inter
0x600000 0x600001 0x600002 0x600003 0x600004 0x600005 0x600006 0x600007 Code value DHP display name USR0 USR1 USR2 USR3 USR4 USR5 USR6 USR7 User-specific processing 0x500028 0x500032 DHP display name WDTSET WRTMEM CPMS library processing Code value User-defined User-defined User-defined User-defined User-defined User-defined User-defined User-defined Trace point wdtset macro issued wrtmem macro issued Trace point DATA1 WDT monitoring time Transfer source address DATA1 DATA2 Transfer destinat
4 ERROR LOG INFORMATION 4.5 Maintenance Commands svelog -- output error log information.
4 ERROR LOG INFORMATION The display of the error log information can be controlled by using the following perusal commands: p, no input: Each displays the next page. -: Displays the previous page. n: Displays the information, starting from the n-th line from the beginning of the file. q: Exits the error log display process. • The svelog command can be used only when the user task is in RUN or STOP state.
4 ERROR LOG INFORMATION svdhp -- display DHP trace information.
4 ERROR LOG INFORMATION The following is an example program using dhpread: #include extern char dhp_g[4096]; main( ){ long size; size=4096; dhpread(dhp_g, &size); } The display of the DHP trace information can be controlled by using the following perusal commands: p, no input: Each displays the next page. -: Displays the previous page. n: Displays the information, starting from the n-th line from the beginning of the file. q: Exits the DHP display process.
4 ERROR LOG INFORMATION • When the -on or -off option is given, this command does not display any DHP trace information. The svdhp command returns one of the following exit codes at the end of its execution: 0: Normal termination made. 1: Parameter error detected. 2: Communication error detected. 3: Signal received. - 344 - https://www.truck-manuals.
4 ERROR LOG INFORMATION svcpunow -- display the CMU’s load ratio.
4 ERROR LOG INFORMATION svtimex -- display task utilization information.
4 ERROR LOG INFORMATION
THIS PAGE INTENTIONALLY LEFT BLANK. https://www.truck-manuals.
5 APPENDIX https://www.truck-manuals.
5 APPENDIX 5.1 Tool Error Messages 5.1.1 Error messages from the LADDER CHART SYSTEM Error message Required action Specify the key code that is not multidefined. Use a non-duplicated key code. This key code cannot be used. Use numeric or Use the correct key code. alphabet. Cannnot loaded this library. Restart the LADDER CHART SYSTEM and try it again. If the same error recurs, reinstall the LADDER CHART SYSTEM. Input number. Enter a numeric value. Not compiled after changed.
5 Error message APPENDIX Required action It failed in time read-out (timeout error). Reinstall the LADDER CHART SYSTEM. Time information is unfixed. Set a time value by using the BASE SYSTEM. The number of label registration exceeded Check the registered labels. maximum. N coil number is outside the range. Use the correct N-coil number. A label name overlaps within same N coil. Use a non-duplicated label name. The timeout occurred during ladder program Check the connection with the PCs.
5 APPENDIX Error message Required action It failed in check sum setup. Check the connection with the PCs. It failed in the setup of transmitting time. It failed in time read-out (timeout error). Cannot find system file Check the specified file. Type of PCs disagrees Specify a file provided for use with the S10V controller. Number of PCs disagrees Check the PCs number. Capacity of disc is insufficient. Terminate some of the active application programs and try it again.
5 Error message APPENDIX Required action Setting value of timer is illegal. Enter the timer value again. Setting value of one shot is illegal. Enter the one-shot timer value again. Setting value of counter is illegal. Enter the counter value again. Parameter is irregular in operation function. Specify the correct parameter. Number of parameters over limit in operation Specify only as many parameters as permitted. function. PI/O address error in operation function.
5 APPENDIX Error message Required action Function type "C", "K", "N" cannot be applied to Specify only a permitted register for the coil. coil. Function type "CU", "CD", "CR", "NM", "NZ" Specify only a permitted register for the a- or b-contact. cannot be applied to connecting point A or B. Function type "V", "LV" cannot be used except to Use a register other than the V- and LV-registers. rising edge contact or falling edge contact.
5 Error message APPENDIX Required action Cannot read sequence program. The ladder chart may have been destroyed. End the ladder Cannot read SQET. chart without saving, and read it in again. Then, if the same error recurs, create the ladder chart again. Cannot read setup value of timer. Cannot read setup value of one shot. Cannot read setup value of counter. Information about SQET is not created. Error in multiple output of coils. Specify a coil not in use.
5 APPENDIX Error message Required action Step cannot be deleted. Delete a step at any of the boxes in lines 1 through 11. Relay symbol on the last line is irregular. Set a wraparound mark at the end of the line. Comment file open error. Specify a comment file that can be opened. Comment file read error. This error is a system error in the personal computer. Restart the personal computer. Comment file write error.
5 Error message APPENDIX Required action Replacement processing cannot be executed Specify, for the coil and contact, symbols allowing symbol name between two cases of specified data in coil and replacement. contact. Replacement cannot be executed because data with Specify, for data under a new name, a symbol that is not used for a new name is already used in coil. any coil.
5 APPENDIX Error message Required action There is no work register. Change the duplicated edge-contact symbol to a non-duplicated one. Unregistered label name. Additionally register the label, or specify an already registered label name. The setting of label is irregular. Specify the label of a specifiable place. Error in redundant address of function type "LV". Specify an LV-register whose number is not used. Cannot open command file. Specify a comment file that can be opened.
5 APPENDIX 5.1.2 Error messages from the HI-FLOW SYSTEM Error message Required action Setup for starting process and termination process A larger number than the ending process number was given as are not correct the starting process number in the range-of-processes specification for process deletion. Supply the correct range specification. PCs is under down status now Restart the PCs and try it again. HI-FLOW system doesn't exist in PCs. Load the HI-FLOW SYSTEM into the PCs.
5 APPENDIX Error message Required action Same condition is setting being completed in timer Correct the specified timer-monitoring information. monitor information in PCs. Setting number of timer monitor information Check the specified timer-monitoring information. exceeds a limit. Timer monitor Information Systems specified Correct the specified timer-monitoring information. doesn't exist in PCs top. Trace condition specified is established already. Correct the specified trace condition.
5 Error message Several of symbol in 1 sentence exceed a limit. APPENDIX Required action Reduce the number of symbols used in the sentence. (Cross-reference table overflow). The output disk volume of object isn't enough. A storage shortage occurred on the PC’s hard disk. Delete unnecessary files and try it again. A character number of symbol exceeds a limit. Reduce the number of characters used in the symbol. It is jump symbol error. Check the jump symbol and solve the problem. It is label error.
5 APPENDIX 5.1.3 Error messages from the BASE SYSTEM Error message Required action Cannot reset PCs. Check the connection with the PCs and try it again. LPU is running. After stopping, clear a battery Stop the LPU and then clear the data in the backup memory. backup memory. A malfunction was detected while the battery Check the connection with the PCs and try it again. backup memory is clear. There is possibility that a battery backup memory isn't cleared. Cannot save memory dump.
5 APPENDIX 5.1.4 Error messages from the FL.NET SYSTEM Error message Required action No option module is mounted. Check if the FL.NET module is installed properly. Now computing. Please try again later. The FL.NET module was unable to write the specified values in place because it was busy. Wait for a while and try it again. Timeout error The write to the PCs failed. Check the connection settings to connect with the PCs. Please Reset or Power OFF/ON PCs.
5 APPENDIX 5.1.6 Error messages from the ET.NET SYSTEM Error message Required action The S10V BASE SYSTEM was not installed. The S10V BASE SYSTEM may not have been installed or may Please install it, first. have been destroyed. Install the S10V BASE SYSTEM again. No option module is mounted. Check if the FL.NET module is installed properly. Line error An attempt to communicate with the PCs failed. Check the connection with the PCs. IP address is outside the range.
5 APPENDIX 5.1.7 Error messages from the J.NET SYSTEM Error message Required action No option module is mounted. Check if the J.NET or J.NET-INT module is installed properly. The form of J.NET module is unknown. The J.NET or J.NET-INT module may be in a failure condition. Replace the module. Enter an address. Although the check box to indicate “addresses not used” is deselected, no addresses were entered. Enter address values for the NET1 and NET2 status table addresses.
5 APPENDIX 5.1.8 Error messages from the IR.LINK SYSTEM Error message Required action No option module is mounted. Check if the IR.LINK module is installed properly. Enter the refresh cycle time. Enter an I/O refresh cycle value selected from among the values The refresh cycle time is out of range (1.5, 2, 2.5, 1.5, 2, 2.5, and 3 through 3000. 3-3000). The status table address is out of range. An invalid address was detected. Set a valid address value.
5 APPENDIX 5.1.9 Error messages from the CPU LINK SYSTEM Error message Please enter an integer between xxx and xxx. Required action Enter hexadecimal numbers in the range shown in the error message into the inter-CPU link and inter-sub-CPU link send areas. 5.1.10 Error messages from the EXTERNAL SERIAL LINK SYSTEM Error message Required action No option module is mounted. Check if the RS-232C or RS-422 module is installed properly. The address is out of bounds.
5 APPENDIX 5.1.11 Error messages from the D.NET SYSTEM Error message Required action No option module is mounted. Check if the D.NET module is installed properly. The refresh time is out of range (3ms-1000ms) The input value was out of the permitted range. Set the correct value. Since PCs is occupied, it cannot set up. An attempt was made to write setting information from more than one place simultaneously. Do not write it simultaneously. Please Reset or Power OFF/ON PCs.
5 Error message Slave timeout detection register is duplicated. APPENDIX Required action In the system parameter setting window, the address of the slave timeout detection register is duplicated with the specified input address, output address, or information storage address. Specify a non-duplicated address. The port to reserve has exceeded under use or the Port reservation failed. Specify the number of input or output last port.
5 APPENDIX 5.1.12 Error messages from the EQ.LINK SYSTEM Error message Required action No option module is mounted. Check if the EQ.LINK module is installed properly. Now computing. Please try again later. The EQ.LINK module was unable to write the specified values in place because it was busy. Wait for a while and try it again. Timeout error The write to the PCs failed. Check the connection settings to connect with the PCs. Please Reset or Power OFF/ON PCs.
5 5.1.13 APPENDIX Error messages from the BACKUP RESTORE SYSTEM Error message Required action Disc is full. Insert new disc. Replace the storage media piece in the drive. Disc is full. Increase the available storage space on the hard disk. Cannot write to disc. Confirm if disc is not full or Increase the available storage space on the hard disk. write protect switch is not set. File is not found. Check if the file and path to it were specified correctly.
5 APPENDIX 5.1.14 Error messages from the NX/Tools-S10V SYSTEM Error message Required action A file to transfer is not chosen. Choose the file to be transferred. A specified file is not the setup information file of Check the specified file. NX. A setup can not be done any further because it The maximum number of TCD information cases that can be exceeds the number which TCD information can be registered is 96. established to. A wrong point was detected during the file access.
5 Error message APPENDIX Required action Alive message timeout is out of range. Set a alive Specify an “alive” message timeout period in the range 1 to message timeout between 1 and 43200. 43200. Alive message interval is not found. Set a Alive Set an “alive” message transmission interval and try it again. message interval. Alive message interval is out of range. Set a alive Specify an “alive” message transmission interval in the range 1 message interval between 1 and 3600. to 3600.
5 APPENDIX Error message Required action Receive port No. is not found. Set a receive port Define the receive port number and try it again. No. Receive port No. is out of range. Set a receive port Specify a receive port number in the range 1 to 65535. No. between 1 and 65535. Receive MCG No. is multiple defined. Set a Specify a unique receive port number. unique number. Port number is multiple defined. Set a unique Specify a unique port number. number. MCG number is multiple defined.
5 Error message APPENDIX Required action Transmitting area overlaps. Check the send area and solve the problem. Send address is inaccurate. Correct the send address. Receive completion register is not found. Set a Set a receive completion register name and try it again. receive completion register. Receive completion register is multiple defined. Specify a unique receive completion register. Set a unique number. Receive completion register is inaccurate. Check the receive completion register.
5 APPENDIX 5.1.15 Error messages from the tools Error message Required action Failed in initialization of OLE. Confirm if the No such OLE library is existent or, if it is existent, its version is OLE library is right version or not. old. Install the latest version of the OLE library. Line error The communication line’s connections or settings may be incomplete, or the PCs may not be up and running.
5 5.2 APPENDIX Trouble Report Fill out this form and submit it to local source. Your company name Person in charge （year / month / day / hour / minute） Data and time of occurrence Address Where to make contact Telephone FAX E-mail Model of defective module OS Ver. LPU model Rev. Support program Program name: Ver. Rev. Program name: Ver. Rev. Symptom of defect Type Model Wiring state Connection load System configuration and switch setting Space for correspondence - 377 - https://www.
