[vip专享]IMM error messages

合集下载

critical error message version -回复

critical error message version -回复错误消息（critical error message）是计算机系统在出现严重错误或故障时向用户报告的通知。

它通常以红色字体显示，突出显示重要信息，以吸引用户的注意。

这些错误消息可以是软件、操作系统、网络连接或硬件设备等多个方面引起的。

本文将逐步解释错误消息的含义、常见的错误消息类型以及如何处理这些错误。

首先，我们来解释错误消息的含义。

在计算机系统中，错误消息是系统向用户提供的一种有用的反馈机制。

它通常描述了出现错误的具体原因和可能的解决方法。

错误消息的主要目的是帮助用户理解问题，并采取必要的措施来修复错误。

然而，由于错误消息通常是技术性的，它们可能对普通用户来说并不清晰明了。

因此，正确理解错误消息是解决问题的第一步。

接下来，我们将讨论一些常见的错误消息类型。

其中一个常见的错误消息是“系统错误”，它通常出现在操作系统崩溃或系统组件损坏时。

这种错误消息可能提醒用户重新启动计算机或重新安装操作系统等解决方案。

另一个常见的错误消息是“应用程序错误”，它显示在软件程序执行过程中发生错误时。

这种错误消息通常会提醒用户程序崩溃或发生内部错误，并建议用户重试或联系技术支持。

其他常见的错误消息包括网络连接错误、数据库错误、设备错误等。

为了更好地处理错误消息，我们应该采取以下步骤：步骤一：阅读错误消息。

当我们遇到错误消息时，第一步是仔细阅读并理解错误消息的内容。

错误消息通常提供了有用的信息，例如错误代码、错误描述和可能的解决方法。

仔细阅读错误消息可以帮助我们更好地了解问题。

步骤二：查找错误的根本原因。

一旦我们理解了错误消息的内容，我们应该尝试找出错误的真正原因。

这可能需要进一步的调查和排除步骤。

例如，如果错误消息是由于网络连接错误引起的，我们可以检查网络连接设置、重启路由器或联系网络服务提供商等。

步骤三：尝试解决问题。

一旦我们确定了错误的根本原因，我们可以尝试采取适当的措施来解决问题。

criticalerrormessage

criticalerrormessageCritical Error MessageWhen using digital devices, encountering a critical error message is something that can cause frustration and panic. These messages often appear unexpectedly, disrupting our work or leisure activities. Understanding what a critical error message is and how to handle it can help alleviate the stress and confusion it may bring.A critical error message is a notification that alerts users to a severe problem or failure within a system or application. It indicates that the system or program cannot continue executing its tasks and may require immediate attention to prevent further damage or data loss. These messages can vary in severity, ranging from minor issues that can be easily resolved to major problems that may require professional assistance.One common example of a critical error message is the infamous "Blue Screen of Death" (BSOD) encountered by Windows users. This error message indicates a system crash, often caused by hardware or software issues. When a BSOD occurs, the system will display a blue screen with errorcodes and instructions for troubleshooting.Another example is the "Fatal Error" message, which can occur in various applications or operating systems. This message typically indicates a severe problem that prevents the program from functioning correctly. It may include error codes, error descriptions, and suggestions for resolving the issue.When confronted with a critical error message, it is essential to remain calm and take appropriate action. Here are some steps to follow:1. Read and Understand the Message: Carefully read the error message and try to comprehend its meaning. Look for any specific error codes or descriptions that can provide clues about the issue at hand.2. Restart the Device or Program: In many cases, a simple restart can resolve minor software glitches or temporary system issues. Close the application or restart the device and see if the error message persists.3. Search for Solutions: If the error message includes an error code or description, consider searching online forsolutions. Many forums and support websites provide step-by-step instructions for troubleshooting common errors.4. Update Software and Drivers: Outdated software or incompatible drivers can often cause critical errors. Check for any available updates for both the operating system and the application in question. Installing the latest patches and updates may resolve the issue.5. Disable Recently Installed Software: If the error message started appearing after installing new software or updates, it is worth considering that the newly added program may be the cause. Uninstall or disable the software temporarily and check if the error message persists.6. Seek Professional Help: If the error message continues to appear or if it indicates a severe hardware problem, it is advisable to seek professional assistance. Contacting customer support or consulting a technician can help diagnose and resolve complex issues.It is important to note that critical error messages should not be ignored or dismissed. They often indicate underlying problems that, if left unaddressed, can lead to furthercomplications. It is always preferable to fix the issue promptly to prevent any potential data loss or system instability.In conclusion, encountering a critical error message can be a frustrating experience, but it is essential to approach it calmly and methodically. By understanding the nature of the error message, following appropriate steps for troubleshooting, and seeking professional help when necessary, users can effectively resolve issues and minimize disruptions caused by critical errors. Remember, a critical error message is not the end of the world; it is an opportunity to identify and rectify problems within our digital systems.。

critical error message version -回复

critical error message version -回复题目：[critical error message version]正文：引言：在现代社会中，无论是个人还是企业，我们几乎每天都会遇到各种各样的错误提示信息。

这些错误提示信息以简短的文字描述或代码为形式，提醒我们发生了一些问题或错误。

然而，在人们生活和工作中，最为关键的错误提示信息往往更加引起人们的关注和重视。

本文将以“[critical error message version]”为主题，深入讨论这样一种严重错误提示信息的出现、影响以及解决方法。

一、错误提示信息出现的原因及情景1. 硬件故障：错误提示信息显示硬件故障的情况是最常见的。

例如，计算机突然黑屏并出现“硬盘错误”的提示信息，这可能是硬盘损坏或连接故障导致。

2. 软件错误：软件在运行过程中出现问题可能导致关键错误提示信息的出现。

有时，软件开发中的错误或缺陷会导致崩溃或不正常操作，并触发错误提示信息。

3. 网络连接问题：在现代社会中，网络连接是必不可少的。

当网络连接出现问题时，计算机显示网络错误提示信息。

例如，“无法连接到互联网”或“服务器故障”。

4. 安全问题：为了保护个人隐私和信息安全，系统会显示与安全相关的错误提示信息。

例如，“非法登录尝试”或“病毒检测到”。

二、严重错误提示信息的影响1. 用户体验下降：对于个人用户或公司员工来说，严重错误提示信息会导致用户体验大大降低。

特别是对于那些不懂技术或不了解错误信息含义的人来说，可能会陷入困惑、无助和沮丧的境地。

2. 生产力受损：某些严重错误提示信息会导致系统崩溃或无法正常工作，进而影响个人或企业的工作效率和生产力。

在商业环境中，每分钟的停机时间都可能造成巨大的经济损失。

3. 数据丢失和风险：某些严重错误提示信息可能会导致数据丢失或损坏，从而给个人或企业带来重大风险。

例如，硬盘故障导致的数据无法恢复，或者安全漏洞导致敏感信息被黑客窃取。

unserialize newest msg error -回复

unserialize newest msg error -回复"Unserialize newest msg error" is an error message related to the process of unserializing the latest message. Unserialization is the process of converting a serialized form of data back into its original state. This error occurs when there is an issue with the unserialization process, preventing the successful retrieval of the newest message. In this article, we will explore the reasons behind this error and provide step-by-step solutions to resolve it.1. Introduction to Serialization and Unserialization: Serialization is the process of converting complex data structures into a format that can be easily stored or transmitted. Unserialization, on the other hand, is the reverse process that converts serialized data back into its original data structure.2. Causes for "Unserialize newest msg error":There can be several reasons for encountering the "unserialize newest msg error." Below are some common causes:a. Incomplete or corrupted serialization data: If the data received for unserialization is incomplete or corrupted, it can lead to this error. It may happen due to transmission errors, data corruptionduring storage, or improper handling of serialized data.b. Incompatible serialization formats: If the data was serialized using a different serialization format or version that is not compatible with the unserialization process, the error can occur.c. Change in data structure: If the data structure of the serialized data has changed since it was serialized, the unserialization process may fail, resulting in the error.3. Step-by-step solutions to resolve the error:Step 1: Check the serialization process:Begin by verifying that the serialization process is correctly implemented. Ensure that the data is serialized properly and that no errors occur during serialization. Double-check for any changes made to the serialization process since the data was serialized.Step 2: Validate the serialized data:Validate the serialized data to ensure its integrity and completeness. If the data is corrupted or incomplete, it will result in the "unserialize newest msg error." Compare the serialized data withthe original data to identify any discrepancies or missing parts.Step 3: Verify compatibility between serialization formats: Ensure that the serialization and unserialization processes use the same format and version. If the data was serialized using a different format or version, convert the serialized data to the correct format before proceeding with the unserialization process.Step 4: Check for changes in data structure:Compare the original data structure with the serialized data structure. If there are any differences, modify the unserialization process to accommodate these changes. Update the code to handle these changes appropriately.Step 5: Debug the unserialization process:If the error persists after following the previous steps, debug the unserialization process. Print relevant variables, step through the code, and analyze the error messages. This will help identify the specific line or section of code causing the error. From there, make the necessary modifications to fix the issue.Step 6: Implement error handling:Implement proper error handling mechanisms to handle any future errors during the unserialization process. This includes usingtry-catch blocks and logging error messages to aid in debugging and resolving similar errors quickly.4. Conclusion:The "unserialize newest msg error" occurs when there are issues with unserialization, preventing the successful retrieval of the newest message. This article presented an overview of serialization and unserialization, identified common causes for the error, and provided step-by-step solutions to resolve it. By following these steps, developers can address the error and ensure a smooth unserialization process.。

3GPP TS 31.111 V8.4.0

