Instrument log acquisition device

Abstract

The invention relates to an instrument log acquisition device. The instrument log acquisition device comprises an upper computer unit; the upper computer unit is respectively configured with log storage addresses of the bottom plate MCU and the core plate CPU; a bottom plate of the instrument to be tested is provided with a special log storage space for a bottom plate MCU and a core plate CPU, and a bottom plate mcu log and a core plate CPU log are respectively uploaded to the special log storage space of the upper computer unit; and mcu and core board cpu serial port logs do not need to be welded on each instrument, so that the labor cost is saved.

Description

Technical Field

[0001] The invention relates to the field of instrument testing, and in particular to a device for acquiring an instrument log. Background Art

[0002] In the daily testing of instruments, in order to quickly locate the cause of the problem, it is necessary to capture the instrument log and find the cause by analyzing the log. The instrument log is generally captured through serial communication. There are two types of instrument logs: baseboard MCU logs and core version (also known as CPU) logs.

[0003] In the traditional log capture method, the following steps need to be performed before testing to start capturing logs: solder serial port line 1 connected to the MCU log and serial port line 2 connected to the core board log; connect the two serial port lines to the corresponding serial port boards respectively; connect the serial port boards to the USB ports of the computer respectively; install serial port printing log tools on the computer, such as Xshell and SecureCRT; open the serial port tool and select the ports corresponding to the two serial port boards. After selecting the serial port baud rate, the MCU log and CPU log of the instrument can be successfully connected. The log windows corresponding to the MCU and CPU need to be opened respectively; in the serial port tool, enter the log printing command, perform instrument operations, and start capturing the instrument MCU log and CPU log.

[0004] The problems of traditional log capture methods include: Each instrument needs to be welded with MCU logs and CPU logs. If multiple instruments need to be tested, multiple logs need to be welded. When the baseboard or core board is damaged, it needs to be replaced with a new one, and the serial port line needs to be re-welded. It consumes labor costs. When multiple instruments need to be tested at the same time (up to 50 instruments can be tested at a time), and multiple instrument logs need to be connected, due to insufficient USB ports on the computer, it is necessary to expand a multi-port USB tool (USB hub) on the computer and add multiple computers (one computer cannot carry it), thereby increasing the cost of the test tool. One instrument requires 2 serial port boards, and more are required for multiple instruments, increasing the cost of the test tool (consumables). When multiple instruments need to be tested, a lot of time is needed to build the test environment. The method of obtaining instrument logs through the serial port is limited to the internal testing stage. When the instrument is shipped to B-end customers or users, it does not have the function of obtaining logs through the serial port. Therefore, when receiving customer problem feedback in this case, it is difficult for the supplier to quickly analyze and solve the problem because there is no log, which greatly increases the difficulty of solving the problem. Summary of the invention

[0005] The present invention aims at the technical problems existing in the prior art and provides a device for obtaining instrument logs, which does not require welding MCU and core board CPU serial port logs for each instrument, thus saving labor costs.

[0006] According to a first aspect of the present invention, there is provided a device for acquiring an instrument log, comprising: a host computer unit;

[0007] The host computer unit configures the log storage address of the baseboard MCU and the core board CPU respectively;

[0008] The bottom plate of the instrument to be tested is provided with dedicated log storage space for the bottom plate MCU and the core plate CPU, and the bottom plate MCU log and the core plate CPU log are uploaded to the dedicated log storage space of the host computer unit respectively.

[0009] Based on the above technical solution, the present invention can also make the following improvements.

[0010] Optionally, the host computer unit further includes: a configuration unit;

[0011] The configuration unit receives configuration information set by the user to obtain the instrument log, and the configuration information includes: a log switch;

[0012] After the instrument to be tested is powered on, the log is printed and uploaded when it is determined that the log switch is in the on state; otherwise, the instrument homepage is entered without automatically printing the log.

[0013] Optionally, the configuration information includes: size of a single log file.

[0014] Optionally, the process of printing and uploading the log of the instrument under test includes: the bottom board MCU prints the log;

[0015] The process of printing logs by the core board CPU includes:

[0016] When the core board cpu starts to print logs and reaches the size of a single log file, the newly created log file continues to print, and the core board cpu logs are transmitted to the bottom board for storage.

