US11475723B2 - Determining a fault in an electronic controller - Google Patents
Determining a fault in an electronic controller Download PDFInfo
- Publication number
- US11475723B2 US11475723B2 US16/227,077 US201816227077A US11475723B2 US 11475723 B2 US11475723 B2 US 11475723B2 US 201816227077 A US201816227077 A US 201816227077A US 11475723 B2 US11475723 B2 US 11475723B2
- Authority
- US
- United States
- Prior art keywords
- electronic controller
- service routine
- memory
- diagnostic service
- fault
- 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, expires
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0841—Registering performance data
- G07C5/085—Registering performance data using electronic data carriers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/005—Testing of electric installations on transport means
- G01R31/006—Testing of electric installations on transport means on road vehicles, e.g. automobiles or trucks
- G01R31/007—Testing of electric installations on transport means on road vehicles, e.g. automobiles or trucks using microprocessors or computers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
Definitions
- Embodiments relate to methods and systems for determining a fault in an electronic controller.
- Computers and electronic controllers control many systems including, for example, vehicle control systems. When a breakdown or fault occurs in these systems, the electronic controller is often replaced.
- a technician When a technician services a system and an electronic controller controlling that system, the technician may mistakenly replace the electronic controller even if a fault has not actually occurred in the electronic controller. Thus, a method is needed for determining if a fault has truly occurred in the electronic controller.
- Embodiments of this invention are therefore directed to determining a fault in an electronic controller.
- One embodiment provides a system for determining a fault in an electronic controller.
- the system includes a first electronic controller, a second electronic controller, and a remote electronic controller.
- the second electronic controller is configured to execute a diagnostic service routine configured to access a restricted section of a memory associated with the first electronic controller, receive a failure code from the restricted section of the memory associated with the first electronic controller, generate a logging file including the failure code, and send the logging file to the remote electronic controller.
- the remote electronic controller is configured to determine a fault in the first electronic controller based upon the logging file.
- Another embodiment provides a method for determining a fault in a first electronic controller.
- the method includes executing, with a second electronic controller, a diagnostic service routine configured to access a restricted section of a memory associated with on the first electronic controller; receiving, with the second electronic controller, a failure code from the restricted section of the memory associated with the first electronic controller in response to executing the diagnostic service routine; generating, with the second electronic controller, a logging file, the logging file including the failure code; sending, with the second electronic controller, the logging file to a remote electronic controller; and determining, with the remote electronic controller, a fault in the first electronic controller based on the logging file.
- FIG. 1 illustrates a system for determining a fault in an electronic controller according to one embodiment.
- FIG. 2 illustrates a first electronic controller according to one embodiment.
- FIG. 3 illustrates a second electronic controller according to one embodiment.
- FIG. 4 illustrates a method for determining a fault in an electronic controller according to one embodiment.
- a plurality of hardware and software based devices may be used to implement various embodiments.
- embodiments may include hardware, software, and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware.
- the electronic based aspects of the invention may be implemented in software (for example, stored on non-transitory computer-readable medium) executable by one or more processors.
- control units” and “controllers” described in the specification can include one or more electronic processors, one or more memory modules including non-transitory computer-readable medium, one or more input/output interfaces, one or more application specific integrated circuits (ASICs), and various connections (for example, a system bus) connecting the various components.
- ASICs application specific integrated circuits
- FIG. 1 illustrates a system 100 for determining a fault in a first electronic controller 105 according to one embodiment.
- the system includes the first electronic controller 105 , a second electronic controller 110 , and a remote electronic controller 115 .
- the first electronic controller 105 is an electronic controller for use in a vehicle.
- the first electronic controller 105 includes a plurality of electrical and electronic components that provide power, operation control, and protection to the components and modules within the first electronic controller 105 .
- the first electronic controller 105 includes a first electronic processor 205 (such as a programmable electronic microprocessor, microcontroller, or similar device), a first input-output interface 210 , and a first memory 215 (for example, a non-transitory, computer-readable medium).
- the first electronic processor 205 is communicatively connected to the first input-output interface 210 and the first memory 215 .
- the first memory 215 may further included a restricted section of memory 220 .
- the restricted section of memory 220 may be protected by a password, a private key, and the like.
- the restricted section of memory 220 may be configured, in some embodiments, to store data that should be accessible only to a manufacturer of the first electronic controller 105 and not to an operator of the first electronic controller 105 (e.g., a technician).
- the first electronic controller 105 is communicatively coupled to the second electronic controller 110 by a first coupling 120 .
- the first coupling 120 is a physical (wired) coupling between the first electronic controller 105 and the second electronic controller 110 .
- the first coupling 120 is a wireless communication coupling between the first electronic controller 105 and the second electronic controller 110 .
- the second electronic controller 110 is similar to the first electronic controller 1105 and includes similar components (such as a second electronic processor 305 , a second input-output interface 310 , and a second memory 315 ) that may function in a similar manner to the components of the first electronic controller 105 .
- the second memory 315 of the second electronic controller 110 does not require a restricted section of memory.
- the second electronic controller 110 is configured to run a diagnostic service routine on the first electronic controller 105 (as described below).
- the second electronic controller 110 is, in some embodiments, an electronic controller used by a technician to diagnose faults in an electronic controller (such as the first electronic controller 105 ) in a vehicle.
- the second electronic controller 110 is communicatively coupled to the remote electronic controller 115 by a second coupling 125 .
- the second coupling 125 is a physical (wired) coupling between the second electronic controller 110 and the remote electronic controller 115 .
- the second coupling 125 is a wireless communication coupling between the second electronic controller 110 and the remote electronic controller 115 .
- the remote electronic controller 115 is, in some embodiments, similar to the second electronic controller 110 .
- the remote electronic controller 115 may be an electronic controller in a computing system at an original equipment manufacturer (OEM) facility, a remote diagnostic facility, and the like.
- OEM original equipment manufacturer
- FIG. 4 illustrates an example method 400 for determining a fault in the first electronic controller 105 according to one embodiment.
- the method 400 includes executing, with the second electronic processor 110 , a diagnostic service routine on the first electronic controller (at block 405 ).
- the second electronic controller 110 through the first coupling 120 , accesses the first electronic controller 105 and runs the diagnostic service routine on the first electronic controller 105 .
- the diagnostic service routine may be a software routine that is executed by the second electronic controller 110 on the first electronic controller 105 .
- the diagnostic service routine may be created and provided by the OEM of the first electronic controller 105 to a user of the second electronic controller 110 , the user being, for example, a dealership employee where service on a vehicle containing the first electronic controller 105 is being performed.
- the diagnostic service routine is configured to access the first memory 215 and, among other things, retrieve failure codes associated with different faults in the first memory 215 (which are stored during the operation of the first electronic controller 105 ).
- the diagnostic service routine when provided by the OEM of the first electronic controller 105 , may be further configured to access the restricted section of memory 220 in the first memory 215 .
- the diagnostic service routine when provided by the OEM, may include the OEM private key or a password to access the restricted section of memory 220 .
- the second electronic controller 110 receives the failure codes saved in the first memory 215 and in the restricted section of memory 220 (at block 410 ).
- the failure codes are received via the first coupling 120 .
- the failure codes are indicative of different faults that have occurred in the first electronic controller 105 .
- a failure code may indicate an attempt to access empty memory, a failure of a software routine, and the like.
- the failure code may be a numerical code (e.g., “111”), a text code, and the like.
- the failure code also includes other failure information, such as date and time, vehicle conditions, and the like.
- the second electronic controller 110 generates a logging file (at block 415 ).
- the logging file includes any failure codes received at block 410 .
- the logging file may further include ticket information generated by the second electronic controller 110 .
- the ticket information may include a serial number of the first electronic controller 105 , a vehicle identification number, a software version number, a part number of the first electronic controller 105 , vehicle line information, dealership information, and the like.
- the ticket information may also include any other product data management (PDM) information concerning the first electronic controller 105 .
- PDM product data management
- the ticket information is obtained when the diagnostic service routine is run on the first electronic controller 105 .
- the second electronic controller 110 then sends the logging file to the remote electronic controller 115 via the second coupling 125 (at block 420 ).
- the remote electronic controller 115 determines, based upon the received logging file, a fault that has occurred in the first electronic controller 105 (at block 425 ). For example, the remote electronic controller 115 receives the logging file, extracts a failure code and associated failure information, extracts ticket information, and then determines a fault in the first electronic controller 105 based upon the extracted information. In some embodiments, only the failure code is used to determine the fault in the first electronic controller 105 .
- the remote electronic controller 115 may be further configured to alert a user of the remote electronic controller 115 or the second electronic controller 110 of the determined fault in the first electronic controller 105 .
- the remote electronic controller 115 may send a notification to the second electronic controller 110 to display on a display screen to a technician.
- the remote electronic controller 115 may further display the determined fault of the first electronic controller 105 to an operator of the remote electronic controller 115 via a display screen.
- the remote electronic controller 115 is owned by the OEM of the first electronic controller 105 , and the determined fault of the first electronic controller 105 is displayed to a software engineer or a quality control engineer to interpret the determined fault and determine a cause of the fault.
- the second electronic controller 110 is configured to initiate a virtual meeting with the operator of the remote electronic controller 115 and one or more other parties. For example, based upon the determined fault, the second electronic controller 115 initiates the virtual meeting using a virtual meeting service (for example, a video meeting service, a chat meeting service, a telephone meeting service, or the like) with the operator of the remote electronic controller 115 (such as an engineer from the OEM of the first electronic controller 105 ), an engineering team associated with a manufacturer of a vehicle containing the first electronic controller 105 , one or more technicians at a dealership where the second electronic controller 110 is located, and others involved in the manufacture of a vehicle containing the first electronic controller 105 , such as an engineering team of a third-party aftermarket part and the like.
- a virtual meeting service for example, a video meeting service, a chat meeting service, a telephone meeting service, or the like
- the operator of the remote electronic controller 115 such as an engineer from the OEM of the first electronic controller 105
Abstract
Systems and methods for determining a fault in an electronic controller. The system includes a first electronic controller, a second electronic controller, and a remote electronic controller. The second electronic controller executes a diagnostic service routine configured to access a restricted section of a memory associated with the first electronic controller, receives a failure code from the restricted section of the memory associated with the first electronic controller, generates a logging file including the failure code, and sends the logging file to the remote electronic controller. The remote electronic controller determines a fault in the first electronic controller based upon the logging file.
Description
This application claims priority to U.S. Provisional Patent Application No. 62/611,761, filed Dec. 29, 2017, the entire contents of which is incorporated by reference in its entirety.
Embodiments relate to methods and systems for determining a fault in an electronic controller.
Computers and electronic controllers control many systems including, for example, vehicle control systems. When a breakdown or fault occurs in these systems, the electronic controller is often replaced.
When a technician services a system and an electronic controller controlling that system, the technician may mistakenly replace the electronic controller even if a fault has not actually occurred in the electronic controller. Thus, a method is needed for determining if a fault has truly occurred in the electronic controller.
Embodiments of this invention are therefore directed to determining a fault in an electronic controller.
One embodiment provides a system for determining a fault in an electronic controller. The system includes a first electronic controller, a second electronic controller, and a remote electronic controller. The second electronic controller is configured to execute a diagnostic service routine configured to access a restricted section of a memory associated with the first electronic controller, receive a failure code from the restricted section of the memory associated with the first electronic controller, generate a logging file including the failure code, and send the logging file to the remote electronic controller. The remote electronic controller is configured to determine a fault in the first electronic controller based upon the logging file.
Another embodiment provides a method for determining a fault in a first electronic controller. The method includes executing, with a second electronic controller, a diagnostic service routine configured to access a restricted section of a memory associated with on the first electronic controller; receiving, with the second electronic controller, a failure code from the restricted section of the memory associated with the first electronic controller in response to executing the diagnostic service routine; generating, with the second electronic controller, a logging file, the logging file including the failure code; sending, with the second electronic controller, the logging file to a remote electronic controller; and determining, with the remote electronic controller, a fault in the first electronic controller based on the logging file.
Other aspects, features, and embodiments will become apparent by consideration of the detailed description and accompanying drawings.
Before any embodiments are explained in detail, it is to be understood that this disclosure is not intended to be limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. Embodiments are capable of other configurations and of being practiced or of being carried out in various ways.
A plurality of hardware and software based devices, as well as a plurality of different structural components may be used to implement various embodiments. In addition, embodiments may include hardware, software, and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware. However, one of ordinary skill in the art, and based on a reading of this detailed description, would recognize that, in at least one embodiment, the electronic based aspects of the invention may be implemented in software (for example, stored on non-transitory computer-readable medium) executable by one or more processors. For example, “control units” and “controllers” described in the specification can include one or more electronic processors, one or more memory modules including non-transitory computer-readable medium, one or more input/output interfaces, one or more application specific integrated circuits (ASICs), and various connections (for example, a system bus) connecting the various components.
An example of the first electronic controller 105 is illustrated in FIG. 2 . In some embodiments, the first electronic controller 105 is an electronic controller for use in a vehicle. The first electronic controller 105 includes a plurality of electrical and electronic components that provide power, operation control, and protection to the components and modules within the first electronic controller 105. In the example illustrated, the first electronic controller 105 includes a first electronic processor 205 (such as a programmable electronic microprocessor, microcontroller, or similar device), a first input-output interface 210, and a first memory 215 (for example, a non-transitory, computer-readable medium). The first electronic processor 205 is communicatively connected to the first input-output interface 210 and the first memory 215. The first memory 215 may further included a restricted section of memory 220. The restricted section of memory 220 may be protected by a password, a private key, and the like. The restricted section of memory 220 may be configured, in some embodiments, to store data that should be accessible only to a manufacturer of the first electronic controller 105 and not to an operator of the first electronic controller 105 (e.g., a technician).
The first electronic controller 105 is communicatively coupled to the second electronic controller 110 by a first coupling 120. In some embodiments, the first coupling 120 is a physical (wired) coupling between the first electronic controller 105 and the second electronic controller 110. In other embodiments, the first coupling 120 is a wireless communication coupling between the first electronic controller 105 and the second electronic controller 110.
An example of the second electronic controller 110 is illustrated in FIG. 3 . In some embodiments, the second electronic controller 110 is similar to the first electronic controller 1105 and includes similar components (such as a second electronic processor 305, a second input-output interface 310, and a second memory 315) that may function in a similar manner to the components of the first electronic controller 105. However, the second memory 315 of the second electronic controller 110 does not require a restricted section of memory. In some embodiments, the second electronic controller 110 is configured to run a diagnostic service routine on the first electronic controller 105 (as described below). The second electronic controller 110 is, in some embodiments, an electronic controller used by a technician to diagnose faults in an electronic controller (such as the first electronic controller 105) in a vehicle.
The second electronic controller 110 is communicatively coupled to the remote electronic controller 115 by a second coupling 125. In some embodiments, the second coupling 125 is a physical (wired) coupling between the second electronic controller 110 and the remote electronic controller 115. In other embodiments, the second coupling 125 is a wireless communication coupling between the second electronic controller 110 and the remote electronic controller 115.
The remote electronic controller 115 is, in some embodiments, similar to the second electronic controller 110. The remote electronic controller 115 may be an electronic controller in a computing system at an original equipment manufacturer (OEM) facility, a remote diagnostic facility, and the like.
The diagnostic service routine may be a software routine that is executed by the second electronic controller 110 on the first electronic controller 105. The diagnostic service routine may be created and provided by the OEM of the first electronic controller 105 to a user of the second electronic controller 110, the user being, for example, a dealership employee where service on a vehicle containing the first electronic controller 105 is being performed. The diagnostic service routine is configured to access the first memory 215 and, among other things, retrieve failure codes associated with different faults in the first memory 215 (which are stored during the operation of the first electronic controller 105). The diagnostic service routine, when provided by the OEM of the first electronic controller 105, may be further configured to access the restricted section of memory 220 in the first memory 215. For example, the diagnostic service routine, when provided by the OEM, may include the OEM private key or a password to access the restricted section of memory 220.
In response to the diagnostic service routine being executed by the second electronic controller 110 on the first electronic controller 105, the second electronic controller 110 receives the failure codes saved in the first memory 215 and in the restricted section of memory 220 (at block 410). The failure codes are received via the first coupling 120.
The failure codes are indicative of different faults that have occurred in the first electronic controller 105. For example, a failure code may indicate an attempt to access empty memory, a failure of a software routine, and the like. The failure code may be a numerical code (e.g., “111”), a text code, and the like. In some embodiments, the failure code also includes other failure information, such as date and time, vehicle conditions, and the like.
The second electronic controller 110 generates a logging file (at block 415). The logging file includes any failure codes received at block 410. The logging file may further include ticket information generated by the second electronic controller 110. The ticket information may include a serial number of the first electronic controller 105, a vehicle identification number, a software version number, a part number of the first electronic controller 105, vehicle line information, dealership information, and the like. The ticket information may also include any other product data management (PDM) information concerning the first electronic controller 105. In some embodiments, the ticket information is obtained when the diagnostic service routine is run on the first electronic controller 105.
The second electronic controller 110 then sends the logging file to the remote electronic controller 115 via the second coupling 125 (at block 420).
The remote electronic controller 115 determines, based upon the received logging file, a fault that has occurred in the first electronic controller 105 (at block 425). For example, the remote electronic controller 115 receives the logging file, extracts a failure code and associated failure information, extracts ticket information, and then determines a fault in the first electronic controller 105 based upon the extracted information. In some embodiments, only the failure code is used to determine the fault in the first electronic controller 105.
The remote electronic controller 115 may be further configured to alert a user of the remote electronic controller 115 or the second electronic controller 110 of the determined fault in the first electronic controller 105. For example, the remote electronic controller 115 may send a notification to the second electronic controller 110 to display on a display screen to a technician.
The remote electronic controller 115 may further display the determined fault of the first electronic controller 105 to an operator of the remote electronic controller 115 via a display screen. For example, in some embodiments, the remote electronic controller 115 is owned by the OEM of the first electronic controller 105, and the determined fault of the first electronic controller 105 is displayed to a software engineer or a quality control engineer to interpret the determined fault and determine a cause of the fault.
In some embodiments, the second electronic controller 110 is configured to initiate a virtual meeting with the operator of the remote electronic controller 115 and one or more other parties. For example, based upon the determined fault, the second electronic controller 115 initiates the virtual meeting using a virtual meeting service (for example, a video meeting service, a chat meeting service, a telephone meeting service, or the like) with the operator of the remote electronic controller 115 (such as an engineer from the OEM of the first electronic controller 105), an engineering team associated with a manufacturer of a vehicle containing the first electronic controller 105, one or more technicians at a dealership where the second electronic controller 110 is located, and others involved in the manufacture of a vehicle containing the first electronic controller 105, such as an engineering team of a third-party aftermarket part and the like.
Various features, advantages, and embodiments are set forth in the following claims.
Claims (15)
1. A method (400) for determining a fault in a first electronic controller (105), the method (400) comprising:
executing, with a second electronic controller (110), a diagnostic service routine configured to access a restricted section of a memory (220) associated with the first electronic controller (105),
receiving, with the second electronic controller (110), a failure code from the restricted section of the memory (220) associated with the first electronic controller (105) in response to executing the diagnostic service routine,
generating, with the second electronic controller (110), a logging file, the logging file including the failure code,
sending, with the second electronic controller (110), the logging file to a remote electronic controller (115), and
determining, with the remote electronic controller (115), a fault in the first electronic controller (105) based on the logging file.
2. The method (400) of claim 1 , wherein the diagnostic service routine is provided to a user of the second electronic controller (110) by an original equipment manufacturer of the first electronic controller (105).
3. The method (400) of claim 1 , wherein the diagnostic service routine accesses the restricted section of memory (220) by using a private key provided by an original equipment manufacturer of the first electronic controller (105).
4. The method (400) of claim 1 , wherein the diagnostic service routine accesses the restricted section of memory (220) by using a password provided by an original equipment manufacturer of the first electronic controller (105).
5. The method (400) of claim 1 , wherein the failure code indicates a fault that has occurred in the first electronic controller (105).
6. The method (400) of claim 5 , wherein the failure code indicates at least one selected from the group consisting of an attempt to access empty memory and a failure of a software routine.
7. The method (400) of claim 5 , wherein the failure code includes other failure information.
8. The method (400) of claim 1 , wherein the logging file includes ticket information generated by the second electronic controller (110) when the diagnostic service routine is executed on the first electronic controller (105).
9. The method (400) of claim 8 , wherein the ticket information includes at least one selected from the group consisting of a serial number of the first electronic controller (105), a vehicle identification number, a software version number, a part number of the first electronic controller (105), vehicle line information, dealership information, and product data management information about the first electronic controller (105).
10. The method (400) of claim 1 , wherein the remote electronic controller (115) is further configured to generate a notification for a user of at least one of the second electronic controller (110) and the remote electronic controller (115) based upon the determined fault.
11. A system (100) for determining a fault in a first electronic controller (105), the system (100) comprising:
the first electronic controller (105);
a second electronic controller (110) configured to
execute a diagnostic service routine configured to access a restricted section of a memory (220) associated with the first electronic controller (105), and
receive a failure code from the restricted section of the memory (220) associated with the first electronic controller (105) in response to executing the diagnostic service routine,
generate a logging file, the logging file including the failure code, and
send, with the second electronic controller (110), the logging file to a remote electronic controller (115); and
the remote electronic controller (115) configured to determine a fault in the first electronic controller (105) based on the logging file.
12. The system (100) of claim 11 , wherein the diagnostic service routine is provided to a user of the second electronic controller (110) by an original equipment manufacturer of the first electronic controller (105).
13. The system (100) of claim 11 , wherein the diagnostic service routine accesses the restricted section of memory (220) by using a private key provided by an original equipment manufacturer of the first electronic controller (105).
14. The system (100) of claim 11 , wherein the diagnostic service routine accesses the restricted section of memory (220) by using a password provided by an original equipment manufacturer of the first electronic controller (105).
15. The system (100) of claim 11 , wherein the logging file includes ticket information generated by the second electronic controller (110) when the diagnostic service routine is executed on the first electronic controller (105).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US16/227,077 US11475723B2 (en) | 2017-12-29 | 2018-12-20 | Determining a fault in an electronic controller |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201762611761P | 2017-12-29 | 2017-12-29 | |
| US16/227,077 US11475723B2 (en) | 2017-12-29 | 2018-12-20 | Determining a fault in an electronic controller |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20190206154A1 US20190206154A1 (en) | 2019-07-04 |
| US11475723B2 true US11475723B2 (en) | 2022-10-18 |
Family
ID=66816781
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US16/227,077 Active 2040-02-22 US11475723B2 (en) | 2017-12-29 | 2018-12-20 | Determining a fault in an electronic controller |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US11475723B2 (en) |
| DE (1) | DE102018222884A1 (en) |
Citations (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040025078A1 (en) * | 2002-06-07 | 2004-02-05 | Eisuke Nagano | Programmable controller with CPU units and special-function modules and method of doubling up |
| US20070213895A1 (en) | 2006-03-10 | 2007-09-13 | Denso Corporation | Vehicle diagnostic system capable of easily acquiring data IDs for vehicle diagnosis |
| US20080010506A1 (en) * | 2005-02-07 | 2008-01-10 | Fujitsu Limited | Multi-CPU computer and method of restarting system |
| US20080033609A1 (en) | 2006-08-04 | 2008-02-07 | Ramin Razavi | Automotive diagnostic and tuning system |
| US20090299566A1 (en) * | 2008-05-30 | 2009-12-03 | Hitachi, Ltd. | Vehicle-mounted information system, and data gathering method in diagnostic equipment |
| US20100023665A1 (en) * | 2006-11-09 | 2010-01-28 | Sony Computer Entertainment Inc. | Multiprocessor system, its control method, and information recording medium |
| US20100138693A1 (en) * | 2008-11-28 | 2010-06-03 | Hitachi Automotive Systems, Ltd. | Multi-Core Processing System for Vehicle Control Or An Internal Combustion Engine Controller |
| US20100229038A1 (en) * | 2009-03-04 | 2010-09-09 | Albrecht Mayer | System and Method for Testing a Module |
| US20100256860A1 (en) * | 2009-04-07 | 2010-10-07 | Denso Corporation | Vehicle test system including plurality of apparatuses mutually communicable via network |
| US8452465B1 (en) * | 2012-03-30 | 2013-05-28 | GM Global Technology Operations LLC | Systems and methods for ECU task reconfiguration |
| US20140005880A1 (en) * | 2012-06-28 | 2014-01-02 | Harman Becker Automotive Systems Gmbh | Telematics system |
| US20140195108A1 (en) * | 2013-01-07 | 2014-07-10 | Service Solutions U.S. Llc | Telecommunication Device Configured to Forward Vehicle Information from a Mobile Vehicle Monitoring Device |
| US9043078B2 (en) * | 2010-08-13 | 2015-05-26 | Deere & Company | Method and system for performing diagnostics or software maintenance for a vehicle |
| US9047718B2 (en) * | 2011-10-28 | 2015-06-02 | Honda Motor Co., Ltd. | Vehicle diagnostic method, and external diagnostic device |
| US20160300402A1 (en) * | 2015-03-27 | 2016-10-13 | Drew Technologies, Inc. | Vehicle diagnostic system and method |
| US20170262011A1 (en) * | 2016-03-14 | 2017-09-14 | Electronics And Telecommunications Research Institute | Processor system and fault detection method thereof |
| US9772839B2 (en) * | 2015-05-14 | 2017-09-26 | Airbiquity Inc. | Centralized management of mobile-assisted motor vehicle software upgrading and vehicle data analytics |
| US20170278320A1 (en) * | 2016-03-23 | 2017-09-28 | Kabushiki Kaisha Toshiba | In-vehicle gateway device, storage control method, and computer program product |
| US20170301154A1 (en) * | 2016-04-19 | 2017-10-19 | Rozint Enterprises, Inc. | Systems and methods for use of diagnostic scan tool in automotive collision repair |
| US9912531B2 (en) * | 2012-05-16 | 2018-03-06 | Bayerische Motoren Werke Aktiengesellschaft | Data logging or stimulation in automotive Ethernet networks using the vehicle infrastructure |
| US20180154906A1 (en) * | 2016-12-05 | 2018-06-07 | Ford Global Technologies, Llc | Autonomous vehicle processor self-diagnostic |
| US20180174373A1 (en) * | 2016-05-13 | 2018-06-21 | International Engine Intellectual Property Company , Llc | Synthetic fault codes |
| US20190180526A1 (en) * | 2017-12-11 | 2019-06-13 | GM Global Technology Operations LLC | Systems, methods and apparatuses for diagnostic fault detection by parameter data using a redundant processor architecture |
| US20190190899A1 (en) * | 2017-12-18 | 2019-06-20 | Thorsten Wilmer | Secure storage of monotonic odo value inside a secure hardware elements update counter |
-
2018
- 2018-12-20 US US16/227,077 patent/US11475723B2/en active Active
- 2018-12-21 DE DE102018222884.1A patent/DE102018222884A1/en active Pending
Patent Citations (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040025078A1 (en) * | 2002-06-07 | 2004-02-05 | Eisuke Nagano | Programmable controller with CPU units and special-function modules and method of doubling up |
| US20080010506A1 (en) * | 2005-02-07 | 2008-01-10 | Fujitsu Limited | Multi-CPU computer and method of restarting system |
| US20070213895A1 (en) | 2006-03-10 | 2007-09-13 | Denso Corporation | Vehicle diagnostic system capable of easily acquiring data IDs for vehicle diagnosis |
| US20080033609A1 (en) | 2006-08-04 | 2008-02-07 | Ramin Razavi | Automotive diagnostic and tuning system |
| US20100023665A1 (en) * | 2006-11-09 | 2010-01-28 | Sony Computer Entertainment Inc. | Multiprocessor system, its control method, and information recording medium |
| US20090299566A1 (en) * | 2008-05-30 | 2009-12-03 | Hitachi, Ltd. | Vehicle-mounted information system, and data gathering method in diagnostic equipment |
| US8095264B2 (en) | 2008-05-30 | 2012-01-10 | Hitachi, Ltd. | Vehicle-mounted information system, and data gathering method in diagnostic equipment |
| US20100138693A1 (en) * | 2008-11-28 | 2010-06-03 | Hitachi Automotive Systems, Ltd. | Multi-Core Processing System for Vehicle Control Or An Internal Combustion Engine Controller |
| US20100229038A1 (en) * | 2009-03-04 | 2010-09-09 | Albrecht Mayer | System and Method for Testing a Module |
| US20100256860A1 (en) * | 2009-04-07 | 2010-10-07 | Denso Corporation | Vehicle test system including plurality of apparatuses mutually communicable via network |
| US9043078B2 (en) * | 2010-08-13 | 2015-05-26 | Deere & Company | Method and system for performing diagnostics or software maintenance for a vehicle |
| US9047718B2 (en) * | 2011-10-28 | 2015-06-02 | Honda Motor Co., Ltd. | Vehicle diagnostic method, and external diagnostic device |
| US8452465B1 (en) * | 2012-03-30 | 2013-05-28 | GM Global Technology Operations LLC | Systems and methods for ECU task reconfiguration |
| US9912531B2 (en) * | 2012-05-16 | 2018-03-06 | Bayerische Motoren Werke Aktiengesellschaft | Data logging or stimulation in automotive Ethernet networks using the vehicle infrastructure |
| US20140005880A1 (en) * | 2012-06-28 | 2014-01-02 | Harman Becker Automotive Systems Gmbh | Telematics system |
| US9201844B2 (en) | 2012-06-28 | 2015-12-01 | Harman Becker Automotive Systems Gmbh | Telematics system |
| US20140195108A1 (en) * | 2013-01-07 | 2014-07-10 | Service Solutions U.S. Llc | Telecommunication Device Configured to Forward Vehicle Information from a Mobile Vehicle Monitoring Device |
| US20160300402A1 (en) * | 2015-03-27 | 2016-10-13 | Drew Technologies, Inc. | Vehicle diagnostic system and method |
| US9772839B2 (en) * | 2015-05-14 | 2017-09-26 | Airbiquity Inc. | Centralized management of mobile-assisted motor vehicle software upgrading and vehicle data analytics |
| US20170262011A1 (en) * | 2016-03-14 | 2017-09-14 | Electronics And Telecommunications Research Institute | Processor system and fault detection method thereof |
| US20170278320A1 (en) * | 2016-03-23 | 2017-09-28 | Kabushiki Kaisha Toshiba | In-vehicle gateway device, storage control method, and computer program product |
| US20170301154A1 (en) * | 2016-04-19 | 2017-10-19 | Rozint Enterprises, Inc. | Systems and methods for use of diagnostic scan tool in automotive collision repair |
| US20180174373A1 (en) * | 2016-05-13 | 2018-06-21 | International Engine Intellectual Property Company , Llc | Synthetic fault codes |
| US20180154906A1 (en) * | 2016-12-05 | 2018-06-07 | Ford Global Technologies, Llc | Autonomous vehicle processor self-diagnostic |
| US20190180526A1 (en) * | 2017-12-11 | 2019-06-13 | GM Global Technology Operations LLC | Systems, methods and apparatuses for diagnostic fault detection by parameter data using a redundant processor architecture |
| US20190190899A1 (en) * | 2017-12-18 | 2019-06-20 | Thorsten Wilmer | Secure storage of monotonic odo value inside a secure hardware elements update counter |
Non-Patent Citations (1)
| Title |
|---|
| www.obdii.com/background.html (Year: 1996). * |
Also Published As
| Publication number | Publication date |
|---|---|
| DE102018222884A1 (en) | 2019-07-04 |
| US20190206154A1 (en) | 2019-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108491301B (en) | Electronic device, abnormality early warning method based on redis and storage medium | |
| US20180227329A1 (en) | Method and apparatus for detecting security using an industry internet operating system | |
| CN108376290B (en) | Financial self-service equipment maintenance control method and device and server | |
| CN110572400A (en) | Vehicle OBD interface authentication method and device, electronic equipment and storage medium | |
| CN105429813A (en) | Monitoring method and client for docker | |
| CN107797887B (en) | Data backup and recovery method and device, storage medium and electronic equipment | |
| CN103501391B (en) | A kind of method and system managing user's brush machine behavior | |
| CN111211929A (en) | Fault positioning method, fault positioning device, control equipment and intelligent equipment | |
| US20160337210A1 (en) | Method and system for trouble ticketing | |
| US11475723B2 (en) | Determining a fault in an electronic controller | |
| CN110276193B (en) | Risk feature output method, application operation control method, system and device | |
| CN108768916B (en) | Method and device for acquiring security configuration information | |
| US20200117799A1 (en) | Graphical user interface tool for configuring a vehicle's intrusion detection system | |
| CN113792285B (en) | Nuclear power station service authority control method and device and terminal equipment | |
| US10459816B2 (en) | Communication setting notification apparatus | |
| CN114844772A (en) | Management method and system based on Zabbix monitoring platform | |
| US10671037B2 (en) | Machine maintenance using a machine controller and a service computer | |
| CN114067473B (en) | Access control authority management method, device and equipment in comprehensive scheduling system | |
| KR101584210B1 (en) | System and method for monitoring MCU | |
| CN113255855A (en) | Alarm system, method and terminal for preventing mistaken entering of electrified interval | |
| US9330030B2 (en) | Bridge decoder for a vehicle infotainment system | |
| CN109450718B (en) | Remote diagnosis method and device for wireless routing equipment | |
| CN111025918B (en) | Information screening method and device, electronic equipment and readable storage medium | |
| CN105718475A (en) | Data query method and device for business organization in ERP system | |
| US20160011932A1 (en) | Method for Monitoring Software in a Road Vehicle |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| AS | Assignment |
Owner name: ROBERT BOSCH GMBH, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHAH, ANKIT R.;JUDGE, ANTHONY;VELUSAMY, SIVARAJA;AND OTHERS;SIGNING DATES FROM 20190325 TO 20190808;REEL/FRAME:050200/0715 |
|
| AS | Assignment |
Owner name: ROBERT BOSCH GMBH, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VIJITHA, EVANGELIN C.;REEL/FRAME:051588/0720 Effective date: 20180223 |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
| STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
| STCV | Information on status: appeal procedure |
Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER |
|
| STCV | Information on status: appeal procedure |
Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED |
|
| STCV | Information on status: appeal procedure |
Free format text: APPEAL READY FOR REVIEW |
|
| STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
| STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
| STCF | Information on status: patent grant |
Free format text: PATENTED CASE |