3GPP TS 31.111 V8.4.0 (2009-01)Technical Specification3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Universal Subscriber Identity Module (USIM)Application Toolkit (USAT)(Release 8)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM ) and may be further elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.KeywordsUMTS, SIM, Card, LTE3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2009, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational PartnersContents Foreword (9)1Scope (10)2References (10)3Definitions, abbreviations and symbols (12)3.1Definitions (12)3.2Abbreviations (12)3.3Symbols (12)4Overview of USAT (12)4.1Profile Download (12)4.2Proactive UICC (13)4.3Data download to UICC (13)4.4Menu selection (13)4.5Call control by USIM (13)4.6MO Short Message control by USIM (13)4.7Event download (13)4.8Security (13)4.9Multiple card (13)4.10Timer Expiration (13)4.11Bearer Independent Protocol (13)4.12Description of the access technology indicator mechanism (14)4.13Description of the network search mode mechanism (14)4.14Geographical location discovery (14)5Profile download (14)5.1Procedure (14)5.2Structure and coding of TERMINAL PROFILE (14)5.3Definition of display parameters in Profile download (18)6Proactive UICC (18)6.1Introduction (18)6.2Identification of ME support (18)6.3General procedure (18)6.4Proactive UICC commands and procedures (18)6.4.1DISPLAY TEXT (18)6.4.2GET INKEY (18)6.4.3GET INPUT (19)6.4.4MORE TIME (19)6.4.5PLAY TONE (19)6.4.6POLL INTERVAL (19)6.4.7REFRESH (19)6.4.7.1EF IMSI changing procedure (19)6.4.7.2Generic Bootstrapping Procedure Request (19)6.4.8SET UP MENU (20)6.4.9SELECT ITEM (20)6.4.10SEND SHORT MESSAGE (20)6.4.11SEND SS (20)6.4.12SEND USSD (21)6.4.12.1MMI Mode (21)6.4.12.2Application Mode (22)6.4.13SET UP CALL (23)6.4.14POLLING OFF (23)6.4.15PROVIDE LOCAL INFORMATION (23)6.4.16SET UP EVENT LIST (25)6.4.17PERFORM CARD APDU (25)6.4.18POWER OFF CARD (25)6.4.23RUN AT COMMAND (25)6.4.24SEND DTMF (25)6.4.25LANGUAGE NOTIFICATION (25)6.4.26LAUNCH BROWSER (26)6.4.27OPEN CHANNEL (26)6.4.27.1OPEN CHANNEL related to CS bearer (26)6.4.27.2OPEN CHANNEL related to GPRS/3G packet service (26)6.4.27.3OPEN CHANNEL related to local bearer (26)6.4.27.4OPEN CHANNEL related to Default (network) Bearer (27)6.4.27.5OPEN CHANNEL related to I-WLAN bearer (27)6.4.27.6OPEN CHANNEL related to Terminal Server Mode (28)6.4.28CLOSE CHANNEL (28)6.4.29RECEIVE DATA (28)6.4.30SEND DATA (28)6.4.31GET CHANNEL STATUS (28)6.4.32SERVICE SEARCH (28)6.4.33GET SERVICE INFORMATION (28)6.4.34DECLARE SERVICE (28)6.4.35RETRIEVE MULTIMEDIA MESSAGE (28)6.4.36SUBMIT MULTIMEDIA MESSAGE (28)6.4.37DISPLAY MULTIMEDIA MESSAGE (28)6.4.38SET FRAMES (29)6.4.39GET FRAME STATUS (29)6.4.40Geographical Location Request (29)6.5Common elements in proactive UICC commands (30)6.6Structure of proactive UICC commands (30)6.6.1DISPLAY TEXT (30)6.6.2GET INKEY (30)6.6.3GET INPUT (30)6.6.4MORE TIME (30)6.6.5PLAY TONE (30)6.6.6POLL INTERVAL (30)6.6.7SET-UP MENU (30)6.6.8SELECT ITEM (30)6.6.9SEND SHORT MESSAGE (30)6.6.10SEND SS (31)6.6.11SEND USSD (31)6.6.12SET UP CALL (31)6.6.13REFRESH (31)6.6.14POLLING OFF (31)6.6.15PROVIDE LOCAL INFORMATION (32)6.6.16SET UP EVENT LIST (32)6.6.17PERFORM CARD APDU (32)6.6.18POWER OFF CARD (32)6.6.19POWER ON CARD (32)6.6.20GET READER STATUS (32)6.6.21TIMER MANAGEMENT (32)6.6.22SET UP IDLE MODE TEXT (32)6.6.23RUN AT COMMAND (32)6.6.24SEND DTMF COMMAND (32)6.6.25LANGUAGE NOTIFICATION (32)6.6.26LAUNCH BROWSER (32)6.6.27OPEN CHANNEL (33)6.6.27.1OPEN CHANNEL related to I-WLAN Bearer (33)6.6.28CLOSE CHANNEL (33)6.6.29RECEIVE DATA (33)6.6.30SEND DATA (33)6.6.31GET CHANNEL STATUS (33)6.6.36SUBMIT MULTIMEDIA MESSAGE (34)6.6.37DISPLAY MULTIMEDIA MESSAGE (34)6.6.38SET FRAMES (34)6.6.39GET FRAMES STATUS (34)6.6.40Geographical Location Request (34)6.7Command results (34)6.8Structure of TERMINAL RESPONSE (35)6.8.1Command details (36)6.8.2Device identities (36)6.8.3Result (36)6.8.4Duration (37)6.8.5Text string (37)6.8.6Item identifier (37)6.8.7Local information (37)6.8.8Call control requested action (37)6.8.9Result data object 2 (37)6.8.10Card reader status (37)6.8.11Card ATR (37)6.8.12R-APDU (37)6.8.13Timer identifier (37)6.8.14Timer value (37)6.8.15AT Response (38)6.8.16Text string 2 (38)6.8.17Channel data (38)6.8.18Channel status (38)6.8.19Channel data length (38)6.8.20Bearer description (38)6.8.21Buffer size (38)6.8.22Total Display Duration (38)6.8.23Service Availability (38)6.8.24Service Record (38)6.9Proactive UICC session and ME display interaction (38)6.10Handling of unknown, unforeseen and erroneous messages (38)6.11Proactive commands versus possible Terminal response (38)7ENVELOPE Commands (39)7.1Data download to UICC (39)7.1.1SMS-PP data download (39)7.1.1.1Procedure (39)7.1.1.2Structure of ENVELOPE (SMS-PP DOWNLOAD) (40)7.1.2Cell Broadcast data download (41)7.1.2.1Procedure (41)7.1.2.2Structure of ENVELOPE (CELL BROADCAST DOWNLOAD) (42)7.2Menu Selection (42)7.3Call Control and MO SMS control by USIM (42)7.3.1Call Control by USIM (42)7.3.1.1Procedure for mobile originated calls (42)7.3.1.2Procedure for Supplementary Services and USSD (43)7.3.1.3Indication to be given to the user (44)7.3.1.4Interaction with Fixed Dialling Number (45)7.3.1.5Support of Barred Dialling Number (BDN) service (45)7.3.1.6Structure of ENVELOPE (CALL CONTROL) (45)7.3.1.7Procedure for PDP Context Activation (47)7.3.2MO Short Message Control by USIM (48)7.3.2.1Description (48)7.3.2.2Structure of ENVELOPE (MO SHORT MESSAGE CONTROL) (48)7.3.2.3Indication to be given to the user (49)7.3.2.4Interaction with Fixed Dialling Number (49)7.4Timer Expiration (49)7.5.1.2Structure of ENVELOPE (EVENT DOWNLOAD – I-WLAN Access Status) (50)7.5.2Network Rejection event (51)7.5.2.1Procedure (51)7.5.2.2 Structure of ENVELOPE (EVENT DOWNLOAD – Network Rejection) (51)7.6USSD Data Download (52)7.6.1Procedure (52)7.6.2Structure of ENVELOPE (USSD Data Download) (52)7.7MMS Transfer Status (53)7.8MMS notification download (53)7.9Terminal Applications (53)7.10Geographical Location Reporting (53)7.10.1Procedure (53)7.10.2Structure of ENVELOPE (Geographical Location Reporting) (53)8COMPREHENSION-TLV data objects (54)8.1Address (54)8.2Alpha identifier (54)8.3Subaddress (54)8.4Capability configuration parameters (54)8.5Cell Broadcast Page (54)8.6Command details (54)8.7Device identities (55)8.8Duration (55)8.9Item (55)8.10Item identifier (55)8.11Response length (55)8.12Result (55)8.12.1Additional information for SEND SS (56)8.12.2Additional information for ME problem (56)8.12.3Additional information for network problem (56)8.12.4Additional information for SS problem (56)8.12.5Additional information for SMS problem (56)8.12.6Not used (57)8.12.7Additional information for USSD problem (57)8.12.8Additional information for interaction with call control or MO SM control (57)8.13SMS TPDU (57)8.14SS string (57)8.15Text string (58)8.16Tone (58)8.17USSD string (58)8.18File List (58)8.19Location Information (58)8.20IMEI (59)8.21Help Request (59)8.22Network Measurement Results (59)8.23Default Text (59)8.24Items Next Action Indicator (59)8.25Event list (59)8.26Cause (60)8.27Location status (60)8.28Transaction identifier (60)8.29BCCH channel list (60)8.30Call control requested action (61)8.31Icon Identifier (61)8.32Item Icon Identifier list (61)8.33Card reader status (61)8.34Card ATR (61)8.35C-APDU (61)8.36R-APDU (62)8.40AT Command (62)8.41AT Response (62)8.42BC Repeat indicator (62)8.43Immediate response (63)8.44DTMF string (63)8.45Language (63)8.46Timing Advance (63)8.47Browser Identity (63)8.48URL (63)8.49Bearer (63)8.50Provisioning File Reference (64)8.51Browser Termination Cause (64)8.52Bearer description (64)8.52.1Bearer parameters for CSD (64)8.52.2Bearer parameters for GPRS/3G Packet Service (64)8.52.3Bearer parameters for UTRAN Packet Service with extended parameters / HSDPA (65)8.52.4 Bearer parameters for I-WLAN (66)8.53Channel data (66)8.54Channel data length (66)8.55Buffer size (66)8.56Channel status (66)8.57Card reader identifier (66)8.58Other Address (66)8.59UICC/ME interface transport level (67)8.60AID (67)8.61Network Access Name (67)8.62Access Technology (67)8.63Display parameters (67)8.64Service Record (67)8.65Device Filter (67)8.66Service Search (67)8.67Attribute Information (67)8.68Service Availability (67)8.69Remote Entity Address (67)8.70Text Attribute (67)8.71Item Text Attribute List (68)8.72PDP context Activation parameters (68)8.73UTRAN Measurement Qualifier (68)8.74Multimedia Message Reference (68)8.75Multimedia Message Identifier (68)8.76Multimedia Message Transfer status (68)8.77MM Content Identifier (68)8.78Multimedia Message Notification (68)8.79Last Envelope (69)8.80Frames Layout (69)8.81Frames Information (69)8.82Frames identifier (69)8.83I-WLAN Identifier (69)8.84I-WLAN Access Status (69)8.85IMEISV (69)8.86Network search mode (69)8.87Battery State (69)8.88Browsing status (69)8.89Registry application data (70)8.90PLMNwAcT List (70)8.91Routing Area Identification (70)8.92Update/Attach Type (70)8.93Rejection Cause Code (71)8.96NMEA sentence (74)8.97PLMN List (74)9Tag values (74)9.1BER-TLV tags in ME to UICC direction (74)9.2BER-TLV tags in UICC TO ME direction (75)9.3COMPREHENSION-TLV tags in both directions (75)Type of Command and Next Action Indicator (75)I Allowed Type of command and Device identity combinations (75)11Security requirements (76)Annex A (normative): Support of USAT by Mobile Equipment (77)Annex B (informative): Example of DISPLAY TEXT Proactive UICC Command (78)Annex C (normative): Structure of USAT communications (79)Annex D (informative): ME display in proactive UICC session (80)Annex E (informative): Help information feature processing (81)Annex F (informative): Monitoring of events (82)Annex G (normative): Support of Multiple Card Operation (83)Annex H (informative): Multiple Card proactive command examples (84)Annex I (informative): Bearer independent protocol proactive command examples (85)Annex J (informative): WAP References (86)Annex K (informative): Use of USAT Bearer independent protocol for local links Bluetooth case (87)Annex L (informative): Bluetooth Service Discovery protocol (88)Annex M (informative): Use of USAT Bearer independent protocol for local links, server case (89)Annex N (informative): USSD information flow between the Network, the ME and the UICC (90)N.1MMI Mode (90)N.2Application Mode (92)N.3USSD Data Download (94)Annex O (informative): Geographical location information discovery information flow betweenthe ME and the UICC (94)Annex P (informative): Change History (96)ForewordThis Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document defines the interface between the UICC and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "USIM Application Toolkit".The present document refers in its majority to the ETSI TS 102 223 [32], which describes the generic aspects of application toolkits within the UICC.USAT is a set of commands and procedures for use during the network operation phase of 3G, in addition to those defined in TS 31.101 [13].Specifying the interface is to ensure interoperability between a UICC and an ME independently of the respective manufacturers and operators.The present document defines for 3G technology:- the commands;- the application protocol;- the mandatory requirements on the UICC and ME for each procedure.The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the UICC or the ME are only specified where these reflect over the interface. The present document does not specify any of the security algorithms which may be used.Within the context of the present document, the term "terminal" used in ETSI TS 102 223 [32] refers to the Mobile Equipment (ME).Within the context of the present document, the term "NAA" used in ETSI TS 102 223 [32] refers to the USIM.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.•References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.•For a specific reference, subsequent revisions do not apply.•For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the sameRelease as the present document.[1] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network(PLMN)".[2] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)".[3] 3GPP TS 22.042: "Network Identity and Time Zone (NITZ); Service description; Stage 1".[4] 3GPP TS 23.038: "Alphabets and language-specific information".[5] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".[6] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".[7] 3GPP TS 23.122: "Non-Access Stratum functions related to Mobile Station (MS) in idle mode".[8] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".[9] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".[10] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radiointerface".[11] 3GPP TS 24.080: "Mobile radio layer 3 supplementary services specification; Formats andcoding".[12] 3GPP TS 27.007: "AT command set for 3G User Equipment (UE)".[13] 3GPP TS 31.101: "UICC-terminal interface; Physical and logical characteristics".[14] 3GPP TS 31.102: "Characteristics of the USIM application".[15] Void.[16] Void.[17] Void.[18] Void.[19] Void.[20] Void.[21] Void.[22] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public LandMobile Network (PLMN)".[23] 3GPP TS 23.048: "Security Mechanisms for the (U)SIM application toolkit; Stage 2".[24] Void.[25] Void.[26] Void.[27] 3GPP TS 44.018: "Mobile radio interface Layer 3 specification; Radio Resource ControlProtocol".[28] Void.[29] Void.[30] 3GPP TS 23.003: "Numbering, addressing and identification".[31] Void.[32] ETSI TS 102 223 Release 7: "Smart Cards; Card Application Toolkit".[33] 3GPP TR 21.905: "Vocabulary for 3GPP specifications".[34] 3GPP TS 22.101: "Service aspects; Service principles".[35] 3GPP TS 25.401: "UTRAN overall description".[36] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".[37] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD) - Stage 3".[38] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification".[39] 3GPP TS 25.133: "Requirements for support of radio resource management".[40] Void.[41] 3GPP TS 31.115: "Secured packet structure for the (U)SIM Toolkit applications".[42] 3GPP TS 24.234: "3GPP System to WLAN Interworking; UE to Network protocols; Stage 3".[43] ETSI TS 101 220 Release 7: "Smart Cards; ETSI numbering system for telecommunicationapplication providers ".[44] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".[45] IEC 61162-1: "Maritime navigation and radio communication equipment and systems – Digitalinterfaces".3 Definitions, abbreviations and symbols3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in ETSI TS 102 223 [32] and TR 21.905 [33] apply.3.2 AbbreviationsFor the purpose of the present document, the abbreviations given in ETSI TS 102 223 [32] and TR 21.905 [33] and the following apply:ADN Abbreviated Dialling NumberBroadcastCB CellCBMID Cell Broadcast Message IDentifierEGPRS EDGE General Packet Radio ServiceNumberFDN FixedDiallingGGSN Gateway GPRS Support NodeGPRS General Packet Radio ServiceGSM Global System for Mobile communicationsHSDPA High Speed Downlink Packet AccessMM MultimediaMessageServiceMMS MultimediaMessagingInterfaceMachineMMI ManPDP Packet Data Protocol, e.g., Ip or X25 or PPPRFU Reserved for Future UseServiceSS SupplementarySSC Supplementary Service Control stringUSAT USIM Application ToolkitUSIM Universal Subscriber Identity ModuleSupplementary Service DataUSSD UnstructuredWSID WLAN Specific IDentifier3.3 SymbolsFor the purposes of the present document, the following symbols apply:'0' to '9' and 'A' to 'F' The sixteen hexadecimal digits.4 Overview of USATThe USAT provides mechanisms which allow applications, existing in the UICC, to interact and operate with any ME which supports the specific mechanism(s) required by the application.The following mechanisms have been defined. These mechanisms are dependent upon the commands and protocols relevant to USAT in TS 31.101 [13].4.1 ProfileDownloadProfile downloading provides a mechanism for the ME to tell the UICC what it is capable of.4.2 ProactiveUICCProactive UICC gives a mechanism whereby the UICC can initiate actions to be taken by the ME. In addition to the actions listed in ETSI TS 102 223 [32], the USAT is extended with the following actions:- sending a SS control or USSD string.- requesting the ME to report current geographical location information.4.3 Data download to UICCData downloading to the UICC uses either dedicated commands (the transport mechanisms of SMS point-to-point and Cell Broadcast) or the Bearer independent protocol. Transferral of information over the UICC-ME interface uses the ENVELOPE command.4.4 MenuselectionSee ETSI TS 102 223 [32].4.5 Call control by USIMWhen this service is activated by the USIM, all dialled digit strings, supplementary service control strings and USSD strings or PDP context parameters are first passed to a USIM application before the ME sets up the call, the supplementary service operation or the USSD operation or establishes the PDP context. The ME shall also pass to the USIM application at the same time its current serving cell. The USIM application has the ability to allow, bar or modify the call, the supplementary service operation or, the USSD operation or PDP context activation by another context activation. The USIM application also has the ability to replace a call request, a supplementary service operation or a USSD operation by another call request or supplementary service operation or USSD operation.EXAMPLE: A call request can be replaced by a supplementary service operation or a USSD operation, and vice-versa.4.6 MO Short Message control by USIMWhen this service is activated by the USIM, all MO short messages are first passed to the USIM application before the ME sends the short message. The ME shall also pass to the USIM application at the same time its current serving cell. The USIM application shall have the ability to allow the sending, bar the sending or modify the destination address of the short message before sending it.download4.7 EventIn addition to the set of events defined in ETSI TS 102 223 [32], the following event may also be reported to the UICC: - Network Rejection4.8 SecuritySee ETSI TS 102 223 [32].card4.9 MultipleSee ETSI TS 102 223 [32].Expiration4.10 TimerSee ETSI TS 102 223 [32].4.11 Bearer Independent ProtocolSee ETSI TS 102 223 [32].4.12 Description of the access technology indicator mechanismSee ETSI TS 102 223 [32].4.13 Description of the network search mode mechanismSee ETSI TS 102 223 [32].4.14 Geographical location discoveryThe proactive command Geographical Location Request and the envelope command Geographical Location Reportingallows the UICC to request and receive the current geographical location information from the ME when the ME isequipped with a positioning feature and it is enabled (e.g. autonomous GPS, Assisted GPS or Assisted GNSS).download5 Profile5.1 ProcedureThe profile download instruction is sent by the ME to the UICC as part of the UICC initialization procedure. The UICCinitialization procedure is specified in TS 31.101 [13].If the UICC indicates the support of "Additional TERMINAL PROFILE after UICC activation" in its USIM ServiceTable, the ME shall handle the profile download procedure as specified in ETSI TS 102 223 [32].If the UICC does not indicate the support of "Additional TERMINAL PROFILE after UICC activation" in its USIMService Table, the profile download instruction shall only be sent by the ME to the UICC as part of the UICCinitialization procedure. However, if a USIM initialisation procedure is performed due to a refresh proactive command,the USIM initialisation procedure may also include a profile download.The profile(s) sent by the ME shall state the facilities relevant to USAT that are supported by the ME.5.2 Structure and coding of TERMINAL PROFILEDirection: ME to UICC.The command header is specified in TS 31.101 [13].Command parameters/data:LengthM/O/CDescription ClauseMlgth Profile -- Profile:Contents:- The list of USAT facilities that are supported by the ME.Coding:- 1 bit is used to code each facility:- bit = 1: facility supported by ME.- bit = 0: facility not supported by ME.NOTE: several bits may need to be set to 1 for the support of the same facility. This is because of backwardcompatibility with SAT: several options existed in SAT for a given facility, and they are mandatory inUSAT when this facility is supported.First byte (Download):b8 b7 b6 b5 b4 b3 b2b1[32]223TS102SeedownloadSMS-PPdatadownloaddataBroadcastCell[32]102223TSSeeBit = 1 if SMS-PP data download is supported223[32]TS102SeeBit = 1 if Call Control by USIM is supportedBit = 1 if Call Control by USIM is supportedSecond byte (Other):b8 b7 b6 b5 b4 b3 b2b1223[32]102TSSeeUSIMbyControlCallBit = 1 if Call Control by USIM is supportedbycontrolUSIMmessageMOshortBit = 1 if Call Control by USIM is supported223[32]TS102See[32]102223SeeTS223[32]TS102SeeThird byte (Proactive UICC):- See ETSI TS 102 223 [32].Fourth byte (Proactive UICC):b8 b7 b6 b5 b4 b3 b2b1223[32]102TSSeeSHORTSENDMESSAGEUICC:ProactiveSSSENDUICC:ProactiveUSSDSENDProactiveUICC:[32]223102SeeTS102[32]223TSSee[32]223102SeeTS(NMR)-inINFORMATIONPROVIDEProactiveUICC:LOCAL3GPP terms, this indicates support for GERANFifth byte (Event driven information):- See ETSI TS 102 223 [32].Sixth byte (Event driven information extensions):- See ETSI TS 102 223 [32].Seventh byte (Multiple card proactive commands) for class "a":- See ETSI TS 102 223 [32].Eighth byte (Proactive UICC):b8 b7 b6 b5 b4 b3 b2b1[32]223102SeeTS[32]223102SeeTS[32]223102SeeTS223[32]TS102See[32]223102SeeTS223[32]TS102See223[32]TS102SeeBit = 1 if Call Control by USIM is supportedNinth byte:b8 b7 b6 b5 b4 b3 b2b1223102[32]TSSee223[32]102TSSee[32]223See102TS223[32]102TSSeeINFORMATIONLOCAL(Timing ProactiveUICC:PROVIDEAdvance)[32]223TS102See223[32]TS102See223[32]TS102SeeTenth byte (Soft keys support) for class "d":- See ETSI TS 102 223 [32].Eleventh byte: (Soft keys information):- See ETSI TS 102 223 [32].Twelfth byte:- See ETSI TS 102 223 [32].Thirteenth byte:- See ETSI TS 102 223 [32].Fourteenth byte: (Screen height):- See ETSI TS 102 223 [32].Fifteenth byte: (Screen width):- See ETSI TS 102 223 [32].Sixteenth byte: (Screen effects):- See ETSI TS 102 223 [32].Seventeenth byte:b8 b7 b6 b5 b4 b3 b2b1223[32]TS102Seeissupported)"e"HSDPA(ifclassEighteenth byte:b8 b7 b6 b5 b4 b3 b2b1[32]223See102TSonGPRSCONTROLCALL[32]102223SeeTSNineteenth byte: (reserved for TIA/EIA-136 facilities):- See ETSI TS 102 223 [32].Twentieth byte: (reserved for TIA/EIA/IS-820 facilities):- See ETSI TS 102 223 [32].。

Indradrive 系列故障代码

Error MessagesF9001 Error internal function call.F9002 Error internal RTOS function callF9003 WatchdogF9004 Hardware trapF8000 Fatal hardware errorF8010 Autom. commutation: Max. motion range when moving back F8011 Commutation offset could not be determinedF8012 Autom. commutation: Max. motion rangeF8013 Automatic commutation: Current too lowF8014 Automatic commutation: OvercurrentF8015 Automatic commutation: TimeoutF8016 Automatic commutation: Iteration without resultF8017 Automatic commutation: Incorrect commutation adjustment F8018 Device overtemperature shutdownF8022 Enc. 1: Enc. signals incorr. (can be cleared in ph. 2) F8023 Error mechanical link of encoder or motor connectionF8025 Overvoltage in power sectionF8027 Safe torque off while drive enabledF8028 Overcurrent in power sectionF8030 Safe stop 1 while drive enabledF8042 Encoder 2 error: Signal amplitude incorrectF8057 Device overload shutdownF8060 Overcurrent in power sectionF8064 Interruption of motor phaseF8067 Synchronization PWM-Timer wrongF8069 +/-15Volt DC errorF8070 +24Volt DC errorF8076 Error in error angle loopF8078 Speed loop error.F8079 Velocity limit value exceededF8091 Power section defectiveF8100 Error when initializing the parameter handlingF8102 Error when initializing power sectionF8118 Invalid power section/firmware combinationF8120 Invalid control section/firmware combinationF8122 Control section defectiveF8129 Incorrect optional module firmwareF8130 Firmware of option 2 of safety technology defectiveF8133 Error when checking interrupting circuitsF8134 SBS: Fatal errorF8135 SMD: Velocity exceededF8140 Fatal CCD error.F8201 Safety command for basic initialization incorrectF8203 Safety technology configuration parameter invalidF8813 Connection error mains chokeF8830 Power section errorF8838 Overcurrent external braking resistorF7010 Safely-limited increment exceededF7011 Safely-monitored position, exceeded in pos. DirectionF7012 Safely-monitored position, exceeded in neg. DirectionF7013 Safely-limited speed exceededF7020 Safe maximum speed exceededF7021 Safely-limited position exceededF7030 Position window Safe stop 2 exceededF7031 Incorrect direction of motionF7040 Validation error parameterized - effective thresholdF7041 Actual position value validation errorF7042 Validation error of safe operation modeF7043 Error of output stage interlockF7050 Time for stopping process exceeded8.3.15 F7051 Safely-monitored deceleration exceeded (159)8.4 Travel Range Errors (F6xxx) (161)8.4.1 Behavior in the Case of Travel Range Errors (161)8.4.2 F6010 PLC Runtime Error (162)8.4.3 F6024 Maximum braking time exceeded (163)8.4.4 F6028 Position limit value exceeded (overflow) (164)8.4.5 F6029 Positive position limit exceeded (164)8.4.6 F6030 Negative position limit exceeded (165)8.4.7 F6034 Emergency-Stop (166)8.4.8 F6042 Both travel range limit switches activated (167)8.4.9 F6043 Positive travel range limit switch activated (167)8.4.10 F6044 Negative travel range limit switch activated (168)8.4.11 F6140 CCD slave error (emergency halt) (169)8.5 Interface Errors (F4xxx) (169)8.5.1 Behavior in the Case of Interface Errors (169)8.5.2 F4001 Sync telegram failure (170)8.5.3 F4002 RTD telegram failure (171)8.5.4 F4003 Invalid communication phase shutdown (172)8.5.5 F4004 Error during phase progression (172)8.5.6 F4005 Error during phase regression (173)8.5.7 F4006 Phase switching without ready signal (173)8.5.8 F4009 Bus failure (173)8.5.9 F4012 Incorrect I/O length (175)8.5.10 F4016 PLC double real-time channel failure (176)8.5.11 F4017 S-III: Incorrect sequence during phase switch (176)8.5.12 F4034 Emergency-Stop (177)8.5.13 F4140 CCD communication error (178)8.6 Non-Fatal Safety Technology Errors (F3xxx) (178)8.6.1 Behavior in the Case of Non-Fatal Safety Technology Errors (178)8.6.2 F3111 Refer. missing when selecting safety related end pos (179)8.6.3 F3112 Safe reference missing (179)8.6.4 F3115 Brake check time interval exceeded (181)Troubleshooting Guide | Rexroth IndraDrive Electric Drivesand ControlsI Bosch Rexroth AG VII/XXIITable of ContentsPage8.6.5 F3116 Nominal load torque of holding system exceeded (182)8.6.6 F3117 Actual position values validation error (182)8.6.7 F3122 SBS: System error (183)8.6.8 F3123 SBS: Brake check missing (184)8.6.9 F3130 Error when checking input signals (185)8.6.10 F3131 Error when checking acknowledgment signal (185)8.6.11 F3132 Error when checking diagnostic output signal (186)8.6.12 F3133 Error when checking interrupting circuits (187)8.6.13 F3134 Dynamization time interval incorrect (188)8.6.14 F3135 Dynamization pulse width incorrect (189)8.6.15 F3140 Safety parameters validation error (192)8.6.16 F3141 Selection validation error (192)8.6.17 F3142 Activation time of enabling control exceeded (193)8.6.18 F3143 Safety command for clearing errors incorrect (194)8.6.19 F3144 Incorrect safety configuration (195)8.6.20 F3145 Error when unlocking the safety door (196)8.6.21 F3146 System error channel 2 (197)8.6.22 F3147 System error channel 1 (198)8.6.23 F3150 Safety command for system start incorrect (199)8.6.24 F3151 Safety command for system halt incorrect (200)8.6.25 F3152 Incorrect backup of safety technology data (201)8.6.26 F3160 Communication error of safe communication (202)8.7 Non-Fatal Errors (F2xxx) (202)8.7.1 Behavior in the Case of Non-Fatal Errors (202)8.7.2 F2002 Encoder assignment not allowed for synchronization (203)8.7.3 F2003 Motion step skipped (203)8.7.4 F2004 Error in MotionProfile (204)8.7.5 F2005 Cam table invalid (205)8.7.6 F2006 MMC was removed (206)8.7.7 F2007 Switching to non-initialized operation mode (206)8.7.8 F2008 RL The motor type has changed (207)8.7.9 F2009 PL Load parameter default values (208)8.7.10 F2010 Error when initializing digital I/O (-> S-0-0423) (209)8.7.11 F2011 PLC - Error no. 1 (210)8.7.12 F2012 PLC - Error no. 2 (210)8.7.13 F2013 PLC - Error no. 3 (211)8.7.14 F2014 PLC - Error no. 4 (211)8.7.15 F2018 Device overtemperature shutdown (211)8.7.16 F2019 Motor overtemperature shutdown (212)8.7.17 F2021 Motor temperature monitor defective (213)8.7.18 F2022 Device temperature monitor defective (214)8.7.19 F2025 Drive not ready for control (214)8.7.20 F2026 Undervoltage in power section (215)8.7.21 F2027 Excessive oscillation in DC bus (216)8.7.22 F2028 Excessive deviation (216)8.7.23 F2031 Encoder 1 error: Signal amplitude incorrect (217)VIII/XXII Bosch Rexroth AG | Electric Drivesand ControlsRexroth IndraDrive | Troubleshooting GuideTable of ContentsPage8.7.24 F2032 Validation error during commutation fine adjustment (217)8.7.25 F2033 External power supply X10 error (218)8.7.26 F2036 Excessive position feedback difference (219)8.7.27 F2037 Excessive position command difference (220)8.7.28 F2039 Maximum acceleration exceeded (220)8.7.29 F2040 Device overtemperature 2 shutdown (221)8.7.30 F2042 Encoder 2: Encoder signals incorrect (222)8.7.31 F2043 Measuring encoder: Encoder signals incorrect (222)8.7.32 F2044 External power supply X15 error (223)8.7.33 F2048 Low battery voltage (224)8.7.34 F2050 Overflow of target position preset memory (225)8.7.35 F2051 No sequential block in target position preset memory (225)8.7.36 F2053 Incr. encoder emulator: Pulse frequency too high (226)8.7.37 F2054 Incr. encoder emulator: Hardware error (226)8.7.38 F2055 External power supply dig. I/O error (227)8.7.39 F2057 Target position out of travel range (227)8.7.40 F2058 Internal overflow by positioning input (228)8.7.41 F2059 Incorrect command value direction when positioning (229)8.7.42 F2063 Internal overflow master axis generator (230)8.7.43 F2064 Incorrect cmd value direction master axis generator (230)8.7.44 F2067 Synchronization to master communication incorrect (231)8.7.45 F2068 Brake error (231)8.7.46 F2069 Error when releasing the motor holding brake (232)8.7.47 F2074 Actual pos. value 1 outside absolute encoder window (232)8.7.48 F2075 Actual pos. value 2 outside absolute encoder window (233)8.7.49 F2076 Actual pos. value 3 outside absolute encoder window (234)8.7.50 F2077 Current measurement trim wrong (235)8.7.51 F2086 Error supply module (236)8.7.52 F2087 Module group communication error (236)8.7.53 F2100 Incorrect access to command value memory (237)8.7.54 F2101 It was impossible to address MMC (237)8.7.55 F2102 It was impossible to address I2C memory (238)8.7.56 F2103 It was impossible to address EnDat memory (238)8.7.57 F2104 Commutation offset invalid (239)8.7.58 F2105 It was impossible to address Hiperface memory (239)8.7.59 F2110 Error in non-cyclical data communic. of power section (240)8.7.60 F2120 MMC: Defective or missing, replace (240)8.7.61 F2121 MMC: Incorrect data or file, create correctly (241)8.7.62 F2122 MMC: Incorrect IBF file, correct it (241)8.7.63 F2123 Retain data backup impossible (242)8.7.64 F2124 MMC: Saving too slowly, replace (243)8.7.65 F2130 Error comfort control panel (243)8.7.66 F2140 CCD slave error (243)8.7.67 F2150 MLD motion function block error (244)8.7.68 F2174 Loss of motor encoder reference (244)8.7.69 F2175 Loss of optional encoder reference (245)Troubleshooting Guide | Rexroth IndraDrive Electric Drivesand Controls| Bosch Rexroth AG IX/XXIITable of ContentsPage8.7.70 F2176 Loss of measuring encoder reference (246)8.7.71 F2177 Modulo limitation error of motor encoder (246)8.7.72 F2178 Modulo limitation error of optional encoder (247)8.7.73 F2179 Modulo limitation error of measuring encoder (247)8.7.74 F2190 Incorrect Ethernet configuration (248)8.7.75 F2260 Command current limit shutoff (249)8.7.76 F2270 Analog input 1 or 2, wire break (249)8.7.77 F2802 PLL is not synchronized (250)8.7.78 F2814 Undervoltage in mains (250)8.7.79 F2815 Overvoltage in mains (251)8.7.80 F2816 Softstart fault power supply unit (251)8.7.81 F2817 Overvoltage in power section (251)8.7.82 F2818 Phase failure (252)8.7.83 F2819 Mains failure (253)8.7.84 F2820 Braking resistor overload (253)8.7.85 F2821 Error in control of braking resistor (254)8.7.86 F2825 Switch-on threshold braking resistor too low (255)8.7.87 F2833 Ground fault in motor line (255)8.7.88 F2834 Contactor control error (256)8.7.89 F2835 Mains contactor wiring error (256)8.7.90 F2836 DC bus balancing monitor error (257)8.7.91 F2837 Contactor monitoring error (257)8.7.92 F2840 Error supply shutdown (257)8.7.93 F2860 Overcurrent in mains-side power section (258)8.7.94 F2890 Invalid device code (259)8.7.95 F2891 Incorrect interrupt timing (259)8.7.96 F2892 Hardware variant not supported (259)8.8 SERCOS Error Codes / Error Messages of Serial Communication (259)9 Warnings (Exxxx) (263)9.1 Fatal Warnings (E8xxx) (263)9.1.1 Behavior in the Case of Fatal Warnings (263)9.1.2 E8025 Overvoltage in power section (263)9.1.3 E8026 Undervoltage in power section (264)9.1.4 E8027 Safe torque off while drive enabled (265)9.1.5 E8028 Overcurrent in power section (265)9.1.6 E8029 Positive position limit exceeded (266)9.1.7 E8030 Negative position limit exceeded (267)9.1.8 E8034 Emergency-Stop (268)9.1.9 E8040 Torque/force actual value limit active (268)9.1.10 E8041 Current limit active (269)9.1.11 E8042 Both travel range limit switches activated (269)9.1.12 E8043 Positive travel range limit switch activated (270)9.1.13 E8044 Negative travel range limit switch activated (271)9.1.14 E8055 Motor overload, current limit active (271)9.1.15 E8057 Device overload, current limit active (272)X/XXII Bosch Rexroth AG | Electric Drivesand ControlsRexroth IndraDrive | Troubleshooting GuideTable of ContentsPage9.1.16 E8058 Drive system not ready for operation (273)9.1.17 E8260 Torque/force command value limit active (273)9.1.18 E8802 PLL is not synchronized (274)9.1.19 E8814 Undervoltage in mains (275)9.1.20 E8815 Overvoltage in mains (275)9.1.21 E8818 Phase failure (276)9.1.22 E8819 Mains failure (276)9.2 Warnings of Category E4xxx (277)9.2.1 E4001 Double MST failure shutdown (277)9.2.2 E4002 Double MDT failure shutdown (278)9.2.3 E4005 No command value input via master communication (279)9.2.4 E4007 SERCOS III: Consumer connection failed (280)9.2.5 E4008 Invalid addressing command value data container A (280)9.2.6 E4009 Invalid addressing actual value data container A (281)9.2.7 E4010 Slave not scanned or address 0 (281)9.2.8 E4012 Maximum number of CCD slaves exceeded (282)9.2.9 E4013 Incorrect CCD addressing (282)9.2.10 E4014 Incorrect phase switch of CCD slaves (283)9.3 Possible Warnings When Operating Safety Technology (E3xxx) (283)9.3.1 Behavior in Case a Safety Technology Warning Occurs (283)9.3.2 E3100 Error when checking input signals (284)9.3.3 E3101 Error when checking acknowledgment signal (284)9.3.4 E3102 Actual position values validation error (285)9.3.5 E3103 Dynamization failed (285)9.3.6 E3104 Safety parameters validation error (286)9.3.7 E3105 Validation error of safe operation mode (286)9.3.8 E3106 System error safety technology (287)9.3.9 E3107 Safe reference missing (287)9.3.10 E3108 Safely-monitored deceleration exceeded (288)9.3.11 E3110 Time interval of forced dynamization exceeded (289)9.3.12 E3115 Prewarning, end of brake check time interval (289)9.3.13 E3116 Nominal load torque of holding system reached (290)9.4 Non-Fatal Warnings (E2xxx) (290)9.4.1 Behavior in Case a Non-Fatal Warning Occurs (290)9.4.2 E2010 Position control with encoder 2 not possible (291)9.4.3 E2011 PLC - Warning no. 1 (291)9.4.4 E2012 PLC - Warning no. 2 (291)9.4.5 E2013 PLC - Warning no. 3 (292)9.4.6 E2014 PLC - Warning no. 4 (292)9.4.7 E2021 Motor temperature outside of measuring range (292)9.4.8 E2026 Undervoltage in power section (293)9.4.9 E2040 Device overtemperature 2 prewarning (294)9.4.10 E2047 Interpolation velocity = 0 (294)9.4.11 E2048 Interpolation acceleration = 0 (295)9.4.12 E2049 Positioning velocity >= limit value (296)9.4.13 E2050 Device overtemp. Prewarning (297)Troubleshooting Guide | Rexroth IndraDrive Electric Drivesand Controls| Bosch Rexroth AG XI/XXIITable of ContentsPage9.4.14 E2051 Motor overtemp. prewarning (298)9.4.15 E2053 Target position out of travel range (298)9.4.16 E2054 Not homed (300)9.4.17 E2055 Feedrate override S-0-0108 = 0 (300)9.4.18 E2056 Torque limit = 0 (301)9.4.19 E2058 Selected positioning block has not been programmed (302)9.4.20 E2059 Velocity command value limit active (302)9.4.21 E2061 Device overload prewarning (303)9.4.22 E2063 Velocity command value > limit value (304)9.4.23 E2064 Target position out of num. range (304)9.4.24 E2069 Holding brake torque too low (305)9.4.25 E2070 Acceleration limit active (306)9.4.26 E2074 Encoder 1: Encoder signals disturbed (306)9.4.27 E2075 Encoder 2: Encoder signals disturbed (307)9.4.28 E2076 Measuring encoder: Encoder signals disturbed (308)9.4.29 E2077 Absolute encoder monitoring, motor encoder (encoder alarm) (308)9.4.30 E2078 Absolute encoder monitoring, opt. encoder (encoder alarm) (309)9.4.31 E2079 Absolute enc. monitoring, measuring encoder (encoder alarm) (309)9.4.32 E2086 Prewarning supply module overload (310)9.4.33 E2092 Internal synchronization defective (310)9.4.34 E2100 Positioning velocity of master axis generator too high (311)9.4.35 E2101 Acceleration of master axis generator is zero (312)9.4.36 E2140 CCD error at node (312)9.4.37 E2270 Analog input 1 or 2, wire break (312)9.4.38 E2802 HW control of braking resistor (313)9.4.39 E2810 Drive system not ready for operation (314)9.4.40 E2814 Undervoltage in mains (314)9.4.41 E2816 Undervoltage in power section (314)9.4.42 E2818 Phase failure (315)9.4.43 E2819 Mains failure (315)9.4.44 E2820 Braking resistor overload prewarning (316)9.4.45 E2829 Not ready for power on (316)。

critical error message version -回复

critical error message version -回复什么是“critical error message version”?Critical error message version ，即关键错误信息版本，是指在计算机软件或系统中出现的重要错误提示。

这些错误信息通常与系统运行或软件操作相关，当发生关键错误时，会阻碍程序的正常运行，甚至导致系统崩溃。

本文将逐步解析关于“critical error message version”的相关主题，并探讨如何处理和避免这些错误。

第一步：理解关键错误信息版本的作用和意义关键错误信息版本的主要作用是告知用户或软件开发人员系统发生了严重错误。

这种错误可能与文件损坏、硬件故障、网络连接问题或未知错误等有关。

通过错误信息，用户或开发人员可以了解到出现的具体错误类型及其可能的原因，从而更好地找到解决方案。

第二步：探索常见的关键错误信息版本及其意义常见的关键错误信息版本包括但不限于以下几种：1. 蓝屏错误（Blue Screen of Death，简称BSOD）：这种错误通常在Windows操作系统中出现。

当系统出现严重问题时，蓝屏错误会显示一条错误代码和错误信息，并导致系统停止运行。

这种错误通常涉及硬件问题，例如内存不足、驱动程序冲突或磁盘错误等。

2. 段错误（segmentation fault）：出现在Linux或Unix系统中的关键错误。

它表示正在访问无效内存地址，常常由程序错误或内存泄漏引起。

段错误可能导致程序异常终止或崩溃。

3. 运行时错误（runtime error）：这种错误类型通常发生在编译型语言中，如C++或Java。

运行时错误包括空指针引用、除零错误或数组访问越界等。

这些错误会导致程序崩溃或产生不可预测的结果。

4. 数据库错误：当使用数据库进行数据存储和检索时，可能会发生关键错误。

例如，连接超时、无效的SQL查询或数据库损坏等。

3GPP TS 36.331 V13.2.0 (2016-06)

3GPP TS 36.331 V13.2.0 (2016-06)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specification(Release 13)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.KeywordsUMTS, radio3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM AssociationBluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its membersContentsForeword (18)1Scope (19)2References (19)3Definitions, symbols and abbreviations (22)3.1Definitions (22)3.2Abbreviations (24)4General (27)4.1Introduction (27)4.2Architecture (28)4.2.1UE states and state transitions including inter RAT (28)4.2.2Signalling radio bearers (29)4.3Services (30)4.3.1Services provided to upper layers (30)4.3.2Services expected from lower layers (30)4.4Functions (30)5Procedures (32)5.1General (32)5.1.1Introduction (32)5.1.2General requirements (32)5.2System information (33)5.2.1Introduction (33)5.2.1.1General (33)5.2.1.2Scheduling (34)5.2.1.2a Scheduling for NB-IoT (34)5.2.1.3System information validity and notification of changes (35)5.2.1.4Indication of ETWS notification (36)5.2.1.5Indication of CMAS notification (37)5.2.1.6Notification of EAB parameters change (37)5.2.1.7Access Barring parameters change in NB-IoT (37)5.2.2System information acquisition (38)5.2.2.1General (38)5.2.2.2Initiation (38)5.2.2.3System information required by the UE (38)5.2.2.4System information acquisition by the UE (39)5.2.2.5Essential system information missing (42)5.2.2.6Actions upon reception of the MasterInformationBlock message (42)5.2.2.7Actions upon reception of the SystemInformationBlockType1 message (42)5.2.2.8Actions upon reception of SystemInformation messages (44)5.2.2.9Actions upon reception of SystemInformationBlockType2 (44)5.2.2.10Actions upon reception of SystemInformationBlockType3 (45)5.2.2.11Actions upon reception of SystemInformationBlockType4 (45)5.2.2.12Actions upon reception of SystemInformationBlockType5 (45)5.2.2.13Actions upon reception of SystemInformationBlockType6 (45)5.2.2.14Actions upon reception of SystemInformationBlockType7 (45)5.2.2.15Actions upon reception of SystemInformationBlockType8 (45)5.2.2.16Actions upon reception of SystemInformationBlockType9 (46)5.2.2.17Actions upon reception of SystemInformationBlockType10 (46)5.2.2.18Actions upon reception of SystemInformationBlockType11 (46)5.2.2.19Actions upon reception of SystemInformationBlockType12 (47)5.2.2.20Actions upon reception of SystemInformationBlockType13 (48)5.2.2.21Actions upon reception of SystemInformationBlockType14 (48)5.2.2.22Actions upon reception of SystemInformationBlockType15 (48)5.2.2.23Actions upon reception of SystemInformationBlockType16 (48)5.2.2.24Actions upon reception of SystemInformationBlockType17 (48)5.2.2.25Actions upon reception of SystemInformationBlockType18 (48)5.2.2.26Actions upon reception of SystemInformationBlockType19 (49)5.2.3Acquisition of an SI message (49)5.2.3a Acquisition of an SI message by BL UE or UE in CE or a NB-IoT UE (50)5.3Connection control (50)5.3.1Introduction (50)5.3.1.1RRC connection control (50)5.3.1.2Security (52)5.3.1.2a RN security (53)5.3.1.3Connected mode mobility (53)5.3.1.4Connection control in NB-IoT (54)5.3.2Paging (55)5.3.2.1General (55)5.3.2.2Initiation (55)5.3.2.3Reception of the Paging message by the UE (55)5.3.3RRC connection establishment (56)5.3.3.1General (56)5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/ discovery (58)5.3.3.2Initiation (59)5.3.3.3Actions related to transmission of RRCConnectionRequest message (63)5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message (64)5.3.3.4Reception of the RRCConnectionSetup by the UE (64)5.3.3.4a Reception of the RRCConnectionResume by the UE (66)5.3.3.5Cell re-selection while T300, T302, T303, T305, T306, or T308 is running (68)5.3.3.6T300 expiry (68)5.3.3.7T302, T303, T305, T306, or T308 expiry or stop (69)5.3.3.8Reception of the RRCConnectionReject by the UE (70)5.3.3.9Abortion of RRC connection establishment (71)5.3.3.10Handling of SSAC related parameters (71)5.3.3.11Access barring check (72)5.3.3.12EAB check (73)5.3.3.13Access barring check for ACDC (73)5.3.3.14Access Barring check for NB-IoT (74)5.3.4Initial security activation (75)5.3.4.1General (75)5.3.4.2Initiation (76)5.3.4.3Reception of the SecurityModeCommand by the UE (76)5.3.5RRC connection reconfiguration (77)5.3.5.1General (77)5.3.5.2Initiation (77)5.3.5.3Reception of an RRCConnectionReconfiguration not including the mobilityControlInfo by theUE (77)5.3.5.4Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE(handover) (79)5.3.5.5Reconfiguration failure (83)5.3.5.6T304 expiry (handover failure) (83)5.3.5.7Void (84)5.3.5.7a T307 expiry (SCG change failure) (84)5.3.5.8Radio Configuration involving full configuration option (84)5.3.6Counter check (86)5.3.6.1General (86)5.3.6.2Initiation (86)5.3.6.3Reception of the CounterCheck message by the UE (86)5.3.7RRC connection re-establishment (87)5.3.7.1General (87)5.3.7.2Initiation (87)5.3.7.3Actions following cell selection while T311 is running (88)5.3.7.4Actions related to transmission of RRCConnectionReestablishmentRequest message (89)5.3.7.5Reception of the RRCConnectionReestablishment by the UE (89)5.3.7.6T311 expiry (91)5.3.7.7T301 expiry or selected cell no longer suitable (91)5.3.7.8Reception of RRCConnectionReestablishmentReject by the UE (91)5.3.8RRC connection release (92)5.3.8.1General (92)5.3.8.2Initiation (92)5.3.8.3Reception of the RRCConnectionRelease by the UE (92)5.3.8.4T320 expiry (93)5.3.9RRC connection release requested by upper layers (93)5.3.9.1General (93)5.3.9.2Initiation (93)5.3.10Radio resource configuration (93)5.3.10.0General (93)5.3.10.1SRB addition/ modification (94)5.3.10.2DRB release (95)5.3.10.3DRB addition/ modification (95)5.3.10.3a1DC specific DRB addition or reconfiguration (96)5.3.10.3a2LWA specific DRB addition or reconfiguration (98)5.3.10.3a3LWIP specific DRB addition or reconfiguration (98)5.3.10.3a SCell release (99)5.3.10.3b SCell addition/ modification (99)5.3.10.3c PSCell addition or modification (99)5.3.10.4MAC main reconfiguration (99)5.3.10.5Semi-persistent scheduling reconfiguration (100)5.3.10.6Physical channel reconfiguration (100)5.3.10.7Radio Link Failure Timers and Constants reconfiguration (101)5.3.10.8Time domain measurement resource restriction for serving cell (101)5.3.10.9Other configuration (102)5.3.10.10SCG reconfiguration (103)5.3.10.11SCG dedicated resource configuration (104)5.3.10.12Reconfiguration SCG or split DRB by drb-ToAddModList (105)5.3.10.13Neighbour cell information reconfiguration (105)5.3.10.14Void (105)5.3.10.15Sidelink dedicated configuration (105)5.3.10.16T370 expiry (106)5.3.11Radio link failure related actions (107)5.3.11.1Detection of physical layer problems in RRC_CONNECTED (107)5.3.11.2Recovery of physical layer problems (107)5.3.11.3Detection of radio link failure (107)5.3.12UE actions upon leaving RRC_CONNECTED (109)5.3.13UE actions upon PUCCH/ SRS release request (110)5.3.14Proximity indication (110)5.3.14.1General (110)5.3.14.2Initiation (111)5.3.14.3Actions related to transmission of ProximityIndication message (111)5.3.15Void (111)5.4Inter-RAT mobility (111)5.4.1Introduction (111)5.4.2Handover to E-UTRA (112)5.4.2.1General (112)5.4.2.2Initiation (112)5.4.2.3Reception of the RRCConnectionReconfiguration by the UE (112)5.4.2.4Reconfiguration failure (114)5.4.2.5T304 expiry (handover to E-UTRA failure) (114)5.4.3Mobility from E-UTRA (114)5.4.3.1General (114)5.4.3.2Initiation (115)5.4.3.3Reception of the MobilityFromEUTRACommand by the UE (115)5.4.3.4Successful completion of the mobility from E-UTRA (116)5.4.3.5Mobility from E-UTRA failure (117)5.4.4Handover from E-UTRA preparation request (CDMA2000) (117)5.4.4.1General (117)5.4.4.2Initiation (118)5.4.4.3Reception of the HandoverFromEUTRAPreparationRequest by the UE (118)5.4.5UL handover preparation transfer (CDMA2000) (118)5.4.5.1General (118)5.4.5.2Initiation (118)5.4.5.3Actions related to transmission of the ULHandoverPreparationTransfer message (119)5.4.5.4Failure to deliver the ULHandoverPreparationTransfer message (119)5.4.6Inter-RAT cell change order to E-UTRAN (119)5.4.6.1General (119)5.4.6.2Initiation (119)5.4.6.3UE fails to complete an inter-RAT cell change order (119)5.5Measurements (120)5.5.1Introduction (120)5.5.2Measurement configuration (121)5.5.2.1General (121)5.5.2.2Measurement identity removal (122)5.5.2.2a Measurement identity autonomous removal (122)5.5.2.3Measurement identity addition/ modification (123)5.5.2.4Measurement object removal (124)5.5.2.5Measurement object addition/ modification (124)5.5.2.6Reporting configuration removal (126)5.5.2.7Reporting configuration addition/ modification (127)5.5.2.8Quantity configuration (127)5.5.2.9Measurement gap configuration (127)5.5.2.10Discovery signals measurement timing configuration (128)5.5.2.11RSSI measurement timing configuration (128)5.5.3Performing measurements (128)5.5.3.1General (128)5.5.3.2Layer 3 filtering (131)5.5.4Measurement report triggering (131)5.5.4.1General (131)5.5.4.2Event A1 (Serving becomes better than threshold) (135)5.5.4.3Event A2 (Serving becomes worse than threshold) (136)5.5.4.4Event A3 (Neighbour becomes offset better than PCell/ PSCell) (136)5.5.4.5Event A4 (Neighbour becomes better than threshold) (137)5.5.4.6Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better thanthreshold2) (138)5.5.4.6a Event A6 (Neighbour becomes offset better than SCell) (139)5.5.4.7Event B1 (Inter RAT neighbour becomes better than threshold) (139)5.5.4.8Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better thanthreshold2) (140)5.5.4.9Event C1 (CSI-RS resource becomes better than threshold) (141)5.5.4.10Event C2 (CSI-RS resource becomes offset better than reference CSI-RS resource) (141)5.5.4.11Event W1 (WLAN becomes better than a threshold) (142)5.5.4.12Event W2 (All WLAN inside WLAN mobility set becomes worse than threshold1 and a WLANoutside WLAN mobility set becomes better than threshold2) (142)5.5.4.13Event W3 (All WLAN inside WLAN mobility set becomes worse than a threshold) (143)5.5.5Measurement reporting (144)5.5.6Measurement related actions (148)5.5.6.1Actions upon handover and re-establishment (148)5.5.6.2Speed dependant scaling of measurement related parameters (149)5.5.7Inter-frequency RSTD measurement indication (149)5.5.7.1General (149)5.5.7.2Initiation (150)5.5.7.3Actions related to transmission of InterFreqRSTDMeasurementIndication message (150)5.6Other (150)5.6.0General (150)5.6.1DL information transfer (151)5.6.1.1General (151)5.6.1.2Initiation (151)5.6.1.3Reception of the DLInformationTransfer by the UE (151)5.6.2UL information transfer (151)5.6.2.1General (151)5.6.2.2Initiation (151)5.6.2.3Actions related to transmission of ULInformationTransfer message (152)5.6.2.4Failure to deliver ULInformationTransfer message (152)5.6.3UE capability transfer (152)5.6.3.1General (152)5.6.3.2Initiation (153)5.6.3.3Reception of the UECapabilityEnquiry by the UE (153)5.6.4CSFB to 1x Parameter transfer (157)5.6.4.1General (157)5.6.4.2Initiation (157)5.6.4.3Actions related to transmission of CSFBParametersRequestCDMA2000 message (157)5.6.4.4Reception of the CSFBParametersResponseCDMA2000 message (157)5.6.5UE Information (158)5.6.5.1General (158)5.6.5.2Initiation (158)5.6.5.3Reception of the UEInformationRequest message (158)5.6.6 Logged Measurement Configuration (159)5.6.6.1General (159)5.6.6.2Initiation (160)5.6.6.3Reception of the LoggedMeasurementConfiguration by the UE (160)5.6.6.4T330 expiry (160)5.6.7 Release of Logged Measurement Configuration (160)5.6.7.1General (160)5.6.7.2Initiation (160)5.6.8 Measurements logging (161)5.6.8.1General (161)5.6.8.2Initiation (161)5.6.9In-device coexistence indication (163)5.6.9.1General (163)5.6.9.2Initiation (164)5.6.9.3Actions related to transmission of InDeviceCoexIndication message (164)5.6.10UE Assistance Information (165)5.6.10.1General (165)5.6.10.2Initiation (166)5.6.10.3Actions related to transmission of UEAssistanceInformation message (166)5.6.11 Mobility history information (166)5.6.11.1General (166)5.6.11.2Initiation (166)5.6.12RAN-assisted WLAN interworking (167)5.6.12.1General (167)5.6.12.2Dedicated WLAN offload configuration (167)5.6.12.3WLAN offload RAN evaluation (167)5.6.12.4T350 expiry or stop (167)5.6.12.5Cell selection/ re-selection while T350 is running (168)5.6.13SCG failure information (168)5.6.13.1General (168)5.6.13.2Initiation (168)5.6.13.3Actions related to transmission of SCGFailureInformation message (168)5.6.14LTE-WLAN Aggregation (169)5.6.14.1Introduction (169)5.6.14.2Reception of LWA configuration (169)5.6.14.3Release of LWA configuration (170)5.6.15WLAN connection management (170)5.6.15.1Introduction (170)5.6.15.2WLAN connection status reporting (170)5.6.15.2.1General (170)5.6.15.2.2Initiation (171)5.6.15.2.3Actions related to transmission of WLANConnectionStatusReport message (171)5.6.15.3T351 Expiry (WLAN connection attempt timeout) (171)5.6.15.4WLAN status monitoring (171)5.6.16RAN controlled LTE-WLAN interworking (172)5.6.16.1General (172)5.6.16.2WLAN traffic steering command (172)5.6.17LTE-WLAN aggregation with IPsec tunnel (173)5.6.17.1General (173)5.7Generic error handling (174)5.7.1General (174)5.7.2ASN.1 violation or encoding error (174)5.7.3Field set to a not comprehended value (174)5.7.4Mandatory field missing (174)5.7.5Not comprehended field (176)5.8MBMS (176)5.8.1Introduction (176)5.8.1.1General (176)5.8.1.2Scheduling (176)5.8.1.3MCCH information validity and notification of changes (176)5.8.2MCCH information acquisition (178)5.8.2.1General (178)5.8.2.2Initiation (178)5.8.2.3MCCH information acquisition by the UE (178)5.8.2.4Actions upon reception of the MBSFNAreaConfiguration message (178)5.8.2.5Actions upon reception of the MBMSCountingRequest message (179)5.8.3MBMS PTM radio bearer configuration (179)5.8.3.1General (179)5.8.3.2Initiation (179)5.8.3.3MRB establishment (179)5.8.3.4MRB release (179)5.8.4MBMS Counting Procedure (179)5.8.4.1General (179)5.8.4.2Initiation (180)5.8.4.3Reception of the MBMSCountingRequest message by the UE (180)5.8.5MBMS interest indication (181)5.8.5.1General (181)5.8.5.2Initiation (181)5.8.5.3Determine MBMS frequencies of interest (182)5.8.5.4Actions related to transmission of MBMSInterestIndication message (183)5.8a SC-PTM (183)5.8a.1Introduction (183)5.8a.1.1General (183)5.8a.1.2SC-MCCH scheduling (183)5.8a.1.3SC-MCCH information validity and notification of changes (183)5.8a.1.4Procedures (184)5.8a.2SC-MCCH information acquisition (184)5.8a.2.1General (184)5.8a.2.2Initiation (184)5.8a.2.3SC-MCCH information acquisition by the UE (184)5.8a.2.4Actions upon reception of the SCPTMConfiguration message (185)5.8a.3SC-PTM radio bearer configuration (185)5.8a.3.1General (185)5.8a.3.2Initiation (185)5.8a.3.3SC-MRB establishment (185)5.8a.3.4SC-MRB release (185)5.9RN procedures (186)5.9.1RN reconfiguration (186)5.9.1.1General (186)5.9.1.2Initiation (186)5.9.1.3Reception of the RNReconfiguration by the RN (186)5.10Sidelink (186)5.10.1Introduction (186)5.10.1a Conditions for sidelink communication operation (187)5.10.2Sidelink UE information (188)5.10.2.1General (188)5.10.2.2Initiation (189)5.10.2.3Actions related to transmission of SidelinkUEInformation message (193)5.10.3Sidelink communication monitoring (195)5.10.6Sidelink discovery announcement (198)5.10.6a Sidelink discovery announcement pool selection (201)5.10.6b Sidelink discovery announcement reference carrier selection (201)5.10.7Sidelink synchronisation information transmission (202)5.10.7.1General (202)5.10.7.2Initiation (203)5.10.7.3Transmission of SLSS (204)5.10.7.4Transmission of MasterInformationBlock-SL message (205)5.10.7.5Void (206)5.10.8Sidelink synchronisation reference (206)5.10.8.1General (206)5.10.8.2Selection and reselection of synchronisation reference UE (SyncRef UE) (206)5.10.9Sidelink common control information (207)5.10.9.1General (207)5.10.9.2Actions related to reception of MasterInformationBlock-SL message (207)5.10.10Sidelink relay UE operation (207)5.10.10.1General (207)5.10.10.2AS-conditions for relay related sidelink communication transmission by sidelink relay UE (207)5.10.10.3AS-conditions for relay PS related sidelink discovery transmission by sidelink relay UE (208)5.10.10.4Sidelink relay UE threshold conditions (208)5.10.11Sidelink remote UE operation (208)5.10.11.1General (208)5.10.11.2AS-conditions for relay related sidelink communication transmission by sidelink remote UE (208)5.10.11.3AS-conditions for relay PS related sidelink discovery transmission by sidelink remote UE (209)5.10.11.4Selection and reselection of sidelink relay UE (209)5.10.11.5Sidelink remote UE threshold conditions (210)6Protocol data units, formats and parameters (tabular & ASN.1) (210)6.1General (210)6.2RRC messages (212)6.2.1General message structure (212)–EUTRA-RRC-Definitions (212)–BCCH-BCH-Message (212)–BCCH-DL-SCH-Message (212)–BCCH-DL-SCH-Message-BR (213)–MCCH-Message (213)–PCCH-Message (213)–DL-CCCH-Message (214)–DL-DCCH-Message (214)–UL-CCCH-Message (214)–UL-DCCH-Message (215)–SC-MCCH-Message (215)6.2.2Message definitions (216)–CounterCheck (216)–CounterCheckResponse (217)–CSFBParametersRequestCDMA2000 (217)–CSFBParametersResponseCDMA2000 (218)–DLInformationTransfer (218)–HandoverFromEUTRAPreparationRequest (CDMA2000) (219)–InDeviceCoexIndication (220)–InterFreqRSTDMeasurementIndication (222)–LoggedMeasurementConfiguration (223)–MasterInformationBlock (225)–MBMSCountingRequest (226)–MBMSCountingResponse (226)–MBMSInterestIndication (227)–MBSFNAreaConfiguration (228)–MeasurementReport (228)–MobilityFromEUTRACommand (229)–Paging (232)–ProximityIndication (233)–RNReconfiguration (234)–RNReconfigurationComplete (234)–RRCConnectionReconfiguration (235)–RRCConnectionReconfigurationComplete (240)–RRCConnectionReestablishment (241)–RRCConnectionReestablishmentComplete (241)–RRCConnectionReestablishmentReject (242)–RRCConnectionReestablishmentRequest (243)–RRCConnectionReject (243)–RRCConnectionRelease (244)–RRCConnectionResume (248)–RRCConnectionResumeComplete (249)–RRCConnectionResumeRequest (250)–RRCConnectionRequest (250)–RRCConnectionSetup (251)–RRCConnectionSetupComplete (252)–SCGFailureInformation (253)–SCPTMConfiguration (254)–SecurityModeCommand (255)–SecurityModeComplete (255)–SecurityModeFailure (256)–SidelinkUEInformation (256)–SystemInformation (258)–SystemInformationBlockType1 (259)–UEAssistanceInformation (264)–UECapabilityEnquiry (265)–UECapabilityInformation (266)–UEInformationRequest (267)–UEInformationResponse (267)–ULHandoverPreparationTransfer (CDMA2000) (273)–ULInformationTransfer (274)–WLANConnectionStatusReport (274)6.3RRC information elements (275)6.3.1System information blocks (275)–SystemInformationBlockType2 (275)–SystemInformationBlockType3 (279)–SystemInformationBlockType4 (282)–SystemInformationBlockType5 (283)–SystemInformationBlockType6 (287)–SystemInformationBlockType7 (289)–SystemInformationBlockType8 (290)–SystemInformationBlockType9 (295)–SystemInformationBlockType10 (295)–SystemInformationBlockType11 (296)–SystemInformationBlockType12 (297)–SystemInformationBlockType13 (297)–SystemInformationBlockType14 (298)–SystemInformationBlockType15 (298)–SystemInformationBlockType16 (299)–SystemInformationBlockType17 (300)–SystemInformationBlockType18 (301)–SystemInformationBlockType19 (301)–SystemInformationBlockType20 (304)6.3.2Radio resource control information elements (304)–AntennaInfo (304)–AntennaInfoUL (306)–CQI-ReportConfig (307)–CQI-ReportPeriodicProcExtId (314)–CrossCarrierSchedulingConfig (314)–CSI-IM-Config (315)–CSI-IM-ConfigId (315)–CSI-RS-Config (317)–CSI-RS-ConfigEMIMO (318)–CSI-RS-ConfigNZP (319)–CSI-RS-ConfigNZPId (320)–CSI-RS-ConfigZP (321)–CSI-RS-ConfigZPId (321)–DMRS-Config (321)–DRB-Identity (322)–EPDCCH-Config (322)–EIMTA-MainConfig (324)–LogicalChannelConfig (325)–LWA-Configuration (326)–LWIP-Configuration (326)–RCLWI-Configuration (327)–MAC-MainConfig (327)–P-C-AndCBSR (332)–PDCCH-ConfigSCell (333)–PDCP-Config (334)–PDSCH-Config (337)–PDSCH-RE-MappingQCL-ConfigId (339)–PHICH-Config (339)–PhysicalConfigDedicated (339)–P-Max (344)–PRACH-Config (344)–PresenceAntennaPort1 (346)–PUCCH-Config (347)–PUSCH-Config (351)–RACH-ConfigCommon (355)–RACH-ConfigDedicated (357)–RadioResourceConfigCommon (358)–RadioResourceConfigDedicated (362)–RLC-Config (367)–RLF-TimersAndConstants (369)–RN-SubframeConfig (370)–SchedulingRequestConfig (371)–SoundingRS-UL-Config (372)–SPS-Config (375)–TDD-Config (376)–TimeAlignmentTimer (377)–TPC-PDCCH-Config (377)–TunnelConfigLWIP (378)–UplinkPowerControl (379)–WLAN-Id-List (382)–WLAN-MobilityConfig (382)6.3.3Security control information elements (382)–NextHopChainingCount (382)–SecurityAlgorithmConfig (383)–ShortMAC-I (383)6.3.4Mobility control information elements (383)–AdditionalSpectrumEmission (383)–ARFCN-ValueCDMA2000 (383)–ARFCN-ValueEUTRA (384)–ARFCN-ValueGERAN (384)–ARFCN-ValueUTRA (384)–BandclassCDMA2000 (384)–BandIndicatorGERAN (385)–CarrierFreqCDMA2000 (385)–CarrierFreqGERAN (385)–CellIndexList (387)–CellReselectionPriority (387)–CellSelectionInfoCE (387)–CellReselectionSubPriority (388)–CSFB-RegistrationParam1XRTT (388)–CellGlobalIdEUTRA (389)–CellGlobalIdUTRA (389)–CellGlobalIdGERAN (390)–CellGlobalIdCDMA2000 (390)–CellSelectionInfoNFreq (391)–CSG-Identity (391)–FreqBandIndicator (391)–MobilityControlInfo (391)–MobilityParametersCDMA2000 (1xRTT) (393)–MobilityStateParameters (394)–MultiBandInfoList (394)–NS-PmaxList (394)–PhysCellId (395)–PhysCellIdRange (395)–PhysCellIdRangeUTRA-FDDList (395)–PhysCellIdCDMA2000 (396)–PhysCellIdGERAN (396)–PhysCellIdUTRA-FDD (396)–PhysCellIdUTRA-TDD (396)–PLMN-Identity (397)–PLMN-IdentityList3 (397)–PreRegistrationInfoHRPD (397)–Q-QualMin (398)–Q-RxLevMin (398)–Q-OffsetRange (398)–Q-OffsetRangeInterRAT (399)–ReselectionThreshold (399)–ReselectionThresholdQ (399)–SCellIndex (399)–ServCellIndex (400)–SpeedStateScaleFactors (400)–SystemInfoListGERAN (400)–SystemTimeInfoCDMA2000 (401)–TrackingAreaCode (401)–T-Reselection (402)–T-ReselectionEUTRA-CE (402)6.3.5Measurement information elements (402)–AllowedMeasBandwidth (402)–CSI-RSRP-Range (402)–Hysteresis (402)–LocationInfo (403)–MBSFN-RSRQ-Range (403)–MeasConfig (404)–MeasDS-Config (405)–MeasGapConfig (406)–MeasId (407)–MeasIdToAddModList (407)–MeasObjectCDMA2000 (408)–MeasObjectEUTRA (408)–MeasObjectGERAN (412)–MeasObjectId (412)–MeasObjectToAddModList (412)–MeasObjectUTRA (413)–ReportConfigEUTRA (422)–ReportConfigId (425)–ReportConfigInterRAT (425)–ReportConfigToAddModList (428)–ReportInterval (429)–RSRP-Range (429)–RSRQ-Range (430)–RSRQ-Type (430)–RS-SINR-Range (430)–RSSI-Range-r13 (431)–TimeToTrigger (431)–UL-DelayConfig (431)–WLAN-CarrierInfo (431)–WLAN-RSSI-Range (432)–WLAN-Status (432)6.3.6Other information elements (433)–AbsoluteTimeInfo (433)–AreaConfiguration (433)–C-RNTI (433)–DedicatedInfoCDMA2000 (434)–DedicatedInfoNAS (434)–FilterCoefficient (434)–LoggingDuration (434)–LoggingInterval (435)–MeasSubframePattern (435)–MMEC (435)–NeighCellConfig (435)–OtherConfig (436)–RAND-CDMA2000 (1xRTT) (437)–RAT-Type (437)–ResumeIdentity (437)–RRC-TransactionIdentifier (438)–S-TMSI (438)–TraceReference (438)–UE-CapabilityRAT-ContainerList (438)–UE-EUTRA-Capability (439)–UE-RadioPagingInfo (469)–UE-TimersAndConstants (469)–VisitedCellInfoList (470)–WLAN-OffloadConfig (470)6.3.7MBMS information elements (472)–MBMS-NotificationConfig (472)–MBMS-ServiceList (473)–MBSFN-AreaId (473)–MBSFN-AreaInfoList (473)–MBSFN-SubframeConfig (474)–PMCH-InfoList (475)6.3.7a SC-PTM information elements (476)–SC-MTCH-InfoList (476)–SCPTM-NeighbourCellList (478)6.3.8Sidelink information elements (478)–SL-CommConfig (478)–SL-CommResourcePool (479)–SL-CP-Len (480)–SL-DiscConfig (481)–SL-DiscResourcePool (483)–SL-DiscTxPowerInfo (485)–SL-GapConfig (485)。

