CN110296010B - Master-slave ECU (electronic control unit) power-down control method and system - Google Patents

Master-slave ECU (electronic control unit) power-down control method and system Download PDF

Info

Publication number
CN110296010B
CN110296010B CN201910582432.0A CN201910582432A CN110296010B CN 110296010 B CN110296010 B CN 110296010B CN 201910582432 A CN201910582432 A CN 201910582432A CN 110296010 B CN110296010 B CN 110296010B
Authority
CN
China
Prior art keywords
ecu
power
master
delay request
slave
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.)
Active
Application number
CN201910582432.0A
Other languages
Chinese (zh)
Other versions
CN110296010A (en
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.)
Weichai Power Co Ltd
Original Assignee
Weichai Power 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 Weichai Power Co Ltd filed Critical Weichai Power Co Ltd
Priority to CN201910582432.0A priority Critical patent/CN110296010B/en
Publication of CN110296010A publication Critical patent/CN110296010A/en
Application granted granted Critical
Publication of CN110296010B publication Critical patent/CN110296010B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
    • F02D—CONTROLLING COMBUSTION ENGINES
    • F02D41/00—Electrical control of supply of combustible mixture or its constituents
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
    • F02D—CONTROLLING COMBUSTION ENGINES
    • F02D41/00—Electrical control of supply of combustible mixture or its constituents
    • F02D41/24—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means
    • F02D41/26—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means using computer, e.g. microprocessor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/10—Current supply arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40208—Bus networks characterized by the use of a particular bus standard
    • H04L2012/40215—Controller Area Network CAN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40267—Bus for use in transportation systems
    • H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle

Abstract

The invention discloses a master-slave ECU power-off control method and a master-slave ECU power-off control system, wherein the master ECU and the slave ECU in the power-off process state judge whether an engine completes power-off delay request operation, if so, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request state messages sent by the opposite sides, the master ECU and the slave ECU determine whether the power-off delay request is completed or not based on the power-off delay request state messages, and if so, the master ECU and the slave ECU simultaneously carry out power-off operation. According to the method, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message sent by the other side, and the master ECU and the slave ECU realize the transmission of control information through CAN communication, so that the master ECU and the slave ECU simultaneously carry out power-off operation, and the occurrence of overtime faults of the messages of the master ECU and the slave ECU caused by the fact that the master ECU and the slave ECU are not powered off at the same time is avoided.

Description

