Encryption recognition method and device based on variable frequency driving, terminal equipment and storage medium

Abstract

The invention provides an encryption identification method based on variable frequency driving. The method comprises the following steps: reading first identification data in a first storage unit; the first storage unit is a storage unit integrated in the first control module in advance; the first identification data are preset first identity data of the first control module and first encrypted data corresponding to the first identity data; verifying the first identification data to obtain a first verification result; reading second identification data in a second storage unit; the second storage unit is a storage unit integrated in the first driving module in advance; the second identification data are preset second identity data of the first driving module and second encrypted data corresponding to the second identity data; verifying the second identification data to obtain a second verification result; and determining whether the first control module is matched with the first driving module according to the first verification result and the second verification result to obtain a matching result. Mixed use of different frequency converter matching modules is avoided, and the product index performance is improved.

Description

Technical Field

[0001] This application belongs to the field of frequency converter technology, and in particular relates to encrypted identification methods, devices, terminal equipment and storage media based on frequency conversion drives. Background Technology

[0002] In the field of frequency converters, general-purpose frequency converters need to be widely adapted to diverse application scenarios such as textiles, fans, and building water supply. However, different industries and customers have significant differences in their requirements for the functional configuration and performance parameters of frequency converters. Manufacturers need to modify the component specifications and control algorithms of the supporting modules to meet personalized needs. This means that even if the installation structure and control interface of the modules are consistent, the supporting modules for frequency converters of different specifications are essentially still different compatible products.

[0003] During equipment maintenance and repair, customers may mix and match different specifications of inverter modules due to lack of knowledge or improper operation, which may lead to unpredictable failures and ultimately cause the product to fail to meet the design expectations and performance. Summary of the Invention

[0004] This application provides an encrypted identification method, device, terminal equipment, and storage medium based on variable frequency drive, which can prevent the mixing of matching modules for variable frequency drives of different specifications and improve the product's performance and specifications.

[0005] In a first aspect, embodiments of this application provide an encrypted identification method based on frequency conversion drive, comprising: Read the first identification data from the first storage unit; wherein, the first storage unit is a storage unit pre-integrated into the first control module; the first identification data is the first identity data of the first control module and the first encrypted data corresponding to the first identity data pre-set; The first identification data is verified to obtain the first verification result; After the first verification result indicates that the verification is successful, the second identification data in the second storage unit is read; wherein, the second storage unit is a storage unit pre-integrated in the first driver module; the second identification data is the second identity data of the first driver module pre-set and the second encrypted data corresponding to the second identity data; The second identification data is verified to obtain the second verification result; Based on the first verification result and the second verification result, determine whether the first control module and the first drive module are matched, and obtain the matching result.

[0006] In this embodiment, the first identifier data of the built-in storage unit of the first control module is first read and verified. After confirming the compliance of the control module itself, the second identifier data of the built-in storage unit of the first drive module is read and verified. Finally, the matching of the modules is determined based on the two verification results. In this method, since both the control module and the drive module have built-in storage units that store unique identity data and corresponding associated data, the association verification logic corresponding to the identity data of modules of different specifications and models of frequency converters is exclusive. The control module will verify its own and the drive module's identity data through the verification logic corresponding to its own model. Only the identity data of modules of the same specification can pass the verification, while the identity data of modules of different specifications will inevitably fail the verification because they do not match the model binding logic of the control module, and will be judged as mismatched. This completely prevents misuse from a technical point of view, thereby ensuring that the product stably achieves the design expected indicators and performance.

[0007] In one possible implementation of the first aspect, the steps of verifying the target identification data to obtain the target verification result include: Encrypt the target identity data corresponding to the target identifier data to obtain the target verification data; The target identity data is verified based on the target verification data to obtain the target verification result; wherein, when the target identification data is the first identification data, the target identity data is recorded as the first identity data and the target verification result is recorded as the first verification result; when the target identification data is the second identification data, the target identity data is recorded as the second identity data and the target verification result is recorded as the second verification result.

[0008] In this embodiment, the logic of "encrypting and calculating verification data + verifying identity data" is used to accurately verify the legality and compatibility of the module. This avoids the mixing of different models of modules due to verification failure, ensuring product performance, and also eliminates the need for complicated operations, improving the convenience of module replacement and reducing usage and maintenance costs.

[0009] In one possible implementation of the first aspect, the target identity data corresponding to the target identifier data is encrypted and calculated to obtain target verification data, including: Extract the equipment model of the variable frequency drive unit; The target identity data is encrypted and calculated according to the encryption method corresponding to the device model to obtain the target verification data.

[0010] In this embodiment, by extracting the device model and matching the corresponding encryption method to encrypt the target identity data to generate verification data, it not only realizes the exclusive verification logic of different model modules, avoiding the mixing of modules of different specifications from the root, and ensuring that the product performance meets the standards, but also requires no additional hardware or network support, taking into account security, low cost, high universality, and flexible adaptation to module replacement scenarios.

[0011] In one possible implementation of the first aspect, the target identity data is verified based on the target verification data to obtain the target verification result, including: Compare the target verification data with the target encrypted data corresponding to the target identity data; If the target verification data is the same as the target encrypted data corresponding to the target identity data, then the target verification result indicates that the verification is successful; If the target verification data is different from the target encrypted data corresponding to the target identity data, the target verification result indicates that the verification failed; where the target identity data is the first identity data, the target encrypted data is recorded as the first encrypted data; when the target identity data is the second identity data, the target encrypted data is recorded as the second encrypted data.

[0012] In this embodiment, the verification result is determined by directly comparing the target verification data with the target encrypted data. The logic is simple and efficient, and it can quickly verify whether the modules are of the same model and have not been tampered with. This not only eliminates the risk of mixing modules of different specifications and software theft from the source, ensuring stable product performance, but also eliminates the need for complicated verification processes, adapts to the scenario of quick module replacement, and improves ease of use.

[0013] In one possible implementation of the first aspect, determining whether the first control module and the first drive module are matched based on the first verification result and the second verification result, and obtaining the matching result, includes: If both the first verification result and the second verification result are successful, the matching result indicates that the first control module and the first drive module are matched. If the first verification result fails, the matching result indicates that the first control module and the first drive module are not compatible.

[0014] If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, then the matching result indicates that the first control module and the first drive module do not match.

[0015] In this embodiment, the "control first, drive later, match only after both passes" judgment logic is adopted. The process is terminated if the first verification fails, which improves the verification efficiency and reduces invalid calculations. The requirement that matching is confirmed only after both verifications pass prevents the mixing of modules of different specifications or abnormal modules, avoids performance problems caused by software theft and module incompatibility, and ensures the compatibility of the matching module, ensuring that the product is stable and meets the standards. Moreover, it does not require complicated operations and can be flexibly changed in the field.

[0016] In one possible implementation of the first aspect, the method further includes: If the matching result indicates that the first control module and the first drive module are matched, then the frequency converter drive device is started; If the matching result indicates that the first control module and the first drive module are not compatible, a fault warning will be issued and the frequency converter drive device will be prohibited from starting. The fault warning is used to prompt the user to replace the unverified first control module or first drive module with a second control module or second drive module of the same model as the frequency converter drive device.

