A method and system for monitoring the state of an IO point of a siemens numerical control machine tool

Abstract

The present application belongs to the technical field of man-machine interaction of numerical control machine tools, and relates to a monitoring method and system for IO point state of a Siemens numerical control machine tool, which comprises the following steps: exporting a point information table from an electrical design software, screening out target points and corresponding point descriptions related to numerical control machine tool monitoring; performing preprocessing and sorting; grouping according to grouping rules, generating a number and writing into a text file; calling a loading instruction to read the text file during the loading process of a man-machine interface, and performing page binding; and displaying and refreshing according to the state of a page register during running. The technical scheme of the present application realizes unified management and dynamic display of point data by preprocessing, grouping numbering and external file loading, in combination with page binding and register control, and can meet the needs of efficient implementation of point data standardization processing, dynamic page display and refreshing of a man-machine interface.

Description

Technical Field

[0001] This invention belongs to the field of human-machine interaction technology for CNC machine tools, and specifically relates to a method and system for monitoring the status of I / O points of Siemens CNC machine tools. Background Technology

[0002] In existing technologies, the human-machine interface (HMI) of CNC machine tools typically relies on point information tables exported from electrical design software. Point addresses and functional descriptions are manually entered into the interface configuration using simple scripts to meet the needs of machine tool debugging and operational status monitoring. However, existing point monitoring methods have some significant shortcomings.

[0003] In practical applications, the point table often contains a large number of I / O points related to machine tool operation. After exporting, this point information often becomes out of order, duplicated, conflicting, or missing. Traditional methods rely on manual sorting and verification, which is not only inefficient but also prone to errors, leading to inconsistencies between the subsequent interface display and the actual PLC points. At the same time, the existing interface binding method is mostly fixed writing, that is, the points and descriptions are directly embedded in the interface project. Once the point data is adjusted, the interface file needs to be modified and redeployed, which increases maintenance costs and reduces debugging flexibility.

[0004] Furthermore, the existing monitoring interface lacks versatility in its display method, and cannot group, number, or paginate a large number of points. This results in a slow response time when the number of points expands, making it difficult for users to quickly locate target points. More importantly, the existing technology relies on a fixed script for the point display refresh mechanism, which cannot be combined with registers to achieve efficient pagination control. This leads to unsmooth interface refresh during operation, affecting the real-time performance and intuitiveness during debugging.

[0005] Therefore, it is evident that existing technologies often suffer from problems such as low efficiency in standardizing point data processing and imperfect interface pagination and refresh mechanisms during the monitoring of CNC machine tool I / O (Input / Output) point status. These are the shortcomings of existing technologies.

[0006] In view of this, it is very necessary to provide a method and system for monitoring the status of I / O points of Siemens CNC machine tools in order to solve the above-mentioned defects in the prior art. Summary of the Invention

[0007] The purpose of this invention is to address the shortcomings of existing technologies, such as low efficiency in standardizing point data processing and imperfect interface pagination and refresh mechanisms, in the monitoring of I / O point status of CNC machine tools. This invention provides a method and system for monitoring the I / O point status of Siemens CNC machine tools to solve the aforementioned technical problems.

[0008] To achieve the above objectives, the present invention provides the following technical solution:

[0009] A method for monitoring the status of I / O points on a Siemens CNC machine tool includes the following steps:

[0010] Export the point information table from the electrical design software, filter out the target points and corresponding point descriptions related to CNC machine tool monitoring, and generate initial data;

[0011] Preprocessing and sorting are performed on the initial data to generate mapping data. The preprocessing includes at least one of conflict detection, duplicate merging, and missing data completion.

[0012] The mapped data is grouped according to a preset grouping rule and numbered to construct a group array;

[0013] Write the grouped array to a text file, which is an external file that the CNC machine tool can parse;

[0014] During the loading process of the human-computer interface, a loading instruction is invoked to read the text file, and pagination binding is performed on the human-computer interface;

[0015] During operation, the target point and its corresponding point description are displayed and refreshed by paging based on the state of the paging register.

[0016] By adopting the above technical solution, the point information table exported by the electrical design software is preprocessed, grouped, numbered, and externally loaded. Combined with the pagination binding and register control of the human-machine interface, unified management and dynamic display of point data can be achieved. This can significantly improve the efficiency of standardized processing of point data and the flexibility of interface display, and meet the needs of efficient standardized processing of point data and dynamic pagination display and refresh of the human-machine interface during the monitoring of CNC machine tool I / O point status.

[0017] Specifically, by exporting the point information table from electrical design software and filtering out the target points and descriptions related to monitoring, the original complex data is transformed into initial data that can be directly used for monitoring, improving the accuracy and relevance of data preparation. In the preprocessing stage, operations such as conflict detection, duplicate merging, and missing data completion ensure the consistency and integrity of point data before it is entered into the interface, reducing the potential for errors caused by manual maintenance. The mapped data is grouped and numbered to construct a structured group array, ensuring the orderly management of a large number of points in the interface and avoiding disordered calls during interface loading. The group array is written to an external text file that can be parsed by CNC machine tools, and the loading command is called to read the file when the human-machine interface is loaded, so that the binding of point descriptions to the interface no longer depends on fixed programming, but is flexibly configured in an externalized way, improving the efficiency of interface maintenance and updates. During operation, the paging register is used to control the paging display and refresh of points, realizing efficient paging management and real-time dynamic updates of a large number of points in the interface, ensuring the intuitiveness and timeliness of status monitoring.

[0018] As a preferred embodiment, conflict detection includes: when the same target location corresponds to multiple location descriptions, selecting one location description as a valid mapping based on a preset priority rule, and recording the other location descriptions in the conflict log.

[0019] This conflict detection technology introduces a preset priority rule during the point mapping stage to select multiple point descriptions for the same target point, and records the unselected point descriptions in the log, achieving the following technical effects:

[0020] First, by limiting the valid mapping through priority rules, a unique valid description can be automatically selected when there are multiple point descriptions, thereby avoiding ambiguity in point data during interface binding, ensuring the consistency and uniqueness of data mapping, and improving the reliability of point information in subsequent processing.

[0021] Second, by fully recording the descriptions of unused locations in the log, a traceability basis for data processing can be formed, enabling the source of conflict to be quickly located during subsequent maintenance or auditing, facilitating manual review and correction by engineers, thereby reducing the risk of abnormal interface display or monitoring distortion caused by location conflicts.

[0022] Third, by automatically completing conflict detection and log recording during the data governance process, the amount of manual comparison and screening can be reduced, the overall automation level of data processing can be improved, the time from point file generation to loading can be shortened, and the system can still have high operating efficiency when the number of points is large.

[0023] Fourth, by combining effective mapping and logging strategies, complete original conflict information can be preserved while ensuring the normal operation of the system. This provides strong support for the management and optimization of point data, ensuring the stability and continuity of point mapping during the long-term operation and multiple upgrades of CNC machine tools.

[0024] As a preferred method, missing data completion includes: when a target point is missing in a continuous group, generating a placeholder entry at the corresponding position and recording the placeholder entry in the missing data log and text file.

[0025] This missing data completion technology maintains group continuity by using placeholders when point data is incomplete, and retains missing information through a dual recording mechanism, achieving the following technical effects:

[0026] First, the introduction of placeholder entries ensures the continuity and integrity of the grouping structure, keeps the data in a fixed order and format during loading and calling, avoids data misalignment and interface display chaos caused by gaps, and ensures the stability of system operation and the consistency of interface refresh.

[0027] Secondly, the logging function clearly presents the missing information, allowing engineers to quickly identify the location and quantity of specific missing points during maintenance. This ensures traceability and manageability, reduces the time and effort required for manual comparison, and improves the efficiency of subsequent adjustments and optimizations.

