Vehicle electrical testing methods, devices, electronic equipment, storage media and program products

Abstract

This application provides a vehicle electrical inspection method, apparatus, electronic device, storage medium, and program product, relating to the field of vehicle inspection technology. The method is applicable to a cloud platform, which is communicatively connected to at least one electrical inspection production line. The production line has at least two electrical inspection stations. The method includes: real-time collection of production line operating parameters, station operating status, and pending inspection task information; matching any electrical inspection task to the corresponding electrical inspection station based on the electrical inspection function list, production line operating parameters, electrical inspection task list, and station operating status, according to a production line load model; generating an electrical inspection task list based on the station information of the matched stations, and associating first vehicle information with the electrical inspection task list; and sending the electrical inspection task list to the electrical inspection stations based on the station information. This method aims to improve vehicle electrical inspection efficiency through multi-station collaborative electrical inspection operations.

Description

Technical Field

[0001] This application relates to the technical field of vehicle inspection, and more particularly to a vehicle electrical inspection method, apparatus, electronic device, storage medium, and program product. Background Technology

[0002] In modern automobile manufacturing, vehicle electrical testing is a crucial step in ensuring the functional integrity of the vehicle's electrical system and production quality. Current electrical testing production lines typically employ a multi-station collaborative model, where vehicles sequentially undergo functional testing, Electronic Control Unit (ECU) calibration, and road testing at different stations. Testing personnel connect the On-Board Diagnostics (OBD) interface to each vehicle and execute the vehicle's electrical testing tasks at the current station using specialized equipment.

[0003] In existing technologies, the electrical inspection tasks for each workstation are typically divided based on a single vehicle dimension. Pre-defined electrical inspection procedures are executed via onboard terminals (such as Telematics Boxes, or Tboxes), without considering collaborative operations between multiple workstations on the electrical inspection production line. This results in low vehicle electrical inspection efficiency. Therefore, how to implement collaborative operations across multiple workstations to improve vehicle electrical inspection efficiency is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a vehicle electrical inspection method, device, electronic device, storage medium, and program product to improve vehicle electrical inspection efficiency through multi-station collaborative electrical inspection operations.

[0005] In a first aspect, embodiments of this application provide a vehicle electrical inspection method. The method is applicable to a cloud platform, which is communicatively connected to at least one electrical inspection production line. The production line has at least two electrical inspection stations. The method includes:

[0006] Real-time collection of production line operation parameters, workstation operation status and task information of the electrical inspection production line, including the task information of the first vehicle and the list of electrical inspection tasks, with the list of electrical inspection tasks containing at least one electrical inspection task.

[0007] Based on the electrical inspection function list, production line operating parameters, electrical inspection task list, and workstation operating status of the electrical inspection station, any electrical inspection task is matched to the corresponding electrical inspection station according to the production line load model; the electrical inspection function list contains the electrical inspection functions that can be executed by the corresponding electrical inspection station.

[0008] Based on the workstation information of the matched electrical inspection workstations, an electrical inspection task list is generated, and the information of the first vehicle is associated with the electrical inspection task list.

[0009] Based on the workstation information, the electrical inspection task list is sent to the electrical inspection workstation.

[0010] In one possible implementation, based on the electrical inspection function list of the electrical inspection station, production line operating parameters, electrical inspection task list, and station operating status, and according to the production line load model, any electrical inspection task is matched to the corresponding electrical inspection station, including:

[0011] Based on the list of electrical inspection functions and the list of electrical inspection tasks, generate a list of workstations corresponding to the electrical inspection tasks;

[0012] Based on production line operating parameters and workstation operating status, and according to the production line load model, calculate the workstation production cycle time for completing the corresponding electrical inspection task in the workstation list.

[0013] Based on the production cycle time of each workstation, the feasibility of the workstation list is verified.

[0014] Once the workstation list passes the feasibility check, any electrical inspection task will be matched to the corresponding electrical inspection workstation based on the workstation list.

[0015] In one possible implementation, the feasibility of the workstation list is verified based on the workstation production cycle time, including:

[0016] Based on the workstation production cycle time and estimated dwell time, calculate the task execution time corresponding to the workstation list;

[0017] When the execution time of a task is determined to be less than or equal to the set total instruction time, the first necessary electrical inspection task in the workstation list is identified.

[0018] Based on the first necessary electrical inspection task, it is matched with the second necessary electrical inspection task in the electrical inspection task list, and based on the matching results, the feasibility of the workstation list is verified.

[0019] In one possible implementation, the method further includes:

[0020] When all the first necessary electrical inspection tasks are matched with the second necessary electrical inspection tasks, the workstation list is deemed to have passed the feasibility check.

[0021] In one possible implementation, the method further includes:

[0022] When at least two workstation lists pass the feasibility check, calculate the cumulative sum of the workstation production cycle time;

[0023] Based on the cumulative and smaller list of workstations, any electrical inspection task is matched to the corresponding electrical inspection workstation.

[0024] In one possible implementation, the method further includes:

[0025] When the workstation list fails the feasibility check, check whether the electrical inspection tasks in the workstation list are necessary electrical inspection tasks. If not, mark the corresponding electrical inspection tasks and generate electrical inspection prompt information based on the marking results.

[0026] If so, the corresponding electrical inspection task is recorded as an electrical inspection task to be executed, and the electrical inspection task to be executed is matched to an alternative electrical inspection station. The alternative electrical inspection station is the adjacent electrical inspection station of the electrical inspection station corresponding to the electrical inspection station of the electrical inspection task to be executed in the station list, and the electrical inspection function list of the adjacent electrical inspection station contains the electrical inspection function corresponding to the electrical inspection task to be executed.

[0027] In one possible implementation, the first vehicle information is: the vehicle identification number and / or the electronic control unit serial number associated with the vehicle identification number.

[0028] In one possible implementation, the method further includes:

[0029] Receive and store the electrical inspection results uploaded by the electrical inspection production line.

[0030] In one possible implementation, the method further includes:

[0031] The results of electrical inspection are analyzed. When it is determined that the results of electrical inspection contain an electrical inspection abnormality code, the electrical inspection abnormality is located based on the electrical inspection abnormality code, and the corresponding electrical inspection station and corresponding electrical inspection task are determined.

[0032] Secondly, embodiments of this application provide a vehicle electrical inspection method, applicable to an electrical inspection production line, wherein the production line has at least two electrical inspection stations, and the method includes:

[0033] Obtain the second vehicle information of the vehicle to be inspected and the first vehicle information in the electric inspection task list;

[0034] Determine whether the second vehicle information matches the first vehicle information. If yes, perform an electrical inspection on the vehicle to be inspected based on the electrical inspection task list. If no, generate an electrical inspection alarm message. The electrical inspection task list is a list generated according to any of the vehicle electrical inspection methods in the first aspect above.

[0035] In one possible implementation, the method further includes:

[0036] Package the electrical inspection results of the vehicles to be inspected and upload the packaged data.

[0037] Thirdly, embodiments of this application provide a vehicle electrical inspection device. The device is suitable for a cloud platform, which is communicatively connected to at least one electrical inspection production line. The electrical inspection production line has at least two electrical inspection stations. The device includes:

[0038] The data acquisition module is used to collect the production line operation parameters of the electrical inspection production line, the workstation operation status of the electrical inspection station, and the information of the tasks to be inspected in real time. The information of the tasks to be inspected includes at least the information of the first vehicle and the list of electrical inspection tasks, and the list of electrical inspection tasks contains at least one electrical inspection task.

[0039] The matching module is used to match any electrical inspection task to the corresponding electrical inspection station based on the electrical inspection function list, production line operating parameters, electrical inspection task list, and station operating status, according to the production line load model; wherein, the electrical inspection function list contains the electrical inspection functions that can be executed by the corresponding electrical inspection station.

[0040] The association module is used to generate an electrical inspection task list based on the workstation information of the matched electrical inspection workstations, and associate the first vehicle information with the electrical inspection task list;

[0041] The sending module is used to send the electrical inspection task list to the electrical inspection workstation based on the workstation information.

[0042] In one possible implementation, based on the electrical inspection function list of the electrical inspection station, production line operating parameters, electrical inspection task list, and station operating status, and according to the production line load model, any electrical inspection task is matched to the corresponding electrical inspection station, including:

[0043] Based on the list of electrical inspection functions and the list of electrical inspection tasks, generate a list of workstations corresponding to the electrical inspection tasks;

[0044] Based on production line operating parameters and workstation operating status, and according to the production line load model, calculate the workstation production cycle time for completing the corresponding electrical inspection task in the workstation list.

[0045] Based on the production cycle time of each workstation, the feasibility of the workstation list is verified.

[0046] Once the workstation list passes the feasibility check, any electrical inspection task will be matched to the corresponding electrical inspection workstation based on the workstation list.

[0047] In one possible implementation, the feasibility of the workstation list is verified based on the workstation production cycle time, including:

[0048] Based on the workstation production cycle time and estimated dwell time, calculate the task execution time corresponding to the workstation list;

[0049] When the execution time of a task is determined to be less than or equal to the set total instruction time, the first necessary electrical inspection task in the workstation list is identified.

[0050] Based on the first necessary electrical inspection task, it is matched with the second necessary electrical inspection task in the electrical inspection task list, and based on the matching results, the feasibility of the workstation list is verified.

[0051] In one possible implementation, the matching module is also used for:

[0052] When all the first necessary electrical inspection tasks are matched with the second necessary electrical inspection tasks, the workstation list is deemed to have passed the feasibility check.

[0053] In one possible implementation, the matching module is also used for:

[0054] When at least two workstation lists pass the feasibility check, calculate the cumulative sum of the workstation production cycle time;

[0055] Based on the cumulative and smaller list of workstations, any electrical inspection task is matched to the corresponding electrical inspection workstation.

[0056] In one possible implementation, the matching module is also used for:

[0057] When the workstation list fails the feasibility check, check whether the electrical inspection tasks in the workstation list are necessary electrical inspection tasks. If not, mark the corresponding electrical inspection tasks and generate electrical inspection prompt information based on the marking results.

[0058] If so, the corresponding electrical inspection task is recorded as an electrical inspection task to be executed, and the electrical inspection task to be executed is matched to an alternative electrical inspection station. The alternative electrical inspection station is the adjacent electrical inspection station of the electrical inspection station corresponding to the electrical inspection station of the electrical inspection task to be executed in the station list, and the electrical inspection function list of the adjacent electrical inspection station contains the electrical inspection function corresponding to the electrical inspection task to be executed.

[0059] In one possible implementation, the first vehicle information is: the vehicle identification number and / or the electronic control unit serial number associated with the vehicle identification number.

[0060] In one possible implementation, the device further includes:

[0061] The data receiving and storage module is used to receive and store the electrical inspection results uploaded by the electrical inspection production line.

[0062] In one possible implementation, the device further includes:

