Multi-protocol remote controller tuner compatible method

Abstract

The invention relates to the technical field of remote controllers, in particular to a multi-protocol remote controller tuner compatible method, which comprises the following steps of: loading multi-protocol parameters and analysis rules, synchronously receiving protocol data by multiple channels, preferentially scanning a safety instruction, monitoring MCU (Microprogrammed Control Unit) computing power in real time, calculating a data change rate, converting an instruction format and transmitting. Through priority scheduling, the security instruction is set as the highest preemptive priority, the problem that the security instruction is blocked by common data is solved, and instant response of an emergency protection function is ensured; by monitoring the computing power of the MCU in real time, performing full parallel analysis when the MCU is not saturated, and allocating fixed computing power to a main control protocol and a standby protocol when the MCU is saturated, computing power saturation caused by multi-protocol parallel is avoided, and single-frame processing delay is reduced; by dynamically adjusting the size of the sliding window according to the data change rate, the problem of decision lag caused by an overlarge window is solved, and both the data stability of a low-dynamic scene and the response timeliness of a high-dynamic scene are considered.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of remote control, in particular to a multi-protocol remote control high-frequency head compatibility method. BACKGROUND

[0002] Remote control has strict requirements for control instruction processing delay, and multi-protocol parallel analysis may saturate MCU computing power, and single-frame processing delay may increase. The safety instructions of the control device are encoded differently in different protocols (such as the "FAILSAFE" frame of FrSky and the "EMERGENCY STOP" instruction of DJI), and if the compatibility method does not set the highest priority for the safety instruction, it may be blocked by ordinary control data, resulting in failure to trigger protection in an emergency.

[0003] In a high dynamic scene of the device, the dynamic change of dual-protocol data (such as the main control protocol + backup protocol) is fast, and if the data smoothing algorithm (such as the sliding window) window is too large, it will cause decision lag and fail to adapt in time. SUMMARY

[0004] The purpose of the present application is to provide a multi-protocol remote control high-frequency head compatibility method to solve the problems raised in the background art.

[0005] In order to solve the above technical problems, the present application provides the following technical solutions: The multi-protocol remote control high-frequency head compatibility method comprises the following steps: Load multi-protocol parameters and analysis rules, set the safety instruction as the highest priority, the ordinary control instruction as the second priority, and the protocol identifier as the lowest priority, and initialize the initial size of the sliding window, the data change rate threshold, and the MCU computing power saturation threshold; Synchronously receive each protocol data through multiple channels, filter valid data through frame header identification and CRC check, store them in the buffer according to the protocol and record the time stamp; Scan the safety instruction first, pause the ordinary data processing immediately after detection, and output directly after analysis; when there is no safety instruction, read the ordinary instruction according to the principle that "the main control protocol is prior to the backup protocol"; Monitor the MCU computing power in real time, and analyze in parallel when it is not saturated; when it is saturated, allocate fixed computing power to the main control protocol and the backup protocol; Calculate the data change rate, and maintain a certain number of frame windows for smoothing processing when it is less than or equal to the first threshold; when it is greater than the first threshold, adjust it to 1 frame window for direct output, and restore the initial window when there are continuous frames of low dynamics; Convert the instruction format and transmit it, record the processing time and the computing power occupation rate, and update the configuration parameters for the next round of optimization.

[0006] Further, the loading of multi-protocol parameters and parsing rules, specifically, after the high-frequency head is powered on, the MCU automatically loads the preset multi-protocol configuration file to configure the frame structure parameters, exclusive parsing rules and communication baud rate of the target compatible protocol, and determines the execution basis of subsequent data receiving and parsing.

[0007] Further, the safety instruction is set as the highest priority, the ordinary control instruction is set as the second priority, and the protocol identifier is set as the lowest priority, specifically, an initialization priority scheduling table is set, the safety instruction of each compatible protocol is marked as the highest priority, the ordinary control instruction is set as the second priority, and the protocol identifier is set as the lowest priority; it is determined that the highest priority instruction has pre-emptive execution authority and can interrupt low-priority data processing; the second priority instruction is parsed when there is no highest priority instruction, and the lowest priority instruction is processed only when there is no higher priority data, thereby ensuring that the safety instruction is responded preferentially.

