DCS man-machine picture conversion method and system, electronic equipment and medium

Abstract

The embodiment of the invention provides a DCS man-machine picture conversion method and system, electronic equipment and a medium, and the method comprises the steps: firstly, responding to a conversion request, locking a target DCS system and a required target picture conversion parameter, and then carrying out the locking of the target picture conversion parameter based on a preset general mapping relation and a unique preset extension mapping relation of the target system, and converting the parameters into an intermediate execution file compatible with the target system. Wherein the problem of cross-system common compatibility is solved through general mapping, and it is ensured that icon layout parameters do not fail due to system differences; extended mapping gives consideration to uniqueness of a target system, so that personalized functions of icons are accurately converted. The generated intermediate file can be directly driven to generate a corresponding picture after being imported into a target system, and a design process does not need to be repeated. Therefore, only one conversion request is needed, and the target system and the expansion mapping relation are adjusted, so that the same set of picture requirements can adapt to different systems, the phenomenon that pictures with the same function are redrawn for each system is avoided, and mutual conversion of man-machine pictures among different DCS systems is effectively realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of nuclear power, and in particular to a DCS man-machine picture conversion method and system, an electronic device and a medium. BACKGROUND

[0002] In the technical field of nuclear power, a DCS (Distributed Control System) is a comprehensive automation control system that integrates computer technology, control technology, communication technology and graphic display technology. The DCS system converts the real-time states of different devices such as different units, reactors, pipelines and valves in a nuclear power plant into a unified DCS man-machine picture through a man-machine interface, aiming to present the working states of different devices to users in a visual form. At the same time, users can adjust the working states of different devices in the DCS man-machine picture through the man-machine interface, thereby realizing dynamic control of each device in the nuclear power plant.

[0003] However, in actual application scenarios, different nuclear power projects correspond to different DCS systems. When there are nuclear power projects with the same reactor type, multiple units but different DCS systems, the DCS man-machine pictures presented to users by different DCS systems are incompatible with each other, so it is necessary to redraw the DCS man-machine pictures with the same function according to the specific icon specifications, file formats, attribute definitions and other rules in different DCS systems, resulting in repetitive DCS man-machine picture design processes for project personnel, and the DCS man-machine pictures for the same component or reactor type cannot be converted between different DCS systems. SUMMARY

[0004] In order to realize the conversion of DCS man-machine pictures between different DCS systems, the embodiments of the present application provide a DCS man-machine picture conversion method, system, electronic device and medium.

[0005] The embodiments of the present application disclose the following technical solutions: In a first aspect, the embodiments of the present application provide a DCS man-machine picture conversion method, which comprises: In response to a DCS picture conversion request, determining a target DCS system and target picture conversion parameters according to the DCS picture conversion request; generate an intermediate execution file compatible with the target DCS system according to the preset general mapping relationship, the preset extended mapping relationship corresponding to the target DCS system alone, and the target picture conversion parameter; the preset general mapping relationship is used to represent a one-to-one mapping relationship between different types of layout parameters in the target picture conversion parameter and different types of icon layout parameters in the target DCS system; and the preset extended mapping relationship is used to represent a one-to-one mapping relationship between different types of function parameters in the target picture conversion parameter and different types of icon function parameters in the target DCS system; import the intermediate execution file into the target DCS system, so as to drive the target DCS system to generate a DCS man-machine picture corresponding to the DCS picture conversion request.

[0006] In a possible implementation, the target picture conversion parameter includes: general icon parameters and custom extended parameters; the general icon parameters are used to represent layout attributes of icons in the DCS man-machine picture; and the custom extended parameters are used to represent custom function attributes of icons in the DCS man-machine picture. The generating, according to the preset general mapping relationship, the preset extended mapping relationship corresponding to the target DCS system alone, and the target picture conversion parameter, of the intermediate execution file compatible with the target DCS system includes: determining icon layout attribute data for the target DCS system according to the preset general mapping relationship and the general icon parameters; the icon layout attribute data is used to represent sizes and layout positions of icons in the DCS man-machine picture; and, determining icon function attribute data for the target DCS system according to the preset extended mapping relationship corresponding to the target DCS system alone and the custom extended parameters; the icon function attribute data is used to represent function attributes of icons in the DCS man-machine picture; generating the intermediate execution file according to the preset general mapping relationship, the preset extended mapping relationship, the icon layout attribute data, and the icon function attribute data.

[0007] In a possible implementation, the generating, according to the preset general mapping relationship, the preset extended mapping relationship, the icon layout attribute data, and the icon function attribute data, of the intermediate execution file includes: performing attribute value analysis on the icon layout attribute data and the icon function attribute data to construct a first attribute value list; the first attribute value list is used to store attribute values respectively associated with icon coordinates and icon functions of different icons; According to the preset general mapping relationship and the preset extended mapping relationship, the attribute value list is format-converted to generate a second attribute value list conforming to a storage format of the target DCS system; For each attribute value in the second attribute value list, according to an intermediate file specification of the target DCS system, the attribute value is encapsulated according to a hierarchical structure of the intermediate file specification to generate the intermediate execution file.

[0008] In a possible implementation, the format conversion of the attribute value list according to the preset general mapping relationship and the preset extended mapping relationship to generate a second attribute value list conforming to a storage format of the target DCS system includes: Based on the first attribute value list, a layout attribute value set and a function attribute value set are determined; According to the preset general mapping relationship, the layout attribute value set is format-converted to generate a layout attribute value pair list; and, According to the preset extended mapping relationship, the function attribute value set is format-converted to generate a function attribute value pair list; The layout attribute value pair list and the function attribute value pair list are field-spliced to generate the second attribute value list conforming to the storage format of the target DCS system; The layout attribute value pair list is used for storing a mapping pair of an attribute feature of a layout attribute and a data format in the target DCS system, and the function attribute value pair list is used for storing a mapping pair of an attribute feature of a function attribute and a data format in the target DCS system.

[0009] In a possible implementation, the intermediate execution file includes a figure layout attribute value and a figure function attribute value, the figure layout attribute value includes a position coordinate value and a size parameter value, and the figure function attribute value includes a medium code value, an execution logic parameter value, and a custom extended attribute conversion value.

[0010] In a second aspect, an embodiment of the present application provides a DCS man-machine picture conversion system, and the system includes: A parameter determination module is configured to determine a target DCS system and target picture conversion parameters according to a DCS picture conversion request in response to the DCS picture conversion request; The first file generation module is configured to generate an intermediate execution file compatible with the target DCS system according to a preset general mapping relationship, a preset extended mapping relationship corresponding to the target DCS system alone, and the target picture conversion parameter; the preset general mapping relationship and the preset extended mapping relationship are used to represent a mapping relationship between each type of parameter in the target picture conversion parameter and a picture icon in the target DCS system. The file import module is configured to import the intermediate execution file into the target DCS system to drive the target DCS system to generate a DCS man-machine picture corresponding to the DCS picture conversion request.