[0063] The anomaly detection module is used to parse the results of electrical inspection operations. When it is determined that the electrical inspection operation results contain electrical inspection anomaly codes, the module locates the electrical inspection anomalies based on the electrical inspection anomaly codes and determines the electrical inspection station and corresponding electrical inspection task corresponding to the electrical inspection anomaly codes.

[0064] Fourthly, embodiments of this application provide a vehicle electrical inspection device. The device is suitable for electrical inspection production lines, which have at least two electrical inspection stations. The device includes:

[0065] The acquisition module is used to acquire the second vehicle information of the vehicle to be inspected and the first vehicle information in the electric inspection task list.

[0066] The operation module is used to determine whether the second vehicle information matches the first vehicle information. If so, it performs an electric inspection on the vehicle to be inspected based on the electric inspection task list. If not, it generates an electric inspection alarm message. The electric inspection task list is a list generated according to any of the vehicle electric inspection methods in the first aspect mentioned above.

[0067] In one possible implementation, the device further includes:

[0068] The data upload module is used to package the electrical inspection results of the vehicles to be inspected and upload the packaged data.

[0069] Fifthly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0070] The memory stores instructions that the computer executes;

[0071] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above, or to perform the second aspect and / or various possible implementations of the second aspect as described above.

[0072] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect, or to implement the second aspect and / or various possible implementations of the second aspect.

[0073] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect, or implements the second aspect and / or various possible implementations of the second aspect.

[0074] The vehicle electrical inspection method, device, electronic equipment, storage medium, and program products provided in this application collect real-time production line operating parameters, electrical inspection station operating status, and pending inspection task information of the electrical inspection production line. Combined with the electrical inspection function list of the electrical inspection station, production line operating parameters, electrical inspection task list, and station operating status, any electrical inspection task is matched to the corresponding electrical inspection station according to the production line load model. This makes the allocation of pending electrical inspection tasks more closely aligned with the current production line load, station capacity, and station status, reducing waiting time and resource idleness at electrical inspection stations. Furthermore, by generating an electrical inspection task list based on the station information of the matched electrical inspection stations, associating the first vehicle information with the electrical inspection task list, and sending the electrical inspection task list to the electrical inspection stations based on the station information, it achieves unified association and orderly distribution of vehicle information, task information, and station information. This achieves the effect of improving vehicle electrical inspection efficiency through multi-station collaborative electrical inspection operations, enhancing the overall detection efficiency of vehicle assembly line electrical inspection, and strengthening the means of full-process data collaborative analysis and monitoring. Attached Figure Description

[0075] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0076] Figure 1 The flowchart of the vehicle electrical inspection method applicable to the cloud platform provided in this application is as follows. Figure 1 ;

[0077] Figure 2 The flowchart of the vehicle electrical inspection method applicable to the cloud platform provided in this application is as follows. Figure 2 ;

[0078] Figure 3 A flowchart illustrating the vehicle electrical inspection method applicable to electrical inspection production lines provided in this application;

[0079] Figure 4 A schematic diagram of the vehicle electrical inspection device for cloud platforms provided in this application;

[0080] Figure 5 A structural schematic diagram of a vehicle electrical inspection device applicable to an electrical inspection production line, provided in this application;

[0081] Figure 6 A schematic diagram of the structure of the electronic device provided in this application.

[0082] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0083] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0084] Vehicle assembly line electrical inspection technology is mainly used in the final assembly, off-line inspection, and final inspection stages of vehicle manufacturing, especially for new energy vehicles and intelligent connected vehicles. In this scenario, the vehicle passes through multiple electrical inspection stations along the conveyor line, with each station undertaking tasks such as confirming wiring harness connectivity, checking basic controller communication, activating functions, verifying parameters, and confirming the overall vehicle electrical status.

[0085] A typical electrical inspection production line usually consists of a conveyor mechanism, a workstation inspection terminal, a vehicle body recognition unit, a production execution system, and a host computer platform for storing inspection records. After a vehicle enters the workstation, the system reads the vehicle identification information and preset inspection items, calls the corresponding inspection equipment to complete the target item test, and records the results locally or uploads them to the production system.

[0086] Under the conditions of mass mixed-line production, vehicles of different models and configurations will continuously flow on the same electrical inspection production line. Moreover, the equipment capacity, working rhythm and current idle status of each electrical inspection station are not consistent. This makes vehicle electrical inspection no longer an isolated inspection activity on a single electrical inspection station, but a continuous process involving multi-station collaboration, task undertaking relationship and production line rhythm matching.

[0087] Especially with the increasingly complex electronic and electrical architecture of vehicles, the electrical inspection scenario not only needs to focus on whether a single test passes, but also needs to focus on the real-time correspondence between vehicle information, task content, workstation capabilities and production line status. Therefore, this technical field is essentially an integrated application scenario of industrial inspection and production line scheduling for multi-workstation manufacturing sites.

[0088] Current vehicle assembly line electrical inspections are typically implemented using a vehicle-by-vehicle independent inspection method. The basic workflow involves configuring relatively fixed dedicated inspection equipment or terminals at each workstation, which then performs the assigned electrical inspection items according to a pre-set procedure. Upon vehicle arrival, the system or operator first obtains vehicle identification information and then determines the inspection tasks required for the vehicle at the current workstation based on process rules. Subsequently, test commands are sent to the vehicle's electrical system via local inspection equipment, reading data from various control units, sensors, actuators, or communication buses, and determining pass / fail based on preset thresholds. Finally, the inspection results are recorded in a local database, workstation controller, or upper-level management system.

[0089] This technical solution can meet basic usage requirements under conditions of single vehicle model, low cycle time, or relatively fixed workstation functional boundaries, but it has revealed obvious shortcomings in actual large-scale assembly line production.

[0090] First, the allocation of electrical inspection tasks often relies on manual experience, fixed rules, or static configurations. There is a lack of coordination mechanisms between workstations based on real-time status. If a workstation experiences temporary congestion, equipment status fluctuations, or an increase in inspection items for a certain vehicle model, and subsequent vehicles still enter according to the original rules, it is very easy to cause waiting at the workstations in front and behind, local accumulation, and equipment idleness.

[0091] Secondly, the test data is usually stored around a single vehicle or a single workstation. Although it can retain local results, the data correlation between different workstations is weak. It is impossible to continuously observe the task execution link of the same vehicle from the perspective of the entire production line, and it is also difficult to identify abnormal patterns formed by cross-workstation transmission in a timely manner.

[0092] Secondly, due to the significant differences in configuration among different vehicles, some electrical inspection tasks can actually be undertaken by any of the multiple workstations. However, the existing methods generally lack a comprehensive assessment of the workstation's electrical inspection capabilities and current operating status, making it impossible to flexibly adjust the task recipients based on production line operating parameters, resulting in the underutilization of multi-workstation resources.

[0093] Furthermore, when managers want to understand the current load of a production line, the operational status of each workstation, and the arrangement of tasks awaiting inspection, they often have to rely on scattered records for manual summarization, failing to form a unified, continuous, and timely end-to-end understanding, thus affecting the efficiency of anomaly response and the depth of quality control. Therefore, while existing technologies can complete basic electrical inspections, they have significant limitations in multi-workstation collaborative scheduling, dynamic adaptation, and end-to-end data organization.

[0094] In view of this, how to improve the flexibility of multi-station task scheduling in the scenario of vehicle assembly line electrical inspection, and to form a more reasonable matching relationship between the information of the vehicle to be inspected, the capacity of the station and the status of the production line, has become an urgent technical problem to be solved.

[0095] To address the aforementioned issues, this application provides a vehicle electrical inspection method applicable to a cloud platform. The cloud platform is communicatively connected to at least one electrical inspection production line, which has at least two electrical inspection workstations, thus forming an application architecture for unified coordination across multiple workstations. When a vehicle is to be inspected on the production line, the cloud platform first collects in real-time the production line's operating parameters, the workstation's operating status, and the task information to be inspected. The task information includes at least the first vehicle information and an electrical inspection task list. After obtaining this information, the cloud platform combines the electrical inspection function list corresponding to each workstation and matches any electrical inspection task to the corresponding workstation according to the production line load model. Subsequently, an electrical inspection task list is generated based on the matched workstation information, and the first vehicle information is associated with this electrical inspection task list. Finally, the electrical inspection task list is sent to the corresponding electrical inspection workstation based on the workstation information. This technical approach transforms the previously fragmented and static workstation execution process into a task matching and distribution process oriented towards the overall production line status. This allows vehicle electrical inspection tasks to be allocated more specifically based on workstation capabilities and production line operation, thereby improving the synergy, adaptability, and overall testing efficiency of the assembly line electrical inspection process. Ultimately, this achieves the goal of improving vehicle electrical inspection efficiency through multi-workstation collaborative electrical inspection operations.

[0096] Figure 1 The flowchart of the vehicle electrical inspection method applicable to the cloud platform provided in this application is as follows. Figure 1 ,like Figure 1 As shown, this method is applicable to a cloud platform, which is communicatively connected to at least one electrical inspection production line. The electrical inspection production line has at least two electrical inspection stations. The method includes:

[0097] S101. Real-time collection of production line operation parameters, workstation operation status and task information of the electrical inspection production line, wherein the task information includes at least the first vehicle information and the electrical inspection task list, and the electrical inspection task list contains at least one electrical inspection task.

[0098] For example, the cloud platform in this application embodiment is a centralized platform that carries and executes the vehicle electrical inspection method. Functionally, it is responsible for communicating with at least one electrical inspection production line and coordinating the collection, matching, generation, and transmission of electrical inspection task-related information. The electrical inspection production line is a production line used to implement vehicle electrical inspection operations. It is the data source and task execution carrier of the vehicle electrical inspection method in this application embodiment. Specifically, it can be an off-line electrical inspection line after vehicle assembly, a final inspection electrical inspection line, or a mixed-line production electrical inspection line containing multiple inspection stations.

[0099] The electrical inspection station is used to perform specific electrical inspection tasks. Each station can be configured with a diagnostic instrument, a bus communication interface, a relay control module, a power supply switching module, and a local station control terminal. The electrical inspection station has a corresponding station identifier, current location, equipment capabilities, and online status in the electrical inspection production line or cloud platform.

[0100] Production line operating parameters are used to describe the overall operation of the electrical inspection production line. Specifically, they may include one or more of the following: the current throughput status of the production line, conveyor speed, vehicle queue length, occupancy status of each branch line, cycle time, remaining buffer capacity, current shift information, and abnormal stoppage flags.

[0101] The workstation operation status describes the current working status of the electrical inspection workstation, which may include one or more of the following: idle status, occupied status, fault status, maintenance status, available status, waiting to be loaded, and waiting for results to be uploaded.

[0102] The task information to be inspected is used to characterize the comprehensive information of the electrical inspection task to be performed. It is the basic input for the cloud platform to schedule tasks and generate task lists. The first vehicle information is used to identify the identity information of the vehicle to be inspected. It can be the vehicle identification number, the electronic control unit serial number bound to the vehicle identification number, the production order number, the configuration code, or a combination of the above information. The electrical inspection task list is used to list the electrical inspection tasks of the vehicles to be inspected. Specifically, it can include wiring harness connectivity confirmation tasks, controller online communication check tasks, diagnostic fault code reading tasks, software version verification tasks, parameter writing or verification tasks, function activation tasks, and vehicle sleep / wake-up status confirmation tasks, etc.

