1.1Thumb lever speed command
Two magnetic position sensors measure the lever angle, and the controller checks that their readings agree. A calibration table maps lever travel to required vehicle speed, with zero speed at the released position.
Generated automatically. Not reviewed by a person. Not legal advice or an opinion.
Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.
Two magnetic position sensors measure the lever angle, and the controller checks that their readings agree. A calibration table maps lever travel to required vehicle speed, with zero speed at the released position.
The controller initializes the stored target to zero at a detected standstill. Each cycle, it limits the change toward required speed to the calibrated rise or fall rate multiplied by elapsed time. The torque loop separately compares measured speed with the resulting target.
The controller subtracts consecutive filtered wheel-speed estimates and divides the difference by the sample interval to estimate longitudinal acceleration. It multiplies that estimate by the next control interval to predict a speed change and adds the change to the target used by the torque loop.
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
The controller normalizes the pedal position signal to a percentage of travel and maps the first 3 percent to zero required speed. Above that threshold, it linearly interpolates between calibrated pedal positions and required speeds stored in a lookup table.
The controller selects an acceleration or deceleration limit from a table indexed by measured vehicle speed. It limits the difference between required and measured speed to that rate multiplied by a 100 millisecond look-ahead interval, then adds the limited difference to measured speed to form the target.
Every 20 milliseconds, the controller subtracts target speed from required speed and multiplies the difference by a dimensionless gain of 0.05. It clips the resulting speed variation between −0.04 and +0.03 metres per second per update.
Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.
Also illustrated is user interface (UI) block 13 which comprises such inputs to system controller 43 such as vehicle throttle position, push button shift selector (PBSS) for available drive range selection, brake effort and fast idle requests among others, from which an operator torque request (To_req) is determined.A · US 7,987,934 B2 · ¶ 37
For example, an acceleration operation, such as operation on an accelerator pedal, may be applied. In this case, in the step S201 in FIG. 3, it is determined whether or not an acceleration operation is being performed, and in the step S203, it is determined whether or not the acceleration operation is released.B · US 2021/0001846 A1 · ¶ 90
An exemplary calibration is depicted with reference to FIG. 6, which graphically depicts values for the engine speed ramp rate limit, Lim(ΔRPM/Δt), determined based upon a difference between the optimal engine speed, Ne_opt, and a limited engine speed, Ne_lim, based upon battery usage.A · US 7,987,934 B2 · ¶ 47
This speed profile is set based on an actual vehicle speed Vs at a timing t0 and a remaining distance Lr from a position of the vehicle at the timing t0 to the target point LE.B · US 2021/0001846 A1 · ¶ 75
However, an alternative acceleration G* set based on a difference between the limited vehicle speed and the actual vehicle speed Vs may be used as acceleration for the vehicle in the acceleration mode.B · US 2021/0001846 A1 · ¶ 94
When the engine speed command is determined, as described above, the system controller 43 determines required torque outputs from MA and MB to meet the operator torque request, taking into account the contribution of the engine to meet the operator torque request.A · US 7,987,934 B2 · ¶ 52
An empty cell means only that no passage was reproduced there.
A hybrid system application can underutilize the energy storage system, due to several factors including the size and power capacity of the primary power source, i.e., the internal combustion engine, and, the specific speed/load duty cycle of the vehicle.A · US 7,987,934 B2 · ¶ 8
In a hybrid system, it is desirable to make full use of the energy storage system in transient operating conditions, i.e., acceleration and decelerations, to reduce the fuel usage.A · US 7,987,934 B2 · ¶ 8
Therefore, if, even after the request is canceled, an operation amount is calculated using the target vehicle speed based on the course of the target vehicle speed set before the request occurs and then the driving device or the braking device is driven based on the operation amount, there is a risk that automatic traveling for moving the vehicle to the target point is disrupted.B · US 2021/0001846 A1 · ¶ 7
Further, by driving the driving device or the braking device based on the operation amount, it is possible to move the vehicle to the target point even when the request occurs during automatic traveling.B · US 2021/0001846 A1 · ¶ 8
patent.fyi, US 2026/0356206 A1, claim 1, first published 2026-11-19T22:03:07-05:00, https://patent.fyi/US20260356206/, SHA-256 ef2ca0a208b4f7e07070dedcd6e327478b553f6330c1f6484abdf27b4d322ef8