Methods and apparatus for suspension adjustment

Information

  • Patent Grant
  • 10036443
  • Patent Number
    10,036,443
  • Date Filed
    Monday, February 7, 2011
    13 years ago
  • Date Issued
    Tuesday, July 31, 2018
    5 years ago
Abstract
Methods and apparatus of a system for vehicles comprising a vehicle suspension, a sensor operable to measure an operational characteristic of the vehicle suspension, and a processor in communication with the sensor that is operable to suggest an operational setting of the vehicle suspension in response to an input from the sensor corresponding to the operational characteristic. A method for adjusting a suspension of a vehicle may comprise receiving suspension data with a processor, calculating a suspension setting suggestion with the processor, communicating the suspension setting suggestion to a user interface device, and adjusting the suspension based on the suspension setting suggestion.
Description
BACKGROUND

Field of the Invention


The invention generally relates to methods and apparatus of an integrated adjustment system for vehicles. Embodiments generally relate to methods and apparatus for use with vehicle suspension system. In particular, embodiments relate to a system for adjusting operational characteristics of a vehicle suspension system.


Description of the Related Art


Despite efforts to educate product managers, retailers, and end consumers on the importance of proper initial vehicle suspension set up, it is evident at event support and trail side encounters that many mountain bikes and motorcycles are ridden with improper suspension initial settings. An important initial setting is suspension “sag.” Suspension sag is the measured distance a shock absorber compresses while the rider, wearing intended riding gear, is seated on (for example) a bicycle or motorcycle (or four wheeled vehicle) in a riding position, versus a fully extended suspension position (sag also applies to ATVs, trucks, and other suspension equipped vehicles). Getting the sag correct sets the front end steering/handling geometry, puts the rear suspension at its intended linkage articulation for pedaling efficiency (if applicable) and bump absorption and provides some initial suspension compression to allow the wheels/suspension to react to negative terrain features (e.g. dips requiring suspension extension) without the entire vehicle “falling” into those features. Often, any attention that is paid to this initial sag setting is focused on the rear suspension, especially in motorcycle applications, but making sure that both the front and rear sag settings are correct is equally important.


Another important initial setting is the rebound damping setting for the rear and the front vehicle suspensions. Rebound damping dissipates stored system spring energy after a suspension compression event and results in a controlled rate of return of the suspension to a more extended condition. It is important for the suspension not to rebound too quickly. In the case of rear suspension, this can result in the rear of the vehicle kicking off the ground and pitching the rider forward after encountering a bump or sharp compression obstacle (“bucking”). In the case of front suspension, it can cause impact to the rider's hands as the front suspension kicks back directly towards the rider in the case of quick rebound. It is also important for the suspension not to rebound too slowly. This can result in the suspension not returning quickly enough to respond to the next bump in a series of bumps, ultimately causing the suspension to “ratchet” itself down into a compressed state. Such a “ratchet” sequence is commonly referred to as suspension “packing.” Packing can result in the suspension being overly stiff (due to retained compression) through the middle to the end of a series of bumps, causing the back of the vehicle kicking off the ground and pitching the rider forward in the case of the rear suspension and causing the suspension to get overly stiff and steering geometry to get steep and unstable in the case of the front suspension. Compression damping setting is similarly important.


Therefore, there is a need for methods and apparatus for assisting the operator of a vehicle to prepare and adjust one or more operating parameters of the vehicle for an optimum riding experience.


SUMMARY OF THE INVENTION

In one embodiment, a system for a vehicle may comprise a vehicle suspension; a sensor operable to measure an operational characteristic of the vehicle suspension; and a processor in communication with the sensor and operable to suggest an operational setting of the vehicle suspension in response to an input from the sensor corresponding to the operational characteristic.


In one embodiment, a system for a vehicle may comprise a sensor operable to measure an operational characteristic of the vehicle; a processor operable to receive data from the sensor corresponding to the operational characteristic; and a communication device operable to receive data from the processor and display information regarding the operational characteristic of the vehicle.


In one embodiment, a method for adjusting a suspension of a vehicle may comprise receiving suspension data with a processor; calculating a suspension setting suggestion with the processor; communicating the suspension setting suggestion to a user interface device; and adjusting the suspension based on the suspension setting suggestion.


In one embodiment, a suspension system may comprise a vehicle suspension; a sensor positioned to sense a feature of the suspension; a computer readable medium having an operative communication link with the sensor; a processor having an operative communication link with the computer readable medium; a transmitter having an operative communication link with the processor; and a graphical user interface having an operative communication link with the transmitter.





BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features can be understood in detail, a more particular description may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.



FIG. 1 illustrates a schematic side view of a vehicle according to one embodiment.



FIG. 2A illustrates a side view in cross section of a damper assembly according to one embodiment.



FIG. 2B illustrates an enlarged view of part of the damper assembly of FIG. 2A according to one embodiment.



FIG. 3 illustrates a schematic block diagram of components of one embodiment of an electric lock out apparatus.



FIG. 4 illustrates a block diagram of a system according to one embodiment.



FIG. 5 illustrates a block diagram of a controller of the system according to one embodiment.



FIG. 6 illustrates a block diagram of a program method for use with the system according to one embodiment.



FIGS. 7-11 illustrate examples of the program method steps according to one embodiment.



FIG. 12 illustrates a block diagram of a process of use with the system according to one embodiment.





DETAILED DESCRIPTION

Integrated damper/spring vehicle shock absorbers often include a damper body surrounded by a mechanical spring or constructed in conjunction with an air spring. The damper often consists of a piston and shaft telescopically mounted in a fluid filled cylinder. A mechanical spring may be a helically wound spring that surrounds the damper body. Various integrated shock absorber configurations are described in U.S. Pat. Nos. 5,044,614; 5,803,443; 5,553,836; and 7,293,764; each of which is herein incorporated, in its entirety, by reference.


FIGS. 1 and 2 of U.S. Pat. No. 5,044,614 show a damper body carrying a thread 42. A helical spring 18 surrounds the damper body. The compression in the helical spring 18 may be pre-set by means of a nut 48 and a lock nut 50. The nut 48 may be translated axially relative to the body (“tube”) 16 and thread 42 by rotating the nut 48 around the threaded sleeve 42. Rotation of the nut 48 in a given direction (e.g. clockwise as viewed from end 44 for a right hand thread 42) will cause the nut to move toward the retainer clip 26 thereby compressing spring 18 between the nut 48 and the retainer clip 26. Once the spring 18 is in a desired state of compression, lock nut 50 is rotated, using a wrench, up against nut 48 and tightened in a binding relation therewith.


Some shock absorbers utilize gas as a spring medium in place of, or in addition to, mechanical springs. Gas spring type shock absorbers, such as for example those having integral dampers, are described in U.S. Pat. Nos. 6,135,434; 6,360,857 and 6,311,962; each of which is herein incorporated, in its entirety, by reference. U.S. Pat. No. 6,360,857 shows a shock absorber having selectively adjustable damping characteristics. U.S. Pat. No. 7,163,222 which is incorporated herein, in its entirety, by reference, describes a gas sprung front shock absorber for a bicycle (a “fork”) having a selective “lock out” and adjustable “blow off” function.


The spring mechanism (gas or mechanical) of some shock absorbers is adjustable so that it can be preset to varying initial states of compression. In some instances the shock spring (gas or mechanical) may comprise different stages having varying spring rates thereby giving the overall shock absorber a compound spring rate varying through the stroke length. In that way the shock absorber can be adjusted to accommodate heavier or lighter carried weight, or greater or lesser anticipated impact loads. In vehicle applications including motorcycle and bicycle applications and particularly off-road applications, shock absorbers are pre-adjusted to account for varying terrain and anticipated speeds and jumps. Shocks are also adjusted according to certain rider preferences (e.g. soft—firm).


