Vehicle machine diagnosis method and device based on QNX system
By creating an independent diagnosis thread for each external device in the vehicle machine, and processing and transmitting information through the receiving and sending threads of the QNX system, the problem of low fault diagnosis efficiency of the vehicle machine system is solved, and efficient and accurate vehicle machine diagnosis is achieved.
Patent Information
- Application Number
- CN202411780815.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-05
- Publication Date
- 2025-03-25
AI Technical Summary
As the complexity of the vehicle and machine system and the number of peripherals increase, troubleshooting and diagnosis have become increasingly difficult, and traditional methods have problems of low diagnostic efficiency and high cost.
Diagnostic threads are created in the external devices of the QNX system in the vehicle machine, and the diagnostic information code is received and converted into the reporting information code through the first receiving thread. The centralized processing of the diagnosis information is realized through memory sharing, and the reporting information code is uploaded to the first sending thread of the QNX system for communication with the Android system, and the reporting information code is sent to the MCU through the second sending thread.
Through centralized processing and efficient information transmission, the efficiency of vehicle-machine diagnosis is improved, efficient collaboration between the QNX system and the Android system is ensured, and the accuracy of diagnostic information and the scalability of vehicle-machine system are enhanced.
Smart Images

Figure CN119690039A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of automobile intelligent cockpits, and in particular to a vehicle computer diagnosis method and device based on a QNX system. Background Art
[0002] With the continuous advancement of smart car technology, the complexity and integration of vehicle computer systems are increasing. Vehicle computer systems not only need to meet traditional driving control and infotainment functions, but also need to integrate more complex intelligent applications. The realization of these functions depends on the support of a large number of hardware devices and sensors.
[0003] However, with the increase in the number of peripherals and system complexity, the troubleshooting and diagnosis of vehicle system faults has become increasingly difficult. Therefore, how to improve the efficiency of vehicle system fault diagnosis has become a problem that needs to be solved. Summary of the invention
[0004] In view of this, the present disclosure provides a vehicle computer diagnosis method and device based on a QNX system to solve the problem of how to improve the efficiency of fault diagnosis of the vehicle computer system.
[0005] On the one hand, the present disclosure provides a vehicle computer diagnosis method based on the QNX system, the method comprising: creating diagnostic threads in external devices of the QNX system in the vehicle computer respectively, and using the diagnostic threads to monitor the external devices; based on a first receiving thread of the QNX system, receiving a diagnostic information code of the external device from the diagnostic thread, converting the diagnostic information code into a reporting information code, writing the reporting information code into a memory, and uploading the reporting information code to a first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer; based on a second sending thread of the QNX system, reading the reporting information code in the memory, and sending the reporting information code to the MCU in the vehicle computer.
[0006] On the other hand, the present disclosure also provides a vehicle computer diagnostic device based on the QNX system, the device includes a diagnostic module, a first sending module and a second sending module, wherein: the diagnostic module is used to create diagnostic threads in external devices of the QNX system in the vehicle computer respectively, and use the diagnostic threads to monitor the external devices; the first sending module is used to receive diagnostic information codes of external devices from the diagnostic thread based on the first receiving thread of the QNX system, convert the diagnostic information codes into reporting information codes, write the reporting information codes into a memory, and upload the reporting information codes to the first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer; the second sending module is used to read the reporting information code in the memory based on the second sending thread of the QNX system, and send the reporting information code to the MCU in the vehicle computer.
[0007] On the other hand, the present disclosure further provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to enable a computer to implement the above-mentioned vehicle computer diagnosis method based on the QNX system.
[0008] On the other hand, the present disclosure further provides a computer program product, including computer instructions, where the computer instructions are used to enable a computer to execute the above-mentioned vehicle computer diagnosis method based on the QNX system.
[0009] Through the vehicle computer diagnosis method and device based on the QNX system of the above embodiment of the present disclosure, the first receiving thread receives the diagnostic information code from the diagnostic thread of each device and converts it into a reporting information code, and writes it into the memory, and realizes the centralized processing of diagnostic information through memory sharing, improves the efficiency of information transmission, and thus improves the efficiency of vehicle computer diagnosis. The first sending thread of the QNX system communicates with the Android system, ensuring the efficient collaboration between the QNX system and the Android system in the vehicle computer system, and further improving the efficiency of vehicle computer diagnosis.
[0010] In addition, by creating a separate diagnostic thread for each external device, the status of the external device can be monitored in real time, interference between devices can be avoided, the accuracy of diagnostic information is ensured, and the effect of vehicle computer diagnosis is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0012] Figure 1 is a flow chart of a vehicle computer diagnosis method based on a QNX system provided by an embodiment of the present disclosure;
[0013] Figure 2 An exemplary schematic diagram showing the architecture of a vehicle computer diagnosis device based on a QNX system applied to a vehicle computer diagnosis method based on a QNX system according to an embodiment of the present disclosure;
[0014] Figure 3 is a structural schematic diagram of a vehicle computer diagnostic device based on a QNX system provided by an embodiment of the present disclosure;
[0015] Figure 4 It is a structural schematic diagram of another vehicle diagnostic device based on the QNX system provided in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0016] With the continuous advancement of smart car technology, the complexity and integration of vehicle systems are increasing. The vehicle system not only needs to meet the traditional driving control and infotainment functions, but also needs to integrate more complex intelligent applications, such as automatic driving assistance systems, in-vehicle voice assistants, remote monitoring and diagnosis, etc. The realization of these functions depends on the support of a large number of hardware devices and sensors, such as cameras, radars, lidars, touch screens, voice recognition modules, etc. These peripherals are closely integrated with hardware platforms such as the smart cockpit system on chip (SoC) and the vehicle microcontroller unit (MCU), together forming the vehicle system.
[0017] However, with the increase in the number of peripherals and system complexity, the troubleshooting and diagnosis of vehicle system faults has become increasingly difficult. Traditional fault diagnosis methods often rely on manual inspection or a single hardware testing tool, resulting in low diagnostic efficiency and high diagnostic costs.
[0018] To solve the above problems, various embodiments of the present disclosure provide a vehicle computer diagnosis method based on the QNX system, the method comprising: creating diagnostic threads in external devices of the QNX system in the vehicle computer respectively, and using the diagnostic threads to monitor the external devices; based on a first receiving thread of the QNX system, receiving a diagnostic information code of the external device from the diagnostic thread, converting the diagnostic information code into a reporting information code, writing the reporting information code into a memory, and uploading the reporting information code to a first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer; based on a second sending thread of the QNX system, reading the reporting information code in the memory, and sending the reporting information code to the MCU in the vehicle computer.
[0019] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.
[0020] Please refer to Figure 1 , Figure 1 : is a flow chart of a vehicle computer diagnosis method based on a QNX system provided by an embodiment of the present disclosure. The flow of the method may include the following steps:
[0021] Step S101 , respectively creating diagnostic threads in the external devices of the QNX system in the vehicle computer, and using the diagnostic threads to monitor the external devices.
[0022] In this embodiment, the vehicle computer may refer to a smart cockpit system, and the vehicle computer may include an MCU and a SoC, wherein the MCU may be used to process simple real-time tasks, and the SoC may be used to process advanced computing tasks.
[0023] As an example, simple real-time tasks handled by MCU may include but are not limited to vehicle hardware and sensor control, and advanced computing tasks handled by SoC may include but are not limited to multimedia processing and display, and external data exchange. Among them, SoC may include Qualcomm 8155 chip, 8295 chip and other processing chips that support operating systems and external devices.
[0024] In a possible implementation, the QNX system in the vehicle computer can be deployed in the SoC, and the external devices of the QNX system can include but are not limited to display devices, sensors, cameras, audio devices, input devices, etc. Among them, the QNX system can be a real-time operating system based on a microkernel architecture.
[0025] Furthermore, the diagnostic thread created in the external device may be a task that runs independently in the external device, and may detect potential faults or anomalies by periodically checking the working status of the external device.
[0026] For example, the diagnostic thread may include: a screen monitoring thread and a camera monitoring thread.
[0027] In a possible implementation, the method may further include:
[0028] Using the QNX system, a corresponding priority is set for each diagnostic thread based on the importance of the external device where the diagnostic thread is located to meet the real-time requirements of the vehicle computer.
[0029] Step S102, based on the first receiving thread of the QNX system, receiving the diagnostic information code of the external device from the diagnostic thread, converting the diagnostic information code into a reporting information code, writing the reporting information code into the memory, and uploading the reporting information code to the first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer.
[0030] In this embodiment, a first receiving thread is created in the QNX system, and the first receiving thread is used to receive the diagnostic information code of the external device; wherein the diagnostic information code is determined and sent by the diagnostic thread.
[0031] The adopting of the first receiving thread to receive the diagnostic information code of the external device may include: based on a preset communication mechanism, adopting the first receiving thread to acquire the diagnostic information code of the diagnostic thread in the external device.
[0032] Here, the preset communication mechanism may include but is not limited to: message queue and shared memory.
[0033] As an example, the diagnostic message code can be used to represent the working state of the external device or the existing fault information. For example, the diagnostic message code 0x00 can be used to indicate that the device is normal, 0x01 can be used to indicate that the device is faulty, and 0xFF can be used to indicate an unknown problem.
[0034] Furthermore, more detailed diagnostic message codes may be used to characterize specific fault types of external devices.
[0035] Converting the diagnostic information code to a reporting information code may include: when the first receiving thread obtains the diagnostic message code, matching the diagnostic message code with a predefined error code to determine a reporting message code corresponding to the diagnostic message code.
[0036] For example, 0x01 indicating a device failure is converted into a reporting information code 0xA1, indicating a multimedia device failure.
[0037] In a possible implementation, a first sending thread is created in the QNX system, the first sending thread is used to receive a reporting message code from the first receiving thread, and the reporting message code is sent to the Android system in the vehicle computer.
[0038] Here, when the Android system receives the reported message code, it can display the fault code and related fault information on the vehicle display screen, or it can trigger the alarm system of the vehicle computer or vehicle-mounted equipment.
[0039] Furthermore, the reported information code may also be stored in the memory of the QNX system.
[0040] Step S103, based on the second sending thread of the QNX system, read the reporting information code in the memory, and send the reporting information code to the MCU in the vehicle computer.
[0041] In this embodiment, a second sending thread is created in the QNX system, and the second sending thread is used to read the reporting information code in the memory, and send the reporting information code to the MCU in the vehicle computer.
[0042] Specifically, the second sending thread is used to access the shared memory or buffer in the QNX system to obtain the reporting information code, and the reporting information code is sent to the MCU in the vehicle computer using a preset communication method.
[0043] As an example, the preset communication mode may include but is not limited to: serial communication and controller area network (CAN) bus communication.
[0044] Here, the reporting information code is sent to the MCU in the vehicle computer, so that the diagnostic information of the external device can be safely viewed when a network failure occurs.
[0045] In the vehicle computer diagnosis method and device based on the QNX system of the above-mentioned embodiment of the present disclosure, the first receiving thread receives the diagnostic information code from the diagnostic thread of each device and converts it into a reporting information code, and writes it into the memory, and realizes the centralized processing of diagnostic information by memory sharing, improves the efficiency of information transmission, and thus improves the efficiency of vehicle computer diagnosis. By communicating with the Android system through the first sending thread of the QNX system, efficient collaboration between the QNX system and the Android system in the vehicle computer system is ensured, and the efficiency of vehicle computer diagnosis is further improved. By creating a diagnostic thread separately for each external device, the status of the external device can be monitored in real time, interference between devices can be avoided, and the accuracy of diagnostic information is ensured, thereby improving the effect of vehicle computer diagnosis.
[0046] In step S101 of the above embodiment, diagnostic threads are respectively created in the external devices of the QNX system in the vehicle computer, and the external devices are monitored using the diagnostic threads, including:
[0047] Creating a corresponding diagnostic thread for each external device in at least one external device of the QNX system, using the diagnostic thread to monitor the corresponding external device, and allowing the diagnostic thread to obtain the monitoring status of the external device in a polling manner; wherein each diagnostic thread in the at least one diagnostic thread is independent of each other;
[0048] The diagnostic thread is used to convert the format of the monitoring status of the external device and determine the diagnostic information code corresponding to the monitoring status.
[0049] In this embodiment, when a corresponding diagnostic thread is created for each external device, a polling time interval corresponding to the diagnostic thread may be set, and the frequency of the diagnostic thread acquiring the monitoring status of the external device may be controlled based on the polling time interval.
[0050] Here, the method may also include:
[0051] When creating a diagnostic thread, set the monitoring logic of each diagnostic thread to not interfere with each other;
[0052] Set the diagnostic thread to sleep for a preset time between each poll to avoid excessive use of system resources.
[0053] In a possible implementation, using a diagnostic thread to convert the format of the monitoring state of the external device and determining the diagnostic information code corresponding to the monitoring state may include:
[0054] When it is determined that the diagnostic thread obtains the monitoring status of the external device, the monitoring status is classified, the format of the monitoring status is converted based on the classification result, and the diagnostic information code corresponding to the monitoring status is determined.
[0055] As an example, the monitoring status is classified into normal, fault, and unknown problem, the monitoring status in the normal state is converted to 0x00, the monitoring status in the fault state is converted to 0x01, and the monitoring status in the unknown problem state is converted to 0xFF.
[0056] In the vehicle computer diagnosis method and device based on the QNX system of the above-mentioned embodiment of the present disclosure, by creating an independent diagnostic thread for each external device and controlling the polling time interval of each thread, it is avoided that multiple threads occupy too many computing resources at the same time, thereby effectively avoiding excessive occupation of system resources. It can ensure that the status monitoring of each device does not interfere with each other, making the vehicle computer diagnosis process more efficient. By classifying the monitoring status and generating different diagnostic information codes according to different statuses, this formatted processing method facilitates subsequent fault diagnosis and problem location. Through the unified diagnostic information code, the vehicle computer system can quickly locate the problem area, further improving the efficiency of fault diagnosis. Each external device has an independent diagnostic thread, and the threads do not interfere with each other, which means that the system can support multiple external devices to run diagnostics at the same time. This parallel monitoring mechanism not only improves the scalability of the vehicle computer system, but also ensures the overall diagnostic efficiency under the multi-device system.
[0057] In a possible implementation of the above embodiment, the method further includes:
[0058] The diagnostic information code of each diagnostic thread in at least one diagnostic thread is sent to the first receiving thread by adopting an inter-process communication method that does not rely on a network.
[0059] In this embodiment, the inter-process communication methods that are not dependent on the network may include, but are not limited to: message queues, shared memory, and events.
[0060] Specifically, the QNX system supports a memory-based message queue. Using the message queue, the diagnostic thread can send a diagnostic information code to the first receiving thread. In QNX, a shared memory area can be created. In the shared memory area, the diagnostic thread can share the diagnostic information code with the first receiving thread. The event mechanism can be used for synchronization and notification between different processes. The diagnostic thread can set an event flag, and the first receiving thread receives the diagnostic information code by waiting for the event.
[0061] In the vehicle computer diagnosis method and device based on the QNX system of the above-mentioned embodiment of the present disclosure, rapid transmission of diagnostic information codes is achieved through an inter-process communication method that does not rely on the network, thereby increasing the efficiency of vehicle computer diagnosis and the speed of problem location.
[0062] In a possible implementation of the above embodiment, converting the diagnostic information code into a reporting information code includes:
[0063] Obtain vehicle model information where the QNX system is located, and determine the conversion mapping relationship between the diagnostic information code and the reporting information code based on the vehicle model information; wherein the conversion mapping relationship includes: a one-to-one mapping relationship, a one-to-many mapping relationship, and a many-to-one mapping relationship;
[0064] Based on the conversion mapping relationship, the diagnostic information code is converted into a reporting information code.
[0065] In this embodiment, obtaining the vehicle model information where the QNX system is located may include: reading the vehicle model information of the vehicle computer where the QNX system is located based on the system configuration file.
[0066] The vehicle model information can be used to determine the mapping rules between the diagnostic information code and the reporting information code required by the vehicle model. The vehicle model information may include but is not limited to: vehicle model ID, vehicle hardware version number, production date, and owner-selected configuration.
[0067] Furthermore, the one-to-one mapping relationship in the conversion mapping relationship can be used to represent that each diagnosis information code corresponds to a unique reporting information code.
[0068] For example, the diagnostic information code 0x01 is always mapped to the reporting information code 0x01.
[0069] The one-to-many mapping relationship in the conversion mapping relationship can be used to represent that one diagnosis information code may correspond to multiple reporting information codes.
[0070] For example, the diagnostic information code 0x01 is mapped to 0x03 in vehicle model A and to 0x04 in vehicle model B.
[0071] The many-to-one mapping relationship in the conversion mapping relationship can be used to represent that multiple diagnosis information codes may be combined into one reporting information code.
[0072] For example, the break information codes 0x01, 0x02, and 0x03 may all be mapped to the same reporting information code 0x10.
[0073] In the vehicle computer diagnosis method and device based on the QNX system of the above embodiment of the present disclosure, by obtaining vehicle type information, finding a suitable mapping rule, and converting the diagnostic information code into a reporting information code, it can be ensured that the vehicle computer system can accurately report fault information under different vehicle types, different equipment or fault types. This mapping mechanism can be adjusted according to the needs of different vehicle types, so that the vehicle computer system has stronger adaptability and flexibility.
[0074] In a possible implementation of the above embodiment, the method further includes:
[0075] Create a second receiving thread in the Android system in the vehicle computer, and use the second receiving thread to receive the reporting information code from the first sending thread based on the HAB communication method;
[0076] The second receiving thread is used to upload the reporting information code to the cloud.
[0077] In this embodiment, the method may include: creating a second receiving thread in the Android system, and configuring a Hypervisor Application Bus (HAB) interface in the Android system; wherein the HAB interface is used to communicate with the first sending thread of the QNX system;
[0078] The reporting information code from the first sending thread of the QNX system is received through the HAB interface of the second receiving thread, the reporting information code is verified and parsed, and the parsed reporting information code is uploaded to the cloud server through the second receiving thread.
[0079] In the vehicle computer diagnosis method and device based on the QNX system of the above-mentioned embodiment of the present disclosure, by uploading the reporting information code to the cloud, the vehicle's fault information can be viewed remotely in real time, thereby improving the efficiency of vehicle computer diagnosis.
[0080] In a specific example, Figure 2 An exemplary schematic diagram showing the architecture of a vehicle diagnostic device based on a QNX system applied to a vehicle diagnostic method based on a QNX system according to an embodiment of the present disclosure is shown, wherein:
[0081] The vehicle system includes SOC and MCU, wherein the SOC includes QNX system, Android system and external devices. The first receiving thread in the QNX system obtains the diagnostic information code sent by the diagnostic thread in the external device, converts the diagnostic information code into a reporting information code, writes the reporting information code into the memory and sends it to the first sending thread. The first sending thread sends the reporting information code to the first receiving thread in the Android system, and the first receiving thread uploads the reporting information code to the cloud server. The second sending thread in the QNX system obtains the reporting information code from the memory and sends the reporting information code to the MCU.
[0082] In one embodiment, a vehicle computer diagnostic device 30 based on a QNX system is provided, and the vehicle computer diagnostic device 30 based on a QNX system corresponds one-to-one to the vehicle computer diagnostic method based on a QNX system in the above embodiment. Figure 3 As shown, the vehicle diagnostic device 30 based on the QNX system includes a diagnostic module 301, a first sending module 302 and a second sending module 303, wherein each functional module is described in detail as follows:
[0083] The diagnostic module 301 is used to create diagnostic threads in the external devices of the QNX system in the vehicle computer, and use the diagnostic threads to monitor the external devices;
[0084] The first sending module 302 is used to receive the diagnostic information code of the external device from the diagnostic thread based on the first receiving thread of the QNX system, convert the diagnostic information code into a reporting information code, write the reporting information code into the memory, and upload the reporting information code to the first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer;
[0085] The second sending module 303 is used to read the reporting information code in the memory based on the second sending thread of the QNX system, and send the reporting information code to the MCU in the vehicle computer.
[0086] In one embodiment, the diagnostic module 301 is used to create a corresponding diagnostic thread for each external device in at least one external device of the QNX system, use the diagnostic thread to monitor the corresponding external device, and enable the diagnostic thread to obtain the monitoring status of the external device in a polling manner; wherein each diagnostic thread in the at least one diagnostic thread is independent of each other;
[0087] The diagnostic thread is used to convert the format of the monitoring status of the external device and determine the diagnostic information code corresponding to the monitoring status.
[0088] In one embodiment, the vehicle diagnostic device 30 based on the QNX system further includes a third sending module 304, wherein:
[0089] The third sending module 304 is used to send the diagnostic information code of each diagnostic thread in the at least one diagnostic thread to the first receiving thread by adopting an inter-process communication method that does not rely on the network.
[0090] In one embodiment, the first sending module 302 is used to obtain vehicle model information of the QNX system, and determine the conversion mapping relationship between the diagnostic information code and the reporting information code based on the vehicle model information; wherein the conversion mapping relationship includes: a one-to-one mapping relationship, a one-to-many mapping relationship, and a many-to-one mapping relationship;
[0091] Based on the conversion mapping relationship, the diagnostic information code is converted into a reporting information code.
[0092] In one embodiment, the vehicle diagnostic device 30 based on the QNX system further includes a first receiving module 305, wherein:
[0093] The first receiving module 305 is used to create a second receiving thread in the Android system in the vehicle computer, and use the second receiving thread to receive the reporting information code from the first sending thread based on the HAB communication method;
[0094] The second receiving thread is used to upload the reporting information code to the cloud.
[0095] It should be noted that: the vehicle diagnostic device based on the QNX system provided in the above embodiment only uses the division of the above program modules as an example to illustrate when implementing the corresponding vehicle diagnostic method based on the QNX system. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the above system can be divided into different program modules to complete all or part of the above-described processing. In addition, the system provided in the above embodiment and the corresponding Figure 1 The embodiments of the method shown belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.
[0096] The present disclosure also provides a computer device having the above Figure 3 The vehicle diagnostic device based on the QNX system is shown.
[0097] See also Figure 4 , Figure 4 is a schematic diagram of the structure of another vehicle diagnostic device based on the QNX system provided by an embodiment of the present disclosure, such as Figure 4 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 4 A processor 10 is taken as an example.
[0098] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.
[0099] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.
[0100] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0101] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.
[0102] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 4 The example of connecting through bus is taken in the following.
[0103] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.
[0104] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.
[0105] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.
[0106] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.
[0107] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.
Claims
1. A vehicle computer diagnosis method based on QNX system, characterized in that: The method comprises: Creating diagnostic threads in external devices of the QNX system in the vehicle computer respectively, and using the diagnostic threads to monitor the external devices; Based on the first receiving thread of the QNX system, receiving the diagnostic information code of the external device from the diagnostic thread, converting the diagnostic information code into a reporting information code, writing the reporting information code into a memory, and uploading the reporting information code to the first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer; Based on the second sending thread of the QNX system, the reporting information code in the memory is read, and the reporting information code is sent to the MCU in the vehicle computer.
2. The method according to claim 1, characterized in that The step of creating diagnostic threads in the external devices of the QNX system in the vehicle computer and using the diagnostic threads to monitor the external devices includes: Creating a corresponding diagnostic thread for each external device in at least one external device of the QNX system, using the diagnostic thread to monitor the corresponding external device, and allowing the diagnostic thread to obtain the monitoring status of the external device in a polling manner; wherein each diagnostic thread in the at least one diagnostic thread is independent of each other; The diagnostic thread is used to perform format conversion on the monitoring status of the external device and determine the diagnostic information code corresponding to the monitoring status.
3. The method according to claim 2, characterized in that The method further comprises: The diagnostic information code of each diagnostic thread in at least one diagnostic thread is sent to the first receiving thread by adopting an inter-process communication method that does not rely on a network.
4. The method according to claim 1, characterized in that The converting the diagnostic information code into a reporting information code comprises: Obtain vehicle model information where the QNX system is located, and determine a conversion mapping relationship between a diagnostic information code and a reporting information code based on the vehicle model information; wherein the conversion mapping relationship includes: a one-to-one mapping relationship, a one-to-many mapping relationship, and a many-to-one mapping relationship; Based on the conversion mapping relationship, the diagnosis information code is converted into a reporting information code.
5. The method according to claim 4, characterized in that The method further comprises: Create a second receiving thread in the Android system in the vehicle computer, and use the second receiving thread to receive the reporting information code from the first sending thread based on the HAB communication method; The second receiving thread is used to upload the reporting information code to the cloud.
6. A vehicle computer diagnostic device based on the QNX system, characterized in that: The device comprises a diagnosis module, a first sending module and a second sending module, wherein: The diagnostic module is used to create diagnostic threads in the external devices of the QNX system in the vehicle computer, and use the diagnostic threads to monitor the external devices; The first sending module is used to receive the diagnostic information code of the external device from the diagnostic thread based on the first receiving thread of the QNX system, convert the diagnostic information code into a reporting information code, write the reporting information code into a memory, and upload the reporting information code to the first sending thread of the QNX system; the first sending thread is used to communicate with the Android system in the vehicle computer; The second sending module is used to read the reporting information code in the memory based on the second sending thread of the QNX system, and send the reporting information code to the MCU in the vehicle computer.
7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the vehicle computer diagnosis method based on the QNX system as described in claims 1-5.
8. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to enable a computer to execute the vehicle computer diagnosis method based on the QNX system according to any one of claims 1 to 5.
Citation Information
Cited By
Cross-system touch screen data processing method, system and equipment based on HAB mechanism
CN120743136A
A cross-system touch screen data processing method, system and device based on a HAB mechanism
CN120743136B