Generalized system operation management method, device and display terminal

Abstract

The application relates to a general system operation management method, device and display terminal, and the general system operation management method comprises the following steps: marking parameter variables in a system according to one or more unit types to which the parameter variables belong; when a unit type required by a user is called, activating all parameter variables marked as the unit type; and managing a unit corresponding to the unit type through the activated parameter variables. The application realizes the adaptability and generality of unit types through the parameter variable marking and activation method, and reduces system redundancy.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of generalization system, and particularly relates to a generalization system operation management method and device and a display terminal. BACKGROUND

[0002] At present, the display terminal of a commercial large-scale heating and ventilation device has low generalization degree. When different unit types are controlled, different display terminal software needs to be matched according to different unit types, that is, different software programs need to be burned and written, which increases maintenance cost and is inconvenient for centralized management. The existing generalization system stores the complete control function modules of each unit type in different storage areas of the system after packaging, and the software of the corresponding unit type is selected when used. Such a system has redundant common functions, occupies storage space, and does not realize true generalization. SUMMARY

[0003] To at least partially overcome the problem of redundant common functions and storage space occupation of the existing generalization system, the application provides a generalization system operation management method, device and display terminal.

[0004] In a first aspect, the application provides a generalization system operation management method, comprising:

[0005] Marking parameter variables in the system according to one or more unit types to which the parameter variables belong;

[0006] When a user required unit type is called, activating all parameter variables marked as the unit type;

[0007] Managing the unit corresponding to the unit type through the activated parameter variables.

[0008] Further, the method further comprises:

[0009] Marking the parameter variables according to menu types to which the parameter variables belong;

[0010] When a menu type is called, the parameter variables corresponding to the menu type are activated and displayed on one or more interfaces corresponding to the menu type.

[0011] Further, the method further comprises:

[0012] Encapsulating the marked parameter variables into different function modules;

[0013] When a function module is called, activating all parameter variables in the function module and executing the corresponding function.

[0014] Further, the method further comprises:

[0015] Judging whether the system and the unit are connected in an entity manner.

[0016] If yes, all parameter variables corresponding to the unit type of the unit are matched;

[0017] The interface display and / or function execution operation of all parameter variables corresponding to the unit type of the unit are activated.

[0018] Further, the method further comprises:

[0019] When one or more parameter variables have parameter exceptions, the states of the parameter variables in different function modules are locked to locate the abnormal causes.

[0020] Further, the parameter exceptions comprise:

[0021] One or more of parameter storage failure, communication exception, attribute assignment error and incorrect display.

[0022] Further, the locating of the abnormal causes comprises:

[0023] The time period when the parameter variables have exceptions is locked by viewing the changes of the marked parameter variables at different time.

[0024] The states of all function modules in the locked time period are viewed, and the abnormal causes are located according to the states of each function module.

[0025] Further, the method further comprises:

[0026] When one or more parameter variables have parameter exceptions, the states of all parameter variables corresponding to the unit type of the one or more parameter variables are searched to locate the abnormal causes.

[0027] In a second aspect, the application provides a universal system operation management device, comprising:

[0028] A marking module is configured to mark parameter variables in the system according to one or more unit types to which the parameter variables belong;

[0029] An activation module is configured to activate all parameter variables marked with a unit type when the unit type is called by a user;

[0030] A management module is configured to manage a unit corresponding to the unit type by using the activated parameter variables.

[0031] In a third aspect, the application provides a display terminal, comprising:

[0032] The universal system operation management device according to the second aspect.

[0033] The technical scheme provided by the embodiments of the application can have the following beneficial effects:

[0034] The universal system operation management method, device and display terminal provided by the embodiment of the application, the universal system operation management method comprises marking parameter variables in a system according to one or more unit types to which the parameter variables belong; when a user required unit type is called, activating all parameter variables marked as the unit type; and managing units corresponding to the unit type through the activated parameter variables, so that the adaptability and universality of unit types are realized through the parameter variable marking and activation method, and system redundancy is reduced.

[0035] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory and are not restrictive of the application. BRIEF DESCRIPTION OF DRAWINGS

