An engine control unit or an “ECU” is a widely used type of electronic controller that controls a series of actuators on an internal combustion engine to ensure optimal engine performance. It does this by reading values of a multitude of sensors in the engine bay and interpreting the data it receives using lookup tables which adjust engine actuators appropriately.
The ECU monitors various sensors on the automobile such as sensors for oxygen level, coolant temperature, mass air flow, air intake temperature, crank shaft angle, throttle position, cam shaft angle and engine knock. Lookup tables provide feedback information for adjustment and control of ignition timing, cam shaft position, fuel injector input, fuel pump input, fuel pump pressure, cooling fan speed, transmission control systems, forced air induction controls, traction controls and transmission gear selections. In many situations, ECUs also send error codes to the vehicle dashboard to indicate immediate problems, such as overheating, or maintenance requirements, like oil changes. In some cases, the error codes activate warning lights which must be deactivated by the dealer.
Certain classes of ECUs are programmable. Modern ECUs incorporate a microprocessor which can process inputs from engine sensors in real time. The microprocessor stores its programming in firmware which is resident in flash memory or e-proms attached to the CPU of the microprocessor.
Programmable ECUs are required, for example, where significant aftermarket performance enhancing modifications have been made. Such modifications often include the addition of a turbo charger, intercooler or modified exhaust system. Programmable ECU's are also used for several vehicle systems, such as engine control module (ECM), transmission control module (TCM), body control module, anti-lock brake system (ABS), airbag control module, and so on, that each receive routine updates from the manufacturer of the vehicle. Each ECU is remapped or reprogrammed to adapt the performance of the involved system to match the required modifications and/or to update the software and parameters of the ECU. Other changes for high performance engines which can be remapped in an ECU include ignition timing, maximum RPM, water temperature correction, transient fueling, low fuel pressure modifiers and a closed loop lambda (in order to modify a target air/fuel ratio), turbo charger waste gate control, staged fuel injection, variable cam timing, gear control and turbo charger anti-lag.
Referring to
Client device 110 is connected through a mobile network to Internet 108. Client device 110 is also connected to local device 112. In a preferred embodiment the local device establishes a Wi-Fi or Bluetooth connection between the client device and the automobile. Local device 112 is hardwired to the automotive controller 114. Automotive controller 114 is connected to sensors 120 and actuators 122 resident on the vehicle. The sensors and actuators communicate with the onboard controller through a CAN BUS (also known as a controller area network (CAN) bus) as is known in the art.
Client device 110, acts as a client of system server 102, and as a client of local device 112. Embodiments of client device 110 include any handheld wireless device, such as, a smart phone, a tablet computer, a notebook computer, a netbook computer, and so on.
Dealer server 116 is also connected to Internet 108 and communicates through the Internet to both the system server and the local device. Similarly, calibration writer server 118 is connected through the Internet to system server 102 and client device 110.
Referring to
At step 201, the client device opens the application and sets up an account by entering certain demographic information. At step 202, the application uploads the account information to system server 102.
At step 203, the calibration writer server sets up an account through a form served up through the Internet from the system server. The calibration writer server includes account information such as name, address, email address, and submit computer Cal/Pid. At step 204, calibration writer server inputs a set of operating system parameters which include programming information and look up tables for the onboard controller. At step 206, the parameters are submitted to system server 102. At step 208, system server 102 stores the parameters and the account implementation. At step 210, the database is updated by the system server with the new parameters and associated with the calibration writer server. At step 212, the system server uploads the parameters to client device 110 via a wireless network.
In an alternative embodiment, a technician downloads the parameters or firmware from calibration writer server 118 via a web browser. The technician then uses system server 102 to download the updated parameters or firmware to smart phone 110.
At step 214, a client device stores the parameters. At step 215, client device opens an application (or “App”) which displays the parameters and certain options to the user. At step 216, the client device receives options from the user as to which parameters to implement. At step 218, the chosen parameters are uploaded to the local device via a Wi-Fi or Bluetooth connection. At step 220, the local device stores the parameters and initiates certain timing functions such as onboard recording and storage of data.
At step 222, the chosen parameters are uploaded to the automotive controller. At step 224, the automotive controller stores the new parameters and lookup tables. At step 226 the automotive controller implements the new parameters and lookup tables. At step 228, the automotive controller generates an acknowledge signal. At step 230, the acknowledge signal is sent to the local device. At step 231, the local device stores the acknowledge signal. At step 232, the local device reports the acknowledge signal to client device 110 via the WiFi or Bluetooth connection. At step 233, the client device stores the acknowledge signal and the App displays the status of the local device and the uploaded parameters.
Referring to
At step 263, client device 110 chooses an option on the application to clear error codes. At step 264, the request is uploaded to the local device. At step 265, the request is stored in memory on the local device. At step 266, the request is uploaded to the automotive controller. At step 267, the automotive controller acknowledges the request and clears the error code.
At step 268, the client device chooses an option on the application to request a diagnostic report. At step 269, the request is uploaded to the local device. At step 270, the local device stores the request. At step 266, the local device uploads the request to the automotive controller. At step 271, the automotive controller generates the diagnostic report. At step 272, the diagnostic report is sent to the local device. At step 273, the local device stores the diagnostic report, according to date and time, in memory. At step 274, the diagnostic report is sent to the client device. At step 275, the diagnostic report is displayed according to the request of the user.
At step 276, the client device, through use of the application requests a calibration report. At step 277, the calibration request is uploaded to the local device. At step 278, the local device stores the request for calibration. At step 279, the local device forwards the request to the automotive controller. At step 280, the automotive controller accesses the currently stored parameters and the calibration. At step 281, the parameters are sent to the local device. At step 282, the local device stores the current set of parameters according a date and time stamp. At step 283, the local device sends the parameters to the client device. At step 284, the application on the client device displays the requested calibration parameters.
Referring to
System server 102 presents a set of webpages for the various users of the system through web server 104 using a user/password interface. At 302, 304, and 306 a schematic of the local home page is shown. Local home page provides options for a choice of a user type for each of calibration writer server, a dealer, and a customer or “end user.” The database includes records for each vehicle 310 and each computer profile ID number 312. Each record 310 includes vehicle identification number, ECU serial number, make, model, engine, fuel tank number, gear ratio, tire size and vehicle modification categories. Each record is associated with a particular vehicle entered into the system. Computer profile ID number 312 is a database entry including vehicle, calibration, PID configuration, and warning type. Computer profile ID number 312 also includes vehicle options and datalog recordings for each vehicle.
Calibration writers webpage 304 includes forms for entry of a data record for users who input engine control parameters. Each data record includes entries for photos or logos, name, phone, address, start date, email and computer Cal/Pid. When the form is complete, upon entry, system server 102 enters the data from the data form into a record into the database. The system server then copies the data record into computer profiles ID number 312. All reports generated by the automotive controller at the request of the local device are associated with current calibration of the vehicle when stored in memory. In a preferred embodiment, the data in the record is then copied directly into memory at vehicles 310.
The dealers webpage 306 serves up a form for data entry including data related to photo/logo, name, phone, address, start date and email address. The “dealers” in a preferred embodiment are typically maintenance shops which service vehicles but do not write calibrations.
The customers webpage 308 includes a form for entry of data regarding photo, phone number, start date and email address. The web form also enables the customer to request download of an application to be locally installed. The APP GUI provides access to the functions of the local device. In a preferred embodiment, the functions include requesting a report of a current calibration, requesting a live report of engine status, requesting a diagnosis report, requesting that an error code be cleared and uploading a calibration update from a dealer or manufacturer.
A preferred embodiment of local device 112 includes the Freescale IMX28 Microcontroller, a UART for translation between parallel and serial data forms, Wi-Fi connectivity employing the IEEE 802.11 standard or other wireless protocol for communication between client device 110 and the local device 112 and provisions for a local interconnect network LIN for communication between vehicle components and a CAN BUS for communication between microcontrollers and other devices.
Referring to
At step 411, automotive controller 114 generates a check engine code and freezes a frame of data. The check engine code identifies a problem with the vehicle. The frozen data indicates the status of the vehicle at the time when the problem that caused the check engine code to be generated occurred.
At step 412, a data connection is established between local device 112 and automotive controller 114. In one embodiment, the data connection is established by connecting local device 112 to an onboard diagnostics port that is connected to a CAN BUS to which automotive controller 114 is connected.
At step 413, a wireless connection is established between client device 110 and local device 112. In one embodiment, local device 112 acts as a wireless local area network (WLAN) access point to which client device 110 can connect. In establishing the wireless connection, transmission control protocol (TCP) socket is opened between client device 110 and local device 112 so that data can be passed back and forth between client device 110 and local device 112 using JavaScript Object Notation (JSON) messages.
At step 414, a request for gauge data is sent from client device 110 and is received by local device 112. In one embodiment, the request is sent using JSON using the TCP socket. For each of the one or more gauges displayed by client device 110, a gauge data request is sent. After receiving the request from client device 110 by local device 112, client device 110 is subscribed to and receives notifications from local device 112 that include updated data to be displayed on the gauge associated with the gauge data request.
At step 415, a data request is sent from local device 112 and is received by automotive controller 114.
At step 416, automotive controller 114 retrieves the gauge data. In one embodiment, automotive controller 114 retrieves parameter identifier (PID) data that is associated with the gauge data.
At step 417, the data is sent from automotive controller 114 and is received by local device 112.
Optionally at step 418, local device 112 records the data received from automotive controller 114 in a log file on local device 112.
At step 419, the requested data is sent from local device 112 and is received by client device 110. In one embodiment, client device 110 is subscribed to local device 112 so as to receive a notification from local device 112 each time local device 112 receives updated data from automotive controller 114.
At step 420, the data is displayed by client device 110. The layout settings that describe the look and feel of the gauge are stored on client device 110 and the data is displayed in accordance to the layout settings.
At step 421, a request for the engine code, the frozen data, and optionally the log data is sent from client device 110 and is received by local device 112.
At step 422, a request for the engine code and the frozen data is sent from local device 112 and is received by automotive controller 114.
At step 423, automotive controller 114 retrieves the engine code and frozen data that were generated in step 411.
At step 424, the engine code and frozen data are sent from automotive controller 114 and are received by local device 112.
At step 425, the engine code, frozen data, and optional log are sent from local device 112 and are received by client device 110.
At step 426, client device 110 stores the engine code, frozen data, and optional log.
At step 427, client device 110 displays the engine code.
At step 428, the engine code, frozen data, and optional log is sent from client device 110 and is received by system server 102.
At step 429, a request for updated engine parameters is sent from client device 110 and is received by system server 102.
At step 430, a request for updated engine parameters is sent from system server 102 and is received by calibration writer server 118.
At step 431, updated parameters and/or firmware are sent from calibration writer server 118, and are received by system server 102.
At step 432, the updated parameters and firmware are sent from system server 102 and are received by client device 110.
At step 433, the updated parameters and firmware are stored on client device 110.
At step 434, the technician selects one or more parameters and firmware with which to update the vehicle.
At step 435, the selected parameters and firmware are sent from client device 110 and are received by local device 112. One or more parameters and the firmware may be selected to be updated and are sent.
At step 436, reprogramming instructions are sent from local device 112 and are received by automotive controller 114. In one embodiment, the instructions cause automotive controller 114 to be flashed with the updated firmware when the firmware is selected to be updated. Additionally, parameters can be changed beyond what was included with the updated firmware. The updated firmware may be the latest default firmware from the vehicle manufacturer that does not have every parameter tuned for the specific configuration of the vehicle. In one embodiment, the reprogramming instructions of local device 112 first reflashes automotive controller 114 with the updated firmware and then updates specific engine tuning parameters.
At step 437, automotive controller 114 updates the firmware and parameters to the values received from local device 112.
Referring to
User interface 502 is displayed on a client device via an app running on the client device. The name, value, and units of each respective mini gauge 510, 512, 514, 516, 518, 520, 522, and 524 are displayed on user interface 502 on a client device. Values 542, 544, 546, 548, 550, 552, 554, and 556 respectively of each mini gauge 510, 512, 514, 516, 518, 520, 522, and 524 are continuously updated as new PID values are received from the automotive controller. In the embodiment of
Mini gauge view 510 includes name 526, value 542, and units 558 and is associated with a PID. Name 526 indicates that mini gauge 510 displays the engine coolant temperature, which value 542 indicates is at 156.0, which units 558 indicates are in degrees Fahrenheit. Mini gauge view 510 is shaded in a green color to indicate that value 542 is within a desired range for the engine coolant temperature.
Mini gauge view 512 includes name 528, value 544, and units 560 and is associated with a PID. Name 528 indicates that mini gauge 512 displays the speed, which value 544 indicates is at 31.0, which units 560 indicates are in miles per hour. Mini gauge view 512 is not shaded green, which would indicate that value 544 is in a desired range, and is not shaded red, which would indicate that value 544 is in a warning range.
Mini gauge view 514 includes name 530, value 546, and units 562 and is associated with a PID. Name 530 indicates that mini gauge 514 displays the revolutions per minute (RPM) of the engine, which value 546 indicates is at 31.0, which units 562 indicates are in revolutions per minute. Mini gauge view 514 is not shaded green, which would indicate that value 546 is in a desired range, and is not shaded red, which would indicate that value 546 is in a warning range.
Mini gauge view 516 includes name 532, value 548, and units 564 and is associated with a PID. Name 532 indicates that mini gauge 516 displays the battery voltage of the engine, which value 548 indicates is at 2.00, which units 564 indicates are in Volts (V). Mini gauge view 516 is shaded red to indicate that value 548 is within a warning range for the battery voltage.
Mini gauge view 518 includes name 534, value 550, and units 566 and is associated with a PID. Name 534 indicates that mini gauge 518 displays the transmission temperature of the engine, which value 550 indicates is at 219.0, which units 566 indicates are in degrees Fahrenheit. Mini gauge view 518 is shaded red to indicate that value 550 is within a warning range for the transmission temperature.
Mini gauge view 520 includes name 536, value 552, and units 568 and is associated with a PID. Name 536 indicates that mini gauge 520 displays the throttle position sensor, which value 552 indicates is at 35, which units 568 indicates is a percentage value. Mini gauge view 520 is not shaded green, which would indicate that value 552 is in a desired range, and is not shaded red, which would indicate that value 552 is in a warning range.
Mini gauge view 522 includes name 538, value 554, and units 570 and is associated with a PID. Name 538 indicates that mini gauge 522 displays the calculated load on the engine, which value 554 indicates is at 35, which units 570 indicates is a percentage value. Mini gauge view 522 is not shaded green, which would indicate that value 554 is in a desired range, and is not shaded red, which would indicate that value 554 is in a warning range.
Mini gauge view 524 includes name 540, value 556, and units 572 and is associated with a PID. Name 540 indicates that mini gauge 524 displays the injector pressure of the engine, which value 556 indicates is at 25.0, which units 572 indicates is in thousand pounds per square inch (kPSI). Mini gauge view 524 is shaded green to indicate that value 556 is in a desired range.
Referring to
Upper row 608 includes mini gauges 510 and 512. Lower row 610 includes mini gauges 518 and 520.
Referring to
Referring to
Referring to
At
Mini gauge view 530 has been selected and selected gauge view 606 is shown on user interface 502.
At
At
Referring to
Settings view 804 includes name 808 and units 810 that identify the name and units of the PID that is associated with selected view 606. Settings view 804 includes user interface element 812 that, when selected, transitions user interface 502 from displaying settings view 804 (
On selected gauge view 606, name 816 and units 818 that identify the name and units of the PID that is associated with selected view 606. Value 820 indicates the current value of the PID associated with selected gauge view 606. Units 822 indicates the current value of the PID associated with selected gauge view 606. User interface element 824 indicates what gear is being reported by the automotive controller as the current gear of the vehicle.
Circular gauge view 814 includes warning section 824. In one embodiment, warning section 824 is shaded in red and indicates that the RPM level is too low.
Circular gauge view 814 includes desired section 826. In one embodiment, desired section 826 is shaded in green and indicates that the RPM level is in a desired operating range for the vehicle.
Referring to
Arc gauge view 904 includes desired section 908. In one embodiment, desired section 908 is shaded in green and indicates that PID values that are within desired section 908 are in a preferred range for one of maximum torque or horsepower.
Referring to
Bar gauge view 1004 includes desired section 1008. In one embodiment, desired section 1008 is shaded in green and indicates that PID values that are within desired section 1008 are in a preferred range for one of maximum torque or horsepower.
Referring to
Referring to
To adjust the settings for warning section 824, desired section 826, and warning section 1202, user interface element 806 is selected to display settings view 804 (
Parameter adjustment view 1206 includes user interface element 1208, user interface element 1210, name 1212, and units 1214
User interface element 1208 is a cancel button that, when selected, undoes changes that were made in parameter adjustment view 1206. After selecting user interface element 1208, user interface 502 returns to multiple gauge view 604 with settings view 804, as in
User interface element 1210 is a button that, when selected, accepts changes that were made in parameter adjustment view 1206. After selecting user interface element 1210, user interface 502 returns to multiple gauge view 604 with settings view 804, as in
Name 1212 and units 1214 identify the type and units of the PID information that is displayed on view 1206. In one embodiment, name 1212 is revolutions per minute (RPM) and units 1214 are RPM.
User interface element 1216 is a checkbox that indicates whether desired section 826 is shown on selected gauge view 606. The range of desired section 826 is controlled by the range between minimum desired threshold 1218 and maximum desired threshold 1220. When the PID value is between minimum desired threshold 1218 and maximum desired threshold 1220, then the PID value is in a desired or preferred range.
The display of warning section 824 and warning section 1202 are controlled by user interface element 1222. The range of the gap between warning section 824 and warning section 1202 is controlled by the range between minimum warning threshold 1224 and maximum warning threshold 1226. When the PID value is below minimum desired threshold 1224 or above maximum desired threshold 1226, then the PID value is in a warning range that could lead to engine fault, damage, or failure.
User interface element 1228 identifies whether the defuel settings are active. When the PID value is below minimum defuel threshold 1224 or above maximum defuel threshold 1226, then the PID value is in a defuel range where the fuel supply to the engine will reduced in order to protect the engine.
In one embodiment, the relationships shown below are maintained by the thresholds displayed on parameter adjustment view 1206.
minimum defuel threshold 1230≤minimum warning threshold 1224 Rel.1
minimum warning threshold 1224≤minimum desired threshold 1218 Rel.2
minimum desired threshold 1218≤maximum desired threshold 1220 Rel.3
maximum desired threshold 1220≤maximum warning threshold 1226 Rel.4
maximum warning threshold 1226≤maximum defuel threshold 1232 Rel.5
Referring to
When maximum desired threshold 1220 is dragged to the right, maximum warning threshold 1226 and maximum defuel threshold 1232 may also move to the right so that both maximum warning threshold 1226 and maximum defuel threshold 1232 remain greater than or equal to maximum desired threshold 1220.
Referring to
When maximum warning threshold 1226 is dragged to the left, maximum desired threshold 1220 may also move to the left so that maximum desired threshold 1220 remains less than or equal to maximum warning threshold 1226.
Referring to
When maximum warning threshold 1226 is dragged to the right, maximum defuel threshold 1232 may also move to the right so that maximum defuel threshold 1232 remains greater than or equal to maximum warning threshold 1226.
Referring to
When maximum defuel threshold 1232 is dragged to the left, maximum warning threshold 1226 and maximum desired threshold 1220 may also move to the left so that both maximum warning threshold 1226 and maximum desired threshold 1220 remain less than or equal to maximum defuel threshold 1232.
Referring to
Referring to
User interface element 1302 and user interface element 1304 allow for the selection between different units for the PID values associated with mini gauge 518. In one embodiment, mini gauge 518 is associated with transmission temperature and can be displayed in degrees Celsius (° C.) upon the selection of user interface element 1302 or in degrees Fahrenheit (° F.) upon the selection of user interface element 1304.
Referring to
Referring to
Large center gauge view 14204 includes name 14207, value 14208, units 14209, gear 14210, and circular gauge view 14211. Circular gauge view 14211 includes lower warning section 14212, desired section 14213, and upper warning section 14214. Large center gauge view 14204 indicates that the vehicle is in reverse and that the transmission temperature is 274.0° F. and is in a warning range that is above the desired range.
Top left gauge view 14203 includes name 14215, units 14216, value 14217, and arc gauge view 14218. Arc gauge view 14218 includes lower warning section 14219, desired section 14220, and upper warning section 14221. Top left gauge view 14203 indicates that the RPM of the motor is 4328 RPM, which is just above the desired range an in the upper warning range.
Bottom left gauge view 14204 includes name 14223, units 14224, value 14225, and arc gauge view 14226. Arc gauge view 14226 includes lower warning section 14227, desired section 14228, and upper warning section 14229. Bottom left gauge 14204 indicates that the battery voltage is 15.00 V and is in the upper warning range.
Top right gauge view 14205 includes name 14230, units 14231, value 14232, and arc gauge view 14233. Arc gauge view 14233 includes lower warning section 14234, desired section 14235, and upper section 14236. Top right gauge 14205 indicates that the engine coolant temperature is 240.0° F. and is in the upper warning section above the desired level.
Bottom right gauge view 14206 includes name 14237, units 14238, value 14239, and arc gauge view 14240. Arc gauge view 14240 includes warning section 14241 that indicates which values are too high. Bottom right gauge 14206 indicates that the speed of the vehicle is 299.0 MPH and is in the upper warning range.
The names, units, and values displayed on the gauges in large five gauge view 14101 are each shaded in red to indicate that each of the values of each of the gauges is in a warning section
When any one of gauge views 14202, 14203, 14204, 14205, and 14206 are selected from large five gauge view 14101, user interface 502 transitions from displaying large five gauge view 14101 to multiple gauge view 14301 and selected gauge view 14302, shown in
Referring to
Selected gauge view 14302 of
When user interface element 14309 of
Referring to
Referring to
Upon selection of small top right gauge view 14306 in
Referring to
Selecting button 1604 removes menu 1602 and brings back the most recent gauge view, which in
Selecting button 1606 removes menu 1602 and transitions user interface 502 to view 1616 of
Upon selecting user interface element 1618, user interface 502 transitions to view 1620 of
Upon selecting user interface element 1622, user interface 502 transitions to view 1626 of
Selecting user interface element 1624 brings up a different view (not shown) that allows for the management of ECU profiles. The management of ECU profiles includes: updating one or more parameters within a profile and deleting a profile from the client device.
Upon selecting user interface element 1628, user interface 502 transitions to view 1630 of
In one embodiment, view 1630 of user interface 502 is displayed on a client device that is used by a technician that is diagnosing the car to allow the technician to log into the server. Upon selection of the “Done” button on keyboard 1634 or user interface element 1636, the client device app will attempt to login to the system server and associated (or share) the vehicle with the technician's client device.
In an alternative embodiment, view 1630 of user interface 502 is displayed on a client device that is used by the owner of the vehicle that is being diagnosed. Upon selection of the “Done” button on keyboard 1634 or user interface element 1636, the client device app will send the technician's email address to the server, which will then allow the technician to log in and will then allow the vehicle information from the ODB2 port of the vehicle to be shared with a second client device that is operated by a technician. Sharing the vehicle information with the technician's client device allow the technician to diagnose the vehicle, even when the vehicle and the technician are remotely located.
Referring to
Referring to
Referring to
User interface element 1904 displays contact information including a name and an email address. When user interface element 1904 is selected, user interface 502 displays another view (not shown) that allows the user to view and manipulate the contact information, which also includes a phone number and a birthday. The contact information is used by the technician to contact the owner of the vehicle that the local device is connected to.
When selected, user interface element 1906 displays one or more videos that show how to use the client device app.
User interface element 1908 is for the development of the client device application itself. When user interface element 1908 selected, the client device app will send the log of information recorded by the client device app via an email to the contact identified in user interface element 1904.
User interface element 1910 displays the version of the client device app that is currently running.
User interface element 1912 displays the version of the firmware running on the local device that is currently running.
User interface element 1914 displays a receive signal strength indicator (RSSI) that indicates the strength of the wireless signal that is sent by the local device and received by the client device.
User interface element 1916 is an edit box that contains the internet protocol (IP) address that the client device will use to connect to the server running on the local device.
User interface element 1918 is a binary selector switch that, when enabled, allows the app to connect to the server running on the local device.
User interface element 1920 is a multiple position single selector switch that is used to select which protocol version that the client device app will use to communicate with the server running on the local device.
Referring to
Vehicles 20102 comprise vehicle records 20200 of
Referring to
Referring to
Referring to
Firmware 20402 is the firmware that runs on an automotive controller, such as automotive controller 114 of
Parameters 20408 are the parameters for the gauges displayed on a client device, such as client device 110 of
Warning max 20418 is a numerical value that indicates the beginning of an upper warning range. Warning min 20420 is a numerical value that indicates the end of a lower warning range. Continued operation of the vehicle with the values associated with the parameter above warning max 20418 or below warning min 20420 could lead to a breakdown of the engine.
Defuel max 20422 is a numerical value that indicates the threshold above which the vehicle will be defueled to prevent a breakdown. Defuel min 20424 is a numerical value that indicates the threshold below which the vehicle will be defueled to prevent a breakdown.
Gauge style 20426 identifies the style of the gauge that will be used to display the parameter values on the client device.
Available units 20428 is a list of units that can be used to display the values related to parameter 20408. Selected units 20430 identifies which units of available units 20428 will be used to display the values of parameter 20408.
Referring to
EMI 2106 is connected to memory 2116 and GPMI 2108 is connected to memory 2118. In one embodiment, memory 2118 is lower speed persistent memory that stores the programs and data run by application processor 2104 using memory 2116.
SSP 2110 is connected to Wi-Fi module 2120 to allow for wireless communication. In one embodiment, program instructions stored in one or more of memory 2116 and memory 2118 are executed by application processor 2104 so that local device 112 may function as an access point to which a client device can connect.
CAN0 interface 2112 is connected to a first CAN transceiver 2124 of a vehicle via the CAN0_HI/LOW link to connector 2122. CAN1 interface 2114 is connected to a second CAN transceiver 2126 through analog multiplexer 2128 and connector 2122. Analog multiplexer 2128 is connected to connecter 2122 through two CAN1_HI_B/LOW_B lines. Input/Output multiplexor control 2113 is also connected to analog multiplexer 2128. In one embodiment, connector 2122 is an RJ45 connector and an adapter (not shown) is connected between connector 2122 and the on-board diagnostics (OBD) port on the vehicle.
Although embodiments of the present disclosure have been described in detail, those skilled in the art should understand that they may make various changes, substitutions and alterations herein without departing from the spirit and scope of the present disclosure. Accordingly, all such changes, substitutions and alterations are intended to be included within the scope of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.
This application is claims priority to U.S. Provisional Application No. 62/201,462 filed Aug. 5, 2015, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6636790 | Lightner et al. | Oct 2003 | B1 |
6732031 | Lightner et al. | May 2004 | B1 |
6732032 | Banet et al. | May 2004 | B1 |
6738697 | Breed | May 2004 | B2 |
6745151 | Marko et al. | Jun 2004 | B2 |
6879894 | Lightner et al. | Apr 2005 | B1 |
6928348 | Lightner et al. | Aug 2005 | B1 |
7050897 | Breed et al. | May 2006 | B2 |
7082359 | Breed | Jul 2006 | B2 |
7162339 | Nguyen | Jan 2007 | B2 |
7225065 | Hunt et al. | May 2007 | B1 |
7228211 | Lowrey et al. | Jun 2007 | B1 |
7363129 | Barnicle et al. | Apr 2008 | B1 |
7421321 | Breed et al. | Sep 2008 | B2 |
7447574 | Washicko et al. | Nov 2008 | B1 |
7480551 | Lowrey et al. | Jan 2009 | B1 |
7554441 | Viegers et al. | Jun 2009 | B2 |
7620484 | Chen | Nov 2009 | B1 |
7629876 | Nagai et al. | Dec 2009 | B2 |
7630801 | Giles et al. | Dec 2009 | B2 |
7650210 | Breed | Jan 2010 | B2 |
7747365 | Lowrey et al. | Jun 2010 | B1 |
7792618 | Quigley et al. | Sep 2010 | B2 |
7904219 | Lowrey et al. | Mar 2011 | B1 |
7917253 | Inbarajan et al. | Mar 2011 | B2 |
8014789 | Breed | Sep 2011 | B2 |
8019501 | Breed | Sep 2011 | B2 |
8024084 | Breed | Sep 2011 | B2 |
8035508 | Breed | Oct 2011 | B2 |
8036788 | Breed | Oct 2011 | B2 |
8055403 | Lowrey et al. | Nov 2011 | B2 |
8108231 | Belanger et al. | Jan 2012 | B2 |
8406951 | Suganuma et al. | Mar 2013 | B2 |
8447459 | Lowrey et al. | May 2013 | B2 |
8527135 | Lowrey et al. | Sep 2013 | B2 |
8559937 | Ram et al. | Oct 2013 | B2 |
8781442 | Link, II | Jul 2014 | B1 |
8825271 | Chen | Sep 2014 | B2 |
8855621 | Chen | Oct 2014 | B2 |
8914187 | Wang et al. | Dec 2014 | B2 |
9002554 | Chen | Apr 2015 | B2 |
9014908 | Chen et al. | Apr 2015 | B2 |
9031710 | Barrett | May 2015 | B2 |
9050862 | Mouchet | Jun 2015 | B2 |
9083581 | Addepalli et al. | Jul 2015 | B1 |
9120357 | Deniau et al. | Sep 2015 | B2 |
9126483 | Aoki et al. | Sep 2015 | B2 |
9135759 | Baer et al. | Sep 2015 | B2 |
9141503 | Chen | Sep 2015 | B1 |
9142065 | Rude et al. | Sep 2015 | B2 |
9142066 | Chen et al. | Sep 2015 | B2 |
9224249 | Lowery et al. | Dec 2015 | B2 |
9224251 | Harata et al. | Dec 2015 | B2 |
9233655 | Barrett | Jan 2016 | B2 |
9248807 | Lee et al. | Feb 2016 | B2 |
9269169 | Morimoto et al. | Feb 2016 | B2 |
9280859 | Itatsu et al. | Mar 2016 | B2 |
9286264 | Johnson et al. | Mar 2016 | B2 |
9292984 | Kitahara et al. | Mar 2016 | B2 |
9324195 | Koenig et al. | Apr 2016 | B2 |
9342934 | Chen | May 2016 | B2 |
9418492 | Sinner et al. | Aug 2016 | B2 |
9483884 | Chen et al. | Nov 2016 | B2 |
9489544 | Naitou et al. | Nov 2016 | B2 |
9747254 | McQuade et al. | Aug 2017 | B2 |
20020007237 | Phung | Jan 2002 | A1 |
20030187556 | Suzuki | Oct 2003 | A1 |
20040111505 | Callahan et al. | Jun 2004 | A1 |
20050256614 | Habermas | Nov 2005 | A1 |
20060129691 | Coffee et al. | Jun 2006 | A1 |
20090178986 | Coglitore et al. | Jul 2009 | A1 |
20090318121 | Marumoto | Dec 2009 | A1 |
20100070107 | Berkobin | Mar 2010 | A1 |
20100292890 | Morris | Nov 2010 | A1 |
20120136827 | Wang et al. | May 2012 | A1 |
20120288016 | Ichikawa | Nov 2012 | A1 |
20130212659 | Maher et al. | Aug 2013 | A1 |
20130246135 | Wang | Sep 2013 | A1 |
20130261907 | McQuade et al. | Oct 2013 | A1 |
20130261914 | Ingram et al. | Oct 2013 | A1 |
20130268754 | Baltes | Oct 2013 | A1 |
20130275214 | Kote et al. | Oct 2013 | A1 |
20140081481 | Nishida | Mar 2014 | A1 |
20140100716 | Kawai et al. | Apr 2014 | A1 |
20140282470 | Buga | Sep 2014 | A1 |
20140294180 | Link, II | Oct 2014 | A1 |
20140379171 | Kim et al. | Dec 2014 | A1 |
20150007155 | Hoffman | Jan 2015 | A1 |
20150180840 | Jung | Jun 2015 | A1 |
20150298653 | Schwartz | Oct 2015 | A1 |
20150317594 | Reznik et al. | Nov 2015 | A1 |
20160189447 | Valenzuela | Jun 2016 | A1 |
20160203652 | Throop | Jul 2016 | A1 |
20160239937 | Kim et al. | Aug 2016 | A1 |
20160274160 | Lee et al. | Sep 2016 | A1 |
20160330284 | Holck | Nov 2016 | A1 |
20160347328 | Takehara et al. | Dec 2016 | A1 |
20160364225 | Moeller | Dec 2016 | A1 |
Number | Date | Country | |
---|---|---|---|
20170039059 A1 | Feb 2017 | US |
Number | Date | Country | |
---|---|---|---|
62201462 | Aug 2015 | US |