[0028] Third, the missing markers retained in the text file ensure the standardization of the data file format. Even if the points have not been configured, the interface can still parse and load the data according to the unified data structure, thereby avoiding operational abnormalities caused by inconsistent file formats and enhancing the system's fault tolerance for incomplete data.

[0029] Fourth, this supplementation mechanism allows the system to expand the number of points or make engineering changes without reconstructing the overall group array. It only needs to add actual points within the existing framework, which improves the scalability of the system, reduces the workload of repeated development and maintenance, and ensures the continuity and reliability of CNC machine tools in long-term operation.

[0030] Preferably, grouping the mapping data according to a preset grouping rule and generating numbers includes: setting numbering intervals for the target points and their corresponding point descriptions, and assigning numbers within the same numbering interval according to the order of the target points.

[0031] This numbering generation technology solution establishes numbering intervals during point data processing and assigns numbers sequentially, achieving the following technical effects:

[0032] First, the setting of numbering intervals ensures that different types of points have clear logical boundaries, enabling the system to quickly identify the category and process accordingly when the interface is called, avoiding conflicts and ambiguities caused by mixing the same numbering space, and improving the standardization and consistency of point management.

[0033] Secondly, the sequential allocation method ensures that the numbers and locations correspond in physical arrangement, which facilitates quick location and indexing when the interface is displayed in pages, reduces additional query overhead, improves the efficiency of the locations on the interface, and also makes it easier for users to understand and use.

[0034] Third, the numbering mechanism that combines intervalization and sequentialization makes the point mapping relationship more intuitive. During subsequent maintenance and expansion, points can be smoothly added or adjusted according to established rules, avoiding large-scale modification work caused by numbering chaos and reducing the risks and complexity in project implementation.

[0035] Fourth, this numbering strategy also provides room for system scalability. Different numbering intervals are kept isolated, and numbering segments can be reserved for future additions of point categories or functions, thereby ensuring that the entire monitoring system maintains an orderly numbering system and stable data management capabilities during long-term operation and continuous upgrades.

[0036] As a preferred approach, during the loading process of the human-machine interface, a lifecycle function is called to read the text file and load the grouped array into memory, and when the human-machine interface exits, the lifecycle function is called to release the grouped array.

[0037] This technical solution for loading and releasing lifecycle functions establishes a unified data management mechanism during interface startup and exit, achieving the following technical effects:

[0038] First, during the interface loading process, the external text file is read directly by calling the lifecycle function and the grouped array is written into memory. This ensures that the point data can be loaded completely and accurately during interface initialization, avoiding the uncertainty caused by relying on manual import or script execution, thereby improving the stability and controllability of the system operation.

[0039] Secondly, by releasing the grouped array using lifecycle functions after the operation ends, memory resources can be cleaned up in a timely manner when exiting the interface, preventing excessive memory usage or resource conflicts caused by data residue. This allows the system to maintain good performance during long-term continuous operation and improves the overall resource management capability.

[0040] Third, the mechanism forms an automated closed-loop process in the interface loading and exit stages, so that there are clear control nodes in the entire process of loading, using and releasing point data, reducing the links of manual intervention and improving the standardization of interface engineering and the predictability of the operation process.

[0041] Fourth, during maintenance and upgrades, the introduction of lifecycle functions enables the system to quickly identify loading and releasing time points, facilitating developers to add targeted logging, anomaly detection, or rollback strategies, providing further assurance for the reliable operation of the system, and also improving the scalability and maintainability of CNC machine tool position monitoring functions.

[0042] Preferably, the paging register includes a page number register for recording the current page number and a line number register for recording the number of lines per page. The refresh logic of the human-machine interface selects the corresponding set of point entries for display based on the values ​​of the page number register and the line number register.

[0043] This paging register refresh logic solution utilizes both the page number register and the row number register to jointly control the selection and display of the point set, achieving the following technical effects:

[0044] First, by recording the current page position through the page number register, the system can quickly locate the required display range in a large amount of point data, so that the page turning operation has a clear index basis, avoiding the efficiency drop caused by relying on sequential traversal search, thus ensuring that the interface still has a good response speed when the number of points is large.

[0045] Second, the row number register setting keeps the number of point entries displayed per page constant, ensuring the uniformity and neatness of pagination display. There is no need to dynamically calculate the number of displays during the interface refresh process, which reduces the complexity of logical processing and keeps the system display stable during continuous operation, preventing layout errors caused by changes in data scale.

[0046] Third, the synergistic effect of the page number register and the row number register makes the interface refresh logic highly regular and predictable. Users can obtain a continuous view of point data by flipping through pages, which ensures the integrity and intuitiveness of the monitoring process and improves the user-friendliness of the interface interaction.

[0047] Fourth, this mechanism also enables the system to have flexible expansion capabilities. When the number of monitoring points increases or the interface parameters are adjusted, the display logic can be changed simply by modifying the register values, without having to modify the overall interface engineering. This improves the adaptability and long-term use value of the monitoring method in different models and application scenarios.

[0048] Preferably, the resource files are also deployed to the standard directory of the CNC machine tool and called uniformly during loading. The resource files include at least one of language files, icon files, configuration files, and interface engineering files.

[0049] This unified deployment solution for resource files centrally stores language files, icon files, configuration files, and interface project files in the standard directory of CNC machine tools and calls them uniformly during loading, achieving the following technical effects:

[0050] First, the use of a standard directory provides a unified storage location for various resource files, avoiding path confusion or file loss caused by decentralized management, and ensuring that the required resources can be accurately called when the interface loads, thereby improving the reliability and consistency of system operation.

[0051] Second, the unified calling method eliminates the need for manual specification or separate configuration in the interface loading process, reducing repetitive operations for engineers during the deployment phase and improving the efficiency of interface launch. In particular, it can significantly shorten debugging time in scenarios where there are frequent changes in device models or projects.

[0052] Third, the centralized resource deployment structure facilitates version management and updates. When resource files need to be modified or replaced, operations can be performed in the standard directory to take effect in all relevant interfaces, avoiding inconsistencies caused by multiple modifications and ensuring the controllability of interface operation and the convenience of long-term maintenance.

[0053] Fourth, this mechanism also facilitates the expansion and portability of the system. When deployed in different machine tools or different HMI (Human-Machine Interface) environments, only the standard directory needs to be copied to complete the migration and loading of all resources without the need for additional adjustments to the interface engineering. This enhances the applicability and promotion value of the monitoring method across platforms and projects.

[0054] As a preferred approach, integrity checks are performed on resource files before deployment, and a rollback mechanism is triggered when file anomalies are detected.

[0055] This integrity verification and rollback mechanism solution performs consistency checks on resource files before deployment and triggers a rollback in case of anomalies, achieving the following technical effects:

[0056] First, integrity verification ensures that resource files are not tampered with or damaged during transmission or copying. File anomalies can be detected before the interface loads, thus preventing erroneous files from entering the system operation process and causing interface display failure or monitoring logic disorder, thereby improving the security and stability of system operation.

[0057] Secondly, the rollback mechanism triggered by anomaly detection enables the system to automatically restore to the previous reliable version when it finds that the resource file does not meet the requirements, ensuring that the interface can still run normally during the loading process, reducing the risk of downtime caused by file errors, and ensuring the continuity of CNC machine tools in the production process.

[0058] Third, the combination of verification and rollback makes the operation and maintenance process predictable and controllable. Engineers do not need to worry about system paralysis caused by operational errors when updating or replacing resource files. This not only improves the fault tolerance of resource management, but also reduces the complexity and risk of maintenance work.

[0059] Fourth, this mechanism forms a closed-loop management process for resource files, which can effectively prevent the accumulation of erroneous files or version chaos during long-term operation and multiple upgrades, ensuring the stability of the file system structure and providing long-term reliable technical support and promotional value for the IO point monitoring method of CNC machine tools.