Master-slave ECU (electronic control unit) power-down control method and system
Technical Field
The invention relates to the technical field of ECU (electronic control unit), in particular to a master-slave ECU (electronic control unit) power-down control method and system.
Background
In order to meet the requirement of hardware drive, a large-bore Engine and an in-cylinder direct injection Engine in an automobile adopt a master-slave ECU (electronic Control Unit) Engine Control Unit to power off, namely, a Control strategy that double ECUs enter a working state simultaneously.
In the prior art, all power-off delay requests are mainly realized in a master ECU, if the slave ECU has no power-off delay request, the slave ECU performs power-off operation firstly, namely the slave ECU enters a stop working state, so that the master ECU cannot receive messages of the slave ECU, and the master ECU and the slave ECU cannot realize transmission of control information through CAN communication, thereby causing the master ECU to report the overtime fault of messages of the master ECU and the slave ECU.
Disclosure of Invention
In view of this, the invention provides a master-slave ECU power-down control method and system, which achieve the purpose of enabling the master ECU and the slave ECU to simultaneously perform power-down operation, and avoiding the occurrence of overtime faults of messages of the master ECU and the slave ECU caused by the fact that the master ECU and the slave ECU do not power down simultaneously.
In order to achieve the above object, the following solutions are proposed:
the invention discloses a master-slave ECU power-down control method, which is applied to an engine control device ECU, wherein the engine control device ECU comprises a master ECU and a slave ECU, and the method comprises the following steps:
the master ECU and the slave ECU in the power-off process state judge whether the engine completes the power-off delay request operation;
if yes, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request status messages sent by the opposite side;
the master ECU and the slave ECU determine whether the power-off delay request is completed or not based on the power-off delay request state message;
if yes, the master ECU and the slave ECU simultaneously carry out power-off operation.
Preferably, the master ECU and the slave ECU in the power-down process state determining whether the engine completes the power-down delay request operation includes:
the master ECU and the slave ECU mutually send power-off delay request states;
judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not;
if yes, the master ECU and the slave ECU in the power-off process state judge that the engine completes power-off delay request operation;
if not, the master ECU and the slave ECU in the power-off process state judge that the engine does not finish the power-off delay request operation.
Preferably, the determining, by the master ECU and the slave ECU, whether the power-off delay request is completed based on the power-off delay request status message includes:
when the master ECU and the slave ECU determine that the state indicated by the power-off delay request state message is a finished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state message sent by the other side, the power-off delay request is determined to be finished;
and when the master ECU and the slave ECU determine that the state indicated by any one of the power-off delay request state messages is an unfinished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side, determining that the power-off delay request is unfinished.
Preferably, the method further comprises the following steps:
entering a fault mode when communication between the master ECU and the slave ECU is abnormal, the master ECU and the slave ECU performing a power-down process state operation.
Preferably, after the master ECU and the slave ECU simultaneously perform the power-off operation, the method further includes:
and the master ECU and the slave ECU simultaneously disconnect a master relay to enter a stop working state.
The second aspect of the invention discloses a master-slave ECU power-down control system, which comprises: applied to an engine control unit ECU that includes a master ECU and a slave ECU, the system comprising:
a first determination unit for determining whether the engine completes a power-down delay request operation by the master ECU and the slave ECU in a power-down process state;
an obtaining unit, configured to obtain, by the master ECU and the slave ECU, power-off delay request status messages sent by the other party when communication between the master ECU and the slave ECU is normal;
a second determination unit, configured to determine whether the power-off delay request is completed based on the power-off delay request status message by the master ECU and the slave ECU;
and the operation unit is used for simultaneously carrying out power-off operation on the master ECU and the slave ECU.
Preferably, the first judging unit includes:
the sending module is used for sending a power-off delay request state between the master ECU and the slave ECU;
the first judgment module is used for judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not;
the second judgment module is used for judging that the engine finishes power-off delay request operation by the master ECU and the slave ECU which are in the power-off process state;
and the third judgment module is used for judging that the engine does not finish power-off delay request operation by the master ECU and the slave ECU in the power-off process state.
Preferably, the second determination unit includes:
the first determining module is used for determining that the power-off delay request is completed when the main ECU and the slave ECU determine that the state indicated by the power-off delay request state message is a completed state based on the fact that the main ECU and the slave ECU respectively receive the power-off delay request state message sent by the opposite side;
and the second determining module is used for determining that the power-off delay request is not finished when the main ECU and the slave ECU determine that the state indicated by any one power-off delay request state message is an unfinished state based on the fact that the main ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side.
Preferably, the method further comprises the following steps:
a failure unit;
the failure unit is used for entering a failure mode when the communication between the master ECU and the slave ECU is abnormal, and the master ECU and the slave ECU execute power-off process state operation.
Preferably, the method further comprises the following steps:
a stopping unit;
and the stopping unit is used for simultaneously disconnecting the main relay from the main ECU and the slave ECU to enter a work stopping state.
According to the technical scheme, the master ECU and the slave ECU which are in the power-off process state judge whether the engine completes the power-off delay request operation, if so, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request state messages sent by the opposite sides, the master ECU and the slave ECU determine whether the power-off delay request is completed based on the power-off delay request state messages, and if so, the master ECU and the slave ECU simultaneously perform the power-off operation. According to the method, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message sent by the other side, and the master ECU and the slave ECU realize the transmission of control information through CAN communication, so that the master ECU and the slave ECU simultaneously carry out power-off operation, and the occurrence of overtime faults of the messages of the master ECU and the slave ECU caused by the fact that the master ECU and the slave ECU are not powered off at the same time is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic flow chart of a master-slave ECU power-down control method disclosed by the embodiment of the invention;
FIG. 2 is a schematic flow chart illustrating a master ECU and a slave ECU determining whether an engine completes a power-down delay request operation in a power-down process state according to an embodiment of the present invention;
fig. 3 is a schematic flow chart illustrating a master ECU and a slave ECU determining whether a power-off delay request is completed based on a power-off delay request status message according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart of another master-slave ECU power-down control method disclosed in the embodiment of the present invention;
fig. 5 is a schematic structural diagram of a master-slave ECU power-down control system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
In the prior art, all power-off delay requests are mainly realized in a master ECU, if the slave ECU does not have the power-off delay request, the slave ECU performs power-off operation first, and the master ECU cannot receive messages of the slave ECU, so that the master ECU and the slave ECU cannot realize transmission of control information through CAN communication, and the master ECU reports overtime faults of messages of the master ECU and the slave ECU.
In order to solve the problem, according to the master-slave ECU power-off control method and system disclosed by the embodiment of the invention, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message sent by the other party, and the master ECU and the slave ECU realize the transmission of control information through the CAN communication, so that the master ECU and the slave ECU simultaneously perform power-off operation, and the generation of overtime faults of messages of the master ECU and the slave ECU, caused by the fact that the master ECU and the slave ECU do not power off at the same time, is avoided.
As shown in fig. 1, a schematic flow chart of a master-slave ECU power-down control method disclosed in the embodiment of the present invention specifically includes the following steps:
step S101: the master ECU and the slave ECU in the power-down process state determine whether the engine completes the power-down delay request operation, if so, execute step S102, and if not, execute step S103.
In the process of executing step S101, the engine enters a stop state, and the master ECU and the slave ECU each enter a power-down process state.
An Electronic Control Unit (ECU) is a microcomputer controller dedicated to an automobile in terms of usage, and is configured to collect signals of each sensor, perform an operation, convert the operation result into a Control signal, and Control the operation of a controlled object.
After the main ECU is powered off, certain self-learning operations need to be completed, such as an EGR valve power-off self-learning function, aftertreatment urea suck-back and the like are completed in the power-off process state stage.
In one application scenario of the invention, the EGR valve power-off self-learning function is used for diagnosis and test of relevant functions of the actuator after the electric engine is stopped at T15, and no fault is ensured.
T15 is a key switch signal indicating a command to enter an operating state of the master ECU or the slave ECU.
In another application scenario of the present invention, before the master ECU and the slave ECU in the power-down process state determine whether the engine completes the power-down delay request operation, it is determined whether the engine enters the power-down stop state, if so, the master ECU and the slave ECU in the power-down process state perform the step of determining whether the engine completes the power-down delay request operation, and if not, the master ECU and the slave ECU enter the waiting state.
In the above step S101, the process of determining whether the engine completes the power-off delay request operation by the master ECU and the slave ECU in the power-off process state is involved, and as shown in fig. 2, a schematic flow chart of determining whether the engine completes the power-off delay request operation by the master ECU and the slave ECU in the power-off process state specifically includes the following steps:
step S201: the master ECU and the slave ECU send a power-off delay request state to each other.
Note that the master ECU and the slave ECU each detect a power-off delay request state therebetween.
Step S202: and judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0, if so, executing step S203, and if not, executing step S204.
In the process of executing step S202, when the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0, it is described that the master ECU and the slave ECU complete all processes before power-off, such as a learning operation before power-off, data storage after power-off, and the like.
Step S203: the master ECU and the slave ECU in the power-down process state judge that the engine completes the power-down delay request operation.
Step S204: the master ECU and the slave ECU in the power-down process state determine that the engine does not complete the power-down delay request operation.
In the process of executing step S204, the master ECU and the slave ECU determine that the engine does not complete the power-off delay request operation, and continue to wait until the power-off delay request operation is completed.
Through mutually sending the power-off delay request state between the master ECU and the slave ECU in the steps S201 to S204, whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not is judged, if yes, the master ECU and the slave ECU in the power-off process state judge that the engine completes the power-off delay request operation, and if not, the master ECU and the slave ECU in the power-off process state judge that the engine does not complete the power-off delay request operation.
In the embodiment of the invention, the main ECU and the slave ECU mutually send the power-off delay request state, and the power-off delay request state is judged, so that whether the engine completes the power-off delay request operation or not is determined.
Step S102: and under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request state messages sent by the opposite sides.
In the process of executing step S102, when the communication between the master ECU and the slave ECU is normal, the master ECU sends the information to the slave ECU through the master-slave interaction message according to the power-off delay request state of the master ECU, and the slave ECU sends the information to the master ECU through the master-slave interaction message according to the power-off delay request state of the slave ECU.
Optionally, when the communication between the master ECU and the slave ECU is abnormal, a failure mode is entered, and the master ECU and the slave ECU perform a power-down process operation.
When communication is abnormal, a message timeout fault between the master ECU and the slave ECU may be caused.
Step S103: waiting for the power down delay request operational state to complete.
Step S104: and the master ECU and the slave ECU determine whether the power-off delay request is completed or not based on the power-off delay request state message, if so, execute step S105, and if not, execute step S106.
In the process of executing step S104, the master ECU and the slave ECU determine whether the power-off delay request is completed based on the power-off delay request status message as a condition for whether the master ECU and the slave ECU are allowed to perform the power-off operation.
It should be noted that, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message, and then allow the master ECU and the slave ECU to perform the power-off operation. And the master ECU and the slave ECU determine that the power-off delay request is not completed based on the power-off delay request state message, and the master ECU and the slave ECU do not allow power-off operation.
In the above step S104, a process of determining whether the power-off delay request is completed or not by the master ECU and the slave ECU based on the power-off delay request status message is involved, as shown in fig. 3, a flow chart of determining whether the power-off delay request is completed or not by the master ECU and the slave ECU based on the power-off delay request status message is shown, and the method specifically includes the following steps:
step S301: and when the master ECU and the slave ECU determine that the state indicated by the power-off delay request state message is a finished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state message sent by the other side, determining that the power-off delay request is finished.
In the process of executing step S301, when it is determined that the state indicated by the power-off delay request state message is the completed state, and when it is determined that the power-off delay request is completed, the master ECU and the slave ECU allow the power-off operation.
Step S302: and when the master ECU and the slave ECU determine that the state indicated by any one of the power-off delay request state messages is an unfinished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side, determining that the power-off delay request is unfinished.
In the process of executing step S302, when it is determined that the status indicated by any one of the power-off delay request status messages is an incomplete status, and it is determined that the power-off delay request is incomplete, the master ECU and the slave ECU do not allow the power-off operation.
And through the steps S301-S302, when the master ECU and the slave ECU determine that the state indicated by the power-off delay request state message is the completed state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state message sent by the opposite side, determining that the power-off delay request is completed. And when the master ECU and the slave ECU determine that the state indicated by any one of the power-off delay request state messages is an unfinished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side, determining that the power-off delay request is unfinished.
In the embodiment of the invention, when the master ECU and the slave ECU respectively receive the power-off delay request state message sent by the other side, the master ECU and the slave ECU judge whether the state indicated by the power-off delay request state message is the finished state, so as to determine whether the power-off delay request is finished.
Step S105: the master ECU and the slave ECU simultaneously perform power-off operation.
The main ECU and the slave ECU simultaneously perform the power-down operation means that the main ECU and the slave ECU receive a power-down command T15 to complete the power-down operation, and the main ECU and the slave ECU simultaneously enter the stop state.
The master ECU is used as a core controller to process more data, the slave ECU is used as an auxiliary controller to process less data, so that the time spent by the master ECU on processing the data is more than the time spent by the slave ECU on processing the data, the master ECU sends a power-off delay request to the slave ECU, the slave ECU delays power-off and waits for the master ECU to perform power-off operation, and when the master ECU performs the power-off operation, the master ECU and the slave ECU perform the power-off operation simultaneously.
When the master ECU and the slave ECU have no power-off delay request state, that is, when the power-off delay request states of the master ECU and the slave ECU are 0, the master ECU and the slave ECU can perform simultaneous power-off operation.
Optionally, after the master ECU and the slave ECU perform power-down operation simultaneously, the master ECU and the slave ECU disconnect the master relay simultaneously to enter a stop operation state.
It should be noted that the master ECU and the slave ECU transmit power-off delay request state information to each other, and when neither the master ECU nor the slave ECU has a power-off delay request state, the master ECU and the slave ECU are allowed to be turned off, and the master ECU and the slave ECU stop operating completely.
Step S106: the master ECU and the slave ECU do not perform a power-down operation.
When one of the master ECU and the slave ECU has the power-off delay request state, that is, when the power-off delay request state of one of the master ECU and the slave ECU is not 0, the master ECU and the slave ECU do not perform the power-off operation.
The embodiment of the invention discloses a master-slave ECU power-off control method, wherein a master ECU and a slave ECU in a power-off process state judge whether an engine completes power-off delay request operation, if so, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request state messages sent by opposite sides, the master ECU and the slave ECU determine whether the power-off delay request is completed or not based on the power-off delay request state messages, and if so, the master ECU and the slave ECU simultaneously carry out power-off operation. According to the method, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message sent by the other side, and the master ECU and the slave ECU realize the transmission of control information through CAN communication, so that the master ECU and the slave ECU simultaneously carry out power-off operation, and the occurrence of overtime faults of the messages of the master ECU and the slave ECU caused by the fact that the master ECU and the slave ECU are not powered off at the same time is avoided.
Based on the flow diagram of the master-slave ECU power-down control method shown in fig. 1, the embodiment of the invention discloses another flow diagram of the master-slave ECU power-down control method, as shown in fig. 4, specifically including the following steps:
step S401: the master ECU and the slave ECU send a power-off delay request state to each other.
Step S402: and judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0, if so, executing step S403, and if not, executing step S404.
Step S403: the master ECU and the slave ECU in the power-down process state judge that the engine completes the power-down delay request operation.
Step S404: the master ECU and the slave ECU in the power-down process state determine that the engine does not complete the power-down delay request operation.
The execution process of the above steps S401 to S404 is the same as the execution process of the steps S201 to S204 shown in fig. 2, and the execution principle is also the same, which can be referred to and is not described again here.
Step S405: and under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request state messages sent by the opposite sides.
The execution process of step S405 is the same as the execution process of step S102 shown in fig. 1, and the execution principle is also the same, which can be referred to herein, and is not described again.
Step S406: and when the master ECU and the slave ECU respectively receive the power-off delay request state message sent by the other side, judging whether the state indicated by the power-off delay request state message is a finished state, if so, executing a step S407, and otherwise, executing a step S408.
Step S407: it is determined that the power-off delay request is completed, step S409 is performed.
Step S408: it is determined that the power-off delay request is not completed, step S410 is performed.
Optionally, in the step S406 to the step S408, when the master ECU and the slave ECU respectively receive the power-off delay request status message sent by the other side, a manner of determining whether the status indicated by the power-off delay request status message is a completed status may also be implemented by using the execution manners of the step S301 to the step S302 disclosed in fig. 3.
Step S409: the master ECU and the slave ECU simultaneously perform power-off operation.
The execution process of step S409 is the same as the execution process of step S105 shown in fig. 1, and the execution principle is also the same, which can be referred to and is not described herein again.
Step S410: the master ECU and the slave ECU do not perform a power-down operation.
The execution process of step S410 is the same as the execution process of step S106 shown in fig. 1, and the execution principle is also the same, which can be referred to herein, and is not described again.
In the embodiment of the invention, the master ECU and the slave ECU mutually send power-off delay request states to judge whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not, if so, the master ECU and the slave ECU in the power-off process state judge that the engine completes the power-off delay request operation, if not, the master ECU and the slave ECU in the power-off process state judge that the engine does not complete the power-off delay request operation, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively obtain the power-off delay request state messages sent by the opposite sides, when the master ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite sides, the master ECU and the slave ECU determine that the power-off delay request state messages indicate the completed state, the power-off delay request is completed, when the master ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite sides, and when the state indicated by any power-off delay request state message is determined to be an incomplete state, determining that the power-off delay request is incomplete, and simultaneously carrying out power-off operation on the master ECU and the slave ECU. According to the method, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message sent by the other side, and the master ECU and the slave ECU realize the transmission of control information through CAN communication, so that the master ECU and the slave ECU simultaneously carry out power-off operation, and the occurrence of overtime faults of the messages of the master ECU and the slave ECU caused by the fact that the master ECU and the slave ECU are not powered off at the same time is avoided.
Based on the master-slave ECU power-down control method disclosed in the embodiment of the present invention, the embodiment of the present invention also discloses a master-slave ECU power-down control system correspondingly, as shown in fig. 5, the master-slave ECU power-down control system 500 mainly includes:
a first determination unit 501 for the master ECU and the slave ECU in the power-down process state to determine whether the engine completes the power-down delay request operation.
An obtaining unit 502, configured to, when communication between the master ECU and the slave ECU is normal, respectively obtain power-off delay request status messages sent by the master ECU and the slave ECU.
A second determination unit 503, configured to determine whether the power-off delay request is completed based on the power-off delay request status message by the master ECU and the slave ECU.
An operation unit 504 for performing a power-down operation simultaneously with the master ECU and the slave ECU.
Further, the first determining unit 501 includes:
and the sending module is used for sending a power-off delay request state between the master ECU and the slave ECU.
The first judgment module is used for judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not.
And the second judgment module is used for judging that the engine finishes the power-off delay request operation by the master ECU and the slave ECU which are in the power-off process state.
And the third judgment module is used for judging that the engine does not finish power-off delay request operation by the master ECU and the slave ECU in the power-off process state.
Further, the second determining unit 503 includes:
the first determining module is used for determining that the power-off delay request is completed when the main ECU and the slave ECU determine that the state indicated by the power-off delay request state message is the completed state based on the fact that the main ECU and the slave ECU respectively receive the power-off delay request state message sent by the opposite side.
And the second determining module is used for determining that the power-off delay request is not finished when the main ECU and the slave ECU determine that the state indicated by any one power-off delay request state message is an unfinished state based on the fact that the main ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side.
Optionally, the method further includes:
a failure unit;
the failure unit is used for entering a failure mode when the communication between the master ECU and the slave ECU is abnormal, and the master ECU and the slave ECU execute power-off process state operation.
Optionally, the method further includes:
a stopping unit;
and the stopping unit is used for simultaneously disconnecting the main relay from the main ECU and the slave ECU to enter a work stopping state.
The specific principle and the implementation process of each unit and module in the master-slave ECU power-down control system disclosed in the embodiment of the present invention are the same as the master-slave ECU power-down control method disclosed in the embodiment of the present invention, and reference may be made to corresponding parts in the master-slave ECU power-down control method disclosed in the embodiment of the present invention, which are not described herein again.
The invention discloses a master-slave ECU power-off control system, wherein a master ECU and a slave ECU in a power-off process state judge whether an engine completes power-off delay request operation, if so, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request state messages sent by the opposite sides, the master ECU and the slave ECU determine whether the power-off delay request is completed based on the power-off delay request state messages, and if so, the master ECU and the slave ECU simultaneously carry out power-off operation. Through the system, the master ECU and the slave ECU determine that the power-off delay request is completed based on the power-off delay request state message sent by the other side, and the master ECU and the slave ECU realize the transmission of control information through CAN communication, so that the master ECU and the slave ECU simultaneously carry out power-off operation, and the generation of overtime faults of messages of the master ECU and the slave ECU caused by the fact that the master ECU and the slave ECU are not powered off at the same time is avoided.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. 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 invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A master-slave ECU power-down control method is applied to an engine control device ECU, wherein the engine control device ECU comprises a master ECU and a slave ECU, and the method comprises the following steps:
the master ECU and the slave ECU in the power-off process state judge whether the engine completes the power-off delay request operation;
if yes, under the condition that the communication between the master ECU and the slave ECU is normal, the master ECU and the slave ECU respectively acquire power-off delay request status messages sent by the opposite side;
the master ECU and the slave ECU determine whether the power-off delay request is completed or not based on the power-off delay request state message;
if yes, the master ECU and the slave ECU simultaneously carry out power-off operation.
2. The method of claim 1, wherein the master ECU and the slave ECU in the power-down process state determining whether the engine completes the power-down delay request operation includes:
the master ECU and the slave ECU mutually send power-off delay request states;
judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not;
if yes, the master ECU and the slave ECU in the power-off process state judge that the engine completes power-off delay request operation;
if not, the master ECU and the slave ECU in the power-off process state judge that the engine does not finish the power-off delay request operation.
3. The method of claim 1, wherein determining whether the power down delay request is complete based on the power down delay request status message by the master ECU and the slave ECU comprises:
when the master ECU and the slave ECU determine that the state indicated by the power-off delay request state message is a finished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state message sent by the other side, the power-off delay request is determined to be finished;
and when the master ECU and the slave ECU determine that the state indicated by any one of the power-off delay request state messages is an unfinished state based on the fact that the master ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side, determining that the power-off delay request is unfinished.
4. The method of claim 3, further comprising:
entering a fault mode when communication between the master ECU and the slave ECU is abnormal, the master ECU and the slave ECU performing a power-down process state operation.
5. The method of claim 1, further comprising, after the master ECU and the slave ECU are simultaneously powered down:
and the master ECU and the slave ECU simultaneously disconnect a master relay to enter a stop working state.
6. A master-slave ECU power down control system, comprising: applied to an engine control unit ECU that includes a master ECU and a slave ECU, the system comprising:
a first determination unit for determining whether the engine completes a power-down delay request operation by the master ECU and the slave ECU in a power-down process state;
an obtaining unit, configured to, when a determination result of the first determining unit is yes, obtain, by the master ECU and the slave ECU, a power-off delay request status message sent by an opposite party in a case where communication between the master ECU and the slave ECU is normal;
a second determination unit, configured to determine whether the power-off delay request is completed based on the power-off delay request status message by the master ECU and the slave ECU;
an operation unit configured to perform a power-down operation simultaneously with the master ECU and the slave ECU when a determination result of the second determination unit is yes.
7. The system according to claim 6, wherein the first determining unit comprises:
the sending module is used for sending a power-off delay request state between the master ECU and the slave ECU;
the first judgment module is used for judging whether the power-off delay request state of the master ECU and the power-off delay request state of the slave ECU are 0 or not;
the second judgment module is used for judging that the engine finishes power-off delay request operation by the master ECU and the slave ECU which are in the power-off process state;
and the third judgment module is used for judging that the engine does not finish power-off delay request operation by the master ECU and the slave ECU in the power-off process state.
8. The system of claim 6, wherein the second determining unit comprises:
the first determining module is used for determining that the power-off delay request is completed when the main ECU and the slave ECU determine that the state indicated by the power-off delay request state message is a completed state based on the fact that the main ECU and the slave ECU respectively receive the power-off delay request state message sent by the opposite side;
and the second determining module is used for determining that the power-off delay request is not finished when the main ECU and the slave ECU determine that the state indicated by any one power-off delay request state message is an unfinished state based on the fact that the main ECU and the slave ECU respectively receive the power-off delay request state messages sent by the opposite side.
9. The system of claim 8, further comprising:
a failure unit;
the failure unit is used for entering a failure mode when the communication between the master ECU and the slave ECU is abnormal, and the master ECU and the slave ECU execute power-off process state operation.
10. The system of claim 6, further comprising:
a stopping unit;
and the stopping unit is used for simultaneously disconnecting the main relay from the main ECU and the slave ECU to enter a work stopping state.
CN201910582432.0A 2019-06-29 2019-06-29 Master-slave ECU (electronic control unit) power-down control method and system Active CN110296010B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910582432.0A CN110296010B (en) 2019-06-29 2019-06-29 Master-slave ECU (electronic control unit) power-down control method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910582432.0A CN110296010B (en) 2019-06-29 2019-06-29 Master-slave ECU (electronic control unit) power-down control method and system

