Efficient and unified pharmaceutical equipment control program development platform and implementation and programming method thereof

Abstract

The invention discloses an efficient and unified pharmaceutical equipment control program development platform and an implementation and programming method thereof. Through the integrated control system hardware library, the production process function library, the cleaning process function library, the platform standard assembly, the customized development area, the program function test panel, the version control assembly and other modules and a matched programming method, rapid development and unified management of the pharmaceutical equipment control program are realized; the platform can reduce dependence on skills and experience of developers, avoid professional problems caused by the skills and experience levels of the developers, reduce complex program development work into development of functions of all modules, save a large amount of repeated development work, shorten the development period, improve the development efficiency, unify the design process and specification, and improve the development efficiency. The consistency of program quality is ensured, the use experience of clients is improved, and the method can be applied to pharmaceutical equipment and can also be popularized to other industries.

Description

Technical Field

[0001] The present invention relates to the technical field of pharmaceutical equipment control program development, and in particular to an efficient and unified pharmaceutical equipment control program development platform and an implementation and programming method thereof. Background Art

[0002] In the field of pharmaceutical equipment, the development of control programs is a key link to ensure the normal operation of equipment and production efficiency. Traditional pharmaceutical equipment control program development is usually based on project requirements, following certain workflows and specifications, and written from scratch. However, this development method from scratch has multiple problems:

[0003] 1) Low development efficiency: Since each project requires rewriting the control program, there is a lot of repetitive work and a long development cycle, which makes it impossible to quickly respond to market changes and customer needs.

[0004] 2) Inconsistent program quality: The ability levels of programmers vary, their development experience and work experience vary, and their understanding of the industry varies. These factors lead to significant differences in the readability, logic, and standardization of program codes.

[0005] 3) Difficulty in maintenance: Due to the diversity of program codes and the lack of unified standards, it is very difficult to maintain and upgrade the program, which increases the maintenance cost.

[0006] 4) Poor customer experience: The operating interface and program logic between different devices are inconsistent, which requires customers to spend extra time and energy to adapt to different devices during use, affecting the customer experience.

[0007] 5) Market competition pressure: With the intensification of market competition, customers have higher and higher requirements for program development efficiency and unified standards. Traditional development methods can no longer meet these requirements.

[0008] Therefore, it is necessary to develop a pharmaceutical equipment control program development platform to integrate existing resources and experience, provide a unified development environment and standardized development process to improve development efficiency, ensure consistency of program quality, and enhance customer experience. Summary of the invention

[0009] The present invention aims to provide an efficient and unified pharmaceutical equipment control program development platform and its implementation and programming method. By integrating control system hardware library, production process function library, cleaning process function library, platform standard components, customized development area, program function test panel and version control components and supporting programming methods, rapid development and unified management of control programs can be achieved. The platform can reduce the dependence on developer skills and experience, reduce complex program development work to the development of each module function, shorten the development cycle, unify the design process and specifications, ensure the consistency of program quality, and improve customer experience.

[0010] To achieve the above object, the present invention provides the following technical solutions:

[0011] 1. An efficient and unified pharmaceutical equipment control program development platform, including:

[0012] Control system hardware library, collecting hardware that needs to write control programs;

[0013] The production process function library stores common standardized production process procedures;

[0014] Cleaning process function library, which stores common standardized cleaning process procedures;

[0015] The platform standard component includes a platform standard interface component, a platform standard material library, a platform standard program library and a platform standard interface library. The platform standard interface component standardizes the software interface of the control program, and the standardization includes the function definition of the data block of the program and the address range specification thereof. The platform standard material library is a collection of image materials in the interface of the control program. The platform standard program library is a collection of other standard programs except the standardized production process program and the standardized cleaning process program. The platform standard interface library is a collection of interface materials formed by reusable interfaces and styles.

[0016] Customized development area, used by programmers to develop customized programs;

[0017] Program function test panel, used to control the test after program development is completed;

[0018] Version control component, used to record the modification history and files of programs or interfaces.

[0019] Further, the platform standard interface component includes a standard machine interface, a cleaning machine interface, and an auxiliary machine interface. The standard machine interface includes but is not limited to an operation interface, a status interface, an alarm interface, a drive interface, a control result interface, a time synchronization interface, a manufacturer parameter interface, a parameter calibration interface, a production process recipe interface, a manual parameter interface, a cleaning parameter recipe interface, a manual cleaning parameter interface, and an operation data interface. The cleaning machine interface and the auxiliary machine interface are used to exchange data with the host.

[0020] Furthermore, the platform standard material library includes a symbol library and a symbol combination library, wherein the symbol library is a collection of material component symbols required for operating the page dynamic flow chart, and the symbol combination library is a collection of related symbols combined into graphic elements with specific meanings;

[0021] Furthermore, the platform standard program library includes a general program library and a process support library, wherein the general program library refers to a collection of underlying programs for data processing functions or single motor or single valve control; the process support library refers to a collection of sub-function programs that need to be called in a single process implementation;

[0022] Furthermore, the platform standard interface library includes an interface style library and an interface program template;

[0023] Further, the customized development area includes a process development area, a customized program development area and a customized interface development area;