[0060] Furthermore, the present invention also provides a monitoring system for the status of I / O points of Siemens CNC machine tools, comprising:

[0061] The data processing module is used to export the point information table from the electrical design software, filter out the target points and corresponding point descriptions related to CNC machine tool monitoring, generate initial data, and perform preprocessing and sorting on the initial data to form mapping data;

[0062] The mapping generation module is used to group the mapping data according to a preset grouping rule and generate numbers, construct a grouping array, and write the grouping array to a text file;

[0063] The interface loading module is used to call loading instructions to read text files during the loading process of the human-computer interface, and to bind the grouped array to pages on the human-computer interface;

[0064] The register control module is used to page and refresh the target point and its corresponding point description according to the state of the paging register during operation.

[0065] By adopting the above technical solution, the export, preprocessing, mapping generation, interface loading and register control of point data are sequentially integrated into the same system, realizing the full-link automated processing of point data from electrical design to human-machine interface monitoring. This ensures that the CNC machine tool can efficiently, intuitively and reliably monitor the status of IO points during operation.

[0066] The data processing module ensures that the raw location information is filtered and preprocessed before entering the system, making the data input more accurate and standardized. The mapping generation module establishes a structured relationship between grouping and numbering, enabling large-scale location data to be organized in an orderly manner and written to a parsable external file. The interface loading module reads the text file and completes page binding by calling instructions during the loading stage, realizing dynamic linkage between location information and the interface and improving the flexibility of the interface in different operating scenarios. The register control module manages the page number and line number registers to achieve efficient execution of page turning and refreshing, ensuring the real-time performance and operability of the interface display.

[0067] Preferably, the system also includes a resource deployment module for deploying resource files to the standard directory of the CNC machine tool, performing integrity checks on the resource files before deployment, and triggering a rollback mechanism when file anomalies are detected. The resource files include at least one of language files, icon files, configuration files, and interface engineering files.

[0068] This technical solution achieves the following technical effects by setting a unified resource deployment mechanism in the system and combining it with verification and rollback strategies:

[0069] First, the centralized resource management method ensures that language files, icon files, configuration files, and interface project files remain consistent during deployment. The interface loading process can directly call the contents of the standard directory, avoiding loading failures caused by scattered files or incorrect paths, thereby improving the reliability of the interface operation.

[0070] Second, the integrity check before deployment enables the system to detect anomalies before files enter the runtime environment, ensuring that all files entering the interface are the correct versions, reducing the uncertainty caused by erroneous files. At the same time, the rollback mechanism triggered when an anomaly is detected can quickly restore the system to a usable state, ensuring the continuity and safety of CNC machine tools during operation.

[0071] Third, the introduction of this mechanism simplifies the maintenance process. When updating or expanding resources, engineers only need to operate on the standard catalog to complete the replacement. The system can automatically complete consistency verification and anomaly recovery, reducing manual intervention and repetitive operations, and improving the efficiency of resource updates and the long-term stability of the system.

[0072] The beneficial effects of this invention are that by preprocessing, grouping, numbering, and loading external files into the point information table exported from electrical design software, and combining it with the pagination binding and register control of the human-machine interface, unified management and dynamic display of point data can be achieved. This can significantly improve the efficiency of standardized processing of point data and the flexibility of interface display, and meet the needs of efficient standardized processing of point data and dynamic pagination display and refresh of the human-machine interface during the monitoring of CNC machine tool IO point status.

[0073] Furthermore, the design principle of this invention is reliable, the structure is simple, and it has a very wide range of application prospects.

[0074] Therefore, it is evident that the present invention has outstanding substantive features and significant progress compared with the prior art, and the beneficial effects of its implementation are also obvious. Attached Figure Description

[0075] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0076] Figure 1 This is a flowchart of a method for monitoring the status of I / O points on a Siemens CNC machine tool, provided by the present invention.

[0077] Figure 2 This is a schematic diagram of a monitoring system for the I / O point status of a Siemens CNC machine tool provided by the present invention.

[0078] The module consists of 1. a data processing module, 2. a mapping generation module, 3. an interface loading module, and 4. a register control module. Detailed Implementation

[0079] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. The following embodiments are explanations of the present invention, but the present invention is not limited to the following implementation methods.

[0080] Example 1:

[0081] like Figure 1 As shown in the figure, this embodiment provides a method for monitoring the status of I / O points of a Siemens CNC machine tool, including the following steps:

[0082] Step S1: Export the point information table from the electrical design software, filter out the target points and corresponding point descriptions related to CNC machine tool monitoring, and generate initial data;

[0083] Step S2: Perform preprocessing and sorting on the initial data to generate mapping data. The preprocessing includes at least one of conflict detection, duplicate merging, and missing data completion.

[0084] Step S3: Group the mapping data according to the preset grouping rules and generate numbers to construct a group array;

[0085] Step S4: Write the grouped array to a text file, which is an external file that the CNC machine tool can parse;

[0086] Step S5: During the loading process of the human-machine interface, call the loading instruction to read the text file and perform pagination binding on the human-machine interface;

[0087] Step S6: During operation, the target point and its corresponding point description are displayed and refreshed by flipping pages according to the state of the paging register.

[0088] By adopting the above technical solution, the point information table exported by the electrical design software is preprocessed, grouped, numbered, and externally loaded. Combined with the pagination binding and register control of the human-machine interface, unified management and dynamic display of point data can be achieved. This can significantly improve the efficiency of standardized processing of point data and the flexibility of interface display, and meet the needs of efficient standardized processing of point data and dynamic pagination display and refresh of the human-machine interface during the monitoring of CNC machine tool I / O point status.

[0089] Specifically, by exporting the point information table from electrical design software and filtering out the target points and descriptions related to monitoring, the original complex data is transformed into initial data that can be directly used for monitoring, improving the accuracy and relevance of data preparation. In the preprocessing stage, operations such as conflict detection, duplicate merging, and missing data completion ensure the consistency and integrity of point data before it is entered into the interface, reducing the potential for errors caused by manual maintenance. The mapped data is grouped and numbered to construct a structured group array, ensuring the orderly management of a large number of points in the interface and avoiding disordered calls during interface loading. The group array is written to an external text file that can be parsed by CNC machine tools, and the loading command is called to read the file when the human-machine interface is loaded, so that the binding of point descriptions to the interface no longer depends on fixed programming, but is flexibly configured in an externalized way, improving the efficiency of interface maintenance and updates. During operation, the paging register is used to control the paging display and refresh of points, realizing efficient paging management and real-time dynamic updates of a large number of points in the interface, ensuring the intuitiveness and timeliness of status monitoring.

[0090] Hereinafter, steps S1 to S6 will be specifically described according to embodiments of this application.

[0091] In step S1, exporting the point information table from the electrical design software is the starting point of the technical solution of this application.

[0092] Specifically, in the design and debugging of CNC machine tools, electrical design software is typically used to complete the overall planning and drawing of the machine tool's electrical system. This software can generate a point information table containing all I / O signals. The point information table records information such as the address, symbol, functional description, and module to which the point belongs, often numbering in the hundreds or even thousands, covering various detection and control signals during machine tool operation. For example, in this embodiment, the electrical design software EPLAN is used to generate the point information table and export it completely as an Excel spreadsheet.

[0093] After exporting the point information table, not all points are directly related to machine tool status monitoring. For example, some points are only used for auxiliary logic control or are not signals that need to be displayed on the human-machine interface. If all point data is used directly, it will lead to interface redundancy and information noise, thereby affecting the operator's understanding of key operating states. Therefore, in this embodiment, the point information table needs to be filtered to retain only the target points closely related to CNC machine tool operation monitoring and their corresponding point descriptions. The filtering process is based on preset filtering conditions, such as whether the point belongs to the machine tool's safety protection signal, whether it involves key sensor feedback in the machining process, and whether it is associated with core units such as the spindle, servo axis, and cooling system. Through the above filtering, the point set can be reduced from a massive amount of data to a target set corresponding to monitoring needs.

