Digital multi-station collaborative manufacturing method and system

Abstract

The present invention proposes a digital multi-station collaborative manufacturing method, including: storing protocol commands in a database; classifying protocol commands; calling protocol commands; recording called protocol commands in a log; and checking the log at a preset frequency. The protocol commands generated between the control terminal and the execution device are saved in a database, and the protocol commands are called from the database by calling, and the call records are saved, so that the operating status of all devices can be traced and queried; real-time data is sent at a certain time and in a certain order, and a time table is established in the switch. Through the time table, the control terminal can know when to transmit real-time information, and the forwarding of information is almost delay-free. The same control terminal issues commands, so that all equipment in the workshop can operate in a collaborative manner.

Description

Technical Field

[0001] The present invention relates to the technical field of shipbuilding, and in particular to a digital multi-station collaborative manufacturing method and system. Background Art

[0002] my country's shipbuilding enterprises have experienced a period of rapid development and have achieved remarkable results: First, they have continued to invest in infrastructure, manufacturing equipment, equipment automation, etc., and have built cutting lines, medium-sized and small-scale stand-alone welding lines, large-tonnage docks / slipways and other advanced hardware facilities. Second, domestic backbone shipbuilding enterprises have vigorously promoted the construction of "digital shipbuilding". PDM systems, ERP systems and MES systems have been implemented to realize the digital design of ship products, the information management and control of production planning, logistics and quality in the manufacturing process, and significantly improve the efficiency and quality of shipbuilding.

[0003] In the shipbuilding process, different shipbuilding workshops have numerous devices, and these automated devices support different network protocols. For example, German equipment supports PROFINET / PROFIBUS protocol, Japanese imported equipment mostly supports MODBUS protocol, and American imported equipment mostly supports Device-net protocol, which makes the overall network interconnection very difficult, and it is difficult for a single workshop management network configuration system to obtain all equipment data at the same time. The shipyard production and manufacturing system has the complex characteristics of multiple production lines, multiple workstations, multiple equipment, multiple tooling, multiple intermediate products, and multiple management information systems. The data sources of these objects have the characteristics of multiple data sources and heterogeneity. These data deviate from process requirements and design models and cannot be effectively coordinated, which leads to problems in production efficiency, quality, and reliability. Summary of the invention

[0004] In view of the above problems, the present invention proposes a digital multi-station collaborative manufacturing method for collecting protocol commands and periodically checking the called protocol commands, including: an aggregation and classification step, collecting the protocol commands of each execution device network protocol, storing the protocol commands in a database, and classifying the protocol commands; a call recording step, when any of the protocol commands is called, the called protocol commands are recorded in a log; and an inspection step, the protocol commands in the log are inspected at a preset frequency.

[0005] The digital multi-station collaborative manufacturing method described in the present invention, wherein the collection and classification step also includes: adding the corresponding execution device UID to the protocol command; extracting keywords in the protocol command; the keywords include the execution device UID, timestamp, and protocol type; and classifying the protocol command execution according to the keywords.

[0006] The digital multi-station collaborative manufacturing method described in the present invention, wherein the call record step specifically includes: setting a production plan file; the production plan file includes the UID of the execution device, the operating status and operating time information corresponding to the execution device; and calling the protocol command according to the production plan file.

[0007] In the digital multi-station collaborative manufacturing method described in the present invention, the calling record step further includes: clearing the log after each preset time period.

[0008] The present invention also proposes a digital multi-station collaborative manufacturing system, including: a collection and classification module, used to collect protocol commands of each execution device network protocol, store the protocol commands in a database, and classify the protocol commands; a call recording module, used to record the called protocol commands in a log when any of the protocol commands is called; and a checking module, used to check the protocol commands in the log at a preset frequency.

[0009] The digital multi-station collaborative manufacturing system described in the present invention, wherein the collection and classification module includes: a preprocessing module, used to add the corresponding execution device UID to the protocol command; a keyword extraction module, used to extract keywords in the protocol command; the keywords include the execution device UID, timestamp, and protocol type; a classification module, used to classify the protocol command execution according to the keywords.

[0010] The digital multi-station collaborative manufacturing system described in the present invention, wherein the call recording module includes: a planning module, used to set a production plan file; the production plan file includes the UID of the execution device, the operating status and operating time information corresponding to the execution device; and a calling module, used to call the protocol command according to the production plan file.