Publications (2)

Publication Number Publication Date
CN110296010A CN110296010A (en) 2019-10-01
CN110296010B true CN110296010B (en) 2022-03-01

Family

ID=68029541

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910582432.0A Active CN110296010B (en) 2019-06-29 2019-06-29 Master-slave ECU (electronic control unit) power-down control method and system

Country Status (1)

Country Link
CN (1) CN110296010B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113348421B (en) * 2021-04-28 2023-02-28 华为技术有限公司 Camera equipment, data acquisition system and method
CN113390642B (en) * 2021-06-15 2023-04-18 潍柴动力股份有限公司 Automatic control method and system for engine switch and engine test run equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2009267A2 (en) * 2007-06-27 2008-12-31 Hitachi Ltd. Measurement methods and measuring equipment for flow of exhaust gas re-circulation
CN102477915A (en) * 2010-11-22 2012-05-30 本田技研工业株式会社 Control apparatus for internal combustion engine
CN105569855A (en) * 2014-10-30 2016-05-11 Ge延巴赫两合无限公司 Method for operating a combustion engine
CN107429626A (en) * 2014-11-06 2017-12-01 沃尔布罗有限责任公司 Engine control strategy

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102009000265A1 (en) * 2009-01-16 2010-07-22 Robert Bosch Gmbh Method for performing a number of injections

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2009267A2 (en) * 2007-06-27 2008-12-31 Hitachi Ltd. Measurement methods and measuring equipment for flow of exhaust gas re-circulation
CN102477915A (en) * 2010-11-22 2012-05-30 本田技研工业株式会社 Control apparatus for internal combustion engine
CN105569855A (en) * 2014-10-30 2016-05-11 Ge延巴赫两合无限公司 Method for operating a combustion engine
CN107429626A (en) * 2014-11-06 2017-12-01 沃尔布罗有限责任公司 Engine control strategy