[0103] In one example, the cloud platform can be deployed on a central server cluster and connected to the production line controller, workstation terminals, and production execution system in the electrical inspection production line via industrial Ethernet, 5G private network, wireless LAN, or dedicated message bus.

[0104] The aforementioned real-time data collection process can be achieved by the cloud platform periodically polling the production line equipment. The polling period can be configured from 1 to 10 seconds according to the production line cycle time. Alternatively, the production line controller can proactively report to the cloud platform when status change events such as vehicle arrival, vehicle release, workstation switching, equipment failure, and task completion occur. Periodic polling can also be combined with event-driven reporting to simultaneously ensure status integrity and data timeliness.

[0105] In one possible implementation, the cloud platform first receives first vehicle information from the vehicle identification unit, which can be a Vehicle Identification Number (VIN) scanner, a Radio Frequency Identification (RFID) reader, or a vehicle identity mapping module connected to the Manufacturing Execution System (MES system).

[0106] Subsequently, the cloud platform queries the production execution system for the vehicle's configuration file and the process formula to be inspected based on the first vehicle information, and then generates or updates the electrical inspection task list corresponding to the vehicle. At the same time, the cloud platform obtains production line operating parameters and workstation operating status from the production line programmable logic controller (PLC), conveyor control system, and workstation controller, and aligns and caches data from different sources according to a unified timestamp.

[0107] For the collected data, the cloud platform can perform format standardization processing, mapping the status words, error codes, and detection capability codes uploaded by different devices into a unified data structure. For example, the workstation status can be uniformly mapped to enumerated values ​​such as idle, running, blocked, fault, and offline, and the production line speed and cycle time can be uniformly converted into standard time units, thereby providing consistent input for subsequent matching calculations.

[0108] In this step, real-time data collection is not limited to a single acquisition, but continuously updates the relationship between the three types of objects: vehicles, electrical inspection stations, and the electrical inspection production line. When the same vehicle moves to a new designated area on the electrical inspection production line, the cloud platform can refresh the vehicle's inspection task information based on the location information; when an electrical inspection station becomes unavailable due to equipment calibration, interface abnormalities, or manual intervention, the station's operating status will be updated immediately; when the electrical inspection production line's cycle time changes due to congestion ahead, the production line's operating parameters will also change synchronously.

[0109] Based on the above analysis, it can be seen that by collecting production line operating parameters, workstation operating status and inspection task information in real time, the cloud platform can obtain full input data reflecting the current production line load and electrical inspection task requirements, avoiding reliance on static configuration for subsequent task allocation, thus providing basic support for dynamic scheduling in multi-workstation scenarios, and ensuring that the inspection vehicle and task data have timeliness, consistency and traceability before entering the matching process.

[0110] S102. Based on the electrical inspection function list, production line operating parameters, electrical inspection task list, and workstation operating status of the electrical inspection station, match any electrical inspection task to the corresponding electrical inspection station according to the production line load model; wherein, the electrical inspection function list contains the electrical inspection functions that can be executed by the corresponding electrical inspection station.

[0111] For example, the electrical inspection function list in this application embodiment is used to characterize the set of electrical inspection and testing tasks that each electrical inspection station can undertake. Specifically, it may include functions such as Controller Area Network (CAN) bus diagnostics, Local Interconnect Network (LIN) bus node detection, Ethernet communication check, high voltage power-on confirmation, low voltage power status acquisition, controller post-write verification, configuration parameter writing, actuator action test, sensor signal reading, and vehicle fault code scanning.

[0112] This list of functions can be preset by the system when the workstation is deployed, or it can be dynamically updated based on the actual online configuration status of the testing equipment at the workstation. For example, when the high-voltage testing module of a certain electrical testing workstation is taken offline for maintenance, the cloud platform can automatically remove the high-voltage testing capability mark corresponding to that electrical testing workstation.

[0113] The production line load model is used to characterize the load-bearing capacity and allocation results of the electrical inspection production line under different production line operating parameters and different workstation operating states. Its purpose is to integrate the functional adaptation of electrical inspection tasks, the real-time status of electrical inspection workstations, and the overall cycle time requirements of the electrical inspection production line into a matching decision-making process.

[0114] In one example, the cloud platform can first parse the task requirements item by item from the list of electrical inspection tasks, extracting attributes such as task type, expected execution time, prerequisites, target controller scope, required communication interface and task priority for each electrical inspection task. Then, these attributes are compared with the list of electrical inspection functions for each workstation to filter out a set of candidate workstations with execution capabilities.

[0115] Afterwards, the cloud platform combines production line operating parameters and workstation operating status to impose feasibility constraints on candidate workstations, excluding workstations that are faulty, offline, under maintenance, congested, or whose cycle time does not meet the conditions, and calculates the load evaluation value for the remaining candidate workstations.

[0116] In one possible implementation, the production line load model can be constructed using a weighted scoring model. The load evaluation value L of the production line load model can be calculated by weighted summation, and the selected parameters can be:

[0117] The cycle time parameter indicates the current estimated waiting time or cycle time deviation of the candidate electrical inspection station;

[0118] The task parameter indicates the number of vehicles queuing at the electrical inspection station or the number of tasks to be performed.

[0119] This indicates the penalty parameter for the electrical inspection station status penalty item, and sets the penalty parameter to a lower value when the electrical inspection station is in an idle state, and a middle value when it is in a state of imminent completion or light occupation.

[0120] The cost parameter represents the path reachability cost or transfer cost between the electrical inspection station and the current location of the vehicle.

[0121] By multiplying the above parameters by their corresponding weights and then summing these products, the cloud platform can select the electrical inspection station with the lowest load evaluation value that meets the functional constraints as the target matching station. If there are multiple electrical inspection stations with the same capabilities and similar loads for the same task, a balancing coefficient can be introduced to give higher priority to electrical inspection stations with fewer recent task loads, thereby reducing long-term load imbalance.

[0122] In another possible implementation, the cloud platform can first conduct a pre-assessment of the overall load capacity of each electrical inspection station based on the production line load model, form a station availability ranking table, and then allocate electrical inspection tasks to electrical inspection stations that meet the functional conditions in order of priority or dependency.

[0123] For example, higher priority is set for safety-related electrical inspection tasks that must be completed before the vehicle arrives at a specific area, and sequential constraints are set for verification tasks that depend on the results of previous parameter writing, so that subsequent tasks are matched only when the preceding task has been assigned and is executable.

[0124] If a workstation that meets the requirements cannot be found temporarily for a certain electrical inspection task, the cloud platform can mark the task as pending reassignment and re-execute the matching based on the updated operating status of the electrical inspection workstations in the next data collection cycle. For multiple tasks on the same vehicle, the cloud platform can also perform task aggregation based on the functional overlap of the electrical inspection workstations, and distribute a combination of tasks that can be completed continuously by the same workstation to reduce the waiting time caused by switching vehicles between different electrical inspection workstations.

[0125] Based on the above analysis, this step essentially establishes a dynamic mapping relationship between task requirements, workstation capabilities, and production line status. Compared to the static allocation method of fixed workstations, this embodiment incorporates cycle time, queue, status, and capacity information into the decision-making process through a production line load model. When a certain electrical inspection workstation is congested or malfunctioning, the corresponding electrical inspection task can be automatically transferred to other electrical inspection workstations with the corresponding functions, thereby alleviating the problem of both localized congestion and equipment idleness. For mixed-line production scenarios, the differences in electrical inspection tasks caused by configuration differences among different vehicle models can also be refined and identified during the matching stage, and the most suitable workstation can be selected accordingly. Therefore, it can improve the utilization rate of multi-workstation resources and enhance the continuous operation capability and overall testing efficiency of the entire electrical inspection production line.

[0126] S103. Based on the workstation information of the matched electrical inspection workstations, generate an electrical inspection task list and associate the first vehicle information with the electrical inspection task list.

[0127] For example, the workstation information in this embodiment is used to identify successfully matched electrical inspection workstations and their contextual attributes. Specifically, it may include one or more of the following: workstation identification information, workstation name, logical address, network address, production line segment location of the workstation, buffer zone number, current receiving window time, execution device identifier, and status summary. The electrical inspection task list is used to carry the matched electrical inspection tasks, workstation information, and their corresponding relationships. It is the direct data object for subsequent workstation issuance and electrical inspection task execution. The first vehicle information is written into the electrical inspection task list in this step to establish a stable binding relationship between the vehicle and the inspection task.

[0128] In one example, after the cloud platform matches electrical inspection tasks with electrical inspection stations, it can organize the task list data structure with the vehicle as the primary key. At this point, the system will create a master task list around the same vehicle, and record the target electrical inspection station, task order, issuance status, and execution status of each electrical inspection task under the master list.

[0129] It should be noted that the task list data structure can also be organized using the electrical inspection station as the primary key. In this case, the system will generate a sub-list to be executed for each vehicle for each station, and then map multiple sub-lists back to the same vehicle through the task association field.

[0130] In one possible implementation, the electrical inspection task list includes at least the following fields: list number, vehicle identifier, task item number, task name, target workstation identifier, estimated start time, estimated completion time, task dependencies, task priority, task parameters, result return address, and version number.

[0131] For electrical inspection tasks that require calling specific detection scripts or diagnostic commands, the above task parameters may also include the target controller address, diagnostic service number, threshold range, number of retries, timeout time, and result judgment rules. Pre-verification commands or status confirmation commands should be inserted when necessary to ensure the integrity of the execution logic at the workstation.

[0132] When associating the first vehicle information with the electronic inspection task list, this can be achieved by establishing a foreign key relationship between the vehicle information table and the task list table in the database, or by directly writing fields such as the vehicle identification number and electronic control unit serial number into the task list message body.

[0133] In one possible implementation, the cloud platform generates a unique task link identifier for the same vehicle and writes the identifier into the task list, execution log, and result record simultaneously, so that regardless of whether the electrical inspection task is assigned to one electrical inspection station or multiple electrical inspection stations, it can be tracked along the same link.

[0134] If the first vehicle information includes the vehicle identification number and configuration code, the cloud platform can also record the detection template version corresponding to the configuration code in the list to prevent the workstation from calling the wrong script due to differences in vehicle configuration.

[0135] For data management after the list is generated, the cloud platform can save the task list to a relational database or a time-series database and simultaneously generate a message queue to be sent. If the task needs to be reassigned due to changes in the workstation status, the cloud platform can generate a new version of the list based on the original list version, while retaining historical versions and reasons for changes, which facilitates production line quality traceability.