[0094] After selecting the target locations, it is necessary to map each target location to its corresponding location description to form a standardized data structure, i.e., initial data. The location description is a textual explanation of the location's function and purpose, typically derived from signal annotations set by electrical design engineers during the design phase.

[0095] In other embodiments of this application, the initial data may also include point addresses and necessary attributes related to CNC machine tool monitoring.

[0096] Because descriptions generated by electrical design software may be inconsistent or semantically unclear, this application's implementation establishes a unified data model to ensure consistent processing. This model standardizes the format of location addresses, transforming different writing styles into comparable standard forms under the same rules. For location descriptions, it performs character set unification, full-width / half-width character conversion, case and symbol regularization, and merging of common synonyms to eliminate semantic shifts caused by differences in source, enabling direct use for human-machine interface display and user identification. For example, "X-axis limit switch left" is uniformly labeled as "X-axis left limit," thus avoiding multiple descriptions of the same signal due to different engineers' naming habits.

[0097] Through step S1 above, the original point information table can be transformed into initial data tailored to the monitoring needs of CNC machine tools. This initial data consists of target points and their corresponding point descriptions, laying the data foundation for subsequent preprocessing, mapping, numbering, and human-machine interface loading. This step not only ensures the relevance and accuracy of the input data but also significantly reduces interference from redundant points during subsequent processing, thereby improving the efficiency and stability of the overall monitoring method.

[0098] In step S2, the initial data obtained in step S1 needs to be preprocessed and sorted to form structurally consistent, semantically clear, and easily processed mapping data before entering the mapping stage. During this process, the normalized initial data enters the preprocessing pipeline, which includes at least one of conflict detection, duplicate merging, and missing data completion, and selects the enabled sub-processes according to the engineering configuration to ensure that the mapping data has traceable identifiers and processing marks.

[0099] Specifically, conflict detection sets up valid mapping selection rules and conflict logging mechanisms for scenarios where "the same target point corresponds to multiple point descriptions." To ensure determinism in selection, a hash index can be established using the standard form of the point address as the first key and the target point identifier as the second key. When a new record is inserted, if the index matches and the point description of an existing record is inconsistent with the new description, a conflict determination is triggered. Conflict determination uses a preset priority rule to select a unique valid mapping. The priority can be calculated comprehensively based on dimensions such as the reliability level of the data source, the freshness of the timestamp, the completeness of the description, and the conformity of the terminology. The calculation process remains deterministic to ensure that the same input produces the same output. The selected point description is marked as a "valid mapping," while the remaining point descriptions are not discarded but written to the conflict log.

[0100] Furthermore, the conflict log is output in a structured format, which can include the target location, standardized address, valid description, alternative description, trigger time, rule version, and processing summary, facilitating quality review and auditing. At the same time, fields such as "conflict resolved" and "conflict count" are set on the corresponding records of the mapped data to record the status of the location in this preprocessing.

[0101] This conflict detection technology introduces a preset priority rule during the point mapping stage to select multiple point descriptions for the same target point, and records the unselected point descriptions in the log, achieving the following technical effects:

[0102] First, by limiting the valid mapping through priority rules, a unique valid description can be automatically selected when there are multiple point descriptions, thereby avoiding ambiguity in point data during interface binding, ensuring the consistency and uniqueness of data mapping, and improving the reliability of point information in subsequent processing.

[0103] Second, by fully recording the descriptions of unused locations in the log, a traceability basis for data processing can be formed, enabling the source of conflict to be quickly located during subsequent maintenance or auditing, facilitating manual review and correction by engineers, thereby reducing the risk of abnormal interface display or monitoring distortion caused by location conflicts.

[0104] Third, by automatically completing conflict detection and log recording during the data governance process, the amount of manual comparison and screening can be reduced, the overall automation level of data processing can be improved, the time from point file generation to loading can be shortened, and the system can still have high operating efficiency when the number of points is large.

[0105] Fourth, by combining effective mapping and logging strategies, complete original conflict information can be preserved while ensuring the normal operation of the system. This provides strong support for the management and optimization of point data, ensuring the stability and continuity of point mapping during the long-term operation and multiple upgrades of CNC machine tools.

[0106] The duplicate merging approach addresses scenarios where the same target location and description are included multiple times, employing a two-tiered strategy of content equivalence determination and weak equivalence determination. Specifically, content equivalence is determined by the simultaneous equality of the standardized location address and location description; weak equivalence allows for negligible differences in descriptions (such as spaces, line breaks, punctuation differences, or minor differences specified in the synonym mapping table). When weak equivalence is established, the record with the higher weight is used as the master record, and the remaining records are merged. The occurrence frequency and source list are accumulated to form a "merging genealogy" field for tracking. During merging, the unique identifier and data quality marker of the master record are retained, and redundant entries are deleted to avoid many-to-one mapping ambiguity during the mapping stage. Furthermore, to prevent erroneous merging, this implementation performs consistency checks on the unit to which the location belongs, signal direction, and electrical level before merging. If the check fails, merging is not performed, and the process proceeds to the conflict detection path.

[0107] Missing data filling is used to maintain the continuity of the data structure when there are gaps in the address sequence. Specifically, to determine whether there are gaps in the "continuous group", a continuity detector can be established according to the natural order of the point addresses (such as the input area and the output area respectively by byte / word and bit index). The detector calculates the sequence increment for the standardized address. When the increment exceeds the set step size and is within the address domain of the same continuous group, it is determined that there is a gap. A placeholder entry is generated at the gap position. The entry carries a placeholder flag, the corresponding address range, the identifier of the continuous group to which it belongs, and a status description such as "unused / to be configured" to ensure that the subsequent data structure is not shifted when it is read and indexed.

[0108] Meanwhile, once a placeholder entry is generated, it is recorded in the missing data log. The log fields can include continuous group identifier, gap start and end, generation time, detection basis, and responsibility domain marker, which facilitates subsequent point filling and engineering closure. At the same time, a persistent field is reserved for this position in the mapping data model, so that the placeholder can participate in sorting, pagination calculation, and subsequent binding as a regular record without affecting the validity determination of the actual point. To avoid redundancy caused by over-filling, upper limits can also be set for the detection range and the maximum filling span. When the gap crosses the domain or exceeds the limit, it is marked as a "structural void", and only the log is recorded without generating a placeholder.

[0109] This missing data completion technology maintains group continuity by using placeholders when point data is incomplete, and retains missing information through a dual recording mechanism, achieving the following technical effects:

[0110] First, the introduction of placeholder entries ensures the continuity and integrity of the grouping structure, keeps the data in a fixed order and format during loading and calling, avoids data misalignment and interface display chaos caused by gaps, and ensures the stability of system operation and the consistency of interface refresh.

[0111] Secondly, the logging function clearly presents the missing information, allowing engineers to quickly identify the location and quantity of specific missing points during maintenance. This ensures traceability and manageability, reduces the time and effort required for manual comparison, and improves the efficiency of subsequent adjustments and optimizations.

[0112] Third, the missing markers retained in the text file ensure the standardization of the data file format. Even if the points have not been configured, the interface can still parse and load the data according to the unified data structure, thereby avoiding operational abnormalities caused by inconsistent file formats and enhancing the system's fault tolerance for incomplete data.

[0113] Fourth, this supplementation mechanism allows the system to expand the number of points or make engineering changes without reconstructing the overall group array. It only needs to add actual points within the existing framework, which improves the scalability of the system, reduces the workload of repeated development and maintenance, and ensures the continuity and reliability of CNC machine tools in long-term operation.

