Cross-platform development board communication fault feedback method and device and storage medium

Abstract

The invention discloses a cross-platform development board communication fault feedback method and device and a storage medium, and relates to the technical field of communication, after main and sub development boards are initialized, a communication state machine is established, a heartbeat timer is started, heartbeat packets are periodically received and sent, an overtime threshold value is dynamically set in an idle state, and error feedback is triggered if no heartbeat packet is received in an overtime state. The connection state periodically detects communication quality, a reconnection mechanism is triggered if continuous packet loss exceeds a threshold value, an error report is generated and reported when reconnection failure reaches an upper limit, error feedback comprises data packet sending, log recording, alarm triggering and the like, and a reconnection request comprises an identifier, a timestamp and a historical communication index; according to the method, communication interruption caused by misjudgment is reduced, and the communication stability and reliability are improved.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and more specifically, to a method, device, and storage medium for cross-platform development board communication fault feedback. Background Art

[0002] In the field of modern cross-platform development board communication, optical fiber links are widely used as high-speed and stable data transmission media. However, in the existing technologies for handling communication faults between development boards, most adopt a timeout reconnection mechanism, which has obvious limitations and defects and is difficult to meet the communication stability requirements under complex working conditions.

[0003] The working principle of the existing timeout reconnection mechanism is as follows: After the development boards complete system initialization, they send heartbeat packets to each other through the optical fiber link. If a heartbeat packet from the other party is not received within a set fixed time duration, the timeout mechanism is triggered, determining that the other development board has disconnected, and then the optical fiber communication is disconnected. This mechanism can theoretically respond quickly to communication anomalies, but in actual applications, it frequently leads to misjudgments and unnecessary communication interruptions.

[0004] There are significant differences in the time taken for different development boards to complete system initialization from power-on. For example, the main development board may quickly complete initialization in a short time, while the sub-development board may take longer due to hardware configuration, software complexity, or external environmental factors. In this case, the main development board has entered the waiting communication state, while the sub-development board is still in the initialization process. Since the timeout reconnection mechanism uses a fixed timeout threshold and cannot dynamically adapt to this initialization time difference, the main development board will misjudge that the optical fiber connection has failed after the timeout and then disconnect the communication link. This misjudgment not only causes communication interruptions but may also trigger a system-level chain reaction, affecting the stability and reliability of the entire system. In addition, the existing mechanism also has deficiencies in communication recovery ability. Once the communication link is disconnected due to misjudgment or real faults, the reconnection mechanism often lacks effective state management and fault diagnosis capabilities and cannot distinguish between temporary communication anomalies and permanent faults. This causes the system to make reconnection attempts too frequently in the face of short communication fluctuations, wasting system resources; while in the face of real faults, it may also lack effective fault location and reporting mechanisms, making it difficult for maintenance personnel to quickly troubleshoot problems and prolonging the system recovery time. Summary of the Invention

[0005] In order to overcome the problems of high misjudgment rate, frequent communication interruptions, and insufficient recovery ability of the existing timeout reconnection mechanism, the present invention discloses a method, device, and storage medium for cross-platform development board communication fault feedback, which can effectively solve the above technical problems.

[0006] To solve the above technical problems, the technical solution of the present invention is as follows:

[0007] A cross-platform development board communication fault feedback method, comprising the following steps:

[0008] After the main development board and the sub-development board initialize the hardware and communication modules respectively, a communication state machine is established, and the communication state machine includes an initialization state, an idle state, a connection state, and an error state;

[0009] After the initialization is completed, the main development board and the sub-development board start heartbeat timers respectively, periodically send heartbeat packets and receive the heartbeat packets of the other party;

[0010] When the communication state machine enters the idle state, start an overtime timer and set an overtime threshold; if the heartbeat packet of the other party is received within the overtime threshold, switch to the connection state and close the overtime timer; if the heartbeat packet is not received within the overtime threshold, switch to the error state and trigger an error feedback;

[0011] Start a connection timer in the connection state, and periodically detect the communication quality; if the number of consecutive lost heartbeat packets exceeds a preset threshold, trigger a reconnection mechanism;

