An interactive mainboard fan debugging method and device, electronic equipment and storage medium

Abstract

The present disclosure provides an interactive mainboard fan debugging method and device, electronic equipment and storage medium, which guides the user to complete the configuration reading, pin checking, drive testing, troubleshooting, speed calculation and parameter correction of the target fan through guided interaction, thereby reducing the dependence of mainboard fan debugging on human experience and improving the positioning efficiency and debugging accuracy of fan abnormal problems. The originally scattered and experience-dependent debugging process can be integrated into a process, realizing the orderly positioning of fan configuration problems, control link problems and speed feedback problems, and having the technical effects of improving the debugging efficiency, shortening the troubleshooting time, improving the parameter checking accuracy and enhancing the convenience of mainboard fan debugging.

Description

Technical Field

[0001] This disclosure relates to the field of computer hardware debugging technology, and more specifically, to an interactive motherboard fan debugging method, apparatus, electronic device, and storage medium. Background Technology

[0002] As the integration of motherboards in servers, industrial control equipment, edge computing devices, and various smart terminals continues to increase, motherboards are typically equipped with multiple cooling fans to actively dissipate heat from the processor, power supply module, memory devices, and other heat-generating components, ensuring the stability and reliability of the entire system. In practical applications, motherboard fans are usually speed-controlled using pulse width modulation (PWM) signals and their operating status is reported via speed feedback (TACH) signals to achieve functions such as fan start / stop control, speed monitoring, and abnormal alarms.

[0003] In existing technologies, troubleshooting motherboard fans typically relies on manual checks by R&D or testing personnel using schematics, configuration files, drivers, and hardware testing tools. For example, when problems arise such as a fan not spinning, abnormal speed, control failure, or feedback errors, it's often necessary to first confirm the fan number and configuration, then verify the mapping between the PWM control pin and the TACH feedback pin, and then use an oscilloscope or logic analysis tool to check if the PWM output is normal, if the fan input receives a valid drive signal, and if the TACH feedback pulse meets expectations. This type of troubleshooting involves a comprehensive assessment of software configuration, hardware connections, and the device's own condition; the operation chain is lengthy and heavily reliant on the experience of the debugging personnel. Summary of the Invention

[0004] This disclosure provides at least one interactive motherboard fan debugging method, apparatus, electronic device, and storage medium. Through a wizard-style interactive process, it guides users to complete the target fan configuration reading, pin verification, driver testing, fault diagnosis, and speed calculation and parameter correction. This reduces the reliance on manual experience in motherboard fan debugging and improves the efficiency and accuracy of locating fan malfunctions. It streamlines the previously fragmented and experience-dependent debugging process, enabling the orderly location of fan configuration problems, control link problems, and speed feedback problems. This results in improved debugging efficiency, shortened fault diagnosis time, enhanced parameter verification accuracy, and increased convenience of motherboard fan debugging.

[0005] This disclosure provides an interactive motherboard fan debugging method, including: Obtain the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information; Output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and receive the user's confirmation result regarding whether the pin information is consistent with the actual hardware connection relationship; When the confirmation result indicates that the pin information is consistent with the actual hardware connection, the fan control signal pin is controlled to output a preset test drive signal, and the user's feedback result on whether the target fan is operating normally is received. When the feedback result indicates that the target fan is not operating normally, fault troubleshooting information related to the fan control signal link is output. When the feedback result indicates that the target fan is operating normally, the pulse parameters corresponding to the speed feedback signal are collected, and the speed information of the target fan is calculated based on the pulse parameters and the preset polarity parameters. The rotational speed information is output, or when the actual rotational speed information of the target fan is received, the corrected polarity parameter is determined based on the rotational speed information, the preset polarity parameter, and the actual rotational speed information.

[0006] In one optional implementation, the target fan identification information input by the user is obtained, and the corresponding fan configuration information is read based on the target fan identification information, specifically including: Launch the fan setup wizard interface; Output a prompt message corresponding to the fan number range supported by the current motherboard to guide the user to enter the fan number of the fan to be debugged; In response to receiving a fan number input by the user, read the fan configuration information corresponding to that fan number from a preset configuration file, driver configuration table, or firmware configuration table; The fan configuration information includes at least one of the PWM control signal pin information and TACH speed feedback signal pin information corresponding to the target fan. If the read fails, the fan number exceeds the limit, or the target fan is not configured, an error message will be output and the user will be prompted to re-enter the information.

[0007] In one optional implementation, the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information are output, and the user's confirmation result regarding whether the pin information is consistent with the actual hardware connection relationship is received, specifically including: Output the SOC-side PWM pin number and SOC-side TACH pin number corresponding to the target fan, as well as the functional descriptions of the PWM pin number and TACH pin number; The user is prompted to confirm, based on the motherboard schematic, PCB silkscreen information, connector definition information, or wiring harness connection relationship, whether the PWM pin and TACH pin are consistent with the actual hardware connection of the target fan. Receive consistent or inconsistent confirmation results from user input; Upon receiving an inconsistent confirmation result, the system further receives the actual hardware connection relationship information input by the user and outputs a configuration error message to prompt the user to modify the target fan configuration information and re-execute the debugging process. Upon receiving a consistent confirmation result, proceed to the fan drive test step.

[0008] In one optional implementation, the fan control signal pin is controlled to output a preset test drive signal and receive user feedback on whether the target fan is operating normally, specifically including: The PWM control signal pin corresponding to the target fan outputs a test PWM signal to perform an active drive test on the target fan. The test PWM signal has a preset frequency and a preset duty cycle. The preset frequency is used to match the drive frequency requirements of the target fan, and the preset duty cycle is used to provide a preset drive force. After the test PWM signal is output for a preset duration, an operation confirmation prompt message is output to prompt the user to observe whether the target fan has started, whether it is rotating continuously, and whether the rotation status is stable, and to receive the operation feedback result input by the user.

[0009] In one optional implementation, when the feedback result indicates that the target fan is not operating normally, fault diagnosis information related to the fan control signal link is output, specifically including: The system prompts you to check whether the PWM output pin on the SOC side outputs a square wave signal corresponding to the preset test drive signal, in order to determine whether there is an abnormality in the SOC side fan control module. If the PWM output pin on the SOC side is working properly, the system prompts the system to check whether the target fan input terminal receives the corresponding PWM drive signal in order to determine whether there is any abnormality in the connection line, level conversion circuit, interface device or intermediate drive circuit between the SOC and the target fan. If the target fan has received the corresponding PWM drive signal at its input terminal, a fault is detected in the target fan itself. Based on different test results, corresponding fault location conclusions are output to attribute the fault to at least one of the following: abnormal parameter configuration, abnormal SOC control, abnormal connection link, abnormal level conversion, or abnormal fan device.

[0010] In one optional implementation, when the feedback result indicates that the target fan is operating normally, the pulse parameters corresponding to the speed feedback signal are collected, and the speed information of the target fan is calculated based on the pulse parameters and preset polarity parameters, specifically including: Obtain the TACH speed feedback signal corresponding to the target fan; The number of pulses in the TACH speed feedback signal is counted within a preset time window; Read the preset polarity parameter corresponding to the target fan, wherein the preset polarity parameter is used to characterize the number of feedback pulses corresponding to each revolution of the target fan; Based on the number of pulses and the preset polarity parameter, the target fan speed information is calculated according to the preset speed conversion relationship, so that the user can judge whether the current target fan speed feedback link is normal.

[0011] In one optional implementation, the rotational speed information is output, or upon receiving the actual rotational speed information of the target fan, a corrected polarity parameter is determined based on the rotational speed information, the preset polarity parameter, and the actual rotational speed information. Specifically, this includes: When the user inputs or the system obtains the actual speed information of the target fan, the speed information calculated from the actual speed information is compared; When the rotational speed information is inconsistent with the actual rotational speed information, the corrected polarity parameter is determined according to the rotational speed information, the preset polarity parameter, and the actual rotational speed information, based on a preset correction relationship. If the actual speed information of the target fan is not obtained, the preset polarity parameter is retained and the speed information is directly output.

[0012] This disclosure also provides an interactive motherboard fan debugging device, including: The data acquisition module is used to acquire the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information; The connection relationship confirmation module is used to output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and to receive the user's confirmation result on whether the pin information is consistent with the actual hardware connection relationship; The normal operation confirmation module is used to control the fan control signal pin to output a preset test drive signal when the confirmation result indicates that the pin information is consistent with the actual hardware connection relationship, and to receive feedback results from the user regarding whether the target fan is operating normally. The fault indication module is used to output fault troubleshooting information related to the fan control signal link when the feedback result indicates that the target fan is not operating normally; The speed calculation module is used to collect the pulse parameters corresponding to the speed feedback signal when the feedback result indicates that the target fan is operating normally, and to calculate the speed information of the target fan based on the pulse parameters and the preset polarity parameters. The data output module is used to output the rotation speed information, or, when receiving the actual rotation speed information of the target fan, to determine the corrected polarity parameter based on the rotation speed information, the preset polarity parameter, and the actual rotation speed information.

[0013] This disclosure also provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, they perform the steps of the above-described interactive motherboard fan debugging method, or any possible implementation of the above-described interactive motherboard fan debugging method.

[0014] This disclosure also provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the above-described interactive motherboard fan debugging method, or any possible implementation of the above-described interactive motherboard fan debugging method.

[0015] This disclosure also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implements the above-described interactive motherboard fan debugging method, or the steps in any possible implementation of the above-described interactive motherboard fan debugging method.

[0016] This disclosure provides an interactive motherboard fan debugging method, apparatus, electronic device, and storage medium. Through a wizard-style interactive process, it guides users to complete target fan configuration reading, pin verification, driver testing, fault diagnosis, and speed calculation and parameter correction. This reduces the reliance on manual experience in motherboard fan debugging and improves the efficiency and accuracy of locating fan malfunctions. It streamlines the previously fragmented and experience-dependent debugging process, enabling the orderly location of fan configuration issues, control link problems, and speed feedback issues. This results in improved debugging efficiency, shorter fault diagnosis time, enhanced parameter verification accuracy, and increased convenience of motherboard fan debugging.

[0017] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0019] Figure 1 A flowchart of an interactive motherboard fan debugging method provided in an embodiment of this disclosure is shown; Figure 2 A schematic diagram of an interactive motherboard fan debugging device provided in an embodiment of this disclosure is shown; Figure 3 A schematic diagram of an electronic device provided in an embodiment of the present disclosure is shown. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0021] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0022] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0023] Research has revealed that in existing technologies, troubleshooting motherboard fans typically relies on manual checks by R&D or testing personnel using schematics, configuration files, drivers, and hardware testing tools. For example, when issues arise such as a fan not spinning, abnormal speed, control failure, or feedback errors, it's often necessary to first confirm the fan number and configuration, then verify the mapping between the PWM control pin and the TACH feedback pin, and finally use an oscilloscope or logic analysis tool to check if the PWM output is normal, if the fan input receives a valid drive signal, and if the TACH feedback pulse meets expectations. This type of troubleshooting involves a comprehensive assessment of software configuration, hardware connections, and the device's own condition; the operational chain is lengthy and heavily reliant on the experience of the troubleshooting personnel.

[0024] Based on the above research, this disclosure provides an interactive motherboard fan debugging method, device, electronic device, and storage medium. Through a wizard-style interactive process, it guides users to complete the target fan configuration reading, pin verification, driver testing, fault diagnosis, and speed calculation and parameter correction. This reduces the reliance on manual experience in motherboard fan debugging and improves the efficiency and accuracy of locating fan malfunctions. It streamlines the previously fragmented and experience-dependent debugging process, enabling the orderly location of fan configuration problems, control link problems, and speed feedback problems. This results in improved debugging efficiency, shortened fault diagnosis time, enhanced parameter verification accuracy, and increased convenience of motherboard fan debugging.

[0025] To facilitate understanding of this embodiment, a detailed description of the interactive motherboard fan debugging method disclosed in this disclosure is provided first. The executing entity of the interactive motherboard fan debugging method provided in this disclosure is generally a computer device with a certain computing capability. This computer device may include, for example, a terminal device, a server, or other processing devices. The terminal device may be a user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, this interactive motherboard fan debugging method can be implemented by the processor calling computer-readable instructions stored in memory.

