Intelligent monitoring system based on MCU and control method

Abstract

The invention relates to an MCU-based intelligent monitoring system and a control method. The monitoring system comprises an independent MCU module which obtains a corresponding host state parameter set; the enable signal input end of the display driving module is connected with the display driving enable end of the independent MCU module; the driving input end of the independent LCD display module is connected with the driving output end of the display driving module; and the independent MCU module performs threshold judgment and graphical processing on the host state parameter set to generate corresponding display data, and outputs the display data to the independent LCD display module for secondary screen display pushing independent of the main display screen. The problems that a monitoring mode occupies CPU resources, the performance of a host is affected, and use is inconvenient due to the fact that the monitoring mode depends on a main displayer are solved, and the stability, the real-time performance and the user experience of the monitoring process are remarkably improved.

Description

Technical Field

[0001] This invention relates to the technical field of intelligent monitoring, and in particular to an intelligent monitoring system and control method based on an MCU. Background Technology

[0002] Currently, with the continuous improvement in the performance of core components in computer hosts, such as CPUs, memory, and SSDs, their operating frequencies and thermal loads are constantly increasing. The health status of these key components is becoming increasingly important for the overall stability of the system. Existing hardware monitoring methods mostly rely on software tools running within the operating system to collect and display parameters.

[0003] In traditional solutions, monitoring software requires the CPU to read temperature information from the memory and solid-state drive via the SMBus bus and obtain the voltage parameters output by the motherboard power supply via the ESPI bus. The CPU then needs to parse and convert the collected monitoring data before outputting it to the main monitor via the display interface. Since all monitoring operations are performed by the CPU, it inevitably consumes CPU computing resources, potentially leading to performance degradation, especially under high-load application scenarios. Summary of the Invention

[0004] To address the performance degradation caused by excessive CPU resources in existing monitoring methods, this application provides an intelligent monitoring system and control method based on an MCU.

[0005] An MCU-based intelligent monitoring system, comprising: An independent MCU module communicates with various key components of the computer host via a corresponding bus to obtain the corresponding host status parameter set; The display driver module has its enable signal input terminal connected to the display driver enable terminal of the independent MCU module. An independent LCD display module, wherein the driving input terminal of the independent LCD display module is connected to the driving output terminal of the display driving module, and the display signal input terminal of the independent LCD display module is connected to the display signal output terminal of the independent MCU module; The independent MCU module performs classification processing on the host status parameter set, divides it into corresponding target parameter groups, performs threshold judgment and graphical processing on the parameter groups in sequence, generates corresponding display data, and outputs it to the independent LCD display module through the display signal output terminal of the independent MCU module for secondary screen display push independent of the main display screen.

[0006] By adopting the above technical solution, and setting up an independent MCU module to handle the acquisition, classification, processing, and display of monitoring data, the monitoring tasks are no longer dependent on the CPU. This prevents the host system from experiencing lag or performance degradation due to the monitoring process consuming computing resources during high-load operation. Simultaneously, outputting monitoring data to a dedicated LCD secondary screen enables real-time display completely independent of the main monitor, allowing users to view hardware status without switching interfaces. This significantly improves the real-time performance, availability, and overall system stability of the monitoring.

[0007] Preferably, the independent MCU module is provided with a first bus interface, a second bus interface and a third bus interface. The first bus interface is connected to the memory module and solid-state drive in the computer host through a USB bus and / or an SMBus bus to obtain the corresponding first temperature parameter. The second bus interface is connected to multiple power output channels in the computer host through an ESPI bus to obtain the corresponding voltage parameter. The third bus interface is connected to the CPU in the computer host through a PECI bus to obtain the corresponding second temperature parameter. The host status parameter set is a set of parameters including the first temperature parameter, the second temperature parameter and the voltage parameter.

[0008] By adopting the above technical solution, and mapping different hardware parameters to three types of bus interfaces, namely USB / SMBus, ESPI and PECI, native protocol access to memory, SSD, power output and CPU temperature is realized. This enables the MCU to obtain real and accurate temperature and voltage data in a way that is closer to the hardware level, avoiding the delay, data distortion or accuracy loss problems that may occur when reading through software in the traditional way, thereby greatly improving the accuracy and stability of monitoring data.

[0009] Preferably, the independent MCU module includes a configuration storage chip CSPI1, a main control chip CU8, and a USB interface expansion chip CU7. The first data communication terminal of the main control chip CU8 is connected to the data communication terminal of the configuration storage chip CSPI1, and the second data communication terminal of the main control chip CU8 is connected to the data communication terminal of the USB interface expansion chip CU7.

[0010] By adopting the above technical solution, and by introducing a configuration storage chip to store initialization parameters, a main control chip to execute logic processing, and a USB expansion chip to provide interface support, the monitoring system can quickly load the monitoring process configuration after power-on, stably establish communication capabilities of each bus, and ensure that the USB data channel has good compatibility and stability. This gives the entire monitoring system the advantages of strong configurability, fast startup speed, and flexible interface expansion.

[0011] Preferably, the display driver module includes a boost driver chip CU6, an inductor CL2, and a diode CD2. The power output terminal of the power supply is connected to the power input terminal of the boost driver chip CU6 and the first terminal of the inductor CL2. The power output terminal of the boost driver chip CU6 and the second terminal of the inductor CL2 are combined into a common node, which is connected to the anode terminal of the diode CD2. The cathode terminal of the diode CD2 is connected to the drive input terminal of the independent LCD display module. The enable input terminal of the boost driver chip CU6 is connected to the display driver enable terminal of the independent MCU module.

[0012] By adopting the above technical solution, the backlight driving module composed of boost driver chip, inductor and diode is integrated into the display path, so that the LCD screen can obtain stable high voltage backlight power supply after the MCU sends an enable signal. This ensures uniform display brightness, fast response and no flicker, and avoids screen blackout or display abnormality caused by power fluctuation of the motherboard, thereby ensuring the continuous visibility and reliable presentation of monitoring information on the secondary screen.

[0013] Preferably, the independent MCU module is connected to an HW monitor chip via an SMBus bus. The temperature signal input terminal of the HW monitor chip is connected to a thermistor, and the voltage signal input terminal of the HW monitor chip is connected to an A / D acquisition unit.

[0014] By adopting the above technical solution and introducing the HW monitor chip as a peripheral acquisition extension module of the MCU, the MCU can quickly acquire temperature and voltage data converted by the thermistor and A / D acquisition unit through the HW monitor, outside of the traditional bus protocol. This realizes a backup acquisition path closer to the physical layer, enabling the monitoring system to have higher fault tolerance and multi-source detection capabilities in special scenarios.

[0015] A control method for an MCU-based intelligent monitoring system, applied to an MCU-based intelligent monitoring system, the control method comprising: Obtain initialization configuration information, and construct the initialization runtime environment for the preset monitoring process based on the initialization configuration information; In the initialization running environment, protocol access and parsing are performed through the corresponding bus interface to obtain the host status parameter set for the current monitoring period; The host status parameter set is classified and divided into multiple target parameter groups; The target parameter group is sequentially subjected to threshold judgment and graphical processing to generate corresponding display data and determine corresponding sampling feedback data. The display data is used for secondary screen display push independent of the main screen, and the sampling feedback data is used to dynamically adjust the sampling parameters for the next monitoring cycle.