[0012] When the number of reconnection attempts reaches the preset upper limit and the communication still cannot be restored, switch to the fault disconnection state, generate an error report containing communication parameters and report it to the system management layer.

[0013] Preferably, the setting method of the overtime threshold is as follows:

[0014] Based on the maximum system initialization delay of the main development board and the sub-development board, the optical fiber link transmission delay, and a preset redundancy coefficient, dynamically adjust the overtime threshold through formula calculation:

[0015] T timeout =(T init_max +T link )×k

[0016] wherein, T init_max is the maximum initialization time of the development board, T link is the one-way transmission delay of the optical fiber link, and k is the redundancy coefficient.

[0017] Preferably, the triggering mechanism of the heartbeat timer is as follows:

[0018] After the initialization is completed, the main development board and the sub-development board send heartbeat packets at a fixed period T heartbeat respectively, and reset the local counter when receiving the heartbeat packet of the other party; if the number of consecutive non-reception times exceeds N times, it is determined that the communication is abnormal.

[0019] Preferably, the error feedback includes at least one of the following operations:

[0020] Send a data packet containing an error code, the timestamp of the last heartbeat, and the link status to the host computer;

[0021] Record the error log and store it in the non-volatile memory;

[0022] Trigger a hardware alarm through the LED indicator or buzzer.

[0023] Preferably, the execution process of the reconnection mechanism includes:

[0024] Suspend the current communication link, reset the heartbeat timer and connection timer;

[0025] Send a reconnection request to the other development board and wait for the response timeout time T reconnect ;

[0026] If a response is received within T reconnect , resume the communication link and reset the state machine to the connected state; otherwise, accumulate the reconnection times and repeat the above steps.

[0027] Preferably, the reconnection request contains the following information:

[0028] The unique identifier of the current development board;

[0029] The timestamp of the last valid communication;

[0030] The historical communication quality index.

[0031] Preferably, when the error report is generated, the following data correlation analysis is performed:

[0032] Perform time series matching between the communication anomaly time and the power fluctuation and temperature change events in the system log;

[0033] Infer the cause of the fault based on the preset rule base.

[0034] An electronic device, comprising:

[0035] An optical fiber interface module for establishing a physical link with the other development board;

[0036] A state machine management unit configured to execute the logic control of the above-mentioned feedback method;

[0037] A timer module for managing the start and stop of the heartbeat timer, timeout timer and connection timer;

[0038] An error processing unit for generating an error report and triggering an alarm action.

[0039] Preferably, it further includes:

[0040] An adaptive learning module for dynamically optimizing the following parameters according to the historical communication data:

[0041] The heartbeat packet sending period Theartbeat ;

[0042] Upper limit of reconnection times

[0043] Timeout threshold T timeout Redundancy coefficient k of

[0044] A computer-readable storage medium stores a computer program which, when executed by a processor, implements the steps of the above-mentioned feedback method.