[0026] See Figure 1 The diagram shows a flowchart of an interactive motherboard fan debugging method provided in this embodiment of the present disclosure. The method includes steps S101 to S106, wherein: S101. Obtain the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information.

[0027] In practice, after starting the debugging wizard, the first step is to obtain the target fan identification information input by the user and read the corresponding fan configuration information based on the target fan identification information. This step is used to determine the target fan to be debugged among multiple fan channels and to provide the corresponding configuration basis for subsequent pin verification, drive testing, fault location, and speed calibration.

[0028] Specifically, the target fan identification information can be a fan number used to distinguish different fans on the motherboard. Since a motherboard typically has multiple fan channels, the control objects, pin assignments, and parameter configurations of different fans in the system may differ. Therefore, when entering the debugging process, the user needs to first specify the fan to be debugged. To this end, the debugging wizard can output a fan number input prompt on the display interface, and simultaneously output the fan number range supported by the current motherboard platform, to guide the user to input the fan number corresponding to the target fan. The limited number range can be preset according to the number of fans supported by the motherboard, for example, it can be a number range of 0, 1, 2, etc.

[0029] In some implementations, after starting the debugging wizard, the interface may display a prompt "Please enter the number of the fan to be debugged" and further display "Currently selectable number range" as a preset number set, so that the user can directly complete the input according to the prompt during the interaction.

[0030] This setup reduces the burden on users to remember the motherboard fan topology and underlying configuration relationships, and also avoids incorrect selection of debugging targets due to inputting invalid fan numbers, thus improving the standardization and accuracy of the debugging process.

[0031] Here, upon receiving user input, the system identifies the input fan number as the target fan identifier. In other words, in this embodiment, the target fan identifier is specifically implemented using the fan number. Using the fan number as the identifier facilitates the system's quick location of the corresponding fan's configuration item within the existing configuration, and also allows users to independently debug different fans one by one in multi-fan scenarios.

[0032] Furthermore, after determining the target fan identification information, the system reads the corresponding fan configuration information based on the target fan identification information. Specifically, the system can retrieve the configuration item corresponding to the fan number from the system's pre-stored configuration data, and read this configuration item as the fan configuration information of the target fan. Controlling the motherboard fan typically involves multiple configuration items, including at least the control signal configuration and feedback signal configuration related to the target fan, so that the corresponding SOC-side PWM signal pin and TACH signal pin can be output subsequently, allowing the user to verify whether it matches the actual hardware connection.

[0033] It should be noted that the fan configuration information may include at least one of the PWM control signal pin information and TACH speed feedback signal pin information corresponding to the target fan. In some embodiments, the fan configuration information may also include parameter configuration, speed configuration, mode configuration, or control strategy configuration related to the fan.

[0034] In some implementations, reading the corresponding fan configuration information can be specifically understood as: based on the fan number input by the user, reading the configuration data corresponding to that fan number from the system configuration file, driver configuration table, control parameter table, or other preset configuration carrier. Any implementation that can locate the corresponding configuration information of a fan from its identifier can be considered a specific implementation of this application. In this way, the system can perform fan debugging based on existing configuration data without revealing the underlying control source code.

[0035] In practical applications, if the fan number entered by the user exceeds the limit range, or if the system does not find the configuration item corresponding to the fan number, the debugging wizard can output an error message and prompt the user to re-enter the fan number or check if the corresponding configuration exists.

[0036] This allows for the timely detection of input errors or missing configurations at the beginning of the debugging process, preventing invalid operations during subsequent pin verification and driver testing. This error notification mechanism also improves the fault tolerance of the debugging process. The step-by-step prompts and item-by-item confirmation interaction method helps users focus on the current single problem point, facilitating the gradual identification of configuration issues in the system.

[0037] S102. Output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and receive the user's confirmation result regarding whether the pin information is consistent with the actual hardware connection relationship.

[0038] In specific implementation, after reading the fan configuration information corresponding to the target fan identification information, this embodiment further executes the steps of outputting the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and receiving the user's confirmation result on whether the pin information is consistent with the actual hardware connection relationship.

[0039] Specifically, after reading the fan configuration information of the target fan, the system can extract the fan control signal pin information and speed feedback signal pin information corresponding to the target fan from the fan configuration information.

[0040] The fan control signal pin information can be the PWM control signal pin information corresponding to the target fan, and the speed feedback signal pin information can be the TACH speed feedback signal pin information corresponding to the target fan. Motherboard fans typically achieve speed regulation through PWM signals and output feedback pulses related to the fan speed through TACH signals. Therefore, these two signal pins constitute the core control and feedback interface during fan tuning.

[0041] In some implementations, the system can output the SOC-side PWM pin number and SOC-side TACH pin number corresponding to the target fan to the debugging wizard interface for user viewing. In addition to the pin number, it can also output functional description information corresponding to the pin, such as whether the pin is used to output fan control signals or to receive fan speed feedback signals.

[0042] Furthermore, after the fan control signal pin information and speed feedback signal pin information are output on the interface, the system can prompt the user to check the pin information against the actual hardware connection relationship of the target fan by referring to the motherboard schematic, PCB silkscreen information, connector definition information, wiring harness connection relationship or other hardware design data.

[0043] In other words, users need to confirm whether the PWM pin indicated in the configuration is indeed connected to the control input terminal of the target fan, and whether the TACH pin indicated in the configuration is indeed connected to the speed feedback output terminal of the target fan.

[0044] In this embodiment, the system can further output confirmation prompts, requiring the user to input a confirmation result regarding whether the pin information matches the actual hardware connection. For example, the system can prompt the user to input "Y" to indicate consistency and "N" to indicate inconsistency. This confirmation result, received by the debugging wizard, can serve as the basis for subsequent process branch judgments.

[0045] Here, when the user inputs a confirmation result indicating that the software configuration relationship and hardware connection relationship of the current target fan are basically matched, the system can continue to the next fan driver test process; when the user inputs a confirmation result indicating that the configuration relationship of the target fan is inconsistent with the actual hardware connection relationship, it is not advisable to continue to execute the subsequent driver test, but the user should be prompted to correct the configuration or check the wiring relationship first.