[0011] In a possible implementation, the target picture conversion parameter includes a general icon parameter and a custom extended parameter; the general icon parameter is used to represent a layout attribute of an icon in the DCS man-machine picture; and the custom extended parameter is used to represent a custom function attribute of the icon in the DCS man-machine picture. The first file generation module is specifically configured to: determine icon layout attribute data for the target DCS system according to the preset general mapping relationship and the general icon parameter; the icon layout attribute data is used to represent a size and a layout position of each icon in the DCS man-machine picture; and, determine icon function attribute data for the target DCS system according to the preset extended mapping relationship corresponding to the target DCS system alone and the custom extended parameter; the icon function attribute data is used to represent a function attribute of each icon in the DCS man-machine picture; generate the intermediate execution file according to the preset general mapping relationship, the preset extended mapping relationship, the icon layout attribute data, and the icon function attribute data.

[0012] In a possible implementation, the first file generation module includes a second file generation unit, which is configured to: perform attribute value analysis on the icon layout attribute data and the icon function attribute data to construct a first attribute value list; the first attribute value list is used to store an icon coordinate corresponding to each icon and an attribute value associated with a function of each icon; perform format conversion on the attribute value list according to the preset general mapping relationship and the preset extended mapping relationship to generate a second attribute value list conforming to a storage format of the target DCS system; According to the intermediate file specification of the target DCS system, each attribute value in the second attribute value list is encapsulated according to a hierarchical structure of the intermediate file specification to generate the intermediate execution file.

[0013] In a third aspect, embodiments of the present application provide an electronic device, the device comprising: a processor, a memory and a system bus; The processor and the memory are connected through the system bus; The memory is configured to store one or more programs, the one or more programs comprising instructions that, when executed by the processor, cause the processor to perform any possible DCS man-machine picture conversion method in the first aspect.

[0014] In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program, which, when executed by a processor, implements any possible DCS man-machine picture conversion method in the first aspect.

[0015] Compared with the prior art, the present application has the following beneficial effects: the embodiments of the present application provide a DCS man-machine picture conversion method, system, electronic device and medium. In the method, first, a target DCS system and required target picture conversion parameters are locked in response to a conversion request, and then the target picture conversion parameters are converted into an intermediate execution file compatible with the target DCS system according to a preset general mapping relationship and a preset extended mapping relationship corresponding to the target DCS system. The preset general mapping solves the common compatibility problem across systems, ensuring that the layout parameters of the picture icons will not be invalid due to system differences; and the preset extended mapping takes into account the uniqueness of the target DCS system, so that the individualized functions of the icons can also be accurately converted, thereby generating an intermediate execution file compatible with the target DCS system. Finally, after importing the intermediate file, the target DCS system can directly generate the corresponding picture without the need to repeatedly perform the design process of the DCS man-machine picture. In this way, in a nuclear power plant with the same type of reactor, multiple units but different DCS systems, only one conversion request is needed, and by adjusting the target DCS system and the corresponding extended mapping relationship, the same set of picture requirements can be adapted to different systems, without the need to redraw the same function pictures for each system, effectively realizing the mutual conversion of DCS man-machine pictures between different DCS systems. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0017] Figure 1 A structure schematic diagram of automatic conversion of man-machine picture between multiple DCS systems provided by the embodiment of the application; Figure 2 A flowchart of a DCS man-machine picture conversion method provided by the embodiment of the application; Figure 3 A schematic diagram of a general platform definition attribute provided by the embodiment of the application; Figure 4 A schematic diagram of conversion of intermediate execution files of a general DCS platform and a DCS1 system to DCS1 system data provided by the embodiment of the application; Figure 5 A flowchart of an intermediate execution file generation method provided by the embodiment of the application; Figure 6 A schematic diagram of a preset general mapping rule and a preset extended mapping relationship provided by the embodiment of the application; Figure 7 A flowchart of another intermediate execution file generation method provided by the embodiment of the application; Figure 8 A structure schematic diagram of a DCS man-machine picture conversion system provided by the embodiment of the application; Figure 9 A structure schematic diagram of an electronic device provided by the embodiment of the application. DETAILED DESCRIPTION

[0018] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the embodiments and the accompanying drawings. It should be particularly pointed out that the embodiments described in the embodiments of the present application are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0019] It should be noted that, unless otherwise defined, technical terms or scientific terms used in the embodiments of the present application shall have the common meaning understood by one of ordinary skill in the art to which the embodiments of the present application belong. The terms "first", "second", and similar terms used in the embodiments of the present application do not denote any order, quantity, or importance, but are merely used to distinguish different constituent parts. The terms "include", "contain", and similar terms mean that the elements or objects before the terms encompass the elements or objects listed after the terms and their equivalents, without excluding other elements or objects. The terms "connect" or "connected" and similar terms are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. The terms "upper", "lower", "left", "right", and the like merely represent relative positional relationships, which can change when the absolute positions of the described objects change.

[0020] As described above, in actual application scenarios, different nuclear power projects often correspond to different DCS systems. When there are nuclear power projects of the same reactor type, multiple units, but different DCS systems, because the DCS human-machine interfaces presented by different DCS systems to users are incompatible with each other, the DCS human-machine interfaces of the same function need to be redrawn according to the specific icon specification, file format, attribute definition, and other rules in different DCS systems, resulting in the need for project personnel to perform repetitive DCS human-machine interface design processes, and the DCS human-machine interfaces of different DCS systems for the same component or reactor type cannot be converted to each other.

[0021] Based on this, the embodiments of the present application provide a DCS human-machine interface conversion method, system, electronic device, and medium. In the method, first, in response to a conversion request, a target DCS system and required target picture conversion parameters are locked, and then the target picture conversion parameters are converted into intermediate execution files compatible with the target DCS system according to a preset general mapping relationship and a preset extended mapping relationship corresponding to the target DCS system. The preset general mapping solves the common compatibility problem across systems, ensuring that the layout parameters of the icons in the picture will not be invalid due to system differences; and the preset extended mapping takes into account the uniqueness of the target DCS system, so that the personalized functions of the icons can also be accurately converted, and then intermediate execution files compatible with the target DCS system are generated. Finally, after importing the intermediate files, the target DCS system can directly generate the corresponding pictures without repeatedly performing the design process of the DCS human-machine interface. In this way, in nuclear power projects of the same reactor type, multiple units, but different DCS systems, only one conversion request is needed, and by adjusting the target DCS system and the corresponding extended mapping relationship, the same set of picture requirements can be adapted to different systems, without the need to redraw the pictures of the same function for each system, effectively realizing the mutual conversion of the DCS human-machine interfaces between different DCS systems.

[0022] In the following, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all the other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0023] Referring to Figure 1 It is particularly pointed out that, in the application scenario of the present embodiment, the user issues a DCS picture conversion request through an interactive terminal in a nuclear power plant. When the user needs to perform DCS man-machine picture conversion and selects the function of "DCS picture conversion" through the interactive terminal, the system presents a general platform DCS man-machine picture through the interactive terminal. The user can select the target DCS system that needs to be converted through the general platform DCS man-machine picture presented on the interactive interface, and select or customize the icon that needs to be converted on the interactive interface, so as to determine the target picture conversion parameters. According to different picture conversion parameters and target DCS systems, the intermediate execution file specific to the DCS system needs to be generated, so as to drive the DCS system to generate the DCS man-machine picture through the intermediate execution file, thereby realizing flexible conversion of the DCS man-machine picture between different DCS systems. The conversion of the DCS man-machine picture can be realized by selecting the target DCS system on the general platform and determining the original picture conversion parameters, without the need of separate DCS man-machine picture design for specific types of DCS systems, thereby effectively improving the development efficiency of the nuclear power project.

