CN116955195A - Power module debugging method and device, upper computer and storage medium - Google Patents

Power module debugging method and device, upper computer and storage medium Download PDF

Info

Publication number
CN116955195A
CN116955195A CN202310947610.1A CN202310947610A CN116955195A CN 116955195 A CN116955195 A CN 116955195A CN 202310947610 A CN202310947610 A CN 202310947610A CN 116955195 A CN116955195 A CN 116955195A
Authority
CN
China
Prior art keywords
plug
upper computer
description information
configuration file
ins
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310947610.1A
Other languages
Chinese (zh)
Inventor
李睿
马群
张�浩
梁宇飞
宋鑫
王首印
白朝阳
刘梦飞
许莉涛
李世龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shijiazhuang Tonghe Electronics Co Ltd
Original Assignee
Shijiazhuang Tonghe Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shijiazhuang Tonghe Electronics Co Ltd filed Critical Shijiazhuang Tonghe Electronics Co Ltd
Priority to CN202310947610.1A priority Critical patent/CN116955195A/en
Publication of CN116955195A publication Critical patent/CN116955195A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G06F9/4451—User profiles; Roaming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)

Abstract

The application provides a power module debugging method, a device, an upper computer and a storage medium, and configuration files stored in the upper computer are obtained; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; changing the description information of the configuration file to add/delete the association relation between the plug-ins; and associating plug-ins in the upper computer according to the description information of the configuration file so as to complete the debugging process of the upper computer. The function of the upper computer is separated into a plurality of plug-ins, then a configuration file read in real time is designed, and the plug-ins are associated by using the description information of the configuration file, so that plug-in connection is dynamically realized, the problem of high coupling caused by static connection between codes is avoided, and when a new power module is tested, only part of plug-ins are required to be replaced and the description information of the configuration file is modified, and the upper computer is not required to be redesigned, so that the upper computer can be reused.

Description