[0114] After preprocessing, further sorting is required to ensure stable consistency and reusability of the points when entering the mapping stage. Sorting is used to output a deterministic order of mapping data, keeping the arrangement of points unchanged under the same input conditions, thus providing a reliable data foundation for subsequent grouping and numbering.

[0115] In this embodiment, a stable sorting method is used. The primary key is the address field (e.g., ascending order of byte / word index values), the secondary key is the signal direction (input takes precedence over output or is set according to engineering configuration), the third key is the bit index, and the fourth key is the natural order identifier of the target point. When the above keys are the same, they are stably scattered according to data quality scores and timestamps to ensure that the main records with the same address and description take precedence. The sorting results are written back to the "sort key" and "continuous grouping key" of the mapped data to ensure that the arrangement of the mapped data is always consistent under the same input conditions.

[0116] For example, in the embodiments of this application, the above preprocessing and sorting operations can be implemented by a Python program, thereby providing cross-platform portability and ease of development and maintenance, and enabling rapid deployment and reuse in machine tool debugging and operation environments. Specifically, the pandas library is used to read and convert the point information table exported by the electrical design software into a data frame. DataFrame objects are used to filter and index the data, and a dictionary and set structure are used to maintain the correspondence between point addresses and descriptions. Simultaneously, the program calls a sorting function during operation to generate stable sequence results, and a log module automatically outputs processing status and exception information. Finally, the processed data is written to a specified path in the form of a standardized text file or table file, providing a unified input for subsequent grouping and numbering.

[0117] Thus far, step S2, without relying on the interface and loading details, has completed the consistency resolution of initial data conflict traces, redundancy removal, and maintenance of structural continuity, and provides a data order that can directly enter the mapping stage, providing a stable, auditable, and scalable mapping data foundation for subsequent processing.

[0118] In step S3, the mapping data obtained in step S2 needs to be grouped according to a preset grouping rule. This organizes a large amount of point data into logical units that are easy to index and retrieve. Then, numbers are generated based on these groups to construct a grouped array that can be used subsequently. For example, in this embodiment, a grouping rule of 16 points per group is used. This grouping size is consistent with the data access characteristics of the CNC system, ensuring that page turning or positioning is performed in fixed steps during subsequent human-machine interface calls, thereby improving operating efficiency.

[0119] Specifically, the point entries are first read sequentially according to the order of the mapped data and filled into the grouped array. When the number of entries in a group reaches 16, the system automatically switches to the next group and continues to fill in subsequent point entries. If a gap appears in a group due to missing points, a placeholder entry is written at that position to maintain the continuity of the entire grouped array. In this way, the final grouped array always maintains a uniform size and regular arrangement in structure, and will not be disordered due to missing points.

[0120] After grouping, the points need to be numbered so that they can be called with a unified logical index, rather than directly depending on the underlying physical address.

[0121] In some embodiments of this application, the numbering intervals can be set in two different ranges: one array map_1 is numbered sequentially starting from 88000, and the other array map_2 is numbered sequentially starting from 88200. The numbering process strictly follows the order of the points in the grouping arrays. For each point entry, the corresponding number is calculated based on its array and grouping position, ensuring the stability of the numbering results under the same input conditions.

[0122] Furthermore, in addition to generating numbers, a "address-number" correspondence can be established in the mapping data so that the corresponding original point information can be quickly retrieved through the number in subsequent operations, realizing forward and reverse mapping of data.

[0123] This numbering generation technology solution establishes numbering intervals during point data processing and assigns numbers sequentially, achieving the following technical effects:

[0124] First, the setting of numbering intervals ensures that different types of points have clear logical boundaries, enabling the system to quickly identify the category and process accordingly when the interface is called, avoiding conflicts and ambiguities caused by mixing the same numbering space, and improving the standardization and consistency of point management.

[0125] Secondly, the sequential allocation method ensures that the numbers and locations correspond in physical arrangement, which facilitates quick location and indexing when the interface is displayed in pages, reduces additional query overhead, improves the efficiency of the locations on the interface, and also makes it easier for users to understand and use.

[0126] Third, the numbering mechanism that combines intervalization and sequentialization makes the point mapping relationship more intuitive. During subsequent maintenance and expansion, points can be smoothly added or adjusted according to established rules, avoiding large-scale modification work caused by numbering chaos and reducing the risks and complexity in project implementation.

[0127] Fourth, this numbering strategy also provides room for system scalability. Different numbering intervals are kept isolated, and numbering segments can be reserved for future additions of point categories or functions, thereby ensuring that the entire monitoring system maintains an orderly numbering system and stable data management capabilities during long-term operation and continuous upgrades.

[0128] In step S4, the grouped array generated in step S3 needs to be written to a text file, thereby persistently storing the grouped array in a normalized form so that it can be directly called during the loading phase without recalculation or parsing. At the same time, the text file must meet the requirements of the CNC machine tool parser so that it can be correctly read and used during system operation.

[0129] Specifically, a target text file named oem_chs.txt is first created and stored in a pre-defined directory of the CNC machine tool to ensure that the machine tool system can automatically retrieve and identify the data during the loading phase. The file is written line by line, with each line containing a point entry number and a point description. The number serves as the key, and the point description serves as the corresponding value. These key-value pairs are written line by line. This organization allows the parser to quickly locate the number and call the corresponding function description, ensuring that the point information is matched with minimal complexity during the interface loading process.

[0130] During file writing, the order of the grouped arrays is strictly adhered to. The map_1 and map_2 arrays are read sequentially. For placeholder entries generated due to missing data, their numbers and descriptions are also written to the file to ensure that the number of lines matches the group width. The numbering follows a fixed interval: entries in map_1 start from 88000 and increment sequentially, while entries in map_2 start from 88200 and increment sequentially. In this way, the file logically corresponds one-to-one with the arrays, ensuring no misalignment or omissions occur during parsing and pagination, guaranteeing the independence of different arrays, avoiding conflicts, and allowing the parser to directly determine the source category of an entry through the numbering interval.

[0131] Furthermore, to ensure the correctness and stability of the file, a two-stage strategy can be adopted in some other embodiments of this application during the writing process. First, the grouped array is written to a temporary file, and an integrity check is performed after writing is complete. The check includes: whether the number of lines in the file matches the number of array entries, whether the numbers are strictly incrementing and fall within a preset range, whether the character encoding matches system requirements, and whether key delimiters appear correctly. If the check passes, the temporary file replaces the old file as the new oem_chs.txt; if the check fails, the temporary file is deleted while the old file remains unchanged, and an error log is recorded. This strategy effectively avoids file corruption caused by writing interruptions or anomalies, thus ensuring that the CNC machine tool can still obtain a valid configuration file upon the next load.

[0132] For example, this can be accomplished using a Python program. The program first reads the two arrays map_1 and map_2 output in step S3, and generates text lines line by line according to the array order. Before writing each record, the original physical address is replaced with a logical number, and the point description is escaped and encoded to meet the format requirements of the CNC system parser. The Python program uses a file stream interface to write data line by line, ensuring that memory usage remains stable, and records the writing progress and exceptions using a log module. After writing is complete, the program also generates a verification digest, which is saved together with the log as a basis for subsequent debugging and maintenance.

[0133] Through steps S3 and S4, the final generated oem_chs.txt file contains a clearly structured and fixed-order list of all target point numbers and descriptions, which can be directly recognized and loaded by the Siemens CNC system. This step transforms the point data from a logical array into an external file, forming a resolvable persistent medium, providing a stable data foundation for subsequent HMI loading and register control.

[0134] In step S5, during the loading process of the human-machine interface, a loading instruction needs to be called to read the text file generated in step S4, and the group array in it needs to be paginated and bound on the interface. This step is the key link for the point information to enter the actual monitoring interface, ensuring that the point status can be accurately displayed when the CNC machine tool is running.