[0024] Further, the version control component includes program writing specification, program library version management and interface library version management modules;

[0025] The present invention also provides a method for implementing the control program development platform, comprising the following steps:

[0026] S1. Analysis of existing control programs: Starting from the existing control programs, summarize and refine the software and hardware conditions, functions and goals required for the development platform;

[0027] S2. Development platform planning: including platform hardware planning and platform software planning, planning the content, standards and usage methods of the hardware and software of the control program development platform;

[0028] S3. Build a control system hardware library: Extract the use scope, combination and complete solution of the control system hardware from the electrical list of pharmaceutical equipment, establish a detailed list of the control system hardware, record the model, specification, communication protocol and other key information of each hardware, and create a corresponding driver or interface program for each hardware;

[0029] S4. Build a production process function library, including the following steps:

[0030] (1) Build the production process data support layer: determine the data processing infrastructure required to support the production process implementation and establish a data storage and management mechanism;

[0031] (2) Build the basic control layer of the production process: Write the underlying program that supports the implementation of a single production process and perform modular design on the underlying program;

[0032] (3) Construct a single production process implementation layer: Write corresponding implementation procedures for each specific production process in the production process;

[0033] (4) Build the production process implementation layer: Integrate the implementation procedures of each single production process to achieve the control of the production process of one product by one device;

[0034] S5. Building a cleaning process function library includes the following steps:

[0035] (1) Build the cleaning process data support layer: determine the data processing infrastructure required to support the cleaning process implementation and establish a data storage and management mechanism;

[0036] (2) Construct the basic control layer of the cleaning process: Write the underlying program that supports the implementation of a single cleaning process and perform modular design on the underlying program;

[0037] (3) Construct a single cleaning process implementation layer: Write corresponding implementation procedures for each specific cleaning process in the production process;

[0038] (4) Construct the cleaning process implementation layer: Integrate the implementation procedures of each single cleaning process to achieve the control of the cleaning process of one product by one device;

[0039] S6. Planning the platform standard interface components, including the following steps:

[0040] (1) Planning standard machine interfaces: define and establish operation interface, status interface, alarm interface, drive interface, control result interface, time synchronization interface, manufacturer parameter interface, parameter calibration interface, production process recipe interface, manual parameter interface, cleaning parameter recipe interface, manual cleaning parameter interface, and operation data interface to provide a set of standardized software interfaces for the control program to achieve efficient and standardized communication and control with the hardware;

[0041] (2) Planning the cleaning machine interface: define the protocol and format of the data exchanged between the cleaning machine interface and the host to ensure that the cleaning machine can communicate effectively with the host and achieve collaborative work;

[0042] (3) Planning the auxiliary machine interface: define the protocol and format of the data exchanged between the auxiliary machine interface and the host machine to ensure that the auxiliary machine can communicate effectively with the host machine and achieve collaborative work;

[0043] S7. Establishing a platform standard material library includes the following steps:

[0044] (1) Establish a symbol library to create and collect the material component symbols required for the dynamic flow chart of the operation page;

[0045] (2) Establish a symbol combination library to combine related symbols into graphic elements with specific meanings for use in the dynamic flow chart of the operation page;

[0046] S8. Establishing a platform standard program library includes the following steps:

[0047] (1) Establish a general program library: collect or write the underlying programs for data processing functions or single motor or single valve control;

[0048] (2) Establish a process support library: write the sub-function programs that need to be called in the implementation of a single process and establish a calling mechanism for the sub-function programs;

[0049] S9. Establishing a platform standard interface library includes the following steps:

[0050] (1) Establish an interface style library: Determine a unified operating style, including the color, font, and layout specifications of the interface, collect interface elements of different styles, and form an interface style library.

[0051] (2) Establish interface program templates: Develop reusable interface program templates, including the device operation main interface template and parameter setting interface template. Define the layout and interaction logic of each interface element in the interface program template to facilitate rapid customization when developing control programs for different devices.

[0052] S10. Establish a customized development area: a special customized development area shall be allocated for programmers as the main area for writing non-standard programs, and necessary development tools and environments shall be provided, including but not limited to programming language support, code editing tools, debugging tools, and an integration mechanism between customized programs and the development platform shall be established to ensure that customized programs can work in coordination with other parts of the development platform;

[0053] (1) Establish a process development area;

[0054] (2) Establish a custom program development area;

[0055] (3) Establish a custom interface development area;

[0056] S11. Create a program function test panel, select appropriate test tools and build a test environment based on the technology stack of the development platform, and develop the test panel interface;

[0057] S12. Create a version control component, select a suitable version management system and integrate it into the development platform, and establish program writing specifications, program library version management, and interface library version management modules;

[0058] The present invention also provides a programming method for a control program development platform, comprising the following steps:

[0059] (1) Determine the electrical parameter table: Analyze the control object and control process from the structural configuration and assembly diagram of the pharmaceutical equipment to form an electrical parameter table;

[0060] (2) Control system hardware selection: Analyze and determine the control scheme from the control object and process requirements in the electrical parameter table, and select the required hardware from the control system hardware library. If the control system hardware library does not exist, the corresponding model can be added to the control system hardware library;