[0016] By adopting the above technical solution, and through constructing an initial operating environment, executing multi-protocol data access, classifying and processing parameters, and generating graphical display data, the monitoring process forms a closed-loop, periodic mechanism from startup to display. This allows the MCU to continuously and autonomously run monitoring tasks without relying on CPU intervention. Simultaneously, by setting sampling feedback data to adjust the sampling parameters for the next cycle, the monitoring process possesses dynamic adaptive capabilities, enabling real-time adjustments to the acquisition strategy based on changes in system status, significantly improving the real-time performance and flexibility of monitoring.

[0017] Preferably, the step of obtaining the host status parameter set for the current monitoring period by performing protocol access parsing through the corresponding bus interface includes: Extract the corresponding priority rules and access arbitration strategies from the initialization runtime environment; The execution order of each protocol access is determined based on the aforementioned priority rules; When the current monitoring cycle is triggered, the busy / idle status of each bus is detected according to the access arbitration policy, and when the corresponding bus is detected to be occupied, the corresponding backoff process is executed according to the access arbitration policy. If no corresponding bus is detected to be occupied, the corresponding access tasks are accessed sequentially according to the execution order. Among them, SMBus bus access is used to obtain the temperature parameters of memory modules and solid-state drives, ESPI bus access is used to obtain the voltage parameters of multiple power output channels, and PECI bus access is used to parse the CPU's DTS temperature data to form a complete set of host status parameters for the current monitoring cycle.

[0018] By adopting the above technical solutions and establishing priority rules and access arbitration strategies in the monitoring process, the MCU can perform orderly scheduling in scenarios where multiple protocols coexist, avoiding data errors or acquisition failures caused by bus conflicts. By executing SMBus, ESPI, and PECI accesses in the order of tasks, the acquisition behavior of different parameters is strictly controlled, thereby improving the stability, timeliness, and execution coordination of the monitoring data among the three types of buses.

[0019] Preferably, the protocol access parsing steps of the PECI bus include: The independent MCU module sends access commands for the digital temperature sensor to the CPU in PECI master control mode; The system receives response frames returned by the CPU in real time and performs parsing processing based on the command field, data field, and verification field contained in the response frame to obtain the corresponding deviation value. Based on a preset offset compensation rule, the deviation value is subjected to temperature conversion calculation to generate the corresponding core temperature parameter, which is then written into the host status parameter set.

[0020] By adopting the above technical solution and using the MCU master control mode to execute the PECI protocol access, the offset value of the digital temperature sensor inside the CPU can be directly read and converted into the actual core temperature through offset compensation rules. This allows the monitoring system to obtain CPU temperature data that is closer to the physical layer and more accurate than traditional software acquisition. This access method reduces the intermediate processing links in the temperature acquisition link, which significantly improves the accuracy, timeliness and reliability of CPU temperature monitoring.

[0021] Preferably, the step of classifying the host status parameter set to divide it into multiple target parameter groups includes: The host status parameter set is classified, and the classification process includes at least type identification, field attribution and correlation analysis, thereby generating the corresponding initial parameter set; Identify anomaly patterns that occur more frequently than a preset frequency threshold in the corresponding historical monitoring period, and determine the corresponding update strategy based on the anomaly patterns; According to the update strategy, the initial parameter group is re-associated and reconstructed to generate a corresponding target parameter group.

[0022] By adopting the above technical solutions, introducing type identification, field attribution and correlation analysis in the parameter classification stage, and determining the classification update strategy by combining the frequency of occurrence of abnormal patterns in historical monitoring cycles, the division of parameter groups evolves from a fixed pattern to an adaptive and optimizable structure. This dynamic reconstruction process based on historical data enables the monitoring system to more accurately distinguish important parameters under different state modes, improving the speed of anomaly identification and the intelligence of the display strategy.

[0023] Preferably, the dynamic adjustment step of the sampling feedback data includes: Based on the sampled feedback data, a mapping vector is determined to characterize the low level of the abnormal state and the trend of parameter changes; Based on the preset sampling mapping relationship table in the initialization running environment, the mapping vector is matched to generate the sampling level information corresponding to the next monitoring cycle; Based on the sampling level information, the sampling period, access frequency of each bus interface, and target parameter accuracy in the independent MCU module are dynamically adjusted to generate corresponding adjustment parameters, and the adjustment parameters are written into the initialization runtime environment to be executed in the next monitoring cycle.

[0024] By adopting the above technical solution, a mapping vector is generated through sampling feedback data, and a preset sampling mapping relationship table is used to determine the sampling level of the next monitoring cycle. This enables the monitoring system to automatically adjust the sampling cycle, bus access frequency, and parameter accuracy based on the current state, achieving an intelligent scheduling mechanism similar to "increasing sampling density when there is high risk and reducing sampling frequency when the situation is stable." This dynamic adjustment method can effectively reduce unnecessary access overhead while ensuring higher quality monitoring data in high-risk scenarios, achieving higher efficiency and more reliable real-time monitoring.

[0025] In summary, this application includes at least one of the following beneficial technical effects: This application eliminates the reliance on the computer's CPU for hardware monitoring. Instead, it utilizes an independently operating MCU control unit to completely decouple the entire process—parameter acquisition, data parsing, status judgment, and information display—from the CPU. This independent MCU module establishes communication links with key components such as memory, SSD, power supply, and CPU via existing motherboard hardware interfaces like USB, SMBus, ESPI, and PECI. It autonomously reads status parameters such as temperature and voltage, performing classification, threshold judgment, and graphical output internally without uploading monitoring data to the CPU for conversion and display. Subsequently, an independent display driver module connected to the MCU and an LCD screen present the monitoring results, allowing the monitoring information to be displayed independently on a secondary screen without consuming resources from the main display. The entire monitoring process, which previously required continuous CPU involvement, is now handled by the MCU, completely freeing the CPU from frequent data acquisition and processing tasks. This prevents system lag, decreased game frame rates, or slowed response times in high-load applications caused by monitoring software consuming CPU resources. Meanwhile, since the monitoring results are displayed on a separate LCD, users can view the hardware status in real time without switching the main screen or interrupting running programs, achieving truly zero-interference monitoring. This effectively solves the problems of monitoring methods consuming CPU resources, affecting host performance, and causing inconvenience due to reliance on the main display, significantly improving the stability, real-time performance, and user experience of the monitoring process. Attached Figure Description

[0026] Figure 1 This is a flowchart of an MCU-based intelligent monitoring system according to one embodiment of this application.