Power module debugging method and device, upper computer and storage medium
Technical Field
The application belongs to the technical field of equipment debugging, and particularly relates to a power module debugging method and device, an upper computer and a storage medium.
Background
Whether the power module is used in the charging pile of the charging station, the vehicle-mounted power module, or the military power supply and the electric power module, an upper computer is generally designed in the power debugging process and used for real-time monitoring of the states of all the power modules so as to accurately position the problems of the power modules in the module debugging process, thereby optimizing the problems.
Because different power supply modules are designed differently, the content to be detected is also different, and thus the functional plug-ins required to be used in the debugging process are also different. Therefore, in the prior art, a designer writes codes of different upper computers according to the type of the power module. Because the upper computer can not be reused, when debugging different power modules, a designer needs to design different upper computers according to different functional modules, and the internal codes of each upper computer are mixed, so that the upper computers are difficult to multiplex and modify.
Disclosure of Invention
In view of the above, the application provides a power module debugging method, a device, an upper computer and a storage medium, which aim to solve the problem that the upper computer for debugging the power module is difficult to reuse in the prior art.
A first aspect of an embodiment of the present application provides a power module debugging method, including:
acquiring a configuration file stored in an upper computer; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in unit of each upper computer is used for realizing one function of the upper computer;
changing the description information of the configuration file to add/delete the association relation between the plug-ins;
and according to the description information of the configuration file, the plug-ins in the upper computer are associated, so that each associated plug-in operates according to the corresponding debugging steps, and the debugging process of the upper computer is completed.
A second aspect of an embodiment of the present application provides a power module debugging device, including:
the acquisition module is used for acquiring the configuration file stored in the upper computer; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in unit of each upper computer is used for realizing one function of the upper computer;
the change module is used for changing the description information of the configuration file so as to add/delete the association relation between the plug-ins;
and the debugging module is used for associating the plug-ins in the upper computer according to the description information of the configuration file, so that each associated plug-in unit operates according to the corresponding debugging steps to complete the debugging process of the upper computer.
A third aspect of an embodiment of the present application provides a host computer, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the power module debugging method of the first aspect above when the processor executes the computer program.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the power module debugging method of the first aspect above.
The embodiment of the application provides a power module debugging method, a device, an upper computer and a storage medium, wherein a configuration file stored in the upper computer is firstly obtained; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in unit of each upper computer is used for realizing one function of the upper computer; changing the description information of the configuration file to add/delete the association relation between the plug-ins; and according to the description information of the configuration file, the plug-ins in the upper computer are associated, so that each associated plug-in operates according to the corresponding debugging steps, and the debugging process of the upper computer is completed. The function of the upper computer is separated into a plurality of plug-ins, then a configuration file read in real time is designed, and the plug-ins are associated by using the description information of the configuration file, so that plug-in connection is dynamically realized, the problem of high coupling caused by static connection between codes is avoided, and when a new power module is tested, only part of plug-ins are required to be replaced and the description information of the configuration file is modified, and the upper computer is not required to be redesigned, so that the upper computer can be reused.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is an application scenario diagram of a power module debugging method provided by an embodiment of the present application;
FIG. 2 is a flowchart of an implementation of a power module debugging method provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of the association of each plug-in unit of the upper computer according to the embodiment of the present application;
FIG. 4 is a schematic diagram of description information of a configuration file according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a power module debugging device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an upper computer according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
Fig. 1 is an application scenario diagram of a power module debugging method provided by an embodiment of the present application. As shown in fig. 1, in some embodiments, the power module debugging method provided by the embodiment of the present application may be applied to the application scenario, but is not limited to the application scenario. In an embodiment of the application, the system comprises: a power module 11 and an upper computer 12.
The power supply module 11 may be a power supply module used in a charging pile, a vehicle-mounted power supply module, a military power supply, a power supply module, or the like, and is not limited herein. The host computer 12 may be a computer, an MCU, etc., and is not limited herein. After the power module 11 is connected with the related debugging device, the upper computer 12 realizes the debugging of the power module 11 through the function designed in the upper computer, and the debugging result is obtained.
Fig. 2 is a flowchart of an implementation of a power module debugging method according to an embodiment of the present application. As shown in fig. 2, in some embodiments, a power module debugging method is applied to the host computer 12 shown in fig. 1, and the method includes:
s210, acquiring a configuration file stored in an upper computer; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in of each upper computer is used for realizing one function of the upper computer.
In the embodiment of the application, each plug-in of the upper computer can be independently developed and used, and each plug-in is not interfered with each other and becomes independent engineering. Therefore, when a new power module is tested, only part of plug-ins need to be replaced, and other plug-ins can still be used continuously, so that the development cost of the upper computer is reduced. And because the plug-ins are mutually independent, the replacement of the plug-ins does not affect the operation of other plug-ins, and only the description information of the configuration file is required to be changed, and the association relation of each plug-in is changed into association with a new plug-in after replacement.
S220, the description information of the configuration file is changed to add/delete the association relation between the plug-ins.
In the embodiment of the present application, the above described modification process of the description information may be automatically implemented by the upper computer according to the type of the power module to be debugged, or may be implemented by a debugger manually operating the upper computer, which is not limited herein.
S230, according to the description information of the configuration file, the plug-ins in the upper computer are associated, so that each associated plug-in operates according to the corresponding debugging steps, and the debugging process of the upper computer is completed.
In the embodiment of the application, the description information of the configuration file expresses the association relation among the plug-ins, namely the signal transmission relation of each plug-in, and after the description information is changed, the plug-ins are instructed to operate according to the signal transmission relation, so that the test of the power supply module is realized.
In the embodiment of the application, the function of the upper computer is separated into a plurality of plug-ins, then a configuration file read in real time is designed, and the plug-ins are associated by using the description information of the configuration file, so that the plug-in connection is dynamically realized, the problem of high coupling caused by static connection between codes is avoided, and when a new power module is tested, only part of plug-ins are required to be replaced and the description information of the configuration file is required to be modified, and the upper computer is not required to be redesigned, thereby realizing the multiplexing of the upper computer.
In some embodiments, the description information of the display configuration file includes the ids of the individual plug-ins and the ids of the associated plug-ins for each plug-in. Correspondingly, the method further comprises the steps of: when a configuration instruction is received, determining a first plug-in and a second plug-in according to plug-ins and description information corresponding to the configuration instruction; the first plug-in is a plug-in to be replaced, and the second plug-in is used for replacing the first plug-in.
The configuration instruction is an instruction formulated by an upper computer debugging personnel according to the debugging requirement of the power module, and the configuration instruction comprises plug-ins required by the dynamic library when the power module is debugged and description information of the corresponding plug-ins required by the configuration file.
Accordingly, S220 may include: changing the id of the first plug-in into the id of the second plug-in the description information; if the associated plug-in of any plug-in except the first plug-in the description information is the first plug-in, the id of the associated plug-in of the plug-in is changed from the id of the first plug-in to the id of the second plug-in.
In the embodiment of the application, when a new power module is tested, if all the functional plug-ins corresponding to the power module are stored in the upper computer, the upper computer can automatically realize the replacement process of the plug-ins according to the configuration instruction and automatically modify the configuration file to complete the debugging of the power module.
In some embodiments, S230 may include: determining a signal transmission relation among all plug-ins of the upper computer according to the description information of the configuration file; and running each plug-in the upper computer according to the debugging step corresponding to the configuration instruction, and transmitting the electric signals generated in the debugging step according to the signal transmission relation.
In the embodiment of the application, when a plurality of functional plug-ins are combined together for use, one side of the plug-ins receiving signals is used as the associated plug-in of the side sending the signals. Wherein, the associated plug-in of a plug-in can be one, a plurality of or no associated plug-in, and is not limited herein.
In some embodiments, prior to determining the first and second plug-ins, the method further comprises: acquiring the type of a power module to be debugged; judging whether the type of the power supply module is a known type; when the type of the power module is a known type, the configuration instruction is determined according to the type of the power module.
In the embodiment of the application, when the tested power module is known (namely, the plug-in unit needed to be used by the type of the power module is stored in the upper computer), a corresponding configuration instruction can be automatically generated according to the type of the power module, and then the plug-in unit is automatically replaced and the configuration file is automatically modified, so that the testing process of the power module is completed.
The modification process of the configuration file is triggered by the configuration instruction, so that the configuration file can be automatically replaced after the configuration instruction is determined. After each debugging of the power module, the type of the power module, the used configuration instruction and corresponding configuration file information are recorded in the upper computer, a configuration instruction editing window is arranged on the upper computer, and the labels of the power modules of various known types, such as a power supply 1, a power supply 2, a power supply 5, are displayed in the editing window. For example, when the power supply 5 is debugged, the corresponding label of the power supply 5 is clicked, the upper computer automatically sends out the configuration instruction corresponding to the power supply 5, and the configuration file indicated by the configuration instruction is selected from the stored configuration files for use, so that the replacement process of the configuration files is completed.
When the type of the power supply module is unknown, the plug-in required by the unknown power supply module can be developed by a developer, and the replacement of the plug-in and the modification of the configuration file can be manually realized on the upper computer by the developer. The specific procedure is shown in the examples below.
In some embodiments, the description information of the display configuration file includes the ids of the individual plug-ins and the ids of the associated plug-ins for each plug-in. Accordingly, S210 may include: and responding to the configuration operation of the host interface of the upper computer, and displaying the description information of the configuration file on the host interface of the upper computer.
Accordingly, S220 may include: and responding to the change operation of the host interface of the upper computer, and changing the ids of the various plug-ins and the ids of the associated plug-ins of each plug-in.
In some embodiments, a plurality of main labels are arranged on a main interface of the upper computer, and at least one sub-label is arranged under each main label; each sub-label corresponds to the description information of at least one plug-in. Correspondingly, responding to the configuration operation of the host interface of the host computer, displaying the description information of the configuration file on the host interface of the host computer comprises the following steps: and responding to the configuration operation of the host interface of the upper computer on any sub-label, and displaying the description information of at least one plug-in corresponding to the sub-label on the host interface of the upper computer.
In the embodiment of the application, the main label refers to toolbar content of a main interface and comprises the following components: tools, files, edits, aids, etc. The sub-tags refer to sub-content contained under the main tag, for example, after the description of the configuration file is performed, the host computer main interface reads the configuration file in the main interface, so that the sub-tags can be dynamically added in the main tag tool, and the main tag tool sub-tag is as follows: CAN tools and CAN drive settings. The CAN tools function is formed by connecting 3 plug-ins of a CAN display interface, a protocol plug-in and a CAN drive, and the CAN drive setting function is formed by connecting 2 plug-ins of a CAN drive setting interface plug-in and a CAN drive plug-in.
In the embodiment of the application, the configuration file can be dynamically added and deleted by adding or deleting the contents of the sub-tags. Plug-and-play can be performed on the plug-in.
In the embodiment of the application, the configuration operation of the host interface of the upper computer can be that the host interface of the upper computer clicks the corresponding host label, the host label is unfolded to display a plurality of sub-labels below the host label, then the host interface of the upper computer clicks the sub-label, at the moment, the configuration operation is considered to be triggered, and the description information of at least one plug-in corresponding to the sub-label is displayed on the host interface of the upper computer. Correspondingly, when the modifiable content in the description information of at least one plug-in corresponding to the sub-label displayed on the main interface is changed, the change operation is considered to be triggered, and then the changed content is stored in the upper computer.
In some embodiments, after modifying the description information of the configuration file to add/delete the association relationship between the plugins, the method further includes: and adding/changing/deleting the sub-tags on the main interface of the upper computer according to the description information of the configuration file.
In the embodiment of the application, after the configuration file is changed, the sub-label and the main label on the main interface are correspondingly updated, so that the content in the configuration file corresponds to the content indicated by the sub-label.
Fig. 3 is a schematic diagram of association of each plug-in unit of an upper computer according to an embodiment of the present application. As shown in fig. 3, in some embodiments, the plug-in of the upper computer includes a first subset and a second subset; the first subset comprises a CAN display interface plug-in, a protocol plug-in and a CAN drive plug-in; the second subset includes a CAN drive setup interface, a CAN drive plug-in; the CAN drive cards in the first subset and the second subset are the same card.
In the embodiment of the application, in order to avoid the problem of high coupling caused by static connection between codes, the purposes of reducing code modification and decoupling among various plug-ins and achieving 'plug-and-play' are realized. If the protocol required by the client is changed, only the protocol plug-in is required to be changed, namely, the protocol 1 is changed into the protocol 2, and the other three plug-ins are not required to be changed.
In the embodiment of the application, the CAN driving plug-in is a plug-in repeatedly applied to the two subsets, and in the description process, only the association relation of the plug-in the current subset is required to be described, and the association relation in other subsets is not required to be described, so that the conditions of repeated description and insufficient description are avoided.
Fig. 4 is a schematic diagram of description information of a configuration file according to an embodiment of the present application. As shown in fig. 4, in some embodiments, each subset corresponds to a primary key and each plug-in corresponds to a secondary key in the profile's description information. The sub value of the sub key is the description information corresponding to the plug-in.
The primary key is the entry id of two subsets, and the primary value is the value corresponding to the primary key, and is also the set of the child key and the child value:
for the first subset, the primary key is: CAN display interface id;
for the second subset, the primary key is: the CAN driver sets the interface id.
The sub-keys of the first subset are: CAN display interface id, protocol plug-in id, CAN drive id;
the sub-keys of the second subset are: the CAN driver sets an interface id and a CAN driver id.
The content of each sub-value, i.e., the descriptive information, may include, but is not limited to, at least one of:
description information one: the authors.
Descriptive information II: the number of plug-in applications is used in the reusable plug-in.
Description information three: and if the number of the plug-in associated plug-ins is n, describing the plug-ins one by one.
Descriptive information four: the plug-in id.
Description information five: the position of the plug-in on the main interface is used for displaying the interface position when the plug-in is displayed on the main interface.
Description information six: the plug-in master tag.
Description information seven: the plug-in sub-label.
5. The associated plug-ins respectively introducing the respective sub-values are as follows:
for the first subset:
firstly, because the signals sent by the CAN display interface need to be connected with the grooves of the protocol 1 and no other signals exist, the associated plug-in of the CAN display interface plug-in is the protocol 1id;
second, the protocol 1 sends two signals to connect the CAN display interface and the CAN driver respectively, so the associated plug-ins of the protocol 1 plug-ins are respectively: CAN display interface id and CAN drive id;
third, the CAN drive transmit signals, although two, are connected to the CAN drive setup interface as content in the second subset, so only the signal slot connection to protocol 1 is in jurisdiction of the first subset, and therefore the associated plug-in for the CAN drive plug-in is: protocol plug-in id.
For the second subset:
firstly, a CAN drive setting interface only sends signals to a CAN drive, and other signals are not available, and an associated plug-in of the CAN drive setting interface plug-in is a CAN drive id;
second, the CAN drive transmission signals are two, but only the connections to the CAN drive setup interface are the contents of the second subset, so the associated plug-in of the CAN drive plug-in is: the CAN driver sets the interface id.
In summary, the beneficial effects of the application are as follows:
CAN drive, protocol 1 and protocol 2 are respectively different plug-ins. The plug-ins are not interfered with each other, and the plug-ins are respectively formed into independent engineering. If the protocol 3 exists, only the content of the protocol 3 needs to be developed, and the CAN drive does not need to be repeatedly developed.
2. The connection relation of each plug-in is described in the configuration file, and the host computer main interface is automatically connected according to the description information in the configuration file, so that the connection relation in the configuration file is only deleted or added no matter the function is added or deleted.
3. The description information of the configuration file not only comprises the connection relation among the plug-ins, but also comprises display information related to a main interface, and the main interface can update the toolbar in real time according to the description information.
4. The description information of the configuration file describes that the same plugin is repeatedly used in different subsets according to a 'subset' mode, and then the associated plugin is added according to the application relation of the plugin in the current subset.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.
Fig. 5 is a schematic structural diagram of a power module debugging device according to an embodiment of the present application. As shown in fig. 5, in some embodiments, the power module commissioning device 5 includes:
the obtaining module 510 is configured to obtain a configuration file stored in the upper computer; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in of each upper computer is used for realizing one function of the upper computer.
And a modification module 520, configured to modify the description information of the configuration file to add/delete the association relationship between the plugins.
And the debugging module 530 is used for associating the plug-ins in the upper computer according to the description information of the configuration file, so that each associated plug-in operates according to the corresponding debugging steps to complete the debugging process of the upper computer.
Optionally, the description information of the display configuration file includes an id of each plug-in and an id of an associated plug-in of each plug-in. Correspondingly, the power module debugging device 5 further comprises: the first determining module is used for determining a first plug-in and a second plug-in according to plug-ins and description information corresponding to the configuration instructions when the configuration instructions are received; the first plug-in is a plug-in to be replaced, and the second plug-in is used for replacing the first plug-in; correspondingly, the modification module 520 is specifically configured to modify the id of the first plug-in to the id of the second plug-in the description information; if the associated plug-in of any plug-in except the first plug-in the description information is the first plug-in, the id of the associated plug-in of the plug-in is changed from the id of the first plug-in to the id of the second plug-in.
Optionally, the debug module 530 is configured to determine a signal transmission relationship between each plug-in unit of the upper computer according to the description information of the configuration file; and running each plug-in the upper computer according to the debugging step corresponding to the configuration instruction, and transmitting the electric signals generated in the debugging step according to the signal transmission relation.
Optionally, the power module debugging device 5 further includes: the second determining module is used for obtaining the type of the power module to be debugged; judging whether the type of the power supply module is a known type; and when the type of the power supply module is a known type, determining a plug-in corresponding to the configuration instruction according to the type of the power supply module.
Optionally, the description information of the display configuration file includes an id of each plug-in and an id of an associated plug-in of each plug-in. Correspondingly, the obtaining module 510 is configured to respond to a configuration operation of the host interface of the host computer, and display description information of the configuration file on the host interface of the host computer; correspondingly, the modification module 520 is specifically configured to modify the ids of the respective plug-ins and the ids of the associated plug-ins of each plug-in response to a modification operation of the host interface.
Optionally, a plurality of main labels are arranged on a main interface of the upper computer, and at least one sub-label is arranged under each main label; each sub-label corresponds to the description information of at least one plug-in; correspondingly, the obtaining module 510 is specifically configured to respond to a configuration operation of the host interface on any sub-label, and display, on the host interface of the host computer, description information of at least one plug-in corresponding to the sub-label.
Optionally, the plug-in of the upper computer comprises a first subset and a second subset; the first subset comprises a CAN display interface plug-in, a protocol plug-in and a CAN drive plug-in; the second subset includes a CAN drive setup interface, a CAN drive plug-in; the CAN drive cards in the first subset and the second subset are the same card.
The power module debugging device provided in this embodiment may be used to execute the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described here again.
Fig. 6 is a schematic structural diagram of an upper computer according to an embodiment of the present application. As shown in fig. 6, an embodiment of the present application provides a host computer 6, where the host computer 6 includes: a processor 60, a memory 61 and a computer program 62 stored in the memory 61 and executable on the processor 60. The steps of the various power module debugging method embodiments described above, such as steps 210 through 230 shown in fig. 2, are implemented by processor 60 when executing computer program 62. Alternatively, the processor 60, when executing the computer program 62, performs the functions of the modules/units of the system embodiments described above, such as the functions of the modules 510-530 shown in fig. 5.
By way of example, the computer program 62 may be partitioned into one or more modules/units, which are stored in the memory 61 and executed by the processor 60 to complete the present application. One or more of the modules/units may be a series of computer program instruction segments capable of performing a specific function, which instruction segments describe the execution of the computer program 62 in the upper computer 6.
The host computer 6 may be a mobile phone, an MCU, an ECU, an industrial personal computer, etc., and the server may be a physical server, a cloud server, etc., and is not limited thereto. The upper computer 6 may include, but is not limited to, a processor 60, a memory 61. It will be appreciated by those skilled in the art that fig. 6 is merely an example of the upper computer 6, and is not meant to be limiting, and that more or fewer components than shown may be included, or certain components may be combined, or different components may be included, for example, the upper computer may also include an input/output device, a network access device, a bus, etc.
The processor 60 may be a central processing unit (Central Processing Unit, CPU), other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may be an internal storage unit of the upper computer 6, for example, a hard disk or a memory of the upper computer 6. The memory 61 may be an external storage device of the host computer 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided in the host computer 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the upper computer 6. The memory 61 is used for storing a computer program and other programs and data required by the host computer. The memory 61 may also be used to temporarily store data that has been output or is to be output.
The embodiment of the application provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the steps in the power module debugging method embodiment when being executed by a processor.
The computer readable storage medium stores a computer program 62, the computer program 62 comprising program instructions which, when executed by the processor 60, implement all or part of the processes of the above described embodiments, or may be implemented by means of hardware associated with the instructions of the computer program 62, the computer program 62 being stored in a computer readable storage medium, the computer program 62, when executed by the processor 60, implementing the steps of the various method embodiments described above. The computer program 62 comprises computer program code, which may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth.
The computer readable storage medium may be an internal storage unit of the upper computer of any of the foregoing embodiments, for example, a hard disk or a memory of the upper computer. The computer readable storage medium may also be an external storage device of the upper computer, for example, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the upper computer. Further, the computer-readable storage medium may include both an internal storage unit of the upper computer and an external storage device. The computer readable storage medium is used for storing computer programs and other programs and data required by the upper computer. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/host computer and method may be implemented in other manners. For example, the apparatus/upper computer embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (10)

