Hooke pair modeling method, electronic equipment, storage medium and program product

Abstract

The invention provides a Hooke pair modeling method, electronic equipment, a storage medium and a program product, and relates to the technical field of vehicles. The method comprises the steps that in response to a modeling instruction of a Hooke pair model, input containing parameterized configuration is obtained, and the parameterized configuration contains parameter values used for representing whether phase angle parameters are contained or not and parameter values of the phase angle parameters when the phase angle parameters are contained; according to the parameterized configuration, modeling a first Hooke pair model corresponding to the parameterized configuration, and displaying the first Hooke pair model on a modeling interaction interface; and in response to a detected type switching instruction of the Hooke pair model, modeling a parameterized configuration corresponding second Hooke pair model, and displaying the second Hooke pair model on the modeling interaction interface, the model types of the first Hooke pair model and the second Hooke pair model being different. According to the method and the device, the modeling operation flexibility of the Hooke pair model is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicles, and in particular to a Hookean pair modeling method, an electronic device, a storage medium and a program product. BACKGROUND

[0002] In actual engineering applications, the Hookean pair is a mechanical transmission device for transmitting torque and rotational motion between two non-coaxial shafts, wherein the shaft that inputs the rotational motion is the driving shaft, and the shaft that outputs the rotational motion is the driven shaft. When the installation angle (phase angle ) of the driven shaft yoke relative to the driving shaft yoke is 0 degrees, the instantaneous angular velocity of the driven shaft is not constant, and it periodically changes with the rotation of the driving shaft: in a complete 360-degree rotation, the speed of the driven shaft exceeds the speed of the driving shaft twice and is lower than the speed of the driving shaft twice. The speed ratio formula is: wherein is the angular velocity of the driving shaft, is the angular velocity of the driven shaft, is the rotation angle of the driving shaft, and thus it can be seen that the output rotation speed can be adjusted synchronously by adjusting the phase angle.

[0003] Due to the inherent speed fluctuation characteristics of the Hookean pair, the Hookean pair without a phase angle is usually used in occasions where the motion stability requirement is not high, for example, the transmission shaft connecting the gearbox and the differential of a rear-drive or four-wheel-drive vehicle, industrial equipment such as a rolling mill, a mine machine, a large pump, etc. that pay more attention to torque transmission capacity rather than motion stability at low speed and heavy load, a control mechanism that does not require uniform speed, and is used to transmit angular changes between control rods or pedals. The Hookean pair with a phase angle is commonly used in the transmission shaft of a truck, a jeep or other commercial or off-road vehicles, precise mechanical transmission that requires smooth motion transmission at a large angle, and compensation for installation errors and deformation in long-distance power transmission.

[0004] In order to better analyze and design the Hookean pair, modeling is essential. There are two independent Hookean pair modeling methods in the current mainstream mechanical system dynamics simulation software, namely, a standard Hookean pair model with a fixed angle between the two shafts and without considering the specific phase relationship, and a Hookean pair model with a phase angle that can define an initial phase angle.

[0005] In the current mechanical system dynamics simulation software implementation scheme, the standard Hookean pair and the Hookean pair model with a phase angle are two independent modeling functions. The Hookean pair model with a phase angle needs to generate multiple intermediate reference points as parameters according to the phase angle to determine the modeling posture of the Hookean pair model when created, and its internal constraint equation is more complex; and the standard Hookean pair model does not need additional hard points, and is uniquely and implicitly determined by the initial installation direction, so the user must make a choice in advance when creating.

[0006] If a phase angle needs to be added after selecting a standard hookean submodel, or if a phase angle needs to be deleted after selecting a hookean submodel with a phase angle, it is usually necessary to delete the created type of hookean submodel and reselect another type for creation, and the operation flexibility is poor. SUMMARY

[0007] The present application provides a hookean submodel modeling method, an electronic device, a storage medium and a program product, to improve the operation flexibility.

[0008] In a first aspect, the present application provides a hookean submodel modeling method, comprising:

[0009] In response to a modeling instruction of a hookean submodel, an input containing a parameterized configuration is obtained, the parameterized configuration containing a parameter for representing whether a phase angle parameter is contained, and a parameter value of the phase angle parameter when the phase angle parameter is contained;

[0010] According to the parameterized configuration, a first hookean submodel corresponding to the parameterized configuration is modeled, and the first hookean submodel is displayed on a modeling interactive interface;

[0011] In response to detecting a type switching instruction of the hookean submodel, a second hookean submodel corresponding to the parameterized configuration is modeled, and the second hookean submodel is displayed on the modeling interactive interface, the model type of the first hookean submodel being different from that of the second hookean submodel.

[0012] In a possible implementation, the first hookean submodel is a standard hookean submodel, and the second hookean submodel is a hookean submodel with a phase angle; or, the first hookean submodel is a hookean submodel with a phase angle, and the second hookean submodel is a standard hookean submodel.

[0013] In a possible implementation, in response to detecting a type switching instruction of the hookean submodel, modeling a second hookean submodel corresponding to the parameterized configuration comprises:

[0014] In response to detecting the type switching instruction, the following operations are performed according to the type switching instruction:

[0015] If the type switching instruction indicates switching a standard hookean submodel to a hookean submodel with a phase angle, an intermediate reference point is added in the standard hookean submodel to model the second hookean submodel corresponding to the parameterized configuration;

