MCU software remote burning system supporting state display in railway system

By designing a remote burning system for MCU software that supports status display, the problem of low upgrade efficiency of railway monitoring equipment software and inability to display the burning status in real time is solved, and efficient and reliable remote upgrades and real-time status display are achieved.

CN119938091APending Publication Date: 2025-05-06XIAN RAILWAY SIGNAL
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411855520.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-12-17
Publication Date
2025-05-06

AI Technical Summary

Technical Problem

The existing railway monitoring equipment software upgrade method is inefficient, time and manpower are consumed, and it is impossible to display the burned state in real time, and it is impossible to obtain update node information.

Method used

Design a remote recording system for MCU software that supports status display, realize remote software upgrade through monitoring information sources, monitoring servers and monitoring terminals, and display the upgrade status in real time through monitoring terminals.

Benefits of technology

It solves the problems of low efficiency and time-consuming remote upgrades, realizes simultaneous upgrade of multiple devices and real-time status display, and improves the reliability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119938091A_ABST
    Figure CN119938091A_ABST
Patent Text Reader

Abstract

The invention relates to an MCU software remote burning system supporting state display in a railway system. The MCU software remote burning system comprises one or more monitoring information sources. A monitoring server; one or more monitoring terminals; the monitoring information source has two working modes, namely a normal mode and an upgrading mode, in the normal mode, monitoring information is generated or output; in the upgrading mode, software upgrading is carried out; the monitoring server is used for collecting monitoring information of the monitoring information source; and sending data to the monitoring information source. Receiving data of the monitoring terminal, and issuing the data to the monitoring terminal; and the monitoring terminal provides a user use interface. And sending data to the monitoring server, and receiving the data of the monitoring server. The system solves the problems that an existing burning mode is low in efficiency and consumes time and manpower; meanwhile, the burning state can be displayed, and the problem that the updating node information cannot be obtained in an existing burning mode is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to the maintenance and upgrading of monitoring equipment, and in particular to a system for remote burning of MCU software supporting status display in a railway system. Background Art

[0002] Monitoring systems are widely used in my country's existing railway systems. However, due to the special environment of the railway system, monitoring equipment is often large in number and widely distributed. During the use of the system, these devices need to be continuously upgraded according to user needs. How to upgrade the software of these devices is a difficult problem.

[0003] The upgrade method of the railway monitoring equipment software system is also gradually evolving. From the initial time-consuming and manpower-consuming upgrade by dedicated personnel to the equipment, to the basic stateless display remote upgrade, there are still problems such as inconvenience and non-intuitiveness in use. Summary of the invention

[0004] The purpose of the present invention is to provide a system for remote burning of MCU software supporting status display in a railway system, and propose an improved remote upgrade solution, which solves the problems of low efficiency, time and manpower consumption of a basic burning method, and can display the burning status, solving the problem that the existing burning method cannot obtain updated node information.

[0005] The object of the present invention is achieved in this way, and relates to a system for remote burning of MCU software supporting status display in a railway system: It includes one or more monitoring information sources (including MCU), a monitoring server, and one or more monitoring terminals.

[0006] The monitoring information source and the monitoring server transmit information in both directions, and the monitoring server and the monitoring terminal transmit information in both directions.

[0007] The monitoring information source has two working modes, normal mode and upgrade mode. In normal mode: monitoring information is generated or output; in upgrade mode, software upgrade is performed; The monitoring server is used to collect monitoring information from monitoring information sources; send data to monitoring information sources, receive monitoring terminal data, and publish data to monitoring terminals; The monitoring terminal provides a user interface, sends data to the monitoring server, and receives data from the monitoring server.

[0008] When the software is burned to the MCU remotely, the monitoring server sends the upgraded software to the monitoring information source, the monitoring terminal subscribes to the software upgrade status message from the monitoring server, displays the upgrade status according to the upgrade status message, and the monitoring information source sends the software upgrade status message to the monitoring server. The specific workflow is as follows: Monitoring terminal: 1) Open the monitoring terminal; 2) Monitor the "Software Upgrade Status Event" topic and notify the monitoring server; 3) The operator selects the device to be upgraded and the upgrade version, and submits the upgrade task; 4) Wait to receive the monitoring server's upgrade status information for the monitoring information source, and change the status on the interface after receiving it.

[0009] Monitoring Server: 1) Confirm the monitoring terminal's notification of starting monitoring; 2) After receiving the upgrade task from the monitoring terminal, send a "start upgrade command" to the corresponding monitoring information source; 3) After receiving the "Start Upgrade Command Confirmation" from the monitoring information source, send the upgrade status information to the "Software Upgrade Status Event" topic, and start sending the upgrade file and file verification code to the monitoring information source; Cut the upgrade file into file slices according to a fixed size, number them in order from small to large, and send them to the monitoring information source in the format of "upgrade file slice content" frame one by one; The "Upgrade File Slice Content" frame includes: 1. Total number of file slices; 2. Current file number; 3. File slice content; 4. File slice content verification code; 4) After receiving the "Confirmation of File Batch Receiving" from the monitoring information source, send the upgrade status information to the "Software Upgrade Status Event" topic according to the file sending progress; 5) After receiving the "file verification passed message" from the monitoring information source, send the upgrade status information to the "software upgrade status event" topic; 6) After receiving the "software upgrade completion message" from the monitoring information source, send the upgrade status information to the "software upgrade status event.