[0017] In this embodiment, the closed-loop control of "starting upon matching and providing a fault warning and prohibiting startup upon mismatch" ensures that only matching modules of the same model can drive the device, thus preventing substandard performance and security risks caused by the mixing of modules of different specifications and software theft from the terminal. It also accurately prompts users to replace the corresponding modules, reducing troubleshooting and maintenance costs. At the same time, it eliminates the need for complicated operations, ensuring the safety, stability and convenience of the device.

[0018] In one possible implementation of the first aspect, after the user replaces the unverified first control module or first drive module with a second control module or second drive module of the same model as the frequency converter drive device, the method further includes: Read the third identification data from the third storage unit; wherein, the third storage unit is a storage unit pre-integrated into the second control module; the third identification data is the third identity data of the second control module and the third encrypted data corresponding to the third identity data pre-set; The third verification result is obtained by verifying the third identifier data; Read the fourth identification data from the fourth storage unit; wherein, the fourth storage unit is a storage unit pre-integrated into the second driver module; the fourth identification data is the fourth identity data of the second driver module and the fourth encrypted data corresponding to the fourth identity data pre-set; The fourth identification data was verified, and the fourth verification result was obtained. Based on the third and fourth verification results, it is determined whether the first control module and the first drive module are matched, and the matching result is obtained.

[0019] In this embodiment, if the matching module is incompatible, it is replaced with a module of the same model, and then a complete secondary verification is performed. This ensures that the replaced second control module and second drive module are consistent with and compliant with the variable frequency drive device model, avoiding the problem of module misuse and software theft after replacement. It also eliminates the need for complex unbinding or network operations, adapting to rapid on-site maintenance scenarios. This ensures that the device can still stably achieve the design performance indicators after module replacement, while improving the flexibility and reliability of use and maintenance.

[0020] Secondly, embodiments of this application provide a frequency converter drive device, comprising: The first identification data reading module is used to read the first identification data in the first storage unit; wherein, the first storage unit is a storage unit pre-integrated in the first control module; the first identification data is the first identity data of the first control module and the first encrypted data corresponding to the first identity data pre-set. The first identifier data verification module is used to verify the first identifier data and obtain the first verification result; The second identification data reading module is used to read the second identification data in the second storage unit. The second storage unit is a storage unit pre-integrated into the first driver module. The second identification data is the second identity data of the first driver module and the second encrypted data corresponding to the second identity data. The second identifier data verification module is used to verify the second identifier data and obtain a second verification result; A matching determination module is provided to determine whether the first control module and the first drive module are matched based on the first verification result and the second verification result, and to obtain the matching result.

[0021] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the frequency conversion drive-based encryption identification method as described in any of the first aspects above.

[0022] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the frequency conversion drive-based encryption identification method as described in any of the first aspects above.

[0023] Fifthly, embodiments of this application provide a computer program product that, when run on a terminal device, causes the terminal device to execute the frequency conversion drive-based encryption identification method described in any of the first aspects above.

[0024] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

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

[0026] Figure 1This is a schematic diagram of the structure of the variable frequency drive device provided in this application; Figure 2 This is a flowchart illustrating the encryption identification method based on frequency conversion drive provided in the embodiments of this application; Figure 3 This is a schematic diagram of the process for obtaining verification results provided in the embodiments of this application. Figure 1 ; Figure 4 This is a schematic diagram of the process for obtaining verification results provided in the embodiments of this application. Figure 2 ; Figure 5 This is a schematic diagram of the process for obtaining matching results provided in an embodiment of this application; Figure 6 The flowchart of the error warning provided in the embodiments of this application is shown; Figure 7 This is a flowchart illustrating the process of replacing the supporting module provided in an embodiment of this application; Figure 8 This is a flowchart illustrating the overall process of factory encryption for the variable frequency drive device provided in this application embodiment; Figure 9 This is a flowchart illustrating the overall process of generating the identification ID and encrypted ID by the control module at the time of shipment, as provided in the embodiments of this application. Figure 10 This is a flowchart illustrating the overall process of generating the driver module identification ID and encrypted ID at the time of shipment, as provided in the embodiments of this application. Figure 11 This is a flowchart illustrating the overall process of power-on identification of the frequency converter drive device provided in the embodiments of this application. Figure 12 This is a flowchart illustrating the overall process of driver module identification provided in the embodiments of this application; Figure 13 This is a structural block diagram of the variable frequency drive device provided in the embodiments of this application; Figure 14 This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application. Detailed Implementation

[0027] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0028] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described feature, integral, step, operation, element or component, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components or a collection thereof.

[0029] It should also be understood that the term "or" as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0030] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0031] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0032] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0033] In the field of frequency converters, general-purpose frequency converters need to be widely adapted to diverse application scenarios such as textiles, fans, and building water supply. However, different industries and customers have significant differences in their requirements for the functional configuration and performance parameters of frequency converters. Manufacturers need to modify the component specifications and control algorithms of the supporting modules to meet personalized needs. This means that even if the installation structure and control interface of the modules are consistent, the supporting modules for frequency converters of different specifications are essentially still different compatible products.

[0034] During equipment maintenance and repair, customers may mix and match different specifications of inverter modules due to lack of knowledge or improper operation, which may lead to unpredictable failures and ultimately cause the product to fail to meet the design expectations and performance.

[0035] To address the aforementioned technical problems, this application provides an encrypted identification method based on variable frequency drive (VFD) technology. This method addresses the pain points of general-purpose VFDs, such as the easy mixing of compatible modules due to customized requirements in various scenarios, and the complexity, high cost, or poor universality of existing solutions. The method adds storage units to both the control module and the drive module, storing an identification ID generated from at least a 32-bit random number and an encrypted ID obtained using a device model-specific encryption method. Encryption configuration is completed by the host computer at the factory. After power-on, the control module verifies whether the verification ID obtained by encrypting its own and the drive module's identification IDs matches the stored encrypted ID, thus achieving module compatibility identification. This effectively avoids the mixing of modules of different specifications, ensuring product specifications and performance, and offers advantages such as ease of use, low cost, and high universality.

[0036] See Figure 1 This is a structural schematic diagram of the variable frequency drive device provided in this application, as shown below. Figure 1 As shown, the variable frequency drive unit includes a control module and a drive module, and each module is equipped with a corresponding storage unit. The control module and drive module are encrypted separately during the factory manufacturing process. Specifically: Encryption process of the control module: At the time of manufacture, the host computer is connected to the frequency converter drive device via wired connection, and can read the data in the storage units of the control module and drive module via wired communication, and can also write the data into the storage units of the control module and drive module via wired communication. During the encryption process, the host computer reads the identification ID and encryption ID of the control module and determines whether the control module has both an identification ID and an encryption ID.

[0037] If the control module has both an ID and an encrypted ID, then older machines do not need to generate or encrypt the ID. If the control module identification ID and encryption ID are not available, the host computer generates at least a 32-bit random number as the identification ID of the control module, and encrypts the control module identification ID using a dedicated encryption method according to the device model of the frequency converter drive to obtain the corresponding encryption ID. The host computer writes the generated identification ID and encryption ID into the storage unit of the control module, thus completing the generation process of the control module identification ID and encryption ID.

[0038] Encryption process of driver module: The host computer reads the identification ID and encryption ID of the driver module and determines whether each driver module has an identification ID and encryption ID.