[0024] Referring to Figure 2 The figure is a flowchart of a DCS man-machine picture conversion method provided by the present embodiment, which specifically includes the following steps: S101: In response to a DCS picture conversion request, determining a target DCS system and target picture conversion parameters according to the DCS picture conversion request.

[0025] Upon receiving the DCS screen conversion request, the request source is first identified through an interactive interface or a preset triggering mechanism, for example, when a user selects the "execute screen conversion" operation on the interactive interface, the basic information in the request is parsed, such as the source screen file path to be converted, the target nuclear power project identifier, and the like, and then the preset configuration file or database mapping table is used to match the DCS system type corresponding to the target nuclear power project. For example, if the project number carried in the request is associated with a certain nuclear power project, the target DCS platform information corresponding to the project can be automatically retrieved to determine the target DCS system. At the same time, the user can also manually select the target DCS system through a drop-down menu on the conversion interface to ensure flexibility in mixed scenarios. After determining the target DCS system, the screen conversion rule library corresponding to the target DCS system is further retrieved, and the mapping relationship of key parameters such as icon attribute, coordinate system, color mode, and the like of different DCS platforms is pre-stored in the rule library to convert the icon selected by the user for screen conversion into specific target screen conversion parameters.

[0026] Among them, the target screen conversion parameters cover the core elements for realizing cross-DCS system mapping, such as the icon name mapping table, the coordinate unit conversion coefficient, the color mode adaptation rule, and the attribute field correspondence, and the like. Among them, the icon name mapping table contains the correspondence between the general platform icon name and the target DCS system icon name, ensuring the unique identification of the icon identity. The coordinate unit conversion coefficient is used to solve the unit difference of the coordinate system of different DCS platforms, and by reading the X / Y coordinate values of the source screen and applying the coefficient conversion, the position accuracy of the icon in the target screen is ensured. The color mode adaptation rule is used to handle the definition difference of color attributes of different platforms (such as the conversion between RGB numerical format and hexadecimal code, or the compatibility processing of transparency parameter). The attribute field correspondence is used to clearly define the mapping logic of the general platform attribute (i.e., which platform is selected by the user for target DCS system and target conversion icon selection) and the target DCS system attribute (such as "medium color"), ensuring that all icon attribute information is transmitted without omission in the conversion process. These parameters can be pre-set in the rule library of the general platform through an Excel table, and temporary editing by the user according to the specific project requirements is also supported, forming a dynamically adjustable conversion parameter set, thereby covering the complex scenarios of multi-platform conversion.

[0027] The target conversion parameters include two types of general icon parameters and custom extension parameters. Among them, the general icon parameters are used to represent the layout attributes of the icons in the DCS human-machine screen. The custom extension parameters are used to represent the custom function attributes of the icons in the DCS human-machine screen. Specific examples of the general icon parameters and the custom extension parameters can be referred to Figure 3FIG. 1 is a schematic diagram of a general platform defining attributes according to an embodiment of the present application. In the figure, the "customized attribute" corresponds to the customized extension parameter in the embodiment of the present application, and the "general" corresponds to the general icon parameter in the embodiment of the present application.

[0028] Specifically, the general icon parameter mainly revolves around the spatial layout and presentation form of the icon in the picture, covering a series of basic attributes related to position, size, and level. For example, the coordinate positioning parameter of the icon is used to record its specific position in the picture, which may be in the form of X coordinate Y coordinate in the general platform. When converted to different target DCS systems, the system will automatically adapt or adjust according to the coordinate unit rules (such as pixels, logical units) of each platform or the conversion coefficient set by the user, ensuring the position accuracy of the icon in the target picture. The size parameter includes the width and height information of the icon, which can either follow the default size of the general platform or support user manual specification of the scaling ratio according to the display resolution of the target DCS system, such as adjusting a certain pipe icon from 100x80 pixels to 120x96 pixels to adapt to a high-definition screen. In addition, the general parameter also contains the hierarchical display order of the icon, which is used to solve the rule difference of different platforms for the superimposed display of the icon, for example, setting the icon of the alarm indicator light to the highest level to ensure that it is always displayed on the uppermost layer of the picture after conversion, avoiding being blocked by other icons. These parameters are like the "spatial identity card" of the icon, ensuring that the converted icon maintains a reasonable layout relationship in the target picture, both meeting the display specifications of each platform and maintaining the original visual logic.

[0029] On the other hand, the customized extension parameter focuses on the functional attributes and individual characteristics of the icon, covering specific attributes that are not pre-set in the general platform but may be needed in the target DCS system. Taking the medium flow icon in the nuclear power DCS picture as an example, its customized attributes may include the medium color parameter, which is used to identify the type of fluid in the pipe (such as red for high-temperature steam and blue for cooling water). This type of attribute needs to be extracted from the customized field of the general platform and mapped to the corresponding attribute of the target DCS system, such as directly converting the "Med_clr" value to the "medium color" parameter of the target DCS system. In addition, the functional interaction class parameter is particularly important, for example, the click event trigger logic of the icon - when the user clicks on a certain device icon through the interactive interface, the general platform may be defined as jumping to the detailed parameter interface, and the target DCS system may need to convert this logic into a specific script language or function call. At this time, the customized parameter records the specific pointing and execution rules of the interactive action. For complex icons, the extension parameter may also include animation effect configuration, such as the dynamic demonstration speed of a valve switch and the flicker frequency of an indicator light, which need to be converted and adapted according to the animation engine characteristics of the target DCS system.

[0030] S102: generating an intermediate execution file compatible with the target DCS system according to the preset general mapping relationship, a preset extended mapping relationship corresponding to the target DCS system alone, and the target picture conversion parameter.

[0031] As can be known from the foregoing, different DCS systems often have differences in the definition rules, data formats, interface specifications and the like of icon parameters, for example, the coordinate unit can be pixels or logical units, the implementation manner of functional interaction can depend on different script languages or API interfaces, and direct conversion is likely to cause information loss or format errors. Therefore, the role of the intermediate execution file is to build a standardized transition carrier, to "translate" the target picture conversion parameter into a language recognizable by the target DCS system through preset general mapping and extended mapping relationships, so that the target DCS system can directly generate a DCS man-machine picture according to the translated content, avoiding repeated design of the man-machine picture.