[0027] Figure 2This is a partial circuit diagram of an independent MCU module in an MCU-based intelligent monitoring system according to one embodiment of this application. Figure 1 ; Figure 3 This is a partial circuit diagram of an independent LCD display module in an MCU-based intelligent monitoring system according to one embodiment of this application; Figure 4 This is a partial circuit diagram of an independent MCU module in an MCU-based intelligent monitoring system according to one embodiment of this application. Figure 2 ; Figure 5 This is a partial circuit diagram of an independent MCU module in an MCU-based intelligent monitoring system according to one embodiment of this application. Figure 3 ; Figure 6 This is a partial circuit diagram of a display driver module in an MCU-based intelligent monitoring system according to one embodiment of this application; Figure 7 This is a flowchart of a control method for an MCU-based intelligent monitoring system according to one embodiment of this application. Detailed Implementation

[0028] The present application will be further described in detail below with reference to the accompanying drawings.

[0029] In one embodiment, such as Figures 1-6 As shown, this application discloses an MCU-based intelligent monitoring system, which includes: An independent MCU module communicates with various key components of the computer host via a corresponding bus to obtain the corresponding host status parameter set; The display driver module's enable signal input terminal is connected to the display driver enable terminal of the independent MCU module; An independent LCD display module, the drive input terminal of the independent LCD display module is connected to the drive output terminal of the display driver module, and the display signal input terminal of the independent LCD display module is connected to the display signal output terminal of the independent MCU module; The independent MCU module performs classification processing on the host status parameter set, divides it into corresponding target parameter groups, performs threshold judgment and graphical processing on the parameter groups in sequence, generates corresponding display data, and outputs it to the independent LCD display module through the display signal output terminal of the independent MCU module for secondary screen display push independent of the main display screen.

[0030] In this embodiment, the MCU-based intelligent monitoring system is installed inside the computer host. It achieves real-time acquisition, processing, and independent display of key operating parameters of the host through the functional collaboration of an independent MCU module, a display driver module, and an independent LCD display module. The core control unit of the entire system is the independent MCU module, which directly establishes data communication connections with key components in the host, such as memory modules, solid-state drives, power output channels, and the CPU, via communication buses such as USB, SMBus, ESPI, and PECI located on the motherboard. These various bus interfaces handle access to different types of monitoring parameters, enabling the independent MCU module to autonomously acquire host status parameter sets without CPU intervention. After receiving data from various buses, the MCU module classifies information such as temperature and voltage within its internal processing unit. Using preset feature recognition and field attribution algorithms, it groups similar information into corresponding target parameter groups, allowing subsequent threshold judgment logic to apply different judgment criteria and numerical range filtering for different parameter categories. When the MCU determines that a certain parameter has exceeded the safety threshold or shows an abnormal fluctuation trend, it will generate a corresponding alarm flag internally and use it as the input source for display data in the subsequent graphical drawing stage.

[0031] To enable the collected and processed monitoring information to be displayed in an independent area outside the main display screen, this embodiment further includes a display driver module. The enable signal input terminal of the display driver module is directly electrically connected to the display driver enable terminal of the independent MCU module, allowing the MCU to precisely control the operating state of the display driver module. After the monitoring system completes initialization and enters a stable operating phase, the MCU actively outputs an enable signal to the display driver module, activating the boost control circuit inside the display driver module. This provides the necessary driving voltage and backlight power to the independent LCD display module. The display driver module not only provides a stable, high-brightness backlight output to the LCD screen but also ensures, through voltage conversion and ripple suppression structures, that the display maintains uniform brightness, flicker-free, and jitter-free display effects under varying load fluctuations.

[0032] The independent LCD display module is used to ultimately present the graphical monitoring data processed by the MCU. Its drive input is connected to the drive output of the display driver module via a cable or FPC ribbon cable, receiving the backlight drive voltage from the latter. Its display signal input is connected to the display signal output of the MCU module. After processing the parameters into RGB or other display formats, the MCU module sends a data stream containing information such as temperature, voltage, and alarms to the LCD module through this display signal output. The LCD's internal display controller then drives the pixels, enabling the monitoring data to be displayed on the independent secondary screen. Because the LCD display module is completely independent of the main display screen, the host user can observe the host's operating status in real time through the independent screen without switching the current foreground program or consuming CPU graphics processing power.

[0033] In summary, the independent MCU module is responsible for low-level access, data analysis, and system control; the display driver module is responsible for converting the MCU's drive signals into stable backlight and drive voltage required by the LCD; and the independent LCD display module is responsible for the final display output. These three components work together through clear signal paths and control links, enabling the entire monitoring system to achieve significant advantages such as not consuming CPU resources, fast response speed, and strong independent display capabilities. This effectively solves the problems of traditional software monitoring solutions interfering with CPU operation and affecting user experience.

[0034] Furthermore, the independent MCU module is equipped with a first bus interface, a second bus interface, and a third bus interface. The first bus interface is connected to the memory module and solid-state drive in the computer host via a USB bus and / or an SMBus bus to obtain the corresponding first temperature parameter. The second bus interface is connected to multiple power output channels in the computer host via an ESPI bus to obtain the corresponding voltage parameter. The third bus interface is connected to the CPU in the computer host via a PECI bus to obtain the corresponding second temperature parameter. The host status parameter set is a set of parameters including the first temperature parameter, the second temperature parameter, and the voltage parameter.

[0035] In this embodiment, the independent MCU module integrates a first bus interface, a second bus interface, and a third bus interface, each corresponding to a different communication protocol, to accurately and completely acquire real-time operating parameters from various key components within the computer host. These three interfaces perform different data access functions within the system, collectively forming a multi-protocol acquisition architecture oriented towards the hardware layer of the independent MCU module. This allows the monitoring system to bypass the CPU and directly access the underlying register data of memory, solid-state drives, power modules, and the CPU itself.

[0036] The first bus interface is configured to connect to the USB bus and / or SMBus bus. This interface directly accesses the internal temperature monitoring registers of the memory modules (DIMMs) and solid-state drives (SSDs) via the existing SMBus routing on the motherboard to read the real-time temperature values ​​of each storage device. During SMBus bus access, the MCU accurately locates the corresponding temperature register through address resolution and register read commands, and maps the received temperature information to the first temperature parameter. If the system also supports a USB temperature extension solution, the first bus interface can also communicate with the host's internal USB-TEMP bridge chip via USB, thereby supplementing the SMBus temperature acquisition path with higher bandwidth and lower latency, enhancing the system's ability to acquire the temperature status of the memory. The existence of the first bus interface allows the MCU to directly obtain real temperature monitoring data from storage hardware without CPU intervention, avoiding the inaccurate data problems caused by latency, permissions, or system load in traditional software acquisition.

[0037] The second bus interface is associated with the motherboard power output and communicates with multiple motherboard power output channels via the ESPI bus. As a key bus in the Intel platform for transmitting power management, status information, and board-level control data, ESPI's voltage status information is highly close to the hardware source. Therefore, by accessing the ESPI bus through the second bus interface, the MCU can directly read the real-time voltage values ​​and offsets of multiple voltage output channels such as 12V, 5V, and 3.3V. This interface enables the monitoring system to accurately detect potential risks such as voltage instability and power supply disturbances, and to construct voltage parameter sets in real time from the collected voltage data. Since ESPI is a motherboard-level information channel, direct access significantly improves the accuracy and timeliness of voltage monitoring, giving the monitoring system near-motherboard hardware diagnostic-level voltage detection capabilities.