[0036] The accompanying drawings incorporated in and forming a part of the specification illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application.

[0037] Figure 1 A flow chart of a universal system operation management method provided by an embodiment of the application.

[0038] Figure 2 A flow chart of a universal system operation management method provided by another embodiment of the application.

[0039] Figure 3 A functional structure diagram of a universal system operation management device provided by an embodiment of the application. DETAILED DESCRIPTION

[0040] To make the objects, technical solutions and advantages of the application clearer, the technical solutions of the application will be described in detail below. Obviously, the described embodiments are only some of the embodiments of the application, but not all the embodiments. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of the application.

[0041] Figure 1 A flow chart of a universal system operation management method provided by an embodiment of the application, as shown in Figure 1 The universal system operation management method comprises the following steps.

[0042] S11: Marking parameter variables in a system according to one or more unit types to which the parameter variables belong.

[0043] S12: When a user required unit type is called, activating all parameter variables marked as the unit type.

[0044] S13: Managing units corresponding to the unit type through the activated parameter variables.

[0045] The conventional universal system is to store a complete set of control function modules of each unit type in different storage areas of the system, and select the software corresponding to the unit type when used. Such a system has redundancy of common functions, occupies storage space, and does not realize true universalization.

[0046] In this embodiment, the universal system operation management method comprises marking parameter variables in the system according to one or more unit types to which the parameter variables belong; when a user required unit type is called, activating all parameter variables marked with the unit type; and managing the unit corresponding to the unit type through the activated parameter variables. The adaptability and universality of the unit type are realized through the parameter variable marking and activating method, and system redundancy is reduced.

[0047] Figure 2 The flowchart of the universal system operation management method provided for another embodiment of the present application is shown in FIG. 2, which comprises the following steps. Figure 2

[0048] S21: Marking parameter variables according to the menu types to which the parameter variables belong;

[0049] S22: When a menu type is called, the parameter variables corresponding to the menu type are activated and displayed on the interface corresponding to one or more menu types.

[0050] S23: Encapsulating the marked parameter variables into different function modules;

[0051] S24: When a function module is called, activating all parameter variables in the function module to execute the corresponding function.

[0052] S25: When one or more parameter variables have parameter exceptions, locking the state of the parameter variables in different function modules horizontally to locate the abnormal cause.

[0053] In some embodiments, the parameter exception comprises one or more of the following:

[0054] Parameter storage failure, communication exception, attribute assignment error, and incorrect display.

[0055] S26: When one or more parameter variables have parameter exceptions, vertically searching the state of all parameter variables in the unit type corresponding to the one or more parameter variables to locate the abnormal cause.

[0056] In some embodiments, locating the abnormal cause comprises:

[0057] Viewing the changes of the marked parameter variables at different times to lock the time period when the parameter variables have exceptions;

[0058] ​View the status of all functional modules during the locking period, and locate the abnormal cause according to the status of each functional module.

[0059] Some embodiments also include:

[0060] Determine whether the system is connected to the unit;

[0061] If so, match all parameter variables corresponding to the unit type of the unit.

[0062] Activate all parameter variables corresponding to the unit type of the unit to complete interface display and / or function execution operation.

[0063] In this application, the required unit type can be set on the display terminal, and the corresponding unit type marker can be activated for viewing and comparison. However, once the system is connected to the unit, the actual unit is used as the reference to match the interface and functions corresponding to the unit type, further ensuring the safety of the match and preventing misoperation due to mismatching of unit types.

[0064] In this embodiment, software functions of different unit types can be integrated to efficiently, simply, conveniently and safely apply to different units, realizing the generalization of commercial large unit display terminals.

[0065] In some embodiments, in the development mode, different unit types can be distinguished by customizing codes, which are assumed to be represented by A, B, C, D, etc. Parameter variables will be marked according to different unit types to facilitate subsequent unit type matching. For example, if parameter variable one is used by unit type A, it is marked as unit type A, and if it is used by other unit types, it is also marked, for example, unit type B, and other parameter variables may be marked by different unit types.