[0010] Monitoring information sources: 1) After receiving the "start upgrade command" from the monitoring server, enter the upgrade mode; 2) After receiving the "upgrade file slice content" from the monitoring server, save the file slice content and return the "file batch reception confirmation" signaling, where the number is the current file number in the received signaling; 3) After receiving all the upgrade file slices, assemble all the received file slices into one file in the order of numbering, and compare and verify with the overall file verification code. If it passes, a "file verification passed message" will be sent and the file will be burned 4) After burning is completed, enter the normal mode; likeFigure 3 As shown in the figure, the software upgrade status is divided into the following categories: 1) In preparation: preparing for upgrade; 2) Downloading: When downloading the burning file, the download progress is displayed in percentage; Whether all file slices are downloaded successfully, if successful, proceed to the next step, otherwise return to step 6); 3) Download successfully, burn the file; 4) Upgrade completed: Upgrade completed; 5) Upgrade failed: Upgrade failed.

[0011] The advantages of the present invention are: solving the problems of low efficiency, time-consuming and labor-intensive burning methods. The program can be upgraded remotely without going to the device location for upgrading; Multiple devices can be upgraded at the same time; You can check the upgrade status in real time; Good reliability.

[0012] The present invention will be further described below in conjunction with the accompanying drawings of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a schematic diagram of the system structure of an embodiment of the present invention; Figure 2 It is a schematic diagram of the system software upgrade process of an embodiment of the present invention; Figure 3 It is an upgrade flow chart. DETAILED DESCRIPTION

[0014] In order to further explain the technical means and effects adopted by the present invention to achieve the predetermined purpose, the specific implementation methods, structural features and effects of the present invention are described in detail below in conjunction with the accompanying drawings and embodiments.

[0015] like Figure 1 As shown, the present invention relates to a system for remote burning of MCU software supporting status display in a railway system, comprising one or more monitoring information sources (including MCU), a monitoring server, and one or more monitoring terminals.

[0016] The monitoring information source and the monitoring server transmit information in both directions, and the monitoring server and the monitoring terminal transmit information in both directions.

[0017] The monitoring information source has two working modes, normal mode and upgrade mode. In normal mode: monitoring information is generated or output; in upgrade mode, software upgrade is performed; The monitoring server is used to collect monitoring information from monitoring information sources; send data to monitoring information sources, receive monitoring terminal data, and publish data to monitoring terminals; The monitoring terminal provides a user interface, sends data to the monitoring server, and receives data from the monitoring server.

[0018] like Figure 2 As shown, the monitoring server sends the upgrade software to the monitoring information source, the monitoring terminal subscribes to the software upgrade status message from the monitoring server, displays the upgrade status according to the upgrade status message, and the monitoring information source sends the software upgrade status message to the monitoring server. The specific workflow is as follows: Monitoring terminal: 1) Open the monitoring terminal; 2) Monitor the "Software Upgrade Status Event" topic and notify the monitoring server; 3) The operator selects the device to be upgraded and the upgrade version, and submits the upgrade task; 4) Wait to receive the monitoring server's upgrade status information for the monitoring information source, and change the status on the interface after receiving it.

[0019] Monitoring Server: 1) Confirm the monitoring terminal's notification of starting monitoring; 2) After receiving the upgrade task from the monitoring terminal, send a "start upgrade command" to the corresponding monitoring information source; 3) After receiving the "Start Upgrade Command Confirmation" from the monitoring information source, send the upgrade status information to the "Software Upgrade Status Event" topic, and start sending the upgrade file and file verification code to the monitoring information source; Cut the upgrade file into file slices according to a fixed size, number them in order from small to large, and send them to the monitoring information source in the format of "upgrade file slice content" frame one by one; The "Upgrade File Slice Content" frame includes: 1. Total number of file slices; 2. Current file number; 3. File slice content; 4. File slice content verification code; 4) After receiving the "Confirmation of File Batch Receiving" from the monitoring information source, send the upgrade status information to the "Software Upgrade Status Event" topic according to the file sending progress; 5) After receiving the "file verification passed message" from the monitoring information source, send the upgrade status information to the "software upgrade status event" topic; 6) After receiving the "software upgrade completion message" from the monitoring information source, send the upgrade status information to the "software upgrade status event.