[0011] In the digital multi-station collaborative manufacturing system described in the present invention, the call record module further includes: a log release module, which is used to clear the log after a preset time period.

[0012] The present invention also proposes a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed, the digital multi-station collaborative manufacturing method as described above is implemented.

[0013] The present invention also proposes a data processing device, including the computer-readable storage medium as described above, and the processor of the data processing device retrieves and executes computer-executable instructions in the computer-readable storage medium to implement a digital multi-station collaborative manufacturing method.

[0014] The digital multi-station collaborative manufacturing method of the present invention saves the protocol commands generated between the control terminal and the execution device into a database, calls the protocol commands from the database and saves the call records, so that the operating status of all devices can be traced and checked; and by pre-setting the production plan file, the operation plan of all equipment within a production cycle is arranged, and the operating status and operating time of each production equipment are coordinated to achieve collaborative production between production equipment with different protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a flow chart of a digital multi-station collaborative manufacturing method in an embodiment of the present invention.

[0016] Figure 2 It is a block diagram of a digital multi-station collaborative manufacturing device in an embodiment of the present invention.

[0017] Figure 3 It is a structural diagram of a digital multi-station collaborative manufacturing terminal in an embodiment of the present invention.

[0018] Figure 4 It is a schematic diagram of a data processing device of the present invention. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0020] Figure 1 FIG. 1 is a flow chart of a digital multi-station collaborative manufacturing method according to an embodiment of the present invention. Figure 1 As shown, an embodiment of the present invention provides a digital multi-station collaborative manufacturing method, including:

[0021] Step S10, storing the protocol command in a database.

[0022] In this embodiment, all protocol commands generated by the automation equipment in the shipbuilding process are stored in the same database. In a specific embodiment, while the workshop equipment is running, the protocol commands generated during the backup period are stored in the database, and all protocol commands are collected.

[0023] Step S20, classifying the protocol commands.

[0024] In this embodiment, for example, classification is performed according to PROFINET / PROFIBUS protocol, MODBUS protocol, Device-net protocol, etc., or classification is performed according to related devices.

[0025] Step S30, calling the protocol command.

[0026] In this embodiment, the protocol command is retrieved from the database, and the retrieved time information is retained. In a specific embodiment, multiple protocol commands are called each time to ensure that the equipment in the workshop can run simultaneously.

[0027] Step S40: Record the called protocol command into the log.

[0028] In this embodiment, the called protocol commands are completely recorded in the log. In a specific embodiment, these protocol commands are recorded in chronological order.

[0029] Step S50: Check the log at a preset frequency.

[0030] In this embodiment, a check program is set to check the log every 30 seconds. In a specific embodiment, if no abnormality is found in the current check result, a check break point is set at the end of the log of the current check, and the next check program starts from the check break point. In a specific implementation method, if two consecutive check results are normal, the previous check break point is cleared and the current check break point is retained.

[0031] The protocol commands generated between the control terminal and the execution device are saved in a database. The protocol commands are called from the database and the call records are saved, so that the operating status of all devices can be traced and queried; real-time data is sent in a certain order at a certain time, and a time table is established in the switch. Through this time table, the control terminal can know when to transmit real-time information, and the forwarding of information has almost no delay. If there is a risk of conflict, the standard TCP / IP information is temporarily saved in the switch and sent again in the next open communication cycle. The same control terminal issues commands, so that all equipment in the workshop can work together.

[0032] As an optional implementation, before step S10, the method further includes:

[0033] Step S01, adding the corresponding execution device UID to the protocol command.

[0034] In this embodiment, the UID of the corresponding execution device is added to the front end or back end of the protocol command statement. In a specific embodiment, the protocol commands are classified by UID.

[0035] As an optional implementation, step S20 includes:

[0036] Step S201, performing classification according to the type of protocol command.

[0037] In this embodiment, the same type of instructions in different protocols are classified, such as pause commands. Combined with step S01, when the protocol command of this category is called, the control terminal can immediately obtain what type of operation the device corresponding to the protocol command will perform.

[0038] As an optional implementation, step S201 includes:

[0039] Step S2011, extracting keywords from the protocol command.

[0040] In this embodiment, the keywords include execution action, device UID, execution time, set variable parameters, etc.

[0041] Step S2012, performing classification according to keywords.

[0042] In this embodiment, classification is performed based on one or more of the execution action, device UID (User Identification) or execution time. For example, the protocol commands of the same device UID are first selected, and then sorted according to the chronological order and stored in the same storage space. In a specific embodiment, the inspection program in the control terminal checks the log. In a specific implementation, the inspection program of the control terminal can set a keyword query, such as querying all device operations within a certain period of time, or a single device operation within a certain period of time.

[0043] As an optional implementation, step S20 further includes:

[0044] Step S202, partitioning the database.

[0045] In this embodiment, the database is fixedly partitioned according to the length and total number of protocol command statements generated in a production cycle of each device: the memory is fixedly divided into a number of partitions of different sizes, and a partition table is created, which includes the starting address, size and status of each partition. When the protocol command statement is loaded into the memory, the partition is allocated according to the UID of the executing device.

[0046] Execution equipment Size (KB) Starting address (K) state UID1 64 0 Allocated UID2 64 64 Unassigned UID3 128 128 Allocated

[0047] Table 1 Partition allocation table

[0048] In a specific embodiment, when a user program is to be loaded, the memory allocation program retrieves the partition allocation table shown in Table 1, finds a partition that meets the requirements and has not been allocated, allocates it to the program, and then sets the status in the table entry to "allocated".

[0049] Step S203: Store the protocol commands of the same category in the same partition.

[0050] In this embodiment, the classification basis of the same category of protocol commands is: the same protocol, for example, the command statements of PROFINET / PROFIBUS protocol are in the first partition, the command statements of MODBUS protocol are in the second partition, and the command statements of Device-net protocol are in the third partition.

[0051] Step S204: Bind the protocol command to the corresponding partition address.

[0052] In this embodiment, the memory of the database is partitioned according to each device. When the memory partition is called, the device that executes the command can be determined based on the address range. There is no need to analyze which protocol the command statement belongs to, only what operation the command statement performs.

[0053] In a specific embodiment, the execution operation content is pre-noted for all protocol command statements. When the protocol command statement is called, the corresponding execution device UID is quickly obtained according to the address range of the memory. Then, according to the execution operation in the remarks, the calling time of the protocol command, the execution device UID and the execution operation content are recorded in the log.

[0054] As an optional implementation, step S40 includes:

[0055] Step S401, converting the keyword into a long string of binary data.

[0056] In this embodiment, the valid information in the protocol command statement is set as keywords, such as the execution action, device UID, execution time and set variable parameters, arranged in a fixed order, or a prefix or suffix is ​​added to the front or back end of each keyword as a label for each keyword, and the keyword string is converted into a long string of binary data.

[0057] Step S402, dividing the character string into short character strings of four digits each.

[0058] In this embodiment, a long binary string is converted into a short hexadecimal string to reduce the amount of text and save memory space.

[0059] Step S403, generating a token according to the short character string.

[0060] In this embodiment, a token is generated according to several characters at a specific position in a short string, such as a string obtained by converting the corresponding device UID, which is used as a token. When the token is allowed by the server, the client sends a request to the server in some way, and the server sends it to the client. The client uses the access token to access the protected resources hosted by the resource server. In general, before accessing protected resources, the client must first obtain authorization from the resource owner, and then exchange the authorization for an access token. The access token indicates the scope, duration, and other attributes of the authorization grant. The client accesses the protected resources by displaying the access token to the resource server. In some cases, the client can directly send its own credentials to the server. By setting the token, the user access rights of the log are limited, reducing the risk of the log being accidentally added or deleted, and at the same time narrowing the scope of personnel responsible for managing the log.

[0061] As an optional implementation, before step S40, the method further includes:

[0062] Step S301, obtaining the length information of the protocol command.

[0063] In this embodiment, the length information of the protocol command is acquired in advance, the storage area is matched, and the appropriate memory space is allocated.

[0064] Step S302: Allocate a storage area for the protocol command in the database according to the length information.

[0065] In this embodiment, a storage area is allocated to each execution device, and the size of the memory area is divided according to the operating frequency of the device. The memory allocation strategy of the device adopts dynamic partitioning. The partition size is not fixed in advance, but is divided according to the job demand; the number and position of the partitions are not predetermined. It effectively overcomes the problem of waste caused by the vacant remaining memory inside the partition in the fixed partitioning method. In a specific embodiment, when a statement is loaded, according to the memory demand of the statement, a partition with the same size as the statement is drawn from the free area to load the job, and the remaining part is still the free area. When the free area can meet the demand (that is, the length of the free area>=statement length), the statement can be loaded; otherwise, the statement cannot be loaded temporarily. In a specific implementation method, a 10% free area of ​​the statement memory size generated by daily full-load operation is preset for each device to ensure that the protocol command statement can be loaded into the memory in real time.