[0045] Compared with the prior art, the beneficial effects of the present invention are as follows: in the prior art, the timeout threshold is a fixed value and cannot adapt to the dynamic changes of the development board initialization time difference and the link transmission delay, and it is easy to misjudge normal communication as a fault. The present invention dynamically calculates the timeout threshold based on the maximum delay of the development board initialization, the optical fiber link transmission delay and the redundancy coefficient, ensuring that communication faults will not be misjudged before the development board initialization is completed, thus avoiding unnecessary communication interruptions and improving the stability and reliability of the system; by introducing a communication state machine of initialization state, idle state, connection state and error state, the present invention can dynamically manage the communication process of the development board, start a timeout timer in the idle state and dynamically set the threshold to avoid misjudgment caused by the initialization time difference; in the connection state, the communication quality is periodically detected to timely discover link anomalies and trigger a reconnection mechanism to ensure the continuity of communication; in the prior art, the sending period of the heartbeat packet is fixed and cannot flexibly respond to link state changes. The present invention dynamically monitors the link state by periodically sending heartbeat packets and resetting the counter when receiving the heartbeat packet from the other party. If the number of consecutive times of not receiving the heartbeat packet exceeds the preset threshold, it is determined that the communication is abnormal, avoiding misjudgment caused by accidental packet loss and improving the detection accuracy of the communication quality at the same time; in the prior art, the reconnection mechanism lacks flexibility and cannot effectively restore the link. The present invention pauses the current communication link during the reconnection process, resets the timer and sends a reconnection request including the development board identifier, timestamp and historical communication quality indicators to ensure the accuracy and efficiency of the reconnection request. If the number of reconnection failures reaches the upper limit, an error report is generated and reported to avoid the system being in an unstable state for a long time; in the prior art, the error feedback mechanism is single and cannot effectively locate the cause of the fault. The present invention sends a data packet including an error code, the timestamp of the last heartbeat and the link state to the host computer, records the error log and stores it in the non-volatile memory, and at the same time prompts the fault through hardware alarm, enhancing the comprehensiveness of the error feedback. In addition, when the error report is generated, the cause of the fault is inferred through data correlation analysis, such as optical fiber breakage, interface looseness or software deadlock, providing an accurate fault diagnosis basis for system maintenance; the present invention further improves the adaptive ability of the communication system and reduces misjudgment and communication interruption caused by fixed parameters through an adaptive learning module that dynamically optimizes the heartbeat packet sending period, the upper limit of reconnection times and the redundancy coefficient of the timeout threshold according to historical communication data. Description of the Drawings

[0046] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only exemplary. For those of ordinary skill in the art, without creative efforts, other implementation drawings can be obtained based on the provided drawings.

[0047] Figure 1 It is a flowchart of a cross-platform development board communication failure feedback method;

[0048] Figure 2 It is a step diagram of the method of the present invention. Specific embodiments

[0049] The drawings are only for exemplary illustration and cannot be construed as a limitation of this patent;

[0050] To better illustrate this embodiment, some components in the drawings will be omitted, enlarged or reduced, which does not represent the size of the actual product;

[0051] For those skilled in the art, it is understandable that some well-known structures and their descriptions in the drawings may be omitted.

[0052] The following will further illustrate the technical solutions of the present invention in conjunction with the drawings and embodiments.

[0053] Embodiment

[0054] A cross-platform development board communication failure feedback method includes the following steps:

[0055] After the main development board and the sub-development board respectively initialize the hardware and communication modules, a communication state machine is established, and the communication state machine includes an initialization state, an idle state, a connection state, and an error state;

[0056] After the initialization is completed, the main development board and the sub-development board respectively start a heartbeat timer, periodically send heartbeat packets and receive the heartbeat packets of the other party;

[0057] When the communication state machine enters the idle state, start an overtime timer and set an overtime threshold; if the heartbeat packet of the other party is received within the overtime threshold, switch to the connection state and close the overtime timer; if the heartbeat packet is not received within the overtime threshold, switch to the error state and trigger an error feedback;

[0058] Start a connection timer in the connection state, periodically detect the communication quality; if the number of consecutive lost heartbeat packets exceeds a preset threshold, trigger a reconnection mechanism;

[0059] When the number of reconnection attempts reaches the preset upper limit and communication still cannot be restored, switch to the fault-disconnected state, generate an error report containing communication parameters, and report it to the system management layer.

[0060] The method for setting the timeout threshold is as follows:

[0061] Based on the maximum system initialization delay between the main development board and the sub-development board, the optical fiber link transmission delay, and the preset redundancy factor, dynamically adjust the timeout threshold through formula calculation:

[0062] T timeout =(T init_max +T link )×k

[0063] Where, T init_max is the maximum initialization time of the development board, T link is the one-way transmission delay of the optical fiber link, and k is the redundancy factor.

[0064] The triggering mechanism of the heartbeat timer is as follows:

[0065] After initialization is completed, the main development board and the sub-development board send heartbeat packets at a fixed period T heartbeat respectively, and reset the local counter when receiving the heartbeat packet of the other party; if the number of consecutive non-received times exceeds N times, it is determined that the communication is abnormal.

[0066] The error feedback includes at least one of the following operations:

[0067] Send a data packet containing the error code, the timestamp of the last heartbeat, and the link status to the host computer;