Also Published As

Publication number Publication date
CN110296010A (en) 2019-10-01

Similar Documents

Publication Publication Date Title
JP5709055B2 (en) Electronic control device for vehicle
CN110296010B (en) Master-slave ECU (electronic control unit) power-down control method and system
CN107272665A (en) A kind of vehicle network management method and system
KR101439050B1 (en) Method for dark current inspection of vehicle
CN102546295B (en) CAN (Controller Area Network) detecting method of hybrid vehicle based on rigid line control
CN108958224B (en) Vehicle diagnosis method, diagnosis terminal and diagnosis box
CN102759922B (en) Electric motorcar communication safety detection method and system thereof
CN105404568A (en) CAN bus test system and test method
CN107911260A (en) A kind of vehicle test system based on OSEC network managements
EP3780329B1 (en) Power supply device
CN103139033B (en) Single main communications control bus main equipment redundancy switching method
WO2007062572A1 (en) Information terminal for long-range diagnosing vehicle breakdown and diagnosing method
CN113406946B (en) Automobile diagnosis method and device and automobile diagnosis equipment
CN102541047A (en) Software adaptive allocation method of combination meter
CN105599706B (en) A kind of standby management method and system of intelligent vehicle-carried information entertainment
CN106603314A (en) Test system and test method for OSEK-based direct network management
CN104076806A (en) Method of carrying out automatic test on automobile electric control device and equipment
WO2022267828A1 (en) Connector of storage battery and detection system and method for storage battery
CN111142504B (en) Bus detection device and method
CN109664902B (en) Rail vehicle and human-computer interaction system thereof
CN111443688B (en) Automobile diagnosis service network layer test system and method based on CAN bus
JP2012147549A (en) Charge reservation system for vehicle
CN111505977B (en) Function auxiliary debugging method, device, system and medium
CN111740972B (en) Method, device, equipment and storage medium for updating communication protocol stack information
CN101441476B (en) Software implementing method of data link layer based on KWP2000

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
GR01 Patent grant
GR01 Patent grant