[0039] If the aforementioned driver module has an identification ID and an encrypted ID, then older machines do not need to generate or encrypt the identification ID. If the drive module identification ID and encryption ID are not available, the host computer generates at least a 32-bit random number as the identification ID of the drive module, and encrypts the drive module identification ID using a dedicated encryption method according to the device model of the frequency converter drive device to obtain the corresponding encryption ID. The host computer writes the generated identification ID and encryption ID into the storage unit of the drive module, thus completing the factory encryption process of the frequency converter drive device.

[0040] After the control module and drive module of the variable frequency drive are encrypted and processed before leaving the factory, when the variable frequency drive is powered on normally, the encrypted data in its storage unit can be used to prevent the mixing of modules for different specifications of variable frequency drives, thereby improving the product's specifications and performance. The details are as follows: See Figure 2 This is a flowchart illustrating an encryption identification method based on variable frequency drive provided in an embodiment of this application. It is applied to the first control module in a variable frequency drive device, which further includes a first drive module. Figure 1 As shown, and not as a limitation, a method may include the following steps: S101, read the first identification data in the first storage unit; wherein, the first storage unit is a storage unit pre-integrated in the first control module; the first identification data is the first identity data of the first control module and the first encrypted data corresponding to the first identity data pre-set.

[0041] In this embodiment, the first storage unit is a dedicated storage device (such as EEPROM) pre-integrated within the first control module. It is used to permanently store core identification data, eliminating reliance on external storage devices and ensuring data security and ease of access. The first identification data includes two sets of associated data: first identity data (i.e., identification ID, generated from at least 32-bit random numbers, serving as the unique basic identifier of the first control module to distinguish different modules) and first encrypted data (i.e., encrypted ID, obtained by encrypting the first identity data using a proprietary encryption method corresponding to the inverter drive device model, serving as an encrypted credential for module legitimacy). After power-on, the first control module retrieves the pre-stored first identity data and first encrypted data from its integrated first storage unit via an internally preset communication link (such as I2C, SPI, etc.), providing raw data support for subsequent "ID verification generation," "data comparison," and "module legitimacy / compatibility determination."

[0042] Specifically, before the first control module leaves the factory, the host computer establishes a connection with the frequency converter drive device through a wired communication interface (such as RS485, Ethernet, etc.). It first checks whether the first storage unit of the first control module has stored the first identity data and the first encrypted data. If not, it generates at least 32-bit random numbers as the first identity data. Then, it encrypts the first identity data according to the dedicated encryption algorithm (such as symmetric encryption, hash algorithm, etc.) corresponding to the device model of the frequency converter drive device to obtain the first encrypted data. Subsequently, the two sets of data are synchronously written into the first storage unit to complete the pre-configuration.

[0043] When the frequency converter is powered on, the first control module automatically initializes the internal communication interface, establishes a data interaction channel with the first storage unit, and retrieves the first identity data and the first encrypted data according to the preset reading protocol.

[0044] S102, the first identification data is verified to obtain the first verification result.

[0045] In this embodiment, after the first control module is powered on, the core verification action after reading the first identification data is intended to confirm the legitimacy of the first control module itself (whether it has been factory encrypted and configured, and whether the software has been stolen). The "first verification result" is the output conclusion of the verification action, which is divided into only two categories: "verification passed" and "verification failed". It directly determines whether the first control module allows the subsequent drive module verification and the start of the frequency converter drive device.

[0046] S103, read the second identification data from the second storage unit; wherein, the second storage unit is a storage unit pre-integrated into the first driver module; the second identification data is the second identity data of the first driver module pre-set and the second encrypted data corresponding to the second identity data.

[0047] In this embodiment, after obtaining the first verification result, and only after the first control module completes its own legitimacy verification (the first verification result is passed), the matching verification action of the second drive module is triggered. The core purpose is to obtain the core identification data of the first drive module, laying the foundation for subsequent judgment on whether the control module and the drive module are compatible. The second identification data includes two sets of associated core data: second identity data (i.e., the identification ID of the first drive module, generated by at least 32 random numbers, which is the unique basic identifier of the first drive module used to distinguish different drive modules) and second encrypted data (i.e., the encrypted ID of the first drive module, obtained by encrypting the second identity data using a dedicated encryption method corresponding to the model of the frequency converter drive device, which is the key encrypted credential for verifying the legitimacy of the drive module and its compatibility with the control module).

[0048] Specifically, after the first control module completes its own verification (the first verification result is passed), it automatically starts the internal communication link with the first drive module. The first control module establishes data interaction with the second storage unit of the first drive module through a preset internal communication link (such as I2C, SPI, etc.), and retrieves the pre-stored second identity data and second encrypted data according to the preset reading protocol, providing raw data support for subsequent "generating the drive module verification ID", "comparing with the second encrypted data" and "determining module compatibility".

[0049] S104, verify the second identifier data to obtain the second verification result.

[0050] In this application embodiment, "verifying the second identification data and obtaining the second verification result" is the core closing step of the frequency converter drive device encryption identification process. It is triggered only after the first control module passes its own verification (the first verification result is passed) and successfully reads the second identification data. The core purpose is to determine whether the first drive module is a matching module of the same model as the first control module, and thus determine whether the frequency converter drive device can operate normally.

[0051] In one embodiment, see Figure 3 This is a schematic diagram of the process for obtaining verification results provided in the embodiments of this application. Figure 1 ,like Figure 3 As shown, the steps for verifying the target identifier data and obtaining the target verification result include: S201, perform encrypted calculation on the target identity data corresponding to the target identification data to obtain the target verification data.

[0052] In this application, the core logic of "verification data generation" in the encrypted identification method for frequency converter drive devices is applicable to the dual verification scenario where the first control module verifies its own legitimacy (first identification data verification) and its compatibility with the first drive module (second identification data verification).

[0053] Before the variable frequency drive unit leaves the factory, a dedicated encryption algorithm (such as a customized symmetric encryption algorithm, hash algorithm, etc.) bound to the model of the variable frequency drive unit has been embedded into the program of the first control module to ensure that the encryption logic is completely consistent with the algorithm of the host computer encrypting the target identity data. After reading the target identification data, the first control module separates the target identity data from the data set (the first identity data is extracted when reading the first identification data, and the second identity data is extracted when reading the second identification data).

[0054] The first control module invokes a pre-embedded dedicated encryption algorithm, using the extracted target identity data as input parameters. Through preset operational logic (such as key matching, data segmentation encryption, and checksum generation), it completes the encryption process, generating corresponding target verification data (first verification ID or second verification ID). The generated target verification data is temporarily stored in the first control module's temporary storage area, awaiting a consistency comparison with the pre-stored encrypted data (first encrypted data or second encrypted data) in the target identification data, and then outputting the verification result.

[0055] In one embodiment, step S201 includes: Extract the device model of the variable frequency drive unit; encrypt the target identity data according to the encryption method corresponding to the device model to obtain the target verification data.

[0056] In the embodiments of this application, "the device model of the variable frequency drive device" refers to the model code (e.g., a unique number for a specific series and parameter combination) that is preset at the factory to uniquely identify the product specifications (such as power level, applicable scenarios, hardware configuration, etc.). It is the core identifier that distinguishes variable frequency drive devices of different specifications, and its associated dedicated encryption method has been pre-embedded in the control module.