[0068] Record the error log and store it in the non-volatile memory;

[0069] Trigger a hardware alarm through the LED indicator or buzzer.

[0070] The execution process of the reconnection mechanism includes:

[0071] Suspend the current communication link, reset the heartbeat timer and the connection timer;

[0072] Send a reconnection request to the other development board and wait for the response timeout period T reconnect ;

[0073] If a response is received within T reconnect , restore the communication link and reset the state machine to the connected state; otherwise, accumulate the number of reconnection attempts and repeat the above steps.

[0074] The reconnection request contains the following information:

[0075] The unique identifier of the current development board;

[0076] Timestamp of the last valid communication;

[0077] Historical communication quality metrics.

[0078] Preferably, when generating the error report, perform the following data correlation analysis:

[0079] Match the communication anomaly time with power fluctuations and temperature change events in the system log in a time series;

[0080] Infer the cause of the fault based on a preset rule library.

[0081] An electronic device, comprising:

[0082] An optical fiber interface module for establishing a physical link with the other development board;

[0083] A state machine management unit configured to perform the logical control of the above-mentioned feedback method;

[0084] A timer module for managing the start and stop of heartbeat timers, timeout timers, and connection timers;

[0085] An error handling unit for generating error reports and triggering alarm actions.

[0086] Further comprising:

[0087] An adaptive learning module for dynamically optimizing the following parameters according to historical communication data:

[0088] Heartbeat packet sending period T heartbeat ;

[0089] Upper limit of the number of reconnection attempts;

[0090] Timeout threshold T timeout Redundancy factor k.

[0091] A computer-readable storage medium storing a computer program, which when executed by a processor, implements the steps of the above-mentioned feedback method.

[0092] In a specific implementation, please refer to Figure 1-2 , in this embodiment, taking the scenario where a type-A main development board for controlling the production process and multiple type-B sub-development boards responsible for data acquisition communicate through an optical fiber link in the industrial automation field as an example, the above cross-platform development board communication fault feedback method is elaborated in detail.

[0093] A type A main development board with high-performance processing capabilities and communication interfaces is selected, such as a development board based on the ARM Cortex-A9 architecture, equipped with a Linux operating system and a dedicated fiber-optic communication module. The type B sub-development board uses a low-power, high-reliability STM32 series microcontroller development board, which also integrates a fiber-optic communication interface to collect data from various sensors on the production line and upload it to the main development board.

[0094] Use single-mode optical fiber to connect the optical interface modules of the Type A main development board and the Type B sub-development board to ensure the stability and low loss of the optical fiber link. To prevent signal interference, the optical fiber link adopts shielding measures and installs optical transceivers at both ends to realize the conversion between electrical signals and optical signals.

[0095] The development board integrates LED indicators and buzzers for hardware alarm prompts, and is equipped with non-volatile memory, such as SPI Flash, for storing error logs and key communication parameters.

[0096] Software system implementation: When the A-type main development board and the B-type sub-development board are powered on respectively, they start the hardware self-test program to check whether the onboard chips, communication interfaces, sensors and other hardware devices are working properly. After the self-test is completed, the communication state machine module is loaded, the heartbeat timer, timeout timer and connection timer are initialized, and the initial parameters are set.

[0097] During the hardware self-test and communication module initialization process, the communication state machines of the main development board and the sub-development board both enter the "waiting for initialization completion" state. At this time, the timeout detection is not started to avoid misjudgment due to initialization time differences.

[0098] After completing system initialization, the main development board and the sub-development board start the heartbeat timer respectively. Assume that the heartbeat packet sending period is set to 500ms, that is, every 500ms, the development board sends a heartbeat packet to the other party and starts the local counter at the same time.

[0099] After the development board sends the heartbeat packet, the communication state machine switches from the "waiting for initialization to complete" state to the "idle" state, and starts the timeout timer. According to the maximum system initialization delay of the main development board and the sub-development board (determined to be 8 seconds after testing), the one-way transmission delay of the optical fiber link (0.5ms) and the preset redundancy coefficient (k=1.5), the formula T timeout =(T init_max +T link )×k, the timeout threshold is calculated to be 12 seconds.