[0136] Through the process described in this embodiment, the scattered matching results are organized into an executable, sendable, and traceable data carrier. Simultaneously, by associating vehicle information, a complete correspondence is established from the vehicle to be inspected to the electrical inspection task list and then to the execution results at the electrical inspection station. Furthermore, after associating the generated electrical inspection task list with the first vehicle information, by querying vehicle connectivity information, electrical inspection tasks received by different electrical inspection stations can be clearly mapped to the same vehicle. The system can also continuously monitor the task execution chain of this vehicle throughout the entire electrical inspection production line, thereby improving the problem of weak data correlation between different stations and the difficulty in forming a whole-vehicle-level full-process tracking in the prior art. It also provides a unified data foundation for subsequent anomaly tracing, quality analysis, and production history preservation.

[0137] S104. Based on the workstation information, send the electrical inspection task list to the electrical inspection workstation.

[0138] For example, in the electrical inspection task list sending process of this application embodiment, the cloud platform determines the corresponding electrical inspection workstation based on the workstation information and sends the electrical inspection task list to that workstation so that the workstation receives and executes the electrical inspection tasks in the electrical inspection task list. The workstation information here is not only used to identify the sending target, but also to control the sending timing, message routing, and confirmation mechanism. For example, the workstation identification information can be used to address the corresponding workstation control terminal, the network address can be used to establish a Transmission Control Protocol (TCP) connection or message subscription channel, and the status-related information can be used to determine whether the current workstation is in a receptive state.

[0139] In one example, the cloud platform can send task lists to the workstations via communication protocols such as industrial message middleware, HyperText Transfer Protocol (HTTP), WebSocket long connections, Message Queuing Telemetry Transport (MQTT), or customized production line communication protocols.

[0140] If a message middleware approach is used, the cloud platform can configure each electrical inspection station as an independent topic or an independent queue, and encapsulate the electrical inspection task list into a structured message according to the station identifier before delivering it to the target electrical inspection station; the station terminal subscribes to the corresponding topic, receives the message, and verifies the list number, version number, and vehicle identifier in the message.

[0141] If the API call method is used, the cloud platform can send a signed task assignment request to the electrical inspection station controller based on the network address in the workstation information. After receiving the request, the electrical inspection station controller will return a receipt confirmation code.

[0142] To ensure accuracy, the cloud platform can re-verify the operational status of the electrical inspection station before sending data. If the station is detected to have switched from an available state to a faulty or offline state, the current sending is paused and a re-matching process is triggered. For task lists that have been sent but have not received confirmation, the cloud platform can resend the data according to a preset number of retries. If the retry limit is exceeded, the task is marked as an abnormal sending and an alarm is recorded for administrators to handle.

[0143] In one possible implementation, after the electrical inspection task list is sent, the workstation terminal will send back the successful reception status, estimated execution time, and queue position to the cloud platform. The cloud platform will then update the task list status to "issued," "pending execution," or "in execution."

[0144] Similarly, after completing the corresponding electrical inspection task, the workstation uploads the test results, original diagnostic data, execution logs, and abnormal information to the cloud platform. The cloud platform then binds these results with the previously associated first vehicle information and task link identifier to achieve closed-loop management.

[0145] In another possible implementation, if a certain electrical inspection station supports local caching, the cloud platform can send a task list in advance before the electrical inspection station approaches the vehicle receiving window, so that the electrical inspection station can start the inspection immediately after the vehicle arrives without waiting for the dispatch instruction again, thereby reducing idle time.

[0146] If the workstation status information indicates that the current workstation load is high, the cloud platform can also control the timing of the transmission, delaying the task list until its receiving window is open before sending it, in order to avoid the accumulation of invalid pending tasks at the workstation.

[0147] Through the process described in this embodiment, the task decisions formed on the cloud platform side are converted into executable instructions on the workstation side, and precise downward distribution and status closure confirmation are achieved through workstation information. This not only enables each electrical inspection workstation to execute corresponding electrical inspection tasks according to the unified scheduling results, but also allows for continuous verification of the availability and receiving status of the electrical inspection workstations before and after transmission, reducing the problems of incorrect or missed task transmission caused by communication anomalies, sudden changes in workstation status, or manual switching, thereby improving the accuracy and efficiency of electrical inspection task distribution and enhancing the stability of multi-workstation collaborative operation.

[0148] This application provides a vehicle electrical inspection method that centrally accesses vehicle information, workstation capacity information, and real-time production line status information through a cloud platform. It constructs a unified task matching and distribution chain for multi-workstation scenarios, transforming the electrical inspection process, which originally relied on fixed rules and was executed independently by dispersed workstations, into a dynamic collaborative process based on the overall production line load. This enables a more reasonable matching of the relationship between vehicle information, workstation capacity, and production line status under conditions of mixed-line production, overlapping workstation capabilities, and fluctuating cycle times. It improves task allocation flexibility, reduces local congestion and resource idleness, increases overall production line inspection efficiency, and enhances the continuous tracking capability of cross-workstation task chains.

[0149] It should be understood that the above examples are merely illustrative and not limiting. The production line load model, communication method, task list field structure, and workstation capability expression form in the embodiments of this application can all be adjusted according to the specific production line architecture. As long as dynamic matching, list generation, and targeted distribution of tasks to be inspected can be achieved, they all fall under the technical ideas disclosed in the embodiments of this application.

[0150] Figure 2 The flowchart of the vehicle electrical inspection method applicable to the cloud platform provided in this application is as follows. Figure 2 ,like Figure 2 As shown, in this embodiment... Figure 1 Based on the embodiments, the vehicle electrical inspection method is described in detail, which includes:

[0151] S201. Real-time collection of production line operation parameters of the electrical inspection production line, workstation operation status of the electrical inspection station and information on tasks to be inspected. Among them, the information on tasks to be inspected shall include at least the information of the first vehicle and the list of electrical inspection tasks, and the list of electrical inspection tasks shall contain at least one electrical inspection task.

[0152] S202. Based on the list of electrical inspection functions and the list of electrical inspection tasks, generate a list of workstations corresponding to the electrical inspection tasks.

[0153] S203. Based on the production line operating parameters and workstation operating status, and according to the production line load model, calculate the workstation production cycle time for the electrical inspection workstation in the workstation list to complete the corresponding electrical inspection task.

[0154] S204. Based on the production cycle time of each workstation, perform a feasibility check on the workstation list.

[0155] S205. When the workstation list passes the feasibility verification, based on the workstation list, any electrical inspection task will be matched to the corresponding electrical inspection workstation.

[0156] S206. Based on the workstation information of the matched electrical inspection workstations, generate an electrical inspection task list and associate the first vehicle information with the electrical inspection task list.

[0157] S207. Based on the workstation information, send the electrical inspection task list to the electrical inspection workstation.

[0158] For example, the electrical inspection function list characterizes the various electrical inspection tasks that each electrical inspection station can undertake. It is typically maintained in advance by the cloud platform and correlated with electrical inspection station numbers or electrical inspection equipment numbers to identify whether a particular electrical inspection station is capable of performing a specific electrical inspection task. The electrical inspection task list records the inspection items for vehicles undergoing electrical inspection and their required functional sets. The station list contains a set of candidate electrical inspection stations that meet the inspection conditions, serving as an intermediate result for task matching and feasibility assessment. The station production cycle time represents the time required for a candidate station to complete its corresponding electrical inspection task; its value reflects the station's current load level and its ability to handle tasks.

[0159] In one example, after the cloud platform obtains the list of electrical inspection tasks, it first parses the electrical inspection function requirements corresponding to each electrical inspection task, then compares the function requirements with the list of electrical inspection functions, filters out electrical inspection workstations with corresponding testing capabilities, and organizes the filtering results into a workstation list.

[0160] Subsequently, the cloud platform inputs production line operating parameters and workstation operating status into the production line load model. Production line operating parameters may include production line load, number of vehicles under online inspection, number of vehicles awaiting inspection, bottleneck workstation identification, workstation spacing and transport speed, capacity deviation, and production line cycle time baseline parameters (maximum total instruction duration), among other relevant parameters. Workstation operating status may include idle, occupied, maintenance, or abnormal status, and may also include workstation communication quality, equipment health, vehicle dwell time, and estimated departure time. Based on this, the production line load model outputs the workstation production cycle time for each candidate workstation to complete the corresponding electrical inspection task.

[0161] For example, it can be set that if the production cycle time of a workstation predicted by the model is less than a preset cycle time threshold, or if it meets the cycle time comparison constraint with other candidate workstations, the workstation list is deemed to have passed the feasibility check; if it does not meet the constraint, the workstation list is deemed unusable for the current task allocation. After passing the check, the cloud platform determines the electrical inspection workstation corresponding to any electrical inspection task based on the workstation list and establishes a mapping relationship between electrical inspection tasks and electrical inspection workstations.

[0162] The above method allows for the initial construction of a candidate workstation set based on functional matching, followed by calculation and verification of the load-bearing cycle time in conjunction with the real-time production line status. This avoids workstations lacking capacity or with excessive loads from being assigned. This approach enables electrical inspection tasks to be dynamically matched to suitable workstations based on production line operation, improving multi-workstation collaboration efficiency, reducing waiting and idle time, enhancing the adaptability and stability of electrical inspection scheduling, and ultimately improving the overall testing throughput and resource utilization of the electrical inspection production line.

[0163] In one possible implementation, the feasibility of the workstation list is verified based on the workstation production cycle time, including: calculating the task execution time corresponding to the workstation list based on the workstation production cycle time and the estimated dwell time; when it is determined that the task execution time is less than or equal to the set total instruction time, identifying the first necessary electrical inspection task in the workstation list; matching the first necessary electrical inspection task with the second necessary electrical inspection task in the electrical inspection task list, and verifying the feasibility of the workstation list based on the matching result.

[0164] For example, the workstation production cycle time is used to characterize the time required for the electrical inspection workstation to complete the corresponding electrical inspection task; the estimated dwell time is used to characterize the expected dwell time of the vehicle or task at the electrical inspection workstation; the task execution time is used to characterize the overall execution time of the corresponding electrical inspection task in the workstation list; and the total instruction duration is used to limit the total time limit for the execution of the electrical inspection task. The first necessary electrical inspection task is used to characterize the electrical inspection task in the workstation list that has a high correlation with the electrical inspection indicators of the current vehicle passing through this workstation and needs to be checked in detail; the second necessary electrical inspection task is used to characterize the task item corresponding to the necessary electrical inspection task in the electrical inspection task list of the vehicle being inspected; and the matching result is used to characterize whether the correspondence between the first and second necessary electrical inspection tasks meets the requirements.

[0165] In one example, after generating the workstation list, the cloud platform first obtains the workstation production rhythm based on the production line load status of each electrical inspection workstation, the workstation occupancy status, and the standard operation time of the corresponding task. Then, it estimates the estimated dwell time by combining the vehicle's historical dwell time at the workstation, the current queue length, and the task complexity, and performs correlation calculations between the two to obtain the task execution time.

[0166] It should be noted that when calculating the task execution time, parameters related to the workstation's operating status, such as workstation communication quality and equipment health, can be combined to calculate the availability weight of the current workstation, and then the workstation's production cycle time can be adjusted using this availability weight.