[0057] The model number of the variable frequency drive device is used as a basic parameter and is embedded in the program storage area of ​​the control module (rather than in the identification data of an independent storage unit) along with the corresponding dedicated encryption algorithm, forming a "model-encryption algorithm" binding relationship. When the control module needs to encrypt the target identity data (the identification ID of the control module or drive module), it directly calls the pre-embedded device model association information in the local program without additional reading or verification, ensuring that the encryption method is consistent with the factory configuration.

[0058] Specifically, the control module activates the corresponding dedicated encryption method (such as customized symmetric encryption, hash operation combined with check bit generation, etc.) based on the pre-preserved device model. It takes the extracted target identity data (identification ID) as the input parameter of the encryption algorithm and performs encryption calculation according to the preset operation logic of the encryption method (such as data segmentation processing, key matching operation, check field generation, etc.). After the encryption operation is completed, it generates unique corresponding check data (i.e., target check data, such as the first check ID or the second check ID). This data will be used to compare the consistency with the pre-stored encrypted ID (first encrypted data or second encrypted data) to determine the legality or compatibility of the module.

[0059] The above method extracts the device model and matches the corresponding encryption method to encrypt the target identity data to generate verification data. This not only realizes the exclusive verification logic of different model modules, avoiding the mixing of modules of different specifications from the root, and ensuring that the product performance meets the standards, but also requires no additional hardware or network support. It balances security, low cost, high universality, and can flexibly adapt to module replacement scenarios.

[0060] S202, verify the target identity data based on the target verification data to obtain the target verification result; wherein, when the target identification data is the first identification data, the target identity data is recorded as the first identity data and the target verification result is recorded as the first verification result; when the target identification data is the second identification data, the target identity data is recorded as the second identity data and the target verification result is recorded as the second verification result.

[0061] In this embodiment, when the target identification data is the first identification data (the identification set of the control module): the target identity data is the first identity data (the identification ID of the control module, ≥32-bit random number), the target verification data is the first verification ID generated by the control module encrypting the first identity data based on its own device model using a dedicated encryption method, and the target verification result is the first verification result (determining whether the control module is legitimate); when the target identification data is the second identification data (the identification set of the driver module): the target identity data is the second identity data (the identification ID of the driver module, ≥32-bit random number), the target verification data is the second verification ID generated by the control module encrypting the second identity data based on its own device model using a dedicated encryption method, and the target verification result is the second verification result (determining whether the driver module and the control module are compatible).

[0062] By comparing the "real-time generated target verification data" with the "factory-stored encrypted data", it is ensured that the control module has not been tampered with (the software has not been stolen) and that the drive module is a matching product of the same model, thus avoiding substandard equipment performance caused by mixed use or illegal replacement of modules.

[0063] The above method uses the logic of "encrypted calculation to obtain verification data + verification data to verify identity data" to accurately verify the legality and compatibility of modules. This not only avoids the mixing of different models of modules due to verification failure, thus ensuring product performance, but also eliminates the need for complicated operations, improves the convenience of module replacement, and reduces the cost of use and maintenance.

[0064] In one embodiment, see Figure 4 This is a schematic diagram of the process for obtaining verification results provided in the embodiments of this application. Figure 2 ,like Figure 4 As shown, step S202 includes: S301, compare the target verification data with the target encrypted data corresponding to the target identity data.

[0065] In this embodiment of the application, "comparing the target verification data with the target encrypted data corresponding to the target identity data" essentially involves comparing the "real-time calculated verification result" with the "factory-pre-stored encryption certificate" to verify the legality or compatibility of the module, covering two major scenarios: control module self-testing and driver module verification. Specifically: Scenario 1 (Control Module Self-Check): The target identity data is the first identity data, the target encrypted data is the first encrypted data, and the target verification data is the first verification ID. The comparison result is the first verification result, which determines whether the control module is legitimate. Scenario 2 (Driver Module Verification): The target identity data is the second identity data, the target encrypted data is the second encrypted data, and the target verification data is the second verification ID. The comparison result is the second verification result, which determines whether the driver module is compatible.

[0066] Specifically, the control module extracts the target encrypted data from the built-in storage units (first storage unit / second storage unit) and simultaneously retrieves the target verification data from temporary storage to ensure that the two sets of data have the same format (e.g., both are hexadecimal encoding) for accurate comparison. Through the comparison logic preset within the control module, the target verification data and the target encrypted data are verified bit by bit or compared with hash values ​​to ensure that the data consistency judgment is error-free.

[0067] S302, if the target verification data is the same as the target encrypted data corresponding to the target identity data, then the target verification result indicates that the verification is successful.

[0068] In this embodiment, after the control module extracts the target identity data, it calls a pre-prepared encryption method to generate target verification data. It then confirms whether the verification data is completely identical to the target encrypted data through bit-by-bit comparison or hash value matching. Verification is only considered successful if the comparison result is "completely identical," thus avoiding misjudgments due to data errors.

[0069] For example, when the target identity data is the first identity data, the target encrypted data is the first encrypted data, and the target verification data is the first verification ID, if the three satisfy "first verification ID = first encrypted data", then the first verification result is "passed", confirming that the control module has not been tampered with (the software has not been stolen) and is a factory-configured security module.

[0070] Another example is when the target identity data is the second identity data, the target encrypted data is the second encrypted data, and the target verification data is the second verification ID. If the three satisfy "second verification ID = second encrypted data", then the second verification result is "passed", confirming that the driver module and the control module are compatible products of the same model and there is no issue of mixed specifications.

[0071] S303, if the target verification data is different from the target encrypted data corresponding to the target identity data, the target verification result indicates that the verification failed; wherein, when the target identity data is the first identity data, the target encrypted data is recorded as the first encrypted data; when the target identity data is the second identity data, the target encrypted data is recorded as the second encrypted data.

[0072] In this embodiment, after the control module extracts the target identity data, it calls a pre-prepared encryption method to generate target verification data. Through precise comparison logic such as bit-by-bit comparison and hash value verification, it confirms whether the two sets of data are completely consistent. If there is any difference in any bit of data or a mismatch in hash value, it is determined to be "different" and the verification fails, thus avoiding the risk of misjudgment.

[0073] For example, the target identity data is the first identity data, the target encrypted data is the first encrypted data, and the target verification data is the first verification ID. If the three satisfy "first verification ID ≠ first encrypted data", then the first verification result is "failed". The underlying reason is that the device model of the control module is inconsistent with the factory configuration (the software has been stolen or the module has been replaced with another model), which means it is an illegal module.

[0074] Two examples illustrate this: the target identity data is the second identity data, the target encrypted data is the second encrypted data, and the target verification data is the second verification ID. If the three satisfy the condition that "the second verification ID ≠ the second encrypted data," then the second verification result is "failed." The core reason is that the driver module and the control module are not compatible products of the same device model, resulting in a mismatch of specifications.

[0075] The above method determines the verification result by directly comparing the target verification data with the target encrypted data. The logic is simple and efficient, and it can quickly verify whether the modules are of the same model and have not been tampered with. This not only eliminates the risk of mixing modules of different specifications and software theft from the source, ensuring stable product performance, but also eliminates the need for complicated verification processes, adapts to the scenario of quick module replacement, and improves ease of use.

[0076] S105, determine whether the first control module and the first drive module are matched based on the first verification result and the second verification result, and obtain the matching result.

[0077] In this embodiment of the application, by integrating the first verification result (the legality verification result of the control module itself) and the second verification result (the compatibility verification result between the drive module and the control module), it is comprehensively determined whether the first control module and the first drive module are compatible modules of the same device model, and finally outputs a matching result of "match" or "not match".

[0078] In one embodiment, see Figure 5 This is a schematic diagram of the process for obtaining matching results provided in an embodiment of this application, such as... Figure 5 As shown, step S105 includes: S401, if both the first verification result and the second verification result are successful, the matching result indicates that the first control module and the first drive module are matched.

[0079] In this embodiment, the first verification result is obtained by the control module after verifying its own first identification data (first identity data + first encrypted data). Only a "pass" result indicates that the control module is a factory-configured security module (not fraudulently used, and the model is consistent with the factory specifications). The second verification result is obtained by the control module after verifying the driver module's second identification data (second identity data + second encrypted data). Only a "pass" result indicates that the driver module and control module are compatible products of the same model. Through the comprehensive judgment of the dual verification results, a dual guarantee of "self-legitimacy + mutual compatibility" is formed.

[0080] If both the first and second verification results are "passed," the matching result is "matched." This indicates that the first control module is a factory-encrypted security module (the software has not been stolen and the model is compliant), and the first driver module and the first control module are compatible modules for the same device model, with no specification mismatch issues, meeting the hardware compatibility requirements for normal device operation.

[0081] S402, if the first verification result fails, the matching result indicates that the first control module and the first drive module are not compatible.

[0082] In this embodiment, the first control module performs its own verification according to a preset process. If it detects missing data, inconsistencies between the verification ID and the encrypted data, it immediately triggers the "first verification failed" determination and initiates the process termination mechanism. It no longer sends data read requests to the second storage unit of the first driving module and directly skips the verification process of the second identifier data.

[0083] Since the control module is the core control unit of the entire variable frequency drive unit, its own legitimacy is the basis for drive module verification. If the control module itself is illegal, even if the drive module is compliant, the safe operation of the equipment cannot be guaranteed. Therefore, there is no need to continue verifying the second identification data, and the process is terminated directly to avoid invalid verification. When the first verification fails, regardless of whether the drive module is a matching model, a "mismatch" result is directly output, blocking the possibility of an illegal control module operating with any drive module from the source.

[0084] S403, if the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, then the matching result indicates that the first control module and the first drive module do not match.