[0016] If the type switching instruction indicates switching a hookean submodel with a phase angle to a standard hookean submodel, an intermediate reference point is removed in the hookean submodel with a phase angle to model the second hookean submodel corresponding to the parameterized configuration.

[0017] In one possible implementation, the first Hooke's submodel is a Hooke's submodel with a phase angle, or the second Hooke's submodel is a Hooke's submodel with a phase angle. The Hooke's submodeling method further includes:

[0018] When an interactive operation command is received for the Hooke sub-model with phase angle, the pose of the Hooke sub-model with phase angle in the modeling interactive interface is adjusted according to the interactive operation command, and during the adjustment process, the adjusted phase angle of the Hooke sub-model with phase angle is calculated.

[0019] The adjusted phase angle will be synchronously updated in the parameterized configuration of the Hooke sub-model displayed in the modeling interactive interface.

[0020] In one possible implementation, adjusting the display content of the Hooke sub-model with phase angle in the modeling interactive interface according to interactive operation instructions includes:

[0021] Retrieve the operation type and operation parameters from the interactive operation command;

[0022] Based on the operation type and operation parameters, determine the attitude transformation applied to the Hooke pair model with phase angle;

[0023] The pose transformation is applied to the Hooke sub-model with phase angle to update the displayed pose of the Hooke sub-model with phase angle in the modeling interface.

[0024] In one possible implementation, the interactive operation command acts on the axis orientation controller corresponding to the Hooke sub-model with phase angle, and the axis orientation controller is displayed around the Hooke sub-model with phase angle.

[0025] In one possible implementation, before synchronously updating the adjusted phase angle to the parametric configuration of the Hooke sub-model displayed in the modeling interface, the method further includes:

[0026] Determine whether the adjusted phase angle meets the preset mechanical constraint conditions;

[0027] If the mechanical constraints are not met, visual feedback information will be output on the modeling interface. The visual feedback information includes highlighting the Hooke sub-model, displaying warning information, and limiting the movement range of the axis direction controller.

[0028] If the mechanical constraints are met, perform a synchronous update of the parameterized configuration.

[0029] Secondly, this application provides a Hooke sub-modeling apparatus, comprising:

[0030] The acquisition module is used to acquire input containing parameterized configuration in response to the modeling instructions of the Hooke sub-model. The parameterized configuration includes a parameter for characterizing whether a phase angle parameter is included, and the parameter value of the phase angle parameter when it is included.

[0031] The processing module is used to model the first Hooke sub-model corresponding to the parameterized configuration based on the parameterized configuration, and display the first Hooke sub-model on the modeling interactive interface.

[0032] The processing module is also used to respond to the detected Hooke sub-model type switching command, configure the corresponding second Hooke sub-model in the modeling parameterization, and display the second Hooke sub-model in the modeling interaction interface. The model types of the first Hooke sub-model and the second Hooke sub-model are different.

[0033] In one possible implementation, the first Hooke submodel is a standard Hooke submodel, and the second Hooke submodel is a Hooke submodel with a phase angle; or, the first Hooke submodel is a Hooke submodel with a phase angle, and the second Hooke submodel is a standard Hooke submodel.

[0034] In one possible implementation, the processing module is specifically used for:

[0035] Upon detecting a type switching instruction, perform the following operations based on the type switching instruction:

[0036] If the type switching instruction indicates that the standard Hooke sub-model is switched to the Hooke sub-model with phase angle, then an intermediate reference point is added to the standard Hooke sub-model to model the corresponding second Hooke sub-model with parameterized configuration.

[0037] If the type switching instruction indicates that the Hooke sub-model with phase angle is switched to the standard Hooke sub-model, then the intermediate reference point is removed in the Hooke sub-model with phase angle to model the corresponding second Hooke sub-model with parameterized configuration.

[0038] In one possible implementation, the first Hooke's submodel is a Hooke's submodel with a phase angle, or the second Hooke's submodel is a Hooke's submodel with a phase angle, and the processing module is further configured to:

[0039] When an interactive operation command is received for the Hooke sub-model with phase angle, the pose of the Hooke sub-model with phase angle in the modeling interactive interface is adjusted according to the interactive operation command, and during the adjustment process, the adjusted phase angle of the Hooke sub-model with phase angle is calculated.

[0040] The adjusted phase angle will be synchronously updated in the parameterized configuration of the Hooke sub-model displayed in the modeling interactive interface.

[0041] In one possible implementation, the processing module is specifically used for:

[0042] Retrieve the operation type and operation parameters from the interactive operation command;

[0043] Based on the operation type and operation parameters, determine the attitude transformation applied to the Hooke pair model with phase angle;

[0044] The pose transformation is applied to the Hooke sub-model with phase angle to update the displayed pose of the Hooke sub-model with phase angle in the modeling interface.

[0045] In one possible implementation, the interactive operation command acts on the axis orientation controller corresponding to the Hooke sub-model with phase angle, and the axis orientation controller is displayed around the Hooke sub-model with phase angle.

[0046] In one possible implementation, the processing module is further configured to:

[0047] Determine whether the adjusted phase angle meets the preset mechanical constraint conditions;

[0048] If the mechanical constraints are not met, visual feedback information will be output on the modeling interface. The visual feedback information includes highlighting the Hooke sub-model, displaying warning information, and limiting the movement range of the axis direction controller.