A type of integrated damper/spring shock absorber, having a gas spring, is shown in FIG. 28, for example, of U.S. Pat. No. 7,374,028 (“'028 patent”), which is incorporated herein, in its entirety, by reference. The shock absorber of FIG. 28 also includes an “adjustable intensifier assembly 510.” That intensifier or “reservoir” accepts damping fluid from chamber 170 as the fluid is displaced from that chamber by the incursion of rod 620 into chamber 170 during a compression stroke of the shock. The intensifier valve assembly regulates flow of damping fluid into and out of the reservoir, and an embodiment of the valve assembly is shown in FIG. 17 of the '028 patent.


It is desirable to “lock out” the suspension, thereby rendering it substantially rigid, on certain vehicles at certain times. Such lock out may be particularly desirable on bicycles to reduce or eliminate so called “pedal bob” or “chain squat” (the cyclic compression and extension of suspension caused by the cyclic tension of the drive chain and the cyclic motion of the pedals, cranks and power input generally). It is noteworthy that the valve assembly of FIG. 17 of the '028 patent may be replaced with any suitable valve assembly depending on the desired result. For example, when the valve is configured (as will be further described herein) with a selectable and correspondingly selected “lock out” (i.e. substantially complete valve closure) damping fluid is excluded from entering the reservoir and, the damping fluid being a relatively incompressible liquid, such exclusion prevents the volume of chamber 170 from being reduced and thereby prevents the shock absorber from compressing telescopically. Such “lock out” may be selectively provided via an external manual adjuster, such as for example knob 512 of FIG. 17, or it may be provided automatically in response to some predetermined and sensed vehicle operation condition (e.g. smooth terrain). Alternatively, a “lock out” condition may be the default mode for the suspension whereby the suspension becomes active only upon some predetermined and sensed vehicle operation condition (e.g. rough terrain) wherein a sensor senses the condition and opens the “lock out” so that the suspension may operate for a prescribed period of time or terrain input.


Although described herein with respect to a bicycle suspension system, the embodiments illustrated in FIGS. 1-11 herein may be used with any type of suspended vehicle, as well as other types of suspension or damping systems.


Referring to FIG. 1 herein, a vehicle, such as a bicycle, generally identified by reference numeral 100 comprises a frame 40 and front forks 80. In this embodiment the frame 40 has a suspension system comprising a swing arm assembly 10 that, in use, is able to move relative to the rest of the frame; this movement is permitted by, inter alia, a rear shock absorber and/or damping assembly 25. The front forks 80 also provide a suspension function via a damping assembly in at least one fork leg; as such the bicycle 100 is a full suspension bicycle (such as an ATB or mountain bike), although the embodiments described herein are not limited to use on full suspension bicycles. In particular, the term “suspension system” is intended to include vehicles having front suspension or rear suspension only, or both and other systems wherein motion damping is included (such as for example vehicle steering dampeners or machine part motion dampeners).


In one embodiment, a sensor 5 may be positioned proximate a rear axle 15 of the bicycle 100 for sensing changes in terrain. As shown in FIG. 1, the sensor 5 is mounted on swing arm assembly 10 proximate the rear axle 15 of the bicycle 100. In one embodiment the angular orientation of a sensor 5 sensing axis is movable through a range or angle 20 (and is shown in each of two positions of many possible positions), thereby allowing alteration of a force component sensed by the sensor in relation to a force (vector) input into the rear swing arm 10. It is understood that the sensor 5 may be moved or mounted in any suitable configuration and allowing for any suitable range of adjustment as may be desirable. It is understood that the sensor may include one, two, three or more sensing axis'. That is useful for adjusting the sensitivity of the sensor 5 to various anticipated terrain and bicycle speed conditions. The bicycle speed affects the vector direction of a force input to the bicycle wheel for constant amplitude terrain 45 disparity 55 or “bump/dip.” Varying size bumps and dips also affect the vector input angle to the wheel for constant bicycle speed. The movement of the swing arm is however limited to a mechanically determined trajectory. In one embodiment, a sensor 5b (also illustrated in FIG. 2A) may be coupled to the rear suspension, such as shock absorber and/or damper assembly 25, for measuring the operational characteristics of the rear suspension. In one embodiment, a sensor 5c may be coupled to the front suspension, such as front forks 80, for measuring the operational characteristics of the front suspension. The operational characteristics may include at least one of position, velocity, acceleration, stroke, sag, compression, rebound, pressure, and temperature of the vehicle suspension.


The sensor 5 (and sensors 5b, 5c, 35, 65 and a pedal force sensor (not shown)) may be any suitable force or acceleration transducer (e.g. strain gage, wheatstone bridge, accelerometer, hydraulic cylinder, interferometer based, optical, thermal, acoustic or any suitable combination thereof). The sensor 5 may utilize solid state electronics, electro-mechanical principles, or any other suitable mechanisms. In one embodiment the sensor 5 comprises a single axis self powered accelerometer, such as for example ENDEVCO Model 2229C. The 2229C is a comparatively small device with overall dimensions of about 15 mm height by 10 mm diameter, and weighs about 4.9 g. Its power is self-generated and therefore the total power requirements for the bicycle 100 are reduced; this is an important advantage, at least for some types of bicycle, where overall weight is a concern. In one embodiment, the single axis accelerometer comprises the ENDEVCO 12M1A, which is of the surface-mount type. The 12M1A is a single axis accelerometer comprising a bimorph sending element which operates in the bender mode. This accelerometer is particularly small and light, measuring about 4.5 mm by 3.8 mm by 0.85 mm, and weighs about 0.12 g. In other embodiments, the sensor 5 may be a tri-axial accelerometer such as the ENDEVCO 67-100. This device has overall dimensions of about 23 mm length and 15 mm width, and weighs about 14 g. Other sensors known in the art may be used with the embodiments described herein.


In one embodiment, the sensor 5 may be attached to the swing arm 10 directly, to any link thereof, to an intermediate mounting member or to any other portion or portions of the bicycle 100 as may be useful for purposes disclosed herein. In one embodiment the sensor 5 is fixed to an unsprung portion of the bicycle 100, such as for example the swing arm 10, and another sensor 35 (such as an accelerometer as described above) is fixed to a sprung portion of the bicycle 100, such as for example the frame 40. Data from each sensor can, by a processor, be overlayed on a common time datum and suspension damping and/or spring effectiveness can be evaluated by comparing the data from the sensors on either “side” of the suspension unit. Sensors may be integrated with the vehicle structure and data processing system as described in U.S. Pat. Nos. 6,863,291; 4,773,671; 4,984,819; 5,390,949; 5,105,918; 6,427,812; 6,244,398; 5,027,303 and 6,935,157; each of which is herein incorporated, in its entirety, by reference. Sensors and valve actuators (e.g. electric solenoid or linear motor type—note that a rotary motor may also be used with a rotary actuated valve) may be integrated herein utilizing principles outlined in SP-861-Vehicle Dynamics and Electronic Controlled Suspensions SAE Technical Paper Series no. 910661 by Shiozaki et al. for the International Congress and Exposition, Detroit, Mich., Feb. 25-Mar. 1, 1991 which paper is incorporated herein, in its entirety, by reference. Further, sensors and valves, or principles, of patents and other documents incorporated herein by reference, may be integrated into embodiments hereof, individually or in combination, as disclosed herein.


In one embodiment the shock absorber 25 is operatively mounted between an unsprung portion of the bicycle 100, such as the swing arm 10 and rear axle 15, and a sprung portion of the bicycle 100 such as the frame 40. A representative example embodiment of the shock absorber 25 derives from a modification, as disclosed herein, of the shock absorber shown in FIG. 28 of, and elsewhere in, U.S. Pat. No. 7,374,028 (the “'028” patent) which is incorporated herein by reference.


Referring to FIG. 2A herein, an intensifier assembly 510 is shown in conjunction with a damper assembly 630. In one embodiment, the damper assembly 630 is disclosed in FIG. 28 of the '028 patent and includes similar reference numerals. FIG. 2B shows an embodiment of a valve assembly 511, such as an intensifier valve, for use with the embodiments disclosed herein. In one embodiment, the valve assembly 511 of FIG. 2B replaces or may be used with the “adjustable intensifier assembly” 510, as shown in FIGS. 16, 17, 28 and elsewhere in the '028 patent. The valve assembly 511 is operable in response to electric current and is capable of being modulated or throttled for selective full opening, closing and intermediate opening or “throttle” positions. The valve assembly 511 comprises a valve portion 110 and an actuator portion 120. The valve portion 110 may include a cylinder 112 with one or more variable orifices 114 and a member (e.g. piston) 116 that moves within the cylinder 112 to control the opening of the orifice(s) 114. The valve assembly 511 is in a closed position when the piston 116 is covering the orifice(s) 114. The valve assembly 511 is in an open position when the piston 116 moves away from the orifice(s) 114 such that at least a portion of the orifice(s) 114 is opened. In the open position, fluid may flow into the valve portion 110 and may flow out of the valve portion 110. The position of the piston 116 relative to the orifice(s) 114 varies the orifice opening and the flow through the valve portion 110. The valve assembly 511 may thus provide an output pressure in response to an input flow.


The valve portion 110 may also include a spring 118 that applies a force against the piston 116 to bias the piston 116 toward the closed position. Fluid pressure against the piston 116 may result in a force that exceeds the spring force causing the piston 116 to move and open the orifice(s) 114.


The actuator portion 120 may also apply a force to the piston 116. The actuator portion 120 may advantageously be back drivable to permit the pressure term to push open the valve, for example, during the onset of a high shock event. One embodiment of the actuator portion 120 is a voice coil type linear actuator including a voice coil 122, a magnet 124, and a back iron 126. The back iron 126 is coupled to the piston 116 such that linear movement of the back iron 126 causes linear movement of the piston 116.


The actuator portion 120 may be controlled using a command such as a voltage command, for example, provided by drive electronics. A voltage command or signal to the actuator portion 120 causes current to flow through the coil 122, creating a magnetic field that applies a force to the magnet 124 and back iron 126. Different voltage commands may thus correspond to different amounts of force applied to the piston 116 in the valve assembly 511. In one embodiment the signals and actuator are configured to move the valve completely between a full open (“unlocked”) and a full closed position (“locked”) thereby allowing the damper to move or substantially locking it, i.e. adjusting the damping rate of the damping assembly 630 between minimum and maximum respectively.


Although one exemplary valve is shown, those skilled in the art will recognize that other types of valves may be used. Although the exemplary actuator 120 is a voice coil type linear actuator, those skilled in the art will recognize that other types of actuator technologies may be used. For example, the sensors, switches, controllers, actuators and other operative elements hereof may comprise optical circuitry and as such the power source may comprises an optical (or other electromagnetic) generator such as a “LASER” and wiring and circuits used herein may comprises fiber optic and optic circuitry including Bragg grating technology and other suitable “electrical equivalents.” The elements hereof may be operable in whole or in part based on sonic wave or microwave transmission and suitable waveguide technology may be employed. An operation of an intensifier valve that may be used with the embodiments described herein is disclosed in U.S. Pat. No. 7,299,112 which is incorporated herein by reference in its entirety.


It should be noted that 122 and 124 are interchangeable such that the voice coil may be either 122 or 124 and the magnet may be the other of 122 and 124 respectively. The voice coil 122 or 124 responds to input current from the power circuit (e.g. position control circuit or other suitable electrical input as described herein). As such input wiring is desirable. The input wiring and terminals for the 122 version of the voice coil is shown at 150. The input wiring and terminals for the 124 version of the voice coil is shown at 151 and includes windings 152 to accommodate extension and contraction of the throughput wires 152 during operation of the valve assembly 511.


The valve assembly 511 is shown in a closed or downward 156, position. As such, piston 116 fully obstructs orifices 114 thereby preventing fluid from flowing from damper assembly 630, through channel 636, into upper chamber 153, through orifice 114, through valve outlet 157 and into floating piston compensator chamber 154. When current of an appropriate magnitude is applied to the voice coil 122 or 124, the magnet electromagnet combination of 122 and 124 causes the back iron 126, and correspondingly the valve piston 116, to move upward 155 in an amount proportional to the voice coil input. Such upward 155 movement is against spring 118, which biases the valve piston 116 downward 156 (i.e. toward closed), and therefore when the voice coil input balances with the force of spring 118, movement of the piston 116 will stop and the valve assembly 511 will be correspondingly throttled.


In operation, the sensor 5 (and/or sensors 5b, 5c, 35) puts out a voltage change corresponding to an input force (for example the outputs from both sensors 5, 5b, 5c, 35 may be reconciled in a controller or processor 65 (described in greater detail below), such as a microprocessor, having an algorithm for weighting their respective inputs and generating a resulting singular command or signal based on a predetermined logic). In one embodiment the sensor 5 senses an input force along the prescribed range or axis 20. A bump in the terrain 45 typically exerts a force 55 on a tire/wheel 60 of the bicycle 100. The angle of the resolved force 55 relative to the tire/wheel 60 is typically normal (substantially) to the tire/wheel 60 at the point of impact. That force 55 then imparts a component of the impact 55 to the axle 15 as dictated by the trajectory of the swing arm linkage 10. That component can be sensed by the sensor 5 at a magnitude corresponding to the orientation of the sensor range or angle 20. The sensor axis orientation can be adjusted to make the sensor 5 more or less sensitive (by imparting more or less of the impact 55 to the sensor range or axis 20) to bumps and dips in the terrain.


It is envisaged that there are various ways the remote lock/unlock function of the rear shock absorber 25 and/or front shock absorber 80 may be provided on the bicycle 100. In one embodiment, remote lock/unlock may be entirely automatically controlled by a controller 65 in response to the input from the sensors 5, 5b, 5c and/or 35 when the bicycle 100 is in use. Optionally, the user may be able to override and/or adjust this automatic control using a device 50. In one embodiment, the remote lock/unlock of the rear shock absorber 25 and/or front shock absorber 80 may be entirely controlled at the user's discretion using the device 50; in such an embodiment the sensors 5, 5b, 5c and/or 35 need not be provided on the bicycle 100 and the user locks and unlocks the suspension system according to his or her own preferences at the time.


Referring to FIG. 3 herein, when the sensor 5 puts out a voltage corresponding to a bump (and/or optionally a dip) that voltage is transmitted to a controller 65 (e.g. comprising a memory and a processor/microprocessor, or an ASIC). In one embodiment the shock absorber 25, including damper assembly 630, intensifier assembly 510, and/or valve assembly 511 (shown in FIGS. 1, 2A, and 2B) is responsive to signals and power transmitted from the controller or processor 65. The valve assembly 511 is default in the closed position and will throttle open corresponding to power input received at terminals 150. The processor or controller 65 compares the output voltage of sensor 5 to a preset (by means of threshold adjuster 75 such as, for example, a potentiometer) value and if that value is exceeded, the controller routes a predetermined amount of power from the power source 70 (e.g. suitable battery, capacitor, photovoltaic generator or other suitable mechanism or combination thereof) to the valve assembly 511. Optionally the controller 65 compares the output voltage to a magnitude comparator value over time (the time constant is also user adjustable). In that option the magnitude of the output voltage must remain above a given threshold value for a predetermined amount of time before the controller 65 will route power to the valve assembly 511. When the output voltage falls below the threshold value, power to the valve assembly 511 is shut off. Optionally, the controller 65 may taper power off over a selectable period of time as part of the shut off function. Optionally, multiple threshold values may be set in the controller 65. At each threshold value may direct a differing amount of power from the source 70 to the valve assembly 511. If, for example, only a lower threshold is met, the controller 65 may direct an amount of power only corresponding to a partial opening of the valve assembly 511. If a higher threshold is met the directed amount of power may correspond to a full open valve assembly 511. Multiple time constants may also (independently or additionally) be preset for different corresponding valve assembly 511 function levels. Optionally the valve assembly 511 may be of a type described in U.S. Pat. No. 6,073,736. Optionally, the valve control/power circuit may be configured and operable in a manner such as disclosed in U.S. Pat. Nos. 5,971,116 and 6,073,736 each of which is herein incorporated, in its entirety, by reference, or by any other means or method disclosed herein or any suitable combinations or portions thereof.


In one embodiment, a device 50 is provided in a location convenient for user manipulation during vehicle operation. In one embodiment, the device 50 may be a manual lock out (or unlock or both) switch. In one embodiment, the device 50 is provided on the handlebar of the bicycle 100 (or other part of the bicycle 100 that is reachable during use). Optionally the device 50 includes the functions of locking and unlocking valve assembly 511, adjusting threshold(s) 75 and adjusting time constant(s) all as shown in FIG. 3. Thus at its simplest, the device 50, such as a manually operated button, trigger or lever, allows the user to remotely lock/unlock the rear shock absorber 25 (and/or the front shock 80) at will. The device 50 may cause both front and rear shocks to lock/unlock together, or it may permit the user to lock/unlock each shock independently.


In one embodiment, the device 50 comprises a lever that is shiftable by the user of the vehicle 100. The lever may shift between first and second positions (each corresponding to a “lock” and “unlock” command to the damping assembly). Alternatively, the lever may move away from a first position and then return to that position having switched between locked and unlocked during the movement; such movement may be similar to the way indexed (e.g. ratcheted) gear shifters operate.


In one embodiment, the device 50 comprises a digital user interface device provided with buttons and/or a touch screen enabling the user to lock and unlock the damping assembly at will. The device 50 may comprise a suitable GPS unit, bicycle computer, heart rate monitor, smart phone, personal computer, cloud connected computer and may further comprise connectivity to the internet. The device 50 may send and receive data via cell phone bands, satellite bands or other suitable electromagnetic frequencies to connect with other computer networks for the sending and or receiving of data wherein the data may be received by and transformed by an outside computing machine and transmitted to the device 50 in an altered form or in a new form corresponding to the result of the outside machine transformation. The functionality of the device 50 may be incorporated into performance recording devices and/or digital user interfaces, such as, but not limited to, the GARMIN EDGE series of devices, and smart phones such as the Apple iPhone or Motorola with Droid.


In one embodiment, the device 50 may provide additional functionality to enable to user to remotely control the rear and/or front shock more finely. For example, the device 50 may permit the user to remotely set a shock (i.e. the amount that the valve assembly 511 is open/closed) at one of a number of predefined (e.g. indexed) positions in transition between locked and unlocked, or may permit the user set the shock at substantially any (“infinite” or “continuous” adjustment) position between those two limits. For example the position of the valve assembly 511 may correspond with a position of an indicator on the device 50. The indicator may be a visual indication (e.g. digital or graphical indicator), or a physical indicator (e.g. position of a lever between two limit positions).


The default or pre-biased position of the valve assembly 511 may be either open or closed, or somewhere in between. In one embodiment, the valve assembly 511 is default set open. In one embodiment, the actuator portion 120 moves the valve portion 110 in one direction from its default or bias and it returns to bias by means of the spring 118 or other suitable biasing mechanism when the actuator portion 120 ceases to function. Controller or processor 65 monitors sensor 5 and/or 35 and after a time period of input corresponding to below threshold sensor output the controller 65 directs power to valve assembly 511 sufficient to close the valve portion 110 (the electromagnetic or voice coil being reversed by power input and the spring 118 set as a tensile spring to hold the valve portion 110 open by default). Optionally (or independently and absent the sensors 5 and 35) the device 50 communicates a signal to the controller 65 and the controller 65 correspondingly directs power from source 70 to the valve assembly 511 thereby closing the valve assembly 511 completely or partially as desired. Optionally, a rider of the bicycle 100 may manipulate the device 50 to cause the valve assembly 511 to close, to open, to throttle at intermediate positions, as desired while operating the bicycle 100 on varying terrain (to eliminate pedal bob or maximize ride comfort or traction).


Some or all of components of embodiments herein including sensors and switches, processor or controller 65, shock absorber 25, intensifier assembly 510, and/or valve assembly 511 at terminals 150 or 151, may be interconnected or connected by wire 30, wireless, WAN, LAN, Bluetooth, Wi-Fi, ANT (i.e. GARMIN low power usage protocol), or any suitable power or signal transmitting mechanism. It is particularly desirable in certain embodiments that the device 50 communicate wirelessly with the controller 65. An output electric signal from the device 50 is transmitted to the controller 65. The controller 65 responds to that signal by adjusting the damping rate of the damping assembly 630 to lock or unlock, and/or set at some intermediate level according to the output electric signal.


In one embodiment, the shock absorber 25, including damper assembly 630, intensifier assembly 510, and/or valve assembly 511, further operates with mechanically variable damping and/or spring features when the valve assembly 511 is open or partially open. In one embodiment, the valve assembly 511 is positioned in series with the “adjustable intensifier assembly” 510 valve of U.S. Pat. No. 7,374,028 so that fluid must traverse both valves between the damper channel 636 and the compensator chamber 154. In operation, the damping function of the shock absorber 25 is consistent with the operation of the intensifier assembly 510 when the valve assembly 511 is open. Other mechanical shock absorber functions may also be integrated with the present disclosure such that the shock absorber 25 is highly versatile and functional when valve assembly 511 is open. Such features are disclosed for example in U.S. Provisional Patent Application Ser. No. 61/157,541, and any individual or combination of features disclosed therein is suitable for combination with embodiments of this present disclosure. In one embodiment of operation, it is desirable to have the features of a highly versatile yet robust mechanically adjustable shock absorber in combination with the electric lock out presently disclosed.


In one embodiment, the controller 65 takes a derivative (differentiation) of the acceleration to determine the rate of change of acceleration for forecasting and implementing adjustment of valve assembly 511 (rebound issue is a big deal) or for determining a data rate or density required to adequately represent current suspension behavior (to for example to cull high rate raw data into more manageable yet representative data streams or sets). For example, if a bump is encountered followed immediately by a dip, it may be desirable to have the rebound of the tire into the dip (terrain following for traction advantage) occur very rapidly. If the valve assembly 511 were opened to an intermediate state as determined by the controller 65, for the bump an immediately following large magnitude reversal of the derivative of the acceleration (as input from the sensor 5) may indicate that the controller 65 direct the power source to full opening of the valve assembly 511 to allow maximum rebound velocity. The controller 65 may also compare input from sensors 5 and 35 to determine optimum setting position for the valve assembly 511. For example, if input from sensor 35 is relatively low in magnitude the controller 65 may open the valve assembly 511 gradually until some increase in sensor 35 is noted and then close the valve assembly 511 back slightly from that. In one embodiment, if input from sensor 35 is consistent in frequency with input from a pedal force sensor (e.g. U.S. Pat. No. 5,027,303 which is incorporated herein by reference), the controller 65 may direct a closure of the valve assembly 511 until such synchronization is eliminated or reduced.


It is noted that embodiments herein of shock absorber 25 and related systems are equally applicable to the vehicle, such as bicycle 100, front forks 80. Further, it is contemplated that the bicycle 100 may include both shock absorber 25 and forks 80, both of which having some or all of the features disclosed herein.



FIG. 4 illustrates a system 1000 according to one embodiment. The system 1000 may include a vehicle 100 (such as vehicle 100 described above), one or more sensors 200 (such as sensors 5, 5b, 5c, 35 described above), a processor or controller 300 (such as processor or controller 65 described above), a computer system 400, and a communication device 500 (such as device 50 described above). An operator or user 600, such as a rider of the vehicle 100, may use the system 1000 according to the embodiments described herein. In one embodiment the vehicle 100, such as a bicycle, is equipped with the processor 300, such as a suspension setup microcomputer device comprising at least one memory, program having an algorithm and computer for executing the program, which captures data in the memory from the sensors 200 that are coupled to one or more vehicle 100 suspension components (such as a fork and rear shock on a bicycle or motorcycle). The data may include suspension component relative position data (e.g. inches of compression or full extension or full compression or any suitable combination of such data) and/or other operational characteristics/features of the vehicle 100 that are measured by the sensors 200. The data may be communicated to the controller 300 via wired and/or wireless communication, and the controller 300 may process the data and communicate the data via for example an industry standard, low power wireless protocol to the communication device 500, such as an external 3rd party device with a display, to instruct the user 600 on what adjustments to make to improve the vehicle 100 suspension setup and/or to describe the current performance of the vehicle 100 suspension system. In one embodiment, the user 600 may use the computer system 400 and/or the communication device 500 to adjust one or more components of the vehicle 100, automatically, manually and/or remotely, wired and/or wirelessly, directly, manually and/or indirectly (such as via the controller 300) during and/or after operation of the vehicle 100.


In one embodiment, the sensor 200 is mounted to a vehicle suspension component, such as front forks 80 of bicycle 100 illustrated in FIG. 1. The sensor 200 may be coupled to the vehicle 100 and may be operable to measure an operational characteristic of a vehicle component, such as the vehicle suspension. In one embodiment, the sensor 200 may be directly coupled to the vehicle component for direct measurement of that component's operational characteristics. In one embodiment, the sensor 200 may be coupled to a portion of the vehicle 100 apart from the vehicle component and may be operable for indirect measurement of that component's operational characteristics. In one embodiment, the sensor 200 may be positioned at any location relative to the vehicle 100 and may be operable to measure an operational characteristic of the vehicle 100 directly or indirectly (e.g. inferred from the position of a vehicle component, such as the position of the vehicle suspension linkage, or the sprung versus un-sprung portion of the vehicle component for example. The sensor 200 is used to determine the position, velocity, and/or acceleration of the suspension component (raw sensor data is used to calculate such parameters within the processor). The sensor 200 may be a linear potentiometer, a string potentiometer, a contact or non-contact membrane potentiometer, a rotary potentiometer (such as if used on a linkage fork or a rear suspension linkage), an accelerometer or accelerometers, a 3D global position sensor (“GPS”), a pressure sensor (for measuring the air spring or coil spring compression), and/or other type of sensor from which a damper assembly position of the vehicle 100 can be determined.


These sensors 200 may communicate either wired or wirelessly to the controller 300, such as a microcomputer device, to communicate the sag position or any other suitable data. Due to potentially high sampling rate requirements associated with suspension movement and power considerations (e.g. economy), it is preferable at this time to communicate from the vehicle suspension sensors 200 to the controller 300 via one or more wires (which can for example carry more data than wireless), including electrical and fiber optical wires, for example. It is expected that in the future wireless protocols and battery life may be such that wireless high speed communication (although possible today) between the sensors 200 and the controller 300 will become more practical and is therefore contemplated hereby. In one embodiment, the data sampling rate is about 500 Hz to allow sufficient sampling and resolution of the vehicle suspension movement during operation.


In one embodiment, the controller 300 is relatively small (about 2″×3-3.5″×0.5-0.625″) and lightweight so as to not negatively impact the user 600 of the vehicle 100. In one embodiment the controller 300 need not literally “control” anything but rather may cull data and send the result to the device 50 or 500. In one embodiment, the controller 300 may contain one or more of the following major components: a low power microprocessor, a wireless communication chip (such as ANT+, Bluetooth, and/or Wi-Fi 802.11 n), a battery, and flash memory. The controller 300 may also have other sensors on board such as a GPS, a compass, an accelerometer, an altimeter, and/or an air temperature sensor. The controller 300 may also have one or more external features such as multi-color LED's to communicate basic state of operation and battery charge to the user 600, and buttons to toggle power and start/stop data logging. The controller 300 may also have an external mini USB connector to connect to a computer, such as the computer system 400, for uploading of data and charging the battery. The controller 300 may also have external connectors to connect to any wired sensors 200.


In one embodiment, the controller 300 (such as a computer or a microcomputer) may record and evaluate the typically high frequency vehicle 100 suspension data in real time. The controller 300 may analyze parameters like sag (static ride height), rebound and compression speed, top out and bottom out events. Then, after analysis is complete, the controller 300 may communicate to the communication device 500, such as an external 3rd party user interface device (e.g. 50 or 500), via an industry-standard, lower power wireless communication protocol in simple and small data packets at about 1 Hz to about 10 Hz. Because there are many user interface devices that already have ANT+ and/or Bluetooth built in (e.g. Garmin GPS, power meters, iPhone and iPod, etc.) it is contemplated that certain embodiments hereof will be so compatible. These interface devices generally have large displays with a developed GUI and user navigation method via any or all of buttons, joystick, touch screen, etc. The built in wireless capabilities are ideal for low density data transmittal, but are not well suited for high speed data acquisition (because low power wireless data rates are generally limited). By leveraging the existing device (e.g. 500) display and GUI capabilities, the applicability of the system is increased. In one embodiment the device 500 is programmed with a data template or templates suitable for filling with data and/or calculations/suggestions from the controller 300. In one embodiment the device 500 is programmed with input templates for facilitating user input of suspension model, user weight, vehicle type, etc. as may be useful in aiding the controller to look up corresponding parameters. The controller 300 will communicate to the communication device 500 selected data or calculations (e.g. graphical, tabular, textual or other suitable format) to display to the user 600, such as suggestions for adjusting spring preload, air spring pressure (to adjust sag), rebound damping setting, compression damping setting, bottom out damper setting, etc. Communication will also work in reverse to allow the user 600 to enter data, such as model of suspension, rider weight, etc., in the communication device 500 which will relay the information to the controller 300. From such model information the controller 300 will look up model relevant parameters and use those to aid in calculating suggestions.


In one embodiment, the controller 300 functions as a data receiver, processor, memory and data filter. The controller 300 receives high frequency (high sampling rate) data from the suspension sensor(s) 200. Because current user interface devices, particularly those using wireless protocol, may not be capable of high enough data rates to directly monitor the suspension sensors 200, the controller may act as a high data rate intermediary between the suspension sensors 200 and the communication device 500. In one embodiment, the controller 300 is configured to prompt and accept high sampling rate data from the suspension sensors 200. The controller 300 then stores the data and processes selected data at selected intervals for transmission to a user interface of the communication device 500, for example. In other words the controller 300 pares the effective data rate and makes that pared data transmission to the user interface in real time. Additionally, the controller 300 stores all un-transmitted data for later analysis if desired. The controller 300 can later be plugged into the computer system 400, such as a home computing device or laptop via a USB pigtail or dongle device. The controller 300 may also preprocess data and generate user friendly viewing formats for transmission to the user interface of the communication device 500. The controller 300 may calculate data trends of other useful data derivatives for periodic “real time” (effectively real time although not exact) display on the user interface of the communication device 500.


In one embodiment, each vehicle 100 suspension component is equipped with a position sensor 200 for indicating the magnitude (or state) of extension or compression existing in the vehicle 100 suspension at any given moment. As the suspension is used over terrain, such a sensor 200 will generate a tremendous amount of data. Relatively high sampling rates are needed to capture meaningful information in devices operating at such high frequencies. In one embodiment, a suitable telescopic tube of the vehicle 100 suspension is equipped or fitted with two piezoelectric sensors 200. In one embodiment, one of the piezoelectric sensors 200 is a high frequency exciter which is configured on the tube such that it (substantially) continuously induces impacts to a wall of the tube. In lay terms, the sensor 200 thumps or pings the tube wall on a continual basis. In one embodiment, the second piezoelectric sensor 200 is an accelerometer fixed or configured with the tube wall so as to monitor vibration of the tube wall. In one embodiment, the exciter and the monitor are vibration ally isolated so as not to directly influence each other. In one embodiment, the frequency of the exciter is intentionally set well outside any resonant mode of the suspension tube as it travels through its operational suspension stroke. In one embodiment, a sensing frequency of the monitor is selected to coincide (substantially) with at least one resonant mode range of the tube as it travels through its operational stroke.


In one embodiment, the aforementioned exciter and monitor are calibrated, in conjunction with the controller 300, so that values for resonant frequencies (in a selected mode or modes) of the suspension tube (or other suitable and variably “ringing” suspension component) are correlated with axial extension/compression of the suspension containing or including the tube. Such correlation data is stored with the controller 300 for use in real time calculation of axial suspension position based on real time input from the suspension resonant frequency monitor. The tube will tend to resonate regardless of the exciter frequency so by monitoring the change in resonant frequency or tube “ringing”, with the monitor, the axial position of the suspension can be derived within the controller 300.


In one embodiment, the exciter and monitor act on and measure resonance with a cavity of the vehicle 100 suspension wherein cavity resonance versus axial suspension displacement is calibrated and correlated for use in the controller 300. In one embodiment, magnetic flux leakage of a suspension component, or magnetic imposition of current in a surrounding conductive structure, is correlated with axial suspension displacement. In one embodiment, optics are used (e.g. Doppler effect). In one embodiment, a magnet is affixed to one portion of the suspension and a conductor is affixed to a relatively movable portion of the suspension so that when the suspension moves axially the relative movement between the magnet and the conductor generates a changing current of flux in the arrangement (and that can be correlated with axial movement). In one embodiment, sonic or ultrasonic waves are used to excite a portion of the suspension and the changing reflective sonic signals are monitored to determine axial disposition of the suspension.


In one embodiment, vehicle 100 suspension components include scan compatible identification codes specifying at least model type and possibly including details including performance specifications (also including manufacture details such as lot, factory source, build date, inventory numbers, invoice or tracking numbers, subassembly/assembly numbers, etc). In one embodiment, the codes and/or data are included on a chip embedded in the suspension. In one embodiment, the chip is an active or passive radio frequency identification (“RFID”) (optionally including data) chip. In one embodiment, the controller 300 detects the chip and based on the data received there from proceeds to configure, or suggest configuration for, the suspension.


In one embodiment, the controller 300 operates in set up mode where it uses rider input weight and suspension product data to suggest initial spring preload and damper settings for the vehicle 100 suspension. In one embodiment, the controller 300 operates in a ride mode wherein it monitors suspension movement (e.g. average travel used versus available, portion or range of travel used, number and severity of bottom out or top out events) and then uses that data in conjunction with the rider and suspension data to suggest changes to the suspension set up that better utilize or maximize usage of the suspension capabilities. In one embodiment the controller monitors compression range of the suspension to determine whether or not the suspension is set up for optimal use of its range over a given terrain. Too many top out events or bottom out events or operation generally over only a portion of the available range will indicate a possibly needed adjustment to the spring pressure and/or damping rate and the controller 300, upon calculating such range usage sends an appropriate suggestion to the device 500. In one embodiment a GPS unit of, for example the device, transmits real time GPS data to the controller 300 and such data is overlayed or paired with corresponding suspension data along an elapsed (or relative sequence) time (or other suitable common data marker or “datum” type) synchronous data marker.


In one embodiment, rebound setting can be automatically achieved by utilizing the air spring pressure or coil spring preload needed to achieve proper sag. The rebound setting is then achieved via feeding the air spring pressure for an air shock, or an oil pressure signal for a coil shock, down the damper shaft to a pressure sensitive damping valve at the damper shaft piston. There would still be an external rebound adjustor to make incremental changes from the predetermined setting to account for varied terrain/conditions, and/or riding style and preference.


In one embodiment, initial sag can be automatically set and facilitated by having a position valve within the shock for a given length bleed off air pressure until a specific sag level is achieved. Each shock stroke would have a specific length of sag/position valve. The user 600 would pressurize their shock to a maximum shock pressure of, for example, 300 psi or so. The actual max number is not important at this point. The idea is to over pressurize the shock beyond any reasonable properly set sag pressure. The user 600 then switches the shock to be in setup or sag mode. The user 600 then sits on the bike. In one embodiment, the shock will bleed air from the air spring until the position valve encounters a shut off abutment which thereby shuts the bleed valve. In one embodiment, the shock, having an axial position sensor 200 and a controller 300, to measure that compression of the shock from full extension (or any selected set “zero” position datum), “knows” it is extended beyond a proper sag level and a an electrically actuated valve is opened to bleed air pressure from the air spring in a controlled manner until the proper predetermined sag level is reached, at which point the valve automatically closes and the shock opts itself out of sag mode. Alternatively, the user 600 can switch the sag set up mode off upon reaching a proper sag setting. In one embodiment, with the controller 300 in normal ride mode the user 600/vehicle 100 will now be in a proper starting point for their sag measurement. When in riding mode, more pressure can be added to the air spring or pressure can be reduced from the air spring to accommodate different rider styles and or terrain. This auto sag feature can be achieved electronically as well, by having a position sensor 200 in the shock, and the shock model data allowing the controller 300 to adjust spring preload (e.g. air pressure) appropriately for the given model (as determined by the controller 300 in a query) what sag measurement it should achieve. An electronically controlled pressure relief valve is utilized to bleed off air spring pressure until the sensor 200 determines the shock is at its' proper sag. The pressure relief valve is then directed to close. Proper sag is achieved.


In one embodiment, the system 1000 can be utilized by integrating certain data collection sensors 200 to both aid in initial set up and to provide hints on how to tweak the vehicle 100 suspension system beyond an initial set up. At least position sensors 200 would be incorporated into the shock or the fork. The sensors 200 communicate with the controller 300. In one embodiment, the sensor 200/controller 300 interface would be wireless. A wired connection would still be acceptable. Data (e.g. model, specifications) corresponding to all possible suspension products that may interface with the controller 300 would be stored in the controller 300 so when one or another of those products is plugged in, or booted up if wirelessly connected, the controller 300 would know lengths, travels, external adjustment features etc. For that/those products the controller 300 would then walk the user 600 through a proper set up routine, starting with sag for example. The user 600 would sit on the bike and the rider sag measurement for the fork and shock would be displayed on the communication device 500 for example. The controller 300 will know what product it is trying to get adjusted properly and will make pressure recommendations for the user 600 to input to the shock or fork. The user 600 will then sit on the bike again, and in this iterative and interactive process, arrive at a perfect sag setting for the fork and shock product being used. In a more elaborate system, the controller 300 will “know” what pressure is in the fork and shock, and will make rebound recommendations based on those settings. In a simpler form, the controller 300 will ask the user 600 to input their final sag attaining pressures and will then make rebound recommendations based on the product and pressures. The controller 300 will also make compression damping setting recommendations based on the product it knows it is communicating with. The user 600 will then go out and ride the product. The controller 300 will transfer to data logging mode once the bike is being ridden or in a simpler form when the user 600 puts the system into ride mode. The controller 300 will log and save bottom out events, average travel used, identify too quick or too slow rebound events, etc. If average travel is more than a specified amount, the controller 300 will make recommendations on settings to have the system hold itself up better in the stroke. If the average travel used in less than a specified amount the controller 300 will make recommendations on settings to utilize more travel. Full travel events will be evaluated versus the average travel used data and make recommendations on how to reduce or increase the amount of full travel events. Computer (PC/laptop) software will be developed so the data logged can be downloaded to the computer system 400 for further evaluation. A website, such as the FOX RACING SHOX website, can be utilized as a place for riders to go to check out settings other riders are using and why, and to provide a way to “geek out” and spend time in a community, such as a FOX RACING SHOX community. In one embodiment, the controller 300 will log ridden hours and will prompt the user 600 to perform certain maintenance operations, and when data is downloaded to the computer system 400, such as a desktop/laptop machine, a link to the service procedure for the particular recommended service will pop up. The link will be to a video guild on how to perform the service, tools needed etc., if a user 600 is at the max of a particular adjustment feature on the closed or open side, the controller 300 will make a recommendation to have a service provider, such as FOX RACING SHOX, re-valve their system to get that particular adjustment feature into the middle of its' range again, and will make recommendations to a service technician, such as a FOX RACING SHOX service tech, on what direction to make the valving changes, etc. A more elaborate system 1000 can incorporate accelerometers, pressure sensors, etc.


The electronically adjustable damping as described herein and in U.S. provisional patent application Ser. No. 61/175,422 may be integrated with the controller 300 and associated features described herein such that in one embodiment the controller 300 calculates needed changes based on sensor 200 input and facilitates those changes to dampers, air springs or other suitably adjustable suspension portions.


In one embodiment, the system 1000 may include one or more of the following features: electric (or electronic) sensor(s) (accelerometer) that senses upward acceleration of the wheel; electric (or electronic) valve(s) that has the same response time or faster as a mechanical (BrassMass) inertia valve fork cartridge; a lightweight, small form factor, fast charging battery that provides 30 hours of ride time (enough to race a 24 hour event); a fixed blow off; and a velocity sensitive shimmed damping.


In one embodiment, the system 1000 may include one or more of the following features: a processor to actively process sensor data and adjust opening of valve accordingly; a wireless communication to vehicle handlebar mounted control console (also rear shock compatible); an adjustable manual mechanical blow-off; an electronic wirelessly adjustable blow-off; an adjustable “g” threshold to open valve; an adjustable “timer” to dose valve; an adjustable low speed bleed (which could be a separate adjustment, or a trim adjustment of the main on-off valve); a program mode where it automatically alters open and closing parameters based on sensor input (for example sensing a rock garden); auto (Inertia sensing)/On (always lockout)/Off (no lockout) modes; a wheel speed sensor that can also dictate how the fork responded; a travel sensor either for bottom out, or discrete travel points (to aid in proper sag); and a data storage.


In one embodiment, the system 1000 may include one or more of the following features: battery charging via base stud with cap (similar to 36/40); all battery/sensing/actuation at bottom of cartridge; manual mechanical rebound adjust on top; on/off and/or auto on/off switch or system; a GPS could be incorporated to program in sections for race courses, either ahead of time, or on the fly for multi lap races (this could even be used for a DH course with a prolonged pedaling section).



FIG. 5 illustrates a block diagram of the controller 300 according to one embodiment. The controller 300 may include a water-proof housing (and shock resistant components or potting) having a front panel 310 and a rear panel 320. The front panel 310 may comprise a connection assembly 311, such as a universal serial bus (“USB”) port, for data read-out and/or power or battery charging; a switch 312, such as a momentary contact switch for turning the controller 300 on and off; and an indicator 313, such as a light emitting diode (“LED”) for on/off and power or battery status. The rear panel 320 may comprise one or more analog inputs 321, such as eight analog inputs each having 10 bit, 500 Hz SR, and 5V ratio-metric communication features; and one or more digital inputs 322, such as eight digital inputs for communication with Reed/Hall-type switches. The analog and digital sensor signals received by the inputs 322, 321 may be communicated to one or more ESD and/or signal conditioning devices 330. The rear panel 320 may comprise a serial port 323/324 for communication with one or more serial devices, such as GPS and Bluetooth; and a power output 325 for transmitting a 5V and/or 20 mA signal. Each of the components and/or devices in communication with the controller 300 via the front and rear panels may also communicate with a processor 340 of the controller 300.


The processor 340, such as a microprocessor or mirco-computer, may communicate with a ANT radio frequency transceiver 343 (e.g. ANT AP2 module, 20×20×3 mm surface-mount), a memory card socket 342 (for communication with a SD card (2 GB), for example), a debug serial interface 341, and one or more analog inputs 344, such as four analog inputs for self-test including Li-polymer battery voltage, +3.3V logic power supply, +5.0V sensor supply, and internal temperature sensor (e.g. LM34-type). The controller 300 may also include a power system 350 including a battery 351, a battery charger 352, and one or more converters 353, 354, such as voltage converters. In one embodiment, the battery 351 may be a Li-polymer battery with the following features: 850 mA-hr charge, about 36 mm×62 mm×3.9 mm dimensions, and a 90 minute charge from USB with about an 8-plus hour operating life. In one embodiment, the converter 353 may be a voltage converter operable to provide a +5.0V power signal to one or more sensors in communication with the controller 300. In one embodiment, the converter 354 may be a voltage converter operable to provide a +3.3V power signal to processor 340 and one or more components in communication with the processor. In one embodiment, the components of the controller 300 may provided on a printed circuit assembly size of about 1.6″×3.0″×0.3″ in dimension, including a 0.062″ thick circuit 6-layer circuit board, a 0.200″ top-side max component height, and/or a 0.040″ bottom-side max component height. In one embodiment, the processor 340 may be configured to send and/or receive one or more signals to and from the other components of the controller 300 for use with the embodiments described herein.



FIG. 6 illustrates a block diagram of a software program 605 that may be used with the system 1000, according to one embodiment. FIGS. 7-11 illustrate a block diagram example of each step of the software program 605 process. The steps used with the software program 605 may be performed and/or repeated in any order.


A first step 610 may include creating a profile. As illustrated in FIG. 7, data about the vehicle 100 and the user 600 may be entered by the user 600 on the computer system 400 (e.g. PC, laptop, etc.) and/or on the communication device 500 (e.g. iPhone, iPod, Garmin, other interface devices, etc.). The computer system 400 may be configured with the full features of the software program, and may include a hard drive to store the vehicle 100 and user 600 data, which data may also be saved to the controller 300. The communication device 500 may include a minimal set of essential questions to be answered by the user 600, the responses to which may be communicated to the controller 300. The data may be stored on the computer system 400 and/or the communication device 500, and may also be sent and stored on the controller 300. The controller 300 may include a storage directory that can transfer and/or receive data from the computer system 400 and/or the communication device 500. Data regarding the basic and advanced setup (further described below) may be stored in the controller 300 in an alternate location on a memory card to be used internally. Several profiles can be stored on the controller 300 for use with different vehicles 100. The computer system 400 and/or communication device 500 can be used to select the profile to activate on the controller 300.


A second step 620 may include setting up basic vehicle 100 parameters. The software program for use with the system 1000 may assist shops and individuals with basic setup parameters of their vehicle 100 components, such as the vehicle suspension. The software program may run on all interface platforms, and may bring the user 600 through a step by step structured procedure to set up the vehicle 100 component based on the data of the vehicle 100 and the user 600 from the profile, as well as specific riding conditions and style anticipated. In one embodiment, the software program may work without the controller 300, but without automatic measurement and some limitations.



FIG. 8 illustrates a procedural example 800 of the second step 620 used to set up basic vehicle 100 suspension system parameters. In particular, the user 600 communicates with the computer system 400 and/or the communication device 500 as described in the first step 610 to provide user 600 and vehicle 100 data, which the software program may then use to guide the user 600 through a set up procedure. In one embodiment, the data may be manually entered if no controller 300 is present. A first command prompt 815 may instruct the user 600 to set shock absorber pressures and spring rates based on vehicle type, user weight and style. A second command prompt 820 may instruct the user 600 to open the vehicle 100 damper adjustment. If the controller 300 is not available, a third command prompt 825 may instruct the user 600 to get on the vehicle 100, bounce, and measure the sag. If the controller 300 is available, a fourth command prompt 830 may instruct the user 600 to get on the vehicle 100 and bounce, so that the controller 300 can acquire the sag. A fifth command prompt 835 may instruct the user 600 to read the percentage sag, and if the sag is bad, the user 600 may be directed to the first prompt 815 to repeat the procedure. However, if the sag reading is good, then a sixth prompt 840 may instruct the user 600 to set the shock absorber and damper at recommended settings. If the controller 300 is not available, a seventh command prompt 845 may notify the user 600 that the basic set up procedure is complete. If the controller 300 is available, an eighth command prompt 850 may instruct the user 600 to compress the vehicle's 100 front and rear suspension against the ground and then pick the vehicle 100 up off the ground quickly to acquire/check rebound settings. A ninth prompt 855 may instruct the user 600 to refine the rebound to a recommended setting. A final prompt 860 may notify the user 600 that the basic set up procedure is complete and/or that the final set up parameters have been saved and stored.


A third step 630 may include setting up advanced vehicle 100 parameters. As illustrated in FIG. 9, the user 600 may set the controller 300 via the computer system 400 and/or communication system 500 into an advanced setup mode where it collects data from the sensors 300 and processes the data. The controller 300 may collect data while riding the vehicle 100 and process the data with parameters from the profile created in the first step 610. In one embodiment, when in the advanced setup mode, the controller 300 collects data from front and rear position, as well as the wheel speed sensors 300 (and any additional sensors that are used) for example during the operation of the vehicle 100. The data is processed to collect significant metrics such as maximum compression and rebound velocities, number of bottom outs, average ride height, and/or pedal bob detection. The data results are updated and stored in an onboard memory device. When connected back to the computer system 400 and/or communication device 500 at the end of the operation of the vehicle 100, a series of questions may be prompted by the controller 300 to the user 600. The questions may be displayed in a fixed format on a user interface or display of the computer system 400 and/or the communication device 500. Based on the answers to the questions provided by the user 600 and the processed data, suggestions will be made to the user 600 as how to further refine the vehicle 100 setup. This is an interactive process so the process can be repeated to continue to develop the vehicle 100 setup.


A fourth step 640 may include acquiring data from the sensor(s) 200 about the operation of the vehicle 100. As illustrated in FIG. 10, the user 600 may set the controller 300 via the computer system 400 and/or communication system 500 into a data acquisition mode where it collects and stores raw data from the sensors 300. In one embodiment, when in the data acquisition mode, the controller 300 collects data from front and rear position, as well as the wheel speed sensors 300 (and any additional sensors that are used) for example during the operation of the vehicle 100. The controller 300 may collect the data while riding the vehicle 100 and store the data on the memory card without processing the data. When connected back to the computer system 400 and/or communication device 500 at the end of the operation of the vehicle 100, the data can be downloaded thereto and analyzed. Additional post processing may be performed on the data once downloaded to assist in the analyzing of the data. The computer system 400 and/or communication device 500 can be used to graphically display the data and allow for manipulation, such as through math channels and overlaying data. The software program on the computer system 400 and/or communication device 500 may generate reports, such as histograms of travel, damper speeds, and pedal bob detection. The data acquisition may be thought of as an advanced function, so it is left to the user 600 to interpolate the data and decide on changes to make. An instructional guide may be provided.


A fifth step 650 may include setting up an electronic file, such as an electronic notebook. As illustrated in FIG. 11, the user 600 may create, edit, and view the electronic notebook using the computer system 400 and/or the communication device 500. The electronic notebook can be used to track vehicle 100 setups and user 600 notes about the vehicle handling, as well as general notes about races, rides, and conditions. Vehicle setups will be able to be saved to the electronic notebook from the profile created in the first step 610 described above. The vehicle setups can be transferred back to the controller 300, the computer system 400, and/or the communication device 500 to run the basic and/or advance set up procedures for different events and/or vehicles. Tracking changes to the vehicle will be one of the key features of the software program so that a history/database of what changes were made to the vehicle 100 and what effect they had will be compiled. The electronic notebook can be searchable so that a symptom can be searched and possible past solutions can be easily found.


In one embodiment, the system 1000 may be used to acquire performance data, including the operation of one or more components of the vehicle 100 and the location of the vehicle 100, during operation of the vehicle 100. The performance data may be associated with a time maker to track the actual time when the performance data was measured. Using the system 1000, the user 600 can utilize the performance data to correlate the actual location of the vehicle 100 at a specific time to a specific operational characteristic of a component of the vehicle 100. In this manner, the user 600 may be able to plot a course over which the vehicle 100 can be operated, and adjust the vehicle 100 components to an optimum setting as the vehicle 100 is operated along the course.


In one embodiment, the user 600 may be able to view the data acquired by the controller 300 during operation of the vehicle 100 via the communication device 500, which may be coupled to the vehicle 100 in any manner for ease of viewing. In one embodiment, the user 600 may be able to view the data acquired by the controller 300 during and/or after operation of the vehicle 100 via the computer system 400 and/or the communication device 500. In one embodiment, the controller 300 may be operable to acquire data from the sensors 200 coupled to the vehicle 100 at pre-determined intervals. In one embodiment, the controller 300 may be operable to automatically adjust (increase, decrease, maintain) the intervals at which to acquire data from the sensors 200 based on the operating performance of the components of the vehicle 100.



FIG. 12 illustrates a block diagram of one process of use with the system 1000 according to the embodiments described herein. As illustrated, during, prior to, and/or after operation of the vehicle 100, the sensor 200 may measure an operational feature of one or more components of the vehicle 100, such as the travel of the vehicle suspension. The processor or controller 300 may be operable to receive the measurement data from the sensor 200 via wired and/or wireless communication. The processor or controller 300 may analyze the data and compare the data to pre-programmed vehicle suspension operational settings that are stored on the processor or controller 300. Based on the analysis, the processor or controller 300 may output a suggested vehicle setting 310 to the computer system 400 and/or communication device 500 via wired and/or wireless communication. The suggested vehicle setting 310 may be displayed on the computer system 400 and/or communication device 500, and may be in the form of an instruction regarding an adjustable feature of the vehicle 100 suspension and/or a rendition of the measurement data that will aid the user 600 in evaluating the setting of an adjustable feature of the vehicle 100 suspension.


As will be appreciated by one skilled in the art, aspects of the invention may be embodied as a system, method or computer program product. Accordingly, aspects of the invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “device,” “sensor,” “processor,” “controller,” or “system,” such as system 1000. Furthermore, aspects of the invention (such as one or more embodiments of the vehicle 100, the sensor 200, the processor or controller 300, the computer system 400, and/or the communication device 500) may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.


Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.


A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.


Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.


Computer program code for carrying out operations for aspects of the invention (such as one or more embodiments of the vehicle 100, the sensor 200, the processor or controller 300, the computer system 400, and/or the communication device 500) may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).


These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks illustrated in one or more of FIGS. 1-12.


The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks illustrated in one or more of FIGS. 1-12.


In one embodiment, a suspension system may comprise a vehicle suspension, a sensor, a computer readable medium, a processor, a transmitter, and a graphical user interface. The sensor may be positioned to sense a feature of the suspension. The computer readable medium may have an operative communication link with the sensor. The processor may have an operative communication link with the computer readable medium. The transmitter may have an operative communication link with the processor. And the graphical user interface may have an operative communication link with the transmitter.


In one embodiment, a suspension system may comprise a vehicle suspension, a sensor, a processor, a transmitter, and a graphical user interface. The sensor may be positioned to sense a feature of the suspension. The processor may have an operative communication link with the sensor, and an operative communication link with a computer readable medium. The transmitter may have an operative communication link with the processor. And the graphical user interface may have an operative communication link with the transmitter.


In one embodiment, the operative communication link with the sensor comprises a wire. In one embodiment, the operative communication with the transmitter comprises a wireless protocol. The operative communication link with the sensor may transfer information at a first data rate, and the operative communication link with the transmitter may transfer information at a second data rate. The first data rate may be greater than the second data rate. The feature of the suspension may comprise at least one of state of compression, velocity, internal pressure and temperature.


In one embodiment, the computer readable medium stores a first amount of information related to real time performance of the suspension, and the graphical user interface receives a second amount of information related to the suspension performance. The first amount of information may be greater than the second amount of information. At least some of the information related to real time performance may be retrieved by the processor, via the operative communication link with the computer readable medium, and may be transformed by the processor into the information related to the suspension performance. The transmitter may transmit at least some of the information related to the suspension performance to the graphical user interface via the operative communication link with the transmitter. The graphical user interface may include a program for receiving information via the operative communication link with the transmitter. The program may include a template format for the graphical user interface into which format received data may be displayed. The graphical user interface may further process at least some of the information related to the suspension performance and may display a result within the template format. The result may comprise a suggestion to alter a set up condition of the suspension. The result may comprise suspension usage efficiency data that illustrates the adequacy, or lack thereof, of the state of at least one initial set up condition.


In one embodiment, the processor may have an operative communication link with a feature controller of the suspension, and the feature controller may comprise a damping adjuster.


In one embodiment, the processor may comprise a receiver, and the graphical user interface may comprise a GUI transmitter having an operative communication link with the receiver.


In one embodiment, a vehicle suspension system may comprise a first portion having a second portion movably engaged therewith. A sensor may be positioned to measure an operational characteristic of the first portion relative to the second portion. A processor may be in communication with the sensor and may have a program to calculate data representative of the operational characteristic. A user interface may be used for displaying a rendition of the data.


While the foregoing is directed to embodiments of the invention, other and further embodiments of the invention may be implemented without departing from the scope of the invention, and the scope thereof is determined by the claims that follow.

Claims
  • 1. A system for a vehicle, comprising: a rear vehicle suspension;a first sensor positioned proximate a rear axle of the vehicle, the first sensor to sense changes in a terrain, said first sensor comprising: a piezoelectric high frequency exciter coupled to a telescopic tube of said rear vehicle suspension, said piezoelectric high frequency exciter configured such that it substantially continuously induces impacts to said telescopic tube;a second sensor coupled with the rear vehicle suspension, the second sensor to measure suspension operational characteristics of the rear vehicle suspension, said second sensor comprising: a piezoelectric accelerometer coupled to said telescopic tube, said piezoelectric accelerometer configured such that it monitors vibration of said telescopic tube; anda processor in communication with the first sensor and the second sensor, the processor operable to suggest an operational setting of the rear vehicle suspension in response to an input from the first sensor and the second sensor corresponding to a sensed change in terrain and the rear vehicle suspension operational characteristics, respectively, the suggested operational setting to enable the rear vehicle suspensions to achieve target level rear vehicle suspension capabilities over a given terrain, wherein the suggested operational setting is displayed on a device in communication with the processor as at least an instruction via an alphanumeric command prompt to a user.
  • 2. The system of claim 1, further comprising: a front vehicle suspension; anda third sensor coupled with the front vehicle suspension the third sensor to measure suspension operational characteristics of the front vehicle suspension.
  • 3. The system of claim 1, wherein the first sensor and the second sensor includes a position sensor, and wherein the suspension operational characteristics of the rear vehicle suspension include a position of the rear vehicle suspension.
  • 4. The system of claim 3, wherein the position of the rear vehicle suspension corresponds to a stroke of the rear vehicle suspension during compression or rebound.
  • 5. The system of claim 1, wherein the suspension system includes a damper valve, and the suspension operational characteristics of the rear vehicle suspension is a position of the damper valve between a full open setting and a full closed setting.
  • 6. The system of claim 1, wherein the processor is in communication with the first sensor and the second sensor via at least one of wired communication and wireless communication.
  • 7. The system of claim 1, wherein the second sensor is operable to measure a plurality of suspension operational characteristics of the rear vehicle suspension, wherein the plurality of suspension operational characteristics of the rear vehicle suspension include position, velocity, and acceleration.
  • 8. The system of claim 1, wherein the second sensor comprises a GPS.
  • 9. The system of claim 1, wherein the device coupled with the processor is at least one of a computer system and a communication device, each operable to communicate with the processor and display data corresponding to the operational characteristic measured by the sensor.
  • 10. The system of claim 9, wherein the at least one computer system and communication device includes at least one of a personal desktop computer, a laptop computer, and a hand-held personal computing device.
  • 11. The system of claim 9, wherein the at least one computer system and communication device is operable to adjust the rear vehicle suspension to the operational setting suggested by the processor.
  • 12. A system for a vehicle, comprising: a first sensor position proximate a rear axle of the vehicle, the first sensor to sense changes in a terrain;a second sensor coupled with a front vehicle suspension, the second sensor to measure suspension operational characteristics of the front vehicle suspension, said second sensor comprising: a piezoelectric high frequency exciter coupled to a telescopic tube of said front vehicle suspension, said piezoelectric high frequency exciter configured such that it substantially continuously induces impacts to said telescopic tube; anda piezoelectric accelerometer coupled to said telescopic tube, said piezoelectric accelerometer configured such that it monitors vibration of said telescopic tube;a processor operable to receive data from the first sensor and the second sensor corresponding to the suspension operational characteristics of the front vehicle suspension; anda communication device operable to receive data from the processor and display, on a device coupled with the processor, information regarding the suspension operational characteristics of the front vehicle suspension, wherein the information comprises a suggested operational setting of the front vehicle suspension, the suggested operational setting to enable the front vehicle suspension to achieve target level front vehicle suspension capabilities over a given terrain, wherein the suggested operational setting is displayed on a device in communication with the processor as at least an instruction via an alphanumeric command prompt to a user.
  • 13. The system of claim 12, wherein the communication device includes a software program operable to generate the information based on the data received from the processor.
  • 14. The system of claim 12, wherein the first sensor and the second sensor include a position sensor, and wherein the suspension operational characteristics of the front vehicle suspension includes an initial sag, compression, or rebound setting of the front vehicle suspension.
  • 15. The system of claim 12, wherein the processor is in communication with at least one of the first sensor and the second sensor via at least one of wired communication and wireless communication.
  • 16. The system of claim 12, wherein the processor is in communication with the communication device via at least one of wired communication and wireless communication.
  • 17. The system of claim 12, further comprising a computer system operable to receive the data from the processor and display the data corresponding to the suspension operational characteristics of the front vehicle suspension.
  • 18. The system of claim 12, wherein the communication device is operable to adjust the suspension operational characteristics of the front vehicle suspension to a recommended setting.
  • 19. A method for adjusting a vehicle suspension of a vehicle, comprising: receiving vehicle suspension data with a processor, wherein the vehicle suspension data comprises: sensor data from a first sensor comprising a piezoelectric high frequency exciter coupled to a telescopic tube of said vehicle suspension, said piezoelectric high frequency exciter substantially continuously inducing impacts to said telescopic tube, the first sensor to sense changes in a terrain;sensor data from a second sensor coupled with a rear vehicle suspension, said second sensor comprising a piezoelectric accelerometer coupled to said telescopic tube, said piezoelectric accelerometer configured such that it monitors vibration of said telescopic tube, the second sensor to measure suspension operational characteristics of the rear vehicle suspension;sensor data from a third sensor coupled with a front vehicle suspension, the set of sensors third sensor to measure suspension operational characteristics of the front vehicle suspension;calculating a vehicle suspension setting suggestion with the processor, the vehicle suspension setting suggestion to enable the rear vehicle suspension and the front vehicle suspension to achieve target level vehicle suspension capabilities over a given terrain, wherein the vehicle suspension setting suggestion is at least an instruction via an alphanumeric command prompt to a user;communicating the vehicle suspension setting suggestion to a user interface device;receiving user input in accordance with the vehicle suspension setting suggestion, wherein the user input comprises an adjustment to a feature of the vehicle; andadjusting at least one of the rear vehicle suspension and the front vehicle suspension based on the user input.
  • 20. The method of claim 19, further comprising obtaining the suspension data with at least one of the second sensor and the third sensor and communicating the suspension data to the processor via at least one of wired communication and wireless communication.
  • 21. The method of claim 19, further comprising inputting the suspension data into the user interface device, and communicating the suspension data to the processor via at least one of wired communication and wireless communication.
  • 22. The method of claim 19, further comprising communicating the suspension setting suggestion to the user interface device via at least one of wired communication and wireless communication.
  • 23. The method of claim 19, further comprising manually adjusting at least one of the rear vehicle suspension and the front vehicle suspension based on the vehicle suspension setting suggestion.
  • 24. The method of claim 19, further comprising creating a profile, entering the vehicle suspension data into the profile using the user interface device, and communicating the vehicle suspension data to the processor.
  • 25. The method of claim 19, further comprising obtaining the vehicle suspension data and communicating the vehicle suspension data to the processor while operating the vehicle.
  • 26. The method of claim 19, further comprising creating an electronic file with the user interface device, and tracking the vehicle suspension data and the vehicle suspension setting suggestion using the electronic file.
  • 27. A suspension system, comprising: a rear vehicle suspension;a first sensor positioned proximate a rear axle of the vehicle, the first sensor to sense changes in a terrain, said first sensor comprising: a piezoelectric high frequency exciter coupled to a telescopic tube of said rear vehicle suspension, said piezoelectric high frequency exciter configured such that it substantially continuously induces impacts to said telescopic tube;a second sensor coupled with the rear vehicle suspension, the second sensor to measure suspension operational characteristics of the rear vehicle suspension, said second sensor comprising: a piezoelectric accelerometer coupled to said telescopic tube, said piezoelectric accelerometer configured such that it monitors vibration of said telescopic tube;a processor operable to make vehicle suspension setting suggestions, the processor having an operative communication link with the first sensor and the second sensor and having an operative communication link with a computer readable medium, the vehicle suspension setting suggestions to enable the rear vehicle suspension to achieve target level rear vehicle suspension capabilities over a given terrain, wherein the vehicle suspension setting suggestions are displayed on a device in communication with the processor and is at least an instruction via an alphanumeric command prompt to a user;a transmitter having an operative communication link with the processor; anda graphical user interface having an operative communication link with the transmitter.
  • 28. The system of claim 27, wherein the operative communication link with at least one of the first sensor and the second sensor comprises a wire.
  • 29. The system of claim 27, wherein operative communication with the transmitter comprises a wireless protocol.
  • 30. The system of claim 27, wherein the operative communication link with the first sensor and the second sensor transfers information at a first data rate and the operative communication link with the transmitter transfers information at a second data rate and the first data rate is greater than the second data rate.
  • 31. The system of claim 27, wherein the feature comprises at least one of state of compression, velocity, internal pressure and temperature.
  • 32. The system of claim 27, wherein the computer readable medium stores a first amount of information related to real time performance of the rear vehicle suspension and the graphical user interface receives a second amount of information related to the rear vehicle suspension performance and the first amount is greater than the second amount.
  • 33. The system of claim 32, wherein at least some of the information related to real time performance is retrieved by the processor, via the operative communication link with the computer readable medium, and is transformed by the processor into the information related to the rear vehicle suspension performance.
  • 34. The system of claim 33, wherein the transmitter transmits at least some of the information related to the rear vehicle suspension performance to the graphical user interface via the operative communication link with the transmitter.
  • 35. The system of claim 34, wherein the graphical user interface includes a program for receiving information via the operative communication link with the transmitter.
  • 36. The system of claim 35, wherein the program includes a template format for the graphical user interface into which format received data may be displayed.
  • 37. The system of claim 36, wherein the graphical user interface further processes the at least some of the information related to the rear vehicle suspension performance and displays a result within the template format.
  • 38. The system of claim 37, wherein the result comprises a suggestion to alter a set up condition of the rear vehicle suspension.
  • 39. The system of claim 37, wherein the result comprises rear vehicle suspension usage efficiency data that illustrates an adequacy, or lack thereof, of a state of at least one initial set up condition.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit of U.S. Provisional Patent Application Ser. No. 61/302,070, filed Feb. 5, 2010, and is a Continuation-In-Part of U.S. patent application Ser. No. 12/727,915, filed Mar. 19, 2010, now U.S. Pat. No. 9,140,325 which claims benefit of U.S. Provisional Patent Application Ser. No. 61/161,552, filed Mar. 19, 2009, and U.S. Provisional Patent Application Ser. No. 61/161,620, filed Mar. 19, 2009, and is also a Continuation-In-Part of U.S. patent application Ser. No. 12/773,671, filed May 4, 2010, now abandoned which claims benefit of U.S. Provisional Patent Application Ser. No. 61/175,422, filed May 4, 2009, each of the aforementioned related patent applications is herein incorporated by reference in its entirety.

US Referenced Citations (541)
Number Name Date Kind
1492731 Kerr May 1924 A
1575973 Coleman Mar 1926 A
1923011 Moulton Aug 1933 A
1948600 Templeton Feb 1934 A
2018312 Moulton Oct 1935 A
2115072 Hunt et al. Apr 1938 A
2259437 Dean Oct 1941 A
2492331 Spring Dec 1949 A
2540525 Howarth et al. Feb 1951 A
2697600 Gregoire Dec 1954 A
2725076 Hansen et al. Nov 1955 A
2729308 Koski et al. Jan 1956 A
2784962 Sherburne Mar 1957 A
2809722 Smith Oct 1957 A
2838140 Rasmusson et al. Jun 1958 A
2846028 Gunther Aug 1958 A
2879971 Demay Mar 1959 A
2897613 Davidson et al. Aug 1959 A
2941629 Etienne et al. Jun 1960 A
2967065 Schwendner Jan 1961 A
2991804 Merkle Jul 1961 A
3074709 Ellis et al. Jan 1963 A
3085530 Williamson Apr 1963 A
3087583 Bruns Apr 1963 A
3202413 Colmerauer Aug 1965 A
3206153 Burke Sep 1965 A
3284076 Gibson Nov 1966 A
3286797 Leibfritz et al. Nov 1966 A
3405625 Carlson et al. Oct 1968 A
3419849 Anderson et al. Dec 1968 A
3420493 Kraft et al. Jan 1969 A
3528700 Janu et al. Sep 1970 A
3556137 Billeter et al. Jan 1971 A
3559027 Arsem Jan 1971 A
3575442 Elliott et al. Apr 1971 A
3584331 Richard et al. Jun 1971 A
3603575 Arlasky et al. Sep 1971 A
3605960 Singer Sep 1971 A
3701544 Stankovich Oct 1972 A
3714953 Solvang Feb 1973 A
3750856 Kenworthy et al. Aug 1973 A
3784228 Hoffmann et al. Jan 1974 A
3791408 Saitou et al. Feb 1974 A
3830482 Norris Aug 1974 A
3842753 Ross et al. Oct 1974 A
3861487 Gill Jan 1975 A
3941402 Yankowski et al. Mar 1976 A
3981204 Starbard et al. Sep 1976 A
3986118 Madigan Oct 1976 A
4022113 Blatt et al. May 1977 A
4032829 Schenavar et al. Jun 1977 A
4036335 Thompson et al. Jul 1977 A
4072087 Mueller et al. Feb 1978 A
4103881 Simich Aug 1978 A
4131657 Ball et al. Dec 1978 A
4139186 Postema et al. Feb 1979 A
4159106 Nyman et al. Jun 1979 A
4174098 Baker et al. Nov 1979 A
4183509 Nishikawa et al. Jan 1980 A
4305566 Grawunde Dec 1981 A
4333668 Hendrickson et al. Jun 1982 A
4334711 Mazur et al. Jun 1982 A
4337850 Shimokura et al. Jul 1982 A
4348016 Milly Sep 1982 A
4366969 Benya et al. Jan 1983 A
4387781 Ezell et al. Jun 1983 A
4465299 Stone et al. Aug 1984 A
4474363 Numazawa et al. Oct 1984 A
4491207 Boonchanta et al. Jan 1985 A
4500827 Merritt et al. Feb 1985 A
4502673 Clark et al. Mar 1985 A
4548233 Wolfges Oct 1985 A
4570851 Cirillo et al. Feb 1986 A
4620619 Emura et al. Nov 1986 A
4630818 Saarinen Dec 1986 A
4634142 Woods et al. Jan 1987 A
4647068 Asami et al. Mar 1987 A
4655440 Eckert Apr 1987 A
4657280 Ohmori et al. Apr 1987 A
4659104 Tanaka et al. Apr 1987 A
4660689 Hayashi et al. Apr 1987 A
4673194 Sugasawa Jun 1987 A
4709779 Takehara Dec 1987 A
4729459 Inagaki et al. Mar 1988 A
4732244 Verkuylen Mar 1988 A
4744444 Gillingham May 1988 A
4750735 Furgerson et al. Jun 1988 A
4765648 Mander et al. Aug 1988 A
4773671 Inagaki Sep 1988 A
4786034 Heess et al. Nov 1988 A
4815575 Murty et al. Mar 1989 A
4821852 Yokoya Apr 1989 A
4826207 Yoshioka et al. May 1989 A
4830395 Foley May 1989 A
4836578 Soltis Jun 1989 A
4838394 Lemme et al. Jun 1989 A
4846317 Hudgens Jul 1989 A
4858733 Noguchi et al. Aug 1989 A
4919166 Sims et al. Apr 1990 A
4936424 Costa Jun 1990 A
4938228 Righter Jul 1990 A
4949262 Buma et al. Aug 1990 A
4949989 Kakizaki et al. Aug 1990 A
4975849 Ema et al. Dec 1990 A
4984819 Kakizaki et al. Jan 1991 A
5027303 Witte Jun 1991 A
5036934 Nishina et al. Aug 1991 A
5040381 Hazen Aug 1991 A
5044614 Rau Sep 1991 A
5060959 Davis et al. Oct 1991 A
5074624 Stauble et al. Dec 1991 A
5076404 Gustafsson Dec 1991 A
5080392 Bazergui Jan 1992 A
5094325 Smith Mar 1992 A
5105918 Hagiwara et al. Apr 1992 A
5113980 Furrer et al. May 1992 A
5152547 Davis Oct 1992 A
5161653 Hare Nov 1992 A
5163742 Topfer et al. Nov 1992 A
5178242 Nakamura et al. Jan 1993 A
5186481 Turner Feb 1993 A
5203584 Butsuen et al. Apr 1993 A
5207774 Wolfe et al. May 1993 A
5230364 Leng et al. Jul 1993 A
5236169 Johnsen et al. Aug 1993 A
5248014 Ashiba Sep 1993 A
5259487 Petek et al. Nov 1993 A
5263559 Mettner Nov 1993 A
5265902 Lewis Nov 1993 A
5277283 Yamaoka et al. Jan 1994 A
5284330 Carlson et al. Feb 1994 A
5293971 Kanari Mar 1994 A
5307907 Nakamura et al. May 1994 A
5318066 Burgorf et al. Jun 1994 A
5347186 Konotchick et al. Sep 1994 A
5348112 Vaillancourt Sep 1994 A
5372224 Samonil et al. Dec 1994 A
5381952 Duprez Jan 1995 A
5390949 Naganathan et al. Feb 1995 A
5396973 Schwemmer et al. Mar 1995 A
5398787 Woessner et al. Mar 1995 A
5413196 Forster May 1995 A
5467280 Kimura Nov 1995 A
5480011 Nagai et al. Jan 1996 A
5503258 Clarke et al. Apr 1996 A
5551674 Johnsen Sep 1996 A
5553836 Ericson Sep 1996 A
5578877 Tiemann Nov 1996 A
5588510 Wilke Dec 1996 A
5597180 Ganzel et al. Jan 1997 A
5598337 Butsuen et al. Jan 1997 A
5601164 Ohsaki et al. Feb 1997 A
5651433 Wirth et al. Jul 1997 A
5657840 Lizell Aug 1997 A
5687575 Keville et al. Nov 1997 A
5697477 Hiramoto et al. Dec 1997 A
5699885 Forster Dec 1997 A
5722645 Reitter Mar 1998 A
5803443 Chang Sep 1998 A
5806159 Inoue et al. Sep 1998 A
5810128 Eriksson et al. Sep 1998 A
5813456 Milner et al. Sep 1998 A
5813731 Newman et al. Sep 1998 A
5816281 Mixon Oct 1998 A
5818132 Konotchick et al. Oct 1998 A
5826935 DeFreitas Oct 1998 A
5853071 Robinson Dec 1998 A
5872418 Wischnewskiy Feb 1999 A
5884921 Katsuda et al. Mar 1999 A
5937975 Forster Aug 1999 A
5947238 Jolly et al. Sep 1999 A
5952823 Sprecher et al. Sep 1999 A
5954318 Kluhsman Sep 1999 A
5956951 O'Callaghan Sep 1999 A
5971116 Franklin Oct 1999 A
5992450 Parker et al. Nov 1999 A
5996745 Jones et al. Dec 1999 A
5996746 Turner et al. Dec 1999 A
5999868 Beno et al. Dec 1999 A
6000702 Streiter Dec 1999 A
6017047 Hoose Jan 2000 A
6035979 Foerster Mar 2000 A
6058340 Uchiyama et al. May 2000 A
6067490 Ichimaru et al. May 2000 A
6073536 Campbell Jun 2000 A
6073700 Tsuji et al. Jun 2000 A
6073736 Franklin Jun 2000 A
6092011 Hiramoto et al. Jul 2000 A
6105988 Turner et al. Aug 2000 A
6131709 Jolly et al. Oct 2000 A
6135434 Marking Oct 2000 A
6141969 Launchbury et al. Nov 2000 A
6151930 Carlson Nov 2000 A
6179098 Hayakawa et al. Jan 2001 B1
6196555 Gaibler Mar 2001 B1
6199669 Huang et al. Mar 2001 B1
6203026 Jones Mar 2001 B1
6213263 De Frenne Apr 2001 B1
6215217 Kurosawa et al. Apr 2001 B1
6217049 Becker Apr 2001 B1
6244398 Girvin et al. Jun 2001 B1
6254067 Yih Jul 2001 B1
6279702 Koh Aug 2001 B1
6293530 Delorenzis et al. Sep 2001 B1
6296092 Marking et al. Oct 2001 B1
6311962 Marking Nov 2001 B1
6318525 Vignocchi et al. Nov 2001 B1
6322468 Wing et al. Nov 2001 B1
6343807 Rathbun Feb 2002 B1
6360857 Fox et al. Mar 2002 B1
6371262 Katou et al. Apr 2002 B1
6371267 Kao et al. Apr 2002 B1
6378885 Ellsworth et al. Apr 2002 B1
6389341 Davis May 2002 B1
6390747 Commins May 2002 B1
6401883 Nyce et al. Jun 2002 B1
6412788 Ichimaru Jul 2002 B1
6415895 Marking et al. Jul 2002 B2
6418360 Spivey et al. Jul 2002 B1
6427812 Crawley et al. Aug 2002 B2
6434460 Uchino et al. Aug 2002 B1
6446771 Sintorn et al. Sep 2002 B1
6474454 Matsumoto et al. Nov 2002 B2
6474753 Rieth et al. Nov 2002 B1
6501554 Hackney et al. Dec 2002 B1
6502837 Hamilton et al. Jan 2003 B1
6510929 Gordaninejad et al. Jan 2003 B1
6520297 Lumpkin et al. Feb 2003 B1
6592136 Becker et al. Jul 2003 B2
6619615 Mayr et al. Sep 2003 B1
6648109 Farr et al. Nov 2003 B2
6659240 Dernebo Dec 2003 B2
6672687 Nishio Jan 2004 B2
6732033 LaPlante et al. May 2004 B2
6782980 Nakadate Aug 2004 B2
6817454 Nezu et al. Nov 2004 B2
6840257 Dario et al. Jan 2005 B2
6857625 Löser et al. Feb 2005 B2
6863291 Miyoshi Mar 2005 B2
6905203 Kremers et al. Jun 2005 B2
6920951 Song et al. Jul 2005 B2
6923853 Kremers et al. Aug 2005 B2
6935157 Miller Aug 2005 B2
6952060 Goldner et al. Oct 2005 B2
6959921 Rose Nov 2005 B2
6966412 Braswell et al. Nov 2005 B2
6978871 Holiviers Dec 2005 B2
6978872 Turner Dec 2005 B2
6991076 McAndrews Jan 2006 B2
7025367 McKinnon Apr 2006 B2
7076351 Hamilton et al. Jul 2006 B2
7128192 Fox Oct 2006 B2
7135794 Kühnel Nov 2006 B2
7147207 Jordan et al. Dec 2006 B2
7163222 Becker et al. Jan 2007 B2
7208845 Schaefer et al. Apr 2007 B2
7234575 Anderfaas et al. Jun 2007 B2
7234680 Hull et al. Jun 2007 B2
7243763 Carlson Jul 2007 B2
7255210 Larsson et al. Aug 2007 B2
7270221 McAndrews Sep 2007 B2
7287760 Quick et al. Oct 2007 B1
7293764 Fang Nov 2007 B2
7299112 LaPlante et al. Nov 2007 B2
7316406 Kimura et al. Jan 2008 B2
7325660 Norgaard et al. Feb 2008 B2
7363129 Barnicle et al. Apr 2008 B1
7374028 Fox May 2008 B2
7397355 Tracy Jul 2008 B2
7413063 Davis Aug 2008 B1
7422092 Hitchcock et al. Sep 2008 B2
7441638 Hanawa Oct 2008 B2
7469910 Münster et al. Dec 2008 B2
7484603 Fox Feb 2009 B2
7490705 Fox Feb 2009 B2
7523617 Colpitts et al. Apr 2009 B2
7569952 Bono et al. Aug 2009 B1
7581743 Graney Sep 2009 B2
7591352 Hanawa Sep 2009 B2
7600616 Anderfaas et al. Oct 2009 B2
7628259 Norgaard et al. Dec 2009 B2
7631882 Hirao et al. Dec 2009 B2
7654369 Murray et al. Feb 2010 B2
7673936 Hsu Mar 2010 B2
7684911 Seifert et al. Mar 2010 B2
7694785 Nakadate Apr 2010 B2
7694987 McAndrews Apr 2010 B2
7703585 Fox Apr 2010 B2
7722056 Inoue et al. May 2010 B2
7722069 Shirai May 2010 B2
7726042 Meschan Jun 2010 B2
7730906 Kleinert et al. Jun 2010 B2
7764990 Martikka et al. Jul 2010 B2
7770701 Davis Aug 2010 B1
7775128 Roessingh et al. Aug 2010 B2
7779974 Timoney et al. Aug 2010 B2
7795711 Sauciuc et al. Sep 2010 B2
7837213 Colegrove Nov 2010 B2
7857325 Copsey et al. Dec 2010 B2
7872764 Higgins-Luthman et al. Jan 2011 B2
7874567 Ichida et al. Jan 2011 B2
7909348 Klieber Mar 2011 B2
7927253 Dibenedetto et al. Apr 2011 B2
7931132 Braun Apr 2011 B2
7946163 Gartner May 2011 B2
8016349 Mouri Sep 2011 B2
8056392 Ryan et al. Nov 2011 B2
8087676 McIntyre Jan 2012 B2
8091910 Hara Jan 2012 B2
8104591 Barefoot et al. Jan 2012 B2
8127900 Inoue Mar 2012 B2
8136877 Walsh Mar 2012 B2
8141438 Roessingh et al. Mar 2012 B2
8151952 Lenz et al. Apr 2012 B2
8191964 Hsu Jun 2012 B2
8210106 Tai et al. Jul 2012 B2
8210330 Vandewal Jul 2012 B2
8256587 Bakke et al. Sep 2012 B2
8262062 Kamo et al. Sep 2012 B2
8262100 Thomas Sep 2012 B2
8285447 Bennett et al. Oct 2012 B2
8286982 Plantet Oct 2012 B2
8291889 Shafer et al. Oct 2012 B2
8292274 Adoline et al. Oct 2012 B2
8307965 Föster et al. Nov 2012 B2
8308124 Hsu Nov 2012 B2
8317261 Walsh Nov 2012 B2
8336683 McAndrews et al. Dec 2012 B2
8393446 Haugen Mar 2013 B2
8413773 Anderfaas et al. Apr 2013 B2
8423244 Proemm et al. Apr 2013 B2
8458080 Shirai Jun 2013 B2
8480064 Talavasek Jul 2013 B2
8550551 Shirai Oct 2013 B2
8556048 Maeda et al. Oct 2013 B2
8556049 Jee Oct 2013 B2
8596663 Shirai Dec 2013 B2
8622180 Wootten et al. Jan 2014 B2
8627932 Marking Jan 2014 B2
8641073 Lee Feb 2014 B2
8655548 Ichida et al. Feb 2014 B2
8744699 Yamaguchi Jun 2014 B2
8752682 Park et al. Jun 2014 B2
8763770 Marking Jul 2014 B2
8770357 Sims et al. Jul 2014 B2
8781680 Ichida Jul 2014 B2
8781690 Hara Jul 2014 B2
8814109 Calendrille et al. Aug 2014 B2
8833786 Camp Sep 2014 B2
8838335 Bass et al. Sep 2014 B2
8857580 Marking Oct 2014 B2
8868253 Hashimoto et al. Oct 2014 B2
8888115 Chubbuck Nov 2014 B2
8936139 Franklin et al. Jan 2015 B2
8950771 Felsl Feb 2015 B2
8955653 Marking Feb 2015 B2
8967343 Battlogg Mar 2015 B2
8991571 Murakami Mar 2015 B2
9033122 Ericksen et al. May 2015 B2
9038791 Marking May 2015 B2
9057416 Talavasek Jun 2015 B2
9073592 Hsu Jul 2015 B2
9103400 Becker Aug 2015 B2
9120362 Marking Sep 2015 B2
9126647 Kuo Sep 2015 B2
9140325 Cox et al. Sep 2015 B2
9157523 Miki Oct 2015 B2
9186949 Galasso et al. Nov 2015 B2
9194456 Laird et al. Nov 2015 B2
9199690 Watarai Dec 2015 B2
9229712 Takamoto et al. Jan 2016 B2
9239090 Marking et al. Jan 2016 B2
9278598 Galasso et al. Mar 2016 B2
9353818 Marking May 2016 B2
9366307 Marking Jun 2016 B2
9422018 Pelot et al. Aug 2016 B2
9452654 Ericksen et al. Sep 2016 B2
9523406 Galasso et al. Dec 2016 B2
9550405 Marking et al. Jan 2017 B2
9556925 Marking Jan 2017 B2
9616728 Marking Apr 2017 B2
9663181 Ericksen et al. May 2017 B2
9682604 Cox et al. Jun 2017 B2
20010017334 Vincent Aug 2001 A1
20010042663 Marking et al. Nov 2001 A1
20020000352 Matsumoto et al. Jan 2002 A1
20020032508 Uchino et al. Mar 2002 A1
20020050518 Roustaei May 2002 A1
20020063469 Nishio May 2002 A1
20020089107 Koh Jul 2002 A1
20020113347 Robbins et al. Aug 2002 A1
20020121416 Katayama et al. Sep 2002 A1
20020130000 Lisenker et al. Sep 2002 A1
20020130003 Lisenker et al. Sep 2002 A1
20020185581 Trask Dec 2002 A1
20030001346 Hamilton et al. Jan 2003 A1
20030001358 Becker et al. Jan 2003 A1
20030034697 Goldner et al. Feb 2003 A1
20030051954 Sendrea Mar 2003 A1
20030065430 Lu et al. Apr 2003 A1
20030075403 Dernebo Apr 2003 A1
20030103651 Novak Jun 2003 A1
20030160369 LaPlante et al. Aug 2003 A1
20040017455 Kremers et al. Jan 2004 A1
20040021754 Kremers et al. Feb 2004 A1
20040075350 Kuhnel Apr 2004 A1
20040099312 Boyer et al. May 2004 A1
20040208687 Sicz Oct 2004 A1
20040222056 Fox Nov 2004 A1
20040256778 Verriet Dec 2004 A1
20050077131 Russell Apr 2005 A1
20050098401 Hamilton et al. May 2005 A1
20050110229 Kimura et al. May 2005 A1
20050121269 Namuduri Jun 2005 A1
20050173849 Vandewal Aug 2005 A1
20050199455 Browne et al. Sep 2005 A1
20050227798 Ichida et al. Oct 2005 A1
20060064223 Voss Mar 2006 A1
20060065496 Fox Mar 2006 A1
20060066074 Turner Mar 2006 A1
20060076757 Bromley Apr 2006 A1
20060081431 Breese et al. Apr 2006 A1
20060096817 Norgaard et al. May 2006 A1
20060113834 Hanawa Jun 2006 A1
20060124414 Hanawa Jun 2006 A1
20060163551 Coenen et al. Jul 2006 A1
20060163787 Munster et al. Jul 2006 A1
20060175792 Sicz Aug 2006 A1
20060185951 Tanaka Aug 2006 A1
20060213082 Meschan Sep 2006 A1
20060219503 Kim Oct 2006 A1
20060225976 Nakadate Oct 2006 A1
20060237272 Huang Oct 2006 A1
20060289258 Fox Dec 2006 A1
20070007743 Becker et al. Jan 2007 A1
20070008096 Tracy Jan 2007 A1
20070034464 Barefoot Feb 2007 A1
20070039790 Timoney et al. Feb 2007 A1
20070051573 Norgaard et al. Mar 2007 A1
20070088475 Nordgren et al. Apr 2007 A1
20070090518 Sauciuc et al. Apr 2007 A1
20070119669 Anderfaas et al. May 2007 A1
20070272458 Taniguchi et al. Nov 2007 A1
20080006494 Vandewal Jan 2008 A1
20080009992 Izawa et al. Jan 2008 A1
20080018065 Hirao et al. Jan 2008 A1
20080029730 Kamo et al. Feb 2008 A1
20080041677 Namuduri Feb 2008 A1
20080059025 Furuichi et al. Mar 2008 A1
20080067019 Jensen et al. Mar 2008 A1
20080093820 McAndrews Apr 2008 A1
20080099968 Schroeder May 2008 A1
20080116622 Fox May 2008 A1
20080185244 Maeda et al. Aug 2008 A1
20080250844 Gartner Oct 2008 A1
20080303320 Schranz Dec 2008 A1
20080314706 Lun et al. Dec 2008 A1
20090001684 McAndrews et al. Jan 2009 A1
20090020382 Van Weelden et al. Jan 2009 A1
20090071773 Lun Mar 2009 A1
20090121398 Inoue May 2009 A1
20090171532 Ryan et al. Jul 2009 A1
20090192673 Song Jul 2009 A1
20090200126 Kondo et al. Aug 2009 A1
20090236807 Wootten et al. Sep 2009 A1
20090261542 McIntyre Oct 2009 A1
20090277736 McAndrews et al. Nov 2009 A1
20090288924 Murray et al. Nov 2009 A1
20090294231 Carlson et al. Dec 2009 A1
20090302558 Shirai Dec 2009 A1
20090324327 McAndrews Dec 2009 A1
20100010709 Song Jan 2010 A1
20100032254 Anderfaas et al. Feb 2010 A1
20100044975 Yablon et al. Feb 2010 A1
20100059964 Morris Mar 2010 A1
20100066051 Haugen Mar 2010 A1
20100109277 Furrer May 2010 A1
20100133764 Greaves Jun 2010 A1
20100170760 Marking Jul 2010 A1
20100186836 Yoshihiro et al. Jul 2010 A1
20100207351 Klieber Aug 2010 A1
20100244340 Wootten et al. Sep 2010 A1
20100252972 Cox et al. Oct 2010 A1
20100276238 Crasset Nov 2010 A1
20100276906 Galasso et al. Nov 2010 A1
20100308628 Hsu Dec 2010 A1
20100314917 Hsieh Dec 2010 A1
20100327542 Hara Dec 2010 A1
20110086686 Avent et al. Apr 2011 A1
20110095507 Plantet Apr 2011 A1
20110097139 Hsu Apr 2011 A1
20110109060 Earle et al. May 2011 A1
20110127706 Sims et al. Jun 2011 A1
20110174582 Wootten et al. Jul 2011 A1
20110202236 Galasso et al. Aug 2011 A1
20110204201 Kodama Aug 2011 A1
20110214956 Marking Sep 2011 A1
20110257848 Shirai Oct 2011 A1
20110284333 Krog et al. Nov 2011 A1
20110315494 Marking Dec 2011 A1
20120006949 Laird Jan 2012 A1
20120007327 Talavasek Jan 2012 A1
20120018263 Marking Jan 2012 A1
20120018264 King Jan 2012 A1
20120048665 Marking Mar 2012 A1
20120080279 Galasso et al. Apr 2012 A1
20120181126 De Kock Jul 2012 A1
20120222927 Marking Sep 2012 A1
20120228906 McAndrews Sep 2012 A1
20120253599 Shirai Oct 2012 A1
20120253600 Ichida et al. Oct 2012 A1
20120274043 Lee Nov 2012 A1
20120305350 Ericksen et al. Dec 2012 A1
20120312648 Yu et al. Dec 2012 A1
20130001030 Goldasz et al. Jan 2013 A1
20130037361 Park et al. Feb 2013 A1
20130090195 Yamaguchi Apr 2013 A1
20130119634 Camp May 2013 A1
20130144489 Galasso et al. Jun 2013 A1
20130168195 Park et al. Jul 2013 A1
20130292218 Ericksen et al. Nov 2013 A1
20130333993 Yu Dec 2013 A1
20140008160 Marking et al. Jan 2014 A1
20140027219 Marking et al. Jan 2014 A1
20140048365 Kim Feb 2014 A1
20140061419 Wehage Mar 2014 A1
20150081171 Ericksen et al. Mar 2015 A1
20150197308 Butora Jul 2015 A1
20160153516 Marking Jun 2016 A1
20160185178 Galasso et al. Jun 2016 A1
20160265615 Marking Sep 2016 A1
20160290431 Marking Oct 2016 A1
20160319899 Franklin et al. Nov 2016 A1
20160355226 Pelot et al. Dec 2016 A1
20170008363 Ericksen et al. Jan 2017 A1
20170136843 Marking May 2017 A1
20170184174 Marking Jun 2017 A1
20170259876 Ericksen et al. Sep 2017 A1
20170282669 Cox et al. Oct 2017 A1
20170291466 Tong Oct 2017 A1
20180010666 Marking Jan 2018 A1
Foreign Referenced Citations (46)
Number Date Country
3709447 Oct 1988 DE
3711442 Oct 1988 DE
3738048 May 1989 DE
3924166 Feb 1991 DE
4029090 Mar 1992 DE
4406918 Sep 1994 DE
10326675 Dec 2004 DE
102005025811 Dec 2006 DE
202010012738 Dec 2010 DE
207409 Jan 1987 EP
304801 Mar 1989 EP
652568 Jul 1993 EP
1138530 Oct 2001 EP
1241087 Sep 2002 EP
1355209 Oct 2003 EP
1394439 Mar 2004 EP
1449688 Aug 2004 EP
1623856 Feb 2006 EP
1757473 Feb 2007 EP
2103512 Sep 2009 EP
2248691 Nov 2010 EP
2357098 Aug 2011 EP
2410203 Jan 2012 EP
2479095 Jul 2012 EP
2495472 Sep 2012 EP
2357098 Oct 2014 EP
2848582 Mar 2015 EP
2289111 Nov 1995 GB
57173632 Oct 1982 JP
57173632 Nov 1982 JP
57182506 Nov 1982 JP
01106721 Apr 1989 JP
H0193637 Apr 1989 JP
H03113139 May 1991 JP
04-203540 Jul 1992 JP
04203540 Jul 1992 JP
05-149364 Jun 1993 JP
05149364 Jun 1993 JP
H084818 Jan 1996 JP
2005119548 May 2005 JP
2007302211 Nov 2007 JP
2008238921 Oct 2008 JP
20070076226 Jul 2007 KR
9840231 Sep 1998 WO
9906231 Feb 1999 WO
0027658 May 2000 WO
Non-Patent Literature Citations (25)
Entry
European Search Report, European Patent Application No. 14189773.6, May 4, 2015, 4 Pages.
“European Patent Office Final Decision dated Mar. 21, 2013”, European Patent Application No. 10161906.2.
“European Search Report and Written Opinion, European Patent Application No. 13165362.8”, Sep. 24, 2014, 6 Pages.
Electronic Translation of DE3709447A1.
English language abstract for EP 0207409 (no date).
EP Search Report for European Application No. 15163428.4, dated Jul. 3, 2017, 7 Pages.
Nilsson, “Opposition Letter Against EP-2357098”, Oct. 13, 2017, 7 pages.
“Communication Re Oral Proceedings for European Application No. 10161906, dated Feb. 15, 2013 (Feb. 15, 2013)”.
“European Search Report for European Application No. 10161906 , 3 pages, Sep. 15, 2010 (Sep. 15, 2010)”.
“European Search Report for European Application No. 10187320, 12 pages, Sep. 25, 2017 (Sep. 25, 2017)”.
“European Search Report for European Application No. 11153607, 3 pages, Aug. 10, 2012 (Aug. 10, 2012))”.
“European Search Report for European Application No. 11172553, 2 pages, Sep. 25, 2017 (Sep. 25, 2017)”.
“European Search Report for European Application No. 11175126, 2 pages, Sep. 25, 2017 (Sep. 25, 2017)”.
“European Search Report for European Application No. 12184150, 10 pages, Dec. 12, 2017 (Dec. 12, 2017)”.
“European Search Report for European Application No. 13158034 , 4 pages, Jun. 28, 2013 (Jun. 28, 2013))”.
“European Search Report for European Application No. 13174817.0, 13 pages, Jan. 8, 2018 (Jan. 8, 2018))”.
“European Search Report for European Application No. 15167426 , 4 pages, Sep. 18, 2015 (Sep. 18, 2015))”.
“European Search Report for European Application No. 17188022 , 9 pages, Feb. 1, 2018 (Feb. 1, 2018))”.
“Office Action for European Application No: 13158034.2, 5 pages, dated May 22, 2014”.
Shiozaki, et al., “SP-861-Vehicle Dynamics and Electronic Controlled Suspensions SAE Technical Paper Series No. 910661”, International Congress and Exposition, Detroit, Mich., Feb. 25-Mar 1, 1991.
Smith, ““The Bump Stop” in Engineer to win—Chapter 13: Springs and Shock Absorbers”, MBI Publishing Company and Motorbooks, USA XP055430818, ISBN: 978-0-87938-186-8, Dec. 31, 1984, 207.
Fachkunde Fahrradtechnik 4 Auflage, Gressmann_Inhaltv und S, 2011, 206-207.
Statement of Grounds of Appeal, EP App. No. 11153607A, May 28, 2018, 88 Pages.
Grounds of Appeal, EP App. No. 11153607.4, Jun. 1, 2018, 28 Pages.
Puhn, “How to Make Your Car Handle”, HPBooks, 1981, 7 Pages.
Related Publications (1)
Number Date Country
20110202236 A1 Aug 2011 US
Provisional Applications (4)
Number Date Country
61302070 Feb 2010 US
61161552 Mar 2009 US
61161620 Mar 2009 US
61175422 May 2009 US
Continuation in Parts (2)
Number Date Country
Parent 12727915 Mar 2010 US
Child 13022346 US
Parent 12773671 May 2010 US
Child 12727915 US