[0085] In this embodiment, the first verification result demonstrates that the first control module itself is legal and compliant, has stored complete first identity data (identification ID generated by a random number of ≥32 bits) and first encrypted data (generated at the factory according to the device model's dedicated encryption method), and the first verification ID generated in real time is consistent with the pre-stored encrypted data, proving that the control module has not been stolen, the model is consistent with the factory configuration, and it is a secure module. The second verification result failing means that the first driver module has a compatibility defect, which may include not storing complete second identity data and second encrypted data (not encrypted at the factory), the second verification ID generated by the control module for encrypting the second identity data being inconsistent with the second encrypted data pre-stored by the driver module (the driver module is a different model or the specifications are incompatible), etc. In essence, the driver module and the control module are not compatible products of the same device model.

[0086] While a valid control module is fundamental to equipment operation, the compatibility of the drive module with the control module, as a core component in high-voltage rectification and inversion, directly determines whether the equipment can achieve its designed performance. Therefore, even if the control module is valid, an incompatibility check is still necessary if the drive module is not compatible to avoid risks arising from module misuse.

[0087] The above method adopts the judgment logic of "control first, drive later, and match only if both passes". If the first verification fails, the process is terminated. This not only improves the verification efficiency and reduces invalid calculations, but also confirms the matching requirement by passing both verifications. This prevents the mixing of modules of different specifications or abnormal modules, avoids performance problems caused by software theft and module incompatibility, and ensures the compatibility of the matching module. This ensures that the product is stable and meets the standards, and requires no complicated operation, allowing for flexible replacement of on-site scenarios.

[0088] In one embodiment, see [link to embodiment]. Figure 6 This is a flowchart illustrating the error warning process provided in an embodiment of this application, such as... Figure 6 As shown, the method also includes: S501, if the matching result indicates that the first control module and the first drive module are matched, then the frequency converter drive device is started.

[0089] In this embodiment, the frequency converter drive is only allowed to start when the matching result between the first control module and the first drive module is "matched" (i.e., both the first verification result and the second verification result pass). The triggering of the start command does not require manual intervention and relies entirely on the judgment logic built into the control module to ensure that the equipment starts without safety hazards or compatibility risks, avoiding performance failures or equipment malfunctions caused by module abnormalities.

[0090] Specifically, when the matching result is "matched", the first control module sends a start-up permission signal to the execution unit of the frequency converter drive device, and the equipment starts according to the preset logic: the control module loads the software algorithm corresponding to the equipment model, and the drive module starts the high-voltage rectification input and inverter output functions. The two work together to ensure that the equipment is adapted to the functional requirements of target scenarios such as textiles, fans, and building water supply, and achieves the expected performance indicators. During the start-up process, the control module continuously monitors the operating status of the two modules, but no longer performs the encryption identification verification repeatedly to avoid affecting the operating efficiency. The protection mechanism is only triggered when an abnormal operating signal is detected.

[0091] S502, if the matching result indicates that the first control module and the first drive module are not compatible, a fault warning is issued and the frequency converter is prohibited from starting; wherein, the fault warning is used to prompt the user to replace the unverified first control module or first drive module with a second control module or second drive module of the same model as the frequency converter.

[0092] In this embodiment, the control module pre-stores the device model and corresponding fault reminder rules. When a "mismatch" is determined, targeted fault information is generated based on the specific circumstances of the first and second verification results (such as "control module is illegal, please replace with the same model control module" or "drive module is incompatible, please replace with the same model drive module"). The fault reminder is triggered through the device's reserved output interface (such as indicator light, communication port, local display screen), prohibiting the start signal from directly acting on the execution unit of the frequency converter drive device, ensuring that the instruction cannot be bypassed.

[0093] For example, (first verification failed): The fault message reads "The first control module failed verification. Please replace it with a second control module that matches the device model." At the same time, the device is prevented from starting, guiding the user to check the legality of the control module. Another example (first verification passed, second verification failed): The fault message reads "First drive module failed verification, please replace with second drive module that matches the device model", and the device is prevented from starting, clearly pointing to a problem with the compatibility of the drive module.

[0094] The above method, through closed-loop control of "starting upon matching and fault warning + prohibiting startup for mismatch", ensures that only matching modules of the same model can drive the device to operate, blocking the performance failure and security risks caused by mixing modules of different specifications and software theft from the terminal. It can also accurately prompt users to replace the corresponding modules, reducing troubleshooting and maintenance costs. At the same time, it does not require complicated operations, ensuring the safety, stability and convenience of device use.

[0095] In one implementation, see Figure 7 This is a flowchart illustrating the process of replacing the supporting module provided in an embodiment of this application, as shown below. Figure 7As shown, after the user replaces the unverified first control module or first drive module with a second control module or second drive module of the same model as the frequency converter, the method further includes: S601, read the third identification data in the third storage unit; wherein, the third storage unit is a storage unit pre-integrated in the second control module; the third identification data is the third identity data of the second control module pre-set and the third encrypted data corresponding to the third identity data.

[0096] In this embodiment, after the user replaces the unverified first control module with a second control module of the same model as the frequency converter drive device, the user initiates the legality verification preparation for the new control module: As a compliant replacement module of the same model, the second control module has a third storage unit pre-integrated for storing core identification data. This unit pre-stores two sets of key data: third identity data (i.e., the identification ID of the second control module, generated by at least 32 random numbers, uniquely identifying the replacement control module) and third encrypted data (i.e., the encrypted ID of the second control module, obtained by encrypting the third identity data using a dedicated encryption method corresponding to the model of the frequency converter drive device).

[0097] After the variable frequency drive unit is powered on again, the newly connected second control module first reads the two sets of identification data pre-stored in its integrated third storage unit. This lays the data foundation for subsequent verification of its own legitimacy and compatibility with the drive module, ensuring that the replaced module can still complete compliance verification through the original encryption identification logic.

[0098] S602, verify the third identification data to obtain the third verification result.

[0099] In this embodiment, after the user replaces the unverified first control module with a second control module of the same model as the frequency converter drive device, the encryption identification process enters the legitimacy verification stage of the second control module: After the second control module reads the third identification data (including the third identity data <the identification ID of the second control module, generated by a random number of ≥32 bits> and the third encryption data <the encryption ID generated by the device model-specific encryption method>) pre-stored in its third storage unit, it will initiate the verification action.

[0100] First, it checks whether the third identity data and the third encrypted data are complete. If they are missing, the third verification result is directly determined to be unsuccessful. If the data is complete, the second control module will call the dedicated encryption algorithm pre-installed on the device and corresponding to the device model to re-encrypt the third identity data and generate a third verification ID. Then, the third verification ID is accurately compared with the third encrypted data, and finally, the third verification result is output as "verification passed" (if they match, it means that the second control module is legitimate and the software has not been stolen) or "verification failed" (if they do not match, it means that the second control module is illegal). This lays the foundation for subsequent compatibility verification with the driver module.

[0101] S603, read the fourth identification data from the fourth storage unit; wherein, the fourth storage unit is a storage unit pre-integrated into the second driver module; the fourth identification data is the fourth identity data of the second driver module pre-set and the fourth encrypted data corresponding to the fourth identity data.

[0102] In this embodiment, after the user replaces the unverified first drive module with a second drive module of the same model as the frequency converter drive device, the user initiates the compatibility verification preparation for the new drive module: The second drive module, as a compliant replacement module of the same model, has a pre-integrated fourth storage unit for storing core identification data. This unit pre-stores two sets of key data: fourth identity data (i.e., the identification ID of the second drive module, generated by at least 32 random numbers, uniquely identifying the replacement drive module) and fourth encrypted data (i.e., the encrypted ID of the second drive module, obtained by encrypting the fourth identity data using a dedicated encryption method corresponding to the model of the frequency converter drive device). The core action of this step is that after the control module completes its own legitimacy verification (if the control module has been replaced, the third verification result is passed; otherwise, the original first verification result is passed), it reads these two sets of identification data from the fourth storage unit in the second drive module through a preset internal communication link. This lays the data foundation for the subsequent generation of the fourth verification ID and the conduct of matching comparisons, ensuring that the replaced drive module can complete compliance verification with the control module through the original encrypted identification logic.

[0103] S604, the fourth identification data is verified to obtain the fourth verification result.

[0104] In this embodiment, after the user replaces the unverified first drive module with a second drive module of the same model as the frequency converter drive device, the encryption identification process enters the compatibility verification stage of the second drive module: After the control module completes its own legitimacy verification (if the control module is not replaced, the first verification result is passed; if the control module is replaced, the third verification result is passed) and reads the fourth identification data (including the fourth identity data <the identification ID of the second drive module, generated by a random number of ≥32 bits> and the fourth encryption data <the encryption ID generated by the dedicated encryption method according to the device model>) in the fourth storage unit of the second drive module, the verification action is initiated.

[0105] First, it checks whether the fourth identity data and the fourth encrypted data are complete. If they are missing, the fourth verification result is directly determined to be unsuccessful. If the data is complete, the control module will call the dedicated encryption algorithm pre-installed on the device and corresponding to the device model to re-encrypt the fourth identity data and generate the fourth verification ID. Then, the fourth verification ID is accurately compared with the fourth encrypted data, and finally, the fourth verification result is output as either "verification passed" (if they match, it means that the second drive module and the control module are compatible) or "verification failed" (if they do not match, it means that the second drive module is not a compatible module). This provides a basis for subsequent determination of whether the control module and the second drive module are compatible and whether the frequency converter drive device is allowed to start.

[0106] S605, determine whether the first control module and the first drive module are matched based on the third verification result and the fourth verification result, and obtain the matching result.

[0107] In this embodiment, after the user completes the module replacement (replacing only the control module with the second control module, only the driver module with the second driver module, or both), the encryption identification process enters the final matching determination stage: The replacement module must be judged comprehensively based on the verification results of the corresponding modules (if the control module is replaced, refer to the third verification result; if the drive module is replaced, refer to the fourth verification result; for modules that are not replaced, refer to the original first or second verification result). The core principle is "matching means both verifications pass"—only if the verification result corresponding to the control module (original first verification result or new third verification result) passes, and the verification result corresponding to the drive module (original second verification result or new fourth verification result) also passes, is the replacement control module and drive module considered to be matched. If the verification result corresponding to either module fails, the two are considered to be mismatched, and this matching result will directly determine whether the frequency converter drive device is allowed to start.

[0108] In the above method, if the matching module is incompatible, it is replaced with a module of the same model, and then a complete secondary verification is performed. This ensures that the replaced second control module and second drive module are consistent with the model of the frequency converter and are compliant, avoiding the problem of module misuse and software theft after replacement. It also eliminates the need for complicated unbinding or network operations, adapts to the scenario of rapid on-site maintenance, ensures that the device can still stably achieve the design performance indicators after the module is replaced, and improves the flexibility and reliability of use and maintenance.

[0109] See Figure 8 This is a flowchart illustrating the overall process of factory encryption for the variable frequency drive device provided in this application embodiment, such as... Figure 8 As shown, specifically: 1) The host computer can read and write data from the control module and drive module storage units via a wired connection to the frequency converter drive device; 2) The host computer reads the identification ID and encryption ID of the control module. If both exist, no processing is required. If not, at least a 32-bit random number is generated as the identification ID of the control module. The identification ID is then encrypted using the dedicated encryption method corresponding to the device model to obtain the encryption ID. Finally, the identification ID and encryption ID are written to the control module storage unit. 3) The host computer reads the identification ID and encryption ID of the driver module. If both exist, no processing is required. If not, at least a 32-bit random number is generated as the identification ID of the driver module. The identification ID is then encrypted using the dedicated encryption method corresponding to the device model to obtain the encryption ID. Finally, the identification ID and encryption ID are written to the driver module storage unit to complete the factory encryption.

[0110] See Figure 9 This is a flowchart illustrating the overall process of generating the identification ID and encrypted ID by the control module at the time of shipment, as provided in the embodiments of this application. Figure 9 As shown, specifically: 1) The host computer is connected to the frequency converter via a wired connection and has the authority to read and write data in the control module's storage unit; 2) The host computer reads the identification ID and encryption ID from the storage unit of the control module; 3) Determine whether the control module has both an identification ID and an encrypted ID. If both are present (i.e., the old machine), no further processing is required. 4) If the control module lacks an identification ID or encrypted ID, the host computer will generate at least a 32-bit random number and use it as the identification ID of the control module. 5) The host computer encrypts the generated control module identification ID using the corresponding dedicated encryption method according to the equipment model of the frequency converter drive device, and obtains the corresponding encrypted ID; 6) The host computer writes the generated control module identification ID and encrypted ID into the storage unit of the control module, completing the generation process of the control module identification ID and encrypted ID.