[0032] Among them, the intermediate execution file, as the core data carrier connecting the target picture conversion parameter and the target DCS system, integrates all the key attribute information required for the icon to be presented in the man-machine picture of the target DCS, mainly covering two core contents of icon layout attribute values and icon function attribute values. The icon layout attribute values focus on the spatial presentation manner of the icon in the picture, wherein the position coordinate value is used to accurately position the specific position of the icon in the target picture, and such parameters need to be adapted according to the coordinate rules of the target DCS system, for example, converting the pixel coordinates of the source picture into the logical coordinate unit of the target DCS system, to ensure that the icon will not have position deviation or display misplacement after conversion; the size parameter value defines the width and height of the icon, which can either follow the original size of the source picture or be scaled and adjusted according to the display resolution or design specification of the target DCS system, such as adjusting a certain device icon from 100x80 units suitable for a low-resolution screen to 150x120 units suitable for a high-definition screen, to ensure the visual proportion and clarity of the icon in different display environments.

[0033] The icon function attribute value focuses on the business logic and interaction characteristics of the icon, the medium code value is used to identify the medium type or state represented by the icon, for example, in the flowchart, different codes correspond to steam, cooling water and other media in the pipeline, ensuring that the target DCS system can accurately map the color, flow direction and other visualization features of the medium according to the code; the execution logic parameter value records the interaction behavior rules of the icon, such as the operation triggered when the user clicks on a certain valve icon - whether to jump to the device detail page, pop up a control pop-up window or perform state switching, such parameters need to be converted according to the script language or function interface of the target DCS system to ensure that the operation logic is completely reproduced on the target DCS system; the custom extension attribute conversion value is for special defined functional requirements in the source picture, for example, some security level DCS systems require icons to have permission verification levels, parameter configuration of specific animation effects, etc. These attributes not preset in the general framework will be converted into a format recognizable by the target DCS system through exclusive mapping rules to avoid losing personalized functions in cross-platform migration.

[0034] On the other hand, the preset general mapping relationship is used to process the spatial layout parameters of the icon, to solve the differences in basic attributes such as coordinate positioning, size definition, and hierarchical display on different platforms. For example, in coordinate mapping, the general platform may mark the icon position with "X / Y value", while different DCS systems may use "position left / position up" or "logical coordinates" respectively. The preset general mapping relationship establishes the corresponding rules for these different representations in advance, ensuring that the coordinate values specified in the target picture conversion parameters can be accurately converted according to the unit rules of the target DCS system (such as the conversion coefficient between pixels and logical units). The mapping of size parameters needs to consider display adaptation. When the icon size of the general platform is defined in pixels, the target DCS system may require relative size based on device resolution. At this time, the preset general mapping relationship will automatically call the preset scaling rules to adjust the specified size to the display standard of the target DCS system in proportion. The mapping of hierarchical order is more critical. The priority definition of icon superimposed display may differ between different DCS systems. The general mapping will convert the hierarchical number of the source picture to the corresponding display order parameter according to the rules of the target DCS system, ensuring that the visual superposition logic of the converted icon is consistent with the original picture. Figure 1

[0035] ​The preset extension mapping relationship is used to realize the migration of the icon function attribute, process the complex parameters such as the customized interaction logic and dynamic effect, and the like. Taking the medium color as an example, the general platform can record the RGB value through a specific field, and the target DCS system can directly call the color code or customize the field. The preset extension mapping relationship can explicitly specify the conversion rule of the personalized attribute, and ensure that the color information is transmitted without distortion between different platforms. The conversion of the function interaction parameter is more targeted. When the icon click event corresponding to the jump operation is specified in the target picture conversion parameter, different target DCS systems can depend on a specific script language or API interface. The preset extension mapping relationship can store the function interface rule of each platform in advance, and convert the operation logic into a code segment executable by the target DCS system. For the animation effect parameter, such as the dynamic speed of the valve switch, the extension mapping can adjust the parameter form according to the animation engine characteristics of the target DCS system, and ensure the smooth presentation of the dynamic effect. In the integration of the intermediate file, the layout and function attribute in the target picture conversion parameter are filled into the corresponding field one by one, forming a structured data set, with the double mapping relationship as the framework. In this process, the system automatically checks the integrity and format compliance of the parameters, such as whether the coordinate value meets the numerical requirements of the target DCS system, and whether the function parameter matches the platform interface rule, to avoid conversion errors caused by mapping vulnerabilities. Through this double mapping mechanism, the intermediate execution file becomes a bridge connecting the source picture and the target DCS system, which not only ensures the standardized conversion of the icon layout, but also realizes the accurate adaptation of the complex function attribute, and finally ensures that the display effect and operation logic after the cross-platform picture migration are highly consistent.

[0036] S103: Importing the intermediate execution file into the target DCS system to drive the target DCS system to generate a DCS human-machine picture corresponding to the DCS picture conversion request.

[0037] As a carrier bearing complete picture information, the hierarchical structure of the intermediate execution file is deeply adapted to the underlying architecture of the target DCS system, and the entire import process relies on the standardized structure of the intermediate file to realize automatic processing. The target DCS system can identify all attributes without manual intervention, which can greatly reduce the adaptation cost of the picture between different DCS systems. The finally generated DCS human-machine picture not only highly restores the original design in details such as visual layout and dynamic effect, but also seamlessly adapts to the operation logic of the target DCS system in the function level such as data monitoring instruction issuing and permission management, which marks the completion of the closed loop of cross-system picture migration. Through the bridging effect of the intermediate execution file, the target DCS system automatically constructs an interactive interface meeting the user's demand based on the standardized data, realizes the efficient reuse and seamless connection of the picture design between different DCS platforms, and effectively improves the migration efficiency and application compatibility of the human-machine interactive interface in a complex industrial environment.

[0038] For the conversion example of the intermediate execution file after being imported into the target DCS system, please refer to Figure 4 , Figure 4 The schematic diagram of the conversion of the intermediate execution file of the general DCS platform provided by the embodiment of the present application to the data of the DCS1 system is not described herein.

[0039] Next, the generation process of the intermediate execution file in step S102 will be introduced in combination with the specific flow embodiment drawings. Please refer to Figure 5 The flow schematic diagram of the intermediate execution file generation method provided by the embodiment of the present application specifically includes the following steps: S1021: determining the icon layout attribute data for the target DCS system according to the preset general mapping relationship and the general icon parameter; the icon layout attribute data is used to represent the size and layout position of each icon in the DCS man-machine picture.

[0040] The essence of this step is to adapt the general icon parameter to the display logic of the target DCS system through the preset general mapping rule, so as to ensure that the position and size of the icon on the man-machine picture of the target DCS system meet the expected visual effect.

[0041] Please refer to Figure 6 The schematic diagram of the preset general mapping rule and the preset extension mapping relationship provided by the embodiment of the present application, and the table shown in the diagram is one form of the preset general mapping rule and the preset extension mapping relationship. In the diagram, the first row of the table represents the attributes of the general platform, the second row represents the attributes of the DCS1 system relative to the general platform, and the third row represents the attributes of the DCS2 system relative to the general platform. As can be seen from the table in the diagram, the preset general mapping relationship is like a "layout translator" between different DCS systems, which defines the corresponding relationship between different DCS systems in basic layout parameters such as coordinate unit, size expression, and level rule in advance, for example, converts the "pixel coordinates" of the general platform into "logical coordinates" of the target DCS system, or converts the "width / height pixel value" into the "device-independent unit" required by the target DCS system. The general icon parameter is the original data used to describe the spatial characteristics of the icon in the target picture conversion parameter, including the position coordinates (such as X=1200, Y=800) of each icon, the geometric size (such as width 200, height 150), and the display level (such as located at the third layer). These data need to break through the format barriers between different DCS systems by means of the preset general mapping relationship, and then be converted into the layout language recognizable by the target DCS system.