1. A power module debugging method is characterized in that a power module is connected with an upper computer; the method comprises the following steps:
acquiring a configuration file stored in an upper computer; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in unit of each upper computer is used for realizing one function of the upper computer;
changing the description information of the configuration file to add/delete the association relation between the plug-ins;
and according to the description information of the configuration file, the plug-ins in the upper computer are associated, so that each associated plug-in operates according to the corresponding debugging steps, and the debugging process of the upper computer is completed.
2. The power module debugging method of claim 1, wherein the description information of the display configuration file comprises an id of each plug-in and an id of an associated plug-in of each plug-in; the method further comprises the steps of:
when a configuration instruction is received, determining a first plug-in and a second plug-in according to plug-ins corresponding to the configuration instruction and the description information; the first plug-in is a plug-in to be replaced, and the second plug-in is used for replacing the first plug-in;
the modifying the description information of the configuration file to add/delete the association relationship between the plugins includes:
changing the id of the first plug-in into the id of the second plug-in the description information;
if the associated plug-in of any plug-in except the first plug-in the description information is the first plug-in, changing the id of the associated plug-in of the plug-in from the id of the first plug-in to the id of the second plug-in.
3. The power module commissioning method of claim 2, wherein prior to determining the first and second plug-ins, the method further comprises:
acquiring the type of a power module to be debugged;
judging whether the type of the power supply module is a known type;
and when the type of the power supply module is a known type, determining the configuration instruction according to the type of the power supply module.
4. The power module debugging method of claim 1, wherein the description information of the display configuration file comprises an id of each plug-in and an id of an associated plug-in of each plug-in;
the obtaining the configuration file stored in the upper computer includes:
responding to configuration operation of a host interface of the upper computer, and displaying description information of a configuration file on the host interface of the upper computer;
the modifying the description information of the configuration file to add/delete the association relationship between the plugins includes:
and responding to the change operation of the host interface of the upper computer, and changing the ids of the various plug-ins and the ids of the associated plug-ins of each plug-in.
5. The power module debugging method of claim 4, wherein a plurality of main labels are arranged on a main interface of the upper computer, and at least one sub-label is arranged under each main label; each sub-label corresponds to the description information of at least one plug-in;
and responding to the configuration operation of the host interface of the host computer, displaying the description information of the configuration file on the host interface of the host computer, wherein the method comprises the following steps:
and responding to the configuration operation of the host interface of the upper computer on any sub-label, and displaying the description information of at least one plug-in corresponding to the sub-label on the host interface of the upper computer.
6. The power module debugging method of claim 5, wherein after modifying the description information of the configuration file to add/delete the association relationship between the plug-ins, the method further comprises:
and adding/changing/deleting the sub-tags on the main interface of the upper computer according to the description information of the configuration file.
7. The power module debugging method according to any one of claims 1-6, wherein the plug-in of the host computer comprises a first subset and a second subset; the first subset comprises a CAN display interface plug-in, a protocol plug-in and a CAN drive plug-in; the second subset includes a CAN driver setup interface, CAN driver plug-in; the CAN drive cards in the first subset and the second subset are the same card.
8. The power module debugging device is characterized in that the power module is connected with an upper computer; the device comprises:
the acquisition module is used for acquiring the configuration file stored in the upper computer; the description information of the configuration file is used for representing the association relation among all plug-ins of the upper computer; the plug-in unit of each upper computer is used for realizing one function of the upper computer;
the change module is used for changing the description information of the configuration file so as to add/delete the association relation between the plug-ins;
and the debugging module is used for associating the plug-ins in the upper computer according to the description information of the configuration file, so that each associated plug-in is operated according to the corresponding debugging steps, and the debugging process of the upper computer is completed.
9. A host computer comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the power module debugging method of any of the preceding claims 1-7 when the computer program is executed by the processor.
10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the steps of the power module debugging method of any of the preceding claims 1 to 7.
CN202310947610.1A 2023-07-31 2023-07-31 Power module debugging method and device, upper computer and storage medium Pending CN116955195A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310947610.1A CN116955195A (en) 2023-07-31 2023-07-31 Power module debugging method and device, upper computer and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310947610.1A CN116955195A (en) 2023-07-31 2023-07-31 Power module debugging method and device, upper computer and storage medium