[0008] Further, the initialization of the sliding window initial size, the data change rate threshold and the MCU computing power saturation threshold, specifically, the core configuration parameters of the data smoothing algorithm are initialized, including the sliding window initial size, the data change rate threshold and the MCU computing power saturation threshold, the scene judgment criteria corresponding to each threshold are determined, and these parameters are stored in the system configuration register, so that the subsequent data processing and computing power scheduling links can directly call, and clear judgment basis is provided for the related dynamic adjustment logic.

[0009] Further, the multi-channel synchronous receiving of each protocol data, the frame header identification, the CRC check screening of valid data, the storage of the valid data in the buffer according to the protocol classification and the recording of the time stamp, specifically, the high-frequency head receives multi-protocol data through independent multi-channel parallel receiving, and then the valid data is screened through frame header identification, CRC check and length verification, and the invalid data is removed, then the protocol identifier field in the valid data is extracted, the data is classified and stored in the independent buffer of the corresponding protocol to avoid interference, and the receiving completion time of each frame of valid data is recorded based on the MCU system clock, thereby providing an accurate time reference for subsequent related processing.

[0010] Further, the priority scanning of the safety instruction, the immediate suspension of the ordinary data processing after detection, and the direct output after parsing, specifically, the scheduling module scans each protocol independent buffer according to the preset period, identifies the highest priority safety instruction feature identifier according to the priority scheduling table, triggers the pre-emptive execution mechanism after detection, suspends the current second priority ordinary control instruction processing, calls the exclusive parsing module to parse according to the corresponding protocol rules, extracts the core parameters to generate standardized execution instructions, and directly sends the standardized execution instructions to the transmitting module without subsequent data smoothing processing, and records the complete processing time of the safety instruction and stores it in the state feedback log.

[0011] Furthermore, when no security instructions are available, ordinary instructions are read according to the principle of "primary control protocol takes precedence over backup protocol". Specifically, when no security instructions are available, the scheduling module prioritizes reading ordinary control instructions from the primary control protocol according to preset rules, processes them in the order of data reception timestamps, and monitors the validity and continuity of the primary control protocol data. If the primary control protocol data is abnormal, the system seamlessly switches to the backup protocol to read the data, ensuring that the output of control instructions is not interrupted. At the same time, the system records relevant protocol processing information to provide a reference for subsequent priority scheduling and computing power allocation optimization.

[0012] Furthermore, the real-time monitoring of MCU computing power involves full parallel parsing when not saturated, and allocating fixed computing power to the main control protocol and backup protocol when saturated. Specifically, the MCU computing power monitoring module collects core computing load, parsing task duration, and queue backlog in real time, calculates computing power utilization, and synchronizes it to the scheduling module and configuration register. When not saturated, the full parallel parsing mode is activated, allocating independent threads to each protocol to synchronously parse ordinary control instructions. When saturated, computing power is allocated to the main control protocol and backup protocol according to preset rules, the parsing frequency of the backup protocol is adjusted, and computing power changes are monitored in real time. Once the computing power drops below the threshold, the full parallel mode is restored, and relevant data is recorded and included in the status feedback to provide a basis for subsequent computing power scheduling optimization.

[0013] Furthermore, the calculated data change rate is maintained for smoothing through several frames when it is less than or equal to a first threshold; when it is greater than the first threshold, it is adjusted to output directly through a 1-frame window; and the initial window is restored when there are several consecutive low dynamic frames. Specifically, the data change rate is calculated based on standardized data and the received timestamp, and the sliding window size is adjusted according to the scenario in which the change rate is located. In low dynamic scenarios, the initial window is maintained for smoothing, and in high dynamic scenarios, the data is output directly through a 1-frame window. When the scenario is continuously in a low dynamic scenario, the initial window is restored. During the process, the change rate, window adjustment status, and triggering reason are recorded and linked with the status feedback data to provide a basis for subsequent optimization of smoothing algorithm parameters.