[0135] Specifically, during the initialization phase of the human-machine interface, the CNC machine tool calls the loading instruction to read a text file from the machine tool's standard directory, uses this file as a data source to introduce into the interface environment, reads each line of the file in sequence, parses the number field and point description in the file, and writes it into a cache structure that the interface can recognize, so that the data can be directly called in the subsequent pagination binding logic.

[0136] After the file content is successfully loaded into the cache structure, a pagination binding relationship needs to be established. The rules for pagination binding are consistent with the grouping rules of arrays. Each page corresponds to a fixed group width, typically 16 items. The data sets of each group are sequentially mapped to the pagination areas of the interface through page number order, forming a one-to-one index relationship between the cache structure and the interface display. In this way, when the interface is invoked, the point data can be directly presented on the corresponding page according to the group order. Users can view the points and their descriptions page by page in the interface, ensuring a stable correspondence between the data structure and the interface display.

[0137] In other embodiments of this application, to ensure the security of the data loading process, necessary checks are performed when reading the file, including checking whether the file exists, whether the file format meets expectations, and whether the file can be parsed normally. If a file is detected to be missing, corrupted, or incompatible, the interface will immediately stop the loading process and record the error information, thereby avoiding data anomalies caused by erroneous files and ensuring that the interface display is always based on the correct data source.

[0138] In some embodiments of this application, the lifecycle function plays a crucial role in the entire loading and paging process, serving as the control logic automatically executed by the human-computer interface during critical stages such as loading and exiting. When the interface enters the loading stage, the lifecycle function is triggered, automatically performing file reading and memory writing operations. After being loaded, the array resides in memory, forming a runtime data cache. The content in the cache remains completely consistent with the file, the order of entries does not change, and the correspondence between numbers and descriptions remains stable, serving as the primary data source during interface operation. When the interface exits, the lifecycle function is triggered again, automatically releasing the cache, clearing the occupied memory resources, and cleaning up the array and index table in the cache.

[0139] This technical solution for loading and releasing lifecycle functions establishes a unified data management mechanism during interface startup and exit, achieving the following technical effects:

[0140] First, during the interface loading process, the external text file is read directly by calling the lifecycle function and the grouped array is written into memory. This ensures that the point data can be loaded completely and accurately during interface initialization, avoiding the uncertainty caused by relying on manual import or script execution, thereby improving the stability and controllability of the system operation.

[0141] Secondly, by releasing the grouped array using lifecycle functions after the operation ends, memory resources can be cleaned up in a timely manner when exiting the interface, preventing excessive memory usage or resource conflicts caused by data residue. This allows the system to maintain good performance during long-term continuous operation and improves the overall resource management capability.

[0142] Third, the mechanism forms an automated closed-loop process in the interface loading and exit stages, so that there are clear control nodes in the entire process of loading, using and releasing point data, reducing the links of manual intervention and improving the standardization of interface engineering and the predictability of the operation process.

[0143] Fourth, during maintenance and upgrades, the introduction of lifecycle functions enables the system to quickly identify loading and releasing time points, facilitating developers to add targeted logging, anomaly detection, or rollback strategies, providing further assurance for the reliable operation of the system, and also improving the scalability and maintainability of CNC machine tool position monitoring functions.

[0144] In some embodiments of this application, resource files required for operation can be loaded simultaneously with the loading of the human-machine interface. These resource files are auxiliary files on which the interface operation depends, including at least one of language files, icon files, configuration files, and interface project files. These files are centrally deployed in the standard directory of the machine tool operating system. The interface loader can then scan the directory sequentially during the startup phase and call the resource files related to the interface display, so that the interface has complete display content and functional configuration during runtime. At the same time, since all resource files are centrally stored in a fixed directory, the loader does not need to specify the path one by one, but can complete the call in a unified way, thereby reducing the configuration workload and the probability of errors.

[0145] This unified deployment solution for resource files centrally stores language files, icon files, configuration files, and interface project files in the standard directory of CNC machine tools and calls them uniformly during loading, achieving the following technical effects:

[0146] First, the use of a standard directory provides a unified storage location for various resource files, avoiding path confusion or file loss caused by decentralized management, and ensuring that the required resources can be accurately called when the interface loads, thereby improving the reliability and consistency of system operation.

[0147] Second, the unified calling method eliminates the need for manual specification or separate configuration in the interface loading process, reducing repetitive operations for engineers during the deployment phase and improving the efficiency of interface launch. In particular, it can significantly shorten debugging time in scenarios where there are frequent changes in device models or projects.

[0148] Third, the centralized resource deployment structure facilitates version management and updates. When resource files need to be modified or replaced, operations can be performed in the standard directory to take effect in all relevant interfaces, avoiding inconsistencies caused by multiple modifications and ensuring the controllability of interface operation and the convenience of long-term maintenance.

[0149] Fourth, this mechanism also facilitates the expansion and portability of the system. When deployed in different machine tools or different HMI environments, only the standard directory needs to be copied to complete the migration and loading of all resources without the need for additional adjustments to the interface engineering, thereby enhancing the applicability and promotion value of the monitoring method across platforms and projects.

[0150] Furthermore, to ensure that the loaded resource files are correct and valid, integrity checks are performed during the deployment phase. When scanning files, the system calculates the file's checksum or hash value and compares it with the checksum information of the original version. Only when the comparison results match will the file enter the loading process. If file anomalies are detected, such as missing, corrupted, or tampered files, the system immediately stops loading and triggers a rollback mechanism to restore to the previous verified file version, ensuring that there are still valid files available when the interface loads.

[0151] This integrity verification and rollback mechanism solution performs consistency checks on resource files before deployment and triggers a rollback in case of anomalies, achieving the following technical effects:

[0152] First, integrity verification ensures that resource files are not tampered with or damaged during transmission or copying. File anomalies can be detected before the interface loads, thus preventing erroneous files from entering the system operation process and causing interface display failure or monitoring logic disorder, thereby improving the security and stability of system operation.

[0153] Secondly, the rollback mechanism triggered by anomaly detection enables the system to automatically restore to the previous reliable version when it finds that the resource file does not meet the requirements, ensuring that the interface can still run normally during the loading process, reducing the risk of downtime caused by file errors, and ensuring the continuity of CNC machine tools in the production process.

[0154] Third, the combination of verification and rollback makes the operation and maintenance process predictable and controllable. Engineers do not need to worry about system paralysis caused by operational errors when updating or replacing resource files. This not only improves the fault tolerance of resource management, but also reduces the complexity and risk of maintenance work.

[0155] Fourth, this mechanism forms a closed-loop management process for resource files, which can effectively prevent the accumulation of erroneous files or version chaos during long-term operation and multiple upgrades, ensuring the stability of the file system structure and providing long-term reliable technical support and promotional value for the IO point monitoring method of CNC machine tools.

[0156] For example, in the embodiments of this application, the loading and pagination binding of text files, and the calling and verification of resource files, are a continuous whole during the interface loading process, and can all be automatically completed by programs such as Python. When the interface starts, the program first calls a lifecycle function to detect and load the text file, writing the grouped array into memory; then, it establishes a pagination index according to the grouping and numbering order, enabling the interface to quickly locate data using the page number as a parameter; after completing the loading of the point array, the program enters the resource file deployment process, scanning various resource files in the standard directory and performing integrity checks on each file. Files that pass the check are written into the runtime environment and uniformly called during the loading phase; files that fail the check trigger a rollback, restoring to the previous stable version. The entire process forms a closed-loop logic, with verification and protection measures in place from data loading to resource calling, ensuring the stability of the interface operation.

[0157] Finally, the interface enters a stable operating state, allowing users to intuitively view the position status on the paginated interface. The entire process requires no manual intervention and is completed automatically by the loading program and lifecycle functions, ensuring the consistency and reliability of the CNC machine tool's performance across different operating cycles.