[0046] In some implementations, when the system receives an inconsistent confirmation result from the user, it can output a configuration error message to indicate that the current target fan has a configuration error or a connection mapping error.

[0047] Furthermore, the system can prompt the user to input the actual correspondence between the target fan and the SOC hardware pins, such as which SOC PWM pin and which SOC TACH pin the target fan is actually connected to. Based on this correspondence information, the user can correct the fan configuration information of the current target fan and restart the debugging process after the correction is completed.

[0048] It's important to note that correctly driving a motherboard fan typically involves numerous configuration items and hardware connectivity issues. An incorrect configuration of any parameter can prevent achieving the desired fan control results. Furthermore, in some application scenarios, users may not have direct access to the underlying control code and must rely on configuration files and hardware design information for integration and debugging. Therefore, before conducting formal PWM driver testing, it is of significant practical importance to first verify that the target fan is connected to the correct pins using a wizard-guided approach.

[0049] Therefore, by outputting the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and receiving the user's confirmation of whether the pin information is consistent with the actual hardware connection relationship, the consistency check between the software configuration relationship and the hardware connection relationship can be completed in advance in the fan debugging process, avoiding misjudging the configuration error as a drive fault or device fault, and providing the correct prerequisites for subsequent PWM testing, fault link location and TACH speed measurement.

[0050] S103. When the confirmation result indicates that the pin information is consistent with the actual hardware connection relationship, control the fan control signal pin to output a preset test drive signal, and receive feedback from the user on whether the target fan is operating normally.

[0051] In specific implementation, after receiving confirmation from the user that the pin information matches the actual hardware connection, this embodiment further executes the following: when the confirmation indicates that the pin information matches the actual hardware connection, the fan control signal pin is controlled to output a preset test drive signal, and feedback from the user regarding whether the target fan is operating normally is received. This step is used to perform an active drive test on the target fan, based on the confirmed matching of the configuration and hardware connection, to determine whether the fan control link can effectively drive the target fan to work normally.

[0052] Specifically, after the user confirms that the currently output fan control signal pin information and speed feedback signal pin information are consistent with the actual hardware connection, the system can assume that the target fan's software configuration and hardware connection meet the subsequent test conditions. At this time, the debugging wizard controls the corresponding fan control signal pin of the target fan to output a preset test drive signal to apply test drive to the target fan.

[0053] In this specific implementation, the fan control signal pin can be the PWM control signal pin corresponding to the target fan, and the preset test drive signal can be a test PWM signal used to drive the fan to rotate.

[0054] In some implementations, the preset test drive signal has a preset frequency and a preset duty cycle. By pre-setting uniform test drive parameters, the effectiveness of the fan control link can be verified in a relatively standardized manner under different users and different debugging scenarios.

[0055] Specifically, the debugging wizard can control the PWM control signal pin to continuously output a PWM test signal with a preset frequency and a preset duty cycle, which is used as the drive input for the target fan.

[0056] Furthermore, in this embodiment, the preset test drive signal is preferably a PWM signal with a frequency of 25kHz and a duty cycle of 50%. This parameter combination meets the needs of basic drive testing of the fan, ensuring the target fan receives a clear drive input during the testing phase, allowing the user to observe whether the fan starts normally and rotates continuously.

[0057] It should be noted that, in some alternative implementations, the preset frequency and preset duty cycle can also be adjusted according to the target fan type, control interface specifications, or test requirements. As long as it can enable the test drive of the target fan and facilitate the judgment of the fan's operating status, it can be used as a specific implementation of this application.

[0058] After outputting the preset test drive signal, the system can maintain the output of the drive signal for a preset duration to provide sufficient response time for the target fan. In some embodiments, the preset duration can be set to 1 second. After the preset duration, the debugging wizard outputs an operation confirmation prompt, prompting the user to observe whether the target fan is operating normally.

[0059] Here, normal operation can be specifically reflected in: whether the fan has started, whether it is rotating continuously, and whether the rotation is stable.

[0060] In some implementations, the debugging wizard can display a prompt message to the user on the interface, such as "Test PWM signal has been output. Please confirm whether the fan is operating normally," and require the user to input the corresponding feedback result. For example, the user can input "Y" to indicate that the target fan is operating normally, and input "N" to indicate that the target fan is not operating normally. After receiving the feedback result, the system can enter different subsequent processing branches according to the user input.

[0061] When the user inputs feedback indicating that the target fan is not operating normally, the system can further enter the troubleshooting process of the fan control signal link; when the user inputs feedback indicating that the target fan is operating normally, the system can further determine that the PWM control link is working normally and enter the subsequent speed measurement and verification process based on the TACH speed feedback signal.

[0062] In this way, this step actually constitutes an active excitation and detection process for the target fan control link. That is to say, after confirming that the pin mapping and hardware connection are correct, it no longer relies solely on static configuration checks, but further verifies the SOC-side output capability, control signal link transmission capability, and fan response capability by outputting a unified test drive signal.

[0063] S104. When the feedback result indicates that the target fan is not operating normally, output the fault investigation information related to the fan control signal link.

[0064] In specific implementation, after outputting a preset test drive signal and receiving feedback from the user regarding whether the target fan is operating normally, if the feedback indicates that the target fan is not operating normally, this embodiment further executes the step of outputting fault diagnosis information related to the fan control signal link. This step is used to segment and locate key nodes in the fan control path when the target fan fails to respond to the test drive signal as expected, thereby helping the user to further determine the source of the fault.

[0065] Specifically, if the debugging wizard has already controlled the fan control signal pin corresponding to the target fan to output the preset test drive signal, but the user reports that the target fan is still not running normally, it indicates that although the software configuration relationship and hardware connection relationship of the target fan have been confirmed to be consistent in the previous steps, there may still be an anomaly in the target fan control link.

[0066] Here, the anomaly may originate from a control output malfunction on the SOC side, a connection line malfunction between the SOC and the target fan, a level conversion circuit malfunction, an intermediate drive circuit malfunction, or a malfunction of the target fan itself. Therefore, in this step, the system no longer simply stops at judging the phenomenon that the fan is not spinning, but further outputs fault diagnosis information related to the fan control signal link to guide the user to check the key nodes in the control link item by item.