[0061] (3) Production process function planning: Select a suitable production process from the production process function library. If the production process function library does not have such a process, you can add a corresponding production process program. After successful testing, the process can be stored in the production process function library for subsequent use;

[0062] (4) Cleaning process function planning: Select a suitable cleaning process from the cleaning process function library. If the cleaning process function library does not have such a process, you can add a corresponding cleaning process program. After successful testing, the process can be stored in the cleaning process function library for subsequent use;

[0063] (5) Operation interface function planning: Compare the equipment PI&D diagram with the platform standard material library. If the platform standard material library does not have relevant materials, use special tools to create materials and add them to the platform standard material library for use. If the platform standard material library has relevant materials, use them directly and select appropriate interface program templates from the platform standard interface library for the equipment. Otherwise, create a new interface program suitable for the equipment and add it to the platform standard interface library for use.

[0064] (6) Platform interface function planning: In the platform standard interface component, the platform interface function planning work is completed according to the device variable planning and address table, so as to generate a variable table for use by the control program.

[0065] (7) General program writing: Select a general program from the platform standard program library. If there is no suitable general program, it will be incorporated into the platform standard program library after being rewritten and tested. Select a suitable interface program template from the platform standard interface library for the general program. If there is no suitable interface program, it will be rewritten and incorporated into the platform standard interface library.

[0066] (8) Customized program writing: Write customized control programs and interface programs in the customized development area;

[0067] (9) Program testing: After the program is completed, use the program function test panel to debug the written program;

[0068] (10) Version Control: Describe program version control and change history in the version control component.

[0069] Compared with the prior art, the present invention has the following beneficial effects:

[0070] The present invention realizes the rapid development and unified management of pharmaceutical equipment control programs by integrating modules such as control system hardware library, production process function library, cleaning process function library, platform standard components, customized development area, program function test panel and version control components and supporting programming methods. The platform can reduce the dependence on the skills and experience of developers, avoid professional problems caused by personnel skills and experience levels, reduce complex program development work to the development of each module function, save a lot of repetitive development work, shorten the development cycle, improve development efficiency, unify design processes and specifications, ensure the consistency of program quality, and improve customer experience. The present invention can not only be used on pharmaceutical equipment, but also can be promoted to other industries. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Figure 1 A schematic diagram of the components of the control program development platform;

[0072] Figure 2 A flow chart of the implementation method of the control program development platform;

[0073] Figure 3 Flowchart of programming method for control program development platform;

[0074] Figure 4 This is a schematic diagram of the control system hardware library composition;

[0075] Figure 5 It is a schematic diagram of the composition of the production process function library;

[0076] Figure 6 It is a schematic diagram of the composition of the cleaning process function library;

[0077] Figure 7 This is a schematic diagram of the platform's standard components;

[0078] Figure 8 It is a schematic diagram of the customized development zone composition;

[0079] Fig. 9 A schematic diagram of the version control component composition;

[0080] Fig.10 Flow chart of the method for programming a continuous coating machine; DETAILED DESCRIPTION

[0081] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments.

[0082] An efficient and unified pharmaceutical equipment control program development platform, such as Figure 1As shown, it includes control system hardware library, production process function library, cleaning process function library, platform standard components, customized development area, program function test panel and version control components:

[0083] The control system hardware library collects hardware that needs to be programmed. The library is formed from the long-term design experience of pharmaceutical equipment. By summarizing the bill of materials of shipped equipment, it collects hardware that needs to be programmed, such as controllers and their expansion modules, fieldbus modules, touch screens, printers, etc., providing developers with a hardware-related resource base, avoiding the repeated exploration process of hardware selection, and improving the efficiency of hardware configuration. The control system hardware library can be further divided into controller hardware library, touch screen hardware library, printer hardware library, etc. For the specific content of the control system hardware library, please refer to Figure 4 ;

[0084] The production process function library stores common standardized production process procedures. Although there are differences in the production processes of different pharmaceutical equipment, since they belong to the same industry, there are many repeated single production processes. These reusable single production process procedures are refined into standard library procedures, and a production process function library is created. Gradually accumulate and then form a rich production process function library. For example, the boiling bed can be divided into preheating, feeding, material preheating, spraying, drying, cooling, discharging and other processes. The film coating machine can also be divided into preheating, feeding, material preheating, coating, drying, cooling, discharging and other processes. It can be seen that most of the process implementations of these two types of equipment are similar. In this case, these process procedures can be reused to reduce the development workload. The production process function library can be subdivided into wet process function library, fluidized bed process function library, coating process function library, etc. For the specific content of the production process function library, please refer to Figure 5 ;

[0085] The cleaning process function library stores common standardized cleaning process procedures. Similar to the production process function library, although the cleaning processes of different pharmaceutical equipment are different, there are many repeated single cleaning processes. These reusable single cleaning process procedures are refined into standard library procedures to form a cleaning process function library. Compared with the production process function library, the cleaning process function library has fewer contents but higher reusability. For example, processes such as drinking water cleaning, hot water cleaning, and purified water cleaning can be reused between different equipment. The cleaning process function library can be further divided into coating machine cleaning process library, wet cleaning process library, fluidized bed cleaning process library, etc. For the specific contents of the cleaning process function library, please refer to Figure 6 ;