[0049] If the mechanical constraints are met, perform a synchronous update of the parameterized configuration.

[0050] Thirdly, this application provides an electronic device, including: a memory and a processor;

[0051] The memory stores instructions that the computer executes;

[0052] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0053] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0054] Fifthly, this application provides a computer program product, including a computer program that, when executed, implements the first aspect and / or various possible implementations of the first aspect.

[0055] Sixthly, this application provides a vehicle including a vehicle body and a vehicle transmission system configured according to the first aspect and / or various possible embodiments of the first aspect.

[0056] This application provides a Hooke pair modeling method, electronic device, storage medium, and program product, relating to the field of vehicle technology. The method includes: in response to a modeling instruction for a Hooke pair model, acquiring input containing a parametric configuration, the parametric configuration including whether a phase angle parameter is included, and the parameter value of the phase angle parameter when it is included; modeling a first Hooke pair model corresponding to the parametric configuration according to the parametric configuration, and displaying the first Hooke pair model on a modeling interactive interface; in response to a detected Hooke pair model type switching instruction, modeling a second Hooke pair model corresponding to the parametric configuration, and displaying the second Hooke pair model on a modeling interactive interface, wherein the first Hooke pair model and the second Hooke pair model have different model types. This application triggers the Hooke sub-modeling process through user-input modeling commands, models the first Hooke sub-model corresponding to the parameterized configuration, and models the second Hooke sub-model corresponding to the parameterized configuration upon detecting a Hooke sub-model type switching command. By replacing the original independent modeling commands with integrated modeling functions, users can directly switch the modeling mode of the Hooke sub-model with a single selection without manually deleting and recreating the Hooke sub-model, thereby significantly improving the flexibility and efficiency of Hooke sub-model modeling operations. Attached Figure Description

[0057] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0058] Figure 1 A flowchart illustrating the Hooke pair modeling method provided in this application embodiment. Figure One ;

[0059] Figure 2 A schematic diagram illustrating the Hooke sub-model switching process provided in an embodiment of this application;

[0060] Figure 3 A flowchart illustrating the Hooke pair modeling method provided in this application embodiment. Figure Two ;

[0061] Figure 4 The content displayed in the data display window provided in the embodiments of this application;

[0062] Figure 5 The process of generating the Hooke sub-model provided in the embodiments of this application;

[0063] Figure 6 This is a schematic diagram of the Hooke sub-model when the current phase angle is 0, provided in an embodiment of this application.

[0064] Figure 7 This is a schematic diagram of the Hooke pair model when the current phase angle is not 0, provided in an embodiment of this application.

[0065] Figure 8 This is a schematic diagram of the structure of the Hooke sub-modeling device provided in the embodiments of this application;

[0066] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0067] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0068] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0069] The existing Hooke sub-model editing function with phase angle adjusts the size by manually inputting values, which is a one-way and numerical method. If the values ​​are not determined, a lot of time is required for debugging.

[0070] As can be seen from the existing Hooke sub-modeling schemes, the creation and editing methods of Hooke sub-models are not flexible and convenient enough, and lack intuitive geometric interaction. The reason for this problem is that the two Hooke sub-models are created independently and without interference, and the interaction is one-way, which can only change the modeling display by modifying the phase angle parameter.

[0071] Furthermore, in mechanical system dynamics simulation software, adjusting the phase angle of the Hooke pair model is no longer a simple "error compensation," but rather a proactive design exploration, performance optimization, and system analysis. For example, it can compensate for vibrations caused by complex effects such as flexible bodies, improve model fidelity, and obtain more realistic results; reproduce problems, verify solutions, shorten troubleshooting time, and reduce trial-and-error costs; and seek system optimization with optimal global performance rather than local mathematical perfection, achieving a balance between lightweight, low cost, and high reliability.

[0072] Based on this, this application provides a Hooke sub-modeling method, which triggers the Hooke sub-modeling process through user-input modeling commands, models a first Hooke sub-model corresponding to the parameterized configuration according to the parameterized configuration, and models a second Hooke sub-model corresponding to the parameterized configuration when a Hooke sub-model type switching command is detected. This integrated modeling function replaces the original independent modeling commands, thereby enabling users to directly switch the modeling mode of the Hooke sub-model with a single selection without manually deleting and recreating the Hooke sub-model.

[0073] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0074] The execution subject of the Hooke sub-modeling method provided in this application embodiment can be a computing device such as a server or server cluster. The server can be a mobile phone, computer, tablet, or other device. This application embodiment does not impose any particular restrictions on the implementation method of the execution subject.

[0075] Figure 1 A flowchart illustrating the Hooke pair modeling method provided in this application embodiment. Figure One ,like Figure 1 As shown, the method includes:

[0076] S101. In response to the modeling instructions of the Hooke sub-model, obtain input containing a parameterized configuration, which includes a parameter for characterizing whether a phase angle parameter is included, and the parameter value of the phase angle parameter when it is included.

[0077] In this step, it can be understood that when a modeling instruction for the Hooke sub-model is detected, the computing device acquires input containing a parameterized configuration. This configuration includes information on whether a phase angle parameter is included, and if so, its value. This setting allows for flexible specification of whether to consider the phase angle parameter in the Hooke sub-model and its specific value, based on actual simulation requirements and analysis accuracy requirements, before its creation. This enables a high degree of customization from the initial Hooke sub-model modeling stage, avoiding tedious manual modifications after model creation, thus significantly improving the efficiency and accuracy of Hooke sub-model modeling.