[0111] See Figure 10 This is a flowchart illustrating the overall process of generating the driver module identification ID and encrypted ID at the factory, as provided in the embodiments of this application. Figure 10 As shown, specifically: 1) The host computer is connected to the frequency converter via a wired connection and has the authority to read and write data in the drive module's storage unit; 2) The host computer reads the identification ID and encryption ID from the driver module's storage unit; 3) Determine whether the driver module has both an identification ID and an encrypted ID. If both are present (i.e., on older machines), no further processing is required. 4) If the driver module lacks an identification ID or encrypted ID, the host computer will generate at least a 32-bit random number and use it as the identification ID of the driver module. 5) The host computer encrypts the generated drive module identification ID using the corresponding dedicated encryption method according to the equipment model of the frequency converter drive device, and obtains the corresponding encrypted ID; 6) The host computer writes the generated driver module identification ID and encrypted ID into the driver module's storage unit, completing the generation process of the driver module identification ID and encrypted ID.

[0112] See Figure 11 This is a flowchart illustrating the overall process of power-on identification of the variable frequency drive device provided in this application embodiment. Figure 11 As shown, specifically: 1) When the frequency converter is powered on, the control module first reads the identification ID and encryption ID from its own storage unit; 2) The control module determines whether it has both an identification ID and an encryption ID. If either of them is missing, it is determined to be an insecure device that has not been encrypted at the factory. The control module reports a fault and prevents the device from starting. 3) If both the identification ID and the encrypted ID exist, the control module will perform encryption calculation on its own identification ID according to the dedicated encryption method corresponding to its own device model to obtain the verification ID; 4) The control module compares the verification ID with its own pre-stored encrypted ID. If they do not match, it determines that the software has been stolen, reports a fault, and prevents the device from starting. 5) If the verification ID matches the encryption ID, the control module is confirmed to be a security module. Subsequently, the control module reads the identification ID and encryption ID from the driver module's storage unit. 6) The control module determines whether the drive module has both an identification ID and an encryption ID. If either is missing, it is determined to be a non-secure device, a fault is reported, and the device is prevented from starting. 7) If both the identification ID and encryption ID of the driver module exist, the control module will perform encryption calculation on the identification ID of the driver module according to the dedicated encryption method corresponding to its own device model to obtain the verification ID; 8) The control module compares the verification ID with the encrypted ID pre-stored in the driver module. If they do not match, it determines that they are different models of incompatible modules, reports a fault, and prevents the device from starting. 9) If the verification ID matches the encryption ID, it confirms that the control module and the drive module are the same model and are compatible. The control module will then be released from its operating restrictions, and the frequency converter drive will start and be used normally.

[0113] See Figure 12 This is a flowchart illustrating the overall process of driver module identification provided in the embodiments of this application, as follows: Figure 12 As shown, specifically: 1) After the control module completes its own legitimacy verification (the identification ID and the encrypted ID are complete and consistent), it starts the driver module's identification process; 2) The control module reads the identification ID and encryption ID from the driver module's storage unit; 3) The control module determines whether the drive module has both an identification ID and an encryption ID. If either is missing, it is determined to be a non-secure device that has not been encrypted at the factory, and a fault is reported and the frequency converter drive device is prohibited from starting. 4) If both the identification ID and encryption ID of the driver module exist, the control module performs encryption calculation on the identification ID of the driver module according to the dedicated encryption method corresponding to its own device model to obtain the verification ID of the driver module. 5) The control module compares the verification ID with the encrypted ID pre-stored in the driver module. If they do not match, it determines that the driver module and the control module are different models and are not compatible, reports a fault, and prevents the device from starting. 6) If the verification ID matches the encryption ID, it confirms that the drive module and the control module are the same model and are compatible. The control module then removes the operating restrictions on the device, allowing the frequency converter drive device to start and run normally.

[0114] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0115] Corresponding to the frequency conversion drive-based encryption identification method in the above embodiments, Figure 13 This is a structural block diagram of the variable frequency drive device provided in the embodiments of this application. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0116] Reference Figure 13 The device includes: The first identification data reading module 131 is used to read the first identification data in the first storage unit; wherein, the first storage unit is a storage unit pre-integrated in the first control module; the first identification data is the first identity data of the first control module and the first encrypted data corresponding to the first identity data pre-set; The first identifier data verification module 132 is used to verify the first identifier data and obtain a first verification result; The second identification data reading module 133 is used to read the second identification data in the second storage unit after the first verification result indicates that the verification is successful; wherein, the second storage unit is a storage unit pre-integrated in the first driver module; the second identification data is the second identity data of the first driver module and the second encrypted data corresponding to the second identity data; The second identification data verification module 134 is used to verify the second identification data and obtain a second verification result; The matching determination module 135 is used to determine whether the first control module and the first drive module are matched based on the first verification result and the second verification result, and to obtain the matching result.

[0117] Optionally, the first identifier data verification module 132 or the second identifier data reading module 133 is further used for: The target identity data corresponding to the target identification data is encrypted and calculated to obtain the target verification data; The target identity data is verified based on the target verification data to obtain a target verification result; wherein, when the target identification data is the first identification data, the target identity data is recorded as the first identity data and the target verification result is recorded as the first verification result; when the target identification data is the second identification data, the target identity data is recorded as the second identity data and the target verification result is recorded as the second verification result.

[0118] Optionally, the first identifier data verification module 132 or the second identifier data reading module 133 is further used for: Extract the device model of the variable frequency drive unit; The target identity data is encrypted and calculated according to the encryption method corresponding to the device model to obtain the target verification data.

[0119] Optionally, the first identifier data verification module 132 or the second identifier data reading module 133 is further used for: Compare the target verification data with the target encrypted data corresponding to the target identity data; If the target verification data is the same as the target encrypted data corresponding to the target identity data, then the target verification result indicates that the verification is successful; If the target verification data is different from the target encrypted data corresponding to the target identity data, the target verification result indicates that the verification failed; wherein, when the target identity data is first identity data, the target encrypted data is recorded as the first encrypted data; when the target identity data is second identity data, the target encrypted data is recorded as the second encrypted data.

[0120] Optionally, the matching determination module 135 is also used for: If both the first verification result and the second verification result are successful, then the matching result indicates that the first control module and the first drive module are matched. If the first verification result fails, the verification of the second identifier data is stopped, and the matching result indicates that the first control module and the first drive module are not compatible.

[0121] If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, then the matching result indicates that the first control module and the first drive module are not compatible.

[0122] Optionally, the matching determination module 135 is also used for: If the matching result indicates that the first control module and the first drive module are matched, then the frequency converter drive device is started; If the matching result indicates that the first control module and the first drive module are not compatible, a fault warning is issued and the variable frequency drive device is prohibited from starting; wherein, the fault warning is used to prompt the user to replace the unverified first control module or first drive module with a second control module or second drive module of the same model as the variable frequency drive device.