[0042] In a specific conversion, the processing of position coordinates needs to consider the coordinate origin definition and unit rules of the target DCS system. For example, the source picture uses pixel positioning with the upper left corner as the origin, while the target DCS system may use the lower left corner as the origin and use logical units (1 logical unit = 2 pixels). The preset general mapping relationship automatically adjusts the coordinate origin position and applies the unit conversion formula to convert the source coordinates (1200, 800) to (600, 400) logical units of the target DCS system, ensuring that the actual display position of the icon in the target picture is consistent with the original Figure 1 The conversion of size parameters needs to adapt to the display resolution or design specifications of the target DCS system. If the source picture is designed for a low-resolution screen with an icon size of 200x150 pixels, and the target DCS system needs to adapt to a high-definition screen, the preset general mapping relationship will call the preset scaling factor (such as 1.5 times) to convert the size to 300x225 units, avoiding stretching or proportioning of the icon on the new screen. The mapping of display levels is also crucial. Different systems may define the order of icon superposition through different ways such as "level number" and "Z-axis coordinate". The general mapping relationship will accurately convert the source level parameters to the corresponding representation of the target DCS system, ensuring that the front and back occlusion relationship of multiple icons is consistent with the original picture.

[0043] S1022: Determine the icon function attribute data for the target DCS system according to the preset extended mapping relationship and the custom extended parameters corresponding to the target DCS system; the icon function attribute data is used to represent the function attributes of each icon in the DCS man-machine picture.

[0044] The preset extension mapping relationship is a set of exclusive conversion rules for each target DCS system, covering the special requirements of the system in terms of functional interface, script syntax, attribute definition, etc. For example, different systems may use different programming languages to implement interactive logic, some rely on Python scripts, and some use their own development languages. The extension mapping relationship will develop special conversion strategies for these differences to convert the functional logic of the source screen into a format that the target DCS system can recognize. Custom extension parameters include all non-standardized function definitions in the source screen, such as specific icon permission verification rules, medium flow animation parameter settings, custom alarm conditions, etc. These contents cannot be processed by general mapping and must be accurately converted with the corresponding extension mapping rules of the target DCS system. In specific conversion, the migration of functional attributes needs to be deeply adapted to the technical specifications of the target DCS system. Taking interactive logic as an example, the click event of a certain button icon in the source screen may correspond to the operation of "calling the device status query API". If the API interface name and parameter format of the target DCS system are different from the source system, the extension mapping will convert the source operation instruction into a code fragment that the target DCS system can recognize according to the preset interface mapping table, ensuring that the click function is correctly triggered on the new platform. The processing of dynamic effect parameters is more targeted. For example, the animation of a valve switch is defined in the source screen as "frame rate 20 frames per second, rotation angle 180 degrees", while the animation engine of the target DCS system requires parameters of "duration 2 seconds, rotation axis coordinates (X=5, Y=3)". The extension mapping will automatically convert the frame rate and angle into the time and coordinate parameters of the target DCS system, ensuring the smoothness and consistency of the animation effect. For custom attributes such as permission level, the source screen may use "administrator / operator / visitor" three-level identification, while the target DCS system uses numerical coding (1 represents administrator, 2 represents operator). The extension mapping will establish a clear code correspondence to ensure that the permission verification logic completely matches the security policy of the target DCS system after conversion.

[0045] In the specific conversion process, the migration of the function attributes needs to be deeply adapted to the technical specifications of the target DCS system. Taking the interactive logic as an example, if the click operation of a button icon in the source screen corresponds to the calling of a specific device state query interface, and the interface name and parameter format of the target DCS system are different, the extended mapping relationship will automatically convert the source operation instruction into a code segment executable by the target DCS system according to the pre-established interface mapping table, so as to ensure that the click function is correctly triggered on the new platform. The processing of dynamic effect parameters also needs to be converted in a targeted manner. For example, the valve switch animation in the source screen is defined by frame rate and rotation angle, while the animation engine of the target DCS system relies on duration and rotation axis coordinate parameters. The extended mapping will convert the frame rate angle and other parameters into the time coordinate parameters required by the target DCS system according to the preset conversion rules, so as to ensure the smoothness and consistency of the animation effect. For the permission check level and other custom attributes, if the source screen uses text to identify different permission levels, and the target DCS system uses numerical coding, the extended mapping relationship will establish clear corresponding rules, so that the permission check logic completely complies with the security policy of the target DCS system after conversion.

[0046] It should be particularly noted that the execution order of steps S1021 and S12022 is not limited in this embodiment, and both belong to steps that need to be executed in parallel.

[0047] S1023: generating the intermediate execution file according to the preset general mapping relationship, the preset extended mapping relationship, the icon layout attribute data, and the icon function attribute data.

[0048] According to the preset general mapping relationship, the preset extended mapping relationship, and the generated icon layout attribute data and icon function attribute data, the intermediate execution file is generated. This process integrates and encapsulates the cross-system adaptation information processed in the early stage to form a transitional data carrier (i.e., the intermediate execution file) that can be recognized by the target DCS system. Next, the generation process of the intermediate execution file in this step will be introduced in combination with a specific flow embodiment and drawings.

[0049] Referring to Figure 7 The figure is a flowchart of another intermediate execution file generation method provided by the embodiment of the application, which specifically includes the following steps: S1024: attribute value analysis is performed on the icon layout attribute data and the icon function attribute data to construct a first attribute value list; the first attribute value list is used to store the icon coordinates corresponding to different icons and the attribute values respectively associated with the icon functions.

[0050] The icon layout attribute data and the icon function attribute data are parsed to construct a first attribute value list. The core of this step is to extract specific attribute parameters from the two types of key data generated in the previous processing, and to organize them in a structured manner according to unified rules, providing a clear attribute mapping basis for subsequent cross-system conversion. The icon layout attribute data contains spatial layout information such as the position coordinates, size, and hierarchical relationship of each icon in the human-machine picture. The icon function attribute data covers interactive logic, dynamic effect parameters, and permission restrictions, etc. The two together constitute the complete attribute characteristics of the icon. In the parsing process, the two types of data need to be deeply disassembled. From the layout data, the coordinate values (such as X-axis and Y-axis coordinates), length and width dimensions, display order, and other layout-related attributes of each icon are extracted. From the function data, interactive trigger conditions, script code fragments, permission level identifiers, animation parameters (such as duration and motion trajectory), and other function-related attributes are extracted. These attribute values are standardized according to the pre-set unified format, such as converting the coordinate units (pixels, inches, etc.) used by different systems into the standard units required by the target DCS system, and adjusting the syntax format of the function script to a general form recognizable by the intermediate file.