[0086] The platform standard components include the platform standard interface components, platform standard material library, platform standard program library and platform standard interface library. The platform standard interface components standardize the software interface of the control program, including the data block function definition and address range specification of the program. The platform standard material library is a collection of image materials in the interface of the control program, which provides a material basis for the production of the operation interface and ensures the consistency of the interface style. The platform standard program library is a collection of other standard programs except the standardized production process program and the standardized cleaning process program, which provides a common program module for program development. The platform standard interface library is a collection of interface materials formed by reusable interfaces and styles, which helps to unify the operation style and interface and improve customer experience. For the specific content of the platform standard components, please refer to Figure 7 ;

[0087] The platform standard interface components include standard machine interface, cleaning machine interface, and auxiliary machine interface. The standard machine interface includes but is not limited to operation interface, status interface, alarm interface, drive interface, control result interface, time synchronization interface, manufacturer parameter interface, parameter calibration interface, production process recipe interface, manual parameter interface, cleaning parameter recipe interface, manual cleaning parameter interface, and operation data interface. The cleaning machine interface and auxiliary machine interface are used to exchange data with the host. These interfaces are generally fixed, making the interaction between different programs more standardized and unified.

[0088] The platform standard material library includes the symbol library and the symbol combination library. The symbol library is a collection of material component symbols required for the dynamic flow chart of the operation page, including materials such as pumps, fans, valves, instruments, and special symbols. The symbol combination library is a collection of related symbols combined into graphic elements with specific meanings, including pump combination symbols, fan combination symbols, valve combination symbols, instrument combination symbols, etc.

[0089] The platform standard program library includes a general program library and a process support library. The general program library refers to a collection of underlying programs for data processing functions or single motor or single valve control, including analog data processing, moisture content calculation, data type conversion, motor control, switch valve control, regulating valve control and other underlying support programs. The process support library refers to a collection of sub-function programs that need to be called in the implementation of a single process, such as material conveying function, temperature control function, etc.

[0090] The platform standard interface library includes interface style library and interface program templates;

[0091] The Customized Development Zone is used by programmers to develop customized programs. It is the main area for programmers to write programs. Customized programs are relative to standard programs. Some customized programs can also be converted into standard programs because they have certain reusability. The Customized Development Zone provides customized program development functions to meet customer customization needs. For the content of the Customized Development Zone, please refer to Figure 8 ;

[0092] The customized development area includes the process development area, the customized program development area and the customized interface development area. The process development area can be subdivided into the production process development area, the cleaning process development area, etc. The customized program development area can be subdivided into the general program development area, the process bottom layer development area, the control algorithm development area, etc. The customized interface development area can be subdivided into the interface material development area, the combination symbol development area, the interface template development area, etc.

[0093] Program function test panel, used to control the test after program development is completed;

[0094] Version control components are used in the process of program design and maintenance to record the modification history and files of programs or interfaces, which facilitates the management and tracing of programs. For details about version control components, please refer to Fig. 9 .

[0095] The version control component includes program writing specifications, program library version management and interface library version management modules. The program writing specifications include main program writing templates, process writing templates, variable declaration templates, etc. The program library version management is used to manage the version history and changes of the control program, and the interface library version management is used to manage the version history and changes of the interface program.

[0096] Development platform implementation methods, such as Figure 2 As shown, the following steps are included:

[0097] S1. Analysis of existing control programs: Starting from the existing control programs, summarize and refine the software and hardware conditions, functions and goals required for the development platform to provide a basis for platform planning;

[0098] S2. Development platform planning: including platform hardware planning and platform software planning, planning the content, standards and usage methods of the hardware and software of the control program development platform;

[0099] S3. Build a control system hardware library: Extract the use scope, combination and complete solution of the control system hardware from the electrical list of pharmaceutical equipment, establish a detailed list of the control system hardware, record the model, specification, communication protocol and other key information of each hardware, and create a corresponding driver or interface program for each hardware, so that the functions of these hardware can be easily called when developing the control program;

[0100] S4. Build a production process function library, including the following steps:

[0101] (1) Build the production process data support layer: Determine the data processing infrastructure required to support the production process implementation, which may include defining common data types (such as integers, floating-point numbers, Boolean values, etc.) and data combinations (such as structures, arrays, etc.), establishing data storage and management mechanisms, and ensuring the accuracy, integrity, and security of the data;

[0102] (2) Build the basic control layer of the production process: Write the underlying programs that support the implementation of a single production process. These underlying programs cover basic control logic, such as equipment start-up, stop-down, and operation status monitoring. The underlying programs are modularly designed to facilitate reuse in different production processes.

[0103] (3) Constructing a single production process implementation layer: For each specific production process in the production process, such as preheating, feeding, spraying, drying, cooling, discharging, etc., write the corresponding implementation program to ensure that each single production process implementation program interacts well with the basic control layer and data support layer, and can obtain the required data and perform corresponding control operations;

[0104] (4) Build the production process implementation layer: Integrate the implementation procedures of each single production process, realize the control of the production process of one product by one device, optimize the overall production process flow, and ensure the efficiency, stability and reliability of the production process;

[0105] S5. Building a cleaning process function library includes the following steps:

[0106] (1) Build the cleaning process data support layer: Determine the data processing infrastructure required to support the implementation of the cleaning process, which may include defining common data types (such as integers, floating-point numbers, Boolean values, etc.) and data combinations (such as structures, arrays, etc.), establishing data storage and management mechanisms, considering the data processing of cleaning parameters (such as cleaning time, cleaning temperature, etc.), and ensuring the accuracy, integrity and security of the data;

[0107] (2) Building the basic control layer of the cleaning process: Write the underlying program that supports the implementation of a single cleaning process, including basic cleaning operation control, such as cleaning liquid supply, cleaning nozzle motion control, etc., and modularize the underlying program to facilitate reuse in different cleaning scenarios;

[0108] (3) Constructing a single cleaning process implementation layer: For each specific cleaning process in the production process, such as drinking water cleaning, hot water cleaning, purified water cleaning, etc., write a corresponding implementation procedure to ensure that the single cleaning process implementation procedure interacts effectively with the cleaning process data support layer and the cleaning process basic control layer, and can perform cleaning operations according to the set cleaning parameters;

[0109] (4) Construct the cleaning process implementation layer: Integrate the implementation procedures of each single cleaning process to achieve the control of the cleaning process of one product by one device, optimize the cleaning process flow, improve the cleaning effect and efficiency, and consider resource conservation in the cleaning process, such as the amount of cleaning fluid used;

[0110] S6. Planning the platform standard interface components, including the following steps:

[0111] (1) Plan standard machine interfaces: define and establish operation interfaces, status interfaces, alarm interfaces, drive interfaces, control result interfaces, time synchronization interfaces, manufacturer parameter interfaces, parameter calibration interfaces, production process recipe interfaces, manual parameter interfaces, cleaning parameter recipe interfaces, manual cleaning parameter interfaces, and operation data interfaces, and provide a set of standardized software interfaces for the control program to achieve efficient and standardized communication and control with the hardware. The operation interface includes the functions and interaction logic of the equipment's operation buttons (such as start, stop, pause, etc.), the status interface is used to obtain the equipment's operating status (such as running, stopped, fault, etc.), the alarm interface specifies how the equipment sends an alarm signal under abnormal conditions (such as overtemperature, abnormal pressure, etc.) and the format of the alarm information, and the drive interface is used to control the equipment's hardware driver to ensure that the equipment can The control result interface feeds back the result of the control operation to other related modules or user interfaces. The time synchronization interface is used to ensure the time synchronization between the modules inside the equipment and with the external system (such as the production management system). The manufacturer parameter interface is used to set and obtain the parameters specific to the equipment manufacturer. The parameter calibration interface is used to calibrate the key parameters of the equipment. The production process recipe interface is used to store and call the production process recipes of different products. The manual parameter interface is used to set the operating parameters of the equipment in the manual operation mode. The cleaning parameter recipe interface is used to store and call the cleaning parameter recipes of different cleaning tasks. The manual cleaning parameter interface is used to set the cleaning parameters in the manual cleaning operation mode. The operation data interface is used to collect and transmit the operation data of the equipment (such as production quantity, operation time, etc.);

[0112] (2) Planning the cleaning machine interface: define the protocol and format of the data exchanged between the cleaning machine interface and the host to ensure that the cleaning machine can communicate effectively with the host and achieve collaborative work;

[0113] (3) Planning the auxiliary machine interface: define the protocol and format of the data exchanged between the auxiliary machine interface and the host machine to ensure that the auxiliary machine can communicate effectively with the host machine and achieve collaborative work;

[0114] S7. Establishing a platform standard material library includes the following steps:

[0115] (1) Establish a symbol library to create and collect the material component symbols required for the dynamic flow chart of the operation page, including various symbols used to represent equipment, process steps, status, etc., such as pumps, fans, valves, instruments, special symbols, etc.;

[0116] (2) Establish a symbol combination library to combine related symbols into graphic elements with specific meanings for use in dynamic flow charts on the operation page. For example, a pump combination symbol can combine a pump and related pipe and control valve symbols to represent a pumping system;

[0117] S8. Establishing a platform standard program library includes the following steps:

[0118] (1) Establish a general program library: collect or write the underlying programs for data processing functions or single motor or single valve control to provide basic program support for program development;

[0119] (2) Establish a process support library: Write the sub-function programs that need to be called in the implementation of a single process, such as the material transportation sub-function and the temperature control sub-function, and establish a calling mechanism for the sub-function programs to ensure that these sub-function programs can be correctly called during the process implementation;

[0120] S9. Establishing a platform standard interface library includes the following steps:

[0121] (1) Establish an interface style library: Determine a unified operating style, including the color, font, and layout specifications of the interface, collect interface elements of different styles, and form an interface style library.

[0122] (2) Establishing interface program templates: Develop reusable interface program templates, including the device operation main interface template and the parameter setting interface template. Define the layout and interaction logic of each interface element in the interface program template to facilitate rapid customization when developing control programs for different devices. Different from the platform standard material library in step S7, the standard interface library focuses on the complete operation page and its page style, with the purpose of unifying the operation style and interface and improving customer experience.

[0123] S10. Establish a customized development area: a special customized development area shall be allocated for programmers as the main area for writing non-standard programs, and necessary development tools and environments shall be provided, including but not limited to programming language support, code editing tools, debugging tools, and an integration mechanism between customized programs and the development platform shall be established to ensure that customized programs can work in coordination with other parts of the development platform;

[0124] (1) Establish a process development area;

[0125] (2) Establish a custom program development area;

[0126] (3) Establish a custom interface development area;

[0127] S11. Create a program function test panel, select appropriate test tools and build a test environment based on the technology stack of the development platform, and develop the test panel interface;

[0128] S12. Create a version control component, select a suitable version management system and integrate it into the development platform, and establish program writing specifications, program library version management, and interface library version management modules;

[0129] Development platform programming methods, such as Figure 3 As shown, the following steps are included:

[0130] (1) Determine the electrical parameter table: Analyze the control object and control process from the structural configuration and assembly diagram of the pharmaceutical equipment to form an electrical parameter table to provide basic data for subsequent steps;

[0131] (2) Control system hardware selection: Analyze and determine the control scheme from the control object and process requirements in the electrical parameter table, and select the required hardware from the control system hardware library. If the control system hardware library does not exist, the corresponding model can be added to the control system hardware library;

[0132] (3) Production process function planning: Select a suitable production process from the production process function library. If the production process function library does not have such a process, you can add the corresponding production process program. After successful testing, the process can be stored in the production process function library for subsequent use. It should be noted that since there are many similar or directly usable pharmaceutical production processes, by calling the processes in the production process function library, the work of repeated programming is reduced. Some similar processes can be modified into new processes based on the original processes. Similarly, repeated work is reduced, the development workload is reduced, and efficiency is improved;

[0133] (4) Cleaning process function planning: Select a suitable cleaning process from the cleaning process function library. If the cleaning process function library does not have such a process, you can add a corresponding cleaning process program. After successful testing, the process can be stored in the cleaning process function library for subsequent use;

[0134] (5) Operation interface function planning: Compare the equipment PI&D diagram with the platform standard material library. If the platform standard material library does not have relevant materials, use special tools to create materials and add them to the platform standard material library for use. If the platform standard material library has relevant materials, use them directly and select appropriate interface program templates from the platform standard interface library for the equipment. Otherwise, create a new interface program suitable for the equipment and add it to the platform standard interface library for use.

[0135] (6) Platform interface function planning: In the platform standard interface component, the platform interface function planning work is completed according to the device variable planning and address table, so as to generate a variable table for use by the control program.

[0136] (7) General program writing: Select a general program from the platform standard program library. If there is no suitable general program, it will be incorporated into the platform standard program library after being rewritten and tested. Select a suitable interface program template from the platform standard interface library for the general program. If there is no suitable interface program, it will be rewritten and incorporated into the platform standard interface library.

[0137] (8) Customized program writing: Write customized control programs and interface programs in the customized development area;

[0138] (9) Program testing: After the program is completed, use the program function test panel to debug the written program;

[0139] (10) Version Control: Describe program version control and change history in the version control component.

[0140] The following example uses the existing film coating machine program library to develop a continuous coating machine program on this development platform. Fig.10 As shown, the programming method includes the following steps:

[0141] (1) Determine the electrical parameter table: Starting from the P&ID diagram and structural assembly diagram of the continuous coating machine, analyze the structure of the continuous coating machine, the sensors and actuators of each structure, the production process and its actuator implementation, and compare the structural configuration and assembly diagram of the film coating machine to form an electrical parameter table;

[0142] (2) Control system hardware selection: Extract the control system IO table from the electrical parameter table to determine the configuration of the continuous coating machine control system. Compared with the film coating machine, the control solution uses the core hardware of the film coating machine and selects the S7-1200 controller, smart screen, and office printer from the control system hardware library;

[0143] (3) Production process function planning: Extract each production process function of the continuous coating machine from the electrical parameter table, as well as the implementation process of these process functions and the setting of process parameters, and prepare the process flow document of the continuous coating machine. Compared with the production process of the film coating machine, the continuous coating machine can select preheating, drying, cooling, spraying and other processes from the production process function library;

[0144] (4) Cleaning process function planning: Extract each cleaning process function of the continuous coating machine from the electrical parameter table, as well as the implementation process of these cleaning process functions and the setting of cleaning process parameters, and prepare the cleaning process flow document of the continuous coating machine. Compared with the cleaning process of the film coating machine, the continuous coating machine can select drinking water, hot water, purified water, air blowing and other processes from the cleaning process function library;

[0145] (5) Operation interface function planning: interface materials do not need to be supplemented. Operation interface function planning should include production P&ID process flow chart design, cleaning P&ID process flow chart design, three working modes (jog, manual, automatic) operation button settings, process parameter settings, process data calibration settings, data recording functions, audit tracking function settings, non-standard configuration function settings, one-key save and restore data function settings, trend chart and historical trend chart settings, alarm and alarm record settings, etc. Compared with the process of film coating machine, the interface style of continuous coating machine is generally similar. Three working modes, process data calibration settings, data recording functions, audit tracking function settings, non-standard configuration function settings, one-key save and restore data function settings, trend chart and historical trend chart settings, alarm and alarm record settings, etc. can be used. Since there is a template program, only the variable address needs to be changed;

[0146] (6) Platform interface function planning: The program interface mainly includes: IO software interface, operation button interface, equipment status display interface, process drive interface, process drive result interface, basic parameter interface, manual parameter interface, recipe interface, inching parameter interface, execution parameter interface, data calibration interface, non-standard parameter interface, time, product information interface, operation data interface, cleaning equipment docking interface, purchased equipment docking interface, etc. The continuous coating machine basically follows the software interface scope of the film coating machine, and the specific functions are set within the functional scope;

[0147] (7) General program writing: The continuous coating machine uses the underlying programs and sub-function programs in the standard program library, such as motor control, switch valve control, regulating valve control, temperature control, spraying process, air volume control, negative pressure control, etc., and uses the interface programs in the platform standard interface library. In addition, the servo motor speed and positioning function programs are added and added to the platform general program library;

[0148] (8) Customized program writing: For programs not available in the platform, the programs of the continuous coating machine need to be customized. These customized programs mainly include host control programs, curtaining, automatic quantitative feeding, automatic discharging, coating film thickness detection, continuous control algorithm, new endpoint determination algorithm, etc.

[0149] (9) Program testing: After the program is completed, a new test page is developed in the program function test panel and program testing is performed;

[0150] (10) Version Control: The version control component explains the program version control and change history, and records the changes made to historical versions as the versions are added.

[0151] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. An efficient and unified pharmaceutical equipment control program development platform, characterized by: include: Control system hardware library, collecting hardware that needs to write control programs; The production process function library stores common standardized production process procedures; Cleaning process function library, which stores common standardized cleaning process procedures; The platform standard component includes a platform standard interface component, a platform standard material library, a platform standard program library and a platform standard interface library. The platform standard interface component standardizes the software interface of the control program, and the standardization includes the function definition of the data block of the program and the address range specification thereof. The platform standard material library is a collection of image materials in the interface of the control program. The platform standard program library is a collection of other standard programs except the standardized production process program and the standardized cleaning process program. The platform standard interface library is a collection of interface materials formed by reusable interfaces and styles. Customized development area, used by programmers to develop customized programs; Program function test panel, used to control the test after program development is completed; Version control component, used to record the modification history and files of programs or interfaces.

2. The development platform according to claim 1, characterized in that: The platform standard interface components include a standard machine interface, a cleaning machine interface, and an auxiliary machine interface. The standard machine interface includes but is not limited to an operation interface, a status interface, an alarm interface, a drive interface, a control result interface, a time synchronization interface, a manufacturer parameter interface, a parameter calibration interface, a production process recipe interface, a manual parameter interface, a cleaning parameter recipe interface, a manual cleaning parameter interface, and an operation data interface. The cleaning machine interface and the auxiliary machine interface are used to exchange data with the host.

3. The development platform according to claim 1, characterized in that: The platform standard material library includes a symbol library and a symbol combination library. The symbol library is a collection of material component symbols required for operating the page dynamic flow chart, and the symbol combination library is a collection of related symbols combined into graphic elements with specific meanings.

4. The development platform according to claim 1, characterized in that: The platform standard program library includes a general program library and a process support library. The general program library refers to a collection of underlying programs for data processing functions or single motor or single valve control; the process support library refers to a collection of sub-function programs that need to be called in a single process implementation.

5. The development platform according to claim 1, characterized in that: The platform standard interface library includes an interface style library and an interface program template.

6. The development platform according to claim 1, characterized in that: The customized development area includes a process development area, a customized program development area and a customized interface development area.

7. The development platform according to claim 1, characterized in that: The version control component includes program writing specification, program library version management and interface library version management modules.

8. A method for implementing the development platform according to any one of claims 1 to 7, characterized in that: The following steps are involved: S1. Analysis of existing control programs: Starting from the existing control programs, summarize and refine the software and hardware conditions, functions and goals required for the development platform; S2. Development platform planning: including platform hardware planning and platform software planning, planning the content, standards and usage methods of the hardware and software of the control program development platform; S3. Build a control system hardware library: Extract the use scope, combination and complete solution of the control system hardware from the electrical list of pharmaceutical equipment, establish a detailed list of the control system hardware, record the model, specification, communication protocol and other key information of each hardware, and create a corresponding driver or interface program for each hardware; S4. Build a production process function library, including the following steps: (1) Build the production process data support layer: determine the data processing infrastructure required to support the production process, and establish a data storage and management mechanism; (2) Build the basic control layer of the production process: write the underlying program that supports the implementation of a single production process, and perform modular design on the underlying program; (3) Construct a single production process implementation layer: Write corresponding implementation procedures for each specific production process in the production process; (4) Constructing the production process implementation layer: integrating the implementation procedures of each single production process to achieve the control of the production process of one product by one device; S5. Building a cleaning process function library includes the following steps: (1) Build a cleaning process data support layer: determine the data processing infrastructure required to support the cleaning process, and establish a data storage and management mechanism; (2) Construct the basic control layer of the cleaning process: write the underlying program that supports the implementation of a single cleaning process, and perform modular design on the underlying program; (3) Construct a single cleaning process implementation layer: Write corresponding implementation procedures for each specific cleaning process in the production process; (4) Construct the cleaning process implementation layer: Integrate the implementation procedures of each single cleaning process to achieve the control of the cleaning process of a product by one device; S6. Planning the platform standard interface components, including the following steps: (1) Planning standard machine interfaces: define and establish operation interface, status interface, alarm interface, drive interface, control result interface, time synchronization interface, manufacturer parameter interface, parameter calibration interface, production process recipe interface, manual parameter interface, cleaning parameter recipe interface, manual cleaning parameter interface, and operation data interface, providing a set of standardized software interfaces for the control program to achieve efficient and standardized communication and control with the hardware; (2) Planning the cleaning machine interface: define the protocol and format of the data exchange between the cleaning machine interface and the host to ensure that the cleaning machine can communicate effectively with the host and achieve collaborative work; (3) Planning the auxiliary machine interface: define the protocol and format of the data exchanged between the auxiliary machine interface and the host machine to ensure that the auxiliary machine can communicate effectively with the host machine and achieve collaborative work; S7. Establishing a platform standard material library includes the following steps: (1) Establish a symbol library to create and collect the material component symbols required for the dynamic flow chart of the operation page; (2) Establish a symbol combination library to combine related symbols into graphic elements with specific meanings for use in the dynamic flow chart of the operation page; S8. Establishing a platform standard program library includes the following steps: (1) Establish a general program library: collect or write the underlying programs for data processing functions or single motor or single valve control; (2) Establish a process support library: write the sub-function programs that need to be called in the implementation of a single process and establish a calling mechanism for the sub-function programs; S9. Establishing a platform standard interface library includes the following steps: (1) Establish an interface style library: determine a unified operating style, including the color, font, and layout specifications of the interface, collect interface elements of different styles, and form an interface style library; (2) Establish interface program templates: Develop reusable interface program templates, including the main interface template for equipment operation and the parameter setting interface template. Define the layout and interaction logic of each interface element in the interface program template to facilitate rapid customization when developing control programs for different devices. S10. Establish a customized development area: a special customized development area shall be allocated for programmers as the main area for writing non-standard programs, and necessary development tools and environments shall be provided, including but not limited to programming language support, code editing tools, debugging tools, and an integration mechanism between customized programs and the development platform shall be established to ensure that customized programs can work in coordination with other parts of the development platform; (1) Establishing a process development area; (2) Establish a custom program development area; (3) Establish a custom interface development area; S11. Create a program function test panel, select appropriate test tools and build a test environment based on the technology stack of the development platform, and develop the test panel interface; S12. Create a version control component, select a suitable version management system and integrate it into the development platform, and establish program writing specifications, program library version management, and interface library version management modules.

9. A programming method for the development platform according to any one of claims 1 to 8, characterized in that: The following steps are involved: (1) Determine the electrical parameter table: Analyze the control object and control process from the structural configuration and assembly diagram of the pharmaceutical equipment to form an electrical parameter table; (2) Control system hardware selection: Analyze and determine the control scheme from the control object and process requirements in the electrical parameter table, and select the required hardware from the control system hardware library. If the control system hardware library does not exist, the corresponding model can be added to the control system hardware library; (3) Production process function planning: Select a suitable production process from the production process function library. If the production process function library does not have such a process, you can add the corresponding production process program. After successful testing, the process can be stored in the production process function library for subsequent use; (4) Cleaning process function planning: Select a suitable cleaning process from the cleaning process function library. If the cleaning process function library does not have such a process, you can add a corresponding cleaning process program. After successful testing, store the process in the cleaning process function library for subsequent use; (5) Operation interface function planning: Compare the equipment PI&D diagram with the platform standard material library. If the platform standard material library does not have relevant materials, use special tools to create materials and add them to the platform standard material library for use. If the platform standard material library has relevant materials, use them directly and select appropriate interface program templates from the platform standard interface library for the equipment. Otherwise, create a new interface program suitable for the equipment and add it to the platform standard interface library for use. (6) Platform interface function planning: According to the device variable planning and address table in the platform standard interface component, the platform interface function planning work is completed to generate a variable table for control program use; (7) General program writing: select general programs from the platform standard program library. If there is no suitable general program, it will be incorporated into the platform standard program library after being rewritten and tested. Select appropriate interface program templates from the platform standard interface library for the general program. If there is no suitable interface program, it will be rewritten and incorporated into the platform standard interface library. (8) Customized program writing: Write customized control programs and interface programs separately in the customized development area; (9) Program testing: After the program is completed, use the program function test panel to debug the written program; (10) Version control: Describe program version control and change history in the version control component.

Images