[0167] The above-mentioned correlation operation in the embodiments of this application can be performed by addition or by weighted calculation, so that the task execution time can reflect the actual capacity of the workstation and the task occupancy.

[0168] When the execution time of a task is determined to be less than the total duration of the instruction, the system also selects the electrical inspection tasks marked as necessary for the current electrical inspection station from the workstation list as the first necessary electrical inspection tasks, and compares them one by one with the second necessary electrical inspection tasks in the electrical inspection task list. If the correspondence is consistent and the preset matching conditions are met, the workstation list is determined to pass the feasibility check.

[0169] It should be noted that when conducting feasibility verification, strong constraints can be set for the boundaries of multiple electrical test intervals. For example, two electrical test intervals can be set. The first electrical test interval is a static electrical test interval, which includes boundary constraints such as front compartment electrical test, functional test, ECU calibration, and communication test. The second electrical test interval can only be entered after the above electrical test tasks are completed. The second electrical test interval is a dynamic verification interval, which can include boundary constraints such as road test electrical test, final test, functional retest, and release test. It is a key and necessary electrical test instruction that cannot be omitted.

[0170] This application embodiment links workstation cycle time, estimated dwell time, and task upper limit constraints, so that the workstation list is first filtered by the time dimension and then verified by the necessary task dimension. This avoids configuring workstation lists that exceed the carrying capacity or cannot cover necessary electrical inspection tasks as pending objects, which can improve the accuracy of workstation list feasibility determination and reduce repeated scheduling and execution failures caused by workstation capacity mismatch or omission of key tasks.

[0171] In one possible implementation, the method further includes: when all the first necessary electrical inspection tasks are matched with the second necessary electrical inspection tasks, determining that the workstation list has passed the feasibility check.

[0172] For example, the first necessary electrical inspection task is used to characterize the critical electrical inspection tasks that must be covered in the workstation list, and the second necessary electrical inspection task is used to characterize the task item corresponding to the necessary electrical inspection task in the electrical inspection task list of the electrical inspection vehicle. The matching relationship between the two is used to determine whether the workstation list can fully meet the necessary inspection requirements set by the electrical inspection vehicle. The workstation list can be understood as a set of workstations and their corresponding task allocation results formed by the system based on the electrical inspection function of the workstation, production line operating parameters, and workstation operating status. Each task in the workstation list corresponds one-to-one with a specific electrical inspection workstation.

[0173] In one example, after generating the workstation list, the cloud platform extracts the first necessary electrical inspection tasks from the workstation list one by one and compares them with the second necessary electrical inspection tasks in the electrical inspection task list. This comparison process can be based on task name, task code, function tag, test object, constraint conditions, or a preset mapping table. The preset mapping table is used to record the allowed correspondence between the first and second necessary electrical inspection tasks to avoid misjudgment due to differences in task descriptions.

[0174] The workstation list generated by the cloud platform is deemed to have passed feasibility verification if and only if all first necessary electrical inspection tasks in the workstation list find a second necessary electrical inspection task that meets the preset matching rules, and if there are no omissions, conflicts, or duplicate occupations in the correspondence. This determination result will then be used as the basis for issuing subsequent electrical inspection tasks. If any first necessary electrical inspection task fails to find a corresponding second necessary electrical inspection task, it indicates that the task coverage in the workstation list is incomplete, and the system will determine that the workstation list has failed feasibility verification.

[0175] In this embodiment of the application, the above matching rules can be jointly limited by the consistency of electrical inspection functions, the constraints of the inspection sequence, and the carrying capacity of the workstation, so as to ensure that the inspection capability corresponding to the first necessary electrical inspection task can indeed be undertaken by the workstation described by the second necessary electrical inspection task.

[0176] Through the above processing, the feasibility assessment of the workstation list no longer relies solely on workstation cycle time or the status of a single piece of equipment. Instead, it further verifies whether the necessary electrical inspection tasks have been fully undertaken, thereby ensuring that the generated workstation list accurately reflects the current production line's coverage of the necessary electrical inspection content for vehicles. This reduces the risks of task omissions, workstation mismatches, and subsequent rework, and improves the accuracy of electrical inspection allocation and overall execution stability under multi-workstation collaboration.

[0177] In one possible implementation, the method further includes: when at least two workstation lists pass the feasibility check, calculating the cumulative sum of the workstation production cycle times; and matching any electrical inspection task to the corresponding electrical inspection workstation based on the workstation list with the smaller cumulative sum.

[0178] For example, the workstation list refers to the set of candidate electrical inspection workstations corresponding to the electrical inspection tasks to be performed on the vehicles to be inspected. The workstation production takt time is used to characterize the work rhythm or time required for each candidate electrical inspection workstation to complete the assigned electrical inspection task, which is usually determined by the current load of the workstation, the equipment response time, and the complexity of task execution. The cumulative sum is the sum of the production takt times corresponding to each electrical inspection workstation in the same workstation list that has passed the feasibility verification, so as to reflect the overall takt time level of these electrical inspection workstations when undertaking the corresponding electrical inspection tasks.

[0179] When multiple workstation lists meet the feasibility requirements, the cloud platform or production line controller extracts the corresponding electrical inspection workstation production cycle time from each workstation in each workstation list, and performs cumulative calculation according to a unified dimension to obtain the cumulative sum of the production cycle times of each workstation.

[0180] Then, the sums of the different workstation lists are compared, and the workstation list with the smaller value is selected as the optimal workstation list. At this time, the time spent performing the electrical inspection task is the shortest, the load on the overall electrical inspection operation is lower, and the task response is faster. Therefore, according to the correspondence between the electrical inspection tasks and electrical inspection workstations in this workstation list, the task allocation and workstation determination are completed.

[0181] The processing method described in this application embodiment, when there is a candidate workstation list on the production line with multiple workstations capable of performing the same electrical inspection task for vehicles awaiting inspection, can filter candidate solutions based on the total cycle time, prioritizing the allocation of electrical inspection tasks to workstation sets with lower overall cycle times. This reduces the probability of local workstation congestion, shortens task waiting time, and improves the utilization efficiency of electrical inspection resources under multi-workstation collaborative conditions. By using the cumulative cycle time value as the priority selection criterion, the task allocation result can also better match the real-time load status of the production line, enhancing the continuity and stability of the vehicle assembly line electrical inspection process.

[0182] In one possible implementation, the method further includes: when the workstation list fails the feasibility check, sequentially determining whether the electrical inspection tasks in the workstation list are necessary electrical inspection tasks; if not, marking the corresponding electrical inspection tasks and generating electrical inspection prompt information based on the marking results; if yes, recording the corresponding electrical inspection tasks as pending electrical inspection tasks and matching the pending electrical inspection tasks to alternative electrical inspection workstations, wherein the alternative electrical inspection workstation is the adjacent electrical inspection workstation of the electrical inspection workstation corresponding to the pending electrical inspection task in the workstation list, and the electrical inspection function list of the adjacent electrical inspection workstation contains the electrical inspection function corresponding to the pending electrical inspection task.

[0183] For example, the workstation list is used to represent the set of workstations associated with the electrical inspection tasks of the same vehicle to be inspected, and their corresponding task relationships. If the workstation list fails the feasibility check, it means that there are at least one electrical inspection task in the current list that cannot be executed according to the vehicle electrical inspection task plan. This could be due to the omission of a necessary electrical inspection task, or it could be due to a mismatch in production cycle time.

[0184] The aforementioned necessary electrical inspection tasks can refer to those with strong constraints on vehicle electrical safety, critical communication connectivity, or basic vehicle functions, or they can be prerequisites for the planned electrical inspection tasks in the next electrical inspection phase. Non-essential electrical inspection tasks are those that have a relatively small impact on the completeness of the current inspection and can be handled through prompts. The marking of electrical inspection tasks can be written to the task status field or the task record table. Electrical inspection prompts are used to notify production line management, workstation terminals, or operators of non-essential electrical inspection tasks that require attention in the current checklist.

[0185] In one example, after determining that the workstation list has failed the feasibility check, the system reads the task attribute information item by item according to the order of the electrical inspection tasks in the workstation list, and combines the task type, task priority, vehicle configuration constraints and process rules or other task information to determine whether the task is a necessary electrical inspection task.

[0186] For tasks deemed unnecessary electrical inspections, the system marks the task with a status and generates an electrical inspection prompt message by combining the task name, workstation, reason for failure, and suggested handling method, so as to remind production line personnel to check or manually confirm.

[0187] For cases where an electrical inspection task is deemed necessary, the system identifies the task as an electrical inspection task to be performed from the original workstation list and searches among adjacent electrical inspection workstations to see if there is a workstation with the corresponding electrical inspection function. If so, the electrical inspection task to be performed is bound to the alternative workstation, so that it can continue to be performed at the alternative workstation, thereby ensuring the compliance of the electrical inspection operation.

[0188] In this application embodiment, the determination of the alternative electrical inspection station can be based on the station topology relationship and station capability constraints. The adjacent electrical inspection station can be the adjacent station in the production line running direction, or it can be the adjacent station that can logically continue to undertake the task. Moreover, its electrical inspection function list must at least contain the electrical inspection function corresponding to the electrical inspection task to be performed.

[0189] Through the processing method described in this application embodiment, the system can distinguish between non-essential and essential tasks when the original workstation list is unexecutable, and take prompting and reassignment measures accordingly. This clearly identifies electrical inspection tasks that can be postponed, while ensuring that essential electrical inspection tasks can still be completed at adjacent workstations with available capacity. This guarantees the continuity of electrical inspection tasks and reduces the risk of entire orders failing due to single-point unavailability. Simultaneously, this processing method also improves workstation resource utilization, reduces the time spent manually rescheduling tasks, and enhances the adaptability and stability of the assembly line electrical inspection scheduling.

[0190] In one possible implementation, the first vehicle information is: the vehicle identification number and / or the electronic control unit serial number associated with the vehicle identification number.

[0191] For example, the Vehicle Identification Number (VIN) is used to uniquely identify the entire vehicle. It is typically carried by a vehicle nameplate, a windshield visible area identifier, a QR code label, or the vehicle master data record in the production management system, and is associated with all electronic inspection records of the vehicle during manufacturing, off-line testing, and final inspection. The Electronic Control Unit (ECU) serial number bound to the VIN is used to further identify specific controllers on the vehicle. The ECU serial number can be formed by the factory code of the engine control unit, vehicle control unit, power battery management unit, body control unit, or other on-board controllers, and is pre-bound to the corresponding VIN through the production execution system so that after the vehicle enters the electronic inspection production line, the vehicle to be inspected can be determined based on the vehicle identifier and the ECU identifier of the same vehicle.

[0192] In one example, after receiving the information for the electrical inspection task, the cloud platform can first read the vehicle identification number (VIN) and use it as a vehicle-level index. Then, it can retrieve the corresponding configuration list, historical inspection records, and the electrical inspection task to be performed from the database. When the VIN is insufficient to distinguish the differences in controllers under different configurations of the same vehicle model, the system can further read the electronic control unit (ECU) serial number bound to the VIN and associate this serial number with the target electrical inspection task, thereby accurately locating the controller node, communication link, or functional item that needs to be inspected.

[0193] By using the vehicle identification number and / or the electronic control unit serial number bound to the vehicle identification number as the first vehicle information, the cloud platform can achieve continuous identification and cross-workstation association of the same vehicle when generating the electrical inspection task list. This avoids task mismatch, record confusion and traceability difficulties caused by non-unique vehicle identification or disconnected controller information, thereby improving the accuracy of electrical inspection task allocation, the consistency of test data and the production line quality traceability capability.

[0194] In one possible implementation, the method further includes: receiving and storing the electrical inspection results uploaded by the electrical inspection production line.

[0195] For example, the above-mentioned electrical inspection results are the detection output information generated by the electrical inspection station after completing the vehicle's electrical inspection. The electrical inspection results may include the completion status of the electrical inspection task, the test pass result, the anomaly code, the original measurement value, and the station identification information. An electrical inspection production line refers to a production line with multiple electrical inspection stations used to perform electrical inspection tasks on vehicles. The electrical inspection production line can upload the results to a cloud platform via industrial Ethernet, wireless LAN, or fieldbus.

[0196] After receiving the electrical inspection results, the cloud platform can write them to the corresponding data storage unit and establish a correlation index based on the first vehicle information, enabling unified retrieval and traceability of inspection records generated by the same vehicle at different workstations. The aforementioned data storage unit can be a relational database, a distributed storage server, or object storage space; this application embodiment does not limit this approach.

[0197] In one example, after completing an electrical inspection task, the inspection terminal at the electrical inspection station encapsulates the collected inspection data along with the task identifier, vehicle identifier, and timestamp to form a standardized operation result message. This message is then sent to the cloud platform via the communication module at the station. The cloud platform's receiving module parses the message, categorizes the results based on the vehicle identifier and task identifier in the message fields, and saves the execution status and inspection output information, thus creating a traceable electrical inspection file.

[0198] When the test results contain abnormal information, the cloud platform can also simultaneously retain the abnormal report code and the corresponding workstation information for subsequent querying, statistics or alarm triggering, realizing closed-loop data processing of "error reporting → location → push → rework".

[0199] The working principle of the above data processing method is to uniformly aggregate the output results of each electrical inspection station after completion of the inspection to the cloud platform, and realize queries by vehicle, workstation, or task through storage and association mechanisms. This ensures that the result data in the electrical inspection process is not lost or scattered, and forms a closed loop with the aforementioned task matching process.

[0200] By adopting the above method, the results of electrical inspection operations can be centrally stored and managed in a unified manner, which facilitates the subsequent traceability of single-vehicle inspection records, analysis of workstation operation quality, and review and statistics of abnormal work orders, thereby improving the integrity and availability of electrical inspection data and the production line's quality control capabilities.

[0201] In one possible implementation, the method further includes: parsing the electrical inspection operation results; when it is determined that the electrical inspection operation results contain an electrical inspection abnormality code, performing electrical inspection abnormality location based on the electrical inspection abnormality code, and determining the electrical inspection station and corresponding electrical inspection task corresponding to the electrical inspection abnormality code.

[0202] For example, the result of an electrical inspection operation is the output data of the electrical inspection station after completing the vehicle's electrical inspection task. It typically includes fields such as inspection item identifier, judgment result, anomaly identifier, and anomaly code. The electrical inspection anomaly code is used to characterize the type, source, or location of anomalies that occur during the execution of a specific electrical inspection task. It can be generated and written into the result message by the station controller, inspection terminal, or upper-level platform when there is a detection failure, communication interruption, threshold exceeding the limit, or equipment feedback anomaly. The electrical inspection station refers to the station that performs the corresponding electrical inspection task, and the electrical inspection task refers to the specific electrical inspection item associated with the vehicle being inspected, such as communication testing, function activation testing, or parameter verification testing.

[0203] In one example, when parsing the results of an electrical inspection, the result message can be first structured and split to identify the field labels and value ranges. Then, the exception code field can be compared with the preset parsing rules to determine whether there is an electrical inspection exception code. When the result is in JSON, XML, tabular record, or fixed-length message format, the exception code field can also be extracted according to the corresponding format.

[0204] When locating electrical inspection anomalies based on electrical inspection anomaly codes, a pre-established anomaly code mapping table can be invoked to associate and retrieve the anomaly code with the electrical inspection station identifier, station address, and task number. This determines which electrical inspection station the anomaly occurred at and the specific electrical inspection task being performed at that station. The mapping table can be stored in a cloud platform database and updated synchronously with the electrical inspection task list to ensure consistency between anomaly location and the current production line execution status.

[0205] Once the electrical inspection anomaly code is identified, along with the corresponding electrical inspection station and task, the cloud platform can generate an anomaly alarm and send the information to the production management system or the corresponding station terminal for re-inspection, reassignment of the task, or manual intervention.

[0206] By using the above processing methods, abnormal results can be linked to specific electrical inspection stations and specific electrical inspection tasks, which facilitates tracing the source of abnormalities, shortens fault location time, and improves the accuracy and consistency of production line electrical inspection result management.

[0207] Figure 3 The flowchart of the vehicle electrical inspection method applicable to the electrical inspection production line provided in this application is as follows: Figure 3 As shown, the method includes:

[0208] S301. Obtain the second vehicle information of the vehicle to be inspected and the first vehicle information in the electric inspection task list.

[0209] For example, an electrical inspection production line, serving as the implementation environment for vehicle electrical inspection operations, typically includes a conveying mechanism, at least two electrical inspection stations, station inspection terminals, a vehicle identification unit, and a data processing unit that communicates with a task management system. The electrical inspection stations are used to carry out specific electrical inspection operations. Different stations can have different inspection capabilities or the ability to perform the same inspection capabilities in parallel, thus enabling the same production line to have the operational foundation for continuous inspection of multiple vehicles.

[0210] The vehicle awaiting electrical inspection is either currently entering or about to enter the current electrical inspection station. The second vehicle information identifies the vehicle and its associated inspection attributes. The first vehicle information is stored in the electrical inspection task list issued to the electrical inspection station, representing the target vehicle corresponding to that task list. The electrical inspection task list is a task carrier generated by the upstream cloud platform based on vehicle information, station capabilities, and production line status. In addition to the first vehicle information, it may also include the task number, station number, set of inspection items, task generation time, effective task period, and execution order.

[0211] In one possible implementation, the above process can be executed by a workstation controller, edge computing terminal, or production line central control server located at the electrical inspection station. When a vehicle to be inspected enters the predetermined identification area via the conveyor line, the vehicle's body identification information is first collected by a vehicle identification device. For example, second vehicle information can be obtained by scanning the vehicle body barcode, reading the vehicle identification number, identifying the RFID electronic tag, reading the identity data pre-written by the on-board controller, or calling the point binding record in the manufacturing execution system; alternatively, the license plate, body code, or vehicle tag can be image-recognized by a camera device, and structured vehicle identification data can be formed after character parsing.

[0212] To ensure recognition stability, multiple consecutive reads can be performed, followed by deduplication, verification, and timestamp binding. The read results are then uploaded to the workstation controller to form the second vehicle information for the current vehicle. The second vehicle information may include at least one of the following: vehicle identification number, vehicle model code, configuration code, order number, vehicle serial number, and production batch number. In practice, the data field that can uniquely identify the vehicle and establish a corresponding relationship with the electrical inspection task list is usually selected as the primary matching field.

[0213] The above process serves as a preliminary identification and task verification step within the overall methodology. In existing assembly line scenarios, when vehicles of different models and configurations are running in mixed flow on the same line, misalignment may occur between the task list and the actual arriving vehicles due to queuing changes, manual intervention, buffer delays, or fluctuations in transport pace.

[0214] By obtaining corresponding vehicle information from both the vehicle entity side and the task list side before performing the inspection, and constructing a dual-source verification mechanism, the risk of false detection, missed detection, or incorrect detection caused by relying on information from only a single source can be reduced. This ensures that subsequent electrical inspection operations are based on the confirmation that the vehicle and the task correspond, thereby improving the accuracy of task execution and the traceability of the production line process under multi-station collaborative conditions.

[0215] S302. Determine whether the second vehicle information matches the first vehicle information. If yes, perform an electrical inspection on the vehicle to be inspected based on the electrical inspection task list. If no, generate an electrical inspection alarm message. The electrical inspection task list is a list generated according to the vehicle electrical inspection method provided above.

[0216] For example, the matching determination of the second vehicle information and the first vehicle information is used to confirm whether the currently arrived vehicle is the intended target for the electrical inspection task list. Both the first and second vehicle information can contain vehicle identification content that can be used for matching determination, such as one or more of the following: vehicle identification number, production serial number, vehicle configuration code, and order identifier. The electrical inspection operation is the actual electrical inspection test process performed at the electrical inspection station after successful matching. It may include controller communication testing, wiring harness connectivity confirmation, function activation check, parameter reading verification, fault code reading, actuator action testing, and confirmation of the vehicle's electrical status. The electrical inspection alarm information is abnormal prompt data generated when vehicle information matching fails. Its purpose is to indicate that the electrical inspection task is inconsistent with the vehicle entering the electrical inspection station, preventing non-compliant electrical inspection processes for that vehicle.

[0217] In one example, after obtaining the second and first vehicle information, the workstation controller can invoke preset matching rules for judgment. For instance, the system first performs a primary key field comparison, directly comparing the vehicle identification number in the second vehicle information with the vehicle identification number in the first vehicle information. When the primary key field is missing, incompletely identified, or requires error tolerance, a combined field matching method can be further adopted, that is, combining the vehicle model code, configuration code, and serial number with the corresponding fields in the task list for joint verification.

[0218] To improve the stability of field applications, the matching rules can also be configured to standardize the format, such as unifying letter case, removing separators, truncating valid characters, cleaning up abnormal spaces, and then performing a consistency comparison.

[0219] If the judgment result is a match, it means that the current vehicle to be inspected and the electrical inspection task list are in a corresponding relationship. The workstation controller sets the status of the task list to "allow execution" or "pending execution confirmation" and calls the interface of the electrical inspection equipment corresponding to the inspection items in the list to start the electrical inspection operation in the order of tasks.

[0220] During the electrical inspection process, the workstation controller can first parse the item content, execution conditions and result record template in the electrical inspection task list, and then send test commands to the corresponding testing instruments, communication diagnostic equipment or vehicle bus interface.

[0221] For example, for communication-related testing items, session establishment and data reading commands can be sent to the target controller via CAN, LIN, Ethernet, or other vehicle communication interfaces, and the response messages returned by the controller can be received and parsed into parameter values ​​or status values. For actuator testing items, motion control commands can be sent to the vehicle, and the completion of the action can be confirmed by feedback sensors or controller status bits. For parameter verification items, the software version, calibration parameters, and configuration entries in the control unit can be read and compared with the preset standard range in the task list.