[0078] Among them, the modeling command refers to the operation command initiated by the user in the simulation software to create a Hooke pair model. For example, the user clicking the "Create Hooke Pair" button on the modeling interaction interface in the mechanical system dynamics simulation software is a modeling command.

[0079] Furthermore, the input for the aforementioned parameterized configuration is not limited to direct input through the user modeling interface. It can also be obtained by loading templates from a preset model library, reading configuration information from a project database, or automatically recommending parameters based on the context of the current modeling and simulation environment.

[0080] S102. Based on the parameterized configuration, model the first Hooke sub-model corresponding to the parameterized configuration, and display the first Hooke sub-model on the modeling interactive interface.

[0081] Since the first Hooke sub-model is generated directly based on the parametric configuration specified in S101, this ensures that the created initial model accurately reflects the intentions and simulation requirements of the Hooke sub-model creator. Simultaneously, the real-time display of the created model in the modeling interface provides immediate visual feedback to the Hooke sub-model creator, enabling them to quickly confirm the model's correctness and conduct preliminary verification. This further enhances the intuitiveness and user experience of Hooke sub-model modeling.

[0082] S103. In response to the detected Hooke sub-model type switching command, the corresponding second Hooke sub-model is configured in the modeling parameterization, and the second Hooke sub-model is displayed in the modeling interaction interface. The model types of the first Hooke sub-model and the second Hooke sub-model are different.

[0083] In step S103, in response to the detected Hooke sub-model type switching command, the computing device configures the corresponding second Hooke sub-model using modeling parameters and displays it on the modeling interface. The first and second Hooke sub-models have different model types. This step allows the Hooke sub-model creator to switch between different types of Hooke sub-models after creation without having to re-enter or adjust parameters.

[0084] For example, a user might initially create a simplified first Hooke's pair model, and then find that a more refined dynamic analysis is needed. At this point, they can use a type switching command to switch the model to a second Hooke's pair model that includes more complex physical properties. This dynamic switching capability greatly enhances the flexibility and adaptability of modeling, allowing users to select the most suitable Hooke's pair model type within a unified modeling environment, based on different analysis stages and accuracy requirements.

[0085] Furthermore, in some examples, the first Hooke submodel is a standard Hooke submodel, and the second Hooke submodel is a Hooke submodel with a phase angle; or, the first Hooke submodel is a Hooke submodel with a phase angle, and the second Hooke submodel is a standard Hooke submodel. The standard Hooke submodel is a Hooke submodel without a phase angle. Figure 2 This is a schematic diagram illustrating the Hooke sub-model switching process provided in an embodiment of this application.Figure 2 As shown, the Hooke's sub-model with phase angle and the standard Hooke's sub-model can be converted into each other.

[0086] Furthermore, the triggering methods for the Hooke sub-model type switching command can be diversified. For example, users can select different model type options in the model's property panel, select via drop-down menus, use specific shortcut key combinations, or trigger automatic switching based on preset conditions in the simulation process.

[0087] Therefore, the embodiments of this application avoid the trouble of remodeling when different model types are needed, significantly reduce the complexity and repetitiveness of modeling work, and thus greatly improve the efficiency of simulation modeling and user satisfaction.

[0088] This application embodiment triggers the Hooke sub-modeling process through user-input modeling commands. It models the first Hooke sub-model corresponding to the parameterized configuration based on the parameterized configuration, and models the second Hooke sub-model corresponding to the parameterized configuration upon detecting a Hooke sub-model type switching command. By replacing the original independent modeling commands with integrated modeling functions, users can directly switch the modeling mode of the Hooke sub-model with a single selection without manually deleting and recreating the Hooke sub-model, thereby significantly improving the flexibility and efficiency of Hooke sub-model modeling operations.

[0089] In some examples, S103 describes a response to a type switching instruction for the Hooke sub-model, modeling a parameterized configuration of the corresponding second Hooke sub-model, including: in response to a type switching instruction, performing the following operations based on the type switching instruction: if the type switching instruction indicates switching the standard Hooke sub-model to a Hooke sub-model with phase angles, then adding intermediate reference points in the standard Hooke sub-model to model the parameterized configuration of the corresponding second Hooke sub-model; if the type switching instruction indicates switching the Hooke sub-model with phase angles to the standard Hooke sub-model, then removing intermediate reference points in the Hooke sub-model with phase angles to model the parameterized configuration of the corresponding second Hooke sub-model.

[0090] These examples detail how to model the corresponding second Hooke submodel for parameterized configuration. Specifically, when a Hooke submodel type switching instruction is detected, the meaning of the instruction must first be determined. If the instruction indicates switching the standard Hooke submodel to a Hooke submodel with phase angles, an intermediate reference point must be added to the standard Hooke submodel to model the corresponding second Hooke submodel for parameterized configuration. Here, the second Hooke submodel is the Hooke submodel with phase angles.

[0091] The intermediate reference point is not a physical component of the Hooke pair, but a virtual structure whose position or orientation is directly related to the phase angle parameter value set in S101. For example, it might be a virtual center of rotation, whose initial angle relative to the input or output axis is the phase angle. The modeling engine inside the computing device modifies or replaces the original kinematic equations based on this newly added intermediate reference point. The addition of an intermediate reference point can be achieved by dynamically adding a data member specifically representing that reference point. This data member can be a variable representing an angle or coordinate; however, this is only an example.

[0092] Furthermore, if the type switching instruction indicates switching from the Hooke sub-model with phase angles to the standard Hooke sub-model, then intermediate reference points are removed from the Hooke sub-model with phase angles to model the corresponding parametrically configured second Hooke sub-model, which is the standard Hooke sub-model. The purpose of removing intermediate reference points is to eliminate computational nodes and geometric anchors related to the phase angle. The computing device identifies and removes intermediate reference points and their associated mathematical expressions or constraints previously added to handle the phase angle. This restores the Hooke sub-model to its simplified standard form, employing kinematic equations that do not consider the phase angle effect. The removal of intermediate reference points can be achieved by removing previously added data members specifically representing those reference points. The computing device can determine whether the current model contains intermediate reference points by checking the presence of these data members.

[0093] This process involves simplifying the Hooke sub-model from complex to simple. By removing unnecessary computational elements, the computational complexity of the Hooke sub-model is reduced, the simulation speed is improved, and the correctness of the Hooke sub-model in the simplified state is ensured.

[0094] In summary, it can be understood that switching between the standard Hooke's sub-model and the Hooke's sub-model with phase angles by adding or removing intermediate reference points greatly improves the efficiency and consistency of model switching. This incremental modification not only reduces computational resource consumption but also ensures that, apart from phase angle-related characteristics, other inherent parameters and geometric properties of the Hooke's sub-model are preserved during the switching process, thereby guaranteeing data consistency and the continuity of analysis results before and after different types of switching.

[0095] Based on the above embodiments, the first Hooke submodel is a Hooke submodel with a phase angle, or the second Hooke submodel is a Hooke submodel with a phase angle. The Hooke submodeling method further includes: when an interactive operation instruction for the Hooke submodel with a phase angle is obtained, adjusting the posture of the Hooke submodel with a phase angle in the modeling interactive interface according to the interactive operation instruction, and, during the adjustment process, calculating the adjusted phase angle of the Hooke submodel with a phase angle; and synchronously updating the adjusted phase angle to the parameterized configuration of the Hooke submodel displayed in the modeling interactive interface.

[0096] After creating the Hooke's sub-model with phase angle using the above embodiments and obtaining the interactive operation instructions for the Hooke's sub-model with phase angle, the posture of the Hooke's sub-model with phase angle in the modeling interactive interface needs to be adjusted according to the interactive operation instructions. The form of the interactive operation instructions is not limited in this embodiment; for example, it can be voice input or drag-and-drop operation.

[0097] Optionally, the interactive operation command is applied to the axis direction controller corresponding to the Hooke sub-model with phase angle, and the axis direction controller is displayed around the Hooke model with phase angle.

[0098] Furthermore, during the process of adjusting the posture of the Hooke sub-model with phase angle in the modeling interface, it is also necessary to calculate the adjusted phase angle of the Hooke sub-model with phase angle. This means that when the creator of the Hooke sub-model adjusts the axial direction of the Hooke sub-model through the axial direction controller, the computing device will calculate the adjusted phase angle in real time based on the drag trajectory.

[0099] Furthermore, the method for calculating the adjusted phase angle of the Hooke pair model with phase angle can be diversified. For example, the geometric information required for calculating the phase angle can be extracted from the Hooke pair model after attitude adjustment. This geometric information includes the axis vectors of the input and output axes, the normal vectors of the input and output fork planes, and the gimbal center point. Subsequently, through geometric inverse calculation, the normal vectors of the two fork planes are typically projected onto a common plane perpendicular to the central axis of the Hooke pair model. Then, using vector multiplication combined with a specific mathematical function, the signed angle between these two projected vectors is accurately calculated. This angle is the adjusted phase angle.

[0100] Finally, the computing device updates the calculated adjusted phase angle into the internal parameters of the Hooke sub-model in real time and displays it synchronously on the modeling interface. This achieves seamless and accurate synchronization between the user's intuitive graphical operation and the underlying physical parameters, greatly improving the convenience, accuracy and reliability of modeling.

[0101] Furthermore, in some examples, the display content of the Hooke sub-model with phase angle in the modeling interactive interface is adjusted according to the interactive operation instructions, including: obtaining the operation type and operation parameters in the interactive operation instructions; determining the attitude transformation to be applied to the Hooke sub-model with phase angle based on the operation type and operation parameters; and applying the attitude transformation to the Hooke sub-model with phase angle to update the display attitude of the Hooke sub-model with phase angle in the modeling interactive interface.

[0102] In these examples, the operation type and parameters in the interactive operation instructions are first obtained to accurately identify the nature and specific values ​​of these instructions, thus laying the foundation for subsequent precise attitude transformation. Next, the operation type and parameters are converted into geometric transformations executable by the computing device; that is, the operation type and parameters are transformed into attitude transformations applied to the Hooke's sub-model with phase angles. Finally, the transformed attitude transformation is applied to the Hooke's sub-model with phase angles to update its displayed attitude in the modeling interface. This means that once the attitude transformation is determined, the computing device applies it to the geometric data of the Hooke's sub-model with phase angles and drives the graphics rendering engine to update the visual representation of the model with phase angles in real time in the modeling interface.

[0103] This instant feedback mechanism allows Hooke's sub-model creators to immediately see the impact of their actions on the model's pose, enabling them to quickly determine whether the actions meet expectations and make necessary adjustments.

[0104] In summary, the feedback mechanism provided by the embodiments of this application not only significantly improves the user experience and enhances the intuitiveness and interactivity of modeling, but also accelerates the speed of modeling and design iteration, because users can quickly verify the effects of different posture configurations, thereby greatly improving overall work efficiency.

[0105] Based on the above embodiments, before synchronously updating the adjusted phase angle to the parameterized configuration of the Hooke pair model displayed in the modeling interactive interface, the method further includes: determining whether the adjusted phase angle meets the preset mechanical constraint conditions; if the mechanical constraint conditions are not met, outputting visual feedback information in the modeling interactive interface, including highlighting the Hooke pair model, displaying warning information, and limiting the movement range of the axis direction controller; if the mechanical constraint conditions are met, performing synchronous updating of the parameterized configuration.

[0106] In this embodiment, it is understood that a conditional check needs to be performed on the adjusted phase angle before it is synchronously updated to the parameterized configuration of the Hooke sub-model displayed in the modeling interface. Only when the adjusted phase angle meets the condition will it be synchronously updated to the parameterized configuration of the Hooke sub-model displayed in the modeling interface. This setting can improve the effectiveness of the adjusted phase angle and provide a reliable data foundation for subsequent updates to the Hooke sub-model.

[0107] If the adjusted phase angle does not meet the preset mechanical constraints, visual feedback information is output on the modeling interface. This feedback includes highlighting the Hooke sub-model, displaying warning messages, and limiting the movement range of the axis direction controller. Timely error feedback significantly improves the user experience, enhances the intuitiveness and interactivity of modeling, and accelerates modeling and design iterations. Users can quickly verify the effects of different posture configurations, thereby greatly improving overall work efficiency.

[0108] Furthermore, the preset mechanical constraints can be set according to the actual situation. For example, in order to achieve constant speed transmission of the transmission shaft composed of two Hooke pairs and avoid angular velocity fluctuations, it is usually required that the included angles of the input shaft and output shaft of the two Hooke pairs be equal, and that the relative phase angles of the fork-shaped parts of the two Hooke pairs in the axial direction satisfy a specific relationship. Therefore, the adjusted phase angles must meet these conditions to ensure that the output end and input end of the transmission shaft maintain a constant angular velocity ratio.

[0109] Furthermore, an incorrect phase angle can cause periodic torsional and bending vibrations in the driveshaft, leading to vehicle vibration and noise problems. Therefore, the preset constraints require that the adjusted phase angle control these vibrations and noises within an acceptable range. It should be noted that the mechanical constraints described herein are merely examples.

[0110] This application embodiment helps Hooke sub-model creators verify the rationality of design schemes in a virtual environment and promptly identify potential problems by determining whether the adjusted phase angle meets preset mechanical constraints. This allows for optimization of the Hooke sub-model configuration and improvement of the performance, reliability, and comfort of the vehicle transmission system.

[0111] The following examples will further illustrate how to utilize the Hooke pair modeling method provided in the embodiments of this application. Figure 3 A flowchart illustrating the Hooke pair modeling method provided in this application embodiment. Figure Two .like Figure 3As shown, when a user edits the Hooke sub-model data, they can adjust the phase angle data through text input in the data display window or geometric interaction in the canvas area. The data display window inputs the phase angle as a parameter; specifically, it uses the mode conversion function to convert the Hooke sub-model mode. This mode conversion function can cancel the phase angle attribute or modify the phase angle data by inputting specific values.

[0112] When a user clicks on a created Hooke sub-model in the canvas area, the geometric interaction processing module is activated simultaneously with the data display window showing relevant content. This activates the Hooke sub-model's interactive state, and an axis controller corresponding to the current rotation axis direction appears around it. The user can drag one of the axis controllers to change the phase angle. The Hooke sub-model rotates in real-time as the user drags the mouse, and the specific phase angle value changes dynamically and continuously, displayed near the model to accurately reflect the current phase angle. This means the computing device monitors mouse movement, the Hooke sub-model rotates in real-time, and dynamically displays the current phase angle value. When the computing device detects the user releasing the mouse, it determines the current phase angle of the Hooke sub-model, locks it, and updates the determined phase angle in the properties panel. Simultaneously, it updates or generates the position and direction of intermediate reference points based on the current phase angle to determine the final relevant data for the Hooke sub-model. If the computing device does not detect the user releasing the mouse, it continues to monitor mouse movement.

[0113] Figure 4 The content displayed in the data display window provided in this application embodiment. Figure 4 In the center, two magenta dashed lines indicate the axial directions of the two axes connecting the Hooke pair. A thin green line depicts the structure of the Hooke pair model, which consists of universal joints connecting the two axes. The magenta curved arrows at the top and orange curved arrows at the bottom are rotation controllers, indicating the direction in which the Hooke pair can be dragged and rotated. The orange arrow indicates that the rotation controller is currently in mouse-controlled rotation mode. Additionally, a floating text box appears in the data display window, offering two-way functionality: users can freely input angle values ​​to set the rotation angle, or, after manually dragging using the rotation controller, the current phase angle will be displayed in real-time.

[0114] Figure 5 The process of generating the Hooke's sub-model provided in the embodiments of this application. For example... Figure 5As shown, the generation of the Hooke pair model is based on data regarding the model's position, associated components, and phase angle. Reference point 1, input marker (IMarker), reference point 2, reference point 3, reference point 4, and output marker (JMarker) are generated sequentially to determine the orientation of the final Hooke pair model. IMarker and JMarker are virtual reference points or coordinate systems used to anchor and define the spatial position and orientation of the two ends (input and output) of the Hooke pair model during its generation.

[0115] Furthermore, data changes generated by adjusting the phase angle through parameter input and geometric interaction will be synchronously updated in real time to the text display in the data display window, the solver's mechanical model, and the Hooke sub-drawing in the canvas area. This will be used to determine whether the data is valid and to make subsequent changes to the Hooke sub-type.

[0116] Furthermore, embodiments of this application also provide structural schematic diagrams of the Hooke's pair model at different phase angles. Specifically, Figure 6 This is a schematic diagram of the Hooke pair model when the current phase angle is 0, provided in an embodiment of this application. Figure 7 This is a schematic diagram of the Hooke pair model when the current phase angle is not 0, as provided in an embodiment of this application. Figure 6 It can be seen that when the current phase angle is 0, the two gimbals in the Hooke pair model are located in the planes of the two components, respectively. Figure 7 It can be seen that when the current phase angle is not 0, both gimbals in the Hooke pair model rotate clockwise by a phase angle. It should be noted that the current phase angle is the angle between the two gimbals and the plane in which they are located.

[0117] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0118] Figure 8 This is a schematic diagram of the structure of the Hooke sub-modeling device provided in the embodiments of this application, as shown below. Figure 8 As shown, the Hooke sub-modeling device 800 provided in this embodiment includes:

[0119] The acquisition module 801 is used to acquire input containing parameterized configuration in response to the modeling instructions of the Hooke sub-model. The parameterized configuration includes a parameter for characterizing whether a phase angle parameter is included, and the parameter value of the phase angle parameter when it is included.

[0120] Processing module 802 is used to model the first Hooke sub-model corresponding to the parameterized configuration according to the parameterized configuration, and display the first Hooke sub-model on the modeling interactive interface.

[0121] The processing module 802 is also used to respond to the detected Hooke sub-model type switching command, configure the corresponding second Hooke sub-model in the modeling parameterization, and display the second Hooke sub-model in the modeling interaction interface. The model types of the first Hooke sub-model and the second Hooke sub-model are different.

[0122] In one possible implementation, the first Hooke submodel is a standard Hooke submodel, and the second Hooke submodel is a Hooke submodel with a phase angle; or, the first Hooke submodel is a Hooke submodel with a phase angle, and the second Hooke submodel is a standard Hooke submodel.

[0123] In one possible implementation, the processing module 802 is specifically used for:

[0124] Upon detecting a type switching instruction, perform the following operations based on the type switching instruction:

[0125] If the type switching instruction indicates that the standard Hooke sub-model is switched to the Hooke sub-model with phase angle, then an intermediate reference point is added to the standard Hooke sub-model to model the corresponding second Hooke sub-model with parameterized configuration.

[0126] If the type switching instruction indicates that the Hooke sub-model with phase angle is switched to the standard Hooke sub-model, then the intermediate reference point is removed in the Hooke sub-model with phase angle to model the corresponding second Hooke sub-model with parameterized configuration.

[0127] In one possible implementation, the first Hooke's submodel is a Hooke's submodel with a phase angle, or the second Hooke's submodel is a Hooke's submodel with a phase angle, and the processing module 802 is further configured to:

[0128] When an interactive operation command is received for the Hooke sub-model with phase angle, the pose of the Hooke sub-model with phase angle in the modeling interactive interface is adjusted according to the interactive operation command, and during the adjustment process, the adjusted phase angle of the Hooke sub-model with phase angle is calculated.

[0129] The adjusted phase angle will be synchronously updated in the parameterized configuration of the Hooke sub-model displayed in the modeling interactive interface.

[0130] In one possible implementation, the processing module 802 is specifically used for:

[0131] Retrieve the operation type and operation parameters from the interactive operation command;

[0132] Based on the operation type and operation parameters, determine the attitude transformation applied to the Hooke pair model with phase angle;

[0133] The pose transformation is applied to the Hooke sub-model with phase angle to update the displayed pose of the Hooke sub-model with phase angle in the modeling interface.

[0134] In one possible implementation, the interactive operation command acts on the axis orientation controller corresponding to the Hooke sub-model with phase angle, and the axis orientation controller is displayed around the Hooke sub-model with phase angle.

[0135] In one possible implementation, the processing module 802 is further configured to:

[0136] Determine whether the adjusted phase angle meets the preset mechanical constraint conditions;

[0137] If the mechanical constraints are not met, visual feedback information will be output on the modeling interface. The visual feedback information includes highlighting the Hooke sub-model, displaying warning information, and limiting the movement range of the axis direction controller.

[0138] If the mechanical constraints are met, perform a synchronous update of the parameterized configuration.

[0139] The Hooke sub-modeling device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0140] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, a processing module can be a separate processing element, or it can be integrated into an integrated circuit within the above device. Alternatively, it can be stored as program code in the device's memory, and its functions can be called and executed by a processing element. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0141] For example, these modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). As another example, when a module is implemented by calling program code through a processing element, that processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together to implement a System-On-a-Chip (SOC).

[0142] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 9 As shown, the electronic device 900 provided in this application embodiment may include: a processor 901, and a memory 902 communicatively connected to the processor, wherein:

[0143] The memory stores instructions that the computer executes;

[0144] The processor executes computer execution instructions stored in memory to implement the method described in the foregoing method embodiments.

[0145] It should be understood that processor 901 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor. Memory 902 may include high-speed random access memory (RAM), and may also include non-volatile memory (NVM), such as at least one disk storage device, or a USB flash drive, external hard drive, read-only memory, disk, or optical disc, etc.

[0146] Optionally, the electronic device 900 may also include a communication interface 903. In specific implementations, if the communication interface 903, memory 902, and processor 901 are implemented independently, they can be interconnected via a bus to complete communication. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not imply that there is only one bus or one type of bus.

[0147] Optionally, in a specific implementation, if the communication interface 903, memory 902, and processor 901 are integrated on a single integrated circuit, then the communication interface 903, memory 902, and processor 901 can communicate through an internal interface.

[0148] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the methods described in any of the foregoing embodiments.

[0149] It is understood that the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0150] An exemplary computer-readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be a component of the processor. The processor and the computer-readable storage medium can reside in an ASIC. Alternatively, the processor and the computer-readable storage medium can exist as discrete components in an electronic device.

[0151] The integrated modules implemented as software functional modules described above can be stored in a computer-readable storage medium. These software functional modules, stored in a computer-readable storage medium, include several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application.

[0152] This application also provides a computer program product, including a computer program that, when executed, implements the method described in any of the foregoing embodiments.

[0153] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0154] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0155] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments have been described. However, as long as these combinations of technical features do not contradict each other, they should be considered within the scope of this specification.

[0156] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0157] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A Hooke's pass modeling method, characterized in that, include: In response to the modeling instructions of the Hooke sub-model, an input containing a parameterized configuration is obtained, the parameterized configuration including a parameter for characterizing whether a phase angle parameter is included, and the parameter value of the phase angle parameter when the phase angle parameter is included; Based on the parameterized configuration, a first Hooke sub-model corresponding to the parameterized configuration is modeled, and the first Hooke sub-model is displayed on the modeling interactive interface. In response to the detected Hooke sub-model type switching command, a second Hooke sub-model corresponding to the parameterized configuration is modeled, and the second Hooke sub-model is displayed on the modeling interaction interface. The model types of the first Hooke sub-model and the second Hooke sub-model are different.

2. The Hooke's pass modeling method according to claim 1, characterized in that, The first Hooke submodel is a standard Hooke submodel, and the second Hooke submodel is a Hooke submodel with a phase angle; or, the first Hooke submodel is a Hooke submodel with a phase angle, and the second Hooke submodel is a standard Hooke submodel.

3. The Hooke's pair modeling method according to claim 2, characterized in that, The response detects a type switching instruction for the Hooke sub-model and models the second Hooke sub-model corresponding to the parameterized configuration, including: In response to the detection of the type switching instruction, perform the following operations according to the type switching instruction: If the type switching instruction indicates that the standard Hooke sub-model is switched to the Hooke sub-model with phase angle, then an intermediate reference point is added in the standard Hooke sub-model to model the second Hooke sub-model corresponding to the parameterized configuration. If the type switching instruction indicates that the Hooke sub-model with phase angle is switched to the standard Hooke sub-model, then the intermediate reference point is removed in the Hooke sub-model with phase angle to model the second Hooke sub-model corresponding to the parameterized configuration.

4. The Hooke pair modeling method according to any one of claims 1 to 3, characterized in that, The first Hooke's submodel is a Hooke's submodel with a phase angle, or the second Hooke's submodel is a Hooke's submodel with a phase angle, and the Hooke's submodeling method further includes: When an interactive operation command is received for the Hooke sub-model with phase angle, the posture of the Hooke sub-model with phase angle in the modeling interactive interface is adjusted according to the interactive operation command, and during the adjustment process, the adjusted phase angle of the Hooke sub-model with phase angle is calculated. The adjusted phase angle is then synchronously updated in the parameterized configuration of the Hooke sub-model displayed in the modeling interaction interface.

5. The method according to claim 4, characterized in that, The step of adjusting the display content of the Hooke sub-model with phase angle in the modeling interaction interface according to the interactive operation instructions includes: Obtain the operation type and operation parameters from the interactive operation instructions; Based on the operation type and the operation parameters, determine the attitude transformation applied to the Hooke sub-model with phase angle; The attitude transformation is applied to the Hooke sub-model with phase angle to update the displayed attitude of the Hooke sub-model with phase angle in the modeling interface.

6. The method according to claim 4, characterized in that, The interactive operation command is applied to the axis direction controller corresponding to the Hooke sub-model with phase angle, and the axis direction controller is displayed around the Hooke sub-model with phase angle.

7. The method according to claim 6, characterized in that, Before synchronously updating the adjusted phase angle to the parameterized configuration of the Hooke sub-model displayed in the modeling interface, the process also includes: Determine whether the adjusted phase angle meets the preset mechanical constraint conditions; If the mechanical constraints are not met, visual feedback information is output on the modeling interface. The visual feedback information includes highlighting the Hooke sub-model, displaying warning information, and limiting the movement range of the axis direction controller. If the mechanical constraints are met, the parameterized configuration is updated synchronously.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, are used to implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed, implements the method described in any one of claims 1-6.

Images