GP-error-message

This section explains the messages that appear when an error has occurred in the GP unit during RUN mode. The origin of the problem behind each error message is explained with appropriate ways of disposing of the error.After a problem has been solved, unplug the GP's power cable and then reattach it.1. Error Message ListThe error messages listed below appear on the GP unit. Instructions on how to find and solve problems causing these error messages are explained on the following pages.• SYSTEM ERROR• ILLEGAL ADDRESS IN SCREEN DATA• UNSUPPORTED TAG IN SCREEN DATA• PLC NOT CONNECTED (02:FF) and (02:F7)• PLC NOT RESPONDING (02:FE)• RECEIVE DATA ERROR (02:FD)• PLC COM. ERROR• SCREEN MEMORY DATA IS CORRUPT• CLOCK SETUP ERROR• SCREEN TRANSFER ERROR• SCREEN TAG LIMIT EXCEEDED• OBJ. PLC HAS NOT BEEN SETUP• GP STATION NO. DUPLICATION ERROR (02:F9)• NETWORK ADDRESS ERROR (02:F8)If there is more than one error, the GP displays the error message for the lasterror detected.2. Error Messages—DetailsSYSTEM ERRORIndicates a fault in the basic operations of the GP.Following the error message, an error code, as shown, will appear. Report theerror number, and details on how the error developed, to your local GP dis-tributor. .• SYSTEM ERROR ( 03 : x x )Displays when a PC transferred file cannot be rebuilt.03 : x xError No.Constant V alue• SYSTEM ERROR ( x x x : x x x : x x x )Displays in RUN mode when a file cannot be rebuilt.x x x : x x x : x x xError No. 3Error No. 2Error No. 1• OFFLINE mode displays during RUN modeWhen the GP changes to OFFLINE mode without pressing the screen, there isa possibility that the screen data has been damaged. When the screen data isdamaged, after the SYSTEM ERROR displays, the screen automatically revertsto OFFLINE mode after about 10 seconds. Run the INITIALIZE MEMORY com-mand and transfer the GP screen data again from your PC.ILLEGAL ADDRESS IN SCREEN DATACaused by an overlap of addresses.Following the error message, error codes, as listed below, appear. If the errorcannot be fixed, please report the error code and details on how the error de-veloped to your local GP distributor.ILLEGAL ADDRESS IN SCREEN DATA ( 0 0 B : x x x : x x x )Error No. 2Error No. 1(See Table on next page)Overlapping Addresses TableOverlapping addresses, other than the ones mentioned above, can also cause the Illegal Address message.E.g. When the starting address of the System Data Area is set to100, and the tag below is setup:The N-tag is set to 32 bits, meaning it uses two word addresses. Since the first address is 99, the second address must be 100. Address 100 is ineligible for use since it has already been used for the System Data Area.UNSUPPORTED TAG IN SCREEN DATAA list of tag(s) in use that are unsupported by the current GP version appear with this error message. Setup the tags to correspond with the GP .Tag Reference Manual .PLC NOT CONNECTED (02:FF) (02:F7)Displays when communication with the PLC has stopped for over 60 seconds,when there is a transmission timeout error, or when there is excess noise .Check the correspondence cable wiring and connect correctly.*1 For details about the T-File (trend graph) and A-File (alarm messages),Tag Reference Manual .Error 1 Error 2 Meaning0C1191 All or part of the T-File or S-tag address rangeoverlap the addresses of System Data Area.1921930C2194 All or part of the System Data Area address, A-File, or S-tag address range overlap theaddresses setup in a T-File.1951960C3197 All or part of the T-File, or the S-tag or K-tag address range overlap the address range set in an A-file.1981990C9 19B All or part of the T-File, or the S-tag or K-tag address range overlap the address range set inan A-file.*1*1*1*1PLC NOT RESPONDING (02:FE)Displays when there is a Reply Timeout Error, or when there is excess noise. The origin of the problem and the matching solutions are listed in the table below.RECEIVE DATA ERROR (02:FD)This problem arises as a result of one of these three:• There is a problem in trying to receive the data• The connected PLC and the PLC setup for the data is different• NoiseThese errors, except for noise, appear when the Communication Cable is pulled out when the GP unit is On, or when normal communication operations are being run, but the GP has been powered Off, then back On. To solve the problem, simply begin running transmissions again.When the error is a result of noise, correct any improper connections.GP STATION NO. DUPLICATION ERROR (02:F9)This error appears for one of two reasons:• The GP number is same as the station number for another GP. Check all the GP station numbers.• In the middle of correspondences, the PLC power has been turned On/ Off. Reset the power on the PLC and GP.NETWORK ADDRESS ERROR (02:F8)The SIO address setup for the GP is different from other GP's. Check the address setup for all the GP's.PLC COM. ERRORAppears when the address setup for tags exceeds the address range on the host side. Check the Error Number that appears and use the following table to solve the problem.PLC COM. ERROR ( 02 : x x )• Disregard the above table if Error Number 51 appears and you are using a PLC other than Fuji Electric. Look up the error contents in your PLC manual and follow the instructions therein.• Disregard the above table if Error Number 53 appears and you are using a PLC other than Matsushita Electronics. Look up the error contents in your PLC manual and follow the instructions therein.• In Hitachi's HIDIC H (HIZAC H) Series, the error code is divided into 2 bytes, whereas the GP Error Number is composed of 1 byte codes.E.g. Reply Return DisplayCommand Code Error No.When the displayed error number is 8*, or 5*, use only the left column as the error number.• In Toshiba's PROSEC T Series, the Error Code is 4 places long; on the GP, Error Numbers are displayed and changed into Hexadecimal.E.g.SCREEN TRANSFER ERRORDisplays when an error occurs in the data transmission from the screen editor to the GP panel. Try re-transmitting the screen data.SCREEN TAG LIMIT EXCEEDED (max 256)When tags are setup beyond the tag limit, these tags are made invalid. Tags are invalidated from the end tag, in the opposite order in which they were registered. Plus, when tags involve registered Windows and loaded screens, they are invalidated in this order: Window Registry, Load Screen. Further details for when multiple displays are set to one screen:1.Invalidate registered windows from the end screen.2.Invalidate loaded screens from the end screen.Check invalidated tags and reduce the tag number.OBJ. PLC HAS NOT BEEN SETUP(02:F9)The host PLC setup in SOFTWARE's does not match the PLC in use. Use the Error Code that follows the error message to select the proper PLC type in the GP and correct the INITIALIZE setup.OBJ. PLC HAS NOT BEEN SETUP ( x x )The PLC number (Hexadecimal)written to the System File(See next page's Table)PLC #PLC TYPE PLC#PLC TYPE0 SYSMAC - C 20 SIEMENS S5 135-1151 MELSEC - AnN (Link) 21 SIEMENS S5 3964(R) protocol2 NEW SATELLITE JW 22 Allen Bradley PLC-53FA500(for GP-PRO/PB3:FACTORY ACE)28 Allen Bradley SLC5004 MICREX-F 63FA500M 1:n SIO (for GP-PRO/PB3: FACTORY ACE 1:n)6 TOYOPUC-PC2 66 GE FANUC 90SNP7 MEWNET-FP 67 HIZAC EC8 HIDIC-S10 68 IDEC 19 Memocon-SC 69 IDEC 2B MELSEC-AnA (LINK) 6A IDEC3D SYSMAC-CV 6B FANUC Power MateE PROSEC EX2000 6C MICRO310 HIZAC H 81 MELSEC-AnN (CPU)11 MELSEC-FX 8B MELSEC-AnA (CPU)12 MELSEC-F2 0C KOSTAC SR21/2214 KOSTAC SG8 6D KEYENCE15 PROSEC T 1C MELSEC - QnA(Link)4D MEMORY LINK(SIO Type)1D MELSEC-QnA (CPU)18 FLEX-PC 6F FLEX-PC(CPU) 1B TC200 6E SELMART1F SIEMENS S5 90-115。

MASM错误代码

L=8 A2047 unexpected character character in string hexa-escape-sequence The hexa-escape sequence contains an unexpected character. Hexa-escape sequences can contain digits 0-9 and/or letters A-F. Examples of correct hexa-escape sequences are: \xa, or \xD9. A2048 illegal bundle brace in automatic mode IAS encountered a curly bracket ({) or (}) while in automatic assembly mode. Automatic mode was specified with the .auto directive. A2049 relocatable expressions based on symbolssymbol and symbol from different sections cannot be subtracted These relocatable expressions are from different sections. To subtract two relocatable expressions, they must originate in the same section. A2050 cannot subtract relocatable expressions based on an external or common symbol To subtract two relocatable expressions, they must be based on symbols defined in the same section. One or both of these relocatable expressions is probably based on an external or common symbol. A2051 wrong operand parenthesis structure

critical error message

critical error messageCritical Error MessageA critical error message is a type of computer error message that indicates a serious problem has occurred. It usually appears when a program or system isunable to continue running due to a problem with the hardware, software, or system configuration.When a critical error message appears, it is important to take action immediately. Depending on the type of error, the system may be unable to continue running, orit may be able to continue running but with limited functionality. In either case, the user should take steps to identify and resolve the issue as soon as possible.The first step is to identify the source of the error. This can be done by looking at the error message itself, as it often contains information about the source of the problem. If the error message does not provide enough information, the usercan use diagnostic tools to help identify the source of the error.Once the source of the error has been identified, the user should take steps to resolve the issue. This may involve updating the software or system configuration, replacing hardware components, or reinstalling the operating system.If the issue cannot be resolved, the user should contact the manufacturer or a qualified technician for assistance. It is important to provide as muchinformation as possible about the error, including the error message, the system configuration, and any other relevant information.In some cases, a critical error message may indicate a serious problem with the system that cannot be resolved. In these cases, the user should back up any important data and consider replacing the system.In conclusion, a critical error message is a type of computer error message that indicates a serious problem has occurred. It is important to take action immediately when a critical error message appears, as the system may be unable to continue running or may be able to continue running but with limited functionality. The user should identify the source of the error and take steps to resolve the issue, or contact the manufacturer or a qualified technician for assistance.。

marshmallow error message

marshmallow error message在程序开发中，错误信息扮演着重要的角色，可以帮助用户识别问题所在，同时也为程序员提供了调试的重要信息。

然而，有些错误信息的表现形式可能不够友好，其中著名的“marshmallow error message”（棉花糖错误信息）就是一例。

什么是“marshmallow error message”？“marshmallow error message”指的是一种长长的、无法拆分的错误提示文本，通常是由于数据输入错误而引发。

与一般的错误提示相比，这种错误提示不仅难以懂，同时也难以判断出问题所在，为用户造成了极大的困扰和不便。

如何避免“marshmallow error message”？1. 尽量详细地描述错误信息在编写错误信息时，应尽量详细地描述错误的原因和解决方案。

保证错误信息充分传递，使用户能够轻松地理解问题所在，并且能够迅速解决问题。

2. 简洁明了错误信息的语言应该是简洁明了的，避免使用过于复杂的词汇或术语，尽量使用普通用户能够理解的语言来表述错误信息。

3. 提供有效的解决方案在错误提示中，应该提供有效的解决方案，比如提供操作步骤或指南，或者提供其他的帮助信息，以帮助用户完全解决问题。

4. 清晰可见错误信息的字体应该足够大，颜色和背景色应该选择和谐的组合，以清晰地呈现错误信息。

5. 反馈和记录对于多次出错的操作，应该记录下用户的反馈，并且将错误信息反馈给开发者，以便在下一个版本中进行改进和优化。

总结“marshmallow error message”不仅会导致用户无法理解错误信息，也可能影响用户的使用体验。

因此，在程序开发中，应该尽可能避免这种错误提示的出现，同时采取有效的措施，使得错误提示更加友好，用户可以轻松理解并且解决相关问题。

Code Home Edition Error Messages

Code Home Edition Error Messages0 操作成功完成。

1 函数不正确。

2 系统找不到指定的文件。

3 系统找不到指定的路径。

4 系统无法打开文件。

5 拒绝访问。

6 句柄无效。

7 存储控制块被损坏。

8 存储空间不足，无法处理此命令。

9 存储控制块地址无效。

10 环境不正确。

11 试图加载格式不正确的程序。

12 访问码无效。

13 数据无效。

14 存储空间不足，无法完成此操作。

15 系统找不到指定的驱动器。

16 无法删除目录。

17 系统无法将文件移到不同的磁盘驱动器。

18 没有更多文件。

19 媒体受写入保护。

20 系统找不到指定的设备。

21 设备未就绪。

22 设备不识别此命令。

23 数据错误(循环冗余检查)。

24 程序发出命令，但命令长度不正确。

25 驱动器找不到磁盘上特定区域或磁道。

26 无法访问指定的磁盘或软盘。

27 驱动器找不到请求的扇区。

28 打印机缺纸。

29 系统无法写入指定的设备。

30 系统无法从指定的设备上读取。

31 连到系统上的设备没有发挥作用。

32 另一个程序正在使用此文件，进程无法访问。

33 另一个程序已锁定文件的一部分，进程无法访问。

36 用来共享的打开文件过多。

38 已到文件结尾。

39 磁盘已满。

50 不支持请求。

51 Windows 无法找到网络路径。

请确认网络路径正确并且目标计算机不忙或已关闭。

如果Windows 仍然无法找到网络路径，请与网络管理员联系。

52 由于网络上有重名，没有连接。

若要加入到域，请到“控制面板”中的“系统”更改计算机名，然后重试。

如果加入工作组，请选择其他工作组名。

53 找不到网络路径。

54 网络很忙。

55 指定的网络资源或设备不再可用。

56 已达到网络BIOS 命令限制。

57 网络适配器硬件出错。

58 指定的服务器无法运行请求的操作。

59 出现了意外的网络错误。

60 远程适配器不兼容。

61 打印机队列已满。

62 服务器上没有储存等待打印的文件的空间。

selfregistration error -回复

selfregistration error -回复self-registration error是指在自助注册过程中发生的错误。

自助注册是指用户可以通过填写表格或在网站上输入个人信息来创建一个新的账号或会员账号。

然而，在这个过程中可能会出现各种错误，从缺失数据到技术故障，都可能导致self-registration error的发生。

文章将从以下几个方面回答self-registration error的不同原因和对应的解决方法：第一部分：self-registration error的概述（100-200字）第二部分：常见的self-registration error（600-800字）2.1 缺失数据2.2 数据格式错误2.3 技术问题2.4 安全性问题第三部分：解决self-registration error的方法（600-800字）3.1 界面设计和指导3.2 数据验证和完整性检查3.3 技术支持和24小时在线帮助3.4 安全认证和防止欺诈行为第四部分：结论（100-200字）第一部分：self-registration error的概述在互联网时代，自助注册已经成为了用户创建新账号的主要方式之一。

然而，自助注册过程中常常会出现各种错误，使得用户无法成功注册。

这些错误可能是由于缺失数据、数据格式错误、技术问题以及安全性问题等导致的。

为了提高自助注册的效率和用户体验，解决self-registration error 变得尤为重要。

第二部分：常见的self-registration error2.1 缺失数据一个常见的self-registration error是用户在注册时漏掉了一些必填的数据。

这可能是因为用户没有注意到这些字段是必填的，或者是由于界面设计不友好而导致用户忽略了这些字段。

例如，许多注册表格中必须填写的字段包括姓名、邮箱地址和密码等。

当用户漏填了这些字段时，系统将无法成功注册账号。

AMM error处理方法

第一步：点击需要加入群集的主机，点击【配置】---【DNS和路由】---【属性】：
第二步：在【域】中随便输入域名，不存在的域名也可以，但是在DNS服务器中需要输入真实DNS的IP地址：
第三步：用ssh工具使用root登陆，保证在集群中主机的hosts文件一致，如下图红色部分，解释如下：
10.250.65.20 ：表示该esx主机的IP地址
JYESX01.jylcm.local：表示完全的FQDN域名，jylcm.local可以随意配置，但是要和上面的域保持一致。

JYESX01 ：表示主机的机器名
[root@JYESX01 ~]# cat /etc/hosts
127.0.0.1 localhost
::1 localhost
10.250.65.20 JYESX01.jylcm.local JYESX01
10.250.65.21 JYESX02.jylcm.local JYESX02
10.250.65.22 JYESX03.jylcm.local JYESX03
第四步：由于vmware配置HA必须要互相可以解析对方才可以，需要保证两台主机可以互相解析，否则就会出现：
HA agent has an error : cmd addnode failed for primary node: Internal AAM Error - agent could not start. : Unknown HA error.。

E-Prime常见错误代码表

Set the value of Channels to 1 or2 to match the format of the WAVfile. All files must be saved usingthe same format
18013
The value forSamplesPerSecond isinvalid
Set the value of BitsPerSampleto 8 or 16 to match the format ofthe WAV file. All files must besaved using the same format.
18012
The value for Channels isinvalid
An object was named in the interface with a value thatcontains an invalid character. E-Object names aregenerated to E-Basic script, which does not permitvariable names to have invalid characters. An objectname can only contain A-Z, a-z, 0-9
The Channels field of the Sound device (ExperimentObject; Devices tab) represents a value that is notvalid. Valid values are 1 for mono and 2 for stereo.
An error occurred while attempting to load a sound file.This can be due to file not found, file already open,lack of resources, invalid configuration, or improperdriver.

ISO 11992-4-2005

ICS 43.040.15 Ref. No. ISO 11992-4:2005/Cor.1:2006(E)© ISO 2006 – All rights reservedPublished in SwitzerlandINTERNATIONAL STANDARD ISO 11992-4:2005TECHNICAL CORRIGENDUM 1Published 2006-05-15INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATIONRoad vehicles — Interchange of digital information on electrical connections between towing and towed vehicles —Part 4:DiagnosticsTECHNICAL CORRIGENDUM 1Véhicules routiers — Échange d'informations numériques sur les connexions électriques entre véhicules tracteurs et véhicules tractés —Partie 4: DiagnosticsRECTIFICATIF TECHNIQUE 1Technical Corrigendum 1 to ISO 11992-4:2005 was prepared by Technical Committee ISO/TC 22, Road vehicles , Subcommittee SC 3, Electrical and electronic equipment.ISO 11992-4:2005/Cor.1:2006(E)Page 6, subclause 5.4.3Replace Figure 3 with the following:Figure 3 — Client service state diagram — Service request with physical server target address2 ©ISO 2006 – All rights reservedISO 11992-4:2005/Cor.1:2006(E)Page 24, subclause 6.4.6Replace Figure 5 with the following:Figure 5 — A_PDU timing diagram confirmed services — physical target address©ISO 2005 – All rights reserved3ISO 11992-4:2005/Cor.1:2006(E)Page 25, subclause 6.4.6Replace Figure 6 with the following:Figure 6 — A-PDU timing diagram confirmed services — functional target address4 ©ISO 2006 – All rights reservedReference numberISO 11992-4:2005(E)© ISO 2005INTERNATIONALSTANDARD ISO 11992-4First edition2005-07-15Road vehicles — Interchange of digitalinformation on electrical connectionsbetween towing and towed vehicles —Part 4:DiagnosticsVéhicules routiers — Échange d'informations numériques sur lesconnexions électriques entre véhicules tracteurs et véhicules tractés —Partie 4: DiagnosticsISO 11992-4:2005(E)PDF disclaimerThis PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area.Adobe is a trademark of Adobe Systems Incorporated.Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.© ISO 2005All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.ISO copyright officeCase postale 56 • CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyright@Web Published in Switzerlandii © ISO 2005 – All rights reservedISO 11992-4:2005(E)Contents PageForeword (iv)Introduction (v)1Scope (1)2Normative references (1)3Terms and definitions (1)4Syntax applied (2)5Diagnostic application specification (2)5.1General (2)5.2Basic diagnostics (2)5.3Enhanced diagnostics (3)5.4Client and server state diagrams (3)6Application layer specification (7)6.1General (7)6.2Application layer functions (7)6.3Application layer services (10)6.4Application layer protocol (22)7Presentation layer specification (27)8Session layer specification (27)9Transport layer specification (27)10Network layer specification (27)10.1General (27)10.2Network layer functions (27)10.3Network layer services (30)10.4Network layer protocol (34)11Data link layer specification (42)11.1General (42)11.2Data link layer service parameter (42)12Physical layer specification (43)Annex A (normative) Addresses (44)Annex B (normative) Basic diagnostic service parameters (46)Annex C (informative) Trailer message routing example (65)Annex D (normative) CAN identifier and frame format (67)Bibliography (68)© ISO 2005 – All rights reserved iiiISO 11992-4:2005(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote.Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights.ISO 11992-4 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment.ISO 11992 consists of the following parts, under the general title Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles:⎯Part 1: Physical and data-link layers⎯Part 2: Application layer for brakes and running gear⎯Part 3: Application layer for equipment other than brakes and running gear⎯Part 4: Diagnosticsiv © ISO 2005 – All rights reservedISO 11992-4:2005(E)© ISO 2005 – All rights reserved vIntroductionISO 11992 has been established in order to define the data interchange between road vehicles and their towed vehicles using a Controller Area Network (CAN) serial data link as specified in ISO 11898[4].The description of this part of ISO 11992 is based on the Open Systems Interconnection (OSI) Basic Reference Model in accordance with ISO/IEC 7498[2] (and ISO/IEC 10731[3]), which structures communication systems into seven layers.When mapped on this model, the communication system specified by ISO 11992 is broken down into: Layer 7Application layer for brakes and running gear.Application layer for equipment other than brakes and running gear.Application layer for diagnostics.Layer 3Network layer for diagnostics.Layer 2Data link layer for all communication types.Layer 1Physical layer for all communication types.Table 1 — Applicability and relationship between International Standards Normal communication Diagnostic communication Applicability Brakes and running gearEquipment other than brakes and running gear All applications Layer 7: Application layer ISO 11992-2ISO 11992-3 ISO 11992-4 ISO 14229-1 Layer 6: Presentation layer No functions specified for this layer.Layer 5: Session layer No functions specified for this layer.Layer 4: Transport layer No functions specified for this layer.Layer 3: Network layer No functions specified for this layer.ISO 11992-4 ISO 15765-2 Layer 2: Data link layer ISO 11992-1Layer 1:Physical layerISO 11992-1INTERNATIONAL STANDARD ISO 11992-4:2005(E) Road vehicles — Interchange of digital information on electricalconnections between towing and towed vehicles —Part 4:Diagnostics1 ScopeThis part of ISO 11992 specifies the data communication for diagnostic purposes on a serial data link between a road vehicle and its towed vehicle(s).This part of ISO 11992 is applicable to road vehicles of a maximum authorized total mass greater than 3 500 kg.2 Normative referencesThe following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signallingISO 11992-1, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 1: Physical and data-link layersISO 11992-2, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 2: Application layer for brakes and running gearISO 11992-3, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 3: Application layer for equipment other than brakes and running gearISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements ISO 15765-2, Road vehicles — Diagnostics on Controller Area Networks (CAN) — Part 2: Network layer services3 Terms and definitionsFor the purposes of this document, the terms and definitions given in ISO 11992-1, ISO 14229-1 and ISO 15765-2 apply.© ISO 2005 – All rights reserved1ISO 11992-4:2005(E)4 Syntax appliedFor the description of services and service parameters of this part of ISO 11992, the following syntax is used: Name: Type Parameter name and type specificationName Mandatory parameter value<Name> Parameter name representing a set of mandatory parameter values [Name] Optional parameter value[<Name>] Parameter name representing a set of optional parameter values{Name 1;Name 2} List of mandatory parameter values{<Name 1>;<Name 2>} List of parameter names representing sets of mandatory parameter values [<Name 1>;<Name 2>] List of parameter names representing sets of optional parameter values{<Name 1>|<Name 2>} Parameter names selection list representing sets of mandatory parameter values[<Name 1>|<Name 2>] Parameter names selection list representing sets of optional parameter valuesName.req Service request primitiveName.ind Service indication primitiveName.rsp Service response primitiveName.rsp- Service negative response primitiveName.rsp+ Service positive response primitiveName.con Service confirmation primitiveName.con- Service negative confirmation primitiveName.con+ Service positive confirmation primitive5 Diagnostic application specification5.1 GeneralThe diagnostic applications are divided into basic diagnostic applications and enhanced diagnostic applications.Functions, services and protocols of the layers 1 to 4 shall be identical for basic diagnostics and enhanced diagnostics.5.2 Basic diagnosticsThe purpose of the basic diagnostics is to provide vehicle-independent identification and diagnostic information.All basic diagnostic functions and services shall be provided under all operation conditions in the default diagnostic session without the need for specific access rights.2 © ISO 2005 – All rights reservedISO 11992-4:2005(E)5.3 Enhanced diagnosticsThe support and the conditions under which enhanced diagnostic functions and services are provided are manufacturer-specific. It is the responsibility of the manufacturer to secure a server against unauthorized access and to guarantee performance and safe operation in all operation modes allowing enhanced diagnostics.5.4 Client and server state diagrams5.4.1 GeneralThe client and server state diagrams describe the diagnostic service processing of the client and server application entity.5.4.2 Client service primitives handlingThe client service primitives handling shall be as specified in Figure 1 and Figure 2.Client states while processing a diagnostic service shall be as specified in Table 2, events resulting in a client state change shall be as specified in Table 3.Figure 1 — Client service state diagram — Service request with physical server target address© ISO 2005 – All rights reserved3ISO 11992-4:2005(E)4© ISO 2005 – All rights reservedFigure 2 — Client service state diagram — Service request with functional server target addressTable 2 — Client state description Client state Description ASAny client state in which a service request can take place. WS Client state while waiting for a confirmation from the server.NCS a) Following a service request with a physical server target address:client state after the reception of a negative confirmation from the server.b) Following a service request with a functional server target address:client state if no positive service confirmation has been received.PCS Client state after the reception of a positive confirmation from a server.ESClient state for error handling, e.g. in case of a time out condition.ISO 11992-4:2005(E)© ISO 2005 – All rights reserved 5Table 3 — Client event description Client eventDescription Tas1.1Transmit <a.>.req The client transmits an <a> service request with a physical server target address. Tas1.2 Transmit <a.>.req The client transmits an <a> service request with a functional server target address.Tws1.1 Receive <a>.con- Following a service request with a physical server target address:the client receives a negative <a> service confirmation with the response code 'Request correctly received - response pending'.The client shall then reset the time outs and enter the WS state again.Tws1.2 Receive <a>.con+ Following a service request with a functional server target address:the client receives a positive <a> service confirmation. The client shall then process the positive service confirmation and enter the WSstate again.Tws2.1 Receive <a>.con- Following a service request with a physical server target address:the <a> service request has been rejected, a corresponding negative <a> service confirmation with a response code has been received.The client shall then change to the NCS state.Tws2.2 ACT1 expiredFollowing a service request with a functional server target address:the time ACT1 for the reception of the first service confirmation has expired andno positive service confirmation has been received.The client shall then change to the NCS state. Tws3.1 Receive <a>.con+ Following a service request with a physical server target address:the <a> service has been executed, a positive <a> service confirmation, i.e. the result of the service, has been received.The client shall then change to the PCS state.Tws3.2 ACT3.2 expired Following a service request with a functional server target address the time ACT3.2for the reception of consecutive service confirmations has expired and at least one positive service confirmation has been received.The client shall then change to the PCS state.Tes1 Error.ind An error condition, e.g. a time out condition, is signalled to the client.The client shall then change to the ES state for error handling.NOTE Negative service responses with a response code 1016, 1116 or 1216 shall not be sent by a server in case of a service request with a functional server target address.<a> Any diagnostic service.5.4.3 Server service primitives handlingThe server diagnostic service primitives handling shall be as specified in Figure 3.Server states while processing a diagnostic service shall be as specified in Table 4, events resulting in a server state change shall be as specified in Table 5.Table 4 — Server state descriptionServer stateDescription ASAny server state in which the reception of a service indication can take place. PSServer state while processing a service. PCSServer state after the diagnostic service has been executed. ES Server state error handling, e.g. after reaching a time out condition.ISO 11992-4:2005(E)Figure 3 — Server state diagram6 © ISO 2005 – All rights reservedISO 11992-4:2005(E)© ISO 2005 – All rights reserved 7Table 5 — Server event description Event Description Tas1Receive <a.>.ind The server receives any <a> service.indication. Tws1 AST1max expiredTransmit <a>.res- The service execution time AST1max has expired. the server shall then send a negative service response with the response code 'Request correctly received - response pending' and change back to the PS state to proceed the service execution.Tws2 Received .indRespond .res± The server receives a service indication, while service <a> is in progress.the server shall reject the service if service ≠ service <a> and send a negative response with response code "Busy - Repeat Request". If service =service <a>, the server shall send a negative service response with response code"Request Correctly Received - Response Pending".The server shall then enter again the PS state to proceed the service execution.Tws3.1 Service execution not completed Respond <a>.res- Following a service request with a physical server target address:the server rejects the service request.The server shall then send a negative <a> service response with a correspondingresponse code and change to the AS state.Tws3.2 Service execution not completed No response Following a service request with a functional server target address:the server rejects the service request.The server shall then send no response code and change to the AS state.Tws4 Service execution completed Respond <a>.res+ The server sends a positive <a> service response.the service has been executed.The server shall then transmit a positive <a> service response, i.e. the serviceresults, and shall change again to the PCS state.Tes1 Error.indAn error condition is indicated to the server, e.g. a time out condition.The server changes to the ES state for error handling. NOTE Negative service responses with a response code 1016, 1116 or 1216 shall not be sent by a server in case of a service request with a functional server target address.<a> Any first diagnostic service. Any second diagnostic service.6 Application layer specification6.1 GeneralThe application layer function, service and protocol specifications comply with ISO 14229-1. In case of differences, the specifications of this part of ISO 11992 shall have precedence.For the diagnostic communication between road vehicles and their towed vehicles, the restrictions described in this clause apply additionally.6.2 Application layer functions6.2.1 GeneralThe application layer provides functions for the execution of the vehicle diagnostics. These functions are used by client and server applications requesting the respective application layer services.6.2.2 Processing of diagnostic services requests and responsesDiagnostic service requests from the client application and diagnostic service responses from the server application shall be processed according to the service identifier. The diagnostic data shall be encoded as an application layer protocol data unit (A_PDU). The A_PDU shall be transmitted to the respective application layer peer entity by requesting services of the layers beneath the application layer.ISO 11992-4:2005(E)6.2.3 Processing of diagnostic service indications and confirmationsDiagnostic data shall be received as an A_PDU from the layers beneath the application layer. If the received A_PDU is addressed to one of the local server or client application, the received A_PDU shall be decoded and processed according to the diagnostic service identifier and delivered to the server or client application as a service indication or confirmation.6.2.4 Determination of network layer service parametersNetwork layer service parameters are determined by the application layer service type, i.e. ClientIdentifier, ServerIdentifier, ServiceIdentifier and ServiceParameter. In addition the specified parameters Priority and ReservedBit shall be used.NOTE As no specific functions have been specified for the presentation, session and transport layer, the PDUs of these layers are identical to the respective application layer PDUs.6.2.5 Application layer protocol timing supervisionThe peer application layer entities communicating shall supervise the specified timing and shall take the respective actions in case a specified time out expires.6.2.6 Server and client addressing6.2.6.1 Vehicle network architectureTowed vehicle server and client applications shall be addressed and identified by means of remote network addressing. The physical sub-networks between towing and towed vehicles are part of the local motor vehicle network and share the same address range. The address type of the target address (TA) and of the remote address (RA) in the case of encoding a remote target address shall be identified by the target address type (TA_Type).Figure 4 shows an example of the vehicle network architecture.Figure 4 — Vehicle network architecture example8 © ISO 2005 – All rights reservedISO 11992-4:2005(E)6.2.6.2 Towing to towed vehicle <Service>.Request and <Service>.IndicationFor a diagnostic service request transmitted from a towing vehicle to a towed vehicle, the address parameters of the service primitives have the following meaning:SA = <Towing vehicle client source address>TA = <Towed vehicle target address>RA = <Towed vehicle remote server target address>TA_type = {<Physical target addresses>|<Functional target addresses>}See Annex A.NOTE TA_type identifies the TA and the RA target address type.6.2.6.3 Towed to towing vehicle <Service>.Response and <Service>.ConfirmationFor a diagnostic service response transmitted from a towed vehicle to a towing vehicle, the address parameters of the service primitives have the following meaning:SA = <Towed vehicle source address>TA = <Towing vehicle client target address>RA = <Towed vehicle remote server source address>TA_type = <Physical target addresses>NOTE TA_type identifies only the TA target address type.6.2.6.4 Towed to towing vehicle <Service>.Request and <Service>.IndicationFor a diagnostic service request transmitted from a towed vehicle to a towing vehicle, the address parameters of the service primitives have the following meaning:SA = <Towed vehicle source address>TA = <Towing vehicle server target address>RA = <Towed vehicle remote client source address>TA_type = {<Physical target addresses>|<Functional target addresses>}NOTE TA_type identifies only the TA target address type.© ISO 2005 – All rights reserved9ISO 11992-4:2005(E)6.2.6.5 Towing to towed vehicle <Service>.Response and <Service>.ConfirmationFor a diagnostic service response transmitted from a towing vehicle to a towed vehicle, the address parameters of the service primitives have the following meaning:SA = <Towing vehicle server source address>TA = <Towed vehicle target address>RA = <Towed vehicle remote client target address>TA_type = <Physical target addresses>NOTE TA_type identifies the TA and RA target address type.6.3 Application layer services6.3.1 GeneralThis subclause specifies the application layer services for diagnostics.6.3.2 Application layer service parameters6.3.2.1 GeneralThis subclause specifies the general application layer service parameter and the respective parameter format. Service specific parameters are specified in 6.3.4.6.3.2.2 Source address (SA)The parameter source address (SA) contains the client or server source address. It represents the physical location of a client or server on the local network.SA = {<Towing vehicle client source address>|<Towed vehicle source address>}6.3.2.3 Target address (TA)The parameter target address (TA) contains the client or server target address. It represents the physical location of a client or server or a functional group of servers on the local network. The target address type is determined by the parameter TA_type.TA = {<Towed vehicle target address>|<Towing vehicle client target address>|<Towing vehicle server target address>}6.3.2.4 Target address type (TA_type)The parameter target address type (TA_type) determines the address type of the target address TA and the remote address RA, in the case that the remote address corresponds to a target address.TA_type = {<Physical target addresses>|<Functional target addresses>}10 © ISO 2005 – All rights reserved6.3.2.5 Remote address (RA)The remote address (RA) contains the remote addresses of servers or clients on a remote network. Depending on the respective application layer primitive, RA represents either a remote target address or a remote source address.RA = {<Towed vehicle remote server target address>|<Towed vehicle remote server source address>|<Towed vehicle remote client source address>|<Towed vehicle remote client target address>}6.3.2.6 ServiceParameterServiceParameter is a record which contains the respective service parameters of the service primitive. ServiceParameter = {<<Service name> request service parameter>|<<Service name> positive response service parameter>|<<Service name> negative response service parameter>}<Service name> request service parameters are those following the <service name> request service identifier. <Service name> positive response service parameters are those following the <service name> positive response service identifier.<Service name> negative response service parameters are those following the negative response service identifier.6.3.3 Application layer service data units (A_SDU)The application layer service data units (A_SDU) of the diagnostic service primitives have the following formats:<Service name>.Request = {<SA>;<TA>;<TA_Type>;<RA>;<<Service name> request service identifier>;<<Service name> request service parameter>}<Service name>.Indication = < <Service name>.Request><Service name>.Response = {<SA>;<TA>;<TA_Type>;<RA>;<<Service name> response service identifier>;<<Service name> response service parameter>}<Service name>.Confirmation = <<Service name>.Response>© ISO 2005 – All rights reserved 11。