[0066] In some embodiments, different menu types can also be distinguished by customizing codes, which are assumed to be represented by I, II, III, IV, etc. Parameter variables will be marked according to different menu types to facilitate subsequent parameter layout. For example, parameter variable one belongs to compressor class parameters, which have two attributes of user and manufacturer. If parameter variable one has both attributes, it will be marked as menu I (compressor user) and menu II (compressor manufacturer). Therefore, other parameters may be marked by more than one menu type.

[0067] The parameter variables marked as above are encapsulated by different functional modules to facilitate subsequent function execution and abnormal problem handling. For example, parameter variable one is encapsulated by logic functional module 1, communication functional module 2, and storage functional module 3.

[0068] In the use mode, the corresponding machine type is automatically selected by the used machine set, such as the machine type A, all parameter variables marked with A are activated. The menu type of the parameter variables marked with A is acquired (activated), and according to different menu types, the interface distribution is distributed in each interface, the interface distribution of the menu can be manually adjusted, and the parameter variables of the same menu type are automatically arranged together. The parameter variables of the machine type A in each function module are activated, and each function is executed, so that the task of the whole system is completed.

[0069] In the maintenance mode, the abnormal situation is locked in two directions of horizontal or vertical. When a parameter variable has a problem, the state of the parameter variable in different function modules can be horizontally locked to quickly find the cause of the problem. Or when a function module has a problem, the state of the parameter variable marked with the machine type is found vertically, and the cause of the problem can also be found out.

[0070] In the embodiment, the display terminal screen using the method can replace multiple screens of different types, different machine sets can be selected or adapted on the display terminal, the development and maintenance period and cost are reduced, the development, use and maintenance modes are integrated and managed, and are completed on the display terminal screen, and the redundancy and errors generated between independent management are reduced. Moreover, the adaptability and universality of the machine type are realized through the parameter variable marking and activation.

[0071] The embodiment of the present application provides a universal system running management device, such as a function structure diagram shown in the figure. Figure 3 The universal system running management device comprises:

[0072] A marking module 31 is configured to mark parameter variables in a system according to one or more machine types to which the parameter variables belong.

[0073] An activation module 32 is configured to activate all parameter variables marked with a machine type when the machine type is called by a user.

[0074] A management module 33 is configured to manage a machine corresponding to the machine type through the activated parameter variables.

[0075] In the embodiment, the marking module marks parameter variables in a system according to one or more machine types to which the parameter variables belong, the activation module activates all parameter variables marked with a machine type when the machine type is called by a user, and the management module manages a machine corresponding to the machine type through the activated parameter variables, so that the adaptability and universality of the machine type are realized, and system redundancy is reduced.

[0076] The embodiment of the present application provides a display terminal, which comprises the universal system running management device described in the above embodiment.

[0077] It should be noted that the generalization system operation management method provided in the present application is applicable to different display terminal control requirements, and is not limited to the heat pump combined with solar display terminals.

[0078] It can be understood that the same or similar parts in the above embodiments can be mutually referenced, and the contents not described in detail in some embodiments can be referred to the same or similar contents in other embodiments.

[0079] It should be noted that in the description of the present application, the terms "first", "second", etc. are only for the purpose of description, and cannot be understood as indicating or implying relative importance. In addition, in the description of the present application, unless otherwise specified, the meaning of "a plurality of" is at least two.

[0080] Any process or method descriptions in flow charts or described herein in other ways can be understood as representing code modules, segments, or portions of code that include one or more executable instructions for performing specific logic functions or steps in the process, and the various embodiments of the present application include additional implementations in which the order of steps can be different, including use of a different order of executing hardware steps, or executing hardware steps in a substantially simultaneous manner, or in reverse order, depending on the functionality involved, which should be understood by those skilled in the art of the technical field to which the embodiments of the present application belong.

[0081] It should be understood that the parts of the present application can be realized by hardware, software, firmware or their combination. In the above embodiments, a plurality of steps or methods can be realized by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if realized by hardware, and as in another embodiment, it can be realized by any one or their combination of the following technologies known in the art: discrete logic circuit with logic gate circuit for implementing logic function on data signal, application specific integrated circuit with suitable combination logic gate circuit, programmable gate array (PGA), field programmable gate array (FPGA) and the like.