[0067] In some implementations, the troubleshooting information may first prompt the user to check whether the SOC-side PWM output pin outputs a square wave signal corresponding to the preset test drive signal.

[0068] Specifically, users can use an oscilloscope, logic analyzer, or other testing tools to measure the corresponding PWM output pin on the SOC side to confirm whether the pin has output a control waveform consistent with the test settings. This includes checking for the presence of a corresponding PWM square wave, whether the frequency of the PWM square wave matches the preset frequency, and whether the duty cycle matches the preset duty cycle. If the test results indicate that the SOC side PWM output pin does not output the corresponding test drive signal, it can be preliminarily determined that there is an abnormality in the SOC side fan control module or an abnormality in the software control process that generates the test drive signal.

[0069] Furthermore, after confirming that the PWM output pin on the SOC side is functioning normally, the troubleshooting information can also prompt the user to check whether the target fan input terminal receives the corresponding PWM drive signal. In other words, assuming the SOC side has correctly output the test drive signal, it is necessary to continue checking whether the control signal has been correctly transmitted to the target fan's control input terminal via the connection lines, connection devices, interface circuits, level conversion circuits, or other intermediate drive links.

[0070] Here, if the test results indicate that the SOC side has normal output, but the target fan input does not receive the corresponding PWM drive signal, then the fault can be further determined to be in the connection link between the SOC and the target fan. Such connection link abnormalities may include, but are not limited to: disconnected connection lines, abnormal pin soldering, poor connector contact, level conversion circuit failure, damaged intermediate drive devices, or other abnormal situations that prevent the control signal from being transmitted correctly.

[0071] In some implementations, if the detection results indicate that the target fan input has received the PWM drive signal corresponding to the preset test drive signal, but the target fan still does not operate normally, the user can be further prompted to determine that the target fan itself is faulty. The fan itself may be faulty, including a damaged fan motor, abnormal internal drive circuitry, abnormal fan input interface, or other fault conditions that prevent the fan from starting and operating normally even when receiving a normal control signal.

[0072] Furthermore, in this embodiment, the system can output corresponding fault location conclusions based on the investigation results of different detection nodes. For example, when the PWM output on the SOC side is abnormal, a prompt message indicating an abnormal SOC control can be output; when the PWM output on the SOC side is normal but the fan input terminal does not receive the corresponding drive signal, a prompt message indicating an abnormal connection link, abnormal level conversion, or abnormal interface can be output; when the fan input terminal has received the corresponding drive signal but the target fan is still not running, a prompt message indicating an abnormal fan device can be output.

[0073] In some implementations, the troubleshooting information may also include prompts related to abnormal parameter configuration. For example, if the user confirms the pin correspondence is consistent in the preliminary steps, but finds in subsequent testing that the type, frequency, or duty cycle of the SOC output signal does not match the requirements of the target fan, the fault can also be attributed to abnormal parameter configuration.

[0074] In other words, the troubleshooting information in this embodiment is not limited to purely hardware-level troubleshooting prompts, but may also include troubleshooting suggestions related to control parameter settings.

[0075] It should be noted that during motherboard fan troubleshooting, users often encounter the final symptom of the fan not spinning, making it difficult to directly pinpoint the specific fault location. Without a clear troubleshooting sequence, users typically need to repeatedly switch between checking software configuration, SOC output, connection lines, and the fan itself, a cumbersome process heavily reliant on experience. This embodiment directly outputs fault troubleshooting information related to the fan control signal link when the fan is not operating properly. It breaks down the control link into several key nodes and guides users to troubleshoot step-by-step from the control source to the load end, thus transforming the fault location process, which originally relied on personal experience, into a standardized, step-by-step interactive troubleshooting process.

[0076] Therefore, by outputting fault diagnosis information related to the fan control signal link when the feedback result indicates that the target fan is not operating normally, it is possible to segment and locate the fan control link when the target fan cannot be driven normally by the test drive signal, and distinguish different sources of faults such as SOC control abnormality, connection link abnormality, level conversion abnormality, parameter configuration abnormality, and fan component abnormality, thereby improving the efficiency and accuracy of locating and debugging motherboard fan abnormality problems.

[0077] S105. When the feedback result indicates that the target fan is operating normally, the pulse parameters corresponding to the speed feedback signal are collected, and the speed information of the target fan is calculated based on the pulse parameters and the preset polarity parameters.

[0078] In a specific implementation, after receiving feedback from the user regarding whether the target fan is operating normally, if the feedback indicates that the target fan is operating normally, this embodiment further executes the steps of collecting the pulse parameters corresponding to the speed feedback signal and calculating the speed information of the target fan based on the pulse parameters and preset polarity parameters.

[0079] Specifically, after the target fan operates normally via the preset test drive signal, the PWM control link can be considered to be in a normal state. At this time, the debugging wizard can further prompt the user that the PWM signal link is normal and enter the speed measurement stage based on the TACH speed feedback signal. Motherboard fans typically include two key control and feedback signals: the PWM signal, output by the SOC, is used to adjust the fan speed by changing the duty cycle; the TACH signal, output by the fan, has a frequency proportional to the fan speed, and the SOC can determine the fan speed based on the frequency of the TACH signal. Therefore, when the fan is already operating normally, by acquiring the TACH signal and performing speed conversion, it is possible to further verify whether the fan feedback link and speed parameter configuration are normal.

[0080] In this embodiment, the speed feedback signal can be the TACH signal corresponding to the target fan. The acquisition of the pulse parameters corresponding to the speed feedback signal can specifically involve counting the number of pulses input by the TACH signal within a preset time window. For ease of calculation and unified processing, the preset time window can be set to 1 second, and the number of TACH pulses counted within this time window is denoted as M.

[0081] In other words, the pulse parameter can be characterized by the number of pulses per unit time. In this way, the system can convert the feedback pulse signal output by the fan into a digital quantity that can be further used in calculations, providing a basis for subsequent speed calculations.