[0100] The communication state machine runs a timeout timer in the "idle" state. When the main development board of type A receives a heartbeat packet from the sub-development board of type B, it confirms that the other party has completed initialization. The main development board resets the local counter, switches the communication state machine to the "connected state", and closes the timeout timer simultaneously. If it does not receive a heartbeat packet from the sub-development board of type B within the 12-second timeout threshold, the communication state machine of the main development board of type A will switch to the "error state".

[0101] When the communication state machine of the main development board of type A enters the "error state", it immediately triggers an error feedback mechanism, sending a data packet containing an error code (e.g., 0x01 indicates timeout for not receiving a heartbeat packet), the timestamp of the last heartbeat, and the link status (disconnected) to the host computer; recording error logs in non-volatile memory, including information such as the error occurrence time and error type; at the same time, lighting up the LED indicator and driving the buzzer to emit an alarm sound.

[0102] In the "connected state", the system starts a connection timer. Assuming the detection period of the connection timer is 1 second, when the connection timer detects that the number of consecutive missed heartbeat packets exceeds a preset threshold (e.g., N = 5 times), it is determined that the communication is abnormal, and the reconnection mechanism is immediately triggered.

[0103] When the communication abnormality triggers the reconnection mechanism, the main development board of type A pauses the current communication link, resets the heartbeat timer and the connection timer, and sends a reconnection request to the sub-development board of type B. The reconnection request contains the unique identifier of the current development board (e.g., 0xABCDEF), the timestamp of the last valid communication, and historical communication quality metrics (e.g., packet loss rate is 2% and average delay is 1ms).

[0104] After sending the reconnection request, the main development board of type A waits for the response timeout period, which is assumed to be 3 seconds. If it receives a response from the sub-development board of type B within 3 seconds, it resumes the communication link and resets the state machine to the connected state; otherwise, it accumulates the number of reconnection attempts. If the number of reconnection attempts reaches the preset upper limit (e.g., 3 times) and the communication still cannot be restored, the communication state machine of the main development board of type A switches to the "faulty disconnection" state.

[0105] When the communication state machine enters the "faulty disconnection" state, a detailed error report is generated, which contains information such as the communication abnormality time, the number of timeouts, the send / receive time of the last heartbeat packet, and historical communication quality metrics.

[0106] Match the communication abnormality time with power fluctuation and temperature change events in the system log in a time series. If the system log recorded an event of an instantaneous drop in power voltage 1 minute before the communication abnormality, combined with the preset rule library, it is inferred that the possible cause of the fault is a power fluctuation resulting in a temporary failure of the communication module.

[0107] The system records the entire operation process of the state machine, including information such as state transition time, heartbeat packet sending / receiving status, etc., and displays the current communication status in real time through the host computer software or monitoring platform, facilitating the operation and maintenance personnel to understand the communication situation between the development boards at any time; when the state machine enters the "error state" or "fault disconnection" state, in addition to triggering local hardware alarms, the system will also send text messages or email notifications to relevant maintenance personnel through the network to inform the communication fault information for timely on-site detection and repair.

[0108] The adaptive learning module dynamically optimizes the heartbeat packet sending period, the upper limit of the reconnection times, and the redundancy coefficient k of the timeout threshold according to historical communication data. For example, if the communication link is stable and the packet loss rate is low within a certain period, the heartbeat packet sending period can be appropriately extended to reduce system overhead; if communication failures occur frequently and the number of reconnections is large, the upper limit of the reconnection times can be increased to improve the system's fault tolerance; the adaptive learning module regularly analyzes historical communication data, updates relevant parameters according to the optimization strategy, stores the updated parameters in the non-volatile memory, and takes effect when the system is restarted next time. Through the cooperation of the above hardware devices and software systems, in the industrial automation production scenario, the type A main development board and the type B sub-development board can communicate efficiently and stably, and can feedback and handle communication failures in a timely manner, effectively ensuring the normal operation of the production process.

[0109] The same or similar reference numerals correspond to the same or similar components;