[0222] After each test is completed, the workstation controller generates a corresponding result record, including the project number, collected value, judgment result, execution time, and equipment identifier, and writes the result to the local database or uploads it to the upper-level management system. After all projects are completed, the vehicle electrical inspection result can be marked as passed, failed, or pending re-inspection, and the on-site display terminal can be driven to display the processing status. At the same time, a release or interception signal is fed back to the conveyor control system, so that subsequent workstations can continue to process the vehicle based on the result.

[0223] If the information of the second vehicle does not match the information of the first vehicle, the corresponding electrical inspection operation will not be initiated, and an electrical inspection alarm will be generated. The electrical inspection alarm may include alarm number, workstation number, current time, information of the second vehicle, information of the first vehicle, mismatch field, task list number, alarm level, and processing status.

[0224] For example, alarm data can be encapsulated in a preset message format within the workstation controller and simultaneously sent to the on-site audible and visual alarm module, workstation display screen, production line monitoring platform, and manufacturing execution system. At the on-site level, a flashing red indicator light, a buzzer sound, or a pop-up notification on the terminal interface can be triggered to remind the operator that the current vehicle is inconsistent with the task. At the system level, the vehicle status can be set to abnormal interception, the subsequent automatic detection process at that workstation can be suspended, and a request can be made to the scheduling system to re-verify the task list or reassign the task.

[0225] The technical solution described in this application introduces a verification mechanism between vehicle information on the task list and on-site vehicle information in at least two electrical inspection workstations on the electrical inspection production line. This ensures that workstation execution no longer relies solely on the static content of the issued tasks, but rather completes a final confirmation with the actual vehicle upon its arrival. After confirmation of consistency, the corresponding inspection items are executed according to the electrical inspection task list, and alarms are generated and erroneous processes are blocked immediately in case of inconsistency. This approach can both accommodate the dynamic task allocation results from the cloud platform across multiple workstations and ensure the consistency between tasks and vehicles at the on-site execution end, thereby reducing the probability of false detections, missed detections, and incorrect releases in mixed-line production scenarios, and improving the detection accuracy, anomaly response efficiency, and end-to-end quality traceability of the entire electrical inspection production line.

[0226] In one possible implementation, the method further includes: packaging the electrical inspection results of the vehicle to be inspected and uploading the packaged data.

[0227] For example, a vehicle awaiting electrical inspection refers to a target vehicle that has entered the inspection process and whose electrical inspection results need to be compiled and uploaded. The electrical inspection results characterize the detection output obtained by the vehicle during the electrical inspection process, and typically include information such as detection status, test values, abnormal prompts, or judgment conclusions. Packaging refers to encapsulating, summarizing, or compressing the electrical inspection results according to a preset data organization method to form a data package suitable for transmission and storage. Uploading refers to sending the packaged data to an external server, cloud platform, or production management system via network communication for centralized storage and subsequent analysis.

[0228] In one example, after completing the inspection of a vehicle, the electrical inspection terminal can first read the corresponding work result for that vehicle from the local cache, inspection controller, or workstation database, and synchronously associate it with vehicle identification information, workstation number, inspection timestamp, and task identifier to ensure the traceability of the result data. Subsequently, the system can encapsulate the above information into a unified message according to a preset data format. The message may contain result fields, status fields, and identifier fields, thereby ensuring that it can be accurately parsed and matched by the upper-level system after being uploaded.

[0229] To adapt to different production line deployment environments, packaging can adopt structured coding or compression and encapsulation of the original test records to reduce transmission overhead and improve data consistency. Uploading can be triggered immediately after the test is completed, or it can be sent in batches when the network is idle, or it can be sent when the cache threshold, task completion flag, or manual confirmation conditions are met, thus balancing real-time performance and communication stability.

[0230] Through the above methods, the results of electrical inspection are standardized and organized before leaving the workstation. After being uploaded, they can enter a unified data management platform, enabling the inspection records of the same vehicle to be associated with the corresponding task chain of the production line. This processing method helps reduce the problems of result loss and information dispersion, improves the traceability, queryability, and centralized control capabilities of inspection data, and also facilitates subsequent quality statistics, anomaly analysis, and production traceability, thereby improving the data management efficiency and collaborative control capabilities of the entire electrical inspection production line.

[0231] Figure 4 The structural schematic diagram of the vehicle electrical inspection device applicable to the cloud platform provided in this application is as follows: Figure 4 As shown, the vehicle electrical inspection device 40 provided in this embodiment is applicable to a cloud platform. The cloud platform is communicatively connected to at least one electrical inspection production line. The electrical inspection production line is equipped with at least two electrical inspection stations. The vehicle electrical inspection device 40 includes:

[0232] The data acquisition module 401 is used to collect the production line operation parameters of the electrical inspection production line, the workstation operation status of the electrical inspection station, and the information of the tasks to be inspected in real time. The information of the tasks to be inspected includes at least the information of the first vehicle and the list of electrical inspection tasks, and the list of electrical inspection tasks includes at least one electrical inspection task.

[0233] The matching module 402 is used to match any electrical inspection task to the corresponding electrical inspection station based on the electrical inspection function list, production line operating parameters, electrical inspection task list and station operating status of the electrical inspection station, and according to the production line load model; wherein, the electrical inspection function list contains the electrical inspection functions that can be executed by the corresponding electrical inspection station.

[0234] The association module 403 is used to generate an electrical inspection task list based on the workstation information of the matched electrical inspection workstations, and associate the first vehicle information with the electrical inspection task list;

[0235] The sending module 404 is used to send the electrical inspection task list to the electrical inspection workstation based on the workstation information.

[0236] In this embodiment, the acquisition module 401 synchronously acquires production line operating parameters, workstation operating status, and tasks to be inspected, enabling the cloud platform to grasp the real-time correspondence between vehicles, electrical inspection tasks, and on-site cycle time, thus providing a unified data foundation for subsequent task scheduling. The matching module 402 combines the electrical inspection function list and workstation operating status of each workstation and matches electrical inspection tasks according to the production line load model, allowing inspection items that were originally executed according to fixed rules to be dynamically allocated according to workstation capacity and current load, thereby reducing local workstation congestion and other workstation idleness. The association module 403 generates an electrical inspection task list based on the matching results and associates it with the first vehicle information, enabling the continuous organization of the task acceptance relationship of the same vehicle at different workstations, thus facilitating cross-workstation tracking of the task execution chain. The sending module 404 then sends the electrical inspection task list to the corresponding workstations, enabling on-site workstations to perform inspections according to unified scheduling results, improving multi-workstation collaboration efficiency, task adaptability, and the overall inspection efficiency of the entire electrical inspection production line.

[0237] In one possible implementation, based on the electrical inspection function list of the electrical inspection station, production line operating parameters, electrical inspection task list, and station operating status, and according to the production line load model, any electrical inspection task is matched to the corresponding electrical inspection station, including:

[0238] Based on the list of electrical inspection functions and the list of electrical inspection tasks, generate a list of workstations corresponding to the electrical inspection tasks;

[0239] Based on production line operating parameters and workstation operating status, and according to the production line load model, calculate the workstation production cycle time for completing the corresponding electrical inspection task in the workstation list.

[0240] Based on the production cycle time of each workstation, the feasibility of the workstation list is verified.

[0241] Once the workstation list passes the feasibility check, any electrical inspection task will be matched to the corresponding electrical inspection workstation based on the workstation list.

[0242] In one possible implementation, the feasibility of the workstation list is verified based on the workstation production cycle time, including:

[0243] Based on the workstation production cycle time and estimated dwell time, calculate the task execution time corresponding to the workstation list;

[0244] When the execution time of a task is determined to be less than or equal to the set total instruction time, the first necessary electrical inspection task in the workstation list is identified.

[0245] Based on the first necessary electrical inspection task, it is matched with the second necessary electrical inspection task in the electrical inspection task list, and based on the matching results, the feasibility of the workstation list is verified.

[0246] In one possible implementation, the matching module 402 is further configured to:

[0247] When all the first necessary electrical inspection tasks are matched with the second necessary electrical inspection tasks, the workstation list is deemed to have passed the feasibility check.

[0248] In one possible implementation, the matching module 402 is further configured to:

[0249] When at least two workstation lists pass the feasibility check, calculate the cumulative sum of the workstation production cycle time;

[0250] Based on the cumulative and smaller list of workstations, any electrical inspection task is matched to the corresponding electrical inspection workstation.

[0251] In one possible implementation, the matching module 402 is further configured to:

[0252] When the workstation list fails the feasibility check, check whether the electrical inspection tasks in the workstation list are necessary electrical inspection tasks. If not, mark the corresponding electrical inspection tasks and generate electrical inspection prompt information based on the marking results.

[0253] If so, the corresponding electrical inspection task is recorded as an electrical inspection task to be executed, and the electrical inspection task to be executed is matched to an alternative electrical inspection station. The alternative electrical inspection station is the adjacent electrical inspection station of the electrical inspection station corresponding to the electrical inspection station of the electrical inspection task to be executed in the station list, and the electrical inspection function list of the adjacent electrical inspection station contains the electrical inspection function corresponding to the electrical inspection task to be executed.

[0254] In one possible implementation, the first vehicle information is: the vehicle identification number and / or the electronic control unit serial number associated with the vehicle identification number.

[0255] In one possible implementation, the device 40 further includes:

[0256] The data receiving and storage module is used to receive and store the electrical inspection results uploaded by the electrical inspection production line.

[0257] In one possible implementation, the device 40 further includes:

[0258] The anomaly detection module is used to parse the results of electrical inspection operations. When it is determined that the electrical inspection operation results contain electrical inspection anomaly codes, the module locates the electrical inspection anomalies based on the electrical inspection anomaly codes and determines the electrical inspection station and corresponding electrical inspection task corresponding to the electrical inspection anomaly codes.

[0259] The vehicle electrical testing device 40 provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0260] Figure 5 The structural schematic diagram of the vehicle electrical inspection device applicable to the electrical inspection production line provided in this application is as follows: Figure 5As shown, the vehicle electrical inspection device 50 provided in this embodiment is suitable for electrical inspection production lines. The electrical inspection production line has at least two electrical inspection stations. The vehicle electrical inspection device 50 includes:

[0261] The acquisition module 501 is used to acquire the second vehicle information of the vehicle to be inspected and the first vehicle information in the electric inspection task list.

[0262] The operation module 502 is used to determine whether the second vehicle information matches the first vehicle information. If yes, it performs an electrical inspection on the vehicle to be inspected based on the electrical inspection task list. If no, it generates an electrical inspection alarm message. The electrical inspection task list is a list generated according to the vehicle electrical inspection method provided above.