[0082] Furthermore, after calculating the number of pulses M input per second for the TACH signal, the system also reads the preset polarity parameter N1 corresponding to the target fan. This preset polarity parameter characterizes the number of feedback pulses corresponding to one revolution of the target fan, or in other words, describes the conversion relationship between the actual number of mechanical revolutions of the fan and the TACH feedback pulses. Since different fan models may have different speed feedback pulse output mechanisms, the polarity parameter configured for the fan needs to be considered in the speed conversion calculation.

[0083] Here, after obtaining the pulse count M and the preset polarity parameter N1, the system calculates the target fan's rotational speed information according to a preset rotational speed conversion relationship. In this embodiment, the preset rotational speed conversion relationship can be expressed as: S1 = M × 60 / N1, where S1 represents the target fan's rotational speed per minute, M represents the number of pulses input per second by the TACH signal, and N1 represents the user-configured polarity parameter. Through the above conversion relationship, the number of pulses counted per unit time can be converted into the target fan's rotational speed per minute, thereby obtaining the target fan's rotational speed information S1 calculated by the software side.

[0084] In some implementations, after calculating the target fan's rotational speed information S1, the system can output this information to the debugging wizard interface for user viewing and evaluation. By outputting this speed information to the user, the user can further understand the current operating speed of the target fan under test drive conditions and make a preliminary judgment on whether the TACH feedback link is working properly.

[0085] For example, if the target fan is already rotating normally, but the calculated speed deviates significantly from the expected range, it may mean that the current polarity parameter setting is unreasonable or that there is an anomaly in the TACH link; while if the calculated speed is basically matched with the fan's operating state, it can be preliminarily indicated that the current speed feedback link and conversion relationship are basically correct.

[0086] Furthermore, this step not only outputs the fan speed information calculated by the software, but also provides a basis for subsequent parameter correction. In some implementations, the debugging wizard may further inquire whether the user can obtain the actual speed information of the target fan. If the user can obtain the accurate actual fan speed through external measurement methods, the actual speed can be compared with the speed information calculated by the software, and the fan polarity parameters can be corrected accordingly; if the user cannot obtain the actual speed, the speed information calculated by the software can be directly output as the current debugging result.

[0087] In other words, the rotational speed information S1 obtained in this step can not only serve as the detection result of the current feedback link, but also as the input basis for subsequent parameter verification and correction.

[0088] It's important to note that during motherboard fan debugging, even if the target fan can rotate normally under the test PWM signal, it doesn't mean the entire fan debugging process is completely correct. The fact that the fan can rotate only indicates that the PWM control link has basic driving capability; whether the fan speed can be accurately sensed by the system depends on the functionality of the TACH feedback link and the correctness of the polarity parameter settings. Therefore, after the target fan is running normally, further performing TACH pulse acquisition and speed conversion helps extend the fan control link verification to the fan feedback link verification, making the debugging results more complete.

[0089] S106. Output the rotation speed information, or when the actual rotation speed information of the target fan is received, determine the corrected polarity parameter based on the rotation speed information, the preset polarity parameter, and the actual rotation speed information.

[0090] In specific implementation, after calculating the target fan's speed information based on the pulse parameters and preset polarity parameters corresponding to the speed feedback signal, this embodiment further executes the steps of outputting the speed information, or determining the corrected polarity parameters based on the speed information, the preset polarity parameters, and the actual speed information when the actual speed information of the target fan is received. This step is used to output the aforementioned speed measurement results to the user, or, when an actual speed reference value is available, to further verify and correct the fan polarity parameters, thereby improving the accuracy of the target fan speed calculation results.

[0091] Specifically, in the aforementioned steps, the system has calculated the target fan's speed information S1 based on the collected speed feedback signal pulse parameters and the preset polarity parameters corresponding to the target fan. The speed information S1 can be understood as the fan speed value calculated by the system based on the current configuration parameters and the statistical results of the feedback pulse. In this step, the debugging wizard can output the speed information to the display interface for user viewing.

[0092] In some implementations, outputting the speed information can specifically mean displaying the target fan's speed per minute (RPM) on the debugging wizard interface and notifying the user that the current fan speed measurement calculation is complete. For example, the interface may output a message such as "Current fan speed is XXXX RPM".

[0093] In some application scenarios, users may not be able to obtain the actual speed information of the target fan. In this case, the system can directly output the calculated speed information S1 as the current debugging result and end the current speed verification process. That is, when the actual speed information of the target fan is not received, the system retains the preset polarity parameter N1 and directly outputs the speed information S1 calculated based on the preset polarity parameter. In this situation, although it is impossible to further determine whether the preset polarity parameter is completely accurate, the system can still provide the user with a speed reference value based on the current configuration conditions by outputting the speed information, so that the user can continue to carry out subsequent debugging, configuration evaluation, or fan control strategy analysis.

[0094] Furthermore, in some other embodiments, if the user can obtain the actual speed information S2 of the target fan through external measurement, the system can, after receiving the actual speed information S2, further determine the corrected polarity parameter N2 based on the speed information S1, the preset polarity parameter N1, and the actual speed information S2.

[0095] Here, the actual rotational speed information S2 can come from external rotational speed measuring instruments, fan specification calibration information, manual reading results, or other methods of obtaining information that can reflect the true rotational speed of the target fan.

[0096] Specifically, in this embodiment, the system can compare the calculated rotational speed information S1 with the actual rotational speed information S2. When the calculated rotational speed information S1 is inconsistent with the actual rotational speed information S2, it can be considered that the currently used preset polarity parameter N1 may not completely match the feedback pulse relationship corresponding to the target fan. At this time, the system can determine the corrected polarity parameter N2 according to the preset correction relationship. The preset correction relationship can be expressed as: N2 = S1 × N1 / S2. Wherein, N2 represents the corrected polarity parameter, S1 represents the rotational speed information calculated based on the current preset polarity parameter N1, and S2 represents the actual rotational speed information of the target fan.

[0097] In some implementations, after obtaining the corrected polarity parameter N2, the system can further output the corrected polarity parameter to the user to indicate that there is a deviation in the current fan polarity configuration and suggest that the user correct the polarity parameter in subsequent configurations to N2.