[0066] As an optional implementation, before step S40, the method further includes:

[0067] Step S303: extract keywords from the protocol command, where the keywords include the execution device UID, timestamp, and protocol type.

[0068] In this embodiment, only the keywords in the protocol commands are recorded in the log text.

[0069] After step S40, the method further includes:

[0070] Step S404: clear the log after a preset time.

[0071] In this embodiment, the preset time is 5-10 days. By clearing log files frequently, memory space in the database is released.

[0072] As an optional implementation, before step S40, the method further includes:

[0073] Step S304, pre-processing the protocol commands in the database using an API algorithm; the pre-processing includes paging, flow, authorization and access control.

[0074] In this embodiment, the MySQL client / server protocol provides prepared statements. This feature uses the MYSQL_STMT statement handler data structure returned by the mysql_stmt_init() initialization function. For statements that are executed multiple times, preprocessing execution is an effective way. First, the statement is parsed and prepared for execution. Next, the statement handle returned by the initialization function is used to execute one or more times in the future.

[0075] Another advantage of prepared statements is that they use a binary protocol, making data transmission between the client and the server more efficient.

[0076] The execution steps are as follows:

[0077] 1. Create a prepared statement handle with msyql_stmt_init(). To prepare a prepared statement on the server, call mysql_stmt_prepare() and pass it a string containing the SQL statement.

[0078] 2. If the statement generates a result set, call mysql_stmt_result_metadata() to obtain the result set metadata. This metadata itself is in the form of a result set, although it is different from the result set that contains the columns returned by the query. The metadata result set indicates how many columns are included in the result and contains information about each column.

[0079] 3. Use mysql_stmt_bind_param() to set the value of any parameter. You must set all parameters. Otherwise, statement execution will return an error or produce unexpected results.

[0080] 4. Call mysql_stmt_execute() to execute the statement.

[0081] 5. If the statement generates a result set, bind the data buffer and retrieve the row values ​​by calling mysql_stmt_bind_result().

[0082] 6. Fetch the data row by row into the buffer by repeatedly calling mysql_stmt_fetch() until no more rows are found.

[0083] 7. Repeat steps 3 to 6 by changing the parameter values ​​and executing the statement again.

[0084] For statements that are executed multiple times, prepared execution is faster than direct execution, mainly because the query is parsed only once. In the case of direct execution, the query is run each time the statement is executed. In addition, since only the parameter data needs to be sent each time the prepared statement is executed, network traffic is reduced.

[0085] The embodiment of the present invention also provides a digital multi-station collaborative manufacturing device, such as Figure 2 As shown, including:

[0086] The storage module 201, the classification module 202, the calling module 203, the recording module 204, the inspection module 205, the memory 206 and the processor 207 are connected to each other for communication. The memory 206 stores computer instructions. The processor 207 executes the computer instructions to implement the digital multi-station collaborative manufacturing method. Figure 3 As shown, the processor 207 and the memory 206 may be connected via a bus or other means.

[0087] As an optional implementation, step S30 further includes:

[0088] Step S305, setting a production plan file. The production plan file includes the UID of the execution device, the operation status and operation time information corresponding to the execution device;

[0089] Step S306, calling the protocol command according to the production plan file.

[0090] In this embodiment, a production plan file can be set up in advance to arrange the operation plan of all equipment within a production cycle. The processor 207 performs instruction analysis on the production plan file, and then the calling module 203 calls the protocol command statement from the memory 206 (i.e., the database) and sends it to each production equipment to coordinate the operating status and operating time of each production equipment to achieve collaborative production between production equipment with different protocols.

[0091] The processor 207 may be a central processing unit (CPU). The processor 207 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0092] The memory 206 is a non-transient computer-readable storage medium that can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions / modules corresponding to the vehicle display device key shielding method in the embodiment of the present invention. The processor 207 executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory 206, that is, realizing the digital multi-station collaborative manufacturing method in the above method embodiment.