[0020] Monitoring information sources: 1) After receiving the "start upgrade command" from the monitoring server, enter the upgrade mode; 2) After receiving the "upgrade file slice content" from the monitoring server, save the file slice content and return the "file batch reception confirmation" signaling, where the number is the current file number in the received signaling; 3) After receiving all the upgrade file slices, assemble all the received file slices into one file in the order of numbering, and compare and verify with the overall file verification code. If it passes, a "file verification passed message" will be sent and the file will be burned 4) After burning is completed, enter the normal mode; like Figure 3 As shown in the figure, the software upgrade status is divided into the following categories: 1) In preparation: preparing for upgrade; 2) Downloading: When downloading the burning file, the download progress is displayed in percentage; Whether all file slices are downloaded successfully, if successful, proceed to the next step, otherwise return to step 6); 3) Download successfully, burn the file; 4) Upgrade completed: Upgrade completed; 5) Upgrade failed: Upgrade failed.

[0021] The present invention can burn multiple machines simultaneously, visualize the burning status, transmit data through power carrier without adding additional lines, and the upgrade command is directly sent from the host computer to the MCU for operation, without the need for an FPGA transfer board to complete the operation.

[0022] The above contents are further detailed descriptions of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A system for remote burning of MCU software supporting status display in a railway system, comprising one or more monitoring information sources (including MCU), a monitoring server, and one or more monitoring terminals; Bidirectional information transmission between monitoring information source and monitoring server, and bidirectional information transmission between monitoring server and monitoring terminal; The monitoring information source has two working modes, normal mode and upgrade mode. In normal mode: it generates or outputs monitoring information; In upgrade mode, perform software upgrade; A monitoring server, used for collecting monitoring information of monitoring information sources; Send data to monitoring information sources, receive monitoring terminal data, and publish data to monitoring terminals; Monitoring terminal, providing user interface. Sending data to monitoring server and receiving data from monitoring server. Its characteristics are: when remotely burning software to MCU, the monitoring server sends the upgraded software to the monitoring information source, the monitoring terminal subscribes to the software upgrade status message from the monitoring server, displays the upgrade status according to the upgrade status message, and the monitoring information source sends the software upgrade status message to the monitoring server.

2. The system for remote burning of MCU software supporting status display in a railway system according to claim 1, characterized in that: The software remote burning workflow is as follows: Monitoring terminal: 1) Open the monitoring terminal; 2) Monitor the "Software Upgrade Status Event" topic and notify the monitoring server; 3) The operator selects the device to be upgraded and the upgrade version, and submits the upgrade task; 4) Wait for the monitoring server to receive the monitoring information source upgrade status information, and change the status on the interface after receiving it; Monitoring Server: 1) Confirm the monitoring terminal's notification of starting monitoring; 2) After receiving the upgrade task from the monitoring terminal, send the "start upgrade command" to the corresponding monitoring information source; 3) After receiving the "Start Upgrade Command Confirmation" from the monitoring information source, send the upgrade status information to the "Software Upgrade Status Event" topic, and start sending the upgrade file and file verification code to the monitoring information source; 4) After receiving the "Confirmation of File Batch Receiving" from the monitoring information source, send the upgrade status information to the "Software Upgrade Status Event" topic according to the file sending progress; 5) After receiving the "file verification passed message" from the monitoring information source, send the upgrade status information to the "software upgrade status event" topic; 6) After receiving the "software upgrade completion message" from the monitoring information source, send the upgrade status information to the "software upgrade status event; Monitoring information sources: 1) After receiving the "start upgrade command" from the monitoring server, enter the upgrade mode; 2) After receiving the "upgrade file slice content" from the monitoring server, save the file slice content and return the "file batch reception confirmation" signaling, where the number is the current file number in the received signaling; 3) After receiving all the upgrade file slices, assemble all the received file slices into one file in the order of numbering, and compare and verify with the overall file verification code. If it passes, a "file verification passed message" will be sent and the file will be burned 4) After burning is completed, enter normal mode.

3. The system for remote burning of MCU software supporting status display in a railway system according to claim 2, characterized in that: The upgrade file slicing is to cut the upgrade file into file slices according to a fixed size, number them in order from small to large, and send them to the monitoring information source in the format of "upgrade file slice content" frame one by one; The "Upgrade File Slice Content" frame includes: 1) Total number of file slices; 2) Current file number; 3) File slice content; 4) File slice content verification code.

4. The system for remote burning of MCU software supporting status display in a railway system according to claim 1, characterized in that: The software upgrade status includes the following: 1) In preparation: preparing for upgrade; 2) Downloading: When downloading the burning file, the download progress is displayed in percentage; After downloading each slice, use the slice checksum to verify it. If successful, download the next file slice. If failed, return to step 6. After the last slice is downloaded successfully, all the file slices are combined into a burning file in order and the verification code is verified. If successful, proceed to the next step. If failed, return to step 6; 3) Download successfully, burn the file; 4) Upgrade completed: Upgrade completed; 5) Upgrade failed: Upgrade failed.