[0014] Furthermore, the conversion of instruction format and transmission, recording of processing time and computing power utilization, and updating of configuration parameters for the next round of optimization are specifically as follows: matching the corresponding protocol output format according to the instruction type, converting standardized data into the target protocol frame structure, and sending it to the controlled device through the transmission module; synchronously collecting key information such as instruction processing time and computing power utilization, integrating them to form status feedback data and archiving it; optimizing relevant parameters based on feedback data, updating to the system configuration register, providing optimization basis for the next round of data processing, and forming a closed-loop optimization mechanism.

[0015] Compared with existing technologies, this invention has the following advantages: This application solves the problem of security instructions being blocked by ordinary data by prioritizing scheduling, ensuring immediate response of emergency protection functions; by monitoring MCU computing power in real time, it performs full parallel parsing when not saturated and allocates fixed computing power to the main control and backup protocols when saturated, avoiding computing power saturation caused by multiple protocols running in parallel and reducing single-frame processing latency; by dynamically adjusting the sliding window size according to the data change rate, it switches to direct output of a single-frame window in high-dynamic scenarios, solving the decision lag caused by excessively large windows, balancing data stability in low-dynamic scenarios and response timeliness in high-dynamic scenarios; simultaneously, based on the seamless switching between the main control protocol and backup protocols and the closed-loop parameter optimization mechanism, it ensures the continuity of control instruction output, further optimizing processing efficiency and adaptability, and comprehensively addressing the core technical pain points mentioned in the background. Attached Figure Description

[0016] Figure 1 This is a flowchart of the multi-protocol remote control high-frequency head compatibility method of the present invention. Detailed Implementation

[0017] The technical solutions of the present invention will be clearly and completely described below with reference to the embodiments and accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] This application discloses a method for multi-protocol remote control LNB compatibility, such as... Figure 1 As shown, the steps include: Load multi-protocol parameters and parsing rules, set security commands as the highest priority, ordinary control commands as the second highest priority, and protocol identifiers as the lowest priority, and initialize the initial size of the sliding window, the data change rate threshold, and the MCU computing power saturation threshold; The system receives data from various protocols synchronously through multiple channels. After frame header identification and CRC check to filter valid data, it is classified according to protocol, stored in the buffer, and timestamp is recorded. Prioritize scanning for security commands. Upon detection, immediately pause normal data processing, parse the data, and output it directly. If no security commands are found, read normal commands according to the principle of "master protocol takes precedence over backup protocol". Real-time monitoring of MCU computing power; full parallel analysis when not saturated; fixed computing power allocated to the main control protocol and backup protocol when saturated. Calculate the rate of change of data. If it is less than or equal to the first threshold, maintain a smooth processing window for several frames. If it is greater than the first threshold, adjust to output directly with a 1-frame window. When there are several consecutive frames of low dynamics, restore the initial window. Convert the instruction format and issue it, record the processing time and computing power utilization, and update the configuration parameters for the next round of optimization.

[0019] In practice, loading multi-protocol parameters and parsing rules involves the MCU automatically loading a preset multi-protocol configuration file after the high-frequency head is powered on. For target compatible protocols such as FrSky and DJI, the MCU configures the frame structure parameters, exclusive parsing rules, and corresponding communication baud rates for each protocol one by one. This ensures that the subsequent reception and parsing of each protocol data has a clear execution basis, and at the same time completes the initial loading of the protocol library, laying the foundation for the parallel processing and compatibility adaptation of multi-protocol data.

[0020] The setting of safety instructions as the highest priority, ordinary control instructions as the second highest priority, and protocol identifiers as the lowest priority is specifically implemented as follows: A priority scheduling table is initialized, and safety instructions corresponding to each compatible protocol (such as FrSky and DJI) (including FrSky's "FAILSAFE" frame and DJI's "EMERGENCY STOP" instruction) are uniformly marked as the highest priority. Ordinary control parameters of each protocol (such as control instructions corresponding to joystick displacement and equipment operation status adjustment instructions) are marked as the second highest priority. The dedicated identifier field used to distinguish protocol types is marked as the lowest priority. Simultaneously, priority execution rules are clearly defined: the highest priority instruction has preemptive execution rights and can interrupt currently processed second-priority or lowest-priority data; second-priority instructions must be parsed only when there are no higher-priority instructions pending processing; and the lowest-priority instructions are only processed when there is no other higher-priority data. This ensures that the scheduling module can strictly respond to safety instructions according to hierarchical priority, guaranteeing timely triggering of protection functions in emergency situations.

[0021] The initialization of the sliding window initial size, data change rate threshold, and MCU computing power saturation threshold, in practice, involves initializing the core configuration parameters of the data smoothing algorithm. The initial sliding window size is set to 3 frames to balance data stability and control response speed in typical scenarios. The data change rate threshold is defined as 20%, meaning that when the ratio of the difference between the standardized data of two adjacent frames to the data of the previous frame exceeds this threshold, it is considered a high-dynamic-change scenario. The MCU computing power saturation threshold is set to 80%, using the real-time MCU computing power utilization rate as a benchmark. When the utilization rate reaches or exceeds this threshold, a dynamic computing power allocation mechanism is triggered. Simultaneously, the aforementioned threshold parameters and window size parameters are stored in the system configuration register, ensuring that they can be directly accessed in subsequent data processing and computing power scheduling stages, providing a clear basis for dynamic adjustment logic.

[0022] The multi-channel synchronous reception of data from various protocols involves frame header identification, CRC check to filter valid data, and storage of data in a buffer according to protocol classification with timestamps recorded. In practice, the LNB is equipped with an independent multi-channel parallel reception module, with each channel pre-bound to target compatible protocols such as FrSky and DJI to ensure synchronous reception of data from each protocol without interference, thus achieving parallel acquisition of multi-protocol data. After receiving data, frame header identification is performed based on the preset frame header feature codes (such as specific byte sequences) of each protocol. Data that does not match the corresponding frame header is directly determined to be invalid.

[0023] Then, the CRC check algorithm (such as CRC8 or CRC16) corresponding to each protocol is used to calculate the CRC value of the received data and compare it with the frame tail check field. Data that does not match the check is discarded. At the same time, the actual length of the received data is checked according to the frame length parameters configured for each protocol. Data that exceeds or falls short of the preset range is considered invalid data. For valid data that passes frame header identification, CRC check and length verification, the built-in protocol identifier field is extracted and matched with the system's preset protocol identifier library. The data is then classified and stored in the independent buffer of the corresponding protocol to avoid cross-interference between data from different protocols.

[0024] Meanwhile, based on the MCU's system clock, the time when each frame of valid data is received is recorded with timestamp accuracy down to the microsecond level, providing an accurate time reference for subsequent data change rate calculation, dynamic smoothing adjustment, and scheduling optimization.

[0025] The priority scanning security command, once detected, immediately suspends normal data processing, parses and outputs directly. In practice, the scheduling module scans the independent buffers of each protocol in real time according to a preset period, and accurately identifies the security command feature identifier marked with the highest priority (such as FrSky's "FAILSAFE" frame feature code and DJI's "EMERGENCYSTOP" command identifier) ​​based on the priority scheduling table configured in the initialization.

[0026] If a safety command is detected, a preemptive execution mechanism is immediately triggered, pausing the ongoing parsing and processing of secondary-priority ordinary control commands. Simultaneously, the system's pre-set dedicated safety command parsing module is invoked to complete data parsing based on the exclusive parsing rules of the protocol to which the safety command belongs. Core execution parameters are quickly extracted and standardized execution commands are generated. Without the need for subsequent data smoothing processing, the commands are directly sent to the LNB transmitter module and transmitted to the controlled device, ensuring an immediate response from the emergency protection function. At the same time, the complete processing time from detection to output of the safety command is recorded and stored in the status feedback log.

[0027] When no security instructions are available, ordinary instructions are read according to the principle of "master control protocol takes precedence over backup protocol". In practice, after the scheduling module scans and confirms that there are no highest priority security instructions in each protocol buffer, it strictly follows the system's preset protocol scheduling rules, prioritizes the independent buffer corresponding to the master control protocol, and reads the ordinary control instruction data of the master control protocol in the order of data reception timestamps (from early to late) to ensure the priority processing of master control instructions.

[0028] During the reading process, the validity and continuity of the main control protocol data are monitored synchronously. If the main control protocol data fails to verify for two consecutive frames, the data stream is interrupted, or the update is not updated after a timeout (the timeout threshold is preset to 50ms to match the control command processing delay requirements), the backup protocol switching logic is immediately triggered, and the system seamlessly switches to the backup protocol buffer. The system reads the ordinary control command data of the backup protocol in the same timestamp order to ensure that the control command output is not interrupted.

[0029] It also records information such as the current protocol type, data reading order, and whether a protocol switch has occurred, and links this information with subsequent computing power utilization data to provide a reference for the next round of priority scheduling and computing power allocation optimization.

[0030] The system monitors MCU computing power in real time, performing fully parallel parsing when it is not saturated. When it is saturated, it allocates fixed computing power to the main control protocol and backup protocols. Specifically, the MCU computing power monitoring module collects the MCU core computing load, the duration of each protocol parsing task, and the task queue backlog in real time based on the system clock cycle, accurately calculates the current computing power utilization rate, and synchronizes the calculation results to the scheduling module and configuration register in real time. If the computing power utilization rate is below 80% (not saturated), the system starts the fully parallel parsing mode, allocating independent parsing threads to each compatible protocol such as FrSky and DJI. Ordinary control command data of each protocol enters the parsing process synchronously, and completes the core parameter extraction and standardization conversion between protocols in parallel to ensure maximum parsing efficiency.

[0031] If the computing power utilization rate reaches or exceeds 80% (saturation), the dynamic computing power allocation mechanism is immediately triggered. According to the preset rules, 60% of the MCU computing power resources are allocated to the main control protocol to ensure the real-time parsing of its core control instructions. The remaining 40% of the computing power is allocated to the backup protocol. At the same time, the parsing frequency of the backup protocol is adjusted from real-time parsing to parsing once every 2 frames of data to reduce the computing power occupation of non-core tasks.

[0032] During the computing power allocation process, the progress of each protocol parsing and the changes in computing power usage are monitored in real time. When the computing power usage rate drops below 80% for three consecutive system cycles, the dynamic allocation mechanism is automatically terminated and the fully parallel parsing mode is restored. At the same time, the trigger time, duration, allocation ratio and parsing effect of each computing power saturation are recorded and incorporated into the status feedback data to provide a basis for the next round of computing power scheduling optimization.

[0033] The calculated data change rate is maintained for smooth processing of several frames when it is less than or equal to the first threshold; when it is greater than the first threshold, it is adjusted to be directly output in one frame window. When there are several consecutive frames of low dynamics, the initial window is restored. Specifically, in implementation, the dynamic change rate of the ordinary control command data of each protocol is calculated frame by frame according to the formula "change rate = |current frame normalized data - previous frame normalized data| / previous frame normalized data × 100%".

[0034] The first threshold corresponds to 20% of the initial system configuration. If the calculated data change rate is ≤20% (low dynamic scenario), the initial 3-frame sliding window size is maintained, and a moving average operation is performed on the standardized data of the current frame and the previous two frames to filter out data fluctuation interference and obtain smoothed stable decision data. If the data change rate is >20% (high dynamic scenario), the sliding window size is immediately adjusted to 1 frame, the smoothing operation is canceled, and the standardized data of the current frame is directly used as the decision data to ensure that the control response is synchronized with the dynamic changes in data.

[0035] Simultaneously, the number of consecutive low-dynamic frames is accumulated in real time. When the change rate of three consecutive frames is ≤20%, the sliding window size is automatically restored to the initial three frames, and the sliding average processing is restarted. Throughout the process, the change rate value of each frame, the window adjustment status, and the reason for the adjustment are recorded synchronously. This is linked with the status feedback data of the previous steps to provide a practical basis for subsequent optimization of smoothing algorithm parameters.

[0036] The process of converting and transmitting command formats, recording processing time and computing power utilization, and updating configuration parameters for the next round of optimization involves several steps. Specifically, the process begins by matching the output format requirements of the corresponding protocol based on the command type (security command execution command or ordinary decision data). A pre-defined format conversion module in the protocol library is then called to convert the standardized command data into the specific frame structure of target protocols such as FrSky and DJI. Frame headers, trailers, check fields, and protocol identification information are added to ensure that the converted command format fully complies with the communication specifications of each protocol (consistent with the frame structure parameters and communication baud rate configured in the previous steps). Subsequently, the converted command data is transmitted to the LNB transmitting module. The transmitting module initiates signal transmission according to the communication parameters of the corresponding protocol, accurately transmitting the command to the controlled device while ensuring signal stability and transmission timeliness during the transmission process.

[0037] Synchronously extract the received timestamp and the current command transmission completion time recorded in the previous steps, calculate the complete processing time of each frame of command (accurate to the microsecond level), and obtain the current real-time computing power utilization rate from the MCU computing power monitoring module. Based on the current processing protocol type, command type (security / normal), sliding window size, computing power allocation ratio, and whether a protocol switch has occurred, integrate these key information to form complete status feedback data, store it in the log buffer, and archive it in chronological order. Based on this status feedback data, dynamic optimization analysis is carried out: if the processing time of ordinary instructions for multiple consecutive frames exceeds the preset threshold, the parsing frequency of the backup protocol is finely adjusted according to the computing power occupancy (e.g., when computing power is continuously strained, the parsing frequency is adjusted from once every 2 frames to once every 3 frames, or real-time parsing is restored when computing power is sufficient); if window size switching is frequently triggered during dynamic smoothing, the 20% change rate threshold or the recovery condition of 3 consecutive frames of low dynamics can be optimized according to the statistical distribution of the data change rate; if the processing time of security instructions is too long, the scanning cycle of priority scheduling is optimized to improve the response speed of security instruction detection; the above optimized parameters (computing power allocation ratio, parsing frequency, smoothing threshold) are updated to the system configuration register, overwriting the original configuration parameters, providing a more realistic optimization basis for the initialization configuration, priority scheduling, parallel processing optimization, and dynamic smoothing adjustment of the next round of data processing, forming a continuously iterative closed-loop optimization mechanism.

[0038] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for ensuring compatibility of high-frequency heads in multi-protocol remote controls, characterized in that, Including the following steps: Load multi-protocol parameters and parsing rules, set security commands as the highest priority, ordinary control commands as the second highest priority, and protocol identifiers as the lowest priority, and initialize the initial size of the sliding window, the data change rate threshold, and the MCU computing power saturation threshold; The system receives data from various protocols synchronously through multiple channels. After frame header identification and CRC check to filter valid data, it is classified according to protocol, stored in the buffer, and timestamp is recorded. Prioritize scanning for security commands. Upon detection, immediately pause normal data processing, parse the data, and output it directly. If no security commands are found, read normal commands according to the principle of "master protocol takes precedence over backup protocol". Real-time monitoring of MCU computing power; full parallel analysis when not saturated; fixed computing power allocated to the main control protocol and backup protocol when saturated. Calculate the rate of change of data. If it is less than or equal to the first threshold, maintain a smooth processing window for several frames. If it is greater than the first threshold, adjust to output directly with a 1-frame window. When there are several consecutive frames of low dynamics, restore the initial window. Convert the instruction format and issue it, record the processing time and computing power utilization, and update the configuration parameters for the next round of optimization.

2. The multi-protocol remote control LNB compatibility method according to claim 1, characterized in that, The loading of multi-protocol parameters and parsing rules specifically refers to the MCU automatically loading a preset multi-protocol configuration file after the high-frequency head is powered on. The frame structure parameters, exclusive parsing rules, and communication baud rate are configured for the target compatible protocol to determine the execution basis for subsequent data reception and parsing.

3. The multi-protocol remote control LNB compatibility method according to claim 1, characterized in that, The setting of security instructions as the highest priority, ordinary control instructions as the second highest priority, and protocol identifiers as the lowest priority involves: initializing a priority scheduling table; marking security instructions of each compatible protocol as the highest priority, ordinary control instructions as the second highest priority, and protocol identifiers as the lowest priority; determining that the highest priority instruction has preemptive execution permission and can interrupt the processing of lower priority data; parsing of the second highest priority instructions when there is no highest priority instruction; and processing of the lowest priority instructions only when there is no higher priority data.

4. The multi-protocol remote control high-frequency head compatibility method according to claim 1, characterized in that, The initialization of the sliding window initial size, data change rate threshold, and MCU computing power saturation threshold specifically involves initializing the core configuration parameters of the data smoothing algorithm, including the initial sliding window size, data change rate threshold, and MCU computing power saturation threshold, determining the scenario judgment criteria corresponding to each threshold, and storing these parameters in the system configuration register for direct use in subsequent data processing and computing power scheduling.

5. The multi-protocol remote control high-frequency head compatibility method according to claim 1, characterized in that, The multi-channel synchronous reception of data from various protocols involves identifying frame headers, filtering valid data through CRC checks, classifying the data by protocol, storing it in a buffer, and recording timestamps. Specifically, the high-frequency head receives multi-protocol data in parallel through independent multi-channels. After reception, valid data is filtered through frame header identification, CRC checks, and length verification, invalid data is removed, and the protocol identifier field in the valid data is extracted. The data is then classified and stored in the independent buffer of the corresponding protocol to avoid interference. At the same time, the time when the reception of each frame of valid data is completed is recorded based on the MCU system clock.

6. The multi-protocol remote control LNB compatibility method according to claim 1, characterized in that, The priority scanning security command, once detected, immediately suspends ordinary data processing, parses it, and outputs it directly. Specifically, the scheduling module scans the independent buffers of each protocol according to a preset period, identifies the highest priority security command feature based on the priority scheduling table, and triggers a preemptive execution mechanism upon detection. It suspends the processing of the current second-lowest priority ordinary control command, calls a dedicated parsing module to parse it according to the corresponding protocol rules, extracts the core parameters to generate a standardized execution command, and sends it directly to the transmission module without subsequent data smoothing processing. At the same time, the complete processing time of the security command is recorded and stored in the status feedback log.

7. The multi-protocol remote control high-frequency head compatibility method according to claim 1, characterized in that, When no security instructions are available, ordinary instructions are read according to the principle of "primary control protocol takes precedence over backup protocol". Specifically, when no security instructions are available, the scheduling module reads the ordinary control instructions of the primary control protocol first according to preset rules, processes them in the order of data reception timestamps, and monitors the validity and continuity of the primary control protocol data. If the primary control protocol data is abnormal, it seamlessly switches to the backup protocol to read the data, ensuring that the output of control instructions is not interrupted, and records relevant protocol processing information.

8. The multi-protocol remote control high-frequency head compatibility method according to claim 1, characterized in that, The real-time monitoring of MCU computing power involves fully parallel parsing when not saturated, and allocating fixed computing power to the main control protocol and backup protocol when saturated. Specifically, the MCU computing power monitoring module collects core computing load, parsing task duration, and queue backlog in real time, calculates computing power utilization, and synchronizes it to the scheduling module and configuration register. When not saturated, the fully parallel parsing mode is activated, allocating independent threads to each protocol to synchronously parse ordinary control instructions. When saturated, computing power is allocated to the main control protocol and backup protocol according to preset rules, the parsing frequency of the backup protocol is adjusted, and changes in computing power are monitored in real time. Once the computing power drops below the threshold, the fully parallel mode is restored, and relevant data is recorded and included in the status feedback.

9. The multi-protocol remote control LNB compatibility method according to claim 1, characterized in that, The calculated data change rate is maintained for smoothing through several frames when it is less than or equal to a first threshold; when it is greater than the first threshold, it is adjusted to output directly through a 1-frame window. The initial window is restored when there are several consecutive low dynamic frames. Specifically, the data change rate is calculated based on standardized data and the received timestamp. The sliding window size is adjusted according to the scenario in which the change rate is located. In low dynamic scenarios, the initial window is maintained for smoothing. In high dynamic scenarios, the data is adjusted to output directly through a 1-frame window. The initial window is restored when there are consecutive low dynamic scenarios. During the process, the change rate, window adjustment status and triggering reason are recorded and linked with the status feedback data.

10. The multi-protocol remote control high-frequency head compatibility method according to claim 1, characterized in that, The process of converting and transmitting instruction formats, recording processing time and computing power utilization, and updating configuration parameters for the next round of optimization involves matching the corresponding protocol output format according to the instruction type, converting standardized data into the target protocol frame structure, and then sending it to the controlled device through the transmission module; synchronously collecting instruction processing time and computing power utilization, integrating them to form status feedback data, and archiving it. Based on the feedback data, the relevant parameters are optimized and updated to the system configuration register.

Images