芬达（Fadal）维修手册说明书

INDEX Numerics15/15XT 515K Air/Oil Spindle Installation 293Install Component Plumbing 297Plumbing Spindle 296Wiring Harness Installation 2952016L 122216 83016 103016L 143020 264020 164020A 184525 2850 Taper Dual Arm Tool Changer 151Alignment 163Arm Installation 161Inserting the Arm Assembly 162Installation 156Installation Notice 157Maintenance 161Sending the Tool Changer Spindle to Home Position 161 Sub-Assemblies 152Tool Changer Specifications 151Troubleshooting 1585020A 206030 226535 308030 24AAir Positive Flow System 287Air Supply 45Alternate Service 50ATC Motor Replacement Procedure 120Pulley Alignment 122Replacing the Slide Motor 121Replacing the Turret Motor on a Geneva Wheel ATC 120Replacing the Turret Motor on a Servo Turret ATC 121Turret Factor Setting 122Attached Optional Devices 325Access from Program Using Macro Statement #DISK 339Macro Statement Format 339Restrictions on File Content and Format 339Restrictions on User Defined Subroutines 340Subprograms and Fixed Subroutines ARE Allowed 340 CNC 88 HS Optional Diskette Drive 336CNC88HS Optional Diskette Drive- Miscellaneous 338Access from Control 338Requirements 338Specifications 338Diskette Drive Error Codes 340Dynamic Tool Load Compensation 332Servo Coolant Assembly 333Servo Coolant Control 334Troubleshooting Checklist 335M-Function Board Use and Setup 3251050-3A M-Function PCBA (PCB-0008) - Two M Functions. 327Fadal M Functions 326Fadal Normally Supplied M-Functions 327Fadal Optional M-Functions 327M-Function Contacts 329M-Function Hook-up 329Miscellaneous Functions (M-Codes) 325Reset Options 328U7 (Dip Switch) 328Remote Manual Pulse Generator 330Installation Procedure 331Auger 80Chip Removal from the Exit Tube 81Chip Removal from the Machine Interior 81Cleaning and Freeing Chips from the Auger Chip Removal System 80 Automatic Tool Changers 107Adjustments 114ATC Slide Belt Replacement & Adjustment 119ATC Turret Slide Adjustment 116Spring Configuration 21 & 30 Tool Changers 116Tool Turret Rotational Adjustment 118Z Axis Cold Start Adjustment 114Operation 107ATC Fault Messages 110ATC Sensors & Switch 110ATC Servo Turret Operation 111Electrical Operation 107Programming 107Servo Turret Controller and Amplifier Boards (PCB-0108) 113Tool Change Sequence 109BBall Pockets Incorrect 279Belt Drive Systems 265Motor Plate Tensioner Cable 269Posi-Drive Belt System 265CChecking Grounding Integrity of Fadal VMCs 48Inspection 49Specification 48Verification 49Chip Removal Devices 447Auger, Chip Removal System 449Daily and Weekly Safety Tests for Door Monitor 452PCB-0197 Auger Control & Door Interlock Monitor Board 1310-0C 449 Chip Conveyor 453Cause of Trouble and Corrective Action 458Chip Conveyor Power and Controls 455Installation Procedure 453Maintenance Schedule Chip Conveyor 459Observance and Inspection 457Pre-Startup Safety Inspection 456Restarting the Chip Conveyor 456Stopping the Chip Conveyor on US and CE Machines 456 HydroSweep 447Maintenance Schedule 447Circuit Breakers 50Clamp-on Ammeter Testing 490Ballscrew Alignment 491ExTech AC/DC Clamp-On Ammeter 490Gib and Gib Strap Verification 490Limit Stop Check 491CNC Controls 3051460-1 Memory Expansion Boards 320DC Power Supply 312Door Interlock Monitor Board 2000-1B (PCB-0196 312Indicators (LEDs) 313Inputs 312Operation 312Outputs 312Power 312Terminals 312Electrostatic Discharge (ESD) 306Emergency Stop Circuit Overview 313Axis Controller 1010-6 319Basic Hardware Operation DescriptionNormal Operation (No Fault) 313Basic Software Operational Description 314Configurations 316Fadal Axis Board Jumper 316Fault Condition 314Troubleshooting Tips 315Fadal’s Block Diagram 305Feedrate Potentiometer (Pot) Adjustment 321Functional Description 306Axis Controller Boards 309Boards in Motherboard or Backplane 306Boards Outside the Motherboard 311J14 310Slot 1 to 4 306Slot 10 308Slot 11 308Slot 12 308Slot 13 308Slot 14 310Slot 15 311Slot 16 311Slot 17 311Slot 5 307Slot 6 308Slot 7 308Slot 8 308Slot 9 308Master Feedrate 320PCBA Compatibility Chart 325Zero Out Memory Procedure 322Zero-out Memory 324Conduit 51Coolant Thru the Spindle 300Coolant-Thru Spindle Seal Kit Instructions 300 Determining the Leak Location 301Electrical 300Hydraulic Actuator Set-up 303Mechanical 300Coolant-Thru Drawbar Cylinder 278DDiagnostic System Commands 483DS - Display Switches 483Diagnostics 483Drawbar Cylinder Bushing 277Drawbar Cylinder Plate 277Drive Control 6 Pin Molex Connector 240Drive Ground 240Dual Arm Tool Changer 124Errors 141Installation & Testing 129Operation 137Scheduled Maintenance 150Sensors 139Set-Up 135Software & Mechanical Test 134Sub-Assemblies 125Sys 101.4 Software Update 139Tool Changer Specifications 124Tool Loading Procedures 137Troubleshooting 140EElectrical Grounding 46Primary Grounding 47Electrical Service 50Alternate Service 50Circuit Breakers 50Conduit 51Preferred Service 50Wiring 50Emergency Error Codes 530Error Numbers From the Axis or Spindle Controller 530 Error Messages 497Exhaust Valve 277Exhaust Valve Nipple 277FFadal Bolt Torque Specifications 32Foundation 41Fuses, Heaters, Parameters 627FORMAT 633GGeneral Information 461Binary Number Groupings 477Binary Numbers 475Number Systems 475 Communications Troubleshooting 463 Cables 466Computer and Computer IO Port 467Environment 463File 463Software 468VMC 464Fadal Machining Centers Serial Numbers 462 Helpful Formulas 461Conversion Factors 461Electrical References 461Expansion Coefficients 461Temperature 461Reading Status Group 477Solving the Thermal Expansion Problem 474 Ambient Sources 475Cooling Systems 475General Considerations 474Radiant Heat 475Sunlight 475Thermal Expansion 470Accuracy and Repeatability 470Ambient Temperature 472Expansion Coefficients 471Fixtures / Sub Plates 473Friction 471Heat Sources 471Machine Assemblies 473Machining Practices 472Material Differences 473Non-Uniform Expansion 473Overview 470Recognizing Thermal Expansion 470 VMC Maintenance 478Cabinet Fans 478Conclusion 481Coolant 479Coolant Through Spindle 480Cooled Ball Screws and Spindle 480Glass Scales 480Lubrication 478Machining Practices 478Monitoring Position Changes 479Probe 480Rough Cut / Cool Down / Finish Cut 479VMC Options 479Warm Up 478HHeidenhain Tester 428Hold Down Clamps 74Hydraulic Actuator Assembly Bolts 278 Hydraulic Brakes 3674th Axis Brake Check-Out 3684th Axis Brake Installation 3674th, 5th Axis Brake Check-Out 3694th, 5th Axis Brake Installation 368 Hydraulic Hi/low System 2707,500 RPM Poly Chain Belt 271Spindle Belt Replacement 271Filling 270HydroSweep 447HydroSweep Only 966-Month Planned Maintenance 97Daily Maintenance 96Each Part Cycle 96Monthly Maintenance 97Weekly Maintenance 97IIllustrations & Data for All VMC Models 1 VMC 15/15XT 5VMC 2016L 12VMC 2216 8VMC 3016 10VMC 3016L 14VMC 3020 26VMC 4020 16VMC 4020A 18VMC 4525 28VMC 5020A 20VMC 6030 22VMC 6535 30VMC 8030 24Input Three Phase Power 240Installation & Hook-Up 53Air Supply 58Moving the VMC-Crane 55Moving the VMC-Fork Lift 54Placing the VMC 56Power Check 58Unlocking Front Doors with CE Door Locks 53Unpacking 53Installation Procedures 53Inverter Wye Delta 6 Pin Molex Connector 241Inverter/Vector Drive Inputs & Outputs 240Drive Control 6 Pin Molex Connector 240Drive Ground 240Input Three Phase Power 240Inverter Wye Delta 6 Pin Molex Connector 241Load Meter Output 241Output Three Phase Power 240Vector Drive Encoder 9 pin Molex Connector 242Vector Drive with Rigid Tapping 243Inverter/Vector Drives 239LLaser Calibration-Renishaw 84Aligning the laser 88Axis Calibration 89Calibration Requirements and Limits 86Definitions 84Documentation 85Download Survey 89Laser Setup 86Laser Shut Down 93Materials and Equipment 84Procedure 84Reference Documentation 84Responsibilities 84Safety and Environmental 84Sample output from a laser measurement system. 91 Scope 84Standard Fadal Cnc88hs 85Leveling 69Box Way VMCs 69For All VMCs 69Linear Way VMCs 70Load Meter Output 241MMachine Maintenance 75Machine Parameters 6323 PHASE NO 5% LOW NO 6385TH AXIS HEAD 644A-AXIS RATIO 635AIR VALVE FEEDBACK 645A-PALLET 644ASPECT 641AT SPEED 645AUTO BRAKE 643AXES X,Y,Z 634AXIS DISPLAY 643BAUD RATE 633B-AXIS RATIO 636BINARY BUFFERS 255 640B-PALLET 644CMD MENU 640CRC MODE 639DEFAULT G0 635DEFAULT G17 636DEFAULT G90 635DEFAULT INCH 638FORMAT 633G0 DETAIL 644GAIN 641HIGH TORQUE 640IMM. FIXED CYCLE 637IPM 642M60/A-AXIS BRAKE 635M62/B-AXIS BRAKE 636M7-FLOOD M8- MIST 638N-WORDS ORDERED 639ORIENTATION FACTOR 638OVERLOAD 642PALLET 641PENDANT 634PU FORMAT 639RAMP 641RPM FACTOR 637SCREW 642SPINDLE AFTER M6 633SPINDLE OFF 640SPINDLE TYPE 637TIMERS 641TOOL CHANGER 636TOOL TABLE 639TRAVEL 634TURRET FACTOR 640VECTOR 643XYZ RAMP 642Z TAP GAIN 643Menu Diagnostics 486Menu Page 1 486Menu Page 2 488Menu Page 3 488Menu Page 4 489Menu Page 5 489Moving the VMC-Crane 55Moving the VMC-Fork Lift 54OOutput Three Phase Power 240Oversized Diameter 278PPallet Changer 431Installation of Light CurtainMirror Alignment 437Installation of Light curtain 436Installation of Pallet Changer 431Maintenance Schedule 444Operation 439Manual Operation 440M-Functions 439Pallets 439Setting the Sensor on the 1840 Board 438Purpose 438Pallet Changer/Hydro Sweep 94Daily Maintenance 94Each Part Cycle 94Monthly Maintenance 95Weekly Maintenance 94PCB-0213 Dual Arm ATC Controller Card 167Currents 169Description and Explanation of Operation of PCB-0213 (1330-0A) 167 Functional Explanations 169Inputs 167LED Indicators 168Outputs 168Phase Converter Rotary 68Positioning 44Preferred Service 50Pre-Installation Procedures 41Primary Grounding 47Probes 371MP-11 Probe 371MP-12 Probe 372TS-27 372Probes & Scales 371RRecommended Mainline Fuses / Circuit Breakers 39Rigid Tapping 260Fadal Rigid Tapping Procedure 260Rigid Tap with AC-0017 Software 262Rotary Tables 3414th Axis 341Adjusting the Cold Start 351Balancing the Amplifier 344Connecting the VH-65 Motor Cable 342Evaluating the Following Error 345FADAL RT-175 360FADAL RT-225 361FADAL RT-275 362FADAL V-300 (V-400) Rotary Table 355FADAL VH-65 & VH-5C 354Horizontal Installation Difference(s) 343Installation 342Installing the Servo Control 343Maintenance 352Pre-installation 341Remove the Rotary Table from the Shipping Crate 342Rotary Set-Up 353Setting Backlash at the Control 345Setting the VH-65 Worm Gear Backlash 346Setting the VMC Parameters 344Setting the Voltage 345Squaring the VH-65 342Technara MD-200R 357Technara MD-300R 358Troyke NC-10 356Tsudakoma RNCV-401 359Verifying Air Brake Engagement 351SScale Box Installation / Side Mount 416Scale Box Installation / Top Mount 421Scales 3731580 Board Setup 414Installing Scales 373Scheduled Maintenance 75Cooling Fans 78Dual Arm Tool Changer 82Cleaning 82Daily Maintenance 83Grease 82Inspection 83Lubricant 82Miscellaneous Maintenance 83Weekly Maintenance 83Fuses, Heaters, & Relays 80Auger 80Fluids 80Lubrication of the Ways 76Flushing a Contaminated Waylube System 77Waylube System 76Maintenance & Lubrication Schedule 75Daily 75Every 4 months 76Weekly 75Pump Filter 78Spindle & Ballscrew Cooling System 78Tank Reservoir 79Pressure 79Source for Dowfrost 79Sequence of Dual Arm-ATC Operation When Used With The Fadal Control 171 DA-ATC Tool Change Cycle Fadal Control 172Feedback 171Part Numbers 171Service Programs 581TA,2 Programs 581O5801-45 Deg Test 581O5802-X Resolver Test 582O5803-Y Resolver Test 582O5804-Z Resolver Test 582O5805-Work Toolchanger 582O5806-Scrape Z Head 584O5807-X Vibration 584O5808-Y Vibration 585O5809-Z Vibration 585O5810-Orientation 586O5811-Balance Inch 595, Metric 700ipm 302 586O5812-X Balance 680 587O5813-Y Balance 680 587O5814-Z Balance 680 588O5815-A or B 680 Balance 588O5817-Spin Fwd Rev 589O5818-Workout 2216 589O5819-Workout 4020 591O5820-Workout 6030 594O5821- X Calib 2216 596O5822 -Y Calib 2216 597O5823-X Calib 4020 597O5824 — Y Calib 4020 598O5825 — X Calib 6030 598O5826-Y Calib 6030 599O5828-Scrape 6030 Table 600O5829 — Mill 6030 Table 601O5830-Scrape 4020 Table 601O5831-Mill 4020 Table 603O5832-Scrape 2216 Table 603O5833-Mill VMC 2216 604O5834-Scrape 20 Table 605O5835-Test Scales 606O5836-Test Cut 607O5837-Probe Cycle Test 609O5838-Spindle Break In 610O5839-Pallet Changer 611O5840-Mill Pallet Table 614O5842-Engrave Pallet A 615O5843 — Center Bearing Assy. 615O5844-Mill VMC 20 616O5845-Mill VMC 15 617O6000-Rigid Tap Cycle 617TA,2 ProgramsO5841-Mill Pallet Slot .687-.689 615 TA,5 Programs 6186001-Ballbar Test 625O5827-Cycle Test 618Tool Offsets for the Service Programs 581 Shipping Dimensions 43Single Phase Input Power 67Specification -Grounding for the Fadal machine48Specifications 1Spindle Belleville Springs Quantity Chart 285Spindle Drawbar and Belleville Spring Replacement 283Drawbar Removal 283Remove Floater (This will rarely be necessary.) 284Replace Belleville Springs 284Spindle Drive Systems 239Adjustments 244Adjusting the AMC Vector Drive 256Adjusting the Baldor Vector Drives 244Adjustments 257Auto Tuning/ Zero Balance 244Baldor Spindle Drive Parameter Usage for Fadal VMC 245LEDs 256Motor Mag Amps for INV-0070 250Non Rigid Tap Machines 259Pot Adjustments 258Pots 257Regenerative Resistors 254Rigid Tap Machines 259Switch Positions 256Switch Settings 258Terms and Procedures245Velocity Monitor Output 256Motors 26310 HP Motor 26315 HP Motor 26320 HP Motor 263WYE / DELTA Motors 264Spindle Drives 239Spindle Duty Cycle 286Spindle Pre-Load 286Measuring the Spindle Pre-Load 286Spindles 28815K Air/Oil Spindle 2887.5K & 10K Grease Packed Spindles 288Adjusting Spindle Tram 293Component Installation 290Control Board Mounting 291Installing Spindle Lubrication Pump 290Pressure Manifold Mounting 291Regulator/ Separation Block Mounting 290Solenoid Modification 291Vacuum Pump Installation 290Spindle Tram 292Spindle/Lube Pump/Control 289Supplemental Grounding 47TTable & T-Slot Dimensions 3315 & 2016L Table 3315, 15XT, 2216, 3016, 2016L & 3016L T-Slots 3415XT & 3016L Table 342216 & 3016 Table 333020, 4525 Table & T-Slots 353020, 4525, 6535 T-Slots 384020 Table 354020, 4020A, 5020A, 6030 & 8030 T-Slots 384020A & 5020A Table 366030 Table 366535 Table 378030 Table 37Tap-Tap Cycle 282Test Cut Procedure 492Tests for CE Safeguards on Fadal Machines 98Daily 99Daily & Weekly Safety Tests for CE Safety Circuits 99Door Interlock Monitor (2000-1A) Weekly Test 100Door Interlock Monitor Daily Test for 2000-1A or 1310-0C 99Door Interlock Monitor on Auger Board (1310-0C) Weekly Test 102 Door Interlock Monitor Weekly Test for 2000-1 B or -1 C 101Dual Arm Tool Changer (1330) Daily Test 99Dual Arm Tool Changer (1330) Weekly Test 103Front Door Lock Daily Test for 2030-OA 99Front Door Lock Weekly Test for 2030-OA 103Pallet Changer (1100-3A) Daily Test 100Pallet Changer (1100-3A) Weekly Test 104Weekly 100Tilting Rotary Tables, 4th & 5th Axis 363A &B Axis Position Loop Gain (1010-5) 365FADAL TR-65 363Tools Sticking in the Spindle During a Change Cycle 2761. Air Supply Pressure 27610. Orientation Bridge "Lifting" 27811. Black Oxide Tool Holders 27812. Dirty Tool Holders 27813. Spring Pilot 27814. Spring Pilot 27915. Drawbar Scored 27916. Damaged Drawbar 27917. Damaged Floater 27918. Testing Procedure 2792. Drawbar Cylinder Hall Effects Switch 2773. Insufficient Air VolumeMAC In-Line Valve 2774. Air Leaks 2775. Air Leaks 2776. Air Leaks 2777. Air Leaks 2778. Air Leaks 2789. Air Leaks 278DRB-0024 Sticking Tools Kit, 10K LDB 281DRB-0025 Sticking Tools Kit, 10K LDB-CT= 281MEASURING DRAWBAR PERFORMANCE 280 Transformer Sensor 68Transformer Tapping 66Troubleshooting 497Troubleshooting Charts 536UUnlocking Front Doors with CE Door Locks 53 Unpacking 53VVector Drive Encoder 9 pin Molex Connector 242Vector Drive with Rigid Tapping 243Verification - Check grounding integrity with Fluke meter 49 VMC Test Cut 494Part 495WWiring 50ZZero-Out Memory Procedure 105Zero-Out Memory Settings 107。

[vip专享]IMM error messages

critical error message version -回复

criticalerrormessage

critical error message version -回复

unserialize newest msg error -回复

3GPP TS 31.111 V8.4.0

Indradrive 系列 故障代码

critical error message version -回复

3GPP TS 36.331 V13.2.0 (2016-06)

GP-error-message

MASM错误代码

critical error message

marshmallow error message

Code Home Edition Error Messages

selfregistration error -回复

AMM error处理方法

E-Prime常见错误代码表

ISO 11992-4-2005

芬达（Fadal）维修手册说明书

Indradrive 系列故障代码