[0038] The third bus interface is dedicated to accessing CPU internal temperature information via the PECI bus. PECI is a point-to-point digital temperature interface directly provided by the CPU. An independent MCU module establishes a master-slave communication connection with the CPU through the third bus interface and actively initiates read commands from the CPU's internal digital temperature sensor (DTS) in PECI master mode. The temperature offset returned by the CPU is used to construct a second temperature parameter. Because the PECI interface directly maps to the CPU's core temperature information, it is closer to the actual hardware value than traditional software tools that read it through the system interface. Therefore, the existence of the third bus interface enables the monitoring system to obtain extremely high-precision CPU temperature information, significantly improving the reliability of CPU temperature monitoring.

[0039] Furthermore, such as Figure 2 , Figure 4 and Figure 5As shown, the independent MCU module includes a configuration storage chip CSPI1, a main control chip CU8, and a USB interface expansion chip CU7. The first data communication terminal of the main control chip CU8 is connected to the data communication terminal of the configuration storage chip CSPI1, and the second data communication terminal of the main control chip CU8 is connected to the data communication terminal of the USB interface expansion chip CU7.

[0040] In this embodiment, the independent MCU module consists of a configuration storage chip CSPI1, a main control chip CU8, and a USB interface expansion chip CU7. These three components are connected via data communication to form a clearly defined startup and communication link, enabling the entire monitoring system to establish data access capabilities stably and configurably after power-on, while ensuring the compatibility and scalability of the USB channel. The main control chip CU8, as the core processing unit, has its first data communication terminal electrically connected to the configuration storage chip CSPI1. This connection is used to implement the configuration loading process during the system initialization phase. When the computer host powers on and provides operating power to the monitoring system, CU8 immediately reads the pre-stored initialization configuration parameters from CSPI1 through the communication link. These configuration contents typically include bus access timings, register address tables, sampling period settings, display driver logic, threshold tables, and basic parameters required for the main control firmware to run. Because this information is stored in CSPI1 in a fixed manner, CU8 does not need to reload the configuration from an external source each time it starts up, which improves startup speed and gives the system upgradeable, customizable, and maintainable characteristics, ensuring the uniformity and stability of the monitoring process.

[0041] After completing the boot configuration loading, the CU8's second data communication terminal establishes a data connection with the USB interface expansion chip CU7, enabling the independent MCU module to exchange data with the host's internal USB bus via CU7. The USB interface expansion chip CU7 plays a role in protocol adaptation and signal conversion in this structure. It contains multiple USB channel management units to handle the splitting, reassembly, and standardized output of USB data frames, allowing the main control chip CU8 to achieve USB data access capabilities without directly interacting with the complex USB protocol stack. In some monitoring environments, temperature sensors, data bridging units, or some monitoring interfaces implemented by motherboard manufacturers provide data via the USB channel. The presence of CU7 enables CU8 to read such USB monitoring data with higher stability and bandwidth, avoiding communication instability or data frame loss caused by insufficient MCU support for the USB protocol.

[0042] In addition, the CU7 also performs USB signal level conversion and channel expansion functions. When an independent MCU module needs to access multiple USB monitoring devices, USB debugging interfaces, or USB power supply status detection modules, the CU7 can arbitrate and allocate channels for each USB branch according to its internal logic control circuit. This enables the CU8 to complete data management of multiple USB devices without the need for an external dedicated switching circuit, greatly improving the interface expansion capability and hardware compatibility of the monitoring system.

[0043] Furthermore, such as Figure 6 As shown, the display driver module includes a boost driver chip CU6, an inductor CL2, and a diode CD2. The power output terminal of the power supply is connected to the power input terminal of the boost driver chip CU6 and the first terminal of the inductor CL2. The power output terminal of the boost driver chip CU6 and the second terminal of the inductor CL2 are combined into a common node, which is connected to the anode of the diode CD2. The cathode of the diode CD2 is connected to the drive input terminal of the independent LCD display module. The enable input terminal of the boost driver chip CU6 is connected to the display driver enable terminal of the independent MCU module.

[0044] In this embodiment, the display output section of the monitoring system provides a stable and fast-responding backlight power supply to the LCD screen by setting up an independent backlight boost driver module. This backlight driver module consists of a boost driver chip CU6, an inductor CL2, and a diode CD2. Its connection relationship and working logic are closely related to the display driver enable terminal of the independent MCU module, thereby forming a stable backlight power supply link that is actively controlled by the MCU and can adapt to fluctuations in the motherboard power supply. In the overall architecture, the input voltage provided by the power module is first simultaneously input to the power input terminal of the boost driver chip CU6 and the first terminal of the inductor CL2. After receiving the display driver enable signal output from the independent MCU module, the PWM oscillation circuit and the switching transistor inside CU6 immediately enter the working state. Through the high-frequency conduction and turn-off action of the internal MOSFET, the inductor CL2 is in a periodic magnetization and demagnetization process. When the inductor releases its stored energy, an induced voltage higher than the input voltage is generated at the second terminal of the inductor. The boost node is connected to the anode of diode CD2 via the same common node, so that the boosted voltage is rectified through the unidirectional conduction of CD2 and sent to the backlight driver input terminal of the LCD display.

[0045] Diode CD2 not only performs rectification throughout the process but also effectively blocks voltage backflow in the backlight circuit under transient conditions such as voltage drop, PWM stoppage, or load disturbances, utilizing its unidirectional conduction characteristic. This prevents voltage fluctuations at the LCD backlight driver end from negatively impacting the boost driver chip and its preceding circuitry. Since the backlight driver circuit typically requires an operating voltage exceeding 12V, while the motherboard usually provides a 5V or 12V regulated power supply, the boost structure formed by the combination of CU6 and CL2 can meet the higher voltage requirements of the LCD backlight and maintain output stability under load changes, ensuring that the LCD display module's brightness does not flicker or jitter during screen illumination, grayscale changes, and image switching.

[0046] Furthermore, the enable input of the boost driver chip CU6 is directly connected to the display driver enable pin of the independent MCU module, allowing the MCU to freely control the start and stop of the backlight circuit before monitoring data output. For example, the MCU typically outputs an enable signal to CU6 only after completing initialization, self-test procedures, and the first acquisition of monitoring parameters, ensuring that the backlight power supply only starts working after the system officially enters the display stage, thus avoiding damage to the display module caused by voltage instability at power-on. Controlling the start and stop of the backlight driver module via the MCU also enables energy-saving management, such as proactively shutting down the backlight power supply when there are no parameter updates for an extended period or when the device enters a low-power mode, thereby reducing overall power consumption.

[0047] Furthermore, the independent MCU module is connected to the HWmonitor chip via the SMBus bus. The temperature signal input terminal of the HWmonitor chip is connected to a thermistor, and the voltage signal input terminal of the HWmonitor chip is connected to an A / D acquisition unit.

[0048] In this embodiment, to enhance the monitoring system's parameter acquisition capabilities under special operating scenarios and provide the independent MCU module with a more secure and redundant acquisition channel closer to the physical layer in addition to the multi-bus protocol acquisition path, the system also connects to an HWmonitor chip via the SMBus bus for auxiliary acquisition of temperature and voltage parameters. The HWmonitor chip, a commonly used hardware-level sensing and conversion unit in motherboard monitoring systems, integrates a temperature acquisition interface, an A / D conversion channel, a voltage comparison circuit, and a register storage unit. It can continuously capture external analog signals and convert them into digital format independently of the host CPU and the main control MCU, providing the monitoring system with a lower-level physical measurement capability.

[0049] The temperature signal input terminal of the HWmonitor chip is connected to a thermistor placed close to the device under test (DUT). This thermistor's resistance changes with the device's temperature. Through voltage division or constant current bias measurement using the thermistor and the HWmonitor's internal constant current source, a temperature-related analog voltage signal is input to the HWmonitor chip in real time. The HWmonitor then digitizes this analog voltage signal through its internal high-precision analog-to-digital converter, writing the converted temperature data into an internal register. This allows the MCU to directly read the converted digital temperature data without needing to acquire an analog signal, thus providing a temperature monitoring path independent of the SMBus device's built-in temperature register. When the temperature acquisition point on the motherboard is far from the DUT or the SMBus device is temporarily offline, the temperature data acquired by the HWmonitor can provide additional monitoring data for the system.

[0050] Meanwhile, the voltage signal input terminal of the HWmonitor chip is connected to the monitored power node via an A / D acquisition unit, typically from the 12V, 5V, or 3.3V power rails of the motherboard. The A / D acquisition unit uses external circuitry such as resistor dividers, filters, and overvoltage protection to condition the voltage from the power rails, ensuring the signal amplitude matches the input range of the HWmonitor's internal A / D converter. This allows for the stable acquisition and conversion of real-time voltage changes from the power rails into digital voltage values. The MCU reads this digital voltage data from the HWmonitor via the SMBus bus, guaranteeing the integrity of voltage monitoring even when the motherboard power supply does not expose all its states via the ESPI bus. This acquisition structure provides the monitoring system with "dual-path" voltage acquisition capabilities, allowing it to obtain critical voltage information from the HWmonitor even when the ESPI channel malfunctions, the bus is occupied, or there is a scheduling delay, thus improving the overall robustness of the monitoring system in complex hardware environments.

[0051] The independent MCU module periodically accesses the temperature and voltage registers of the HWmonitor via SMBus, actively reading the converted digital parameters according to a preset sampling interval. It then writes the data output by the HWmonitor, along with temperature and voltage parameters obtained from other bus acquisition paths, into the host status parameter set, making it an integral part of the multi-source data fusion process. This architecture not only enhances the reliability of the monitoring system, allowing it to maintain a certain level of monitoring capability even when a channel in SMBus, ESPI, or PECI experiences a temporary anomaly, but also, by introducing a physical layer analog-to-digital conversion mechanism, enables the system to achieve higher anomaly identification accuracy and better environmental adaptability.

[0052] like Figure 7As shown, a control method for an MCU-based intelligent monitoring system is applied to such a system. The control method includes: S10. Obtain initialization configuration information and construct the initialization runtime environment for the preset monitoring process based on the initialization configuration information. The initialization configuration information can be understood as a set of operating parameters loaded by the main control chip after the system is powered on or reset. This set of parameters is usually stored in non-volatile memory and is used to specify the initial behavior of the monitoring system, including the access timing of various buses, sampling period, threshold conditions, display rules, protocol parsing table, and error handling strategies. The existence of the initialization configuration information enables the monitoring system to complete all necessary configuration preparations before the device officially starts working, thereby ensuring that the monitoring process has a stable operating foundation and a complete protocol stack when entering the first monitoring cycle. The initialization runtime environment constructed based on this initialization configuration information is a set of working states generated by the main control chip during the startup phase according to the configuration content. This includes the allocation of bus access resources, the establishment of the buffer area, the refreshing of parameter registers, the activation of display logic, and the initialization of the state machine, enabling the entire system to enter the ready state for executing monitoring tasks from the unworking state.

[0053] S20. In the initialization environment, protocol access and parsing are performed through the corresponding bus interface to obtain the host status parameter set for the current monitoring cycle. The corresponding bus interface refers to the hardware communication port on the independent MCU module used to access different hardware devices of the host. It usually includes the corresponding SMBus interface, ESPI interface, and PECI interface. Each interface establishes a communication link with different types of hardware targets to access low-level parameters such as temperature and voltage. Protocol access and parsing refers to the actual communication process executed by the MCU when accessing the above bus interfaces. This includes initiating commands, reading registers, parsing response data frames, verifying data validity, and converting raw data into parameter values ​​that can be used for monitoring and analysis. This parsing process involves not only data format conversion but also unpacking, converting, and standardizing the data according to the structure of different protocols, so that temperature and voltage information obtained from different hardware can be written into the host status parameter set in a unified data format. The host status parameter set is a data set consisting of all hardware monitoring data collected by the MCU in each monitoring cycle. It usually includes the temperature value of the digital temperature sensor inside the CPU, the temperature information of the memory and solid-state drive, and the real-time voltage level of the motherboard voltage rail. Each data source corresponds to a different bus acquisition path. This parameter set not only records real-time values, but may also include the rate of change of the previous period, valid identification information, and sampling error information, which are used to support subsequent classification and judgment logic.

[0054] S30. Classify the host status parameter set to divide it into multiple target parameter groups. Classification is the process by which the MCU organizes the data in the host status parameter set according to set rules. These rules can be based on parameter category, hardware type, anomaly sensitivity, historical trend, or system-defined display strategy. For example, temperature data from CPUPECI and voltage data from the VRM module may be grouped into the same group affecting CPU stability; while temperatures from the SSD and memory modules may constitute another parameter association group. The target parameter groups divided through classification are the sets of parameters that need to be focused on during the monitoring period or that need to participate in subsequent threshold judgments. These sets are assigned different analysis and display priorities according to their category or purpose.

[0055] S40. The target parameter group is sequentially subjected to threshold judgment and graphical processing to generate corresponding display data and determine corresponding sampling feedback data. The display data is used for secondary screen display push independent of the main screen, and the sampling feedback data is used to dynamically adjust the sampling parameters for the next monitoring cycle. Threshold judgment is the process by which the MCU analyzes the data in each target parameter group through pre-set safety ranges or risk conditions, such as whether a certain temperature exceeds the warning limit, whether a certain voltage deviates from the target range, or whether the rate of change of a certain parameter exceeds the allowable range. Once a parameter group triggers the threshold condition, the system will generate a corresponding alarm mark and enter the graphical processing stage. Graphical processing refers to the MCU generating a visual data format that can be presented on the LCD secondary screen based on the judgment result of the target parameter group. This format may include color marks, dynamic icons, curve data, numerical information, or warning symbols, allowing users to directly read the hardware status through an independent screen. The display data is the final visual content generated after graphical processing. It will be transmitted to the LCD module through the MCU's display signal output terminal to achieve a secondary screen display that is completely independent of the main display screen, ensuring that users can view the hardware operating status without switching the main interface.

[0056] Sampling feedback data is a set of feedback information generated by the system after threshold judgment, based on the acquisition quality, parameter fluctuations, or abnormal triggering events of the current cycle. This information guides the adjustment of sampling parameters for the next monitoring cycle. For example, if a large fluctuation in CPU temperature is detected in a certain cycle, the sampling feedback data will increase the sampling frequency for the next cycle; if all parameters are stable in the current cycle, the sampling feedback data may reduce the access frequency of certain buses to reduce system load. Sampling parameters are operating parameters automatically adjusted based on the sampling feedback data, including the sampling interval for the next cycle, the priority of each bus access task, sampling accuracy, and cache behavior, creating a dynamic closed loop in the monitoring process.

[0057] Furthermore, the step of obtaining the host status parameter set for the current monitoring period by parsing the protocol through the corresponding bus interface includes: S201. Extract the corresponding priority rules and access arbitration strategy from the initialization runtime environment. Priority rules can be understood as the order control strategy used by the monitoring system when executing different bus access tasks. These rules are usually pre-set in the initialization runtime environment to define the sequential execution architecture of various protocol access tasks within the same monitoring cycle. The design of priority rules is typically based on the sensitivity and real-time requirements of different hardware parameters. For example, the rate of change of CPU temperature is much higher than that of memory temperature or power supply voltage. Therefore, the corresponding PECI access task usually needs to be assigned a higher priority, while SMBus tasks related to memory temperature can be scheduled for later execution to ensure that the critical path of monitoring receives sufficient response. The access arbitration strategy is an internal system mechanism used to coordinate the queuing, conflict detection, and timing control of various bus access tasks at the physical bus level. This strategy handles the scheduling logic when multiple protocols simultaneously compete for bus resources. By detecting the bus busy / idle status, setting retry time slices, or executing backoff delays, it avoids access conflicts, ensuring that the monitoring process always proceeds stably in a controlled manner.

[0058] S202. Determine the execution order of each protocol access based on priority rules; S203. When the current monitoring cycle is triggered, the busy / idle status of each bus is detected according to the access arbitration policy. If a corresponding bus is detected to be occupied, the corresponding backoff process is executed according to the access arbitration policy. Triggering the current monitoring cycle refers to the system starting a new round of monitoring tasks after a preset sampling interval is reached or a certain type of state change event is detected. For example, completing data processing of the previous cycle and preparing to enter the access process of the next cycle. After the trigger action is executed, the independent MCU module first detects the current occupancy status of buses such as SMBus, ESPI, and PECI according to the access arbitration policy. It reads the corresponding busy / idle flags through the internal bus monitoring module. If a bus is detected to be occupied by other controllers or internal management logic, the backoff process logic is executed to perform delay waiting, priority adjustment, or task postponement to ensure that access is not forcibly initiated when the bus is busy, which could lead to data errors or communication failures. Backoff processing typically includes incremental delays, exponential backoff, or automatic retries within a limited number of attempts, enabling the entire monitoring system to maintain stable operation when bus resources are scarce.

[0059] S204. If no corresponding bus is detected as occupied, the corresponding access tasks are scheduled sequentially according to the execution order. Specifically, SMBus bus access is used to acquire temperature parameters of the memory module and solid-state drive; ESPI bus access is used to acquire voltage parameters of multiple power output channels; and PECI bus access is used to parse the CPU's DTS temperature data to form a complete set of host status parameters for the current monitoring cycle. The execution order refers to the arrangement of access tasks determined by the system according to priority rules. Therefore, when the bus is idle, the MCU will strictly schedule the access tasks in the execution order. SMBus bus access corresponds to reading the temperature registers exposed inside the memory module and solid-state drive, submitting a temperature acquisition request through standardized register access commands, and parsing the return value to enable the system to acquire the operating temperature of the storage devices. ESPI bus access corresponds to acquiring the real-time voltage output of the motherboard power supply, obtaining the operating status of each power rail (e.g., 12V, 5V, 3.3V) by accessing the register data of the motherboard power management controller, thereby monitoring power stability. PECI bus access corresponds to reading the DTS offset value from the CPU's internal digital temperature sensor and parsing it to obtain the CPU core temperature, achieving highly accurate temperature monitoring by directly accessing the CPU physical layer temperature data source.

[0060] For example, at the start of an actual monitoring cycle, the system first determines PECI as the highest priority based on the priority rules loaded during the initialization of the runtime environment, followed by ESPI, and finally SMBus. The system then triggers the monitoring cycle and checks the status of each bus according to the access arbitration policy. If the PECI bus is detected as idle, CPU temperature acquisition can be performed immediately. If the ESPI bus is found to be temporarily busy during PECI access, the system delays the voltage acquisition task according to the backoff policy until the bus is released before continuing access. After completing the first two access tasks, SMBus access is performed to obtain memory temperature. Finally, all collected data is combined into a complete host status parameter set for this cycle for subsequent classification and display processing, thus achieving a structured, prioritized, and conflict-avoidance-enabled complete monitoring data acquisition process.

[0061] Furthermore, the protocol access parsing steps for the PECI bus include: The independent MCU module sends access commands for the digital temperature sensor to the CPU in PECI master control mode; The system receives response frames returned by the CPU in real time and performs parsing processing based on the command field, data field, and verification field contained in the response frame to obtain the corresponding deviation value. Based on the preset offset compensation rules, the deviation value is converted into a temperature value to generate the corresponding core temperature parameter, which is then written into the host status parameter set.

[0062] The PECI bus protocol access and parsing process is based on an independent MCU module acting as the bus master device. The so-called PECI master mode refers to the MCU actively initiating communication by sending specific temperature read commands to the CPU and being responsible for the entire communication session's initiation, data request, timing control, and data verification. Since PECI is a point-to-point digital temperature interface directly exposed by the CPU, the digital temperature sensor access command sent by the MCU in master mode is a hardware-level access instruction expressed in a specific data frame format. It requests the CPU's internal digital temperature sensor to return offset data representing the current core temperature. This command, following the PECI protocol format, consists of multiple bytes, including the target device address, operation type, and requested data length, enabling the CPU to correctly identify the request and return the corresponding response data.

