Vehicle management method, client, server, and storage medium
By setting negative tags on the vehicles and managing them on the server side, production problems caused by vehicle wear and tear were solved, enabling timely detection and handling of defective vehicles, reducing production risks, and improving product quality and efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- FU TAI HUA IND SHENZHEN
- Filing Date
- 2025-01-23
- Publication Date
- 2026-07-24
AI Technical Summary
Frequent collisions between the vehicle and the mechanical structure during the production process cause wear and tear, affecting product quality. Existing technologies make it difficult to detect and handle defective vehicles in a timely manner.
By setting negative tags on vehicles, the usage status of vehicles can be determined based on the number of negative tags. Statistics and management can be carried out on the server side to promptly detect and deal with defective vehicles and prevent them from continuing to be used.
It effectively reduced the impact of defective vehicles on production, lowered production risks, and improved product quality and production efficiency.
Smart Images
Figure CN122452901A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of production control technology, and in particular to a vehicle control method, client, server and storage medium. Background Technology
[0002] Carriers are typically used on automated production lines to carry products. Carriers can fix products in place, effectively preventing direct contact between products and mechanical structures when products move between production equipment, and reducing the impact on products during flow.
[0003] Currently, the flow of containers typically employs a main flow line and a return flow line. The main flow line loads containers with products for processing, while the return flow line returns empty containers; the containers do not leave the production equipment but are recycled. During mass production, the containers flow at very high speeds within the flow lines, resulting in frequent collisions with mechanical structures. These collisions cause wear and tear on the containers, such as from mechanical grippers, affecting product production. Summary of the Invention
[0004] In view of the above, it is necessary to provide a vehicle management method, client, server and storage medium that can promptly detect defective vehicles, reduce the impact of defective vehicles on production and reduce production risks.
[0005] In a first aspect, this application provides a vehicle management method, the method comprising: when a vehicle carrying a product enters a workstation, if the vehicle's usage status is determined to be disabled based on the vehicle code, discarding the vehicle and the product; if the vehicle's usage status is available, controlling the workstation's production equipment to process the product and obtaining the test results of the processed product; if the test results indicate that the processed product failed the test, discarding the vehicle and the processed product; and generating a negative tag for the vehicle and sending the negative tag to a server.
[0006] In one embodiment of this application, the usage status of the vehicle is determined based on the number of negative tags on the vehicle.
[0007] Secondly, this application provides a vehicle management method applied to a server. The method includes: receiving negative tags of vehicles sent by a client; counting the number of negative tags of the vehicles; setting the usage status of the vehicles according to the number of negative tags; and responding to a query request sent by the client to query the usage status of the vehicles, sending the usage status of the vehicles to the client.
[0008] In one embodiment of this application, the method further includes: dividing the production process of the product into multiple stages, wherein each stage corresponds to multiple workstations, and each workstation corresponds to a client.
[0009] In one embodiment of this application, counting the number of negative tags on the vehicle includes: determining the phase to which the client that sent the negative tag belongs; and counting the number of negative tags on the vehicle based on the phase to which the client that sent the negative tag belongs.
[0010] In one embodiment of this application, setting the usage status of the vehicle based on the number of negative tags includes: if the number of negative tags of the vehicle corresponding to any of the plurality of stages is greater than or equal to a preset value, setting the usage status of the vehicle to a disabled state; and if the number of negative tags of the vehicle corresponding to any of the stages is less than the preset value, setting the usage status of the vehicle to an available state.
[0011] In one embodiment of this application, setting the usage status of the carrier based on the number of negative tags further includes: when the product carried by the carrier has completed the processing operation of the last workstation corresponding to any stage and passed the test, if the number of negative tags of the carrier corresponding to any stage is less than the preset value, the number of negative tags of the carrier corresponding to any stage is set to 0.
[0012] In a third aspect, this application provides a client comprising: a memory storing computer-readable instructions; and a processor executing the computer-readable instructions to implement the vehicle control method described in the first aspect.
[0013] In a fourth aspect, this application provides a server, comprising: a memory storing computer-readable instructions; and a processor executing the computer-readable instructions to implement the vehicle control method described in the second aspect.
[0014] In a fifth aspect, this application provides a computer-readable storage medium storing computer-readable instructions; when the computer-readable instructions are executed by a processor, the vehicle control method described in the first or second aspect is implemented. Compared with existing technologies, this application can detect defective vehicles in a timely manner, reduce the impact of defective vehicles on production, and reduce production risks. Attached Figure Description
[0015] Figure 1 This is an application scenario for the vehicle control method provided in the embodiments of this application.
[0016] Figure 2 This is a first flowchart of the vehicle control method provided in the embodiments of this application.
[0017] Figure 3 This is a second flowchart of the vehicle control method provided in the embodiments of this application.
[0018] Figure 4 This is a functional block diagram of the vehicle control device provided in the embodiments of this application.
[0019] Figure 5 This is a functional block diagram of a vehicle control device provided in another embodiment of this application.
[0020] Figure 6 This is a schematic diagram of the client structure provided in the embodiments of this application.
[0021] Figure 7 This is a schematic diagram of the server structure provided in an embodiment of this application. Detailed Implementation
[0022] To make the objectives, technical solutions, and advantages of this application clearer, the application will be described in detail below with reference to the accompanying drawings and specific embodiments.
[0023] It should be noted that in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects, not to describe a specific order or sequence.
[0024] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner. Unless otherwise specified, the following embodiments and features described herein can be combined with each other.
[0025] like Figure 1 The diagram shown is an application scenario diagram of the vehicle control method provided in the embodiments of this application.
[0026] Multiple clients 1 can communicate and connect with server 2. Multiple clients 1 correspond to multiple workstations 3. Each workstation 3 can correspond to one client 1. Server 2 can be a cloud server, and client 1 can be a computer device with data processing capabilities. Server 2 can control the carrier 4 during the product manufacturing process based on information such as tags sent by client 1 regarding the carrier 4 carrying the product.
[0027] In one embodiment of this application, the product to be manufactured can be, for example, a mobile phone, a tablet computer, automotive parts such as seats, medical devices such as blood pressure monitors, or other products. In one embodiment of this application, server 2 can pre-define the product's production process into multiple stages according to the product's processing requirements. Depending on the production needs, each stage can correspond to multiple workstations, and each workstation is configured with one client. Server 2 can also store the sequence of the multiple workstations corresponding to each stage. It should be noted that the sequence between workstations is also the sequence between the clients corresponding to the workstations.
[0028] For example, with Figure 1 Taking the client 1 corresponding to workstation 3 as an example, from left to right, the first three workstations 3 are responsible for the initial processing of the product (e.g., applying foam, pressure holding, and screwing in, in sequence). Server 2 can set these first three workstations to correspond to a stage. Client 1 can control the production equipment of its workstation to perform corresponding processing operations on the product carried by carrier 4. Taking a certain workstation 3 responsible for product pressure holding as an example, when the product carried by carrier 4 flows to that certain workstation 3, client 1 can control the pressure holding equipment of that certain workstation 3 to perform pressure holding processing on the product carried by carrier 4.
[0029] For example, to simplify the explanation, let's assume the production process of the product "tablet computer" includes a first stage and a second stage. The first stage corresponds to three workstations, A1, A2, and A3, and the second stage corresponds to three workstations, B1, B2, and B3. Workstation A1 attaches foam to the product, workstation A2 applies pressure to the product, and workstation A3 screws in the product. Workstation B1 attaches ribbon cables to the product, workstation B2 applies pressure to the product, and workstation B3 screws in the product.
[0030] In one embodiment of this application, each stage may also correspond to a set of loading and unloading equipment (not shown in the figure). The loading equipment is used to load the products onto the carrier 4, and the carrier 4, carrying the products, flows through the various workstations corresponding to the current stage. When the products in the carrier 4 have completed the processing operations of the various workstations in the current stage, the unloading equipment can unload the products from the carrier 4 for product inspection or temporarily remove the products from the carrier 4, or the unloading equipment can not unload the products and the carrier 4 can directly enter the next stage for further processing operations on the products.
[0031] In one embodiment of this application, after any workstation completes the processing operation on the product carried by the vehicle 4, the client 1 of any workstation will generate a tag for the vehicle 4 based on the test results of the processed product. In one embodiment of this application, when the processed product fails the test, the corresponding client 1 generates a negative tag (also called a "black tag") for the vehicle 4 and sends this negative tag to the server 2. The negative tag carries the vehicle code of the vehicle.
[0032] In other embodiments of this application, when the processed product passes the test, the corresponding client 1 can also generate a positive label for the carrier 4 and send this positive label to the server 2. The positive label carries the carrier code of the carrier 4. The positive and negative labels can be used to distinguish whether the product carried by the carrier 4 has passed the test after completing one processing cycle.
[0033] Server 2 can effectively manage carrier 4 during the product manufacturing process based on the tags sent by client 1 to prevent the impact on production caused by continued use of carrier 4 in a defective state. Server 2 can receive negative tags on carrier 4 sent by client 1, count the number of negative tags on carrier 4, set the usage status of carrier 4 based on the number of negative tags, and send the usage status of carrier 4 to client 1 when it receives a query request from client 1. Thus, client 1 can determine whether it is necessary to discard carrier 4 and the product it carries based on the usage status of carrier 4.
[0034] In one embodiment of this application, server 2 can determine the stage to which client 1 that sends negative tags belongs, and count the number of negative tags on vehicle 4 based on the stage to which client 1 that sends negative tags belongs.
[0035] For example, to simplify the explanation, assume the first stage corresponds to three workstations A1, A2, and A3, with clients C1, C2, and C3 respectively. If a product carried by vehicle 4 (vehicle code "Z123") fails the test after processing at workstation A1, then vehicle 4 and the processed product will be discarded. Simultaneously, client C1 will generate a negative tag for vehicle 4 and send it to server 2. Server 2 will then record one negative tag for vehicle 4 (vehicle code "Z123") in the first stage. If, again, a product carried by vehicle 4 fails the test after processing at workstation A1, vehicle 4 and the processed product will again be discarded. Client C1 will again generate a negative tag for vehicle 4 and send it to server 2. Therefore, server 2 will now record two negative tags for vehicle 4 (vehicle code "Z123") in the first stage.
[0036] In one embodiment of this application, if the number of negative tags on vehicle 4 corresponding to any stage is greater than or equal to a preset value, such as 3, server 2 can set the usage status of vehicle 4 to disabled state. If the number of negative tags on vehicle 4 corresponding to any stage is less than a preset value, server 2 can set the usage status of vehicle 4 to available state.
[0037] In one embodiment of this application, when the product carried by the carrier 4 has completed the processing operation of the last workstation corresponding to any stage and passed the test, if the number of negative tags of the carrier 4 corresponding to any stage is less than a preset value, the server 2 can set the number of negative tags of the carrier 4 corresponding to any stage to 0.
[0038] Continuing with the example above, suppose server 2 has currently recorded two negative tags for vehicle 4 with vehicle code "Z123" corresponding to the first stage. If the product carried by vehicle 4 completes the processing operations of workstations A1, A2, and A3 in sequence and passes the test (i.e., server 2 has only recorded a total of 2 negative tags for vehicle 4 with vehicle code "Z123" corresponding to the first stage), then when it is determined that the product carried by vehicle 4 has completed the processing operation of the last workstation A3 and passed the test, server 2 can update the number of negative tags for vehicle 4 corresponding to the first stage to 0, that is, it will then recount the total number of negative tags for vehicle 4 corresponding to the first stage.
[0039] In one embodiment of this application, the server 2 can determine whether the product carried by the vehicle 4 has completed the processing operation of the last workstation and passed the test based on the test results sent by the client 1.
[0040] In one embodiment of this application, when the product carried by the carrier 4 completes the processing operation of the last station of any stage and passes the test, the client 1 of the last station can also send an unbinding signal to the server 2. Thus, when the server 2 receives the unbinding signal, it can set the number of negative tags of the carrier 4 corresponding to the any stage to 0.
[0041] In one embodiment of this application, server 2 may also respond to user input signals to set the number of negative tags for vehicle 4 corresponding to any stage to 0. Specific methods for controlling vehicle 4 are described below.
[0042] like Figure 2 The diagram shown is a first flowchart of a vehicle control method provided in this application embodiment. The vehicle control method is applied to a client, for example... Figure 1 Client 1 is shown. Depending on different requirements, the order of steps in the flowchart can be changed, and some steps can be omitted.
[0043] 201. When a vehicle carrying a product enters the workstation, the vehicle's usage status is determined based on the vehicle's vehicle code.
[0044] In one embodiment of this application, a client can send a query request to the server to inquire about the usage status of a vehicle. The query request includes the vehicle's vehicle code. The server records the usage status of the vehicle and returns the vehicle's usage status to the client upon receiving the query request. In one embodiment of this application, the usage status of the vehicle can be divided into a disabled status and an available status.
[0045] In one embodiment of this application, if it is determined that the vehicle's usage status is disabled, step 202 is executed; if it is determined that the vehicle's usage status is available, step 203 is executed.
[0046] In one embodiment of this application, a carrier code is used to uniquely identify a carrier. That is, different carriers have different carrier codes. In the mass production of a product, multiple carriers may be used. The carrier code can be used to distinguish between different carriers.
[0047] In one embodiment of this application, the various vehicles may use the same material, or some of the vehicles may use different materials. In another embodiment of this application, the server may also store the material used by each vehicle based on its vehicle code.
[0048] 202. When it is determined that the vehicle is in a disabled state, the vehicle and the product shall be disposed of.
[0049] In one embodiment of this application, when it is determined that the use status of the carrier is disabled, the client can send a control signal to the corresponding moving mechanism of the workstation to control the moving mechanism to drive the carrier out of the current production process, thereby realizing the disposal of the carrier and the product, thus avoiding the use of a problematic carrier that results in the processed product not meeting the requirements and avoiding invalid processing.
[0050] 203. When the vehicle's usage status is determined to be usable, the control station's production equipment processes the product and obtains the test results of the processed product.
[0051] For example, assuming the product carried by the carrier is currently flowing into a foam-applying station, the client can control the foam-applying equipment to apply foam to the product carried by the carrier, and control the relevant testing equipment to detect the foam application effect and obtain test results. The test results then indicate whether the processed product passes the test.
[0052] In one embodiment of this application, the client may also send the test results to the server, whereby the server can perform further analysis on the test results.
[0053] 204. Determine whether the test result indicates that the processed product has passed the test. If the processed product passes the test, proceed to step 205; if the processed product fails the test, proceed to step 206.
[0054] 205. When the processed product passes the test, a positive label for the carrier is generated and sent to the server.
[0055] In one embodiment of this application, the positive label carries the carrier code of the carrier, which is used to indicate that the product carried by the carrier with the carrier code has completed the processing operation of the workstation and passed the test.
[0056] 206. When the processed product fails the test, the carrier and the processed product shall be disposed of.
[0057] 207. Generate the vehicle's negative tag and send the vehicle's negative tag to the server.
[0058] In one embodiment of this application, the negative label carries the carrier code of the carrier, which is used to indicate that the product carried by the carrier with the carrier code has completed the processing operation of the workstation but failed the test.
[0059] As can be seen from the above process, after a carrier is disposed of, it can be reused as long as its usage status is not disabled. For example, if a product carried by a carrier fails the test after processing at station A1, that carrier can be used again to carry the product and transfer it to station A1.
[0060] like Figure 3 The diagram shown is a second flowchart of the vehicle control method provided in this application embodiment. The vehicle control method is applied to servers, for example... Figure 1 In server 2 shown, the order of steps in the flowchart can be changed, and some steps can be omitted, depending on different requirements.
[0061] 301, receive the negative tag of the vehicle sent by the client.
[0062] In one embodiment of this application, the server also receives information such as the vehicle's positive tag and test results sent by the client.
[0063] 302, count the number of negative tags on vehicles.
[0064] In one embodiment of this application, the server can pre-divide the entire production process of a product into multiple stages according to actual needs. Each stage corresponds to multiple workstations, and each workstation corresponds to one client. Different workstations perform different processing operations on the product.
[0065] For example, the production process of the product "tablet computer" includes a first stage and a second stage. The first stage corresponds to three workstations A1, A2, and A3, and the second stage corresponds to three workstations B1, B2, and B3. The production equipment at workstation A1 attaches foam to the product, the production equipment at workstation A2 holds the product under pressure, and the production equipment at workstation A3 screws in the product. The production equipment at workstation B1 attaches ribbon cables to the product, the production equipment at workstation B2 holds the product under pressure, and the production equipment at workstation B3 screws in the product.
[0066] In one embodiment of this application, counting the number of negative tags on a vehicle includes: determining the phase to which the client that sent the negative tag belongs; and counting the number of negative tags on the vehicle based on the phase to which the client that sent the negative tag belongs.
[0067] In one embodiment of this application, the server can also count the number of positive tags on the vehicle. Specifically, the server can determine the phase to which the client sending the positive tag belongs; and count the number of positive tags on the vehicle based on the phase to which the client sending the positive tag belongs.
[0068] In other embodiments of this application, the server pre-stores the carrier code and material information for each carrier. The server can also count the number of positive and negative tags on the carriers based on their material, and analyze which material carrier is more suitable for product production based on the statistical results. For example, after completing a batch production of a product, the total number of positive tags on carriers using material "M1" is N1, and the total number of negative tags is N2; the total number of positive tags on carriers using material "M2" is N3, and the total number of negative tags is N4, where N1 + N2 = N3 + N4. If N1 / (N1 + N2) is greater than N3 / (N3 + N4), it can be predicted that carriers using material "M1" are more suitable for producing the product.
[0069] 303, Set the vehicle's usage status based on the number of negative tags.
[0070] In one embodiment of this application, setting the usage status of a vehicle based on the number of negative tags includes: if the number of negative tags of a vehicle corresponding to any of the multiple stages is greater than or equal to a preset value, setting the usage status of the vehicle to a disabled state; and if the number of negative tags of a vehicle corresponding to any stage is less than a preset value, setting the usage status of the vehicle to an available state.
[0071] In one embodiment of this application, the preset value can be set according to actual needs. For example, the preset value can be set to 3.
[0072] For example, assuming statistics show that a vehicle with vehicle code "Z123" has 3 negative tags in the first phase, which equals the preset value of 3, the server can set the usage status of the vehicle with vehicle code "Z123" to disabled. As another example, assuming statistics show that a vehicle with vehicle code "Z321" has 2 negative tags in the first phase, which is less than the preset value of 3, the server can set the usage status of the vehicle with vehicle code "Z321" to available.
[0073] In one embodiment of this application, when the product carried by the carrier completes the processing operation of the last workstation corresponding to any stage and passes the test, if the number of negative tags on the carrier corresponding to any stage is less than a preset value, the server can set the number of negative tags on the carrier corresponding to any stage to 0. That is, the number of negative tags on the carrier corresponding to any stage will then be recounted.
[0074] For example, the first stage corresponds to three workstations A1, A2, and A3, with clients C1, C2, and C3 respectively. If a product carried by a vehicle with the vehicle code "Z123" fails the test after completing the processing operation at workstation A1, both the vehicle and the processed product will be discarded. Simultaneously, client C1 will generate a negative tag for the vehicle and send it to the server, thus recording one negative tag for the vehicle. If the same vehicle carries another product that fails the test after completing the processing operation at workstation A1, both the vehicle and the processed product will again be discarded. Client C1 will again generate a negative tag for the vehicle and send it to the server, thus recording two negative tags for the vehicle at this point. If the product carried by the vehicle completes the processing operations of workstations A1, A2, and A3 in sequence and passes the test (i.e., the server only recorded a total of 2 negative tags for the vehicle corresponding to the first stage), then the server can update the number of negative tags for the vehicle corresponding to the first stage to 0, that is, the total number of negative tags for the vehicle corresponding to the first stage will be recounted.
[0075] In one embodiment of this application, if the product carried by the vehicle has completed the processing operation of the last workstation corresponding to any stage and passed the test, the client corresponding to the last workstation can send an unbinding signal for the vehicle to the server. When the server receives the unbinding signal, it updates the number of negative tags of the vehicle corresponding to any stage to 0.
[0076] 304 indicates a response to a client's query request for the vehicle's usage status, which sends the vehicle's usage status information to the client.
[0077] In one embodiment of this application, the query request carries the vehicle code. The server can then query the vehicle's usage status based on the vehicle code and send the usage status to the client, allowing the client to determine whether to perform a disposal process on the vehicle and the products it carries.
[0078] like Figure 4 The diagram shown is a functional block diagram of the vehicle control device provided in this application embodiment. The vehicle control device 10 runs on the client 1. The vehicle control device 10 includes a determination module 101, a control module 102, and a generation module 103. The module / unit referred to in this application refers to a series of computer-readable instruction segments that can be acquired by a processor and perform a fixed function, and which are stored in a storage device.
[0079] The determining module 110 is used to discard the vehicle and the product when the vehicle carrying the product enters the workstation if the vehicle's usage status is determined to be disabled based on the vehicle code. The control module 102 is used to control the workstation's production equipment to process the product when the vehicle's usage status is available, and to obtain the test results of the processed product; and to discard the vehicle and the processed product when the test results indicate that the processed product has failed the test. The generating module 102 is used to generate a negative tag for the vehicle and send the negative tag to the server.
[0080] like Figure 5 The diagram shown is a functional block diagram of the vehicle control device provided in an embodiment of this application. The vehicle control device 20 runs on server 2. The vehicle control device 20 includes a receiving module 201, a statistics module 202, a setting module 203, and a sending module 204. The module / unit referred to in this application refers to a series of computer-readable instruction segments that can be acquired by a processor and perform a fixed function, and which are stored in a storage device.
[0081] The receiving module 201 is used to receive negative tags of the vehicle sent by the client. The statistics module 202 is used to count the number of negative tags of the vehicle. The setting module 203 is used to set the usage status of the vehicle according to the number of negative tags, and the sending module 204 is used to respond to the query request sent by the client to query the usage status of the vehicle and send the usage status of the vehicle to the client.
[0082] Another embodiment of this application also provides a client. For example... Figure 6As shown, in one embodiment of this application, client 1 includes, but is not limited to, a memory 11, a processor 12, a display device 13, and a computer program 110 stored in the memory 11 and executable on the processor 12. The computer program 110 may be a software program for controlling the carriers used in the production process of the product, for example, it may implement... Figure 2 The vehicle control method is shown. Memory 11 and processor 12 are connected via bus 14. Display device 13 can be a touch screen or other device capable of displaying data of client 1 during operation.
[0083] Those skilled in the art will understand that the schematic diagram is merely an example of a client and does not constitute a limitation on the client. It may include more or fewer components than shown in the diagram, or combine certain components, or different components. For example, the client may also include input / output devices, network access devices, buses, etc.
[0084] Processor 12 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. Processor 12 is the computing core and control center of the client, connecting various parts of the client through various interfaces and lines, and executing the operating system of client 1, as well as various installed applications and program code.
[0085] For example, computer program 110 may be divided into one or more modules / submodules / units, one or more of which are stored in memory 11 and executed by processor 12 to complete this application. One or more modules / submodules / units may be a series of computer-readable instruction segments capable of performing a specific function, which describe the execution process of computer-readable instructions in client 1. For example, computer program 110 may be divided into a determination module 101, a control module 102, and a generation module 103. The memory 11 can be used to store computer-readable instructions and / or modules. The processor 12 implements various functions of the client 1 by running or executing the computer-readable instructions and / or modules stored in the memory 11 and by calling the data stored in the memory 11. The memory 11 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the client 1, etc. The memory 11 may include non-volatile and volatile memory, such as: hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other storage device.
[0086] The memory 11 can be the external memory and / or internal memory of the client 1. Furthermore, the memory 11 can be a physical memory, such as a memory stick, a TF card (Trans-flash Card), etc.
[0087] If the modules / units integrated in client 1 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by instructing related hardware through computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when executed by a processor, they can implement the steps of the various method embodiments described above.
[0088] Computer-readable instructions include computer-readable instruction code, which can be in the form of source code, object code, executable file, or some intermediate form. Computer-readable media can include: any entity or device capable of carrying computer-readable instruction code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), and random access memory (RAM).
[0089] Combination Figure 2 The memory 11 in client 1 stores computer-readable instructions, and the processor 12 can execute the computer-readable instructions stored in memory 11 to achieve, for example... Figure 2 The vehicle control method shown. Specifically, the specific implementation method of the processor 12 for the above-mentioned computer-readable instructions can be found in [reference]. Figure 2The descriptions of the relevant steps in the corresponding embodiments are not repeated here.
[0090] Another embodiment of this application also provides a server. For example... Figure 7 As shown, in one embodiment of this application, server 2 includes, but is not limited to, a memory 21, a processor 22, a display device 23, and a computer program 210 stored in the memory 21 and executable on the processor 22. The computer program 210 may be a software program for controlling the carriers used in the production process of the product, for example, it may implement... Figure 3 The vehicle control method is shown. Memory 21 and processor 22 are connected via bus 24. Display device 23 can be a touch screen or other device capable of displaying data from server 2 during operation.
[0091] Those skilled in the art will understand that the schematic diagram is merely an example of server 2 and does not constitute a limitation on server 2. It may include more or fewer components than shown in the diagram, or combine certain components, or different components. For example, server 2 may also include input / output devices, network access devices, buses, etc.
[0092] Processor 22 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. Processor 22 is the computing core and control center of server 2, connecting various parts of server 2 via various interfaces and lines, and executing the operating system of server 2, as well as various installed applications and program code.
[0093] For example, computer program 210 can be divided into one or more modules / submodules / units. One or more modules / submodules / units are stored in memory 21 and executed by processor 22 to complete this application. One or more modules / submodules / units can be a series of computer-readable instruction segments capable of performing specific functions, which describe the execution process of computer-readable instructions in server 2. For example, computer program 210 can be divided into a receiving module 201, a statistics module 202, a setting module 203, and a sending module 204. The memory 21 can be used to store computer-readable instructions and / or modules. The processor 22 implements various functions of the server 2 by running or executing the computer-readable instructions and / or modules stored in the memory 21 and by accessing the data stored in the memory 21. The memory 21 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the server 2, etc. The memory 21 may include non-volatile and volatile memory, such as: hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other storage devices.
[0094] The memory 21 can be the external memory and / or internal memory of the server 2. Furthermore, the memory 21 can be a physical memory, such as a memory stick, a TF card (Trans-flash Card), etc.
[0095] If the modules / units integrated in server 2 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by instructing related hardware through computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium, and when executed by a processor, they can implement the steps of the various method embodiments described above. The computer-readable instructions include computer-readable instruction code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying computer-readable instruction code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), and random access memory (RAM).
[0096] Combination Figure 3 The memory 31 in server 2 stores computer-readable instructions, and the processor 32 can execute the computer-readable instructions stored in memory 31 to achieve, for example, Figure 3 The vehicle control method shown. Specifically, the specific implementation method of the processor 22 for the above-mentioned computer-readable instructions can be found in [reference]. Figure 3 The descriptions of the relevant steps in the corresponding embodiments are not repeated here.
[0097] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.
[0098] The modules described as separate components may or may not be physically separate. The components shown as modules 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 modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0099] Furthermore, the functional modules 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. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.
[0100] Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of this application is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within this application. No appended diagram markings in the claims should be construed as limiting the scope of the claims.
[0101] Furthermore, it is clear that the word "including" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices can also be implemented by a single unit or device through software or hardware. Terms such as "first," "second," etc., are used to indicate names and do not indicate any specific order.
[0102] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of this application without departing from the spirit and scope of the technical solutions of this application.
Claims
1. A vehicle control method, characterized in that, The method includes: When a product is carried into a workstation by a carrier, if the carrier's usage status is determined to be disabled based on the carrier's carrier code, the carrier and the product are disposed of. If the vehicle is in an available state, control the production equipment of the workstation to process the product and obtain the test results of the processed product; If the test result indicates that the processed product fails the test, the carrier and the processed product are discarded; and Generate a negative tag for the vehicle and send the negative tag for the vehicle to the server.
2. The vehicle control method as described in claim 1, characterized in that, The usage status of the vehicle is determined based on the number of negative tags on the vehicle.
3. A vehicle control method, applied to a server, characterized in that, The method includes: Receive the negative tag of the vehicle sent by the client; Count the number of negative tags on the vehicle; The usage status of the vehicle is set according to the number of negative tags; and In response to a query request sent by the client to inquire about the vehicle's usage status, the system sends the vehicle's usage status to the client.
4. The vehicle control method as described in claim 3, characterized in that, The method further includes: The production process of the product is divided into multiple stages, wherein each stage corresponds to multiple workstations, and each workstation corresponds to one client.
5. The vehicle control method as described in claim 4, characterized in that, The counting of negative tags on the vehicle includes: Determine the phase to which the client sending the negative label belongs; and The number of negative tags on the vehicle is counted based on the phase to which the client that sent the negative tag belongs.
6. The vehicle control method as described in claim 5, characterized in that, The step of setting the usage status of the vehicle based on the number of negative tags includes: If the number of negative tags on the vehicle corresponding to any of the plurality of stages is greater than or equal to a preset value, the usage status of the vehicle is set to disabled; and If the number of negative tags on the vehicle corresponding to any stage is less than the preset value, the usage status of the vehicle is set to available status.
7. The vehicle control method as described in claim 6, characterized in that, The step of setting the usage status of the vehicle based on the number of negative tags also includes: When the product carried by the vehicle has completed the processing operation of the last workstation corresponding to any stage and passed the test, if the number of negative tags on the vehicle corresponding to any stage is less than the preset value, the number of negative tags on the vehicle corresponding to any stage is set to 0.
8. A client application, characterized in that, The client includes: Memory, which stores computer-readable instructions; and The processor executes the computer-readable instructions to implement the vehicle control method as described in any one of claims 1 to 2.
9. A server, characterized in that, The server includes: Memory, which stores computer-readable instructions; and The processor executes the computer-readable instructions to implement the vehicle control method as described in any one of claims 3 to 7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions; when the computer-readable instructions are executed by a processor, the vehicle control method as described in any one of claims 1 to 2 and / or 3 to 7 is implemented.