[0082] Those skilled in the art of the present technology can understand that all or part of the steps carried out by the above-mentioned embodiment methods can be completed by programs instructing related hardware, and the programs can be stored in a computer readable storage medium, and when executed, include one or a combination of steps of the method embodiments.

[0083] In addition, the functional units in each embodiment of the present application can be integrated in one processing module, or each unit can be physically present separately, or two or more units can be integrated in one module. The above integrated module can be realized in the form of hardware or in the form of a software function module. The integrated module, if realized in the form of a software function module and sold or used as an independent product, can also be stored in a computer readable storage medium.

[0084] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0085] In the description of the present specification, the description referring to the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0086] Although the embodiments of the present application have been shown and described above, it is understood that the above-described embodiments are exemplary, and should not be construed as limiting the present application, and those skilled in the art can make changes, modifications, replacements and variations to the above-described embodiments within the scope of the present application.

[0087] It should be noted that the present application is not limited to the above-mentioned best mode, and those skilled in the art can derive other various forms of products under the inspiration of the present application, but regardless of any changes in shape or structure, any technical solution having the same or similar technical solutions as the present application falls within the scope of the present application.

Claims

1. A generalized system operation management method, characterized in that, include: The parameter variables in the system are labeled according to the model of one or more generating units to which they belong; When the unit model required by the user is invoked, activate all parameter variables marked as the unit model; The activated parameter variables are used to manage the units corresponding to the unit model; Also includes: The parameter variables are labeled according to the menu type to which they belong; When a menu type is invoked, the parameter variable corresponding to that menu type is activated and displayed on one or more interfaces corresponding to that menu type. Also includes: The marked parameter variables are encapsulated into different functional modules; When a functional module is invoked, all parameter variables in that functional module are activated, and the corresponding function is executed. Also includes: Determine whether a physical connection has been established between the system and the generator unit; If so, match all parameter variables corresponding to the unit model of the unit; The system activates all parameter variables corresponding to the unit model to complete the interface display and / or function execution.

2. The generalized system operation management method according to claim 1, characterized in that, Also includes: When one or more parameter variables exhibit abnormal behavior, the state of the parameter variables in different functional modules is horizontally locked to locate the cause of the abnormality.

3. The generalized system operation management method according to claim 2, characterized in that, The parameter anomalies include: One or more of the following may cause an error: parameter storage failure, communication error, incorrect attribute assignment, or incorrect display.

4. The generalized system operation management method according to claim 3, characterized in that, The reasons for the location anomaly include: Examine the changes of the marked parameter variables at different times to pinpoint the time periods when the parameter variables exhibited abnormalities; View the status of all functional modules within the locked time period, and locate the cause of the anomaly based on the status of each functional module.

5. The generalized system operation management method according to claim 1, characterized in that, Also includes: When one or more parameter variables exhibit abnormalities, the status of all parameter variables in the corresponding unit model is searched vertically to locate the cause of the abnormality.

6. A universal system operation management device, characterized in that, include: The tagging module is used to tag parameter variables in the system according to one or more unit models to which they belong; The activation module is used to activate all parameter variables marked with the desired unit model when the unit model is called by the user. Also includes: The parameter variables are labeled according to the menu type to which they belong; When a menu type is invoked, the parameter variable corresponding to that menu type is activated and displayed on one or more interfaces corresponding to that menu type. Also includes: The marked parameter variables are encapsulated into different functional modules; When a functional module is invoked, all parameter variables in the functional module are activated, and the corresponding function is executed; the management module is used to manage the unit corresponding to the unit model through the activated parameter variables. Also includes: Determine whether a physical connection has been established between the system and the generator unit; If so, match all parameter variables corresponding to the unit model of the unit; The system activates all parameter variables corresponding to the unit model to complete the interface display and / or function execution.

7. A display terminal, characterized in that, include: The universal system operation management device as described in claim 6.

Images