[0110] The terms describing the positional relationship in the drawings are only for illustrative purposes and should not be construed as a limitation of this patent;

[0111] Obviously, the above embodiments of the present invention are merely examples for clearly explaining the present invention, rather than limitations on the implementation manners of the present invention. For those of ordinary skill in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to enumerate all the implementation manners here. Any modifications, equivalent replacements, and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the claims of the present invention.

Claims

1. A cross-platform development board communication fault feedback method, characterized in that: The following steps are involved: After the main development board and the sub-development board initialize the hardware and the communication module respectively, a communication state machine is established, wherein the communication state machine includes an initialization state, an idle state, a connection state and an error state; After initialization is completed, the main development board and the sub-development board start the heartbeat timer respectively, periodically send heartbeat packets and receive each other's heartbeat packets; When the communication state machine enters the idle state, the timeout timer is started and the timeout threshold is set; if the heartbeat packet of the other party is received within the timeout threshold, it switches to the connection state and turns off the timeout timer; if the heartbeat packet is not received within the timeout threshold, it switches to the error state and triggers error feedback; Start the connection timer in the connected state and periodically check the communication quality; If the number of consecutive heartbeat packet losses exceeds the preset threshold, the reconnection mechanism is triggered; When the number of reconnection times reaches the preset upper limit and communication cannot be restored, it switches to the fault disconnection state, generates an error report containing communication parameters and reports it to the system management layer.

2. The feedback method according to claim 1, characterized in that: The method for setting the timeout threshold is: Based on the maximum system initialization delay of the main development board and the sub-development board, the fiber link transmission delay and the preset redundancy coefficient, the timeout threshold is dynamically adjusted through the formula calculation: T timeout =(T init_max +T link )×k Among them, T init_max The maximum time consumed for initializing the development board, T link is the one-way transmission delay of the optical fiber link, and k is the redundancy coefficient.

3. The feedback method according to claim 1, characterized in that: The triggering mechanism of the heartbeat timer is: After initialization is completed, the main development board and the sub-development board are respectively heartbeat Send a heartbeat packet and reset the local counter when receiving the other party's heartbeat packet; If the number of consecutive non-receptions exceeds N times, it is determined to be a communication abnormality.

4. The feedback method according to claim 1, characterized in that: The error feedback includes at least one operation: Send a data packet containing an error code, the timestamp of the last heartbeat, and the link status to the host computer; Record error logs and store them in non-volatile memory; Trigger hardware alarms via LED indicators or buzzers.

5. The feedback method according to claim 1, characterized in that: The execution process of the reconnection mechanism includes: Pause the current communication link, reset the heartbeat timer and connection timer; Send a reconnection request to the other development board and wait for the response timeout T reconnect ; If in T reconnect If a response is received within 10 seconds, the communication link is restored and the state machine is reset to the connected state; otherwise, the number of reconnections is accumulated and the above steps are repeated.

6. The feedback method according to claim 5, characterized in that: The reconnection request contains the following information: Unique identifier of the current development board; The timestamp of the last valid communication; Historical communication quality indicators.

7. The feedback method according to claim 1, characterized in that: When the error report is generated, the following data association analysis is performed: Match the communication anomaly time with the power fluctuation and temperature change events in the system log in time series; Infer the cause of the failure based on the preset rule base.

8. An electronic device, characterized in that: include: Optical fiber interface module, used to establish a physical link with the other party's development board; A state machine management unit configured to execute the logic control of the feedback method according to any one of claims 1 to 7; The timer module is used to manage the start and stop of the heartbeat timer, timeout timer and connection timer; The error handling unit is used to generate error reports and trigger alarm actions.

9. The device according to claim 8, characterized in that Also includes: Adaptive learning module for dynamically optimizing the following parameters based on historical communication data: Heartbeat packet sending cycle T heartbeat ; Maximum number of reconnections; Timeout threshold T timeout The redundancy coefficient k.

10. A computer-readable storage medium, characterized in that: A computer program is stored, and when the program is executed by a processor, the steps of the feedback method according to any one of claims 1 to 7 are implemented.

Images