[0263] In this embodiment, by acquiring the second vehicle information of the vehicle to be inspected on-site and the first vehicle information pre-associated in the task list simultaneously by the acquisition module 501, a corresponding verification relationship between the physical vehicle and the issued task can be established before the workstation execution, thereby avoiding the miscalling of inspection items when the vehicle model, configuration, or body identity is inconsistent in mixed-line production. When the match is successful, the operation module 502 directly performs the electrical inspection operation according to the electrical inspection task list, so that the execution content on the workstation side is consistent with the task allocation result generated by the cloud platform, thereby ensuring the continuity and accuracy of the multi-workstation task undertaking link; when the match is unsuccessful, an electrical inspection alarm message is generated, thus timely blocking the entry of erroneous vehicles into the subsequent electrical inspection process, reducing false detections, missed detections, and invalid operations, and enabling production line anomalies to be quickly identified and handled, thereby improving the collaborative efficiency of multi-workstation electrical inspection and the quality control capability of the entire production line.

[0264] In one possible implementation, the device 50 further includes:

[0265] The data upload module is used to package the electrical inspection results of the vehicles to be inspected and upload the packaged data.

[0266] The vehicle electrical inspection device 50 provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0267] Figure 6 A schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 60 provided in this embodiment includes at least one processor 601 and a memory 602. Optionally, the device 60 further includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus 604.

[0268] In a specific implementation, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to perform the above-described method.

[0269] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0270] In this embodiment, the electronic device can be deployed as a cloud platform server, edge computing node, or production line scheduling and control terminal. The memory is used to store the program instructions corresponding to the vehicle electrical inspection method, the information of the vehicle to be inspected, the workstation operating status, and the task matching rules. After the processor calls the instructions, it can obtain the production line operating parameters, electrical inspection workstation status, and task information of at least one electrical inspection production line in real time. It can also complete task matching, task list generation, and execution by combining the electrical inspection function lists of each workstation, thereby enabling the device to have the ability to coordinate and control the electrical inspection process of multiple workstations in a unified manner. By centrally executing vehicle information association, workstation capability judgment, and task allocation processing by the same electronic device, the information fragmentation caused by traditional distributed workstation control can be reduced. This allows the task to be inspected to be dynamically adjusted according to the production line load and workstation idleness, thereby improving the flexibility of task allocation and resource utilization under multi-model mixed-line production conditions. Therefore, it helps to reduce the coexistence of workstation congestion, waiting, and equipment idleness, and improves the coordination, real-time performance, and overall inspection efficiency of the vehicle assembly line electrical inspection.

[0271] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0272] The memory may include random access memory (RAM) and non-volatile memory (NVM), such as at least one disk storage device.

[0273] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0274] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0275] In this embodiment, when the computer program product is deployed on a cloud platform, production line server, or workstation control terminal, the processing logic for collecting production line operating parameters, workstation operating status, and information on tasks to be inspected can be solidified into an executable program. This allows the processor to automatically perform a comprehensive analysis of the first vehicle information, the electrical inspection task list, and the workstation electrical inspection function list. The program further performs dynamic matching of tasks and workstations based on the production line load model, and generates an electrical inspection task list associated with vehicle information before distributing it to the corresponding workstation. This transforms task allocation, which previously relied on manual experience or static rules, into a unified scheduling system oriented towards real-time production line status. This improves the flexibility and adaptability of multi-workstation collaborative electrical inspection, reduces workstation congestion, waiting, and resource idleness, and ultimately enhances the detection efficiency, task continuity, and full-process control capabilities of the entire electrical inspection production line under mixed-line production conditions.

[0276] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0277] In this embodiment, the method for scheduling vehicle assembly line electrical inspections is pre-installed in a computer-readable storage medium as computer-executable instructions. This allows for direct invocation and execution by a cloud platform server, workstation control terminal, or host computer when needed, enabling continuous collection and unified processing of production line operating parameters, workstation operating status, and inspection task information. The processor can then perform task matching, task list generation, and task assignment to corresponding workstations based on the electrical inspection function list for each workstation and the production line load model, making the allocation of electrical inspection tasks more flexible under mixed-model conditions. This reduces congestion, waiting, and resource idleness caused by manual configuration and static rules, thus improving multi-workstation collaboration capabilities, overall line cycle time matching, and data continuity and management efficiency throughout the vehicle electrical inspection process.

[0278] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0279] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0280] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0281] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0282] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0283] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0284] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0285] Finally, it should be noted that other embodiments of this application will readily conceive of by those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for vehicle electrical inspection, characterized in that, The method is applicable to a cloud platform, which is communicatively connected to at least one electrical inspection production line, wherein the electrical inspection production line is equipped with at least two electrical inspection workstations, and the method includes: The system collects in real time the production line operation parameters of the electrical inspection production line, the workstation operation status of the electrical inspection station, and the information on tasks to be inspected. The information on tasks to be inspected includes at least the information of the first vehicle and a list of electrical inspection tasks, and the list of electrical inspection tasks includes at least one electrical inspection task. Based on the electrical inspection function list of the electrical inspection station, the production line operating parameters, the electrical inspection task list, and the station operating status, any electrical inspection task is matched to the corresponding electrical inspection station according to the production line load model; wherein, the electrical inspection function list contains the electrical inspection functions that the corresponding electrical inspection station can execute; Based on the workstation information of the matched electrical inspection workstations, an electrical inspection task list is generated, and the first vehicle information is associated with the electrical inspection task list. Based on the workstation information, the electrical inspection task list is sent to the electrical inspection workstation.

2. The method according to claim 1, characterized in that, The process of matching any electrical inspection task to the corresponding electrical inspection station based on the electrical inspection function list of the electrical inspection station, the production line operating parameters, the electrical inspection task list, and the station operating status, according to the production line load model, includes: Based on the electrical inspection function list and the electrical inspection task list, a workstation list corresponding to the electrical inspection task is generated; Based on the production line operating parameters and the workstation operating status, and according to the production line load model, the workstation production cycle time for the electrical inspection workstation in the workstation list to complete the corresponding electrical inspection task is calculated. Based on the production cycle time of the workstation, the feasibility of the workstation list is verified. When the workstation list passes the feasibility verification, any one of the electrical inspection tasks will be matched to the corresponding electrical inspection workstation based on the workstation list.

3. The method according to claim 2, characterized in that, The feasibility verification of the workstation list based on the production cycle time of the workstation includes: Based on the production cycle time and estimated dwell time of the workstation, the task execution time corresponding to the workstation list is calculated; When it is determined that the execution time of the task is less than or equal to the set total instruction time, the first necessary electrical inspection task in the workstation list is identified; Based on the first necessary electrical inspection task, it is matched with the second necessary electrical inspection task in the electrical inspection task list, and based on the matching result, the feasibility of the workstation list is verified.

4. The method according to claim 3, characterized in that, The method further includes: When all the first necessary electrical inspection tasks are matched with the second necessary electrical inspection tasks, the workstation list is determined to have passed the feasibility check.

5. The method according to any one of claims 2-4, characterized in that, The method further includes: When at least two of the workstation lists pass the feasibility check, calculate the cumulative sum of the production cycle times of the workstations; Based on the cumulative and smaller workstation list, any one of the electrical inspection tasks is matched to the corresponding electrical inspection workstation.

6. The method according to any one of claims 2-4, characterized in that, The method further includes: When the workstation list fails the feasibility check, it is determined whether the electrical inspection tasks in the workstation list are necessary electrical inspection tasks. If not, the corresponding electrical inspection tasks are marked, and electrical inspection prompt information is generated based on the marking results. If so, the corresponding electrical inspection task is recorded as an electrical inspection task to be executed, and the electrical inspection task to be executed is matched to an alternative electrical inspection station. The alternative electrical inspection station is the adjacent electrical inspection station of the electrical inspection station corresponding to the electrical inspection station of the electrical inspection task to be executed in the station list, and the electrical inspection function list of the adjacent electrical inspection station contains the electrical inspection function corresponding to the electrical inspection task to be executed.

7. The method according to any one of claims 1-4, characterized in that, The first vehicle information is: the vehicle identification number and / or the electronic control unit serial number bound to the vehicle identification number.

8. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive and store the electrical inspection results uploaded by the electrical inspection production line.

9. The method according to claim 8, characterized in that, The method further includes: The electrical inspection results are analyzed. When it is determined that the electrical inspection results contain an electrical inspection abnormality code, the electrical inspection abnormality is located based on the electrical inspection abnormality code, and the electrical inspection station and the corresponding electrical inspection task corresponding to the electrical inspection abnormality code are determined.

10. A method for vehicle electrical inspection, characterized in that, The method is applicable to electrical inspection production lines, wherein the electrical inspection production lines are provided with at least two electrical inspection stations, and the method includes: Obtain the second vehicle information of the vehicle to be inspected and the first vehicle information in the electric inspection task list; Determine whether the second vehicle information matches the first vehicle information. If yes, perform an electrical inspection on the vehicle to be inspected based on the electrical inspection task list. If no, generate an electrical inspection alarm message. The electrical inspection task list is a list generated by the vehicle electrical inspection method according to any one of claims 1-7.

11. The method according to claim 10, characterized in that, The method further includes: The electrical inspection results of the vehicles to be inspected are packaged and the packaged data is uploaded.

12. A vehicle electrical inspection device, characterized in that, The device is applicable to a cloud platform, which is communicatively connected to at least one electrical inspection production line. The electrical inspection production line has at least two electrical inspection workstations. The device includes: The data acquisition module is used to collect in real time the production line operation parameters of the electrical inspection production line, the workstation operation status of the electrical inspection station, and the information of the tasks to be inspected. The information of the tasks to be inspected includes at least the information of the first vehicle and the list of electrical inspection tasks, and the list of electrical inspection tasks includes at least one electrical inspection task. The matching module is used to match any electrical inspection task to the corresponding electrical inspection station based on the electrical inspection function list of the electrical inspection station, the production line operating parameters, the electrical inspection task list, and the station operating status, according to the production line load model; wherein, the electrical inspection function list contains the electrical inspection functions that can be executed by the corresponding electrical inspection station. The association module is used to generate an electrical inspection task list based on the workstation information of the matched electrical inspection workstations, and associate the first vehicle information with the electrical inspection task list; The sending module is used to send the electrical inspection task list to the electrical inspection workstation based on the workstation information.

13. A vehicle electrical inspection device, characterized in that, The device is suitable for an electrical inspection production line, wherein the electrical inspection production line has at least two electrical inspection stations, and the device includes: The acquisition module is used to acquire the second vehicle information of the vehicle to be inspected and the first vehicle information in the electric inspection task list. The operation module is used to determine whether the second vehicle information matches the first vehicle information. If yes, it performs an electric inspection on the vehicle to be inspected based on the electric inspection task list. If no, it generates an electric inspection alarm message. The electric inspection task list is a list generated by the vehicle electric inspection method according to any one of claims 1-9.

14. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-9, or to perform the method as described in any one of claims 10-11.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-9, or to perform the method as described in any one of claims 10-11.

16. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-9, or performs the method of any one of claims 10-11.

Images