[0158] Thus, step S5 completes the loading process from external files to interface pagination. Combined with lifecycle functions, resource file deployment, and integrity verification mechanisms, it can present point information in a structured and stable manner during runtime, ensuring not only the standardization of data loading but also the consistency and security of resources during interface operation.

[0159] In step S6, the human-machine interface of the CNC machine tool is in operation. At this time, the display and update of the control point information can be controlled according to the value of the paging register. The paging register is a key control variable in the operation of the interface. It is responsible for recording the range of the display page and the number of items. It contains two core fields: the page number register and the line number register, which are used to record the page number displayed on the current interface and the number of items to be displayed on each page, respectively. Together, they determine the data set displayed on the current interface.

[0160] This paging register refresh logic solution utilizes both the page number register and the row number register to jointly control the selection and display of the point set, achieving the following technical effects:

[0161] First, by recording the current page position through the page number register, the system can quickly locate the required display range in a large amount of point data, so that the page turning operation has a clear index basis, avoiding the efficiency drop caused by relying on sequential traversal search, thus ensuring that the interface still has a good response speed when the number of points is large.

[0162] Second, the row number register setting keeps the number of point entries displayed per page constant, ensuring the uniformity and neatness of pagination display. There is no need to dynamically calculate the number of displays during the interface refresh process, which reduces the complexity of logical processing and keeps the system display stable during continuous operation, preventing layout errors caused by changes in data scale.

[0163] Third, the synergistic effect of the page number register and the row number register makes the interface refresh logic highly regular and predictable. Users can obtain a continuous view of point data by flipping through pages, which ensures the integrity and intuitiveness of the monitoring process and improves the user-friendliness of the interface interaction.

[0164] Fourth, this mechanism also enables the system to have flexible expansion capabilities. When the number of monitoring points increases or the interface parameters are adjusted, the display logic can be changed simply by modifying the register values, without having to modify the overall interface engineering. This improves the adaptability and long-term use value of the monitoring method in different models and application scenarios.

[0165] Specifically, when a user flips through pages on the interface, the CNC machine tool immediately updates the page number register. Once the control logic detects the change in the register value, it immediately calculates the range of entries corresponding to that page. For example, the calculation method can be: the starting entry number equals (page number register value - 1) multiplied by the line number register value, and the ending entry number equals the starting entry number + the line number register value - 1. This quickly locates the set of points required for the current page. Simultaneously, during this process, the interface does not need to parse the external text file again; instead, it directly searches the already loaded grouped array in memory, allowing the page-flipping action to take effect instantly.

[0166] Furthermore, the refresh logic is automatically triggered every time the register state changes. Based on the calculated set of entries, the corresponding target points and point descriptions are loaded into the interface display area, replacing the display content of the previous page. The refresh operation can be performed in a whole-page replacement manner at the rendering level to avoid the delay caused by updating item by item. At the same time, since the group array in memory has been established and kept intact in step S5, the refresh logic only involves the switching between data index and interface rendering, and will not trigger structural adjustments or additional calculations.

[0167] In some embodiments of this application, to ensure display stability and consistency, the refresh logic also includes boundary checks. When the page number register is less than 1 or greater than the maximum page number, the CNC machine tool automatically corrects it to a value within the valid range to prevent user error from causing display abnormalities. When the row number register is modified, the interface recalculates the paging index to ensure that the new display row number correctly corresponds to the array entry. This mechanism ensures that the system maintains correct display effects under different paging parameters.

[0168] In practical applications, the paging register enables CNC machine tools to monitor a large number of points without being limited by the interface size. Users can switch between different pages simply by adjusting the value of the page number register, while the row number register allows users to adjust the number of items displayed per page as needed, thus freely switching between "overview mode" and "detail mode". Throughout the entire operation, the page turning and refresh logic remains responsive in real time, ensuring intuitiveness and convenience for operators during machine tool monitoring.

[0169] In some embodiments of this application, fault analysis can also be performed by combining logical conditions during the monitoring process. When an abnormal situation is detected, alarm information is automatically output and corresponding diagnostic data is provided, thereby enhancing the intelligence level of the overall monitoring process and improving the response capability to sudden faults.

[0170] By executing step S6, the human-machine interface of the CNC machine tool can dynamically switch the point display page in the running state and refresh it in real time under the control of the register, ensuring the complete presentation of monitoring information and the consistency of the operating experience.

[0171] In some embodiments of this application, steps S1 to S6 can be automatically completed by a computer program, such as a Python script, in an integrated process. During operation, the program sequentially completes functions such as data processing, mapping generation, file writing, interface loading, and register control, thereby ensuring that the point data monitoring process is executed continuously and stably in the CNC machine tool environment.

[0172] Furthermore, by combining automated scripts with modular programming, the processing and deployment of location information can be fully automated. Users do not need complex programming experience, nor do they need to modify any configuration files or interface files to update the location monitoring function. Compared with traditional methods that rely on manual configuration, this approach can significantly shorten development and deployment time. In practical applications, operations that take hours can be compressed into minutes, thus significantly improving development efficiency. At the same time, this approach lowers the professional threshold for function implementation, allowing non-professionals to quickly complete the configuration and deployment of location monitoring functions. In scenarios with a large number of locations or complex equipment structures, it demonstrates more prominent efficiency advantages and applicability, ensuring the efficient implementation and application of location monitoring functions in engineering practice.

[0173] In summary, this method sequentially completes the steps of point information extraction, preprocessing, grouping and numbering, file generation, interface loading, and register control, realizing a complete monitoring process for the I / O point status of CNC machine tools. Combined with the unified deployment and integrity verification mechanism of resource files, the entire method maintains stability and consistency in data processing, interface display, and file management, meeting the needs of CNC machine tools for efficient monitoring of I / O point status and efficient implementation of dynamic pagination display and refresh of human-machine interface in multiple scenarios.

[0174] It should be noted that, although the embodiments in this application are based on... Figure 1 Steps S1 to S6 are described sequentially, but this does not mean that steps S1 to S6 must be performed in a strict order. The reason this embodiment follows this order is... Figure 1 The order in which steps S1 to S6 are described is provided to facilitate understanding of the technical solutions of the embodiments of this application by those skilled in the art. In other words, in the embodiments of this application, the order of steps S1 to S6 can be appropriately adjusted according to actual needs.

[0175] Example 2:

[0176] like Figure 2 As shown in the figure, this embodiment provides a monitoring system for the status of I / O points of a Siemens CNC machine tool, including:

[0177] Data processing module 1 is used to export a point information table from electrical design software, filter out target points and corresponding point descriptions related to CNC machine tool monitoring, generate initial data, and perform preprocessing and sorting on the initial data to form mapping data;

[0178] Mapping generation module 2 is used to group the mapping data according to a preset grouping rule and generate numbers, construct a grouping array, and write the grouping array to a text file;

[0179] Interface loading module 3 is used to call loading instructions to read text files during the loading process of the human-machine interface, and to bind the grouped array to pages on the human-machine interface;

[0180] Register control module 4 is used to page and refresh the target point and its corresponding point description according to the state of the paging register during operation.

[0181] By adopting the above technical solution, the export, preprocessing, mapping generation, interface loading and register control of point data are sequentially integrated into the same system, realizing the full-link automated processing of point data from electrical design to human-machine interface monitoring. This ensures that the CNC machine tool can efficiently, intuitively and reliably monitor the status of IO points during operation.

[0182] Specifically, data processing module 1 ensures that the raw location information can be filtered and preprocessed before entering the system, making the data input more accurate and standardized; mapping generation module 2 establishes a structured relationship between grouping and numbering, enabling large-scale location data to be organized in an orderly manner and written to a parsable external file; interface loading module 3 realizes dynamic linkage between location information and interface by calling instructions to read text files and complete page binding during the loading stage, improving the flexibility of the interface in different operating scenarios; register control module 4 realizes efficient execution of page turning and refreshing through register management of page number and line number, ensuring the real-time performance and operability of the interface display.