[0017] Optionally, the process of printing and uploading the log of the instrument under test includes: the core board CPU prints the log;

[0018] When the baseboard MCU starts printing logs and reaches the size of a single log file, the newly created log file continues printing.

[0019] Optionally, the configuration information further includes: selecting to copy the local log to be uploaded to a USB disk or to upload it to the host computer unit;

[0020] The process of printing and uploading the log of the instrument under test also includes: copying the local log to be uploaded to a U disk or uploading it to the host computer unit;

[0021] Optionally, the process of uploading the local log to be uploaded includes:

[0022] Determine whether the instrument holds logs to be uploaded locally. If yes, remind the user to confirm uploading the logs. After receiving the confirmation from the user, upload the logs. If the upload is successful, the baseboard MCU deletes the uploaded logs. If not, remind the user whether to re-upload the logs. Re-upload or interrupt the upload according to the user's configuration information.

[0023] Optionally, the process of copying the local log to be uploaded to the USB disk includes:

[0024] Determine whether the instrument holds the log to be copied locally. If yes, remind the user to confirm the connection of the USB flash drive. After receiving the user's confirmation message, copy the log. If the copy is successful, the baseboard MCU deletes the copied log. If it is unsuccessful, remind the user whether to copy the log again, and re-transmit or interrupt the copy according to the user's configuration information.

[0025] The present invention provides a device for obtaining instrument logs, which does not require welding of MCU and core board CPU serial port logs for each instrument, thus saving labor costs. No serial port board and USB hub are required to save consumable costs. When multiple instruments are tested at the same time, there is no need to connect serial port logs, thus saving the cost of setting up the test environment. Usually, when multiple instruments are tested at the same time, it takes at least 0.5 to 1.5 days to set up a single environment. Different test items require different environments to be set up. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 This is a schematic diagram of the traditional instrument log capture method;

[0027] Figure 2 A log storage business flow chart of an embodiment of a device for acquiring instrument logs provided by the present invention. DETAILED DESCRIPTION

[0028] The principles and features of the present invention are described below in conjunction with the accompanying drawings. The examples given are only used to explain the present invention and are not used to limit the scope of the present invention.

[0029] The present invention provides an instrument log acquisition device comprising: a host computer unit.

[0030] The host computer unit configures the log storage addresses of the baseboard MCU and the core board CPU respectively.

[0031] The bottom plate of the instrument to be tested is provided with dedicated log storage space for the bottom plate MCU and the core plate CPU, and the bottom plate MCU log and the core plate CPU log are uploaded to the dedicated log storage space of the host computer unit respectively.

[0032] The present invention provides a device for obtaining instrument logs, which does not require welding of MCU and core board CPU serial port logs for each instrument, thus saving labor costs. No serial port board and USB hub are required to save consumable costs. When multiple instruments are tested at the same time, there is no need to connect serial port logs, thus saving the cost of setting up the test environment. Usually, when multiple instruments are tested at the same time, it takes at least 0.5 to 1.5 days to set up a single environment. Different test items require different environments to be set up.

[0033] Example 1

[0034] Embodiment 1 provided by the present invention is an embodiment of a device for obtaining an instrument log provided by the present invention, such as Figure 2 A log storage business flow chart of an embodiment of an instrument log acquisition device provided by the present invention, combined with Figure 2 It can be known that the embodiment of the acquisition device includes: a host computer unit.

[0035] The host computer unit configures the log storage addresses of the baseboard MCU and the core board CPU respectively.

[0036] The bottom plate of the instrument to be tested is provided with dedicated log storage space for the bottom plate MCU and the core plate CPU, and the bottom plate MCU log and the core plate CPU log are uploaded to the dedicated log storage space of the host computer unit respectively.

[0037] In a possible embodiment, the host computer unit further includes: a configuration unit.

[0038] The configuration unit accepts the configuration information set by the user to obtain the instrument log, and the configuration information includes: log switch.

[0039] After the instrument to be tested is powered on, the log will be printed and uploaded when the log switch is turned on. Otherwise, the log will not be automatically printed when the instrument homepage is entered.

[0040] In a possible embodiment, the configuration information includes: a single log file size.