[0093] The memory 206 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created by the processor 207, etc. In addition, the memory 206 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some embodiments, the memory 206 may optionally include a memory remotely arranged relative to the processor 207, and these remote memories may be connected to the processor 207 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0094] The one or more modules are stored in the memory 206 and when executed by the processor 207, perform the following steps: Figure 1 The digital multi-station collaborative manufacturing method in the illustrated embodiment.

[0095] Figure 4Schematic diagram of the data processing device of the present invention. Figure 4 As shown, an embodiment of the present invention further provides a computer-readable storage medium and a data processing device. The computer-readable storage medium of the present invention stores computer-executable instructions. When the computer-executable instructions are executed by the processor of the data processing device, the above-mentioned digital multi-station collaborative manufacturing method is realized. Those skilled in the art can understand that the implementation of all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk (Hard Disk Drive, abbreviated as: HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0096] Beneficial effects of the digital multi-station collaborative manufacturing method embodiment of the present invention:

[0097] 1. Save the protocol commands generated between the control terminal and the execution device to a database. By calling the protocol commands from the database and saving the call records, the operating status of all devices can be traced and queried; real-time data is sent in a certain order at a certain time, and a time table is established in the switch. Through this time table, the control terminal can know when to transmit real-time information, and the forwarding of information has almost no delay. If there is a risk of conflict, the standard TCP / IP information is temporarily stored in the switch and sent again in the next open communication cycle. The same control terminal issues commands, so that all equipment in the workshop can work together.

[0098] 2. Set up the production plan file in advance and arrange the operation plan of all equipment within a production cycle. The processor will analyze the instructions of the production plan file, and then the calling module will call the protocol command statement from the memory (i.e., the database) and send it to each production equipment to coordinate the operation status and operation time of each production equipment to achieve collaborative production between production equipment with different protocols.

[0099] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A digital multi-station collaborative manufacturing method, characterized in that: include: A collection and classification step, collecting the protocol commands of the network protocol of each execution device, adding the corresponding execution device UID to the protocol command; extracting keywords from the protocol command, and classifying the protocol command according to the keywords, the keywords including the execution device UID, timestamp, and protocol type; Partition the database, store the same category of protocol commands in the same partition of the database, and bind the protocol commands to the corresponding partition addresses; In the calling recording step, when any of the protocol commands is called, the called protocol commands are recorded in the log; The checking step is to check the protocol commands in the log at a preset frequency.

2. The digital multi-station collaborative manufacturing method according to claim 1, characterized in that: The call recording steps specifically include: Set a production plan file; the production plan file includes the UID of the execution device, the operation status and operation time information corresponding to the execution device; The protocol command is called according to the production plan file.

3. The digital multi-station collaborative manufacturing method according to claim 2, characterized in that: The call recording step also includes: After a preset period of time, the log is cleared.

4. A digital multi-station collaborative manufacturing system, characterized in that: include: A collection and classification module is used to collect the protocol commands of the network protocol of each execution device, store the protocol commands in a database, and classify the protocol commands; including: a preprocessing module, used to add the corresponding execution device UID to the protocol command; a keyword extraction module, used to extract keywords in the protocol command, the keywords include the execution device UID, timestamp, and protocol type; a classification module, used to classify the protocol command execution according to the keywords, and partition the database, store the protocol commands of the same category in the same partition of the database, and bind the protocol commands to the corresponding partition addresses; A call recording module is used to record the called protocol command into a log when any of the protocol commands is called; The checking module is used to check the protocol commands in the log at a preset frequency.

5. The digital multi-station collaborative manufacturing system according to claim 4, characterized in that: The call logging module includes: The planning module is used to set a production planning file; the production planning file includes the UID of the execution device, the operation status and operation time information corresponding to the execution device; The calling module is used to call the protocol command according to the production plan file.

6. The digital multi-station collaborative manufacturing system according to claim 5, characterized in that: The call recording module also includes: The log release module is used to clear the log after a preset period of time.

7. A computer-readable storage medium storing computer-executable instructions, which, when executed, implement the digital multi-station collaborative manufacturing method as described in any one of claims 1 to 3.

8. A data processing device, comprising the computer-readable storage medium as described in claim 7, wherein the processor of the data processing device retrieves and executes the computer-executable instructions in the computer-readable storage medium to implement a digital multi-station collaborative manufacturing method.

Images