[0123] Optionally, the matching determination module 135 is also used for: Read the third identification data from the third storage unit; wherein, the third storage unit is a storage unit pre-integrated into the second control module; the third identification data is the third identity data of the second control module pre-set and the third encrypted data corresponding to the third identity data; The third identification data is verified to obtain a third verification result; Read the fourth identification data from the fourth storage unit; wherein, the fourth storage unit is a storage unit pre-integrated into the second driver module; the fourth identification data is the fourth identity data of the second driver module pre-set and the fourth encrypted data corresponding to the fourth identity data; The fourth identification data is verified to obtain the fourth verification result; Based on the third verification result and the fourth verification result, it is determined whether the first control module and the first drive module are matched, and a matching result is obtained.

[0124] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0125] in addition, Figure 13 The variable frequency drive device shown can be a software unit, hardware unit, or a combination of software and hardware built into existing terminal equipment, or it can be integrated into the terminal equipment as an independent component, or it can exist as an independent terminal equipment.

[0126] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0127] Figure 14 This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application. For example... Figure 14 As shown, the terminal device 14 of this embodiment includes: at least one processor 140 ( Figure 14 (Only one is shown in the image) a processor, a memory 141, and a computer program 142 stored in the memory 141 and executable on at least one processor 140. When the processor 140 executes the computer program 142, it implements the steps in any of the above embodiments of the frequency conversion drive-based encryption identification method.

[0128] The terminal device can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. This terminal device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that... Figure 14This is merely an example of terminal device 14 and does not constitute a limitation on terminal device 14. It may include more or fewer components than shown, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0129] The processor 140 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0130] In some embodiments, memory 141 may be an internal storage unit of terminal device 14, such as a hard disk or memory of terminal device 14. In other embodiments, memory 141 may be an external storage device of terminal device 14, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc., equipped on terminal device 14. Furthermore, memory 141 may include both internal storage units and external storage devices of terminal device 14. Memory 141 is used to store operating system, application programs, bootloader, data, and other programs, such as program code of computer programs. Memory 141 can also be used to temporarily store data that has been output or will be output.

[0131] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the above-described method embodiments.

[0132] This application provides a computer program product that, when run on a terminal device, enables the terminal device to implement the steps described in the various method embodiments above.

[0133] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code to a device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0134] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0135] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0136] In the embodiments provided in this application, it should be understood that the disclosed apparatus / terminal devices and methods can be implemented in other ways. For example, the apparatus / terminal device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0137] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0138] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for encrypted identification based on variable frequency drive, characterized in that, A first control module is applied in a variable frequency drive device, the variable frequency drive device further comprising a first drive module; the method includes: Read the first identification data from the first storage unit; wherein, the first storage unit is a storage unit pre-integrated into the first control module; the first identification data includes the first identity data of the first control module pre-set and the first encrypted data corresponding to the first identity data; The first identification data is verified to obtain a first verification result; Read the second identification data from the second storage unit; wherein, the second storage unit is a storage unit pre-integrated into the first driver module; the second identification data is the second identity data of the first driver module and the second encrypted data corresponding to the second identity data, which are pre-set; The second identification data is verified to obtain a second verification result; Based on the first verification result and the second verification result, the matching result of the first control module and the first drive module is determined.

2. The encryption identification method based on frequency conversion drive as described in claim 1, characterized in that, The steps to verify the target identifier data and obtain the target verification result include: The target identity data corresponding to the target identification data is encrypted and calculated to obtain the target verification data; The target identity data is verified based on the target verification data to obtain a target verification result; wherein, when the target identification data is the first identification data, the target identity data is recorded as the first identity data and the target verification result is recorded as the first verification result; when the target identification data is the second identification data, the target identity data is recorded as the second identity data and the target verification result is recorded as the second verification result.

3. The encryption identification method based on frequency conversion drive as described in claim 2, characterized in that, The step of encrypting and calculating the target identity data corresponding to the target identifier data to obtain target verification data includes: Extract the device model of the variable frequency drive unit; The target identity data is encrypted and calculated according to the encryption method corresponding to the device model to obtain the target verification data.

4. The encryption identification method based on frequency conversion drive as described in claim 2, characterized in that, The step of verifying the target identity data based on the target verification data to obtain the target verification result includes: Compare the target verification data with the target encrypted data corresponding to the target identity data; If the target verification data is the same as the target encrypted data corresponding to the target identity data, then the target verification result indicates that the verification is successful; If the target verification data is different from the target encrypted data corresponding to the target identity data, the target verification result indicates that the verification failed; wherein, when the target identity data is first identity data, the target encrypted data is recorded as the first encrypted data; when the target identity data is second identity data, the target encrypted data is recorded as the second encrypted data.

5. The encryption identification method based on frequency conversion drive as described in claim 4, characterized in that, The step of determining whether the first control module and the first drive module are matched based on the first verification result and the second verification result, and obtaining the matching result, includes: If both the first verification result and the second verification result are successful, then the matching result indicates that the first control module and the first drive module are matched. If the first verification result fails, the verification of the second identifier data is stopped, and the matching result indicates that the first control module and the first drive module are not compatible. If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, then the matching result indicates that the first control module and the first drive module are not compatible.

6. The encryption identification method based on frequency conversion drive as described in claim 5, characterized in that, The method further includes: If the matching result indicates that the first control module and the first drive module are matched, then the frequency converter drive device is started; If the matching result indicates that the first control module and the first drive module are not compatible, a fault warning is issued and the variable frequency drive device is prohibited from starting; wherein, the fault warning is used to prompt the user to replace the unverified first control module or first drive module with a second control module or second drive module of the same model as the variable frequency drive device.

7. The encryption identification method based on frequency conversion drive as described in claim 6, characterized in that, After the user replaces the unverified first control module or first drive module with a second control module or second drive module of the same model as the frequency converter, the method further includes: Read the third identification data from the third storage unit; wherein, the third storage unit is a storage unit pre-integrated into the second control module; the third identification data is the third identity data of the second control module pre-set and the third encrypted data corresponding to the third identity data; The third identification data is verified to obtain a third verification result; Read the fourth identification data from the fourth storage unit; wherein, the fourth storage unit is a storage unit pre-integrated into the second driver module; the fourth identification data is the fourth identity data of the second driver module pre-set and the fourth encrypted data corresponding to the fourth identity data; The fourth identification data is verified to obtain the fourth verification result; Based on the third verification result and the fourth verification result, it is determined whether the first control module and the first drive module are matched, and a matching result is obtained.

8. An encryption identification device based on frequency conversion drive, characterized in that, include: The first identification data reading module is used to read the first identification data in the first storage unit; wherein, the first storage unit is a storage unit pre-integrated in the first control module; the first identification data is the first identity data of the first control module and the first encrypted data corresponding to the first identity data pre-set; The first identifier data verification module is used to verify the first identifier data and obtain a first verification result; The second identification data reading module is used to read the second identification data in the second storage unit; wherein the second storage unit is a storage unit pre-integrated in the first driver module; the second identification data is the second identity data of the first driver module and the second encrypted data corresponding to the second identity data pre-set. The second identifier data verification module is used to verify the second identifier data and obtain a second verification result; A matching determination module is provided to determine whether the first control module and the first drive module are matched based on the first verification result and the second verification result, and to obtain a matching result.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 7.

Images