[0063] The response data returned by the CPU after executing a command is provided to the MCU in the form of a response frame. This response frame consists of multiple protocol fields, including a command field, a data field, and a checksum field. The command field indicates the correspondence between this response and the previously sent access command, allowing the MCU to confirm that the received data belongs to the current access session. The data field contains the deviation value output by the CPU's internal digital temperature sensor. This deviation value is typically a negative temperature offset, representing the difference between the CPU core's current temperature and its maximum allowable junction temperature. The checksum field verifies whether any errors occurred during data transmission. It can use CRC checksum or a protocol-defined checksum method, allowing the MCU to determine the validity of the response frame based on the checksum result. If the checksum passes, the MCU will continue with the subsequent parsing process.

[0064] Offset compensation rules are the calculation rules used by the MCU to recover the true core temperature after obtaining the deviation value. Since PECI does not return the direct temperature, but rather the offset obtained by subtracting the current temperature from Tjmax, the MCU performs temperature recovery calculations based on a preset compensation algorithm and the monitored CPU's Tjmax parameter, converting the deviation value into a usable core temperature parameter. This temperature conversion process includes not only offset compensation but may also include filtering, outlier suppression, and numerical normalization steps, making the obtained core temperature parameters more stable and accurate. The core temperature parameter is ultimately written into the host status parameter set, forming a complete monitoring data set for that monitoring period together with temperature, voltage, current, and other parameters collected through SMBus, ESPI, or other interfaces during the same period. This supports subsequent system classification, threshold judgment, and graphical display.

[0065] For example, in one operating cycle, the MCU sends an access command to "read CPUDTS temperature" in PECI master control mode. A few microseconds later, the CPU returns a response frame containing a command field, a data field, and a checksum field. The deviation value in the data field is assumed to be 0xD5. Combined with the current CPU's Tjmax (assumed to be 100°C), the actual core temperature is calculated to be approximately 43°C using offset compensation rules. The MCU then writes this temperature value, along with the memory temperature and power supply voltage collected in the same cycle, into the host status parameter set, thus completing a full hardware monitoring and acquisition task.

[0066] Furthermore, the step of classifying the host status parameter set and dividing it into multiple target parameter groups includes: S301. Classify the host status parameter set. The classification process includes at least type identification, field attribution, and correlation analysis, and then generate the corresponding initial parameter set. S302. Determine the abnormal patterns that occur more frequently than the preset frequency threshold in the corresponding historical monitoring period, and determine the corresponding update strategy based on the abnormal patterns. S303. According to the update strategy, the initial parameter group is re-associated and reconstructed to generate the corresponding target parameter group.

[0067] Classification processing is a logical step of splitting and organizing raw parameters according to their functional attributes, hardware sources, and influence paths. In this process, type identification is used to determine whether a parameter belongs to different technical dimensions such as temperature, voltage, current, or status, enabling the system to determine the parameter type based on a unified standard. Field attribution involves classifying parameters according to their source hardware module or monitoring purpose. For example, voltage fields from a VRM power module and CPU temperature fields may need to be grouped together to analyze CPU load status. Correlation analysis involves the system calculating the logical or physical relationships between different parameters based on historical trends, mutual influence relationships, or multi-parameter coupling patterns, allowing related parameters to be combined into the same analysis set. By executing the above steps, a clearly structured initial parameter set is generated. This is the result of the first structuring of the raw data, providing a foundation for subsequent filtering strategies and reconstruction.

[0068] Historical monitoring periods refer to the sequence of monitoring data recorded by the system over multiple consecutive monitoring periods in the past, used to reflect the behavioral trends of hardware within a certain time range. Anomaly patterns occurring more frequently than a preset frequency threshold refer to specific abnormal states (such as CPU temperature consistently exceeding a certain threshold, power supply voltage fluctuations, or a significant upward trend in storage temperature) occurring at a certain proportion in these historical monitoring periods, indicating their persistence, regularity, or significant impact. The system establishes an update strategy by identifying these anomaly patterns. This strategy guides the system on how to adjust the initial parameter set to more specifically identify potential problems within the current monitoring period. For example, if a certain anomaly pattern occurs frequently, the strategy will increase the weight, correlation, or sampling priority of related parameters, placing them in a more stringent monitoring path within the current monitoring period.

[0069] Guided by the update strategy, the system re-associates and reconstructs the initial parameter set. This process further optimizes the initial classification results to adapt to parameter coupling patterns revealed during long-term monitoring. For example, parameters originally belonging to different groups may be recombined due to high correlation observed in historical anomalies, while some redundant fields may be removed according to the strategy, thus generating a target parameter set that more closely reflects the actual monitoring needs of the system. The target parameter set is the final dataset used for threshold judgment, graphical output, and risk identification. After reconstruction, it possesses higher compactness, relevance, and analytical value, enabling subsequent logic to more accurately reflect the host's operating status.

[0070] Furthermore, the dynamic adjustment steps for the sampling feedback data include: Based on the sampled feedback data, a mapping vector is determined to characterize the low level of the abnormal state and the trend of parameter changes; Based on the preset sampling mapping relationship table in the initialization running environment, the mapping vector is matched to generate the sampling level information corresponding to the next monitoring cycle; Based on the sampling level information, the sampling period, access frequency of each bus interface, and target parameter accuracy in the independent MCU module are dynamically adjusted to generate corresponding adjustment parameters, which are then written into the initialization runtime environment for execution in the next monitoring cycle.

[0071] In this embodiment, the sampling feedback data is a set of feedback information formed by the monitoring system at the end of the current monitoring cycle, consisting of threshold judgment results, parameter fluctuation values, abnormal trigger information, and the sampling performance evaluation of the previous cycle. This feedback data is used to reflect the stability and data change characteristics of the sampling behavior in this cycle. The sampling feedback data includes judgment information for low-level abnormal states. A low-level abnormal state means that although the trigger warning threshold has not been reached, the relevant parameters have shown a significant trend of change or a slight deviation compared to the previous cycle, such as an accelerated increase in temperature or slight instability in voltage, enabling the system to respond in advance at the early stage of abnormal states. The parameter change trend is the trend result calculated by the system after analyzing the numerical differences, change slopes, and short-term fluctuation amplitudes between the parameters of the current cycle and the parameters of several past cycles. It is used to reflect whether the parameters are in an upward, downward, or stable state, and to assess the possible future development direction.

[0072] The mapping vector is a structured data vector generated from sampled feedback data after feature extraction. It describes multiple dimensions of features such as anomaly level, trend of change, and parameter sensitivity, enabling the system to map actual monitoring performance to a preset sampling scheduling strategy in a unified format. The sampling mapping relationship table is a set of pre-set relationship tables based on the built-in strategy model in the initialization runtime environment. It associates different types of mapping vectors with corresponding sampling level information, allowing the system to automatically look up the table to determine the sampling intensity for the next cycle based on the current monitoring performance. The sampling level information is a level identifier generated by the system based on the matching results, used to define the sampling strategy for the next monitoring cycle. It may include high-frequency, medium-frequency, or low-frequency sampling levels, and specifies the fine-grained sampling requirements for each level.