[0051] When constructing the first attribute value list, an independent attribute set is established for each icon, and the layout attributes and function attributes are integrated in an associated manner to form a corresponding relationship of "icon unique identifier - layout attribute value - function attribute value". For example, the layout attribute values of a certain valve icon may include coordinates (100, 200), width 50 pixels, and height 30 pixels, and the function attribute values may include the state query instruction corresponding to the click event, the delay time parameter of animation switching, and the access permission identifier of the operator level, etc. These attribute values are arranged in order in the list according to the established rules, ensuring that the attribute information of each icon is not only independent and clear, but also mutually related. The role of this list is to convert the scattered attribute data into a structured storage form, which not only facilitates subsequent matching and conversion with the pre-set mapping relationship (including general layout mapping and extended function mapping), but also eliminates the differences in attribute definition between different DCS systems through a unified data format, providing a standardized data source for generating intermediate execution files. During the parsing process, the system will simultaneously perform validity checks on the attribute values, such as checking whether the coordinate values are negative, whether the function script has syntax errors, whether the permission level is within the defined range of the target DCS system, etc., to ensure that each data item in the first attribute value list accurately corresponds to the actual characteristics of the icon, laying a foundation for the accurate restoration of picture layout and correct execution of function logic in the subsequent cross-system migration process. This attribute parsing and list construction process essentially converts complex picture attribute information into structured data recognizable by machines, solves the data format barriers between different systems through standardized processing, and ensures the efficiency and accuracy of data conversion in subsequent steps.

[0052] S1025: Format conversion is performed on the attribute value list according to the preset general mapping relationship and the preset extended mapping relationship, to generate a second attribute value list conforming to the storage format of the target DCS system.

[0053] The core of the process of format conversion of the attribute value list according to the preset general mapping relationship and the preset extended mapping relationship to generate the second attribute value list is to eliminate the differences in data format, syntax specification and rule definition between the source system and the target DCS system through two layers of mapping rules, so that the attribute data can be directly recognized and processed by the target DCS system. Specifically, the process is realized through the following three steps: Step one, based on the first attribute value list, determine the layout attribute value set and the function attribute value set; Step two, according to the preset general mapping relationship, format conversion is performed on the layout attribute value set to generate a layout attribute value pair list.

[0054] And, According to the preset extended mapping relationship, format conversion is performed on the function attribute value set to generate a function attribute value pair list; Step three, field splicing is performed on the layout attribute value pair list and the function attribute value pair list to generate the second attribute value list conforming to the storage format of the target DCS system; Among them, the layout attribute value pair list is used to store the mapping pair of the attribute characteristics of the layout attribute and the data format in the target DCS system; the function attribute value pair list is used to store the mapping pair of the attribute characteristics of the function attribute and the data format in the target DCS system.

[0055] In the process of generating the second attribute value list, first, based on the first attribute value list that has been constructed, the attribute data therein is split into a layout attribute value set and a function attribute value set according to the functional characteristics. This splitting is derived from the essential difference between the two types of attributes: the layout attribute value set mainly contains the position coordinates, size, hierarchical order and other spatial layout related parameters of the icon, which determine the visual presentation mode of the icon in the target picture; the function attribute value set covers interactive logic, script code, permission level, animation parameters and other functional description contents, which directly affect the behavior logic of the icon in the target DCS system. By clearly distinguishing the two types of attributes, the system can call different mapping rules specifically, avoid conversion confusion caused by mixed processing, and lay a foundation for subsequent accurate adaptation to the technical specifications of the target DCS system.

[0056] For the conversion of the layout attribute value set, a preset general mapping relationship needs to be enabled. Such rules focus on solving the common differences in basic layout parameters of different DCS systems. For example, when the source system uses pixels as the coordinate unit and the target DCS system requires logical coordinates, the general mapping will convert the coordinate values according to the preset proportion formula, ensuring the position accuracy of the icon in the target picture; for the size parameter, the mapping rule will unify the expression of the long numerical value, avoiding display deviation caused by different units or precision standards; the description rule of the hierarchical order will also be standardized through the general mapping, ensuring that the front and back occlusion relationship of the icon is correctly restored in the target DCS system. After this series of conversion, the layout attribute value set will be converted into a layout attribute value pair list, where each "value pair" records the mapping relationship between the source attribute characteristics and the data format of the target DCS system, such as "source coordinate (pixel) - target coordinate (logical unit)", and these value pairs constitute the core basis for the target DCS system to parse the picture layout.

[0057] The conversion of the function attribute value set depends on the preset extended mapping relationship. Such rules aim to solve the individualized function adaptation problem of the target DCS system. Due to the significant differences in script syntax, interactive interface, permission system, etc. of different DCS systems, the extended mapping needs to deeply reconstruct the function attributes: if the interactive logic of the source system is implemented through Python script, and the target DCS system only supports its own script language, the mapping rule will parse the source script code line by line, and reorganize the function calls and variable definitions according to the target syntax; the textual description of the permission level (such as administrator, operator) will be converted into the numerical code defined by the target DCS system (such as 1, 2), ensuring seamless connection of the permission verification logic; the time axis setting in the animation parameter, the motion trajectory description, etc. will also be adjusted according to the characteristics of the rendering engine of the target DCS system, ensuring the consistency of dynamic effects. The converted function attribute value pair list also exists in the form of "source function characteristics - target implementation method" mapping pairs, such as "source script trigger event - target interface call instruction" and "source permission description - target coding rule". Finally, the layout attribute value pair list and the function attribute value pair list are field-spliced according to the storage format of the target DCS system, so that the layout information and the function logic form an organic whole in the second attribute value list, which not only retains the design elements of the source picture, but also through the precise adaptation of the two-layer mapping rules, makes all the attributes data conform to the parsing specification of the target DCS system.

[0058] S1026: For each attribute value in the second attribute value list, according to the intermediate file specification of the target DCS system, the attribute value is encapsulated according to the hierarchical structure of the intermediate file specification to generate the intermediate execution file.

[0059] For each attribute value in the second attribute value list, hierarchical encapsulation is performed according to the intermediate file specification of the target DCS system to generate an intermediate execution file. The core of this process is to organize the formatted attribute data in an order according to the format recognized by the target DCS system, forming a complete data carrier with a clear hierarchical relationship.

[0060] The intermediate file specification of the target DCS system generally defines a multi-level architecture from the file as a whole to the specific icon attributes, for example, the top layer may contain file basic information (version, generation time, target DCS system identification), the middle layer corresponds to the overall layout parameters of the picture (resolution, background setting), and the bottom layer is refined to the layout and function attributes of each icon. When encapsulating, the system needs to extract attribute pairs (i.e. layout and function attributes that have been adapted to the format of the target DCS system) from the second attribute value list one by one, and place them according to the hierarchical order preset by the specification, to ensure that each attribute value finds a corresponding "data node" in the file structure.