[0098] Furthermore, in some implementations, if the system finds that the speed information S1 and the actual speed information S2 are basically consistent after comparison, it can be considered that the current preset polarity parameter N1 is set reasonably. In this case, the system can directly retain the preset polarity parameter N1 and output a prompt indicating that the current polarity parameter configuration is correct. In this way, the user can confirm that the current target fan is in a normal state in terms of both the TACH speed feedback link and the polarity parameter configuration.

[0099] It should be noted that the fan polarity parameter is used to establish the conversion relationship between the actual mechanical rotation of the fan and the TACH feedback pulse. Therefore, the accuracy of this parameter directly affects the fan speed calculation result. If this parameter is not configured accurately, even if the target fan is rotating normally and the TACH feedback link is outputting pulses normally, the speed information finally obtained by the system may still deviate from the actual speed.

[0100] Therefore, this embodiment introduces an actual speed comparison and polarity parameter correction mechanism on the basis of the output speed information, which can simultaneously complete the output of speed measurement results and parameter calibration during the fan debugging process, thereby improving the accuracy of fan speed calculation.

[0101] Therefore, by outputting the rotational speed information, or by determining the corrected polarity parameters based on the rotational speed information, the preset polarity parameters, and the actual rotational speed information when the actual rotational speed information of the target fan is received, the fan rotational speed result display and fan polarity parameter verification and correction can be realized under different debugging conditions. When the actual rotational speed cannot be obtained, the user is provided with a rotational speed reference result under the current configuration. When the actual rotational speed can be obtained, the accuracy of the fan polarity parameters is further improved, thereby enhancing the reliability of subsequent fan rotational speed calculation and fan control configuration.

[0102] This disclosure provides an interactive motherboard fan debugging method that guides users through a wizard-style interactive process, including target fan configuration reading, pin verification, driver testing, fault diagnosis, speed calculation, and parameter correction. This reduces the reliance on manual experience in motherboard fan debugging and improves the efficiency and accuracy of locating fan malfunctions. It streamlines the previously fragmented and experience-dependent debugging process, enabling the orderly location of fan configuration issues, control link problems, and speed feedback issues. This method offers the technical benefits of improved debugging efficiency, shorter troubleshooting time, enhanced parameter verification accuracy, and increased ease of motherboard fan debugging.

[0103] Those skilled in the art will understand that, in the above-described method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0104] Based on the same inventive concept, this disclosure also provides an interactive motherboard fan debugging device corresponding to the interactive motherboard fan debugging method. Since the principle of the device in this disclosure for solving the problem is similar to the interactive motherboard fan debugging method described above, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0105] Please see Figure 2 , Figure 2 This is a schematic diagram of an interactive motherboard fan debugging device provided in an embodiment of this disclosure. Figure 2 As shown in the figure, the interactive motherboard fan debugging device 200 provided in this embodiment includes: The data acquisition module 210 is used to acquire the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information.

[0106] The connection relationship confirmation module 220 is used to output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and to receive the user's confirmation result on whether the pin information is consistent with the actual hardware connection relationship.

[0107] The normal operation confirmation module 230 is used to control the fan control signal pin to output a preset test drive signal when the confirmation result indicates that the pin information is consistent with the actual hardware connection relationship, and to receive feedback results from the user regarding whether the target fan is operating normally.

[0108] The fault indication module 240 is used to output fault troubleshooting information related to the fan control signal link when the feedback result indicates that the target fan is not operating normally.

[0109] The speed calculation module 250 is used to collect the pulse parameters corresponding to the speed feedback signal when the feedback result indicates that the target fan is operating normally, and to calculate the speed information of the target fan based on the pulse parameters and preset polarity parameters.

[0110] The data output module 260 is used to output the rotation speed information, or, when receiving the actual rotation speed information of the target fan, to determine the corrected polarity parameter based on the rotation speed information, the preset polarity parameter, and the actual rotation speed information.

[0111] The processing flow of each module in the device and the interaction flow between each module can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0112] This disclosure provides an interactive motherboard fan debugging device that guides users through a wizard-style interactive process to complete target fan configuration reading, pin verification, driver testing, fault diagnosis, speed calculation, and parameter correction. This reduces the reliance on manual experience in motherboard fan debugging and improves the efficiency and accuracy of locating fan malfunctions. It streamlines the previously fragmented and experience-dependent debugging process, enabling the orderly location of fan configuration issues, control link problems, and speed feedback issues. This results in improved debugging efficiency, shorter troubleshooting time, enhanced parameter verification accuracy, and increased convenience in motherboard fan debugging.

[0113] Corresponding to Figure 1 The interactive motherboard fan debugging method in this disclosure also provides an electronic device 300, such as... Figure 3 The diagram shown is a structural schematic of an electronic device 300 provided in an embodiment of this disclosure, including: Processor 31, memory 32, and bus 33; memory 32 is used to store execution instructions, including main memory 321 and external memory 322; the main memory 321, also called internal memory, is used to temporarily store the computational data in processor 31, as well as the data exchanged with external memory 322 such as hard disk. Processor 31 exchanges data with external memory 322 through main memory 321. When the electronic device 300 is running, processor 31 and memory 32 communicate through bus 33, enabling processor 31 to execute... Figure 1 The steps of the interactive motherboard fan debugging method.

[0114] This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the interactive motherboard fan debugging method described in the above method embodiments. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0115] This disclosure also provides a computer program product, which includes computer instructions. When the computer instructions are executed by a processor, they can perform the steps of the interactive motherboard fan debugging method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0116] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0117] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this disclosure, it should be understood that the disclosed device and method can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0118] 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.

[0119] In addition, the functional units in the various embodiments of this disclosure 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.

[0120] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0121] Finally, it should be noted that the above-described embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, 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 disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. An interactive motherboard fan debugging method, characterized in that, include: Obtain the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information; Output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and receive the user's confirmation result regarding whether the pin information is consistent with the actual hardware connection relationship; When the confirmation result indicates that the pin information is consistent with the actual hardware connection, the fan control signal pin is controlled to output a preset test drive signal, and the user's feedback result on whether the target fan is operating normally is received. When the feedback result indicates that the target fan is not operating normally, fault troubleshooting information related to the fan control signal link is output. When the feedback result indicates that the target fan is operating normally, the pulse parameters corresponding to the speed feedback signal are collected, and the speed information of the target fan is calculated based on the pulse parameters and the preset polarity parameters. The rotational speed information is output, or when the actual rotational speed information of the target fan is received, the corrected polarity parameter is determined based on the rotational speed information, the preset polarity parameter, and the actual rotational speed information.