[0183] In some embodiments of this application, the system further includes a resource deployment module for deploying resource files to the standard directory of the CNC machine tool, performing integrity verification on the resource files before deployment, and triggering a rollback mechanism when file abnormalities are detected. The resource files include at least one of language files, icon files, configuration files, and interface engineering files.

[0184] This technical solution achieves the following technical effects by setting a unified resource deployment mechanism in the system and combining it with verification and rollback strategies:

[0185] First, the centralized resource management method ensures that language files, icon files, configuration files, and interface project files remain consistent during deployment. The interface loading process can directly call the contents of the standard directory, avoiding loading failures caused by scattered files or incorrect paths, thereby improving the reliability of the interface operation.

[0186] Second, the integrity check before deployment enables the system to detect anomalies before files enter the runtime environment, ensuring that all files entering the interface are the correct versions, reducing the uncertainty caused by erroneous files. At the same time, the rollback mechanism triggered when an anomaly is detected can quickly restore the system to a usable state, ensuring the continuity and safety of CNC machine tools during operation.

[0187] Third, the introduction of this mechanism simplifies the maintenance process. When updating or expanding resources, engineers only need to operate on the standard catalog to complete the replacement. The system can automatically complete consistency verification and anomaly recovery, reducing manual intervention and repetitive operations, and improving the efficiency of resource updates and the long-term stability of the system.

[0188] Furthermore, this system incorporates a modular decoupling mechanism in its design, enabling the point-of-care monitoring function to adapt to different CNC machine tool models. Under this mechanism, the interface files, icon files, and configuration files remain unchanged; only the external point-of-care monitoring files need to be updated to complete the adaptation. Resource files are organized into independent directories according to their functions. Language files are used to store point descriptions and text information, icon files are used to store symbols required for status display, configuration files are used to set the interface layout and language environment, and interface project files are used to define the overall structure and elements of the interface. Point-of-care monitoring files are uniformly stored in the language file directory, ensuring that the interface remains consistent with external point-of-care data during loading.

[0189] In actual deployment, the system can be combined with automated scripts such as Python scripts to uniformly install the above resource files into the standard directory of the machine tool operating system. After the script runs, it will automatically complete the copying of files and the establishment of the directory structure, reducing manual intervention. The interface has a hot reloading function. When the point monitoring file or configuration file is updated, the interface can automatically detect and reload the content. Users can see the update results directly on the interface without restarting the equipment, which significantly improves the flexibility and operation and maintenance efficiency of the system in actual application.

[0190] Furthermore, this system can link and run its various modules together under the control of software programs such as Python scripts, forming a complete integrated execution process that can achieve the acquisition, processing, display, and monitoring of location data without manual intervention.

[0191] In summary, this system, through the organic integration of data processing module 1, mapping generation module 2, interface loading module 3, and register control module 4, achieves full-process management of point data during acquisition, processing, storage, loading, and operational monitoring. It not only ensures that raw point information is accurately screened and standardized before entering the monitoring stage, but also enables large-scale data to be structured and stored through grouping and numbering mapping relationships, and automatically binds it to the display logic during interface loading. During operation, the paging register control ensures efficient execution of point status page turning and refreshing, thereby achieving real-time, intuitive, and stable monitoring. The resource deployment module further enhances the system's integrity and reliability, enabling stable application in various CNC machine tool environments.

[0192] The above-disclosed embodiments are merely preferred embodiments of the present invention, but the present invention is not limited thereto. Any non-creative variations that can be conceived by those skilled in the art, as well as any improvements and modifications made without departing from the principles of the present invention, should fall within the protection scope of the present invention.

Claims

1. A method for monitoring the status of I / O points on a Siemens CNC machine tool, characterized in that, Includes the following steps: Export the point information table from the electrical design software, filter out the target points and corresponding point descriptions related to CNC machine tool monitoring, and generate initial data; The initial data is preprocessed and sorted to generate mapping data. The preprocessing includes at least one of conflict detection, duplicate merging, and missing data completion. The mapping data is grouped according to a preset grouping rule and numbered to construct a grouping array, including: setting numbering intervals for the target points and the corresponding point descriptions, and assigning numbers according to the order of the target points within the same numbering interval; Write the grouped array into a text file, where the text file is an external file that the CNC machine tool can parse; During the loading process of the human-computer interface, a loading instruction is invoked to read the text file, and pagination binding is performed on the human-computer interface; During operation, the target point and its corresponding point description are displayed and refreshed by paging based on the state of the paging register. The conflict detection includes: when the same target location corresponds to multiple location descriptions, selecting one location description as a valid mapping based on a preset priority rule, and recording the other location descriptions in a conflict log; The repeated merging includes: when the same target location and the same location description are included multiple times, a two-level strategy of content equivalence judgment and weak equivalence judgment is adopted. Content equivalence is judged by the fact that the standardized location address and the location description are equal at the same time. Weak equivalence allows negligible differences in the description. When weak equivalence is established, the record with higher weight is used as the main record, and the remaining records are merged in. The occurrence frequency and source list are accumulated. Negligible differences include differences in spaces, line breaks or punctuation. The missing completion includes: when the target point is missing in a continuous group, generating a placeholder entry at the corresponding position and recording the placeholder entry in the missing log and the text file; The pagination binding includes: after the content of the text file is successfully loaded into the cache structure, establishing a pagination binding relationship rule consistent with the grouping rule of the array, assigning each page to a fixed group width, and sequentially mapping the data sets of each group to the pagination area of ​​the interface according to the page number order, and forming an index relationship in the cache structure that corresponds one-to-one with the interface display. The paging register includes a page number register for recording the current page number and a line number register for recording the number of lines per page. The refresh logic of the human-machine interface selects the corresponding set of point entries for display based on the values ​​of the page number register and the line number register.

2. The method for monitoring the I / O point status of a Siemens CNC machine tool as described in claim 1, characterized in that, During the loading process of the human-machine interface, a lifecycle function is called to read the text file and load the group array into memory. When the human-machine interface exits, the lifecycle function is called to release the group array.

3. The method for monitoring the status of I / O points of a Siemens CNC machine tool as described in claim 1, characterized in that, It also includes deploying resource files to the standard directory of the CNC machine tool and calling them uniformly during loading. The resource files include at least one of language files, icon files, configuration files, and interface engineering files.

4. The method for monitoring the status of I / O points of a Siemens CNC machine tool as described in claim 3, characterized in that, Before deployment, the resource files are subjected to integrity verification, and a rollback mechanism is triggered when file anomalies are detected.

5. A monitoring system for the I / O point status of a Siemens CNC machine tool, used to implement the monitoring method for the I / O point status of a Siemens CNC machine tool as described in any one of claims 1 to 4, characterized in that, The system includes: The data processing module is used to export a point information table from the electrical design software, filter out the target points and corresponding point descriptions related to CNC machine tool monitoring, generate initial data, and perform preprocessing and sorting on the initial data to form mapping data; The mapping generation module is used to group the mapping data according to a preset grouping rule and generate numbers, construct a grouping array, and write the grouping array into a text file; The interface loading module is used to call the loading instruction to read the text file during the loading process of the human-computer interface, and to bind the grouped array to pages on the human-computer interface; The register control module is used to page and refresh the target point and its corresponding point description according to the state of the paging register during operation.

6. The monitoring system for the I / O point status of a Siemens CNC machine tool as described in claim 5, characterized in that, It also includes a resource deployment module, which is used to deploy resource files to the standard directory of the CNC machine tool, and perform integrity verification on the resource files before deployment, and trigger a rollback mechanism when file abnormality is detected. The resource files include at least one of language files, icon files, configuration files and interface engineering files.

Images