[0041] In a possible embodiment, the process of printing and uploading the log of the instrument under test includes: the bottom board MCU prints the log.

[0042] The process of the core board CPU printing log includes:

[0043] When the core board CPU starts printing logs and reaches the size of a single log file, the newly created log file continues to print and the core board CPU logs are transmitted to the bottom board for storage.

[0044] In a possible embodiment, the process of printing and uploading the log of the instrument under test includes: the core board CPU prints the log.

[0045] When the baseboard MCU starts printing logs and reaches the size of a single log file, the newly created log file continues printing.

[0046] In specific implementation, after the instrument is turned off, it stops printing logs and saves the last log.

[0047] In a possible embodiment, the configuration information further includes: selecting to copy the local log to be uploaded to a USB disk or to upload it to a host computer unit.

[0048] The process of printing and uploading the log of the instrument to be tested also includes: copying the local log to be uploaded to a U disk or uploading it to the host computer unit.

[0049] In a possible embodiment, the process of uploading the local log to be uploaded includes:

[0050] Determine whether the instrument holds logs to be uploaded locally. If yes, remind the user to confirm uploading the logs. After receiving the confirmation from the user, upload the logs. If the upload is successful, the baseboard MCU deletes the uploaded logs. If not, remind the user whether to re-upload the logs. Re-upload or interrupt the upload according to the user's configuration information.

[0051] In a possible embodiment, the process of copying the local log to be uploaded to the USB disk includes:

[0052] Determine whether the instrument holds the log to be copied locally. If yes, remind the user to confirm the connection of the USB flash drive. After receiving the user's confirmation message, copy the log. If the copy is successful, the baseboard MCU deletes the copied log. If it is unsuccessful, remind the user whether to copy the log again, and re-transmit or interrupt the copy according to the user's configuration information.

[0053] Specifically, the acquisition process of an embodiment of a device for acquiring an instrument log provided by the present invention includes:

[0054] Set up a log storage server. The server is configured with the log storage address of the baseboard MCU: ur l 1; the log storage address of the core board CPU: ur l 2. The instrument baseboard is designed with a 4G network module. The instrument baseboard is designed with dedicated storage space for MCU and core board CPU logs. The USB device interface is designed in the instrument interface definition, and the USB flash drive is connected through this interface. In the instrument version information interface, press and hold the OK key for 10 seconds to enter the password input interface. After entering the password, the engineering interface is automatically entered. Log printing is turned off by default. After selecting to turn it on, select the log saving method according to the usage environment. For example, select USB flash drive copy for internal testing; after shipment, select upload to the server. When the log switch is turned off, the two options below are grayed out and cannot be operated. After changing the log switch status, you need to restart the instrument for the setting to take effect. The storage format of MUC log is: project number_instrument unique id_MCU_YYYYMMDDhhmmss.log; the storage format of core board cpu log is: project number_instrument unique id_MCU_YYYYMMDDhhmmss.log; for example: JMMT01_1234567_MCU_20240723145959.log; the time is the time when the log file is created. Set the size of a single log file: for example, 200M. After exceeding 200M, recreate the next log file. Configure the mcu and core board cpu upload addresses in the baseboard MCU. After the instrument is turned on, the core board system will first determine whether the log switch is turned on. If not, the log will not be printed automatically; if it is turned on, it will start to create the core board cpu log file and start printing all user operation logs; at the same time, the core board system notifies the MCU that the log is turned on. After receiving the notification, the MCU responds to the core board cpu, and then starts to create the MCU log file and starts printing all user operation logs. When the size of the core board cpu log file reaches 200M, a new log file is created and printing continues. At the same time, the previous log file is sent to the MCU. After receiving the log, the MCU responds to the core board cpu and saves the core board cpu log in the bottom board log storage space. When the system determines that the user has turned off the electric door lock (turned off the key), the log printing stops and the last log is saved. When the user chooses to upload to the server: the next time the instrument is turned on, the MCU continues to print and save new logs while judging whether there are local logs to be uploaded. The date in the log file name is earlier than the current instrument date. If there are, a pop-up window prompts the user: There are logs to be uploaded to the server. Do you want to upload them? After clicking [OK], the logs will start to be uploaded to the corresponding place of the server according to the pre-configured server address. After the transmission is completed, it prompts that the upload is successful. After the upload is completed, the local log is cleared. If the upload fails, the log is not cleared, and the user is reminded whether to re-upload until the upload is successful. If the user clicks Cancel, the upload is interrupted.When the user chooses to copy the log to the USB flash drive: The next time the instrument is turned on, the MCU will continue to print and save new logs while determining whether there are local logs to be copied, and the date in the log file name is earlier than the current instrument date. If there are, a pop-up window will prompt the user: Please connect the USB flash drive and copy the new log. After clicking OK, start copying to the USB flash drive and directory. After the copy is completed, a pop-up window will prompt that the copy is successful. At the same time, the copied logs will be cleared. If the copy fails, the user will be reminded whether to continue copying. Until the copy is successful. If the user clicks Cancel, the copy will be interrupted. According to the date and time of the fault reported by the user, go to the server or P disk to find the corresponding log file, and you can use the log to determine the cause of the fault, so that the fault can be solved quickly and effectively.

