SYSTEMS FOR DETECTING ACTUATOR MISFORTUNATIONS IN VEHICLES
The system uses unique identifiers for actuators to detect and correct misconfigurations, ensuring correct installation and preventing safety hazards by comparing received identifiers with stored vehicle-specific data, thus enhancing vehicle safety.
Patent Information
- Application Number
- DE102023128136
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2023-10-14
- Publication Date
- 2024-11-21
AI Technical Summary
Vehicles often face safety hazards due to actuator misconfigurations, where similar hardware components are installed at incorrect locations, leading to potential failures in systems like brake-by-wire braking systems, vehicle doors, and steering systems.
A system with unique identifiers for each actuator, communicated via serial data connections, allows a control module to compare received identifiers with stored vehicle-specific identifiers, detecting and correcting misconfigurations by sending error signals.
Ensures accurate verification and detection of actuator positions, preventing safety-critical events by correcting misconfigurations during manufacturing, ensuring correct actuator installation and reducing the need for mechanical keying or hardware variants.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
INTRODUCTION
[0001] The information provided in this section is intended to provide a general context for the disclosure. The work of the presently named inventors, to the extent described in this section, as well as those aspects of the description that do not otherwise qualify as prior art at the time of filing, are neither expressly nor implicitly admitted as prior art against the present disclosure.
[0002] The present disclosure relates to systems for detecting actuator misconfigurations in vehicles.
[0003] Vehicles often include actuators to enable physical movement of vehicle components. Such actuators may be controlled by signals from a control module, such as a centralized supervisory control module. For example, a vehicle braking system may include a control module for controlling brake actuators located at each of the vehicle's four corners. This vehicle braking system is sometimes referred to as a brake-by-wire braking system. In other examples, actuators may be located and / or deployed near vehicle doors, steering systems, propulsion systems, etc. SUMMARY
[0004] A system for detecting an actuator misconfiguration in a vehicle is disclosed. The system includes a plurality of actuators and a control module. Each actuator of the plurality of actuators is assigned a unique identifier. The control module includes a plurality of interface ports that communicate with the plurality of actuators via serial data connections. Each interface port of the control module is in communication with two of the plurality of actuators. Each actuator of the plurality of actuators is in communication with two interface ports.The control module is configured to receive a message from an actuator of the plurality of actuators installed at a location of the vehicle, the message including the unique identifier assigned to the actuator, compare the received unique identifier assigned to the actuator with a stored identifier specific to the location of the vehicle, and in response to the received unique identifier being different from the stored identifier, send an error signal indicating an error associated with the actuator.
[0005] In further features, the control module is configured to identify a reason for the error based on the received unique identifier and the stored identifier and to send the error signal with the reason for the error.
[0006] In further features, the control module's multiple interface ports include four interface ports and the multiple actuators include four actuators.
[0007] In further features, each actuator of the plurality of actuators includes a first interface port in communication with one of the four interface ports and a second interface port in communication with another of the four interface ports.
[0008] In further features, the four actuators include a first actuator installed at a front left location of the vehicle, a second actuator installed at a front right location of the vehicle, a third actuator installed at a rear left location of the vehicle, and a fourth actuator installed at a rear right location of the vehicle. The four interface ports include a first interface port in communication with the first actuator and the fourth actuator, a second interface port in communication with the second actuator and the third actuator, a third interface port in communication with the third actuator and the fourth actuator, and a fourth interface port in communication with the first actuator and the second actuator.
[0009] In further features, the four actuators are brake actuators.
[0010] In further features, each brake actuator of the brake actuators includes a memory module configured to store information about the brake actuator and an expected location of the brake actuator in the vehicle before the brake actuator is installed in the vehicle.
[0011] In addition, the serial data connections include Ethernet connections.
[0012] In further features, the unique identifier assigned to each actuator is a predefined MAC address stored in a memory module associated with the actuator.
[0013] A system for detecting an actuator misconfiguration in a vehicle is disclosed. The system includes a plurality of actuators and a control module. Each actuator of the plurality of actuators is assigned a unique identifier. The control module includes a first aggregator module and a second aggregator module. The first aggregator module includes a plurality of interface ports. Each interface port of the first aggregator module is in communication with two different actuators of the plurality of actuators via a serial data connection. The second aggregator module includes a plurality of interface ports. Each interface port of the second aggregator module is in communication with two different actuators of the plurality of actuators via a serial data connection.The control module is configured to receive, via the first aggregator module or the second aggregator module, a message from an actuator of the plurality of actuators installed at a location of the vehicle, the message including the unique identifier assigned to the actuator, compare the received unique identifier assigned to the actuator with a stored identifier specific to the location of the vehicle, and, in response to the received unique identifier being different from the stored identifier, send an error signal indicating an error associated with the actuator.
[0014] In further features, the control module is configured to identify a reason for the error based on the received unique identifier and the stored identifier and to send the error signal with the reason for the error.
[0015] In further features, the plurality of interface ports of the first aggregator module includes two interface ports, the plurality of interface ports of the second aggregator module includes two interface ports, and the plurality of actuators includes four actuators.
[0016] In further features, each actuator of the plurality of actuators includes a first interface port in communication with one of the two interface ports of the first aggregator module and a second interface port in communication with one of the two interface ports of the second aggregator module.
[0017] In further features, the four actuators include a first actuator located at a front left position of the vehicle, a second actuator located at a front right position of the vehicle, a third actuator located at a rear left position of the vehicle, and a fourth actuator located at a rear right position of the vehicle. The two interface ports of the first aggregator module include a first interface port in communication with the first actuator and the fourth actuator, and a second interface port in communication with the second actuator and the third actuator. The two interface ports of the second aggregator module include a first interface port in communication with the third actuator and the fourth actuator, and a second interface port in communication with the first actuator and the second actuator.
[0018] In further features, the four actuators are brake actuators.
[0019] In further features, each brake actuator of the brake actuators includes a memory module configured to store information about the brake actuator and an expected location of the brake actuator in the vehicle before the brake actuator is installed in the vehicle.
[0020] In other features, the serial data connection includes an Ethernet connection.
[0021] In further features, the unique identifier assigned to each actuator is a predefined MAC address stored in a memory module associated with the actuator.
[0022] Further areas of applicability of the present disclosure will become apparent from the detailed description, claims, and drawings. The detailed description and specific examples are for purposes of illustration only and are not intended to limit the scope of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] The present disclosure will be more fully understood from the detailed description and the accompanying drawings, in which: Fig. 1 is a block diagram of an exemplary actuator misconfiguration detection system including a control module and four actuators, according to the present disclosure; Fig. 2 is a block diagram of another exemplary actuator misconfiguration detection system including two aggregator modules, according to the present disclosure; Fig. 3 is a block diagram of another exemplary actuator misconfiguration detection system, wherein the actuators are brake actuators for a vehicle, according to the present disclosure; Fig. 4 a diagram of a vehicle showing the system of Fig. 3 contains, according to the present disclosure; Fig. 5 is a block diagram of an exemplary actuator misconfiguration detection system with two actuators that are swapped, according to the present disclosure; Fig. 6 is a block diagram of an exemplary actuator misconfiguration detection system having two actuators experiencing a loss of communication, in accordance with the present disclosure; Fig. 7 is a block diagram of an exemplary actuator misconfiguration detection system having an actuator experiencing a loss of performance, in accordance with the present disclosure; Fig. 8 is a block diagram of an exemplary actuator misconfiguration detection system having an actuator that is incorrectly installed, according to the present disclosure; and Fig. 9 is a flowchart of an example control process for detecting an actuator misconfiguration in a vehicle according to the present disclosure.
[0024] In the drawings, reference symbols may be used multiple times to identify similar and / or identical elements. DETAILED DESCRIPTION
[0025] Vehicles often contain controllable actuators for moving vehicle components. Sometimes, actuators associated with similar components in a vehicle are manufactured in such a way that a commonality of hardware components exists. For example, brake actuators used with a vehicle braking system and located at different corner brakes of the vehicle may each have the same (or similar) hardware components. While a commonality of hardware components can reduce the cost and time of manufacturing and installation, etc., such a benefit can be overshadowed by vehicle-level hazards associated with that commonality. For example, the commonality of hardware components increases the likelihood that at least one of the actuators can be mechanically installed at a faulty location (e.g., a corner, etc.) of the vehicle, which would create a vehicle-level hazard.For example, if a corner brake actuator is misconfigured (e.g., a left-side actuator is installed on the right side, etc.), a vehicle-level hazard may arise when a control module attempts to control the brake actuator. In such scenarios, the control module may intend to send a control signal to the corner brake actuator it believes is installed on the left side, but instead (unknowingly) send the control signal to another corner brake actuator (e.g., installed on the right side). Similar concerns may exist with actuators used with vehicle doors, steering systems, propulsion systems, and / or other safety-critical features in vehicles.
[0026] The systems and methods according to the present disclosure provide accurate verification and detection of hardware installation positions of actuators and their corresponding software by leveraging automotive communication networks and unique communication connections between the actuators and one or more control modules. For example, the systems and methods herein may include multiple actuators, each assigned a unique identifier, and at least one control module including interface ports in communication with the actuators via serial data connections. In such examples, each interface port is in communication with two actuators, and each actuator is in communication with two interface ports.With this unique configuration, the control module can receive a message from one of the actuators installed at a location on the vehicle containing its unique identifier, compare the received unique identifier assigned to the actuator with a stored identifier specific to the vehicle location, and then send an error signal indicating an error associated with the actuator in response to the received unique identifier being different from the stored identifier. Therefore, due to the unique configurations of communication networks to each actuator, along with the control module's ability to identify the physical location of each actuator based on which communication network the actuator is communicating on, the control module can detect if one of the actuators in the vehicle is mislocated and / or otherwise misconfigured and then set a system fault.Therefore, a misconfiguration of actuators in a vehicle can be detected and corrected during vehicle manufacturing, preventing the occurrence of potential safety-critical events (e.g., triggering the wrong brake, door, etc.) when the vehicle is operated.
[0027] Now, with reference to Fig. 1 shows a block diagram of an example system 100 for detecting an actuator misconfiguration in a vehicle. The system 100 of Fig. 1 may be applicable to any suitable vehicle, such as an electric vehicle (e.g., a pure electric vehicle, a plug-in hybrid electric vehicle, etc.), an internal combustion engine vehicle, etc. Additionally, the system 100 may be applicable to an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.
[0028] As in Fig. 1, the system 100 generally includes a control module 102 and four actuators 104, 106, 108, 110 in communication with the control module 102. Specifically, the control module 102 includes four interface ports 112, 114, 116, 118 that are in communication with the actuators 104, 106, 108, 110 via serial data links 120, 122, 124, 126. In the example of Fig. 1, each actuator 104, 106, 108, 110 contains two interface ports. Specifically, and as shown in Fig. 1, the actuator 104 includes the interface ports 128, 130, the actuator 106 includes the interface ports 132, 134, the actuator 108 includes the interface ports 136, 138, and the actuator 110 includes the interface ports 140, 142. Although the system 100 of Fig. 1 as including four actuators and four control module interface ports, it should be appreciated that system 100 may include more or fewer actuators and / or control module interface ports if desired. For example, system 100 may include two actuators, three actuators, five actuators, six actuators, etc., and / or two interface ports, three interface ports, five interface ports, six interface ports, etc.
[0029] In the example of Fig. 1, each interface port 112, 114, 116, 118 of control module 102 is in communication with two actuators 104, 106, 108, 110. For example, interface port 112 is connected to actuators 104, 110 via serial data connection 120, and interface port 114 is connected to actuators 106, 108 via serial data connection 122. Furthermore, interface port 116 is connected to actuators 106, 110 via serial data connection 124, and interface port 118 is connected to actuators 104, 108 via serial data connection 126. While the interface ports 112, 114, 116, 118 are shown and described as being connected to specific actuators, it should be appreciated that the system 100 may include a different control module interface port to actuator configuration as long as each interface port is in communication with a different set of two actuators.
[0030] Additionally and as in Fig. 1, each actuator 104, 106, 108, 110 is in communication with two interface ports 112, 114, 116, 118. For example, interface ports 128, 130 of actuator 104 are connected, respectively, to interface ports 118, 112 of control module 102. Similarly, interface ports 132, 134 of actuator 106 are connected (respectively) to interface ports 116, 114, interface ports 136, 138 of actuator 108 are connected (respectively) to interface ports 118, 114, and interface ports 140, 142 of actuator 110 are connected (respectively) to interface ports 116, 112.While the interface ports of the actuators 104, 106, 108, 110 are shown and described as being connected to specific interface ports of the control module 102, it should be appreciated that the system 100 may include a different actuator interface port to control a module configuration, as long as each actuator is in communication with a different set of two interface ports of the control module 102.
[0031] In the system 100 of Fig. 1, the interface ports of the control module 102 and the actuators 104, 106, 108, 110 may be any suitable type of serial interface connector. For example, the interface ports may be multi-pin, multi-socket, etc. serial ports. In such examples, the serial data connections 120, 122, 124, 126 may be wired networks. In further examples, the interface ports of the control module 102 and the actuators 104, 106, 108, 110 may form wireless connection points with antennas and receivers.
[0032] The serial data connections 120, 122, 124, 126 of Fig. 1 may be any suitable serial communications network. For example, each serial data connection 120, 122, 124, 126 may be an Ethernet connection (e.g., a wired or wireless network) or another suitable serial communications network. In various embodiments, each serial data connection 120, 122, 124, 126 may form a 10BASE-T1S network that includes the control module 102 (with its specific interface port) and the two connected actuators. In such examples, each 10BASE-T1S network may employ Ethernet networking techniques that use twisted-pair cables to send data at a rate of 10 megabits per second. With this configuration, each 10BASE-T1S network uses half-duplex transmission, such that at a given time only one module (e.g., the control module 102 or one of the connected actuators) can send data (e.g., in the form of a message).For example, each module of each 10BASE-T1S network can be given the opportunity to send data in a round-robin manner.
[0033] In the example of Fig. 1, each actuator 104, 106, 108, 110 is assigned one or more unique identifiers. Further, in certain examples, each interface port of each actuator 104, 106, 108, 110 may be assigned one or more unique identifiers. For example, the one or more unique identifiers for a particular actuator 104, 106, 108, 110 may use a defined vehicle location for the actuator as a basis. For example, actuator 104 may be referred to as a front left actuator (e.g., intended to be installed at a front left location of the vehicle), actuator 106 may be referred to as a rear left actuator, actuator 108 may be referred to as a front right actuator, and actuator 110 may be referred to as a rear right actuator.In such examples, the one or more unique identifiers assigned to the particular actuator based on the designated vehicle location may be stored in a memory module (described in . Fig. 1 (not shown) associated with this actuator. For example, software instructions stored in the memory module may be written to flash memory during actuator manufacturing to include the one or more unique identifiers. In such examples, the one or more unique identifiers may overwrite (e.g., mask) existing identifiers of the actuator.
[0034] In various embodiments, the unique identifiers for the actuators 104, 106, 108, 110 may include any suitable type of identifying reference. For example, the unique identifiers may include media access control (MAC) addresses, Internet Protocol (IP) addresses, Scalable Service-Oriented Middleware over IP (SOME / IP) addresses, etc. In one non-limiting example, the interface port 128 of the actuator 104 may be assigned a MAC address AA, the interface port 130 of the actuator 104 may be assigned a MAC address EE, the interface port 136 of the actuator 108 may be assigned a MAC address BB, and the interface port 138 of the actuator 108 may be assigned a MAC address FF. Similarly, the interface ports of the remaining actuators 106, 110 may be assigned additional MAC addresses.Thus, during the manufacture of the actuators 104, 108, software instructions associated with the actuator 104 may be written to a flash memory such that they contain the unique MAC addresses AA, EE, and software instructions associated with the actuator 108 may be written to a flash memory such that they contain the unique MAC addresses BB, FF.
[0035] Additionally, in the example of Fig. 1, the control module 102 is operable to receive and store identifiers specific to the locations of the vehicle. For example, the control module 102 may store identifiers AA, EE for ports of an actuator designated as a front left actuator and identifiers BB, FF for ports of an actuator designated as a front right actuator. Further, the control module 102 may store or associate associated ports 112, 114, 116, 118 thereof with the designated actuators. For example, the control module 102 may associate the front left actuator identifiers AA, EE (respectively) with the interface ports 118, 112 and associate the front right actuator identifiers BB, FF (respectively) with the interface ports 118, 114.Therefore, with the configuration of the stored identifiers and the associated interface ports, the control module 102 knows which actuators should be positioned at specific locations of the vehicle and which identifiers should be received from the locations.
[0036] The control module 102 is also operable to know which actuators are actually installed at specific locations on the vehicle. For example, the control module 102 receives messages from actuators 104, 106, 108, 110 installed at various locations on the vehicle. In such examples, each message contains the unique identifier assigned to the transmitting actuator. For example, in the link 126 (e.g., a network), the control module 102 (at interface port 118) may receive a message containing the unique identifier AA from the interface port 128 of the actuator 104 and the unique identifier BB from the interface port 136 of the actuator 108.
[0037] The control module 102 may then compare the received unique identifiers assigned to the actuators 104, 106, 108, 110 with the stored identifiers specific to the vehicle locations. For example, after the control module 102 receives (at the interface port 118) the unique identifier AA from the interface port 128 of the actuator 104 and the unique identifier BB from the interface port 136 of the actuator 108, the control module 102 may retrieve stored identifiers associated with the interface port 118. In such examples, the control module 102 may retrieve the stored identifiers AA, BB. The control module 102 may then compare each stored identifier AA, BB with each received unique identifier AA, BB. If the stored and received identifiers match, no action is required by the control module 102.
[0038] However, if the stored and received identifiers are different, the control module 102 may generate and transmit an error signal indicating an error associated with one or more of the actuators 104, 106, 108, 110. For example, the control module 102 transmits the error signal to a device, such as a display device, to notify technicians that the one or more actuators are misconfigured. In response, the technicians may correct the one or more misconfigured actuators.
[0039] Additionally, the control module 102 may identify a reason for the error. For example, because the control module 102 is operable to know which actuators should be positioned at specific locations of the vehicle and which identifiers should be received from the locations, the control module 102 may identify whether certain actuators are swapped (e.g., the front left actuator and the front right actuator are swapped), whether a particular actuator is at an incorrect location, whether a particular actuator is programmed with the incorrect identifiers, etc., as further explained below. Then, the control module 102 may generate and transmit the error signal with the reason for the error, if necessary.
[0040] In various embodiments, the control module 102 may be Fig. 1 may contain and / or be in communication with multiple modules for communicating with, receiving data from, etc., the actuators 104, 106, 108, 110. For example, in certain embodiments, the control module 102 may contain and / or be in communication with multiple aggregator modules, each having a different set of the interface ports 112, 114, 116, 118 of Fig. 1. In such examples, each aggregator module may be a networking component that allows multiple network connections to be bundled into a single connection. This configuration may meet potential redundancy requirements for single-point failures in the system.
[0041] For example, Fig. 2 illustrates another system 200 for detecting an actuator misconfiguration in a vehicle. The system 200 is substantially similar to the system 100 of Fig. 1, but includes two aggregator modules 250, 252. Specifically, the system 200 includes a control module 202 that controls the aggregator modules 250, 252 and the actuators 104, 106, 108, 110 of Fig. 1. As shown, the aggregator module 250 includes the interface port 112 connected to the actuators 104, 110 (via the serial data connection 120 and the interface ports 130, 142), and the interface port 114 connected to the actuators 106, 108 (via the serial data connection 122 and the interface ports 134, 138). Additionally, the aggregator module 252 includes the interface port 116 connected to the actuators 106, 110 (via the serial data connection 124 and the interface ports 132, 140), and the interface port 118 connected to the actuators 104, 108 (via the serial data connection 126 and the interface ports 128, 136).
[0042] In the example of Fig. 2, the control module 202 can be configured in a similar manner to the control module 102 of Fig. 1. For example, the control module 202, through the aggregator modules 250, 252, may receive messages containing the unique assigned identifiers from the actuators 104, 106, 108, 110 installed at locations of the vehicle, compare the received unique identifiers with stored identifiers specific to the locations of the vehicle, and then generate and transmit an error signal indicating an error associated with one or more of the actuators 104, 106, 108, 110 (and, in some embodiments, an identified reason for the error) if the compared identifiers are different, as explained herein.
[0043] Although the system 200 of Fig. 2 depicts the aggregator modules 250, 252 as internal to the control module 202, it should be appreciated that other suitable configurations may be employed if desired. For example, the aggregator modules 250, 252 may be separate (e.g., external) components from the control module 202, but may be in communication with the control module 202. In further examples, the aggregator modules 250, 252 may each be considered a control module and may be considered the control module 102 of Fig. 1 be operable.
[0044] As explained herein, actuators 104, 106, 108, 110 may be used with a variety of vehicle features. For example, actuators 104, 106, 108, 110 may be actuators used with a vehicle braking system, vehicle doors, a vehicle steering system, a vehicle propulsion system, and / or any other suitable vehicle feature.
[0045] Fig. 3 illustrates another system 300 for detecting an actuator misconfiguration in a vehicle, the system 300 including actuators used in a vehicle braking system. As shown, the system 300 includes the control module 202 of Fig. 2 and the actuators 104, 106, 108, 110 of Fig. 1 in communication with the control module 202 by means of the unique configurations of communication networks as explained herein.
[0046] In the example of Fig. 3, the actuators 104, 106, 108, 110 may be any suitable type of brake actuator for the vehicle. For example, the actuators 104, 108 may be considered front brake actuators and installed at front left and front right locations of the vehicle, respectively. The actuators 106, 110 may be considered rear brake actuators and installed at rear left and rear right locations of the vehicle, respectively. In various embodiments, the front actuators 104, 108 may be electro-hydraulic actuators for brakes associated with the front wheels of a vehicle, and the rear actuators 106, 110 may be electromechanical actuators for brakes associated with the rear wheels of a vehicle. In such examples, each actuator 104, 106, 108, 110 may include various components 304, 306, 308, 310, such as: B. contain an electric motor, valves, etc.
[0047] As in Fig. 3, the actuators 104, 106, 108, 110 also include control modules 360, 362, 364, 366 and memory modules 370, 372, 374, 376 associated with the control modules 360, 362, 364, 366. For example, the memory modules 370, 372, 374, 376 may include components in the control modules 360, 362, 364, 366 (as shown in Fig. 3) and / or outside of (but in communication with) the control modules 360, 362, 364, 366.
[0048] In various embodiments, the memory modules 370, 372, 374, 376 associated with the control modules 360, 362, 364, 366 can store desired information. For example, the memory modules 370, 372, 374, 376 can store unique identifiers such as MAC addresses, etc., as explained above. In such examples, flash memory of the memory modules 370, 372, 374, 376 can be written to contain unique identifiers during manufacture of the actuators 104, 106, 108, 110.
[0049] Additionally, in certain examples, the memory modules 370, 372, 374, 376 may store information about the actuators 104, 106, 108, 110 and an expected location of the actuators 104, 106, 108, 110 in the vehicle. In various embodiments, the information and location of the actuators 104, 106, 108, 110 may be stored when the actuators 104, 106, 108, 110 are originally manufactured. The information about the actuators 104, 106, 108, 110 may include, for example, an actuator size (e.g., a torque value), the type of actuator (e.g., hydraulic, electro-hydraulic, electromechanical, etc.), etc. Additionally, the expected location of the actuators 104, 106, 108, 110 may include, for example, left front, right front, left rear, right rear, etc.
[0050] Additionally included in the example of Fig. 3 the control modules 360, 362, 364, 366 interface ports for communicating with the aggregator modules 250, 252. Specifically, the control module 360 contains the interface ports 128, 130 of Fig. 1, the control module 362 contains the interface connections 132, 134 of Fig. 1, the control module 364 contains the interface connections 136, 138 of Fig. 1 and the control module 366 contains the interface connections 140, 142 of Fig. 1. In such examples, the interface ports 128, 130, 132, 134, 136, 138, 140, 142 are in communication with the interface ports 112, 114, 116, 118 of the aggregator modules 250, 252, as explained above.
[0051] In various embodiments, one of the actuator misconfiguration detection systems herein and / or components thereof may be deployed in a vehicle. For example, Fig. 4 represents a vehicle 400 that the system 300 of Fig. 3. Specifically and as in Fig. 4, the vehicle 400 includes the control module 202 and the actuators 104, 106, 108, 110 of Fig. 3. As shown, the actuators 104, 108 are arranged at locations on the front left and right of the vehicle 400, respectively, and the actuators 106, 110 are arranged at locations on the rear left and right of the vehicle, respectively. Although the vehicle 400 is Fig. 4 as including the system 300, it should be appreciated that the vehicle 400 may include another actuator misconfiguration detection system such as one of the systems 100, 200. Furthermore, although the actuators 104, 106, 108, 110 of Fig. 4 as brake actuators, it should be recognized that the actuators 104, 106, 108, 110 can be used with other vehicle features such as vehicle doors, a vehicle steering system, a vehicle propulsion system, etc.
[0052] In various embodiments, the control modules herein may detect one or more actuator misconfigurations in vehicles, as explained herein. For example, the control modules 102, 202 of Fig. 1- Fig. 3 be preconfigured to know which actuators should be positioned at specific locations on the vehicle (and therefore connected to specific interface ports of the control module) and which identifiers should be received from those locations. Thus, if the actuators are installed at specific locations on the vehicle and then send their unique identifiers to the control module, the control module can compare its stored (preconfigured) identifiers with the received unique identifiers to detect an actuator misconfiguration (e.g., a system failure) and identify a cause of the system failure.
[0053] For example, the control module 202 may detect and identify a software misconfiguration specific to one of the installed actuators 104, 106, 108, 110. For example, the actuators 104, 106, 108, 110 may contain defined software identifiers (SW identifiers) stored therein and known by the control module 202. The SW identifier for each actuator 104, 106, 108, 110 is different due to different software commands (e.g., with different MAC addresses) employed by the actuator. When communicating with the control module 202, the actuators 104, 106, 108, 110 may provide their SW identifiers along with other data about the actuators. If the received SW identifier for one of the actuators 104, 106, 108, 110 is unexpected (e.g., not the correct SW identifier for the installed location in the vehicle), the control module 202 may identify the software misconfiguration for the particular actuator as the reason for a system failure.
[0054] In further examples, the control module 202 may detect and identify a hardware and / or physical misconfiguration specific to one of the installed actuators 104, 106, 108, 110. For example, Fig. 5 represents a system 500 which is substantially similar to the system 200 of Fig. 2, but with the actuators 104, 108 swapped. In such examples, the control module 202 expects to receive unique identifiers (e.g., MAC addresses AA, EE) for the interface ports 128, 130 of the actuator 104 at the interface ports 118, 112, respectively, and unique identifiers (e.g., MAC addresses BB, FF) for the interface ports 136, 138 of the actuator 108 at the interface ports 118, 114, respectively. However, if the actuators 104, 108 are swapped, the control module 202 actually receives the unique identifier (e.g., the MAC address EE) for the interface port 130 of the actuator 104 at the interface port 114 and the unique identifier (e.g., the MAC address FF) for the interface port 138 of the actuator 108 at the interface port 112.Therefore, when the control module 202 compares the received unique identifiers with its stored identifiers, the control module 202 can detect that the actuators 104, 108 are swapped.
[0055] Additionally, the control module 202 may detect and identify misconfigurations when additional sets of actuators 104, 106, 108, 110 are swapped in a similar manner as explained above. For example, the control module 202 may detect and identify misconfigurations when the actuators 104, 106 are swapped, the actuators 108, 110 are swapped, the actuators 106, 110 are swapped, the actuators 104, 110 are swapped, and the actuators 106, 108 are swapped.
[0056] The control modules 102, 202 may also detect and identify a loss of communication and / or a loss of power with respect to one or more of the actuators 104, 106, 108, 110. For example, Fig. 6 represents a system 600 which is substantially similar to the system 200 of Fig. 2, however, interface port 130 of actuator 104 and interface port 138 of actuator 108 experience a loss of communication with control module 202 (as indicated by reference numerals 678, 680). In such examples, control module 202 expects to receive data from actuators 104, 108 at interface ports 112, 114 of aggregator module 250. If communication with respect to ports 130, 138 is lost, aggregator module 250 may not receive data with respect to ports 130, 138, may receive a diagnostic trouble code (DTC), etc. Again, control module 202 detects the loss of communication for ports 130, 138 of actuators 104, 108 as the reason for a system fault.
[0057] Although the system 600 of Fig. 6 as having a communication loss with respect to the interface ports 130, 138 of the actuators 104, 108, it should be appreciated that other interface ports (e.g., the interface ports 128, 136) of the actuators 104, 108 and / or interface ports of the actuators 106, 110 may experience a communication loss. Additionally, it should be appreciated that while the system 600 includes two interface ports experiencing a communication loss, only one interface port or more than two interface ports of the system 600 may experience a communication loss. Regardless of the one or more specific interface ports experiencing a communication loss, the control module may detect and recognize the communication loss for the one or more specific interface ports in a similar manner as discussed above.
[0058] Fig. 7 illustrates a system 700 which is substantially similar to the system 200 of Fig. 2, however, actuator 104 is experiencing a power loss (as indicated by reference numerals 782, 784). In such examples, control module 202 expects to receive data from actuator 104 at interface ports 112, 118 of aggregator modules 250, 252. If power has failed at actuator 104, aggregator modules 250, 252 need not receive data related to ports 128, 130, may receive a DTC, etc. Again, control module 202 detects the power loss for actuator 104 as the reason for a system failure. Control module 202 may also detect a power loss related to the other actuators 106, 108, 110 in a similar manner.
[0059] In various embodiments, the control module 102, 202 may also detect and identify a faulty actuator installed at a particular location. For example, Fig. 8 represents a system 800 which is substantially similar to the system 200 of Fig. 2, but with an incorrectly installed actuator. Specifically and as in Fig. 8, the system 800 includes the control module 202, the actuators 104, 108, 110 and an actuator 104-1. In the example of Fig. 8, the actuators 104, 108, 110 are correctly installed and the actuator 104-1 is incorrectly installed. In such examples, the actuator 104 is designated as a front left actuator (e.g., and installed at a front left location of a vehicle) and is assigned unique identifiers for that location (e.g., a MAC address AA for the interface port 128 and a MAC address EE for the interface port 130). Additionally, the actuator 106 may be designated as a rear left actuator and assigned identifiers for that location, while the actuator 110 may be designated as a rear right actuator and assigned unique identifiers for that location. In the example of Fig. 8, actuator 104-1 is the same as actuator 104, but is installed on the front right side of the vehicle. Therefore, actuator 104-1 contains unique identifiers (e.g., a MAC address AA for an interface port 128-1 and a MAC address EE for an interface port 130-1) for a front left location of the vehicle.
[0060] In such examples, the control module 202 receives the same unique identifiers (e.g., MAC addresses AA, EE) from the actuators 104, 104-1. For example, the control module 202 may expect to receive the MAC addresses AA, EE from the front left actuator (respectively) at the interface ports 118, 112 of the aggregator modules 252, 250 and the MAC addresses BB, FF from the front right actuator (respectively) at the interface ports 118, 114 of the aggregator modules 252, 250. However, in the example of Fig. 8, the control module 202 actually receives the MAC addresses AA, EE from both actuators 104, 104-1. Therefore, the control module 202 can detect that the faulty actuator is installed at the front right location of the vehicle because the interface port 114 of the aggregator module 250 receives the MAC address EE instead of (as expected) FF.
[0061] Furthermore, in various embodiments, the control module 202 may receive and / or generate a DTC because the faulty actuator 104-1 is installed at the front right location. For example, because both actuators 104, 104-1 are the same (physically and in terms of software installed therein), the actuators 104, 104-1 have the same device identifier, which can be used to prioritize (e.g., order) communication on the serial data connection (e.g., a network) associated with the interface port 118 of the aggregator module 252 and the actuators 104, 104-1. Therefore, because both actuators 104, 104-1 have the same device identifier, the actuators 104, 104-1 may attempt to communicate with the aggregator module 252 at the same time. This may result in a DTC indicating a possible collision at interface port 118 of aggregator module 252.
[0062] Fig. 9 illustrates an example control process 900 performed by the system 300 of Fig. 3 for detecting an actuator misconfiguration in a vehicle. Although the example control process 900 with respect to the system 300 of Fig. 3, the process 900 may be performed by any suitable system such as the systems 100, 200 of Fig. 1- Fig. 2. The control process 900 may start when the system is turned on and / or at another suitable time.
[0063] As in Fig. 9, control begins at 902, where unique identifiers are stored in actuator memory modules. For example, the unique identifiers such as MAC addresses, IP addresses, SOME / IP addresses, etc., may be stored in actuators 104, 106, 108, 110 (e.g., in memory modules 370, 372, 374, 376) during actuator manufacturing. In such examples, the unique identifiers may be assigned to the actuators based on designated vehicle locations (e.g., intended locations within the vehicle). For example, actuator 104 may be designated as a front left actuator and assigned unique identifiers specific to the front left of the vehicle.
[0064] Control then proceeds to 904, where identifiers specific to locations of the vehicle are stored in a memory module associated with control module 202. For example, control module 202 may store identifiers for actuators at various locations of the vehicle (e.g., a front left actuator; a front right actuator; a rear left actuator; a rear right actuator; etc.), as explained herein.
[0065] Control then proceeds to 906, where the control module 202 initiates communication with one or more of the installed actuators 104, 106, 108, 110. For example, the aggregator modules 250, 252 may first send beacons to the actuators 104, 106, 108, 110 and then wait for responses from the actuators 104, 106, 108, 110. As an example, the aggregator module 250 may send a beacon from the interface port 112 to the actuators 104, 110 (e.g., to the control modules 360, 366). The actuators 104, 110 may then respond with messages containing, for example, their unique identifiers.
[0066] Control then proceeds to 908, where control module 202 determines whether messages are being received from the actuators. If so, control proceeds to 910. Otherwise, control proceeds to 920. At 910, control module 202 extracts the unique identifiers from the received messages. Control then proceeds to 912.
[0067] At 912, the control module 202 compares the unique identifiers extracted from the received messages with identifiers previously stored in its memory module. For example, the control module 202 may determine the location of the actuators associated with the received messages. In such examples, if the messages are received at the interface port 112 of the aggregator module 250, the control module 202 may determine the locations of the actuators because the control module 202 knows that the interface port 112 receives messages from the specific locations in the vehicle (e.g., a front left location and a rear right location). The control module 202 may then retrieve the identifiers associated with the specific locations from the memory module associated with the control module 202.Once retrieved, control module 202 may compare the unique identifiers extracted from the received messages with the previously stored identifiers. Control then proceeds to 914.
[0068] At 914, the control module 202 determines whether the compared identifiers are different. If the compared identifiers are not different, control proceeds to 916. However, if the compared identifiers are different, control proceeds to 920. At 920, the control module 202 identifies one or more failure reasons for the installed actuator, as explained herein. For example, the control module 202 may identify a loss of communication and / or a loss of power with respect to one or more of the actuators 104, 106, 108, 110 if, for example, no message is received at 908. In further examples, the control module 202 may identify a hardware misconfiguration and / or a physical misconfiguration with respect to one or more installed actuators based on the comparison between the extracted unique identifiers and the previously stored identifiers.In yet further examples, control module 202 may identify a software misconfiguration specific to one of the installed actuators, as explained herein. Control then proceeds to 916.
[0069] At 916, the control module 202 determines whether any additional actuators are installed. If so, control proceeds to 918, where the control module 202 initiates communication with the next installed actuator (or set of installed actuators) in a similar manner as explained above with respect to 906. Control then returns to 908. If no additional actuators are installed, control proceeds to 922, as in Fig. 9 is shown.
[0070] At 922, the control module 202 determines whether a fault reason has been identified for any of the installed actuators. If not, control may end as shown in Fig.9. If so, control proceeds to 924, where the control module 202 determines the system state based on all identified fault reasons. Control then proceeds to 926, where the control module 202 generates and transmits a fault signal indicating a system fault based on the identified fault reasons. For example, the control module 202 may transmit the fault signal indicating the reason for a fault associated with one or more of the actuators 104, 106, 108, 110 to a device, such as an indicator device, thereby notifying technicians that the one or more actuators are misconfigured.
[0071] The actuator misconfiguration detection systems and methods herein achieve numerous benefits. For example, the unique communication links associated with actuators and one or more control modules ensure that vehicles have correct actuator configurations before the vehicles are delivered to users, car dealers, etc. For example, if the actuators are incorrectly installed and / or have software misconfigurations, the control modules herein will detect such issues unless unreasonable interventions are made to significantly modify the actuators, vehicle wiring harnesses, etc. Additionally, the actuator misconfiguration detection systems and methods allow one part number to be applied to different corner actuators, preventing the proliferation of hardware variants within the actuators.For example, each of the actuators may be physically the same, but assigned different unique identifiers, enabling the use of a single part number. Furthermore, the actuator misconfiguration detection systems and methods eliminate the need for mechanical connector keying, keying using unique terminal hardware (e.g., a specific voltage on a terminal), or keyed mounting features (e.g., a unique screw spacing for each corner).
[0072] The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure may be implemented in various forms. Therefore, while this disclosure contains specific examples, the true scope of the disclosure should not be so limited because other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It is to be understood that one or more steps within a method may be performed in a different order (or overlapping in time) without altering the principles of the present disclosure.Furthermore, although each of the embodiments has been described above with certain features, one or more of the features described with respect to any embodiment of the disclosure may be implemented in any of the other embodiments and / or combined with their features, even if this combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with each other remain within the scope of this disclosure.
[0073] Spatial and functional relationships between elements (e.g., between modules, circuit elements, semiconductor layers, etc.) are described using various terms, such as "connected," "engaged," "coupled," "adjacent," "adjacent," "on top of," "over," "below," and "disposed." Unless explicitly described as "direct," when the above-described disclosure describes a relationship between a first and a second element, that relationship may be a direct relationship, with no other intervening elements between the first and second elements, but it may also be an indirect relationship, with one or more intervening elements (either spatial or functional) between the first and second elements.
[0074] As used herein, the phrase at least one of A, B, and C shall be construed to mean a logical (A OR B OR C) using a non-exclusive logical OR, and shall not be construed to mean "at least one of A, at least one of B, and at least one of C."
[0075] In the figures, the direction of an arrow, indicated by the arrowhead, generally demonstrates the flow of information (such as data or commands) of interest for the illustration. For example, if element A and element B exchange different information, but the information transmitted from element A to element B is relevant for the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no further information is sent from element B to element A. Furthermore, element B may send requests or acknowledgments of receipt of the information to element A for the information sent from element A to element B.
[0076] Throughout this application, including the definitions below, the term "module" or the term "controller" may be replaced with the term "circuit." The term "module" may refer to, be part of, or include: an application-specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field-programmable gate array (FPGA); processor circuitry (shared, dedicated, or group) that executes code; memory circuitry (shared, dedicated, or group) that stores code executed by the processor circuitry; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.
[0077] The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules connected via interface circuits. For example, multiple modules may enable load balancing. In another example, a server module (also known as a remote or cloud module) may perform some functionality on behalf of a client module.
[0078] The term code, as used above, may include software, firmware, and / or microcode, and may refer to programs, routines, functions, classes, data structures, and / or objects. The term shared processor circuitry includes a single processor circuit that executes some or all of the code from multiple modules. The term group processor circuitry includes a processor circuit that, in combination with additional processor circuitry, executes some or all of the code from one or more modules. References to multiprocessor circuitry include multiprocessor circuits on discrete chips, multiprocessor circuits on a single chip, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above.The term shared memory circuit refers to a single memory circuit that stores some or all of the code from one or more modules. The term group memory circuit refers to a memory circuit that, in combination with additional memories, stores some or all of the code from one or more modules.
[0079] The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not include transient electrical or electromagnetic signals that propagate through a medium (such as on a carrier wave); the term computer-readable medium can therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory, tangible computer-readable medium include non-volatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such asa CD, a DVD or a Blu-ray disc).
[0080] The devices and methods described in this application may be implemented partially or entirely by a special-purpose computer, which is created by configuring a general-purpose computer to perform one or more specific functions embodied in computer programs. The functional blocks, flowchart components, and other elements described above serve as software specifications that can be translated into computer programs through the routine work of a trained technician or programmer.
[0081] The computer programs contain processor-executable instructions stored on at least one non-transitory tangible computer-readable medium. The computer programs may also contain or access stored data. The computer programs may include a basic input / output system (BIOS) that interacts with the computer's hardware for a special purpose, device drivers that interact with specific devices of the computer for a special purpose, one or more operating systems, user applications, background services, background applications, etc.
[0082] The computer programs may contain: (i) descriptive text to be parsed, such as: B. HTML (Hypertext Markup Language), XML (Extensible Markup Language) or JSON (JavaScript Object Notation), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a compiler at runtime, etc. By way of example only, the source code may be written using the syntax of languages including C, C++, C#, Objective C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language, 5th Revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK and Python®.
Claims
[1] A system for detecting an actuator misconfiguration in a vehicle, the system comprising: several actuators, each of the several actuators being assigned a unique identifier; and a control module including a plurality of interface ports in communication with the plurality of actuators via serial data connections, wherein each interface port of the control module is in communication with two of the plurality of actuators, each actuator of the plurality of actuators is in communication with two interface ports, and the control module is configured to: Receiving a message from an actuator of the plurality of actuators installed at a location of the vehicle, the message including the unique identifier assigned to the actuator; Comparing the received unique identifier assigned to the actuator with a stored identifier specific to the location of the vehicle; and Sending, in response to the received unique identifier that is different from the stored identifier, an error signal indicating an error associated with the actuator. [2] The system of claim 1, wherein the control module is configured to: Identifying a reason for the error based on the received unique identifier and the stored identifier and Sending the error signal with the reason for the error. [3] System according to claim 1, wherein the control module’s multiple interface ports contain four interface ports and the multiple actuators contain four actuators. [4] System according to claim 3, wherein the four actuators include a first actuator installed at a front left location of the vehicle, a second actuator installed at a front right location of the vehicle, a third actuator installed at a rear left location of the vehicle, and a fourth actuator installed at a rear right location of the vehicle, and the four interface ports include a first interface port in communication with the first actuator and the fourth actuator, a second interface port in communication with the second actuator and the third actuator, a third interface port in communication with the third actuator and the fourth actuator, and a fourth interface port in communication with the first actuator and the second actuator. [5] The system of claim 4, wherein the four actuators are brake actuators. [6] The system of claim 5, wherein each brake actuator of the brake actuators includes a memory module configured to store information about the brake actuator and an expected location of the brake actuator in the vehicle before the brake actuator is installed in the vehicle. [7] A system for detecting an actuator misconfiguration in a vehicle, the system comprising: several actuators, each of the several actuators being assigned a unique identifier; and a control module including a first aggregator module and a second aggregator module, wherein the first aggregator module includes a plurality of interface ports, each interface port of the first aggregator module being in communication with two different actuators of the plurality of actuators via a serial data connection, the second aggregator module includes a plurality of interface ports, each interface port of the second aggregator module being in communication with two different actuators of the plurality of actuators via a serial data connection, and the control module is configured to: Receiving, by the first aggregator module or the second aggregator module, a message from an actuator of the plurality of actuators installed at a location of the vehicle, the message including the unique identifier assigned to the actuator; Comparing the received unique identifier assigned to the actuator with a stored identifier specific to the location of the vehicle; and Sending, in response to the received unique identifier that is different from the stored identifier, an error signal indicating an error associated with the actuator. [8] System according to claim 7, wherein the plurality of interface ports of the first aggregator module include two interface ports; the plurality of interface ports of the second aggregator module include two interface ports and the multiple actuators contain four actuators. [9] The system of claim 8, wherein each actuator of the plurality of actuators includes a first interface port in communication with one of the two interface ports of the first aggregator module and a second interface port in communication with one of the two interface ports of the second aggregator module. [10] System according to claim 8, wherein the four actuators include a first actuator arranged at a front left position of the vehicle, a second actuator arranged at a front right position of the vehicle, a third actuator arranged at a rear left position of the vehicle, and a fourth actuator arranged at a rear right position of the vehicle; the two interface ports of the first aggregator module include a first interface port in communication with the first actuator and the fourth actuator and a second interface port in communication with the second actuator and the third actuator, and the two interface ports of the second aggregator module include a first interface port in communication with the third actuator and the fourth actuator and a second interface port in communication with the first actuator and the second actuator.