[0061] For example, the coordinate attribute value of an icon will be placed under the "picture layout-icon instance-position parameter" node, and the function script attribute value will be placed under the "icon function-interaction logic-execution instruction" node. Through this hierarchical organization method, the scattered attribute data forms a logically closely related whole. The encapsulation process needs to strictly follow the node naming rules, data type requirements and nesting relationships defined by the target DCS system, such as limiting numerical attribute values within a certain value range, matching enumeration values defined by the specification for enumeration attributes, and ensuring that the data format under each hierarchical node completely conforms to the parsing rules of the intermediate file. At the same time, the system generates a unique identifier for each icon and establishes an internal association between the layout attributes and the function attributes in the hierarchical structure, to avoid their isolated existence in the file, for example, by binding "position coordinates" and "click response logic" under the same sub-node through the icon ID, to ensure that the target DCS system can accurately associate the visual presentation and behavior logic of the icon when parsing.

[0062] The final intermediate execution file not only contains the complete attribute information of all icons, but also gives the data a clear logical context through the standardized hierarchical structure. This structured encapsulation not only facilitates efficient reading and parsing by the target system, but also eliminates data misplacement or format errors through hierarchical verification mechanisms. The intermediate execution file, as the "final data product" for cross-system migration, its hierarchical encapsulation process essentially builds a "data dictionary" for the target DCS system, so that each attribute value has a clear identity in the file architecture, ensuring that the picture layout and function logic can be restored step by step from top to bottom when parsing the file in the target system, achieving seamless connection from data conversion to actual application.

[0063] The embodiment of the present application provides a DCS man-machine picture conversion method, in the method, first, a target DCS system and required target picture conversion parameters are locked in response to a conversion request, then the target picture conversion parameters are converted into intermediate execution files compatible with the target DCS system according to a preset general mapping relationship and a preset extended mapping relationship corresponding to the target DCS system. The preset general mapping solves the common compatibility problem across systems, and ensures that the layout parameters of picture icons in the picture will not be invalid due to system differences; and the preset extended mapping takes into account the uniqueness of the target DCS system, so that the personalized functions of the icons can also be accurately converted, and then the intermediate execution files compatible with the target DCS system are generated. Finally, after the intermediate files are imported, the target DCS system can directly generate the corresponding picture without repeating the design process of the DCS man-machine picture. Therefore, in the project of the same reactor type, multiple units but different DCS systems, only one conversion request is needed, and by adjusting the target DCS system and the corresponding extended mapping relationship, the same set of picture requirements can be adapted to different systems, without the need to redraw the pictures with the same function for each system, and the mutual conversion of the DCS man-machine picture between different DCS systems is effectively realized.

[0064] A DCS man-machine picture conversion system provided by the embodiment of the present application is introduced below, and the DCS man-machine picture conversion system described below can be correspondingly referred to the DCS man-machine picture conversion method described above.

[0065] Referring to Figure 8 The figure is a structural schematic diagram of a DCS man-machine picture conversion system provided by the embodiment of the present application, and specifically includes the following modules: A parameter determination module 100 is configured to determine a target DCS system and target picture conversion parameters according to a DCS picture conversion request in response to the DCS picture conversion request; A first file generation module 200 is configured to generate intermediate execution files compatible with the target DCS system according to a preset general mapping relationship, a preset extended mapping relationship corresponding to the target DCS system and the target picture conversion parameters; the preset general mapping relationship and the preset extended mapping relationship are used to represent the mapping relationship between each type of parameter in the target picture conversion parameters and picture icons in the target DCS system; A file import module 300 is configured to import the intermediate execution files into the target DCS system to drive the target DCS system to generate a DCS man-machine picture corresponding to the DCS picture conversion request.

[0066] In a possible implementation, the target picture conversion parameter comprises: a general icon parameter and a custom extension parameter; the general icon parameter is used to represent layout attributes of icons in the DCS man-machine picture; and the custom extension parameter is used to represent custom function attributes of icons in the DCS man-machine picture. The first file generation module 200 is specifically configured to: determine icon layout attribute data for the target DCS system according to the preset general mapping relationship and the general icon parameter; the icon layout attribute data is used to represent sizes and layout positions of icons in the DCS man-machine picture; and, determine icon function attribute data for the target DCS system according to the preset extension mapping relationship corresponding to the target DCS system and the custom extension parameter; the icon function attribute data is used to represent function attributes of icons in the DCS man-machine picture; generate the intermediate execution file according to the preset general mapping relationship, the preset extension mapping relationship, the icon layout attribute data, and the icon function attribute data.

[0067] In a possible implementation, the first file generation module 200 comprises a second file generation unit, which is configured to: perform attribute value analysis on the icon layout attribute data and the icon function attribute data to construct a first attribute value list; the first attribute value list is used to store attribute values respectively associated with icon coordinates and icon functions of different icons; perform format conversion on the attribute value list according to the preset general mapping relationship and the preset extension mapping relationship to generate a second attribute value list conforming to a storage format of the target DCS system; for each attribute value in the second attribute value list, encapsulate the attribute value according to a hierarchical structure of an intermediate file specification of the target DCS system to generate the intermediate execution file.

[0068] Referring to Figure 9 , the figure is a structural schematic diagram of an electronic device provided by an embodiment of the present application, comprising: a memory 11 configured to store a computer program; a processor 12 configured to perform steps of a DCS man-machine picture conversion method provided by any method embodiment when the computer program is executed.

[0069] In the embodiment, the device can be a vehicle-mounted computer, a PC (Personal Computer), a smart phone, a tablet computer, a palm computer, a portable computer, or other terminal device.

[0070] The device can include a memory 11, a processor 12, and a bus 13.

[0071] The memory 11 includes at least one type of readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of the device, such as a hard disk of the device. In other embodiments, the memory 11 can also be an external storage device of the device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Further, the memory 11 can include both an internal storage unit and an external storage device of the device. The memory 11 can be used to store application software and various data installed in the device, such as program codes for performing the DCS man-machine picture conversion method, etc., and to temporarily store data that has been output or will be output. The processor 12 can be a central processing unit (CPU) in some embodiments.

[0072] The processor 12 can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments, and is used to run program codes or process data stored in the memory 11, such as program codes for performing the DCS man-machine picture conversion method, etc.

[0073] The bus 13 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 9 Only one thick line is used to represent the bus in the figure, but it does not mean that there is only one bus or only one type of bus.

[0074] Further, the device can also comprise a network interface 14, which can optionally comprise a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), typically used to establish a communication connection between the device and other electronic devices.

[0075] Optionally, the device can also comprise a user interface 15, which can comprise a display, an input unit such as a keyboard, and optionally a standard wired interface, a wireless interface. Optionally, in some embodiments, the display can be an LED display, a liquid crystal display, a touch liquid crystal display, an OLED (Organic Light-Emitting Diode) touch, etc. The display can also be appropriately referred to as a display screen or a display unit, for displaying information processed in the device and for displaying a visualized user interface.

[0076] Figure 9 Only the device with components 11-15 is shown, and those skilled in the art can understand that, Figure 9 The structure shown does not constitute a limitation on the device, and can comprise fewer or more components than shown, or combine certain components, or different component arrangements.