2. The method according to claim 1, characterized in that, Obtain the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information, specifically including: Launch the fan setup wizard interface; Output a prompt message corresponding to the fan number range supported by the current motherboard to guide the user to enter the fan number of the fan to be debugged; In response to receiving a fan number input by the user, read the fan configuration information corresponding to that fan number from a preset configuration file, driver configuration table, or firmware configuration table; The fan configuration information includes at least one of the PWM control signal pin information and TACH speed feedback signal pin information corresponding to the target fan. If the read fails, the fan number exceeds the limit, or the target fan is not configured, an error message will be output and the user will be prompted to re-enter the information.

3. The method according to claim 1, characterized in that, Output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and receive the user's confirmation of whether the pin information is consistent with the actual hardware connection relationship, specifically including: Output the SOC-side PWM pin number and SOC-side TACH pin number corresponding to the target fan, as well as the functional descriptions of the PWM pin number and TACH pin number; The user is prompted to confirm, based on the motherboard schematic, PCB silkscreen information, connector definition information, or wiring harness connection relationship, whether the PWM pin and TACH pin are consistent with the actual hardware connection of the target fan. Receive consistent or inconsistent confirmation results from user input; Upon receiving an inconsistent confirmation result, the system further receives the actual hardware connection relationship information input by the user and outputs a configuration error message to prompt the user to modify the target fan configuration information and re-execute the debugging process. Upon receiving a consistent confirmation result, proceed to the fan drive test step.

4. The method according to claim 1, characterized in that, The system controls the fan control signal pin to output a preset test drive signal and receives user feedback on whether the target fan is operating normally, specifically including: The PWM control signal pin corresponding to the target fan outputs a test PWM signal to perform an active drive test on the target fan. The test PWM signal has a preset frequency and a preset duty cycle. The preset frequency is used to match the drive frequency requirements of the target fan, and the preset duty cycle is used to provide a preset drive force. After the test PWM signal is output for a preset duration, an operation confirmation prompt message is output to prompt the user to observe whether the target fan has started, whether it is rotating continuously, and whether the rotation status is stable, and to receive the operation feedback result input by the user.

5. The method according to claim 1, characterized in that, When the feedback result indicates that the target fan is not operating normally, fault diagnosis information related to the fan control signal link is output, specifically including: The system prompts you to check whether the PWM output pin on the SOC side outputs a square wave signal corresponding to the preset test drive signal, in order to determine whether there is an abnormality in the SOC side fan control module. If the PWM output pin on the SOC side is working properly, the system prompts the system to check whether the target fan input terminal receives the corresponding PWM drive signal in order to determine whether there is any abnormality in the connection line, level conversion circuit, interface device or intermediate drive circuit between the SOC and the target fan. If the target fan has received the corresponding PWM drive signal at its input terminal, a fault is detected in the target fan itself. Based on different test results, corresponding fault location conclusions are output to attribute the fault to at least one of the following: abnormal parameter configuration, abnormal SOC control, abnormal connection link, abnormal level conversion, or abnormal fan device.

6. The method according to claim 1, characterized in that, When the feedback result indicates that the target fan is operating normally, the pulse parameters corresponding to the speed feedback signal are collected, and the speed information of the target fan is calculated based on the pulse parameters and preset polarity parameters, specifically including: Obtain the TACH speed feedback signal corresponding to the target fan; The number of pulses in the TACH speed feedback signal is counted within a preset time window; Read the preset polarity parameter corresponding to the target fan, wherein the preset polarity parameter is used to characterize the number of feedback pulses corresponding to each revolution of the target fan; Based on the number of pulses and the preset polarity parameters, the target fan speed information is calculated according to the preset speed conversion relationship, so that the user can determine whether the current target fan speed feedback link is normal.

7. The method according to claim 1, characterized in that, Outputting the rotational speed information, or, upon receiving the actual rotational speed information of the target fan, determining the corrected polarity parameters based on the rotational speed information, the preset polarity parameters, and the actual rotational speed information, specifically includes: When the user inputs or the system obtains the actual speed information of the target fan, the speed information calculated from the actual speed information is compared; When the rotational speed information is inconsistent with the actual rotational speed information, the corrected polarity parameter is determined according to the rotational speed information, the preset polarity parameter, and the actual rotational speed information, based on a preset correction relationship. If the actual speed information of the target fan is not obtained, the preset polarity parameter is retained and the speed information is directly output.

8. An interactive motherboard fan debugging device, characterized in that, include: The data acquisition module is used to acquire the target fan identification information input by the user, and read the corresponding fan configuration information based on the target fan identification information; The connection relationship confirmation module is used to output the fan control signal pin information and speed feedback signal pin information corresponding to the fan configuration information, and to receive the user's confirmation result on whether the pin information is consistent with the actual hardware connection relationship; The normal operation confirmation module is used to control the fan control signal pin to output a preset test drive signal when the confirmation result indicates that the pin information is consistent with the actual hardware connection relationship, and to receive feedback results from the user regarding whether the target fan is operating normally. The fault indication module is used to output fault troubleshooting information related to the fan control signal link when the feedback result indicates that the target fan is not operating normally; The speed calculation module is used to collect the pulse parameters corresponding to the speed feedback signal when the feedback result indicates that the target fan is operating normally, and to calculate the speed information of the target fan based on the pulse parameters and the preset polarity parameters. The data output module is used to output the rotation speed information, or, when receiving the actual rotation speed information of the target fan, to determine the corrected polarity parameter based on the rotation speed information, the preset polarity parameter, and the actual rotation speed information.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the interactive motherboard fan debugging method as described in any one of claims 1 to 7 are performed.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the interactive motherboard fan debugging method as described in any one of claims 1 to 7.

Images