[0073] Based on sampling level information, the system dynamically adjusts several key sampling parameters in the independent MCU module, including the sampling period, the access frequency of each bus interface, and the precision of target parameters. The sampling period controls how often the MCU triggers the monitoring process; changing the sampling period can extend or shorten the monitoring cycle. The access frequency adjusts the number of times different buses (such as SMBus, ESPI, and PECI) are accessed in the next cycle, used to increase the sampling density of key parameters or reduce the sampling load of non-key parameters. Parameter precision is achieved by adjusting the sampling bit width, filtering strength, or multiple sampling averaging mechanism, enabling the system to improve the sampling fineness of certain parameters when needed, such as increasing the sampling bit resolution of PECI data when CPU temperature changes rapidly. The adjusted parameters form a complete configuration data set after the above adjustments, containing all the strategy information required for the next cycle's sampling behavior. These adjusted parameters are written into the initialization runtime environment, allowing the next monitoring cycle to execute directly according to the new strategy upon startup, achieving adaptive adjustment and dynamic optimization of the monitoring process.

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

Claims

1. An intelligent monitoring system based on an MCU, characterized in that, The aforementioned MCU-based intelligent monitoring system includes: An independent MCU module communicates with various key components of the computer host via a corresponding bus to obtain the corresponding host status parameter set; The display driver module has its enable signal input terminal connected to the display driver enable terminal of the independent MCU module. An independent LCD display module, wherein the driving input terminal of the independent LCD display module is connected to the driving output terminal of the display driving module; The independent MCU module performs classification processing on the host status parameter set, divides it into corresponding target parameter groups, performs threshold judgment and graphical processing on the parameter groups in sequence, generates corresponding display data, and outputs it to the independent LCD display module for secondary screen display push independent of the main display screen.

2. The MCU-based intelligent monitoring system according to claim 1, characterized in that, The independent MCU module is equipped with a first bus interface, a second bus interface, and a third bus interface. The first bus interface is connected to the memory module and solid-state drive in the computer host via a USB bus and / or an SMBus bus to obtain the corresponding first temperature parameter. The second bus interface is connected to multiple power output channels in the computer host via an ESPI bus to obtain the corresponding voltage parameter. The third bus interface is connected to the CPU in the computer host via a PECI bus to obtain the corresponding second temperature parameter. The host status parameter set is a set of parameters for the first temperature parameter, the second temperature parameter, and the voltage parameter.

3. The MCU-based intelligent monitoring system according to claim 1, characterized in that, The independent MCU module includes a configuration storage chip CSPI1, a main control chip CU8, and a USB interface expansion chip CU7. The first data communication terminal of the main control chip CU8 is connected to the data communication terminal of the configuration storage chip CSPI1, and the second data communication terminal of the main control chip CU8 is connected to the data communication terminal of the USB interface expansion chip CU7.

4. The MCU-based intelligent monitoring system according to claim 1, characterized in that, The display driver module includes a boost driver chip CU6, an inductor CL2, and a diode CD2. The power output terminal of the power supply is connected to the power input terminal of the boost driver chip CU6 and the first terminal of the inductor CL2. The power output terminal of the boost driver chip CU6 and the second terminal of the inductor CL2 are combined into a common node, which is connected to the anode terminal of the diode CD2. The cathode terminal of the diode CD2 is connected to the drive input terminal of the independent LCD display module. The enable input terminal of the boost driver chip CU6 is connected to the display driver enable terminal of the independent MCU module.

5. The MCU-based intelligent monitoring system according to claim 4, characterized in that, The independent MCU module is connected to an HW monitor chip via an SMBus bus. The temperature signal input terminal of the HW monitor chip is connected to a thermistor, and the voltage signal input terminal of the HW monitor chip is connected to an A / D acquisition unit.

6. A control method for an intelligent monitoring system based on an MCU, characterized in that, Applied to an MCU-based intelligent monitoring system as described in any one of claims 1-5, the control method includes: Obtain initialization configuration information, and construct the initialization runtime environment for the preset monitoring process based on the initialization configuration information; In the initialization running environment, protocol access and parsing are performed through the corresponding bus interface to obtain the host status parameter set for the current monitoring period; The host status parameter set is classified and divided into multiple target parameter groups; The target parameter group is sequentially subjected to threshold judgment and graphical processing to generate corresponding display data and determine corresponding sampling feedback data. The display data is used for secondary screen display push independent of the main screen, and the sampling feedback data is used to dynamically adjust the sampling parameters for the next monitoring cycle.

7. The control method for an MCU-based intelligent monitoring system according to claim 6, characterized in that, The step of obtaining the host status parameter set for the current monitoring period by performing protocol access parsing through the corresponding bus interface includes: Extract the corresponding priority rules and access arbitration strategies from the initialization runtime environment; The execution order of each protocol access is determined based on the aforementioned priority rules; When the current monitoring cycle is triggered, the busy / idle status of each bus is detected according to the access arbitration policy, and when the corresponding bus is detected to be occupied, the corresponding backoff process is executed according to the access arbitration policy. If no corresponding bus is detected to be occupied, the corresponding access tasks are accessed sequentially according to the execution order. Among them, SMBus bus access is used to obtain the temperature parameters of memory modules and solid-state drives, ESPI bus access is used to obtain the voltage parameters of multiple power output channels, and PECI bus access is used to parse the CPU's DTS temperature data to form a complete set of host status parameters for the current monitoring cycle.

8. The control method for an MCU-based intelligent monitoring system according to claim 7, characterized in that, The protocol access and parsing steps of the PECI bus include: The independent MCU module sends access commands for the digital temperature sensor to the CPU in PECI master control mode; The system receives response frames returned by the CPU in real time and performs parsing processing based on the command field, data field, and verification field contained in the response frame to obtain the corresponding deviation value. Based on a preset offset compensation rule, the deviation value is subjected to temperature conversion calculation to generate the corresponding core temperature parameter, which is then written into the host status parameter set.

9. The control method for an MCU-based intelligent monitoring system according to claim 6, characterized in that, The step of classifying the host status parameter set and dividing it into multiple target parameter groups includes: The host status parameter set is classified, and the classification process includes at least type identification, field attribution and correlation analysis, thereby generating the corresponding initial parameter set; Identify anomaly patterns that occur more frequently than a preset frequency threshold in the corresponding historical monitoring period, and determine the corresponding update strategy based on the anomaly patterns; According to the update strategy, the initial parameter group is re-associated and reconstructed to generate a corresponding target parameter group.

10. The control method for an MCU-based intelligent monitoring system according to claim 6, characterized in that, The dynamic adjustment steps for the sampling feedback data include: Based on the sampled feedback data, a mapping vector is determined to characterize the low level of the abnormal state and the trend of parameter changes; Based on the preset sampling mapping relationship table in the initialization running environment, the mapping vector is matched to generate the sampling level information corresponding to the next monitoring cycle; Based on the sampling level information, the sampling period, access frequency of each bus interface, and target parameter accuracy in the independent MCU module are dynamically adjusted to generate corresponding adjustment parameters, and the adjustment parameters are written into the initialization runtime environment to be executed in the next monitoring cycle.

Images