[0077] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the embodiments of the present application also provide a computer readable storage medium, which stores computer instructions for causing the computer to execute the DCS human-machine interface conversion method of any of the above embodiments.

[0078] The computer readable medium of the embodiments of the present application includes permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. The information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0079] The computer instructions stored in the storage medium of the above embodiments are used to make the computer execute the DCS man-machine picture conversion method according to any one of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which are not described herein again.

[0080] It should be noted that each of the embodiments in the present specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other. Each of the embodiments mainly describes the difference from other embodiments. Especially, the system, method, electronic device and medium embodiments are described relatively simply because they are basically similar to the method embodiments, and the relevant parts can be referred to the part of the method embodiments. The above described system, method, electronic device and medium embodiments are only illustrative, and the units described as separate components can be or can not be physically separated, and the components prompted as units can be or can not be physical units, that is, they can be located in one place or distributed on multiple network units. Part or all of the modules can be selected to achieve the purpose of the embodiments according to the actual needs. Those skilled in the art can understand and implement it without creative labor.

[0081] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited to this. Any skilled person in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for DCS human-machine picture conversion, characterized in that, The method comprises: in response to a DCS screen conversion request, determining a target DCS system and target screen conversion parameters according to the DCS screen conversion request; generating an intermediate execution file compatible with the target DCS system according to a preset general mapping relationship, a preset extended mapping relationship corresponding to the target DCS system alone, and the target screen conversion parameters; the preset general mapping relationship is used to represent a one-to-one mapping relationship between different types of layout parameters in the target screen conversion parameters and different types of icon layout parameters in the target DCS system; the preset extended mapping relationship is used to represent a one-to-one mapping relationship between different types of function parameters in the target screen conversion parameters and different types of icon function parameters in the target DCS system; importing the intermediate execution file into the target DCS system to drive the target DCS system to generate a DCS man-machine screen corresponding to the DCS screen conversion request.

2. The method of claim 1, wherein, The target screen conversion parameters comprise general icon parameters and custom extended parameters; the general icon parameters are used to represent layout attributes of icons in the DCS man-machine screen; the custom extended parameters are used to represent custom function attributes of icons in the DCS man-machine screen; The method comprises: determining icon layout attribute data for the target DCS system according to the preset general mapping relationship and the general icon parameters; the icon layout attribute data is used to represent sizes and layout positions of icons in the DCS man-machine screen; and determining icon function attribute data for the target DCS system according to the preset extended mapping relationship corresponding to the target DCS system alone and the custom extended parameters; the icon function attribute data is used to represent function attributes of icons in the DCS man-machine screen; generating the intermediate execution file according to the preset general mapping relationship, the preset extended mapping relationship, the icon layout attribute data, and the icon function attribute data.

3. The method of claim 2, wherein, The method comprises: performing attribute value analysis on the icon layout attribute data and the icon function attribute data to construct a first attribute value list; the first attribute value list is used to store icon coordinates corresponding to different icons and attribute values respectively associated with icon functions; performing format conversion on the attribute value list according to the preset general mapping relationship and the preset extended mapping relationship to generate a second attribute value list conforming to a storage format of the target DCS system; and According to the intermediate file specification of the target DCS system, the attribute value is encapsulated according to the hierarchical structure of the intermediate file specification to generate the intermediate execution file for each attribute value in the second attribute value list.

4. The method of claim 3, wherein, The format conversion of the attribute value list according to the preset general mapping relationship and the preset extended mapping relationship to generate a second attribute value list conforming to the storage format of the target DCS system includes: Based on the first attribute value list, a layout attribute value set and a function attribute value set are determined; According to the preset general mapping relationship, the layout attribute value set is format-converted to generate a layout attribute value pair list; And, According to the preset extended mapping relationship, the function attribute value set is format-converted to generate a function attribute value pair list; The layout attribute value pair list and the function attribute value pair list are field-spliced to generate the second attribute value list conforming to the storage format of the target DCS system; Wherein, the layout attribute value pair list is used to store the mapping pair of the attribute characteristics of the layout attribute and the data format in the target DCS system; the function attribute value pair list is used to store the mapping pair of the attribute characteristics of the function attribute and the data format in the target DCS system.

5. The method of claim 1, wherein, The intermediate execution file includes: icon layout attribute values and icon function attribute values, the icon layout attribute values include: position coordinate values and size parameter values, and the icon function attribute values include: medium code values, execution logic parameter values and custom extended attribute conversion values.

6. A DCS human picture conversion system, characterized by, The system includes: A parameter determination module is configured to determine a target DCS system and target picture conversion parameters in response to a DCS picture conversion request; A first file generation module is configured to generate an intermediate execution file compatible with the target DCS system according to a preset general mapping relationship, a preset extended mapping relationship corresponding to the target DCS system, and the target picture conversion parameters; the preset general mapping relationship and the preset extended mapping relationship are used to represent the mapping relationship between each type of parameter in the target picture conversion parameters and the picture icons in the target DCS system; A file import module is configured to import the intermediate execution file into the target DCS system to drive the target DCS system to generate a DCS human-machine picture corresponding to the DCS picture conversion request.

7. The system of claim 6, wherein, The target picture conversion parameters include: general icon parameters and custom extended parameters; the general icon parameters are used to represent the layout attributes of the icons in the DCS human-machine picture; the custom extended parameters are used to represent the custom function attributes of the icons in the DCS human-machine picture; The first file generation module is specifically configured to: Determine icon layout attribute data for the target DCS system according to the preset general mapping relationship and the general icon parameters; the icon layout attribute data is used to represent the size and layout position of each icon in the DCS human-machine picture; And, According to the preset extension mapping relationship and the self-defined extension parameter corresponding to the target DCS system, determine the icon function attribute data of the target DCS system; the icon function attribute data is used to represent the function attribute of each icon in the DCS man-machine picture; According to the preset general mapping relationship, the preset extension mapping relationship, the icon layout attribute data and the icon function attribute data, generate the intermediate execution file.

8. The system of claim 7, wherein, The first file generation module comprises a second file generation unit, and the second file generation unit is configured to: Perform attribute value analysis on the icon layout attribute data and the icon function attribute data to construct a first attribute value list; the first attribute value list is used to store the icon coordinates corresponding to different icons and the attribute values associated with the icon functions respectively; According to the preset general mapping relationship and the preset extension mapping relationship, perform format conversion on the attribute value list to generate a second attribute value list conforming to the storage format of the target DCS system; For each attribute value in the second attribute value list, according to the intermediate file specification of the target DCS system, encapsulate the attribute value according to the hierarchical structure of the intermediate file specification to generate the intermediate execution file.

9. An electronic device, comprising: The device comprises a processor, a memory and a system bus; The processor and the memory are connected through the system bus; The memory is used to store one or more programs, and the one or more programs comprise instructions which, when executed by the processor, cause the processor to execute the DCS man-machine picture conversion method in any one of claims 1-5.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the DCS man-machine picture conversion method in any one of claims 1-5.

Images