Publications (1)

Publication Number Publication Date
CN116955195A true CN116955195A (en) 2023-10-27

Family

ID=88460237

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310947610.1A Pending CN116955195A (en) 2023-07-31 2023-07-31 Power module debugging method and device, upper computer and storage medium

Country Status (1)

Country Link
CN (1) CN116955195A (en)

Similar Documents

Publication Publication Date Title
CN106055361B (en) Integrated firmware implementation method and system for multiple different types based on BMC (baseboard management controller)
CN105787364B (en) Automatic testing method, device and system for tasks
CN112506779A (en) Software interface testing method and device, electronic equipment and storage medium
US8196143B2 (en) Storing resource information
CN110096419A (en) Acquisition methods, interface log management server and the service server of interface log
CN112579446A (en) Interface testing method and device, electronic equipment and storage medium
CN104978276A (en) Method, device and system used for detecting software
CN112948233A (en) Interface testing method, device, terminal equipment and medium
CN112631937A (en) Automatic CAN operation testing method and device for T-Box
CN112445490A (en) File sequence processing method and device, terminal equipment and storage medium
CN116560586B (en) Determination method and device of attribute value, storage medium and electronic equipment
CN117474306A (en) Production flow control method and device, electronic equipment and readable storage medium
CN111693294A (en) Vehicle detection method and device, terminal equipment and storage medium
CN116955195A (en) Power module debugging method and device, upper computer and storage medium
CN114745452B (en) Equipment management method and device and electronic equipment
CN113495723B (en) Method, device and storage medium for calling functional component
CN111580812B (en) Data visualization component communication method, system, electronic device and storage medium
Lee et al. Collecting big data from automotive ECUs beyond the CAN bandwidth for fault visualization
CN106850546B (en) Map module software organization method of radar terminal
CN111638905A (en) Version number generation method and device, electronic equipment and readable storage medium
US11243761B2 (en) Link management device, link management method, and computer readable medium
CN115543227B (en) Cross-system data migration method, system, electronic device and storage medium
CN114816876B (en) Automatic test system for server Redfish interface specifications
CN112668194B (en) Automatic driving scene library information display method, device and equipment based on page
CN116954758A (en) Host computer dynamic library and configuration file management method, host computer and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination