Parameter verification and increment recovery method and device for parameter version of heat pump system, equipment and medium
By dynamically reading parameter version numbers and verification values, the problem of misjudgment caused by changes in parameter structure during version upgrades of heat pump systems is solved, realizing automated parameter migration and updates, and improving system stability and user experience.
Patent Information
- Application Number
- CN202510767809.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-10
- Publication Date
- 2025-11-04
AI Technical Summary
During software upgrades, existing heat pump systems cannot effectively handle verification failures caused by changes in parameter structure in new versions. This leads to the system misjudging the data as corrupted, forcing all parameters to be restored to their default values. Furthermore, manual intervention is required to configure parameters after the upgrade, which is cumbersome, error-prone, and degrades the user experience.
By dynamically reading parameter version numbers and verification values, the migration between old and new versions can be achieved without manual intervention. The parameter version number management and verification method supports flexible expansion of parameter length. Only fields that fail verification are reset, while other fields retain user configurations, and parameter migration and updates are completed automatically.
It improves system stability and user experience, reduces parameter reset time, and achieves compatibility and automated upgrades for different parameter versions without manual intervention.
Smart Images
Figure CN120892243A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of embedded system non-volatile storage technology, in particular to a parameter verification and incremental recovery method, device and medium for parameter version of a heat pump system. BACKGROUND
[0002] The parameter migration embedding of the dynamic version of the parameter of the heat pump system mainly refers to that in the running process of the heat pump system, the updated parameters are migrated to the control logic of the heat pump system according to the parameter software of the new version, so that the heat pump system can adjust and optimize the system parameters, so as to realize the efficient running and performance optimization of the heat pump system.
[0003] In the process of software version upgrade of the existing heat pump system, when the parameter migration embedding of the dynamic version is adopted, if the fixed length parameter structure and global CRC verification are used for parameter update of the heat pump system, when the parameter structure of the new version changes, such as adding a field to the parameter structure, the verification value will fail, which will cause the heat pump system to misjudge that the system parameter data is damaged, and the operation of forcibly restoring the full amount of parameters to the default value is performed, that is, the full amount of parameters is restored to the default value of the factory setting. If the parameter version number management identifier parameter version is used, the parameter migration problem when the parameter structure of the new version changes cannot be solved, and manual intervention is still needed after the parameter version is upgraded, and the user needs to reconfigure all parameters, which is tedious and prone to errors. SUMMARY
[0004] Therefore, the purpose of the present application is to provide a parameter verification and incremental recovery method for parameter version of a heat pump system, to realize new and old version migration under zero manual intervention, improve version compatibility, and avoid the problem of reducing user experience caused by misjudgment of the system and full parameter recovery to the default value.
[0005] A parameter verification and incremental recovery method for parameter version of a heat pump system, comprising the following steps:
[0006] S10 initializes all parameters of the current parameter version to default values;
[0007] S20 obtains the version number of the current parameter version and the version number of the stored parameter version, and judges whether the version number of the current parameter version is the same as the version number of the stored parameter version:
[0008] If they are the same, read the parameters according to the parameter length of the current parameter version, and execute S30;
[0009] If they are different, read the parameters according to the parameter length of the stored parameter version, and execute S40;
[0010] S30 retrieves the parameter values of the stored parameter version, calculates the checksums of each parameter in the current parameter version, and determines whether the checksums of each parameter in the current parameter version are equal to the checksums of the parameters corresponding to the stored parameter version.
[0011] If so, the system uses the parameter value of the stored parameter version;
[0012] If not, the parameter data is determined to be corrupted. The system reads the default value of the parameter in the current parameter version, recalculates the check value of the parameter in the current parameter version, and saves it.
[0013] S40 overwrites the parameter value of the stored parameter version with the parameter value of the current parameter version; concatenates the newly added parameters and / or newly added sub-parameters of the current parameter version with the parameter length of the stored parameter version to form a new parameter length; concatenates the default values of the newly added parameters and / or newly added sub-parameters of the current parameter version with the overwritten parameter value to form a new parameter value; the system reads and uses the new parameter length and the new parameter value, and retains the version number of the current parameter version.
[0014] Compared with existing technologies, this invention dynamically reads parameter length according to parameter version number, achieving precise retention of stored parameter version number parameters and isolation of default values for newly added parameter items. This solves the data overwrite problem caused by traditional fixed-length reading. By managing parameter sets through parameter length, it supports flexible parameter expansion, such as adding parameter A, adding sub-parameter C of parameter B, and changing the parameter length, thus achieving compatibility breakthroughs for different parameter versions. Through joint decision-making of parameter version number and parameter validation, scenario-based parameter validation processing reduces the risk of misjudgment during version upgrades, enabling incremental parameter recovery. Only fields that fail validation are reset, while other fields retain user configurations, improving system stability and user experience. After user parameter version upgrades, the system automatically completes parameter migration and storage updates without manual reconfiguration.
[0015] Furthermore, the parameter version includes a version number and a parameter set P{[P1,V1],[P2,V2],....,[P i V i ],...,[P n V n The parameter set P contains parameters, including the parameter length P. i and parameter value V i Parameter length P i Includes parameter name, sub-parameter items, and the number of sub-parameter items: P{[P1(name1,(p 11 ,p 12 ,...p 1m ),m),V1(v 11 ,v 12 ,...v 1m)],...,[P i (name i ,(p i1 ,p i2 ,...p il ),l),V i (v i1 ,v i2 ,...v il )],...,[P n (name n ,(p n1 ,p n2 ,...p k ),k),V n (v n1 ,v n2 ,...v nk )]}
[0016] wherein, the parameter length P of the parameter i i includes the parameter name name i , and the sub-parameter items (p i1 ,p i2 ,...p il ) and the number of sub-parameter items l; the parameter value V i includes the parameter values (v i1 ,v i2 ,...v il ) corresponding to the sub-parameter items (p i1 ,p i2 ,...p il ).
[0017] Further, the parameter check values of each parameter of the current parameter version in step S30 and the parameter check values corresponding to the stored parameter version are calculated by using the same parameter check method, and the parameter check method can be selected from the CRC (Cyclic Redundancy Check, cyclic redundancy check) parameter check method, the Hamming code parameter check method, or the Adler-32 parameter check method.
[0018] Further, step S40 further includes: based on the new parameter length and the new parameter value, re-computing and saving each parameter check value, and saving the new parameter length and the new parameter value in the current parameter version, and updating the parameter set.
[0019] Meanwhile, the present application also provides a parameter check and incremental recovery device for parameter version of a heat pump system, which comprises: a parameter initialization unit, a version number judgment unit, a check parameter calculation judgment unit and an overwriting and splicing parameter reading unit; wherein,
[0020] the parameter initialization unit is used for initializing all parameters of the current parameter version as default values;
[0021] The version number judging unit is used to acquire the version number of the current parameter version and the version number of the stored parameter version, and judge whether the version number of the current parameter version is same as the version number of the stored parameter version:
[0022] If yes, the parameter is read according to the parameter length of the current parameter version, and the parameter verification calculation judging unit is entered;
[0023] If no, the parameter is read according to the parameter length of the stored parameter version, and the overwritten spliced parameter reading unit is entered;
[0024] The parameter verification calculation judging unit is used to acquire the parameter value of the stored parameter version, calculate the parameter verification value of the current parameter version, and judge whether the parameter verification value of the current parameter version is equal to the corresponding parameter verification value of the stored parameter version:
[0025] If yes, the system uses the parameter value of the stored parameter version;
[0026] If no, it is determined that the parameter data is damaged, the system reads the parameter default value of the current parameter version, and re-calculates the parameter verification value of the current parameter version and saves it;
[0027] The overwritten spliced parameter reading unit is used to overwrite the parameter value of the corresponding current parameter version with the parameter value of the stored parameter version, splice and fuse the newly added parameter and / or newly added sub-parameter of the current parameter version and the parameter length of the stored parameter version into a new parameter length, splice and fuse the default value of the newly added parameter and / or newly added sub-parameter of the current parameter version and the overwritten parameter value into a new parameter value, and the system reads the new parameter length and the new parameter value, and retains the version number of the current parameter version.
[0028] Compared with the prior art, the parameter verification and incremental recovery device for the parameter version of the heat pump system has the same advantages as the above-mentioned parameter verification and incremental recovery for the parameter version of the heat pump system, which will not be repeated here.
[0029] In order to better understand and implement, the present application will be described in detail below with reference to the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS
[0030] Figure 1 The flowchart of the parameter verification and incremental recovery method for the parameter version of the heat pump system of the present application. DETAILED DESCRIPTION
[0031] The technical solutions of the present application will be described in detail below with reference to the accompanying drawings of the embodiments of the present application.
[0032] To address the problems of existing heat pump systems that, during software version upgrades, use fixed-length parameter structures and global CRC checks for parameter updates when dynamically migrating parameters, which cannot effectively handle verification failures caused by changes in the parameter structure of new versions, leading to misjudgments and forced full parameter restoration to default values, thus preventing system parameter optimization; and the issue that using parameter version numbers to manage parameter versions still requires manual intervention and user reconfiguration after upgrades, resulting in cumbersome, error-prone, and user-degraded parameter configuration, this invention proposes a parameter verification and incremental restoration method for heat pump system parameters. This method achieves zero-manual-intervention migration between old and new versions, improving version compatibility; and avoids system misjudgments leading to full parameter restoration to default values, preventing optimization of parameters with changed structures and degrading user experience.
[0033] Please see Figure 1 The parameter verification and incremental recovery method for heat pump system parameter versions described in this invention specifically includes the following steps.
[0034] After the S10 is powered on, it initializes all parameters of the current parameter version to their default values.
[0035] The parameter version is the running parameter that is managed using a version control system.
[0036] In specific implementation, the parameter version includes a version number and a parameter set P{[P1,V1],[P2,V2],....,[P i V i ],...,[P n V n The parameter set P contains parameters, including the parameter length P. i and parameter value V i Parameter length P i This includes the parameter name, sub-parameter items, and the number of sub-parameter items, as shown below:
[0037] P{[P1(name1,(p 11 ,p 12 ,...p 1m ),m),V1(v 11 ,v 12 ,...v 1m )],...,[P i (name i ,(p i1 ,p i2 ,...p il ),l),V i (v i1 ,v i2,...v il )]},...,[P n (name n ,(p n1 ,p n2 ,...p k ),k),V n (v n1 ,v n2 ,...v nk )]}
[0038] wherein, the parameter length P i of the parameter i includes the parameter name name i , and the sub-parameter items (p i1 ,p i2 ,...p il ) and the number of sub-parameter items l; the parameter value V i includes the parameter values (v i1 ,v i2 ,...v il ) corresponding to the sub-parameter items (p i1 ,p i2 ,...p il ).
[0039] For example, the parameter length of the compressor frequency parameter in the parameter version V2.0 includes the parameter name compressor frequency, and the sub-parameter items parameter values (the maximum operating frequency F MAX , the minimum operating frequency F MIN , the first platform frequency F 1-p , the second platform frequency F 2-p ), and the number of sub-parameter items 4.
[0040] This step initializes all parameters to default values before reading the stored parameters in the current parameter version, including initializing the parameter values of the new parameters and new sub-parameters to default values, to ensure the independence of the new parameters and new sub-parameters.
[0041] S20 obtains the version number of the current parameter version and the version number of the stored parameter version, and determines whether the version number of the current parameter version is the same as the version number of the stored parameter version:
[0042] If they are the same, the parameters are read according to the parameter length of the current parameter version, and step S30 is performed;
[0043] If they are different, the parameters are read according to the parameter length of the stored parameter version, and step S40 is performed.
[0044] The step is based on the parameter length of the stored parameter version number to read the parameter when the current parameter version and the stored parameter version are different, that is, the new and old versions are different, to realize accurate reservation of the old parameter; in combination with the parameter value setting of the added parameter and the added sub-parameter in S10 as the default value, the default value isolation of the added parameter and the added sub-parameter can be ensured, and the technical problem that the system full parameter needs to be reset or manual intervention is required to reset the parameter due to data abnormity when the parameter length of the new version is read in the traditional way is solved.
[0045] Meanwhile, the parameter is managed according to the parameter length instead of the hard-coded length, the system running parameter can be flexibly expanded, the system can be continuously upgraded to obtain better running parameters, and the running reliability and efficiency of the system can be improved on the basis of the same hardware.
[0046] S30 obtains the parameter value of the stored parameter version, and calculates the parameter check value of the current parameter version; whether the parameter check value of the current parameter version is equal to the parameter check value corresponding to the stored parameter version is judged:
[0047] If yes, the system uses the parameter value of the stored parameter version;
[0048] If no, it is determined that the parameter data is damaged, the system reads the parameter default value of the current parameter version, and re-calculates the parameter check value of the current parameter version read and saved.
[0049] The step is based on the parameter length of the stored parameter version number to read the parameter when the current parameter version and the stored parameter version are different, that is, the new and old versions are different, to realize accurate reservation of the old parameter; in combination with the parameter value setting of the added parameter and the added sub-parameter in S10 as the default value, the default value isolation of the added parameter and the added sub-parameter can be ensured, and the technical problem that the system full parameter needs to be reset or manual intervention is required to reset the parameter due to data abnormity when the parameter length of the new version is read in the traditional way is solved.
[0050] In specific implementation, when the parameter check values of the current parameter version and the stored parameter version are compared, the parameter check method of each parameter of the current parameter version and the stored parameter version is the same. In the selection of the parameter check method for calculating the parameter check value, the CRC (Cyclic Redundancy Check, cyclic redundancy check) parameter check method is preferentially recommended, and the Hamming code parameter check method or the Adler-32 parameter check method can also be used, and the application does not limit the parameter check method as long as the parameter check method of each parameter of the current parameter version and the stored parameter version is the same.
[0051] S40 overwrites the parameter value of the stored parameter version to the corresponding parameter value of the current parameter version; the new parameter length is obtained by splicing and fusing the added parameter and / or the added sub-parameter of the current parameter version and the parameter length of the stored parameter version, and the new parameter value is obtained by splicing and fusing the default value of the added parameter and / or the added sub-parameter of the current parameter version and the overwritten parameter value; the system reads and uses the new parameter length and the new parameter value, and retains the version number of the current parameter version.
[0052] Further, step S40 further comprises: based on the new parameter length and the new parameter value, recalculating and saving each parameter check value, saving the new parameter length and the new parameter value in the current parameter version, and updating the parameter set.
[0053] The application realizes accurate reservation of the parameter version number parameter and isolation of the default value of the new parameter item by dynamically reading the parameter length according to the parameter version number, solves the data coverage problem caused by traditional fixed-length reading, manages the parameter set through the parameter length, can support flexible expansion, such as adding A parameter, adding B parameter, changing the parameter length of the sub parameter C of the B parameter, and realizes compatibility breakthrough of different parameter versions; through the joint decision of the parameter version number and the parameter check, the scene-based parameter check processing reduces the risk of misjudgment during version upgrade, realizes incremental recovery of the parameter, only resets the field that does not pass the check, the remaining fields remain user configuration, improves system stability and user experience; after the user parameter version is upgraded, the system automatically completes parameter migration and storage update, without manual reconfiguration, in the factory debugging scene, the parameter reset time is shortened from an average of 5 minutes to 0 minutes.
[0054] Embodiment 1
[0055] For the scenario of different version numbers and parameter length expansion.
[0056] The NUM_X length in the storage parameter version is 10 bytes, the NUM_X length in the current parameter version is 12 bytes, and 2 bytes of parameters are added.
[0057] After the heat pump system is powered on, the NUM_X in the current parameter version is initialized to the default value.
[0058] Since the storage parameter version number and the current parameter version number are inconsistent, the parameters are read according to the parameter length of the storage parameter version, and the parameter length of the storage parameter version and the 2 bytes of newly added parameters of the current parameter version are fused to form the storage parameter version of NUM_X 10 bytes+2 bytes of default value, and the system parameter version number and the parameter check value of NUM_X are automatically updated.
[0059] Embodiment 2
[0060] For the scenario of the same version number but with new parameters.
[0061] The current parameter version adds a parameter NUM_Y, and the storage parameter version does not have this parameter.
[0062] After the heat pump system is powered on, the NUM_X in the current parameter version is initialized to the default value.
[0063] Since the storage parameter version number and the current parameter version number are consistent, the parameters are read according to the parameter length of the current parameter version.
[0064] Meanwhile, the application also provides a parameter verification and incremental recovery device for parameter version of a heat pump system, which comprises a parameter initialization unit, a version number judgment unit, a verification parameter calculation judgment unit and an overwritten spliced parameter reading unit; wherein,
[0065] The parameter initialization unit is used to initialize all parameters of the current parameter version to default values in step S10.
[0066] The version number judgment unit is used to acquire the version number of the current parameter version and the version number of the stored parameter version and judge whether the version numbers are the same in step S20.
[0067] If yes, the parameters are read according to the parameter length of the current parameter version, and the verification parameter calculation judgment unit is entered.
[0068] If no, the parameters are read according to the parameter length of the stored parameter version, and the overwritten spliced parameter reading unit is entered.
[0069] The verification parameter calculation judgment unit is used to acquire the parameter values of the stored parameter version, calculate the verification values of the parameters of the current parameter version and judge whether the verification values of the parameters of the current parameter version are equal to the corresponding verification values of the parameters of the stored parameter version in step S30.
[0070] If yes, the system uses the parameter values of the stored parameter version.
[0071] If no, it is determined that the parameter data is damaged, the system reads the default values of the parameters of the current parameter version, recalculates the verification values of the parameters of the current parameter version and saves them.
[0072] The overwritten spliced parameter reading unit is used to overwrite the parameter values of the stored parameter version with the corresponding parameter values of the current parameter version in step S40, splice and fuse the newly added parameters and / or newly added sub-parameters of the current parameter version with the parameter length of the stored parameter version into a new parameter length, splice and fuse the default values of the newly added parameters and / or newly added sub-parameters of the current parameter version with the overwritten parameter values into new parameter values, the system reads and uses the new parameter length and the new parameter values, and the version number of the current parameter version is kept.
[0073] The parameter verification and incremental recovery method for parameter version of a heat pump system is stored in an electronic device and is executed by the electronic device to realize parameter verification and incremental recovery for parameter version of a heat pump system. The electronic device includes but is not limited to a memory, a processor, a network interface and the parameter verification and incremental recovery device for parameter version of a heat pump system which are communicatively connected to each other through a system bus.
[0074] The electronic device can be a rack server, a blade server, a tower server, or a cabinet server, etc. The electronic device can be a standalone server, or a server cluster composed of multiple servers.
[0075] The memory includes at least one type of readable storage medium, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. The memory can be an internal storage unit of the electronic device, such as a hard disk or a memory of the electronic device. The memory can also be an external storage device of the electronic device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device. The memory can also include both the internal storage unit and the external storage device of the electronic device.
[0076] The processor can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor is generally used to control the overall operation of the electronic device, such as performing control and processing related to data interaction or communication of the electronic device, etc. The processor is used to run the program code or process data stored in the memory, such as running the parameter verification and incremental recovery method of the parameter version of the heat pump system, etc.
[0077] The network interface can include a wireless network interface or a wired network interface, which is generally used to establish a communication connection between the electronic device and other electronic devices. For example, the network interface is used to connect the electronic device with an external data platform through a network, to establish a data transmission channel and a communication connection between the electronic device and the external data platform. The network can be an intranet, the Internet, a global system for mobile communication (GSM), a wideband code division multiple access (WCDMA), a 4G network, a 5G network, Bluetooth, Wi-Fi, etc. wireless or wired network.
[0078] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of embodiments of the application. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. Expressions such as "first", "second", "third" etc. as used herein are to distinguish between similar entities but do not imply a sequence or order unless stated otherwise. The above description is presented to enable any person skilled in the art to make and use the application. Modifications within the scope of the application will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without the use of the inventive faculty. The present application is not intended to be limited to the embodiments shown, but is to be accorded the full scope consistent with the claims, to em¬brace all changes and modifications of the embodiments ac¬cording to the principles of the application, and the speci¬fically scope thereof.
[0079] The above description is presented to enable any person skilled in the art to make and use the application. Modifications within the scope of the application will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without the use of the inventive faculty. The present application is not intended to be limited to the embodiments shown, but is to be accorded the full scope consistent with the claims, to em¬brace all changes and modifications of the embodiments ac¬cording to the principles of the application, and the speci¬fically scope thereof.
Claims
1. A method for parameter verification and incremental recovery of a heat pump system parameter version, characterized in that, Includes the following steps: S10 initializes all parameters of the current parameter version to their default values; S20 obtains the version number of the current parameter version and the version number of the stored parameter version, and determines whether the version number of the current parameter version is the same as the version number of the stored parameter version: If they are the same, then read the parameters according to the parameter length of the current parameter version and execute S30; If they are different, the parameters are read according to the parameter length of the stored parameter version, and S40 is executed; S30 retrieves the parameter values of the stored parameter version, calculates the checksums of each parameter in the current parameter version, and determines whether the checksums of each parameter in the current parameter version are equal to the checksums of the parameters corresponding to the stored parameter version. If so, the system uses the parameter value of the stored parameter version; If not, the parameter data is determined to be corrupted. The system reads the default value of the parameter in the current parameter version, recalculates the check value of the parameter in the current parameter version, and saves it. S40 overwrites the parameter value of the current parameter version with the parameter value of the stored parameter version; The new parameter length is formed by concatenating the newly added parameters and / or sub-parameters in the current parameter version with the parameter length of the stored parameter version. The default values of the newly added parameters and / or sub-parameters in the current parameter version are concatenated with the overridden parameter values to form the new parameter values. The system reads and uses the new parameter length and the new parameter values, while retaining the version number of the current parameter version.
2. The method for parameter verification and incremental recovery of heat pump system parameter versions according to claim 1, characterized in that, The parameter version includes the version number and the parameter set P{[P1,V1],[P2,V2],....,[P i V i ],...,[P n V n The parameter set P contains parameters, including the parameter length P. i and parameter value V i Parameter length P i Includes parameter name, sub-parameter items, and the number of sub-parameter items: P{[P1(name1,(p 11 ,p 12 ,...p 1m ),m),V1(v 11 ,v 12 ,...v 1m )],...,[P i (name i ,(p i1 ,p i2 ,...p il ),l),V i (v i1 ,v i2 ,...v il )],...,[P n (name n ,(p n1 ,p n2 ,...p k ),k),V n (v n1 ,v n2 ,...v nk )]} Wherein, the parameter length P of parameter i i Including parameter name i and sub-parameters (p) i1 ,p i2 ,...p il ), and the number of sub-parameter items l; parameter value V i Including sub-parameter items (p) i1 ,p i2 ,...p il The corresponding parameter value (v) i1 ,v i2 ,...v il ).
3. The method for parameter verification and incremental recovery of heat pump system parameter versions according to claim 1, characterized in that, In step S30, the parameter verification values of the current parameter version and the parameter verification values corresponding to the stored parameter version are all calculated using the same parameter verification method. The parameter verification method can be selected from CRC (Cyclic Redundancy Check) parameter verification method, Hamming code parameter verification method, or Adler-32 parameter verification method.
4. The method for parameter verification and incremental recovery of heat pump system parameter versions according to claim 1, characterized in that, Step S40 further includes: recalculating and saving the verification values of each parameter based on the new parameter length and the new parameter values, and saving the new parameter length and the new parameter values in the current parameter version to update the parameter set.
5. A parameter verification and incremental recovery device for a heat pump system parameter version, characterized in that, include: The system includes a parameter initialization unit, a version number judgment unit, a parameter calculation and judgment unit, and a parameter overwrite and concatenation reading unit; among which... The parameter initialization unit is used to initialize all parameters of the current parameter version to their default values. The version number determination unit is used to obtain the version number of the current parameter version and the version number of the stored parameter version, and to determine whether the version number of the current parameter version and the version number of the stored parameter version are the same. If they are the same, the parameter is read according to the parameter length of the current parameter version and then enters the parameter calculation and judgment unit. If they are different, the parameters are read according to the parameter length of the stored parameter version, and then the parameter reading unit is entered for overwriting and splicing. The parameter calculation and judgment unit is used to obtain the parameter values of the stored parameter version, calculate the verification values of each parameter in the current parameter version, and determine whether the verification values of each parameter in the current parameter version are equal to the verification values of the parameters corresponding to the stored parameter version. If so, the system uses the parameter value of the stored parameter version; If not, the parameter data is determined to be corrupted. The system reads the default value of the parameter in the current parameter version, recalculates the check value of the parameter in the current parameter version, and saves it. The overwrite and concatenation read parameter unit is used to overwrite the parameter value of the stored parameter version with the parameter value of the current parameter version; to concatenate the newly added parameters and / or newly added sub-parameters of the current parameter version with the parameter length of the stored parameter version to form a new parameter length; to concatenate the default values of the newly added parameters and / or newly added sub-parameters of the current parameter version with the overwritten parameter value to form a new parameter value; the system reads and uses the new parameter length and the new parameter value, and retains the version number of the current parameter version.
6. The parameter verification and incremental recovery device for heat pump system parameter versions according to claim 5, characterized in that, The parameter version includes a version number and a parameter set P{[P1,V1],[P2,V2],....,[P i V i ],...,[P n V n The parameter set P contains parameters, including the parameter length P. i and parameter value V i Parameter length P i Includes parameter name, sub-parameter items, and the number of sub-parameter items: P{[P1(name1,(p 11 ,p 12 ,...p 1m ),m),V1(v 11 ,v 12 ,...v 1m )],...,[P i (name i ,(p i1 ,p i2 ,...p il ),l),V i (v i1 ,v i2 ,...v il )],...,[P n (name n ,(p n1 ,p n2 ,...p k ),k),V n (v n1 ,v n2 ,...v nk )]} Wherein, the parameter length P of parameter i i Including parameter name i and sub-parameters (p) i1 ,p i2 ,...p il ), and the number of sub-parameter items l; parameter value V i Including sub-parameter items (p) i1 ,p i2 ,...p il The corresponding parameter value (v) i1 ,v i2 ,...v il ).
7. The parameter verification and incremental recovery device for heat pump system parameter versions according to claim 5, characterized in that, The parameter verification values of the current parameter version and the parameter verification values of the stored parameter version in the parameter calculation and judgment unit are all calculated using the same parameter verification method. The parameter verification method can be selected from CRC (Cyclic Redundancy Check) parameter verification method, Hamming code parameter verification method, or Adler-32 parameter verification method.
8. The parameter verification and incremental recovery device for heat pump system parameter versions according to claim 5, characterized in that, The overwrite splicing and reading parameter unit also includes: recalculating and saving the verification values of each parameter based on the new parameter length and the new parameter value, and saving the new parameter length and the new parameter value in the current parameter version to update the parameter set.
9. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 4.
10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 4.