[0055] An instrument log acquisition device provided by an embodiment of the present invention does not need to weld MCU and core board CPU serial port logs for each instrument, saving labor costs. No serial port board and USB hub are needed to save consumable costs. When multiple instruments are tested at the same time, there is no need to connect serial port logs, saving the cost of setting up the test environment. Usually, when multiple instruments are tested at the same time, it takes at least 0.5 to 1.5 days to set up a single environment. Different test items require different environments to be set up.

[0056] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0057] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0058] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0059] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0060] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0061] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0062] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A device for acquiring instrument logs, characterized in that: The acquisition device comprises: a host computer unit; The host computer unit configures the log storage address of the baseboard MCU and the core board CPU respectively; The bottom plate of the instrument to be tested is provided with dedicated log storage space for the bottom plate MCU and the core plate CPU, and the bottom plate MCU log and the core plate CPU log are uploaded to the dedicated log storage space of the host computer unit respectively.

2. The acquisition device according to claim 1, characterized in that: The host computer unit also includes: a configuration unit; The configuration unit receives configuration information set by the user to obtain the instrument log, and the configuration information includes: a log switch; After the instrument to be tested is powered on, the log is printed and uploaded when it is determined that the log switch is in the on state; otherwise, the instrument homepage is entered without automatically printing the log.

3. The acquisition device according to claim 1, characterized in that: The configuration information includes: the size of a single log file.

4. The acquisition device according to claim 3, characterized in that: The process of printing and uploading the log of the instrument under test includes: the core board CPU prints the log; The process of printing logs by the core board CPU includes: When the core board cpu starts to print logs and reaches the size of a single log file, the newly created log file continues to print, and the core board cpu logs are transmitted to the bottom board for storage.

5. The acquisition device according to claim 3, characterized in that: The process of printing and uploading the log of the instrument under test includes: the bottom board MCU prints the log; When the baseboard MCU starts printing logs and reaches the size of a single log file, the newly created log file continues printing.

6. The acquisition device according to claim 1, characterized in that: The configuration information also includes: selecting to copy the local log to be uploaded to a USB disk or to upload it to the host computer unit; The process of printing and uploading the log of the instrument under test also includes: copying the local log to be uploaded to a U disk or uploading it to the host computer unit.

7. The acquisition device according to claim 6, characterized in that: The process of uploading the local logs to be uploaded includes: Determine whether the instrument holds logs to be uploaded locally. If yes, remind the user to confirm uploading the logs. After receiving the confirmation from the user, upload the logs. If the upload is successful, the baseboard MCU deletes the uploaded logs. If not, remind the user whether to re-upload the logs. Re-upload or interrupt the upload according to the user's configuration information.

8. The acquisition device according to claim 1, characterized in that: The process of copying the local log to be uploaded to the USB disk includes: Determine whether the instrument holds the log to be copied locally. If yes, remind the user to confirm the connection of the USB flash drive. After receiving the user's confirmation message, copy the log. If the copy is successful, the baseboard MCU deletes the copied log. If it is unsuccessful, remind the user whether to copy the log again, and re-transmit or interrupt the copy according to the user's configuration information.

Images